Oracle Contract Lifecycle Management for Public Sector (CLM) is a comprehensive solution for managing procurement processes that need to be performed by federal agencies. CLM features are available in OA Framework HTML pages. CLM supports FAR, DFARS, and other agency regulations that define the federal business processes, and encompasses a full procure-to-pay process flow within Oracle e-Business Suite which maximizes benefits to federal users. CLM enables contracting officers to drive operational excellence in federal procurement functions and enables the agencies to cut procurement costs dramatically. By providing the end-to-end business intelligence with a single source of data, CLM provides data transparency and visibility and provides contracting officers with support for strategic planning and improved decision making.
The following process flow depicts the procurement lifecycle in CLM:
Contract Lifecycle Management
The flow starts with the creation of a purchase requisition which is a document that represents a requirement or demand for supplies and services. This is associated to an acquisition plan that outlines the procurement plan on a larger scale. The purchase requisition is converted to a solicitation and the solicitation is sent out to vendors for obtaining their quotes/offers. When the offers are received from the vendors, the offers are evaluated and the contract is awarded to one of the vendors.
This process depicts all of the major procurement steps from purchase request initiation and commitment, through competitive solicitation with an offer evaluation phase, and ultimate award decision. The process is often not executed in its entirety – several steps are optional and at the discretion of the contracting officer depending on the procurement process. Some steps may be required by an agency in order to follow it's policies and regulations, but from a system's perspective, the steps can be executed without every procurement document in the chain.
You can create a configurable, intelligent numbering format for CLM documents that follow Federal Acquisition Regulations (FAR) and Defence Federal Acquisition Regulations (DFARs) processes. Based on your configuration and setup of the numbering structure, a document number is defaulted automatically on the CLM documents. You can modify the defaulted document number as long as the document is in draft mode. Lines for CLM documents are automatically numbered in accordance to line/ subline numbering conventions used in federal agencies. CLINs are automatically numbered with four-character strings (0001, 0002, and so on) which can be modified by the user, while SLINs append a two-character string (0001AA, 0001AB, 000101, 000102). The contracting professional can modify the system assigned line number.
Note: To set up the document numbering structure for use in purchasing documents, refer to the Oracle Contract Lifecycle Management for Public Sector Implementation Guide.
For more information about Document Numbering, refer to the appendix - Common CLM Functionality.
The Contract Line (CLIN) and Sub-line (SLIN) structure is used in all CLM documents, including modifications and amendments to the purchasing documents. A Contract Line captures information about the item(s) or service(s) to be procured in the contract with or without the pricing details. Thus, a Contract Line (CLIN) can be a priced line or an informational line. Similarly, sub-lines, which are used to capture additional information about the CLIN, can be priced sub-lines or informational sub-lines.
When a line is added to a CLM document, it is numbered automatically according to the line numbering setup that follows federal government regulations. This provides a flexible way to configure line numbering. In the CLM document, you can specify if the line should be priced or informational, as well as organize them into a complex line and sub-line structure, in accordance with federal regulations.
For more information on CLINs/SLINs, refer to the appendix - Common CLM Functionality.
Exhibit Lines (ELINs) are lines in a contract that are typically bulky (100s / 1000s) and are printed separately for ease of use. ELINs are like any other lines in a contract document. Exhibit Lines can be Contract Data Requirements Lists (CDRLs) or Non-CDRLs.
Contract Data Requirements Lists (CDRLs) are lines that have no cost or not separately priced, but are related to other contract lines. CDRLs need to be received, accepted and otherwise accounted for.
The actual exhibit information prints separately from the contract, similar to an attachment. Users have the ability to print each individual exhibit along with the corresponding exhibit lines in a PDF format. The Non-CDRL exhibit lines should print in a standard format similar to the way in which CLINs/SLINs appear on the contract continuation pages (Section B of UCF). CDRLs, however, need to be generated on the standard DD1423 form.
ELINs are similar to CLINs and SLINs in that they can be either Priced or Informational, can be multiple in a contract, can be funded, can be received, and can be matched and paid for. However, ELINs are different from CLINs and SLINs in that : ELINs must always have a parent line reference to a CLIN or a SLIN, they can have multiple parent lines, a CLIN can have multiple Exhibits (each Exhibit can have multiple lines).
CDRLs are similar to CLINs and SLINs in that they can be multiple in a contract, can refer to an Exhibit line and can be received. However, CDRLs are different from CLINs and SLINs in that: CDRLs must always have a parent line reference, they can have multiple parent lines, cannot be informational, cannot be funded, has additional information that is captured separately.
For more information on ELINs and CDRLs, refer to the appendix – Common CLM Functionality.
You can create an option line on a purchasing document that you intend to exercise as a regular line at a future point in time. Instead of modifying / amending the source document at a future date, enter the anticipated options that the base line is associated to. For example, a software purchase can be entered as a base line. This necessarily entails support and training as options for the purchase of a software package. Therefore support and training can be entered as option lines as the vendor has promised them. At a later date, the options of support and training can be exercised as regular purchase order lines because the vendor has now promised to deliver support and training. If it is not required to procure the optional support and training from the same vendor who supplies the software package, the option lines can be created without linking them to the software package line as the base line. The option lines of support and training, once exercised, can be received and invoiced as well.
This capability in CLM enables the contracting professional to mark lines as Option lines – lines which can be exercised later via a modification to the award if required. Option lines may or may not be associated with base lines and often involve follow-on work. Option lines behave similarly to CLINs/SLINs except they are not funded, cannot be received or invoiced until exercised after the awarding of the contract.
A priced CLIN or SLIN can be further defined as an Option Line. An Option Line stores and displays information that is used at a future point in time.
This diagram explains the flow of Option lines between different CLM users.
For more information on Options, refer to the appendix - Common CLM Functionality.
Using CLM, contracting professionals are able to price Awards, Orders, IDVs and Modifications by specifying federal Contract Types such as Firm Fixed Price, Cost plus Award Fee, Time & Materials, Cost Sharing, and so on. The Contract Types form the basis for determining the price payable to a vendor. Prices are manually entered by the user or are defaulted on the purchasing document line depending on the item/supplies/service setup. The final price calculation depends on a number of factors: Contract Type, Cost Constraint, price of the item/service.
The CLIN or SLIN can be a Priced or Informational line. For pricing calculations to take place, the line should be defined as a Priced Line, and not an Informational Line.
Lines can be Quantity Based or Amount Based. A Quantity Based Line Type enables you to enter information for goods/supplies. An Amount Based Line Type enables you to enter pricing information about services. Select a value from the Type LOV in the Lines region (for each row) to use a Quantity Based or an Amount Based Line. Different Contract Types display depending on the line type you select.
The Contract Type is available on the lines of a Purchase Requisition, an Award, IDV or a Solicitation. The Contract Type may be changed by the user depending on business requirements.
The IDC Type field displays for Solicitation documents and IDVs on the line details page.
For more information on Pricing, refer to the appendix - Common CLM Functionality.
Oracle CLM provides you the ability to amend a solicitation to cater to supplier comments or questions during the competitive period where the procurement office may issue an amendment to clarify certain requirements, or terms and conditions, within the solicitation document, or update the items or services to be purchased, and so on. You can change the submission date or due date for proposals, and in some instances, you might want to modify the requirements themselves through issuance of a Solicitation Amendment.
You can create solicitation amendments in CLM and maintain them as individual documents, while maintaining the original solicitation. The application automatically displays all the fields you entered in the original solicitation and enables you to edit them per your requirements. You can create the solicitation amendment any time after the solicitation approval and publication, and also after the solicitation is closed for bidding. Additionally, when a new round is approved, published, or closed, you can create a solicitation amendment.
The solicitation amendment goes through its own approval workflow, similar to the original solicitation. The collaboration team from the original solicitation is automatically included in the amendment document. However, you can update the list to add or remove members, as required.
Once you have completed amending your document, you can generate a description with the details of the amendment, which include the previous value, current value and the difference (if the value is a number or a date such as Price, Quantity or Option From Date, Option To Date).
You can print the description of changes in the SF30, the previous value, current value and the difference is also printed in the SF30 form.
Once approved, you must conform the amendment to merge the changes in the amendment with the original document and publish the new solicitation document. The application maintains the original and amended documents separately. Note that the conformed document retains the original document number.
You can also cancel solicitations via an amendment. The application designates the solicitation as cancelled and you cannot award the solicitation. You must send a cancellation amendment for approval, and the approval process is similar as for an amendment. When you conform the cancellation amendment, the process ensures that the original document is marked as cancelled, all suppliers are notified of the cancellation, and all existing offers from suppliers are invalidated.