MSV(L)_DRAFT_-_CDRLs__A001_-_A100.pdf

PDF 968 KB Posted Feb 19, 2016

Attached to: Maneuver Support Vessel (Light) MSV-L Federal contract opportunity
Solicitation number: W56HZV15R0187
Issued by: Department of the Army Materiel Command Contracting Command Detroit Arsenal

View the file

Other files for this federal contract opportunity

Other files attached to Maneuver Support Vessel (Light) MSV-L, newest first.
File	Type	Posted
RFI_Q&As_02Dec2016.pdf	PDF	Dec 2, 2016
Interested_Potential_Subcontractors_MSV(L)_26JULY16.pdf	PDF	Jul 26, 2016
Interested_Potential_Subcontractors_MSV(L)_26JULY16.pdf	PDF	Jul 26, 2016
Interested_Potential_Subcontractors_MSV(L)_20JULY16.pdf	PDF	Jul 20, 2016
Interested_Potential_Prime_Contractors_MSV(L)_22JUNE16.pdf	PDF	Jun 22, 2016
RFI_Maneuver_Support_Vessel_(MSV)_Light_(2016).pdf	PDF	Mar 4, 2016
MSV(L)_DRAFT_-_Statement_of_Work_(SOW).pdf	PDF	Feb 19, 2016
RFI_Maneuver_Support_Vessel_(MSV)_Light_(2016).pdf	PDF	Feb 19, 2016
MSV(L)_DRAFT_-_Payload_Data_Table.pdf	PDF	Feb 19, 2016
MSV(L)_DRAFT_-_SOW_Attachment_List.pdf	PDF	Feb 19, 2016
MSV(L)_DRAFT_-_Production_Schedule.pdf	PDF	Feb 19, 2016
MSV(L)_DRAFT_-_CDRL_List.pdf	PDF	Feb 19, 2016
Industry_Day_Q As.pdf	PDF	Feb 10, 2016
Instructions_for_Interested_Potential_PRIME_Contractors-MSV(L).xlsx	XLSX spreadsheet	Dec 9, 2015
Instructions_for_Interested_Potential_SubC-MSV(L).xlsx	XLSX spreadsheet	Dec 9, 2015
Industry_Day_Agenda.pdf	PDF	Nov 24, 2015
NoticeMSV(L)-Revised_ATPD-Classified_Annex-Nov2015.docx	DOCX document	Nov 19, 2015
Notice-MSV-L-FOUO-Instructions.docx	DOCX document	Nov 13, 2015
DD_254_Continuation_Sheets_W56HZV-15-R-0187.pdf	PDF	Nov 13, 2015
DD_254_MSV(L)_Solicitation_W56HZV-15-R-0187.pdf	PDF	Nov 13, 2015
QA-MSVL-28Oct15.pdf	PDF	Oct 29, 2015
Army_Watercraft_Systems_(AWS)_Industry_Day_Announcement.pdf	PDF	Oct 14, 2015
NoticeMSV(L)-RFI-Sept2015.docx	DOCX document	Sep 11, 2015
MSV(L)SpeedRFIQuestions-Aug2015.docx	DOCX document	Sep 8, 2015
RFI-MSV-L.doc	DOC document	Sep 8, 2015
NoticeMSV-L.docx	DOCX document	Sep 8, 2015

Show all 26

On GovTribe

Work with this file on GovTribe

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.

DD FORM 1423, FEB 2001

CONTRACT DATA REQUIREMENT LIST, PREVIOUS EDITION MAY BE USED Form Approval OMB No. 0704-0188 The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.: A001 B. EXHIBIT: A

C. CATEGORY: TDP ____ TM ____ OTHER __X

D. SYSTEM/ITEM: MSV(L) E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A001 2. TITLE: Conference Agenda

3. SUBTITLE: Agenda and Read-Ahead Packages 4. AUTHORITY: DI-ADMN-81249A

5. CONTRACT REFERENCE: SOW C.2.2, C.3.1, C.6.1.1, C.6.2, C.6.4.1.1, C.6.4.2.1,

C.6.4.3.1, C.6.5.1, C.6.5.3,

6. REQUIRING OFFICE: SFAE-CSS-TS-W (PM TS AWS) 7. DD250 REQ: LT

8. APP CODE: A 9. DIST. STATEMENT REQ: C

