Attachment 7 DD Form 1423 _Contract Data Requirements List_ signed.pdf

PDF 1 MB Posted Nov 6, 2026

Attached to: STANDARD LABOR DATA COLLECTION AND DISTRIBUTION APPLICATION (SLDCADA) REQUEST FOR PROPOSAL
Solicitation number: N0003926R0005
Issued by: Department of the Navy Information Warfare Systems Command

About this file

Written by GovTribe AI · Nov 6, 2026

This is a Contract Data Requirements List (DD Form 1423) dated February 2024 for the SLDCADA (Sea-Lift Deployment Cargo and Data Application) system under PMW 220 Navy ERP. The document specifies 26 mandatory data items and deliverables required throughout the contract performance period across all contract line items for base and option periods.

Key deliverables include monthly contractor progress and status reports (A001, A002), monthly financial reports (A003, A004), and comprehensive management and planning documents due 45-60 days after award, including a Program Management Plan (A005), Systems Engineering Management Plan (A006), Production Support Plan (A007), Risk Management Plan (A008), Quality Assurance Plan (A009), Configuration Management Plan (A00A), Cyber Security Plan (A00B), and DOD Risk Management Framework/C&A Package (A00C). Additional required deliverables encompass Customer Support Plan (A00D), training materials (A00E), integrated master schedule (A00F), data management plan (A00G), system account management plan (A00H), technical data packages (A00J), after-action reports (A00K), transition phase-in and phase-out plans (A00L, A00M), contract kick-off meeting minutes (A00N), government-owned assets inventory (A00P), annual customer satisfaction survey results (A00Q), master test plan (A00R), meeting minutes records (A00S), contingency plan (S001), and Cyber Security Workforce Report (A00T). Most management plans require annual updates by the 30th of each month following initial submission. All data submissions must be delivered with unlimited rights in Microsoft Office format to PMW 220 POC, with distribution restricted to Department of War and U.S. DoW contractors only under Distribution Statement D.

View the file

Other files

File	Type	Posted
Attachment 1 Performance Work Statement.pdf	PDF	Nov 6, 2026
Solicitation - N0003926R0005.pdf	PDF	Nov 6, 2026
Attachment 2 Section L_SLDCADA.pdf	PDF	Nov 6, 2026
Attachment 06 C-211-HQ001 Personnel Qualifications Minimum Requirements.pdf	PDF	Nov 6, 2026
SLDCADA Response to FOPR Questions.xlsx	XLSX spreadsheet	Nov 6, 2026
Attachment 3 Section M_SLDCADA.pdf	PDF	Nov 6, 2026
Attachment 4 SLDCADA QASP.pdf	PDF	Nov 6, 2026
Attachment 05 L4 Price Workbook.xlsx	XLSX spreadsheet	Nov 6, 2026

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

PREVIOUS EDITION MAY BE USED.

DD FORM 1423, FEB 2024 Page 1 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

CONTRACTOR'S PROGRESS AND STATUS REPORT

3. SUBTITLE

SLDCADA MONTHLY STATUS REPORT

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81928

5. CONTRACT REFERENCE

PWS PARA 5.1.1, 5.1.1.2, 5.1.1.5, 5.1.3.2, 5.1.5.3

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

11. AS OF DATE

TO AWARD

12. DATE OF FIRST SUBMISSION

45 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

15TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK A: Associated with ALL CLINs for Base and Option Periods

DESCRIPTION:

Monthly Status Report must contain:

Monthly highlights and milestones achieved.

Accomplishments by POR Sustainment PWS Area (Program Management, Release Management, IT Infrastructure Management and Support, Customer Support, Data and Interface Management Support), schedule status, problems/risks/ issues identified and mitigation/resolution actions with status, and planned key efforts planned for the next three months.

Status of deliverables.

Metrics Reporting IAW paragraph 5.1.1.2 - For all metrics, the contractor will also track and report the trend over time with analysis of the trend to include possible causes and recommended corrective action(s) as necessary.

Security Report: Detail all security events related to the facility or equipment which occurred during the reporting period.

Cyber Security Report IAW paragraph 5.1.3.2 - The report must include a report of any CS incidents, and a status of existing plans in execution, penetration, backup, and COOP statuses for review.

