CDRLs.doc
DOC document 4 MB Posted
- Attached to
- Route Clearance Interrogation System (RCIS)
- Solicitation number
- W56HZV15R0156
About this file
RCIS Contract Data Requirements Lists
View the file
Other files
Show 40 more
Latest 50 of 72 listed here. See the rest on GovTribe.
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
RCIS Contract Data Requirements List
15 April 2015 DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense (DOD) and U.S. DOD Contractors Administrative or Operational use (21 Nov 2011).Other requests for this document shall be referred to the PM FP, PdM ALUGS
Note: All CDRL deliverables, both formal and informal, shall be submitted to the Government TARDEC ACE repository.
| CDRL |
| Title |
| A001 |
| Integrated Master Schedule (IMS) |
| A002 |
| Contract Work Breakdown Structure (CWBS) |
| A003 |
| Contract Funds Status Report (CFSR) |
| A004 |
| Systems Engineering Management Plan (SEMP) |
| A005 |
| System/Subsystem/Component Specification |
| A006 |
| Requirements Compliance Matrix (RCM) |
| A007 |
| System/Subsystem Design Description (SSDD) |
| A008 |
| Interface Control Documents (ICDs) |
| A009 |
| Interoperability Profile (IOP)-Contractor Standards |
| A010 |
| Reserved |
| A011 |
| Frequency Allocation Data |
| A012 |
| Proposed Vehicle Modifications |
| A013 |
| Routing Diagrams-Cabling, Wiring Harnesses, and Plumbing |
| A014 |
| Software Development Plan (SDP) |
| A015 |
| Software Requirements Specification (SRS) |
| A016 |
| Interface Requirements Specification (IRS) |
| A017 |
| Interface Design Document (IDD) |
| A018 |
| Software Design Description (SDD) |
| A019 |
| Software Test Plan (STP) |
| A020 |
| Software Test Description (STD) |
| A021 |
| Software Test Report (STR) |
| A022 |
| Software Version Description (SVD) |
| A023 |
| Source Code and Executables |
| A024 |
| Software License Package |
| A025 |
| Security Authorization Package |
| A026 |
| Configuration Baseline |
| A027 |
| Baseline Change Notification (BCN) |
| A028 |
| EMD Technical Data Package (TDP) |
| A029 |
| Risk Management Status Reports |
| A030 |
| Reliability & Maintainability Program Plan (RPP) |
| A031 |
| R&M Case Report (RCR) |
| A032 |
| System Safety Program Plan (SSPP) |
| A033 |
| Safety Assessment Report (SAR) |
| A034 |
| Hazard Tracking System (HTS) |
| A035 |
| Hazardous Material Management Report (HMMR) |
| A036 |
| Human Systems Integration (HSI) Management Plan (HSIMP) |
| A037 |
| HSI Issue Database |
| A038 |
| HSI Event Test Plan |
| A039 |
| HSI Test Reports |
| A040 |
| Human Factors Engineering Analysis (HFEA) |
| A041 |
| Soldier Performance and Workload |
| A042 |
| Soldier Survivability Assessment (SSvA) |
| A043 |
| Logistics Management Information (LMI) Data Summaries |
| A044 |
| LORA |
| A045 |
| Core Logistics Analysis Source of Repair Analysis (CLA/SORA) |
| A046 |
| Engineering Data for Provisioning (EDFP) |
| A047 |
| Provisioning and Other Pre-Procurement Screening Data |
| A048 |
| Technical Manuals |
| A049 |
| Item Unique Identification (IUID) |
| A050 |
| Operator & MaintainerTask Analysis |
| A051 |
| Training Aids, Devices, Simulators, and Simulations (TADSS) analysis |
| A052 |
| Program of Instruction (POI) |
| A053 |
| Course Management Plan (CMP) |
| A054 |
| Individual Student Assessment Plan (ISAP) |
| A055 |
| Operator Test Administrative Guide (TAG) |
| A056 |
| Student Guide Part Training Support Package (TSP) |
| A057 |
| Risk Management Worksheets |
| A058 |
| Advance Sheets |
| A059 |
| Multi-Media |
| A060 |
| Operator Course Testing Plan (CTP) |
| A061 |
| Contractor Verification Test Plan |
| A062 |
| Test Inspection Report |
| A063 |
| Certifications |
| A064 |
| Analysis Reports |
| A065 |
| EMD Test Support Plan (ETSP) |
| A066 |
| Failure Analysis and Corrective Action Report (FACAR) |
| A067 |
| Manufacturing Development Strategy |
| A068 |
| Obsolescence Management |
| A069 |
| Anti-Tamper Plan |
| A070 |
| Meeting Minutes |
| A071 |
| Conference Agenda |
CONTRACT DATA REQUIREMENTS LIST
Form Approved OMB No. 0704-0188
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, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
A
C. CATEGORY:
TDP _ _ TM _ _ OTHER
D. SYSTEM/ITEM
RCIS
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A001
2. TITLE OF DATA ITEM
Integrated Master Schedule (IMS)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MGMT-81650(T)
5. CONTRACT REFERENCE
C.2.3
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
Monthly
12. DATE OF 1ST SUBMISSION
20 DAC
14.
DISTRIBUTION
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
11. AS OF DATE
7 Days
13. DATE OF SUBSEQUENTMonthly
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS:
Block 4: The IMS shall be prepared IAW DI-MGMT-81650 as specified except for the paragraphs below which represent tailoring of the Data Item Description (DID).
References to planning packages are not applicable. The contractor shall not utilize planning packages in the creation or update of the IMS. A formal Integrated Master Plan (IMP) is not required by the SOW. References to the IMP are not applicable.
The IMS shall be delivered electronically in an electronic file produced by the contractor's scheduling tool that is compatible with Microsoft Project version 2010.
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Blocks 12, 13: To be submitted to the Contracting Officer Representative (COR) at the monthly IPT meetings IAW SOW C.3.5.1.
Block 14: Distribution email addresses:
To be submitted to the COR identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
Repro = Electronic Delivery
COR
| - |
| - |
| 1 |
| 15. TOTAL |
| - |
| - |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
21 Jan 2015
1. DATA ITEM NO.
A002
2. TITLE OF DATA ITEM
Contract Work Breakdown Structure (CWBS)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MGMT-81334D
5. CONTRACT REFERENCE
C.2.4
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
A
11. AS OF DATE
13. DATE OF SUBSEQUENT
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The contractor shall deliver the draft CWBS at the Start of Work Meeting (SOWM).
The Government requires up to 15 business days to review and comment.
Block 13: The contractor shall deliver the final CWBS no later than 15 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
| 1. DATA ITEM NO. |
| 2. TITLE OF DATA ITEM |
| 3. SUBTITLE |
| A003 |
| Contract Funds Status Report (CFSR) |
| 4. AUTHORITY |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| DI-MGMT-81468 |
| C.2.5 |
| PM FP, PdM ALUGS |
7. DD 250 REQ
NO
| 9. DISTRIBUTION STATEMENT REQUIRED |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| D |
| Quarterly |
| See Block 16 |
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
SUBMISSION
| Draft |
| Final |
| See Block 16 |
| See Block 16 |
| Reg |
| Repro |
16. REMARKS:
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 12: The initial submission shall be within 20 business days after the end of the Calendar Quarter following Contract Award.
Block13: Subsequent submission shall be submitted within 20 business days after the end of each Calendar Quarter, Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
COR
15. TOTAL
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A004
2. TITLE OF DATA ITEM
Systems Engineering Management Plan (SEMP)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-SESS-81785(T)
5. CONTRACT REFERENCE
C.4.1
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft SEMP no later than 40 business days after contract award.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final SEMP no later than 15 business days after Government comments are provided.
Tailered as follows:
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A005
2. TITLE OF DATA ITEM
System/Subsystem/Component Specification
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81431A,
5. CONTRACT REFERENCE
C.4.2
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/r
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 4: This CDRL applies to system, subsystem and component level specifications. DI-IPSC-81431A tailored as follows: It is preferred (but not required) the specifications be submitted IAW DOORS Project Archive (DPA). See embedded attachment for DPA format.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Specification no later than 15 business days prior to the Preliminary Design Review (PDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Specification no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in Microsoft Office format and/or DOORS DPA format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A006
2. TITLE OF DATA ITEM
Requirements Compliance Matrix (RCM)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MISC-80711A(T)
5. CONTRACT REFERENCE
C.4.3
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/r
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 4: DI-MISC-80711A(T) tailored as follows: The RCM shall be delivered IAW the embedded spreadsheet and include supporting data that describes the analysis that has been done to support the assessment of compliance. The RCM shall describe and include all related data which includes sketches, preliminary drawings, schematics, functional diagrams, test results necessary to support compliance assessment.
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: Date of first submission (draft RCM) is at the Start of Work Meeting (SOWM). Preliminary analysis is acceptable.
Block 13: Date of second submission (final RCM) is 15 business days prior to the Preliminary Design Review (PDR). Complete final analysis and related data to support assessment of compliance is required.
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A007
2. TITLE OF DATA ITEM
System/Subsystem Design Description (SSDD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81432A
5. CONTRACT REFERENCE
C.4.4
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft SSDD no later than 15 business days prior to the Critical Design Review (CDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final SSDD no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A008
2. TITLE OF DATA ITEM
Interface Control Document (ICD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-CMAN-81248B(T)
5. CONTRACT REFERENCE
C.4.5
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft ICD no later than 15 business days prior to the Critical Design Review (CDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final ICD no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in a Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A009
2. TITLE OF DATA ITEM
Interoperability Profile (IOP) – Contractor Standards
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MISC-80711A(T)
5. CONTRACT REFERENCE
C.4.7
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 4: DI-MISC-80711A(T) tailored as follows: The contractor shall provide a non-proprietary interface description with electrical, signal, mechanical, connector, and digital message protocol information in contractor format to completely describe the implementation.
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft IOP documentation no later than 15 business days prior to the Preliminary Design Review (PDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final IOP documentation no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO
A011
2. TITLE OF DATA ITEM
Frequency Allocation Data
3. SUBTITLE
Preparation of DD Form 1494, Application for
Equipment Frequency Allocation.
4. AUTHORITY (Data Acquisition Document No.)
DI-EMCS-81827
5. CONTRACT REFERENCE
C.4.8
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST
STATEMENT
C
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
14. DISTRIBUTION
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
A
11. AS OF DATE
13. DATE OF SUBSEQUENT SUBMISSION
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft DD1494 form, Application for Equipment Frequency Allocation, no later than 15 business days prior to the Preliminary Design Review (PDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final DD1494 form no later than 15 business days after Government comments are provided.
Block 14: Submit data using form DD1494 in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL ---------( |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A012
2. TITLE OF DATA ITEM
Proposed Vehicle Modifications
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MISC-80711A(T)
5. CONTRACT REFERENCE
C.4.10
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Vehicle Modification documentation no later than 15 business days prior to the Preliminary Design Review (PDR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Vehicle Modification documentation no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A013
2. TITLE OF DATA ITEM
Routing Diagrams - Cabling, Wiring Harnesses, and Plumbing)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MISC-80711A
5. CONTRACT REFERENCE
C.4.11
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Routing Diagrams no later than 15 business days prior to the System Verification Review (SVR).
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Routing Diagrams no later than 15 business days after Government comments are provided.
Block 14: Deliver documents in Microsoft Office format.
Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 0 |
| 1 |
| 15. TOTAL |
| 1 |
| 0 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A014
2. TITLE OF DATA ITEM
Software Development Plan (SDP)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81427A
5. CONTRACT REFERENCE
C.5.2
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Development Plan no later than 40 business days after contract award.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Development Plan no later than 15 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A015
2. TITLE OF DATA ITEM
Software Requirements Specification (SRS)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81433A
5. CONTRACT REFERENCE
C.5.3
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Requirements Specification no later than 60 business days after contract award.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Requirements Specification no later than 15 business days after Government comments are provided.
Block 14 : Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A016
2. TITLE OF DATA ITEM
Interface Requirements Specification (IRS)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81434A
5. CONTRACT REFERENCE
C.5.4
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Interface Requirements Specification no later than 60 business days after contract award.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Interface Requirements Specification no later than 15 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A017
2. TITLE OF DATA ITEM
Interface Design Document (IDD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81436A
5. CONTRACT REFERENCE
C.5.5
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Interface Design Document no later than 30 business days after PDR.
The Government requires up to 45 business days for review and comment.
Block 13: The Contractor shall deliver the final Interface Design Document no later than 30 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A018
2. TITLE OF DATA ITEM
Software Design Description (SDD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81435A
5. CONTRACT REFERENCE
C.5.6
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Design Description no later than 30 business days after PDR.
The Government requires up to 45 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Design Description no later than 30 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A019
2. TITLE OF DATA ITEM
Software Test Plan (STP)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81438A
5. CONTRACT REFERENCE
C.5.8
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Test Plan no later than 30 business days before CDR.
The Government requires up to 30 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Test Plan no later than 30 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A020
2. TITLE OF DATA ITEM
Software Test Description (STD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81439A
5. CONTRACT REFERENCE
C.5.9
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Test Description no later than 30 business days before CDR.
The Government requires up to 30 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Test Description no later than 30 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A021
2. TITLE OF DATA ITEM
Software Test Report (STR)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81440A
5. CONTRACT REFERENCE
C.5.10
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software Test Report no later than 30 business days after the Software test event.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Test Report no later than 15 business days after Government comments are provided.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| APM |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A022
2. TITLE OF DATA ITEM
Software Version Description (SVD)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81442A
5. CONTRACT REFERENCE
C.5.11
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
SEE BLOCK 16
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: Software Version Description shall be delivered for each formal software release.
Block 12: The Contractor shall deliver the draft Software Version Description no later than 15 business days prior to each Software test event.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Software Version Description no later than 15 business days after Government comments are provided.
The Contractor shall deliver additional Software Version Descriptions to correspond with each formal release of software versions 15 business days prior to the software test event. The Government requires up to 15 business days for review and comment. The Contractor shall deliver the final Software Version Description no later than 15 business days after Government comments are provided.
Blpock 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A023
2. TITLE OF DATA ITEM
Source Code and Executables
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-IPSC-81447A
5. CONTRACT REFERENCE
C.5.12
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
AS REQ
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Format and delivery will be discussed and determined at the Start of Work meeting. (SOWM).
Dates of subsequent submissions will be determined at the SOWM and mutually agreed to by both parties.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A024
2. TITLE OF DATA ITEM
Software License Package
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-SESS-81877(T)
5. CONTRACT REFERENCE
C.5.13
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ONE/R
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 4: This deliverable is tailerod to only identify and deliver all commercial software licenses for all software utilized on the delivered SAC systems.
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Software Documentation; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: ONE/R is defined as one submittal with revisions.
Block 12: The Contractor shall deliver the draft Software License Package no later than 60 business days prior to end of contract.
The Government requires up to 15 business days for review and comment.
Block 13: The Contractor shall deliver the final Interface Requirements Specification no later than 30 business days after Government comments are provided.
Software License Package shall be in Contractor format.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A025
2. TITLE OF DATA ITEM
Security Authorization Package
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MISC-81762
5. CONTRACT REFERENCE
C.6.4
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
SEE BLOCK 16
12. DATE OF 1ST SUBMISSION
SEE BLOCK 16
14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
| 11. AS OF DATE |
| 13. DATE OF SUBSEQUENT |
SEE BLOCK 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only Operations Security; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10, 12, 13: The Cyber Security Assessment and Authorization (A&A) artifacts are due 90 business days prior to the start date of any formal test event requiring an interim authority to test (IATT), and 90 business days prior to request for an Authority to Operate (ATO) decision. The Government will provide comments and return to the Contractor within 10 business days of receipt. Upon any comments received, the contractor shall address those comments within 15 business days of receipt.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| 1 |
| 1 |
| 15. TOTAL |
| 1 |
| 1 |
G. PREPARED BY
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A026
2. TITLE OF DATA ITEM
Configuration Baseline
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-SESS-81877
5. CONTRACT REFERENCE
C.7.3
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ASREQ
| 12. DATE OF 1ST SUBMISSIONSee Block 16 |
| 14. |
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Submit configurations for approval in contractor format.
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 10: Copies are due 20 business days prior to Critical Design Review (CDR) Block 12: Final copy is to be submitted 20 business days after CDR Block 13: Subsequent copies are due within 20 business days of Government approved contractor revisions , approved by the COR, to the Configuration Baseline. Prior to revision, the contractor shall submit the proposed revisions to the COR for Government approval..
Block 14: Distribution email addresses:
To be submitted to the COR identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| - |
| - |
| 1 |
| 15. TOTAL |
| - |
| - |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A027
2. TITLE OF DATA ITEM
Baseline Change Notification (BCN)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-CMAN-80639C(T)
5. CONTRACT REFERENCE
C.7.4.2
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ASREQ
12. DATE OF 1ST SUBMISSION
SEE BLOCK 16
14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
11. AS OF DATE
SEE BLOCK 16
13. DATE OF SUBSEQUENT
SEE BLOCK 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 11, 12, and 13 Within 10 business days after any changes to the Baseline Configuration.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
| COR |
| - |
| - |
| 1 |
| 15. TOTAL |
| - |
| - |
| 1 |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A028
2. TITLE OF DATA ITEM
EMD Technical Data Package (TDP)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-SESS-80776A
5. CONTRACT REFERENCE
C.8.3, C.8.4.2
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
ASREQ
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
11. AS OF DATE
See Block 16
13. DATE OF SUBSEQUENT
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Blocks 11, 12, and 13: The TDP is to be delivered upon completion of EMD.
Block 14: Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract at the completion of the contract.
COR
| 15. TOTAL |
| - |
| 1 |
| - |
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO
A029
2. TITLE OF DATA ITEM
Risk Management Status Report
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-MGMT-81809
5. CONTRACT REFERENCE
C.9.2
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
MONTHLY
12. DATE OF 1ST SUBMISSION
See Block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
N/A
11. AS OF DATE
5 DAY
13. DATE OF SUBSEQUENT
See Block 16
| Draft |
| Final |
| Reg |
| Repro |
16. REMARKS
Block 9: “DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or Operational Use; 21-MAY-2015). Other requests shall be referred to PdM ALUGS, Building 1414 West Perimeter Road, SFAE-CSS-FP-RA; MS 901, Harrison Township MI 48045.
Block 12: Date of first submission (initial Status) is 20 business days prior to the Start of Work Meeting (SOWM).
Block 13: Monthly submissions should be made 5 business days before the end of the month.
Block 14: Deliver documents in Microsoft Office format Distribution email addresses:
To be submitted to the Contracting Officer Representative (COR) identified in FAR clause 52.242-4016 “Communications” located in Section G of the contract.
COR
15. TOTAL
G. PREPARED BY
APM
H. DATE
21 Jan 2015
I. APPROVED BY
PdM ALUGS
J. DATE
1. DATA ITEM NO.
A030
2. TITLE OF DATA ITEM
Reliability & Maintainability (R&M) Program Plan (RPP)
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
DI-SESS-81613(T)
5. CONTRACT REFERENCE
C.10.1
6. REQUIRING OFFICE
PM FP, PdM ALUGS
7. DD 250 REQ
NO
9. DIST STATEMENT
D
10. FREQUENCY
One
12. DATE OF 1ST SUBMISSION
See block 16 14.
| a. ADDRESSEE |
| b. COPIES |
8. APP CODE
A
11. AS OF DATE
N/A
13. DATE OF SUBSEQUENT
See block 16
| Draft |
| Final |
| Reg |
| Repro |
REMARKS
Block 4: Content. Delete subparagraphs a-l and replace with:
a. Reliability Management and Organization. The report shall include an organizational chart that provides visibility into the management and organizational structure of those responsible and accountable for the conduct of reliability activities. The organization structure shall clearly define how those responsible for reliability activities interact with the design, systems engineering, test and evaluation, cost, and supportability teams. The organization structure shall also depict the interface between the Government and all subcontractors/suppliers (when applicable). The report shall define all responsibilities for the reliability team.
b. Reliability Requirements. The report shall include all reliability requirements and the source of the requirements. Any derived requirements shall include all assumptions related to the derivation of the reliability metric.
c. System Reliability Model (SRM). The report shall address the methods and tools that will be used for developing and refining the SRM. The report shall document how the SRM will be updated as the design evolves and new information about failure modes is identified. The SRM is a graphical depiction of the system with an underlying analysis such as Reliability Block Diagram, Fault Tree, or Event Tree.
d. Critical Elements. The report shall identify how critical elements will be identified. Critical elements are defined as those elements (subsystems/assemblies/subassemblies) whose failure impacts mission completion, essential functions, or safety; or elements whose failure rates contribute significantly to the overall system.
e. Design for Reliability (DfR) Activities. The report shall document all planned DfR activities and the resources required to conduct the associated activities. DfR encompasses the management and reliability engineering activities executed during the design stage that identify and characterize failure modes at the lowest indenture levels possible before system-level prototyping.
f. Reliability Growth Management. The report shall document the reliability growth schedule (the closing of the gap between the current predicted levels and the goals), plans for tracking reliability growth, and any associated risks.
g. Software Reliability. The report shall define the software reliability process to ensure the robustness of all software items. The process describes the assumptions and software development activities such as fault-tolerant software design, software verification methods, software integration and dynamic test approaches to achieve system reliability goals. The report shall describe a detailed approach to collect software reliability data and reliability metrics and how the contractor will use the software reliability best practices as cited in Software Reliability Implementation Guide - SAE JA 1003 (May 2012) to address possible software task activities, methods and techniques.
h. System Constraints, Loads, and Stresses. The report shall document the expected constraints, loads, and stresses for the life cycle of the system and the impact on the system design. The report shall also document plans to verify and validate the expected constraints, loads, and stresses. The plan shall include all stresses and loads that the system may encounter during normal operational usage (as defined by the User) and their effect on the reliability of the system.
i. Reliability Prediction. The report shall document planned reliability predictions and how they are integrated into the program’s master schedule. The report shall document what tools and techniques will be used for assessing the reliability throughout system development. Each prediction shall include its associated reliability metric and risk criteria (low, medium, high) based upon the following guidance:
i. Low Risk – Test data or reliability analysis of comparable systems (under Operational Mode Summary/Mission Profile [OMS/MP] conditions);
ii. Medium Risk – Historical reliability of systems of similar complexity, test data, or reliability analysis of comparable systems (not following OMS/MP conditions) ; and
iii. High Risk – SME engineering estimates
j. Failure Mode, Effects, and Criticality Analysis (FMECA). The report shall document how failure modes and their effects will be identified. The report shall also document how this information will influence system design and corrective action analysis, development, and implementation.
k. Failure Reporting, Analysis, and Corrective Action System (i.e. FRACAS). The report shall document the Closed-Loop Failure Mode Mitigation Process. The report shall document how analysis, test, and field failure modes will be monitored, assessed, prioritized, and communicated throughout the organization. The report shall also document what strategies will be used for identifying, developing, and approving corrective actions to eliminate failure causes throughout the life cycle.
l. Reliability Test Plans. The report shall document all planned reliability test(s) and other development or operational tests where reliability data will be collected for failure mitigation and reliability assessments. Any data collection requirements shall also be addressed.
m. Reliability Reviews and Reports. The report shall document all planned reliability reviews and reports. These reviews shall be integrated into the master schedule and may include Preliminary Design Review, Critical Design Review, Test Readiness Reviews, Failure Review Boards, and Reliability Assessment Conferences.
n.
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 .