10. FREQUENCY: SEE BLK 16 11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: SEE BLK 16

13. DATE OF SUBS. SUBMISSION: SEE BLK 16

14. DISTRIBUTION:

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

BLK 10,12 & 13: Unless otherwise stated in the SOW, All Meetings with a recurrence of Monthly or more frequent, Submission is due no later than (NLT) 1 day prior to Meeting. SOWM Submission is due NLT 2 days prior to the SOWM.

Unless otherwise stated in the SOW, All Meetings that occur less than Monthly and onetime events, initial submission is due NLT 14 days prior to each event and meeting. The Government will propose any changes to the agenda and read ahead package no later than 7 days prior to the event and meeting. Subsequent submission with the Final Version of the agenda and briefing charts is due NLT 2 days prior to the event.

BLK 14: Meeting agendas and read-ahead package shall be submitted electronically to the PD AWS SharePoint server. The Government IPT Lead shall be notified when data has been submitted. The submission shall be prepared and delivered in an editable Microsoft Office software suite file format (MS Word, MS Excel, MS PowerPoint, etc.)

G. PREPARED BY: Brian Matthews I: APPROVED BY:

H: DATE: 25 Jan 2016 J: DATE:

No. 0704-0188 The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.: A002 B. EXHIBIT: A

C. CATEGORY: TDP ____ TM ____ OTHER __X

D. SYSTEM/ITEM: MSV(L) E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A002

2. TITLE: Report, Record of Meeting Minutes

3. SUBTITLE: Minutes

4. AUTHORITY: DI-ADMN-81505

5. CONTRACT REFERENCE: SOW C.2.2, C.3.1, C.6.1.2, C.6.2, C.6.3.4.6, C.6.5.3,

6. REQUIRING OFFICE: SFAE-CSS-TS-W (PM TS AWS)

7. DD250 REQ: LT

8. APP CODE: A

9. DIST. STATEMENT REQ: C

10. FREQUENCY: SEE BLK 16

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: SEE BLK 16

13. DATE OF SUBS. SUBMISSION: SEE BLK 16

14. DISTRIBUTION:

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

BLK 8: Final version of minutes shall be submitted for Government approval within 7 days of receipt of Government comments.

BLK 10, 12 and 13: Initial submission is due NLT 7 days after these events.

The final version of the minutes is due NLT 7 days after receipt of Government feedback.

BLK 14: Meeting Minutes shall be submitted electronically the PD AWS SharePoint server. The Government IPT Lead shall be notified when data has been submitted. The submission shall be prepared and delivered in an editable Microsoft Office software suite file format (MS Word, MS Excel).

G. PREPARED BY: Brian Matthews I: APPROVED BY:

A. CONTRACT LINE ITEM NO.: A003 B. EXHIBIT: A

C. CATEGORY: TDP ____ TM ____ OTHER __X D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A003

2. TITLE: Integrated Master Schedule (IMS)

3. SUBTITLE:

4. AUTHORITY: DI-MGMT-81861(T) – SEE BLK 16

5. CONTRACT REFERENCE: SOW C.2.4.4, C.6.2.1, C.6.2.2, C.6.5.4.1, C.14.2

6. REQUIRING OFFICE: SFAE-CSS-TS-W (PM TS AWS)

7. DD250 REQ: LT

8. APP CODE: A

9. DIST. STATEMENT REQ: C

10. FREQUENCY: SEE BLK 16

11. AS OF DATE: SEE BLK 16

12. DATE OF FIRST SUBMISSION: SEE BLK 16

13. DATE OF SUBS. SUBMISSION: SEE BLK 16

14. DISTRIBUTION:

A. ADDRESSEE: SEE BLK 16

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

BLK 4: The DID is tailored as follows: Only Format 6 of the Integrated Program Management Report (IPMR) is required. The IMS will track all contractor scope for the life of the contract.

In addition to the contents of the DID applicable to Format 6, the monthly IMS submittals shall include a Critical and Near Critical Path report that includes tasks within 10 working days of the critical float value to Government indicated milestones, provided at the Start of Work Meeting (SOWM), in Gantt Chart format. A float analysis and variance report of the Critical Path with a narrative explanation of the root cause and corrective action or mitigation plan to recover the lost schedule shall be provided. The IMS submittal shall include all schedule changes to actual dates, target dates, estimated dates, and physical percent complete. A list of late start and late finish activities with a narrative explanation shall be provided.