Data submissions provided under this CDRL are to be delivered with Unlimited Rights as detailed under DRARS 252.227-7013-Rights in Technical data--Noncommercial Items (FEB 2014) of the Contract/Task Order.

BLOCK 9: Distribution Statement D: Distribution authorized to the Department of War and U.S. DoW contractors only (fill in reason) (date). Other requests for this document shall be referred to (insert controlling DoW office).

COR 0 1 1

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 1

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

C. Bradley

H. SIGNATURE I. APPROVED BY J. SIGNATURE

DD FORM 1423, FEB 2024 Page 2 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

CONTRACTOR'S PROGRESS AND STATUS REPORT

3. SUBTITLE

MONTHLY STATUS REPORT (MSR)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81928

5. CONTRACT REFERENCE

PWS PARA 2.1.2, 2.8.1, 2.9.1, 11.0, 11.3.1

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

SEE BLK 16

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

30DAAWD

13. DATE OF SUBSEQUENT

SUBMISSION

SEE BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK 4: Monthly Status Report (MSR) shall be in accordance with DI-MGMT-81928 requirements except or, as modified or defined by the following instructions:

MSR consists of two(2) parts. Part one (1) shall be provided in Excel format in accordance with Attachment 1 of this CDRL. Part two (2) shall be provided in Word format and consist of a narrative addressing, at a minimum:

A. Performance Status: Identify significant accomplishments and progress made during the affected reporting period by Performance Work Statement (PWS) paragraph. Identify significant challenges or risks encountered that impact the successful delivery of required services.

B. Schedule Status: Identify schedule for and status of all deliverables. If the efforts are not on schedule, indicate the reason for the delay and provide a revised completion/delivery date.

C. Financial Status: In addition to the DID reporting requirements, identify any travel accomplished with sufficient detail to support costs and provide a detailed description of the ODCS authorized at time of award and ODCS incurred to date.

This description does not waive the requirement for formal limitation of funds/cost notifications, when warranted.

D. Staffing: Any/all subcontractor data must be included and integrated into the MSR. Identify by employee code, labor category, fully burdened labor rate.

BLOCK 8: Approval will be for technical content. Deliverables shall provide comprehensive coverage of the required content, be free of spelling and grammatical errors. The Government will have ten (10) business days to review and provide comments back. The Contractor shall have five (5) business days after receipt of comments to make corrections and return to Government. No Government response to Report within 10 days of submission constitutes approval.

BLOCK 9: Distribution Statement C: Distribution authorized to U.S. Government agencies and their contractors for Administrative and Operational Use, 22 February 2021. Other requests for this document shall be referred to PMW 220, Washington Navy Yard, DC.

BLOCK 12: The MSR initial submission shall be NLT 30 calendar days after Task Order Award.

BLOCK 13: Subsequent submissions shall be NLT 10 days after the end of the prior month.

BLOCK 14: Media/Data Submission shall be posted to a designated government portal and/or via electronic E-mail as directed by the COR. Format shall be compatible to MICROSOFT OFFICE VERSION 2010/2016.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

TBD 0 1 0

15.TOTAL 0 4 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 3 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A003

2. TITLE OF DATA ITEM

CONTRACT FUNDS STATUS REPORT (CFSR)

3. SUBTITLE

SLDCADA FINANCIAL & CONTRACT MGT RPTS

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81468

5. CONTRACT REFERENCE

PWS PARA 5.1.1, 5.1.1.1, 6.3

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

11. AS OF DATE

CONTRACT AWARD

12. DATE OF FIRST SUBMISSION

45 DACA

13. DATE OF SUBSEQUENT

SUBMISSION

15TH OF EACH MONTH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK A: Associated with ALL CLINs for Base and Option Periods.

DESCRIPTION:

Submit a Task Order Level Monthly Expenditure Report that provided financial summary information to include planned budget and actual execution of funds by personnel, hours, cost, and by Contract Line Item Number (CLIN).

For CPFF CLINs (CDRL A002):

Cost Summary including funds expended based on efforts during the reporting period by funded CLIN, Project, PWS functional area and employee charged (hours and cost).

Cost Summary and a summary of work completed during the reporting period based on efforts by functional area to the 5.x.x.x level of the PWS by funded Contract Line Item Number (CLIN).

