Documentation standards. The records that defend the deal.

The Oracle purchase you cannot document is the Oracle purchase you cannot defend, whether in an audit, a renewal, or an internal review. The buyer that keeps disciplined records protects both the entitlement position and the decision.

Documentation standards, the discipline of keeping the records an Oracle purchase requires, serve two distinct purposes, and both matter to the buyer. The first is the entitlement record, the documentation of what the organisation is licensed to use, which defends the compliance position in an Oracle audit. The second is the decision record, the documentation of how the purchase decision was made, which defends the procurement in an internal or external review. The customer that keeps disciplined documentation on both fronts protects its entitlement position and its decision. The customer that keeps poor records exposes both.

This article walks through the Oracle procurement documentation standards. The entitlement record and the license position. The deployment data and the usage record. The negotiation history and the decision record. The contemporaneous audit trail. The retention and the accessibility. The framework helps a procurement team keep the records the Oracle relationship requires.

The entitlement record and the license position.

The entitlement record is the documentation of what the organisation is licensed to use, and it is the foundation of the compliance position in an Oracle audit. The entitlement record should capture every license the organisation holds, the products, the metrics, the quantities, and the terms, drawn from the contracts, the order documents, and the support renewals, and it should be maintained as a current and complete record of the entitlement. The customer that maintains a complete entitlement record can demonstrate its license position when the audit comes. The customer that cannot reconstruct its entitlement is exposed.

The entitlement record is frequently harder to maintain than it appears, because the entitlement accumulates over years of contracts, orders, renewals, and amendments, and the record can become fragmented across documents and systems. The customer should consolidate the entitlement into a single, current record, reconciling it against the contracts and the order documents, so the license position is clear and defensible. The entitlement record is the foundation of the compliance position, and it deserves disciplined maintenance. See the audit documentation article.

The structural response is to maintain a complete and current entitlement record, consolidated from the contracts and order documents. The buyer that maintains the entitlement record defends the license position. See the sourcing procurement pillar and the Oracle Database product page.

The deployment data and the usage record.

The deployment data and the usage record document the organisation's actual use of the Oracle products, and they are the counterpart to the entitlement record in the compliance position. The compliance position is the comparison of the entitlement to the deployment, and the customer needs an accurate record of both. The deployment data should capture the actual installation and use of the Oracle products, the servers, the processors, the users, and the options, measured on the basis the licenses require, so the deployment can be compared to the entitlement.

The deployment data is frequently the more difficult of the two to maintain, because the deployment changes continuously as the organisation provisions, decommissions, and reconfigures its systems, and the usage record can drift from the actual deployment. The customer should maintain the deployment data on an ongoing basis, capturing the changes as they happen, so the compliance position is always current. The deployment data that is accurate and current allows the customer to manage its compliance proactively rather than discovering a gap in an audit. See the database compliance article.

The structural response is to maintain accurate and current deployment data, allowing the compliance position to be managed proactively. The buyer that maintains the deployment data manages its compliance. See our audit defense service and the database licensing deal type page.

The negotiation history and the decision record.

The negotiation history and the decision record document how the purchase decision was made, and they are the foundation of the defence of the procurement in an internal or external review. The decision record should capture the requirements, the alternatives considered, the evaluation, the approvals, and the rationale for the decision, so the procurement can be demonstrated to have followed the policy and reached a sound decision. The customer that maintains the decision record can defend the procurement when the review comes. The customer that cannot reconstruct the decision is exposed.

The negotiation history is a particularly valuable record, because it documents the offers, the counteroffers, and the terms negotiated, and it supports both the defence of the decision and the future negotiation. The negotiation history of a past deal informs the next negotiation, establishing the baseline of what was achieved and the terms that were agreed, and the customer that maintains the negotiation history negotiates from a record rather than a recollection. The negotiation history and the decision record serve both the defence and the future negotiation. See the procurement compliance article.

The structural response is to maintain the negotiation history and the decision record, documenting how the decision was made. The buyer that maintains the decision record defends the procurement. See the Oracle Negotiation Playbook white paper and the RFP process design article.

The contemporaneous audit trail.

The contemporaneous audit trail is the record built during the process rather than reconstructed after the fact, and the contemporaneous nature of the record is what makes it credible. The documentation built as the events happen, the requirements as they are defined, the alternatives as they are considered, the approvals as they are obtained, is contemporaneous and credible, while the documentation reconstructed after the fact is incomplete and suspect. The customer that builds the audit trail contemporaneously has a credible record. The customer that reconstructs it after the fact has a record that invites question.

The contemporaneous audit trail requires the discipline to document the process as it happens, capturing the decisions and the approvals in real time rather than at the end. The discipline costs little when it is built into the process and a great deal when it is skipped, because the reconstructed record is both more work and less credible than the contemporaneous one. The customer that builds the contemporaneous audit trail protects the decision with a credible record. The audit trail is the defence of the decision, and it must be built as the decision is made. See the order document negotiation article.

The structural response is to build the audit trail contemporaneously, capturing the decisions and approvals as they happen. The buyer that builds the contemporaneous trail has a credible record. See the contract review service and the quarter end tactics article.

The retention and the accessibility.

The retention and the accessibility of the documentation determine whether the records are available when they are needed, and the customer that keeps the records but cannot find them has not kept them at all. The Oracle relationship spans years, and the records, the contracts, the order documents, the entitlement record, the deployment data, and the decision record, must be retained and accessible across that span. The customer that retains the records in an organised and accessible form can produce them when the audit or the review comes. The customer that retains them in a fragmented or inaccessible form cannot.

The retention should be organised so the records are accessible to the people who need them, the procurement team, the license management function, and the advisors, when the need arises. The records that are scattered across individuals, systems, and formats are effectively lost, and the customer should consolidate the documentation into an organised and accessible repository. The retention and accessibility of the documentation are the final discipline, ensuring the records are available when they are needed. See the sourcing procurement pillar for the broader framework.

The structural response is to retain the documentation in an organised and accessible form, ensuring the records are available when needed. The buyer that retains accessible records can produce them when needed. See the audit documentation article and the ULA deal type page.

Records that defend the deal.

The Oracle procurement documentation standards protect the buyer on two fronts, the entitlement position in an audit and the decision in a review, and the customer that keeps disciplined records is protected on both. The entitlement record, the deployment data, the negotiation history, the contemporaneous audit trail, and the disciplined retention each contribute to the defence, and the customer that maintains them can demonstrate its compliance and its decision when the need arises. The Oracle purchase that cannot be documented cannot be defended. The Oracle purchase that is properly documented defends both the entitlement and the decision.

For the broader framework see the sourcing procurement pillar and the procurement compliance article.