The IMS shall be capable of expanding and collapsing the Logistics, System Engineering and Test & Evaluation sections within the IMS to allow the IPTs to easily track their specific schedule activities.

In addition to providing Format 6 in the contractor’s native IMS schedule electronic file format, the contractor will also deliver the Format 6 IMS, showing all schedule activities, in Portable Document Format (PDF) file format.

IMS required from subcontractors shall be integrated with the prime contractors scheduling system submission. IMS required from subcontractors shall also be provided in Subcontractors approved scheduling system in its original format.

BLK 10: Submission of the IMS is monthly.

BLK 11: Status will reflect progress through the contractors week ending date immediately prior to the date of CDRL delivery.

BLK 12: Initial submission is due at the SOWM.

BLK 13: The IMS is due monthly on the dates agreed upon at the SOWM. The IMS will be delivered until the end of the contract.

BLK 14: All file formats (native IMS schedule, XML, and PDF) must be electronically forwarded to the PD AWS SharePoint server site for electronic delivery. The Government IPT lead shall be notified when data has been submitted.

G. PREPARED BY: Brian Matthews I: APPROVED BY:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__

D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A004

2. TITLE: Technical Report–Study/Services

3. SUBTITLE: Cybersecurity Program Plan

4. AUTHORITY: – DI-MISC-80508B

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: ASREQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS: Block 4: In addition to the content of the DID, the Cybersecurity Program Plan shall include in contractor format the following items:

a. implementation of data at rest;

b. implementation of data loss prevention;

c. protection of data in transit over wired and wireless networks;

d. prevention of unauthorized software;

e. incident reporting and response;

f. continuous monitoring and compliance checking;

g. controls of information and data;

h. classified information;

i. information inventory;

j. information disclosure;

k. subcontractor flow down;

l. distribution statement marking;

m. access control;

n. contractor location;

o. network threat monitoring;

p. user and administrator training;

q. roles, responsibilities, and access;

r. acceptable use policies;

s. other government information oversight organizations;

t. cyber supply chain risk management plan;

u. mitigation plan for common weakness enumeration items;

v. mitigation plan for common attack patterns enumeration and classification items.

Block 8: Comments from the Government shall be addressed in an updated re-submission by the Contractor within 30 business days of receipt of Government comments.

Block 12: Initial submission required when Allocated Baseline is established.

Block 13: Subsequent submissions are due every six months. If no changes occur a submittal is not required, but the contractor shall submit a negative notification.

Block 14: This information shall be submitted electronically to the MSV(L) SharePoint server. The Government IPT lead shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Office 2007 file format (MS Word, MS Excel).

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: D. Brown

H: DATE: 1/26/16

I: APPROVED BY: PdAWS

J: DATE:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__

D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A005

2. TITLE: Technical Report–Study/Services

3. SUBTITLE: Cybersecurity Artifact Package

4. AUTHORITY: DI-MISC-80508B – SEE BLK 16

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: ASREQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

Block 4: In addition to the content of the DID, the Cybersecurity Artifact Package shall include the following items:

a. high and low level information systems architecture;

b. ports, protocols and services documentation;

c. configuration management plan;

d. software development plan;

e. system backup and restoration procedures;

f. account management procedures;

g. roles based access permission description;

h. user manual(s);

i. administrator and maintainer manual(s);

j. legal and technical document traceability;

k. products undergoing cryptographic certification, status and evaluating organization;

l. products undergoing IA and IA enabled product certification, status and evaluating organization;

m. other artifacts as needed to meet risk management framework documentation requirements.

Block 8: Comments from the Government shall be addressed in an updated re‐ submission by the Contractor within 15 business days of receipt of Government comments.

Block 12: Initial submission required 45 days prior to Baseline Cybersecurity Scan.

Block 13: A subsequent submission is required 60 days after the Baseline Cybersecurity Scan. After the first subsequent delivery, subsequent submissions are required 5 business days after government approval of contractor initiated ECPs.

Block 14: This information shall be submitted electronically to the MSV(L)SharePoint server. The Government IPT lead shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Office 2007 file format (MS Word, MS Excel).

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: D. Brown

H: DATE: 1/26/16

I: APPROVED BY: PdAWS

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A006