Cost Summary reporting: CLIN Ceiling, funded amount, Total funds expended, Average Weekly Spend Rate, and Estimate at Completion (EAC) of the current task order Period of Performance (PoP).

The Monthly Reports will also indicate when CLIN or Project will be 75% expended in accordance with FAR 52.232-20 Limitation of Cost, or FAR 52.232-22 Limitation of Funds, as applicable.

The Contractor shall furnish performance metrics as defined in its Quality Assurance Plan.

Data submissions provided under this CDRL are to be delivered with Unlimited Rights as detailed under DFARS 252.227-7013-Rights in Technical Data--Noncommercial Items (FEB 2014) of the Contract/Task Order.

BLOCK 4: Description:

Financial and Contract Management Report will include:

1. Budget and Cost Report to include Cost Summary including funds depletion estimates based on efforts for the order period allocated CLINs, Project and PWS functional areas.

2. Monthly amount invoiced and Projections for Monthly Invoicing for next 3 months

3. Contractor Onboards/Offboards (as applicable -- Key Personnel in particular)

4. Report will indicate when CLINs will be at 75% expended in accordance with FAR 52.232-20 Limitation of Cost, or FAR 52.232-22 Limitation of Funds as applicable.

BLOCK 14: Electronically delivered-reproducible Microsoft Office format per the current NMCI Gold Disk (unless otherwise approved by the Government) to the PMW 220 POC.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 4 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER FNCL

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A004

2. TITLE OF DATA ITEM

FUNDS & LABOR HOUR EXPENDENTURE REPORT

3. SUBTITLE

SLDCADA MONTHLY INVOICE

4. AUTHORITY (Data Acquisition Document No.)

DI-FNCL-81537

5. CONTRACT REFERENCE

PWS PARA 5.1.1.1

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

11. AS OF DATE

CONTRACT AWARD

12. DATE OF FIRST SUBMISSION

45 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

15TH OF EACH MONTH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Provide on a monthly basis a physical copy of the monthly invoice submitted via Wide Area Workflow (WAWF)/ Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) to the Government Contracting Officer's Representative

(COR).

Monthly Invoice will include:

1. Copy of Monthly Invoice submitted via WAWF to Government

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 5 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A005

2. TITLE OF DATA ITEM

PROGRAM MANAGEMENT PLAN

3. SUBTITLE

SLDCADA PROGRAM MANAGEMENT PLAN

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81797

5. CONTRACT REFERENCE

PWS PARA 5.1.1, 5.1.1.4, 8.3

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

TASK AWARD

12. DATE OF FIRST SUBMISSION

45 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

The SLDCADA Program Management Plan shall identify all contractor resources; i.e., equipment, material, supplies, and staffing plan on how these resources will enable the contractor to meet performance objectives. The plan must also include the contractors specific approach to each of the following items, also listed under section 5.1.1 of the PWS:

Project Integration Project Scope Management Project Time Management Decision Analysis and Resolution Incident Management Records Management Project Monitoring and Controlling Stakeholder Management Quality Management Communication Management Project Cost Management Casual Analysis and Resolution Risk Management Process Improvement

The plan must include continuity of operations (Remote Work) plan in the event of base shut down, closure, or extended remote work, to include collaboration tools used and stakeholder communication plans. The Contractor shall provide a Standard Operating Procedure (SOP) for all security activities, including the separation of personnel, in accordance with Department of Navy regulations; the plan must ensure communication to all personnel to ensure they are aware of and familiar with the SOP.

Data submissions provided under this CDRL are to be delivered with Unlimited Rights as detailed under DFARS 252.227-7013-Rights in Technical data--Noncommercial Items (FEB 2014) of the Contract/Task Order.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 6 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A006

2. TITLE OF DATA ITEM

SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP)

3. SUBTITLE

