Contracting for Digital Product Support
Looking for help developing contract language to incorporate Digital Product Support into your program? While still very much a work in progress, the military departments, materiel commands, and individual programs are blazing trails to assist programs in contracting for Digital Product Support, including for development of new (“born digital”) systems, modifications to legacy systems, and legacy system support. These resources, primarily in the form of “tailor-in” information, include statement of work (SOW) or performance work statement (PWS) language, contract data requirements lists (CDRLs) and data item descriptions (DIDs), and contract clauses. A few examples include:
- The Air Force’s Acquisition and Sustainment Data Package (ASDP)
- The Navy Data Acquisition Requirements Tool (NDART), one of three Model Based Product Support (MBPS) capabilities (Navy practitioners, please consult your command for info).
- The Army’s Optionally Manned Fighting Vehicle (OMFV) Request for Proposal (RFP)
- MIL-HDBK-539 Digital Engineering and Modeling Practices
- DAU Digital Product Support artifacts (CDRLs and DIDs) resources
For additional guidance on contracting for data with specific emphasis on Intellectual Property (IP) considerations, encourage you to view the recording (coming soon) of our recent Logistics LIVE “Contracting Data Rights” webinar, featuring Ms Vicki Allums and Colonel Christopher Monsey.
Lastly, your DAU teammates are currently developing two related defense acquisition credentials, CLCL 016 Digital Product Support Credential, and CLCL 018, Product Support Data Requirements Credential, to further assist practitioners in developing knowledge and skills to deliver affordable and effective systems for the Warfighter.