2. TITLE: Tactical Public Key Infrastructure (TPKI) Implementation Analysis

3. SUBTITLE:

4. AUTHORITY: DI-MISC-80508B– SEE BLK 16

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: 1TIME

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

Block 4: In addition to the content of the DID, The TPKI Implementation Analysis shall include the following items to be implemented and managed:

a. digital signature for software

b. digital signature and encryption for communications;

c. PKI support for data encryption;

d. PKI implementation for identification;

e. interoperation with DoD GIG PKI;

f. future interface of devices that will utilize MSV(L) and MSV(L) -hosted resources to connect to the

GIG;

g. ruggedized PKI token and reader (used for group and/or individual certificates) Block 8: Comments from the Government shall be addressed in an updated re-submission by the Contractor within 30 business days of receipt of Government comments.

Block 12: Submission is required 60 days after Functional Baseline is established.

Block 14: This information shall be submitted electronically to the MSV(L) SharePoint server. The

Government IPT lead shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Office 2007 file format (MS Word, MS Excel).

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: C. Hodder

H: DATE: 1/26/16

I: APPROVED BY: PdAWS

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A007

2. TITLE: Cybersecurity Log Management Plan

3. SUBTITLE:

4. AUTHORITY: DI-MISC-80508B– SEE BLK 16

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: AS REQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS: Block 4: In addition to the content of the DID, The Cybersecurity Log Management Plan shall include the following items:

a. identification, format and location of audit logs

b. event and file audit logging settings

c. access control restrictions on audit log files and folders

d. audit log management and archive process

e. audit event‐based management and alerting Block 8: Comments from the Government shall be addressed in an updated re‐ submission by the Contractor within 30 business days of receipt of Government comments.

Block 12: Initial submission required 45 days prior to Baseline Cybersecurity Scan.

Block 13: A subsequent submission is required 60 days after the Baseline Cybersecurity Scan.

After the first subsequent submission, subsequent submissions are required 5 business days after government approval of contractor initiated ECPs.

SharePoint server. The Government IPT lead shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Office 2007 file format (MS Word, MS Excel).

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: D. Brwon

H: DATE: 1/26/16

I: APPROVED BY: PdAWS

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A008

2. TITLE: Cybersecurity Vulnerability Management Software Maintenance Plan

3. SUBTITLE:

4. AUTHORITY: DI-MISC-80508B– SEE BLK 16

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: AS REQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS: Block 4: In addition to the content of the DID, the Cybersecurity Software Vulnerability Management Plan shall include the following items:

a. source, chain of custody, and verification of software patches

b. patch integration and testing

c. patch deployment and verification

d. patch application and verification on smart displays

e. process for out‐of‐band or emergency patches Block 8: Comments from the Government shall be addressed in an updated re‐ submission by the Contractor within 30 business days of receipt of Government comments.

Block 12: Initial submission required 45 days prior to Baseline Cybersecurity Scan.

Block 13: A subsequent submission is required 60 days after the Baseline Cybersecurity Scan.

After the first subsequent submission, subsequent submissions are required 5 business days after government approval of contractor initiated ECPs.

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: D. Brown

H: DATE:

I: APPROVED BY: PdAWS

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A009

2. TITLE: Risk Management Plan

3. SUBTITLE:

4. AUTHORITY: DI-MGMT-81808

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: 7. DD250 REQ:

8. APP CODE: 9. DIST. STATEMENT REQ:

10. FREQUENCY: ASREQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS: Block 4:

Block 12: Initial draft submission is due 30 Calendar days after contract award.

Block 13: Subsequent submissions 30 days after receipt of government comments on initial submission.

Block 14: The CDRL shall be submitted electronically to the MSV(L) SharePoint server. The Government IPT Lead shall be notified when data has been submitted. The submission shall be prepared and delivered in an editable and Microsoft Office 2007 software suite file format (MS Word, MS Excel, MS PowerPoint, MS Visio)

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: I: APPROVED BY:

H: DATE: J: DATE:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A010 2. TITLE: Performance and Cost Report

3. SUBTITLE: 4. AUTHORITY: 5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: SFAE-CSS-TS-W (PM TS AWS)

7. DD250 REQ: LT

8. APP CODE: NA

9. DIST. STATEMENT REQ: A

10. FREQUENCY: As Requested

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: SEE BLK 16

13. DATE OF SUBS. SUBMISSION: SEE BLK 16

