General CLS Model Concept_Oct 2024.pdf
PDF 208 KB Posted
- Attached to
- DoD Clause Logic Service
- Solicitation number
- FY2025DPCAP0001
- Issued by
-
Office of the Secretary of Defense
About this file
This document is a general concept description for a Clause Logic Service (CLS) that would provide extensible markup language (XML) data outputs for Terms and Conditions inclusion in solicitations, awards, and modifications for the Department of Defense and other federal agencies. The key details are:
The CLS would be a modular software capability that integrates with cloud-hosted contract writing systems and leverages authoritative data sources like Acquisition.gov to provide clause data. It would include a clause repository, instance document records, a business rules engine, and a user interface. The solution must support multiple configurations, including stand-alone, "headless" APIs, and classified environments.
The government is conducting market research to inform its strategy for modernizing or replacing the existing CLS capability. Respondents must demonstrate expertise in DoD procurement processes, business system design, data standards, cloud integration, accessibility requirements, and clause logic capabilities. The government plans to hold an industry day on December 9, 2024 and is seeking responses to this sources sought notice by November 29, 2024. No acquisition strategy or set-aside determination has been made at this time.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CLS Industry Day - Interested Vendors (December 9 2024).xlsx | XLSX spreadsheet | |
| Clause Logic Service Industry Day 12-9-24.pptx | PPTX presentation |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
General CLS Model Concept October 2024
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
Solicitation Module
1 Authoritative Content Data Source
• For FAR-based contracts, acquisition.gov will be the sole content provider regardless of regulation/supplement
• Acquisition.gov will provide XML or XHTML files via web API
• Intent is to have Acquisition.gov provide data without need for transformations, but likely need CLS to have capability to provide transformations to fit with PDS
• In disconnected environment, Acquisition.gov’s GitHub will allow for XHTML files to be downloaded for import into disconnected CLS
Focus right now is acquisition.gov and FAR-based contracts on NIPRNet, but leave room for extensibility to other instrument types and sources
• For grants/cooperative agreements, the data source is TBD (grants.gov?)
• For OTs, the data source is CWSs contributing to the clause repository if they wish to publish
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
2 Stock Clause Repository
• Clauses fed from authoritative sources must be stored within the clause repository for 100 years
• Clause in this repository must be uniquely identified (a FAR-based clause number is not unique identification)
• Clauses in this repository have all data and metadata necessary to trace their origin and capture contents to be used within CWSs via XML output
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
3 Instance Document Records
• Instance document records include several elements:
• Unique identification for documents
• Clause lists for an instance document (such as a particular solicitation, award, or modification)
• Fill-in content and tailored content
• Q&A responses
• PDS XML (as applicable)
• ADS XML (as applicable)
• Need to Know Metadata
Restrictions
• Relationships to other documents
• Document history log
• Saved and retrievable states for all types of related records
• Think of Git Hub: Need commits, branches, etc.
• Signed, 508-compliant XML output for CWS consumption
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
4 Business Rules Engine
• Business rules engine is separated from clause repository and instance document records to allow for modularity and efficient business rule maintenance
• Given certain inputs for an instance document, business rules engine applies pre-defined logic to return clause list for a given instance document
• Business rules engine needs to capture an audit trail of rules applied to inputs to produce outputs
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
5 App UI
• Application provides 508-compliant user interface to access instance document records – main use function is for non-modern CWSs, although modern CWS users may also use CLS
• App uses PIEE’s SSO and functions within the PIEE suite using same hierarchy and RBSA
• App is not necessary to operate other components of CLS; other components may work using web APIs
• App must handle RBSA when used
• App also must be self-contained for use within disconnected environment?
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
6 Modern CWSs
• Modern CWSs have two-way interaction with CLS for multiple operations:
• Document initialization
• PDS/ADS feeds
• Q&A API
• CLS clause XML retrieval
• Updates to documents throughout creation process… expect many drafts, retrievals from different saved states, etc.
• CLS should maximize reuse of data from Modern CWSs and other authoritative sources
• Modern CWSs handle single use (such as H) clauses not in a regulation/supplement
• Modern CWSs have a “handshake” with CLS to ensure only signed CLS output is accepted for input into the CWS
• Modern CWSs may supply fill-in values and tailored content, but CLS must be in sync with provided values with handshake
• Modern CWSs map line item clauses to line items/groups
• Modern CWSs perform PDS (ADS) preval/val/and conformance check
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
7 Industry Systems
• Industry partners responding to solicitations to provide fill-in content, requests to add/strike/tailor clauses must have access to same XHTML version of clauses as the DoD
• Industry must be able to make requests to CLS via the solicitation module to accomplish these ends
CLS
App UI
Acquisition.gov
Business Rules
Engine
Content Feed/Extract for Disconnected
DoD Contract Writing Systems
PIEE
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
Industry Systems
Solving for Classified/ Disconnected State
• DoD’s disconnected environment’s need to have access to a Clause Logic Service that allows them to retrieve and import a clause set for a solicitation/ award.
• CLS must:
• Provide a UI solution for determining the correct clauses
• Provide a means to transmit the clause data into the disconnected solution.
CLS
App UI
Acquisition.gov
Business Rules
Engine
Extract for Disconnected
Disconnected DoD Contract
Writing Systems
Grants.gov?
Clause Repository
Instance Document
Records
PDS/ADS/Q&A
in, Signed CLS XML out
| General CLS Model Concept |
| Slide Number 2 |
| Slide Number 3 |
| Slide Number 4 |
| Slide Number 5 |
| Slide Number 6 |
| Slide Number 7 |
| Slide Number 8 |
| Slide Number 9 |
| Slide Number 10 |
File details come from the government source that posted it. Updated .