SLDCADA SYS ENGINEERING MGT PLAN (SEMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-81785A

5. CONTRACT REFERENCE

PWS PARA 5.1.2.2

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

TO AWARD

12. DATE OF FIRST SUBMISSION

45 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Systems Engineering Plan will address the overall systems engineering approach, processes and procedures for the sustainment of the SLDCADA System incorporating best practices from ITIL Service Management and CMMI and adhering to Government/Navy regulations and standards. The SEMP will address all software engineering activities including, but not limited to, requirements definition, technical specification development, design, coding, tuning, testing, cyber security, installation, implementation, maintenance, and documentation of all software for the SLDCADA system and SLDCADA support systems.

It will include structured project management techniques including planning, quality assurance, and risk management with disciplined processes and metrics for the System Development Lifecycle of SLDCADA.

The SEMP will also address the following:

The conduct of any SE Technical Review events for SLDCADA system development lifecycle per DoD 5000 regulations (SRR, PDR, CDR, TRR, PRR, etc) if required.

Interface Management processes and procedures, metrics and reporting including the development and/or maintenance of Interface Control Agreements (ICAs), Data Exchange Agreements, Interface Requirements Specifications (IRSs) and Interface Design Descriptions (IDDs).

Software Engineering processes and procedures, metrics and reporting.

Release Management processes and procedures, metrics and reporting.

Shall reference and discuss Configuration Management Plan, Risk Management Plan, Production Support Plan, Quality Assurance Plan, Cyber Security Support Plan.

the performance of code reviews to promote code quality and consistency; and reference all code libraries, Configuration items, TEMP, and tools utilized, reporting and metrics. Developed code base should be easily maintainable.

Include a standardized estimation model to estimate labor hours and cost for each SCR submitted.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 7 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A007

2. TITLE OF DATA ITEM

PRODUCTION STATUS REPORT

3. SUBTITLE

SLDCADA PRODUCTION SUPPORT PLAN (PSP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81255

5. CONTRACT REFERENCE

PWS PARA 5.1.3, 5.1.3.1

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

TASK AWARD

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

A comprehensive Production Support Plan for the SLDCADA solution environments of Development, Test, Production, High Availability and Disaster Recovery environments located within the AWS-GOV Cloud West region provided by the Government (currently 36 total servers) including schedule, cost, and dependencies.

1. The Production Support Plan will present the processes and procedures, roles and responsibilities, and reporting and metrics to maintain the full suite of the SLDCADA computing environments; it will address all activities required to maintain and support the SLDCADA Development, Test, Production, High Availability and Disaster Recovery systems, including but not limited to, System Maintenance and Security procedures; Hardware and software refresh or upgrades;

and Operational support procedures.

All activities reviewed and approved by the Government will be included in the SLDCADA integrated Master Schedule for execution and statusing (CDRL A00F).

2. System Monitoring plan of Production, Dev and Test Environments to provide real time feedback on system resource levels, availability, response times, connectivity. This should include metrics and alerts to be employed when system performance or availability falls out of tolerance. Standards for tolerances to be submitted to the Government for approval upon baselined performance data under optimal conditions. this should include the system performance metrics defined in PWS Section 5.1.1.2 Reporting and Metrics and the SLDCADA QASP.

3. Batch Program Guide including the processes and procedures for performing the weekly Batch Processing required as part of SLDCADA Sustainment and identifying any coordinating activities/dependencies. This should include the batch performance metrics defined in PWS Section 5.1.1.2 and the SLDCADA QASP.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 8 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A008

2. TITLE OF DATA ITEM

CONTRACTOR'S RISK MANAGEMENT PLAN

3. SUBTITLE

SLDCADA RISK MANAGEMENT PLAN (RMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81808

5. CONTRACT REFERENCE

PWS PARA 5.1.1.6

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

A comprehensive SLDCADA Risk Management Plan incorporating best practices from the Program Management Body of Knowledge (PMBOK) and defining the processes, roles & responsibilities, reporting, and metrics that will be followed for performing risk management on all tasks performed under this contract. It will include:

1. Procedures and processes governing the identification, capture, assessment, communication/reporting, mitigation, and tracking of risks identified in sustainment of the SLDCADA system.

2. The risk reporting including status of mitigations to be included in the SLDCADA Monthly Status Report (CDRL A001).

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 9 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER QCIC

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A009

2. TITLE OF DATA ITEM

QUALITY ASSURANCE PROGRAM PLAN (QAP)

3. SUBTITLE

SLDCADA QUALITY ASSURANCE PLAN (QAP)

4. AUTHORITY (Data Acquisition Document No.)

DI-QCIC-81794

5. CONTRACT REFERENCE

PWS PARA 5.1.6.1, 5.1.6.2

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

20 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Establish a Quality Assurance Plan to include a Quality System Manual that includes:

1. A comprehensive QA plan including procedures and processes governing software development, testing, IT infrastructure support activities in alignment with the Government QASP. QA Plan should ensure the products or services conform to the specified contract technical requirements as defined in the PWS, and provide and maintain an internal quality control inspection system acceptable to the Government covering the services from recurring. Contractor shall develop quality control procedures that address the areas identified in the AQLs identified in the Government issued

QASP.

2. An established Quality Management System for the contractor team along with Manual/Handbook and/or associated SOPs with contractor training.

3. Procedures and processes, roles and responsibilities based on best practices (ISO 9001 standards and ITIL Service Management framework).

4. The associated metrics and reporting back through established status reporting mechanisms for SLDCADA.

5. A procedure to address CDRL development and delivery to the Government.

6. A procedure for elevation QA issues or risks to Program Management.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 10 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00A

2. TITLE OF DATA ITEM

SUPPLIER'S CONFIGURATION MANAGEMENT PLAN

3. SUBTITLE

SLDCADA CONFIGURATION MGT PLAN (CMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80858C

5. CONTRACT REFERENCE

PWS PARA 5.1.1.7

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

The Configuration Management (CM) Plan will include procedures for performing CM across the SLDCADA program including equipment, software, processes, system functionality, and data across all environments. It should incorporate best practices from CMMI and ITIL Service Management framework for Change Management in accordance with Government regulations and specifications utilizing CM tools. All configuration items must be fully documented and saved in approved CM Tool/repository. This repository will be used for configuration, transport, and release control, and will provide ad hoc reports as needed to support user and management needs. Serena PVCS is the current Government tool provided for the CM Repository. The CM Plan should ensure requirements traceability for all configuration changes.

The CM Plan must address at a minimum:

1. Request for Change Standard Operating Procedure - includes process and tools and any reporting metrics for end user commands and others to petition for Requests for Change to the SLDCADA system (software, hardware).

2. Procedures for System Improvement Requests (SIR) and associated reporting - includes process and tools and any reporting metrics for any system improvements. Contractor must investigate and provide solutions as these changes/ requests for improvements become known.

3. Guidelines, procedures, and schedules for conducting periodic and event driven CM audits. Conduct audits and follow-on discrepancy resolution. Maintain audit documentation and records of Corrective Actions taken.

4. How the Contractor will monitor configuration status of external systems that maintain interfaces with SLDCADA in order to identify changes that may impact SLDCADA interfaces.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 11 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00B

2. TITLE OF DATA ITEM

CYBERSECURITY VULNERABLITY REPORT

3. SUBTITLE

SLDCADA CYBER SECURITY PLAN (CSP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-82191

5. CONTRACT REFERENCE

PWS PARA 5.1.3.2

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

SLDCADA Cyber Security (CS) Plan will address all of the necessary Cyber Security tasks, including system maintenance, Information Assurance Vulnerability Alert (IAVA) upgrades, Security Technical Implementation Guides (STIG) applications, database scans, testing and accreditation processes. It will include:

1. A comprehensive Cyber Security Plan detailing specific CS tasking for sustainment of all environments of SLDCADA (Production and Non Production) under the RMF Framework in order to successfully maintain annual accreditation cycle, including the development in coordination with SSC LANT and delivery of the C&A Package (CDRL A00C).

2. The reporting and metrics to be provided to the Government; the monthly CS report addressing all outstanding CS requirements (including documentation) with plans to accomplish requirements prior to Navy mandated deadlines. The report must include a report of any CS incidents, and a status of existing plans in execution, penetration, backup, and COOP statuses for review. This report will be included in the Monthly Status Report (CDRL A001).

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 12 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00C

2. TITLE OF DATA ITEM

DOD RISK MGMT FRAMEWORK (RMF) PKG DELIVERABLES

3. SUBTITLE

SLDCADA C&A PKG, RMF SBMT FOR ANNL ACCRD

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-82001

5. CONTRACT REFERENCE

PWS PARA 5.2.1.1, 5.2.3, 5.2.4

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

ASREQ

13. DATE OF SUBSEQUENT

SUBMISSION

ASREQ

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

In accordance with RMF Guidelines and procedures, DoW and DON policies and regulations, the contractor will support the development and submission of the SLDCADA Certification & Accreditation (C&A) package set of system documentation and data will be developed in coordination with NIWC LANT and delivered in support of the annual RMF accreditation cycle.

IAW PWS paragraph 5.2.1.1 and 5.2.4: Ensure that all RMF tasks are completed successfully in order to obtain an acceptable Authorization to Operate (ATO) for all SLDCADA solution environments.

IAW PWS paragraph 5.2.3: Ensure that all RMF tasks are completed successfully in order to renew the Authorization to Operate (ATO) for all SLDCADA solution environments.

BLOCK 14. Electronically delivered-reproducible Microsoft Office format per the current NMCI Gold Disk (unless otherwise approved by the Government) to the PMW 220 POC.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 13 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00D

2. TITLE OF DATA ITEM

MANAGEMENT PLAN

3. SUBTITLE

SLDCADA CUSTOMER SUPPORT PLAN (CUSP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80004A

5. CONTRACT REFERENCE

PWS PARA 5.1.5.1

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

AT AWARD

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Provide a comprehensive customer support plan that includes:

1. The plan to provide customer support for all aspects of SLDCADA application including Help Desk Support for accessibility, technical problems, system performance and connectivity issues, user training and end of year processing;

batch scheduling and processing, support for external interfaces; new site requests and stand up; site specific configurations and requests; organizational decentralizations/reorganizations (requiring backend database updates, bulk loading of site data, DCPS requests); migration including data to new time and attendance systems, and other special assistance. This plan must address all specific tasks for customer support including user training, training materials and materials maintenance, help desk support, processes to address incidents, tracking and prioritization of help desk tickets (support requests), processes to address requests for additional functionality or changes, and must set out how the contractor plans to achieve all performance objectives in this section.

2. The conduct of semi annual User Focus Groups/Configuration Control Boards (CCBs) to review customer requested changes and prioritization, user satisfaction or issues; and communicate upcoming release changes and/or planned system outages. Decisions made and meeting minutes are to be produced and delivered to the Government as a work product and recorded and maintained per Configuration Management Plan (CMP) (CDRL A009).

3. The conduct of end user satisfaction surveys at a minimum annually (see CDRL A00Q) to confirm requirements met following upgrades in software release and/or help desk tickets were resolved satisfactorily. It is expected that end users will be involved in the gathering of requirements, prioritizing of development, and software development with sufficient customer input throughout the entire development process to provide excellent customer satisfaction upon delivery.

4. Define Help Desk Support construct, processes, and procedures for the end user support of the SLDCADA System.

5. Define End User Training development, delivery, and maintenance processes and procedures for end user training in the SLDCADA System.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 14 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER ILSS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00E

2. TITLE OF DATA ITEM

TRAINING MATERIALS

3. SUBTITLE

SLDCADA TRNG GUIDES & CMPTR TRNG (CBT)

4. AUTHORITY (Data Acquisition Document No.)

DI-ILSS-80872

5. CONTRACT REFERENCE

PWS PARA 5.1.5.4

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ASREQ See Block 16)

11. AS OF DATE

ASREQ

12. DATE OF FIRST SUBMISSION

ASREQ

13. DATE OF SUBSEQUENT

SUBMISSION

ASREQ

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

The contractor shall develop and maintain the supporting training material in support of the SLDCADA users including administrative and end users. This includes:

1. SLDCADA online self-service WBT courses, FAQs, and job aids to support SLDCADA Supervisory end users on how to fully utilize the SLDCADA system capabilities to support their Time & Attendance business and reporting needs, and approval processing.

2. Provide online self-service web-based training (WBT) courses, frequently asked questions (FAQs), and job aids to support SLDCADA end users on how to fully utilize the SLDCADA system capabilities to support their Time & Attendance business needs.

BLOCK 10: Updates are required if new functionality is introduced, functionality is significantly modified/removed, or software/system update has changed the user interface to SLDCADA.

COR 0 1 0

TPOC 0 1 0

15.TOTAL 0 2 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 15 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER TMSS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00F

2. TITLE OF DATA ITEM

TECHNICAL MANUAL SCHEDULE AND STATUS REPORT

3. SUBTITLE

SLDCADA INTEGRATED MASTER SCHEDULE (IMS)

4. AUTHORITY (Data Acquisition Document No.)

DI-TMSS-81812

5. CONTRACT REFERENCE

PWS PARA 5.1.1, 5.1.3.1, AND SECTION 5.2

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

11. AS OF DATE

AWARD

12. DATE OF FIRST SUBMISSION

30 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

15TH OF EACH MONTH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

SLDCADA Integrated Master Schedule: the format of the schedule will be Microsoft Project and must include resources, cost, dependencies, and other content for each task, as specified within the PMW 220 Integrated Program Management Guidelines.

1. Submit an Integrated Master Schedule, defining the timeline in which required deliverables and all sustainment efforts will be completed.

2. Schedule shall include milestones, responsible parties, dependencies, durations, and any predecessor/successor relationships defined.

3. Will be statused for process and any issues/risks to schedule will be identified per the Program Management Plan (CDRL A005) to the Government along with actions for mitigation or resolution in the SLDCADA Monthly Status Report

(CDRL A001).

4. Will be used to report progress and any issues at the SLDCADA Weekly Status Meeting.

5. It will include the schedule for prioritized, approved infrastructure management activities.

6.It will include all the schedule for all planned maintenance and Cyber Test and Evaluation for all SLDCADA solution environments, and all recurring activities such as software upgrades and cyber security requirements.

7. If required, it will include the schedule of activities required to migrate SLDCADA to an alternate data center.

8. The schedule will include all Risk Management Framework activities required to obtain an approved ATO and renew an existing ATO.

9. The schedule will include all activities required to implement SLDCADA for a New User community.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 16 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00G

2. TITLE OF DATA ITEM

CONTRACTOR'S DATA MANAGEMENT PLAN (CDMP)

3. SUBTITLE

SLDCADA DATA MANAGEMENT PLAN (DMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-82228

5. CONTRACT REFERENCE

PWS PARA 5.1.4.1

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

SLDCADA Data Management Plan will include:

1. Comprehensive plan to support the stewardship and maintenance of all master data and records maintained in the SLDCADA application.

2. Address master date governance and business rule documentation

3. Address any considerations for PII information handling

4. Address data archiving and data retention policies

5. Address data quality metrics and program

6. Include metrics and reporting around data management

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 17 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00H

2. TITLE OF DATA ITEM

MANAGEMENT PLAN

3. SUBTITLE

SLDCADA SYSTEM ACCOUNT MGT PLAN (SAMP)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-80004A

5. CONTRACT REFERENCE

PWS PARA 5.1.3.3

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ANNLY

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

60 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

30TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Provide a comprehensive plan and reporting structure to ensure consistent configuration, provision, and review of SLDCADA user accounts to ensure they are managed in accordance with Navy and DoW policy, ensuring only personnel with a current need to know are granted to the system.

SLDCADA System Account Management Plan will identify processes, procedures, roles, responsibilities, and metrics (Account Creation, Account Removal, Automatic Account Lock, Removal of Unnecessary Account, User Termination) and reporting to be followed.

It will:

1. Describe how the contractor will perform all actions required to approve, grant and monitor proper access for all personnel for which SLDCADA has responsibility for creating such access.

2. Describe how the contract will ensure access to all systems is given at access levels that provide the minimum necessary authority on all systems.

3. Describe how the contractor will address all FIAR and FISCAM user access and separation of duties oversight and monitoring efforts.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 18 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00J

2. TITLE OF DATA ITEM

TECHNICAL DATA PACKAGE

3. SUBTITLE

SLDCADA SW TECHNICAL DATA PACKAGE (TDP)

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-80886A

5. CONTRACT REFERENCE

PWS PARA 5.1.2.4, 5.1.3.4

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

SEMIA

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

6 MONTHS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

15TH

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

BLOCK 8: Document and deliver a Technical Data Package (TDP) for each semi-annual software release, to include software requirements, functional specifications, technical specifications, test plans, and test evidence. The Government shall receive unlimited rights for all system documentation. Documents shall be saved in the Government provided repository, which is currently Serena PVCS. These documents and the required updates comply with Configuration Management processes.

DESCRIPTION:

In alignment with the Systems Engineering Management Plan (SEMP) (CDRL A006), and the Configuration Management Plan (CMP) (CDRL A00A), the Technical Data Package (TDP) for each software/code developed as part of the release will include:

1. Software Requirements Specifications documented.

2. Software Design Description Document outlining functional and technical specifications to meet the requirements.

3. All design reviews conducted to include PDR and CDR.

4. Software Test Plan defining tests conducted to ensure code functioned properly and met the requirement, and any regression testing performed.

5. Test Readiness Review (TRR) Report.

6. Software Installation Plan (SIP) Document.

7. Production Readiness Review (PRR) Document.

All content must be fully documented and saved in an approved industry standard repository, Currently, the Government provides Serena PVCS as the repository for use.

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 19 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00K

2. TITLE OF DATA ITEM

AFTER ACTION REPORT (AAR)

3. SUBTITLE

SLDCADA RELEASE AFTER ACTION REPORT (AAR)

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-82245

5. CONTRACT REFERENCE

PWS PARA 5.1.2.1, 5.1.3.4

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

SEMIA

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

6 MONTHS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

10/14/2022

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

Semi-annually, one technical data package delivered per software modification made as part of semi-annual release.

DESCRIPTION:

SLDCADA Release After Action Report (AAR) detailing all known issues and action items, at the completion of each production release.

It will include:

1. At completion of each planned production release, an operational assessment report shall be provided detailing all known issues and action items.

2. System incident reports and release lessons learned documentation and identified corrective actions to include analysis of software quality (follow on defects if any), and recommended improvements to processes. Metrics are to be reported in alignment with those defined in PWS Section 5.1.1.2 and the SLDCADA QASP.

3. A Customer Satisfaction survey of release results measuring customer acceptance of changes introduced as part of the contractors Quality Assurance Plan (QAP) (CDRL A009).

COR 0 1 0

TPOC 0 1 0

PCO 0 1 0

15.TOTAL 0 3 0

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY

DD FORM 1423, FEB 2024 Page 20 of 29

(Updated 20260512)UNCLASSIFIED

UNCLASSIFIED

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

All CLINS

B. EXHIBIT

C. CATEGORY:

TDP TM OTHER ALSS

D. SYSTEM/ITEM

SLDCADA

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A00L

2. TITLE OF DATA ITEM

PHASED SUPPORT PLAN

3. SUBTITLE

CONTRACTOR TRANSITION PHASE-IN PLAN

4. AUTHORITY (Data Acquisition Document No.)

DI-ALSS-80037B

5. CONTRACT REFERENCE

PWS PARA 5.1.1.10

6. REQUIRING OFFICE

PMW 220 Navy ERP

7. DD 250 REQ

8. APP CODE

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ONE/P

11. AS OF DATE

N/A

12. DATE OF FIRST SUBMISSION

10 DAYS AFTER AWARD

13. DATE OF SUBSEQUENT

SUBMISSION

N/A

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

16. REMARKS

DESCRIPTION:

Develop a Transition Phase-in Plan that consists of a timeline for onboarding support personnel and transitioning actions and shall provide sufficient detail to ensure that no break in services is experienced. Onboarding contractor lead shall provide Transition Phase-in Plan to the Government to coordinate any necessary efforts with the out-processing contractor.

1. The Contractor shall provide the Government a Transition Phase-in Plan that addresses the first 30 days (in calendar days) of the task order performance period.

2. The Transition Phase-in Plan shall address all activities and tasks to orderly and efficiently receive knowledge transfer from the out-processing contractor with the Government providing the coordination.

3. The Plan shall consist of a timeline for onboarding support personnel, transitioning actions, and sufficient detail to ensure that no break in services is experienced.

4. The Plan shall detail all required meetings with out-processing Contractor to review work in progress tasks and challenges, and deliverables in progress and planned, and the required transition knowledge needed.

5. The Plan shall be reviewed in detail at the Contract Kickoff Meeting (CDRL A00N) with the Government for acceptance.

COR 0 1 0

TPOC…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Nov 6, 2026.