14. DISTRIBUTION:

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

Block 11: Contractor’s fiscal month accounting period end (cutoff) date.

Block 12: Initial submission is due no later than (NLT) 12 calendar days following the first full fiscal month accounting period after contract award.

Block 13: Subsequent submissions are due each month, NLT 12 calendar days following the contractor’s fiscal month accounting period end (cutoff) date.

Block 14: The CDRL shall be submitted electronically to the PD AWS MSV(L) SharePoint site. The contractor shall notify the Government IPT Lead when data has been submitted. A list of IPT leads will be provided to the contractor at the Start of Work Meeting (SOWM). Submissions shall be in a readable format utilizing MS Word 2007®, MS Excel 2007®, or Adobe Acrobat®; variation from these formats requires Government approval. Submissions shall not include macros, program executables, embedded objects, or external files.

G. PREPARED BY: Roxanne Szczesniak I: APPROVED BY:

H: DATE: 25 Nov 2015 J: DATE:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A011

2. TITLE: CONTRACT WORK BREAKDOWN STRUCTURE (CWBS) INDEX & DICTIONARY

3. SUBTITLE:

4. AUTHORITY: DI-MGMT-81334D

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit the CWBS Index and CWBS Dictionary (at Level 3 CWBS) in accordance with DI-MGMT-81334D, MIL-STD-881C (Appendix E: Sea Systems), and as tailored in this CDRL.

MIL-STD-881C, Data Item Descriptions (DIDs) and Reporting Forms, as well as examples are available from the Defense Cost and Resource Center (DCARC) Web site at http://dcarc.cape.osd.mil/csdr/default.aspx.

Blocks 10, 11, 12 and 13:

Frequency, As of Date, and Submission dates must be in accordance with the Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2

Production). Draft submissions are required 45 days prior to the Final submission.

Block 13:

The Contractor shall update and maintain both the CWBS Index and the CWBS Dictionary during the life of the contract. Changes to the CWBS or associated definitions, at any reporting level, require approval of the Government prior to implementation.

Block 14:

The deliverables shall be submitted electronically. The Government IPT lead shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Excel 2007 file format.

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY:

H: DATE:

I: APPROVED BY:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A012

2. TITLE: COST DATA SUMMARY REPORT (DD FORM 1921)

3. SUBTITLE:

4. AUTHORITY: DI-FNCL-81565C

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit initial, interim and final DD Form 1921 (Level 3 CWBS) in accordance with the Cost and Software Data Reporting (CSDR) Plan (Attachment 1), the CWBS Data Dictionary (Level 3 CWBS), and DI-

FNCL-81565C.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense Cost and Resource Center (DCARC) Web site at http://dcarc.cape.osd.mil/csdr/default.aspx.

Blocks 10, 11, 12 and 13:

Block 14:

The deliverables shall be submitted electronically. The Government IPT lead

G. PREPARED BY:

H: DATE:

I: APPROVED BY:

A. CONTRACT LINE ITEM NO.:

B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER _X__

D. SYSTEM/ITEM: MANEUVER SUPPORT VESSEL (LIGHT)(MSV(L))

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A013

2. TITLE: FUNCTIONAL COST-HOUR REPORT (DD FORM 1921-1)

3. SUBTITLE:

4. AUTHORITY: DI-FNCL-81566C

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit initial, interim and final DD Form 1921-1 (Level 3 CWBS) in accordance with the Cost and Software Data Reporting (CSDR) Plan (Attachment 1), the CWBS Data Dictionary (Level 3 CWBS), and DI-

FNCL-81665C.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense Cost and Resource Center (DCARC) Web site at http://dcarc.cape.osd.mil/csdr/default.aspx.

Blocks 10, 11, 12 and 13:

G. PREPARED BY: JENNIFER FLANAGAN, jennifer.l.flanagan8.civ@mail.mil

H: DATE: 25 OCTOBER 2015

A. CONTRACT LINE ITEM NO.:

B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER _X__

D. SYSTEM/ITEM: MANEUVER SUPPORT VESSEL (LIGHT)(MSV(L))

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A014

2. TITLE: SOFTWARE RESOURCES DATA REPORT: INITIAL DEVELOPER REPORT AND DATA

DICTIONARY

3. SUBTITLE: SOFTWARE RESOURCES DATA REPORTING (SRDR)

4. AUTHORITY: DI-MGMT-81739B

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit the Software Resources Data Report (SRDR): Initial Developer Report and Data Dictionary IAW the Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2 Production), the CWBS Data Dictionary (Level 3 CWBS), and Data Item Description DI-MGMT-81739B.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense Cost and Resource Center (DCARC) Web site at

Cost and Software Data Reporting (CSDR) Plan (Attachment 1). Draft submissions are required 45 days prior to the Final submission.

G. PREPARED BY:

H: DATE:

A. CONTRACT LINE ITEM NO.:

B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER _X__

D. SYSTEM/ITEM: MANEUVER SUPPORT VESSEL (LIGHT)(MSV(L))

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A015

2. TITLE: SOFTWARE RESOURCES DATA REPORT: FINAL DEVELOPER REPORT AND DATA

DICTIONARY

3. SUBTITLE: SOFTWARE RESOURCES DATA REPORTING (SRDR)

4. AUTHORITY: DI-MGMT-81740A

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit the Software Resources Data Report (SRDR): Final Developer Report and Data Dictionary IAW the Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2 Production), the CWBS Data Dictionary (Level 3 CWBS), and Data Item Description DI-MGMT- 81739B.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense

G. PREPARED BY:

H: DATE:

I: APPROVED BY:

A. CONTRACT LINE ITEM NO.:

B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER _X__

D. SYSTEM/ITEM: MANEUVER SUPPORT VESSEL (LIGHT)(MSV(L))

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A016

2. TITLE: BILL OF MATERIAL (BOM) MAPPED TO LEVEL 3 CWBS

3. SUBTITLE:

4. AUTHORITY: DI-SESS-81903(T)

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit a BoM (mapped to Level 3 CWBS) in accordance with DI-SESS-81903, the Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2 Production), and the CWBS Data Dictionary (Level 3 CWBS):

The BoM shall show part level detail and cost of each delivered MSV(L) vessel. Including all of the following:

‐ CWBS Element and Structure Level of Assembly (Hierarchy) ‐ Unit of Measure (each, kilograms, millimeters, or other) ‐ Quantity or Value required per MSV(L) (count, weight, length, or other) ‐ Weight per Unit of Measure (metric units) ‐ Nomenclature ‐ OEM Part Number (Contractor or Vendor as applicable) ‐ National Stock Number (NSN), if applicable ‐ OEM CAGE Code ‐ Level of Repair ‐ Cost Source (quote, purchase order, estimate, or other) ‐ Make or Buy ‐ Buy Type (if applicable - COTS, modified COTS, MSV(L) unique) ‐ Cost (to the USG) ‐ Extended Cost (to the USG) ‐ OEM Vendor

The cost data shall reflect actual costs. The Contractor shall provide a mapping of the BoM piece parts to Level 3 of the CWBS so that costs of the BoM piece parts roll up to the material cost at Level 3 on the DD Form 1921 (CDRL A002) and 1921-1 (CDRL A003). The Contractor shall explain any discrepancies in the data.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense Cost and Resource Center (DCARC) Web site at http://dcarc.cape.osd.mil/csdr/default.aspx.

DI-FNCL-81565C is available from the Federal Aviation Administration https://sowgen.faa.gov/.

Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2 shall be notified when the data has been submitted. All submissions shall be prepared and delivered in an editable and Microsoft Excel 2007 file format.

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY:

H: DATE:

I: APPROVED BY:

A. CONTRACT LINE ITEM NO.:

B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER _X__

D. SYSTEM/ITEM: MANEUVER SUPPORT VESSEL (LIGHT)(MSV(L))

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A017

2. TITLE: PROGRESS CURVE REPORT (DD FORM 1921-2)

3. SUBTITLE:

4. AUTHORITY: DI-FNCL-81567C

5. CONTRACT REFERENCE:

6. REQUIRING OFFICE: AMSTA-MSP-V & SFAE-CSS-TS-W

7. DD250 REQ:

8. APP CODE:

9. DIST. STATEMENT REQ:

10. FREQUENCY: BLOCK 16

11. AS OF DATE: BLOCK 16

12. DATE OF FIRST SUBMISSION: BLOCK 16

13. DATE OF SUBS. SUBMISSION: BLOCK 16

14. DISTRIBUTION: B

A. ADDRESSEE: GOVERNMENT ISSUING PROCURING CONTRACT OFFICER (PCO)

B. COPIES:

DRAFT: 1

FINAL: 1

REG REPRO:

15. TOTAL COPIES: 2

16. REMARKS:

Block 4:

The Contractor shall prepare and submit DD Form 1921-2 in accordance with the Cost and Software Data Reporting (CSDR) Plan (Attachment 1 EMD, Attachment 2 Production), the CWBS Data Dictionary (Level 3 CWBS), and DI-FNCL-81567C.

Data Item Descriptions (DIDs) and DD Forms are available from the Defense

G. PREPARED BY:

H: DATE:

A. CONTRACT LINE ITEM NO: B. EXHIBIT:

C. CATEGORY: TDP ____ TM ____ OTHER __X__ D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.: F. CONTRACTOR:

1. DATA ITEM NO: A018 2. TITLE: Design Review Documentation

3. SUBTITLE: 4. AUTHORITY: – SEE BLK 16

5. CONTRACT REFERENCE: 6. REQUIRING OFFICE:

7. DD250 REQ: 8. APP CODE:

9. DIST. STATEMENT REQ: 10. FREQUENCY: ASREQ

11. AS OF DATE:

12. DATE OF FIRST SUBMISSION: See blk 16

13. DATE OF SUBS. SUBMISSION: See blk 16

14. DISTRIBUTION: See blk 16

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS: Block 4: All material planned to be presented at the PDR and CDR. Contractor Format Acceptable.

Block 12/: Initial Read ahead material submission is due 30 Calendar days prior to PDR & CDR, respectively.

Block 13: A final delivery of the presentation material that incorporates/addresses Government comments shall be submitted 7 calendar days prior to the event. Government will provide comments 10 calendar days after receipt.

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

G. PREPARED BY: T. kler I: APPROVED BY: Pd,AWS

H: DATE: 1/27/16 J: DATE:

A. CONTRACT LINE ITEM NO.: B. EXHIBIT: A

C. CATEGORY:

TDP ____ TM ____ OTHER __X

D. SYSTEM/ITEM: MSV(L)

E. CONTRACT/PR NO.:

F. CONTRACTOR:

1. DATA ITEM NO: A019

2. TITLE: Test Readiness Reviews (TRRs)

3. SUBTITLE: DESIGN REVIEW INFORMATION PACKAGE (DRIP)

4. AUTHORITY: DI-SESS-81757A (T)

5. CONTRACT REFERENCE: C.6.5.4

6. REQUIRING OFFICE: SFAE-CSS-TS-W (PM TS AWS)

7. DD250 REQ: LT

8. APP CODE: A

9. DIST. STATEMENT REQ: C

10. FREQUENCY: SEE BLK 16

11. AS OF DATE: N/A

12. DATE OF FIRST SUBMISSION: SEE BLK 16

13. DATE OF SUBS. SUBMISSION: SEE BLK 16

14. DISTRIBUTION:

A. ADDRESSEE:

B. COPIES:

DRAFT:

FINAL:

REG REPRO:

15. TOTAL COPIES:

16. REMARKS:

BLK 4: DID DI-SESS-81757A shall be tailored as follows:

The contactor shall submit the package in accordance with sections 1.0 and

2.8 of the DID.

BLK 10,12 & 13: The contactor shall develop and submit to the Government TRR Packages for the following test events:

EMD Phase Testing

a. Scale Model Testing

b. Ballistic Coupon Testing

c. Contractor Engineering Development Testing (EDT)

d. Government EDT

Production & Deployment Phase Testing

a. Contractor Testing (Acceptance Trials)

b. Government Production Verification Testing (PVT)

c. Cybersecurity Testing

d. Government Reliability, Availability, and Maintainability (RAM)

e. Initial Operational Test and Evaluation (IOT&E)

The contractor shall submit the TRR package no less than 10 business days prior to the event.

BLK 14: The TRR package shall be submitted electronically to the PD AWS SharePoint server. The Government IPT Lead shall be notified when data has been submitted. The submission shall be prepared and delivered in an editable Microsoft Office software suite file format (MS Word, MS Excel, MS PowerPoint, etc.)

G. PREPARED BY: Jay Jambekar

H: DATE: 25 JAN 2016

I: APPROVED BY:

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 14, 2017.