Exhibit-A-CSRR- CM-CDRLs18Dec2017.pdf

PDF 560 KB Posted Jan 9, 2018

Attached to: Common Submarine Radio Room (CSRR) Control and Management (C&M) Software
Solicitation number: N00039-17-R-0056
Issued by: Department of the Navy Information Warfare Systems Command

View the file

Other files

File	Type	Posted
Attachment 3 - Prime_Contractor_Cost_Summary-Spreadsheet.xlsx	XLSX spreadsheet	Jan 9, 2018
Attachment 2 - DD254 N00039-17-R-0056.pdf	PDF	Jan 9, 2018
Attachment 5 - Reference Information Form.docx	DOCX document	Jan 9, 2018
Attachment 4 - Subcontractor_Cost_Summary-Spreadsheet.xlsx	XLSX spreadsheet	Jan 9, 2018
CSRR NDA for RFP.docx	DOCX document	Jan 9, 2018
Attachment 8 - Government Furnished Property.pdf	PDF	Jan 9, 2018
Attachment 1 - CSRR_CandM_SOW__18Dec2017.pdf	PDF	Jan 9, 2018
Attachment 6 - Past Performance Questionnaire.docx	DOCX document	Jan 9, 2018
N00039-17-R-0056.pdf	PDF	Jan 9, 2018
CSRR RFI SOW DRAFT 24JAN2017 REV1.pdf	PDF	Apr 26, 2017
CSRR NDA.docx	DOCX document	Apr 26, 2017

Show all 11

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.

N00039-17-R-0056

Common Submarine Radio Room (CSRR) Control and Management (C&M)

Contract Data Requirements List (CDRL)

Exhibit A

CDRL Title Date of First Occurrence

SOW

Reference

A001 Contract Work Breakdown Structure

(CWBS)

ASREQ 2.1.1.7

A002 Integrated Program Management Report

(IPMR)

12 working days after the end of the first full accounting period

ACA

2.1.1.1, 2.1.1.2, 2.1.1.5, 2.1.1.6

A003 Contract Funds Status Report (CFSR) 12 working days after the end of the first full accounting period

ACA

2.1.1.8

A004 Manpower Reporting Yearly, NLT OCT

A005 Contractor's Progress, Status and Management Report

NLT 10th of each month

2.1.1, 2.3.3

A006 Conference Agenda ASREQ 2.1.1.10, 2.1.2.1, 2.1.2.2, 2.1.2.3, 2.1.2.4, 2.1.2.5

A007 Conference Minutes ASREQ 2.1.1.10, 2.1.2.1, 2.1.2.2, 2.1.2.3, 2.1.2.4, 2.1.2.5

A008 Software Development Plan (SDP) 30DACA 2.5.1.1, 2.5.4 A009 Software Requirements Specification

(SRS)

ASREQ 2.5.4

A010 Technical Report Studies/Services ASREQ 2.1.2.1, 2.1.2.2, 2.2 A011 System/Subsystem Design Description

(SSDD)

ASREQ 2.5.4

A012 Software Development File (SDF) 30 DA software acceptance

2.5.4

A013 Software Version Description (SVD) Prior to entering test acceptance

2.5.4

A014 Software Installation Plan (SIP) At EOE delivery 2.5.4 A015 Software Test Plan (STP) ASREQ 2.5.4, 2.5.5 A016 Software Test Procedures 30 days prior to

TRR

2.5.4, 2.5.5

A017 Software Test Report (STR) 30 DA software acceptance

2.5.4, 2.5.5

A018 Software Users Manual (SUM) Prior to entering test acceptance

2.5.4

A019 Computer Software Product End Items ASREQ 2.5.3.4 A020 Status of Government Furnished Property

Report

ASREQ 2.3

CONTRACT DATA REQUIREMENTS LIST Form Approved

OMB No. 0704-0188

Public reporting burden for this collection of information is estimated to average 440 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 Washington Headquarter 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

A. CONTRACT LINE ITEM NO.

0001, 0101, 0201, 0301, 0401

B. EXHIBIT NO.

C. CATEGORY

TDP TM OTHER

D. SYSTEM/ITEM

CSRR C&M

E. CONTRACT/PR NO.

F. CONTRACTOR

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Contract Work Breakdown Structure (CWBS)

3. SUBTITLE

17. PRICE

GROUP

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81334D

5. CONTRACT REFERENCE

SOW Para. 2.1.1.7

6. REQUIRING OFFICE

PMW 770-4

18. ESTIMATED

TOTAL PRICE

7. DD 250 REQ 9. DIST

STATEMENT

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ONE/R See Blk 16 See Blk 16 B. COPIES

8. APP CODE

11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

A. ADDRESSEE DRAFT FINAL

See Blk 16 D ASREQ/ See Blk 16 REG REPRO

16. REMARKS

The CWBS shall consist of two parts as follows:

Part I INDEX: The CWBS shall include a table mapping/correlating all CWBS elements to:

a. The associated Technical Direction Letter(s), CLIN(s) and PWS paragraph(s)

b. The contractor’s responsible organizational/functional element(s) and/or Integrated Product Team(s) responsible for accomplishment of the CWBS element work scope.

Part II CWBS DICTIONARY: CWBS dictionary definitions shall include complete descriptions of the technical and cost content of each CWBS element. Definitions shall include a physical characterization for product-oriented elements, and shall be as descriptive as possible about the components, efforts, and tasks that are included in the CWBS element. Short descriptions of the work content and work processes to produce the end item or service shall also be included. The CWBS elements shall be in the same order as the Part I Index. CWBS element numbers shall precede the CWBS element title/description.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8: PMW 770 will be the Approving Activity.

BLOCKS 10, 11, 13: Subsequent submissions shall be as required, 12 business days after the end of the contractor’s first full accounting period following any of the following:

• To reflect any Government approved evolutionary CWBS and associated CWBS Dictionary element additions and/or major revisions. CWBS Dictionary submissions shall not be for more frequent than CWBS report submissions.

• Award of a new Technical Direction Letter.

• In accordance with Integrated Baseline Review

The CWBS shall also be updated and available for review at PMRs and other meetings as requested by the Government.

For all submissions the Government will have 20 working days to review and provide written comments. Government will submit comments by email and/or the PMW 770 shared server. Contractor shall have 5 working days to analyze Government comments and schedule a comment adjudication followed by 10 working days to resubmit a revised document. Government will review revised document to verify adjudicated comments and provide approval within 10 working days.

Shared server

See Blk 16

15. TOTAL

G. PREPARED BY

K. BOISVERT

H. DATE

I. APPROVED BY

CAPT M.J. BOONE

J. DATE

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-3

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A002

2. TITLE OF DATA ITEM

Integrated Program Management Report (IPMR)

DI-MGMT-81466A

5. CONTRACT REFERENCE

SOW Para. 2.1.1.1, 2.1.1.2, 2.1.1.5, 2.1.1.6

See Blk 16 REQUIRED MTHLY See Blk 16 B. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

See Blk 16 D See Blk 16 See Blk 16 REG REPRO

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8: PMW 770 will be the Approving Activity.

BLOCK 4: The contractor shall deliver a monthly Integrated Program Management Report (IPMR) in accordance with DI-MGMT-81861 requirements except or as modified by the following instructions:

General Instructions:

• Formats 1, 5, 6, and 7 are mandatory. Until such time as the total estimated contract price (including all known options and/or TDL’s) exceeds $50M, Formats 2, 3, and 4 are not required.

• The "as of" date on the monthly CPR submittal will follow the contractor's accounting period and the contractor will submit its accounting calendar for the period of performance of the contract for planning purposes.

• If applicable, any/all subcontractor CPR or other EVM-like report submittals to the Prime shall be submitted to the Government along with the Prime contractor’s monthly CPR submittal. Subcontractor data shall not lag in performance periods.

Format 1 (WBS Performance Data) tailoring Instructions:

• Format 1 IPMR reporting levels will be at CWBS level 3 of the MIL-STD-881 CWBS.

Prime Mission Product hardware and Software elements and any other elements of special interest or high risk may be selected for reporting at lower levels identified using the contractor’s extended CWBS.

• Format 1 data shall provide standalone visibility for major subcontractor effort and material procurement.

• Cost of Money (COM) costs shall be included at the CWBS level in block 8a.

Corresponding non-additive COM entries shall also be made in Block 8b.

• G&A costs shall be included at the CWBS level block in 8a. Corresponding non-additive G&A entries will also be made in Block 8c.

Format 5 (Explanations and Problem Analyses) tailoring instructions:

• Initial Format 5 Explanations and Problem Analyses shall be in accordance with DI- MGMT-81861, Section 3.6, as tailored by the following:

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-4

A002 – Integrated Program Management Report (IPMR) (continued)

• The contractor shall provide explanations in Format 5 for current period, cumulative, and at-completion variances for Format 1 CWBS reporting level elements that exceed the following thresholds:

VARIANCE THRESHOLD

Current Month +/- 5% and $50k Cumulative +/- 10% and$75k Variance at Completion +- 5% and $50k

• Thresholds above are estimates used on similar SPAWAR programs. Once the Government can review a Responsibility Assignment Matrix assigning dollars to the WBS elements, thresholds shall be discussed at the Post Award Conference and adjusted as necessary at no cost to the government to ensure they provide appropriate insight and visibility relative to the target cost/risk. The Contractor shall follow DiD paragraphs 3.6.10.2.3, 3.6.10.2.4 and 3.6.10.2.4.2.2 to determine the pool of reportable variances and the variance reporting down selection process.

• Periodically, the Government and the contractor will jointly review and mutually agree if adjustment to Format 1 reporting levels and Format 5 variance analysis threshold levels are required to ensure the IPMR continues to provide appropriate management visibility through the period of performance of the program. Thresholds shall not be changed without Government approval.

• Current Month variances are to be explained separately from cumulative variances, and cost variances are to be explained separately from schedule variances. Variance at Completion analysis is to be included as part of the accompanying Format 5 Program Management Overview narrative (see below).

• Variance explanations for each CWBS element breaking the agreed to thresholds shall address the technical cause, the near-term impact to the reporting element, the impact to other elements and the overall program, and the corrective action plan established to adjudicate the issue. The corrective action plans are to be updated in each submittal.

• Schedule variance narratives shall also identify the significant missed milestones, impact to major milestones, and expected recovery dates.

• In addition to WBS variance analyses, Format 5 shall also include a Program Management Overview narrative assessment of EVM performance to date as well as a predictive narrative of overall program health. This narrative is to include:

o A forward-looking, proactive Program Management view of the expected progress to be made, and problems anticipated to be encountered for at least the three next reporting periods o MR changes and usage o UB contents and changes o Differences and rational for the Best, Worst Case, and Most Likely Management EAC's o Explanation of changes to the time phasing of the baseline information in Format 3 (when Format 3 is applicable) o Explanation of changes to the staffing information in Format 4, identifying staffing issues (attrition, shortfalls, etc.,) where they exist (when

Format 4 is applicable) o Performance measurement milestones that are not consistent with contractual milestones (e.g., in the event an approved OTS is implemented) o Formal reprogramming implementation details (e.g., in the event an approved OTB is implemented) and any other topic relevant to cost, schedule or technical performance.

Format 6 (Integrated Master Schedule- IMS) Tailoring Instructions:

The contractor shall develop, maintain, and deliver Format 6, a logically networked Integrated Master Schedule (IMS) in accordance with DI-MGMT- 81861 requirements (Section 3.7) as tailored by the following instructions:

• The contractor shall use the Department of Defense Integrated Master Plan and Integrated Master Schedule Preparation and Use Guide (Version 0.9, 21 OCT 2005) as a reference in preparing the IMS.

• The IMS shall include the activities for all subcontractor and supplier efforts unless IPMR Format 6 IMS requirements are flowed down to the subcontractor, in which case the subcontractor Format 6 IMS will be submitted as a standalone deliverable in addition to and in conjunction with the prime contractor’s monthly IPMR submittal.

• The IMS shall be sufficiently detailed such that the network critical path, driving paths to interim milestones defined in the Delivery Order SOW (i.e., SFR, TRR, PRR), high technical risk activities, and other significant SOW efforts are identified and planned realistically to assure executability

• Any/all external dependencies shall be included in the IMS and logically linked to appropriate tasks. Required or expected external dependency delivery date shall also be identified in the IMS. External dependencies shall be identified with unique coding/structure to facilitate separate analysis

• The contractor shall submit Schedule Risk Assessments (SRA) in accordance with DI-MGMT-81861 section 3.7.1.3.6 requirements as tailored by the following instructions:

• SRAs shall be performed and submitted as follows:

• An SRA shall be submitted as part of/in conjunction with the contractor’s IMP/IMS Technical Volume proposal response.

• An SRA shall be submitted prior to the initial Integrated Baseline Review.

• Subsequent SRAs shall be performed on an interim milestone event driven schedule (i.e., milestones defined in the SOW). The specific interim milestone event SRA delivery schedule will be mutually agreed to at the Post Award Conference or as soon as possible following award.

Format 7 (Electronic History and Forecast File) Tailoring Instructions):

Format 7 is to be submitted in accordance with DI-MGMT-81861 requirements (Section 3.8) as tailored by the following instructions:

• Quarterly Format 7 submittals shall contain time-phased and historical monthly performance data provided at the same CWBS reporting levels specified in Format 1 instructions above. Exceptions will apply when significant (+/-5%) changes are made to the EAC in the interim months of the quarter. Quarters will be defined at the PAC with consideration to the vendor’s accounting calendar and EAC review processes.

• If the contractor flows down IPMR requirements to subcontractors (e.g., those subcontracts that meet EVM application thresholds), the contractor shall submit separate subcontract Format 7 data files. Otherwise, inclusion of subcontractor data in Format 7 is limited to that which is included in the prime contractor’s EVM cost tool.

BLOCKS 11 & 12: First submission is due within 12 working days after the end of the first full accounting period following contract award. Formats, content, and requirements of the first submission will be mutually agreed to NLT the post contract award kick-off meeting. IPMR reporting will continue during the program period of performance until end of contract award.

BLOCK 13: Subsequent monthly submissions shall be provided within 12 working days after the close of the contractor’s monthly accounting period, no exceptions. Submittal timelines are set by the DiD. CSRR is not determined to be a complex EVM implementation. Final submission is due when the last significant milestone/deliverable, as defined by the contract, has been achieved and remaining risk areas have been mitigated with Government concurrence.

BLOCK 14: The contractor shall format CPR deliverables for Electronic Data Interchange (EDI) in accordance with the instructions contained in DI- MGMT 81861. The Contractor shall post electronic copy to the PMW 770 shared server placing the file(s) in the “Documents” section in the subfolder identified for deliverables and submit an e-mail notification. At a minimum, the name of the file being posted shall contain the CDRL number, title of the document being submitted, document revision, and document date with no spaces but using “underscore” for data separation (i.e., A002_IPMR_Rev1_2011May23). When a document is being reposted, the Contractor shall also post the associated Comment Adjudication matrix.

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-7

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A003

2. TITLE OF DATA ITEM

Contract Funds Status Report (CFSR)

DI-MGMT-81468 (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.1.1.8

6. REQUIRING OFFICE

PMW 770-4

See Blk 16 REQUIRED QTRLY See Blk 16 B. COPIES

BLOCK 4: The contractor shall deliver a quarterly CFSR in accordance with DI-MGMT- 81468 requirements except or as modified by the following instructions:

a. The CFSR will provide funding requirements and time phased detail by TDL , by CLIN (and for multiple funding appropriations, if applicable.) A total program rollup is also required.

b. The prime contractor is responsible for flowing down/ integrating CFSR requirements to all subcontractors if applicable.

c. The prime contractor shall reconcile the reporting elements in the CFSR with the relevant reporting elements in the IPMR when the documents are submitted in the same month. The contractor will also identify the components of fee, overruns, cost sharing, termination liability and open commitments, as applicable, in the notes section of the CFSR.

d. All time phased data will be grouped in a manner that provides visibility by Government fiscal year. It may be necessary for the contractor to provide monthly increments at the beginning of the program or when EAC changes and/or contract modifications, new TDL’s are implemented.

BLOCK 8: PMW 770 will be the Approving Activity.

BLKS 11 & 12: First submission shall be NLT 12 working/calendar days after the end of the contractor’s first accounting month following contract award. If the baseline changes as a result of PMB/IBR planning, a revision to the first CFSR submission will be made and submitted NLT 12 working/ calendar days after the end of the contractor’s first accounting month following completion of the IBR.

BLOCK 13: Subsequent submissions will be quarterly, NLT 12 calendar days after the end of the contractor's accounting quarter for March, June, September, and December.

BLOCK 14: The contractor shall submit the CFSR in accordance with DI-MGMT- 81468.The Contractor shall post electronic copy to the PMW 770 shared server placing the file(s) in the “Documents” section in the subfolder identified for deliverables and submit an e-mail notification. At a minimum, the name of the file being posted shall contain the CDRL number, title of the document being submitted, document revision, and document date with no spaces but using “underscore” for data separation (i.e., A003_CFSR_Rev1_2011May23). When a document is being reposted, the Contractor shall also post the associated Comment Adjudication matrix.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A004

2. TITLE OF DATA ITEM

Labor Hours Reporting

NMCARS 5237.102(90)

5. CONTRACT REFERENCE

SOW Para 2.1.1.9

18.

ESTIMATED

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION See Blk 16 REQUIRED YEARLY See Blk 16 B. COPIES

BLKS 11 & 12: Inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

BLOCK 13: Subsequent submissions will be yearly, NLT October 31 of each calendar year.

BLOCK 14: The contractor shall submit ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Space and Naval Warfare Systems Command (SPAWAR) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil. E-mail notification to the COR upon completion of data entry.

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-8 https://doncmra.nmci.navy.mil/ https://doncmra.nmci.navy.mil/

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A005

2. TITLE OF DATA ITEM

Contractor’s Progress, Status and Management Report

DI-MGMT-80227 (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.1.1, 2.3.3

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED MTHLY NLT 10th of month B. COPIES

See Blk 16 D See Blk 16 NLT 10th of month REG REPRO

BLOCK 4: Contractor’s format is acceptable.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8: PMW 770 will be the Approving Activity.

BLOCK 11: Report shall be as of the end of the Contractor’s business month.

BLOCK 16: Report shall include:

1. Updated Integrated Master Schedule

2. Management Risks

3. Work Accomplished

4. Major Issues

5. Software Metrics

a. Number of software personnel charging to the software project (estimated vs. actual staffing levels)

b. Number of total hours worked (estimated vs. actual hours)

c. CSRR software project personnel turnover (estimated vs. actual) and recovery plan

d. Listing of all efforts performed identifying functional areas.

e. Percentage Progress Report on each effort

f. Outstanding Issues

g. Requirements Volatility

h. Use cases (planned vs actuals)

i. SLOCs (estimated vs actuals)

j. Component test cases (planned vs completed)

k. Integration test cases (planned vs completed)

l. Software builds (planned vs completed)

m. Problem reports (open vs closed)

6. Reports of Significant TELECONs and Commitments

7. Status of ECPs

8. Planned Work

9. Identification of Organization Changes

10. Status of Previously Reported Problems

11. Identification of Completed Travel

12. Commitments/Action Items and Issues from Meetings

13. Government Property

a. Number of items on contract

b. Number of items on contact which require IUID marking

c. Provide number of items marked with IUID reported to IUID Registry

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-9

B. EXHIBIT NO.

E. CONTRACT/PR NO.

1. DATA ITEM

NO.

A006

2. TITLE OF DATA ITEM

Conference Agenda

DI-ADMN-81249A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.1.1.9, 2.1.2.1, 2.1.2.2, 2.1.2.3, 2.1.2.4, 2.1.2.5

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ASREQ/ See Blk 16 See Blk 16 B. COPIES

See Blk 16 D See Blk 16 REG REPRO

BLOCK 4: Contractor’s format is acceptable. The Government reserves the right to modify the agenda.

BLOCK 8: PMW 770 will be the Approving Activity.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 10, 12 & 13: Prior to major milestones, the contractor shall submit an agenda 10 days prior to meetings. The contractor shall submit briefing materials 5 days prior to major milestone meetings. The Government reserves the right to modify the agenda and request additional briefing material.

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-10

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-11

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A007

2. TITLE OF DATA ITEM

Conference Minutes

DI-ADMN-81250A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.1.1.9, 2.1.2.1, 2.1.2.2, 2.1.2.3, 2.1.2.4, 2.1.2.5

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14 DISTRIBUTION

See Blk 16 REQUIRED ASREQ See Blk 16 ASREQ/ See Blk 16 B. COPIES

BLOCK 4: Contractor’s format is acceptable. Minutes outline, topics, and action items shall be signed by principal representatives for the contractor and PMW770 at the conclusion of meetings.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8: PMW 770 will be the Approving Activity.

BLOCK 10, 12 & 13: For major milestone meetings the Contractor shall submit meeting minutes 5 days after meeting or review.

BLOCK 14: The Contractor shall post electronic copy to the PMW 770 shared server placing the file(s) in the “Documents” section in the subfolder identified for deliverables and submit an e-mail notification. At a minimum, the name of the file being posted shall contain the CDRL number, title of the document being submitted, document revision, and document date with no spaces but using “underscore” for data separation (i.e., Public reporting burden for this collection of information is estimated to average 440 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 Washington Headquarter 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

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A008

2. TITLE OF DATA ITEM

Software Development Plan (SDP)

DI-IPSC-81427A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.5.1.1, 2.5.4

See Blk 16 REQUIRED ONE/R See Blk 16 30DACA B. COPIES

BLOCK 4: Contractor’s format is acceptable. The content of the SDP, however, needs to meet certain criteria. Specifically, the SDP shall:

Document all processes applicable to the system to be acquired, including the Primary, Supporting, and Organizational life cycle processes as defined by IEEE/EIA Std. 12207 as appropriate;

Contain the content defined by all information items listed in Table 1 of IEEE/EIA Std. 12207.1, as appropriate for the system and be consistent with the processes proposed by developers. If any information item is not relevant to either the system or to the proposed process, that item need not be required;

Adhere to the characteristics defined in section 4.2.3 of IEEE/EIA Std. 12207, as appropriate; and Contain information at a detail sufficient to allow the use of the SDP as the full guidance for the developers. In accordance with section 6.5.3a of IEEE/EIA Std. 12207.1, it should contain, “specific standards, methods, tools, actions, reuse strategy, and responsibility associated with the development and qualifications of all requirements, including safety and security.”

DID No. DI-IPSC-81427A provides the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.

BLOCK 8 & 13: PMW 770 will be the Approving Activity. As required, the Government will have 20 working days to review and provide written comments. Government will submit comments by e-mail and/or the PMW 770 shared server. Contractor will have 10 working days to analyze Government comments and schedule a comment adjudication followed by 15 working days to resubmit a revised document. Government will review revised document to verify adjudicated comments and provide approval within 15 working days.

BLOCK 10 & 13: Update document as major changes necessitate.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A009

2. TITLE OF DATA ITEM

Software Requirements Specification (SRS)

DI-IPSC-81433A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.5.4

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ONE/R See Blk 16 ASREQ/See Blk 16 B. COPIES

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8 & 13: PMW 770 will be the Approving Activity. The Government and the Contractor will schedule a Joint Technical Review within 10 working days after posting a draft version of the CDRL. The Contractor shall have 15 working days after the Joint Technical Review to incorporate comments and post a final version of the CDRL. The Government will have 15 working days to provide approval.

BLOCK 10, 12 & 13: Update document as major changes necessitate.

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-13

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A010

2. TITLE OF DATA ITEM

Technical Report – Study/Services

DI-MISC-80508B (See Blk 16)

SOW Para. 2.1.2.1, 2.1.2.2, 2.2

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ASREQ See Blk 16 ASREQ/ See Blk 16 B. COPIES

BLOCK 4: Contractor format is acceptable.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8: PMW 770 will be the Approving Activity. The Government and the Contractor will schedule a Joint Techical Review within 5 working days after posting a draft version of the CDRL. The Contractor shall have 10 working days after the Joint Technical Review to incorporate comments and post a final version of the CDRL. The Government will have 10 working days to provide approval.

BLOCK 10, 12 & 13: Update document as major changes necessitate.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A011

2. TITLE OF DATA ITEM

System/ Subsystem Design Description (SSDD)

DI-IPSC-81432A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.5.4

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ONE/R See Blk 16 ASREQ/See Blk B. COPIES

BLOCK 4: Contractor’s format is acceptable. Contractor shall provide software data applicable for inclusion into an overall CSRR System level SSDD to be prepared by Naval Undersea Warfare Center (NUWC) code 341.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 10, 12 & 13: Update document as major changes necessitate.

DD Form 1423-2, JUN 90 Previous editions are obsolete. Page A-15

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A012

2. TITLE OF DATA ITEM

Software Development File (SDF)

SOW Para. 2.5.4

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ONE/R See Blk 16

ASREQ/ See Blk 16 B. COPIES

BLOCK 4: Contractor format is acceptable. The SDFs will be provided on a CD-ROM.

The SDFs will be provided 30 days after software acceptance. The SDFs contain technical, planning, progress, and defect information pertinent to the software development. The SDFs will be implemented almost entirely in an electronic form. With the exception of the software design information, which is maintained primarily in Together UML databases, the SDF information is maintained in the PC-based program development files. The SDFs will include project information such as change control information, products, design, papers, product information, COTS information, process information, and development tools; software management information such as schedules, cost/effort, progress, and status; test information such as test plans, test cases, test procedures, and test results; software development information such as source (to include common) , object, and executable software and documentation; and the requirements database.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8 & 13: PMW 770 will be the Approving Activity. Government will have 20 working days to review and provide written comments. Government will submit comments by e-mail and/or the PMW 770 shared server. Contractor shall have 10 working days to analyze Government comments and schedule a comment adjudication followed by 15 working days to resubmit a revised document. Government will review revised document to verify adjudicated comments and provide approval within 15 working days.

BLOCK 10 & 13: Updates will be provided as versions of modules are added or revised.

BLOCK 12: SDF will be provided 30 days after software acceptance.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A013

2. TITLE OF DATA ITEM

Software Version Description (SVD)

DI-IPSC-81442A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.5.4

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED ONE/R See Blk 16 ASREQ/See Blk 16 B. COPIES

See Blk 16 D ASREQ/See Blk 16 REG REPRO

BLOCK 4: Contractor’s format is acceptable submission shall include the source and executable code.

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8 & 13: PMW 770 will be the Approving Activity. Government will have 15 working days to review and provide written comments. Government will submit comments by e-mail and/or the PMW 770 shared server. Contractor shall have 10 working days to analyze Government comments and schedule a comment adjudication followed by 15 working days to resubmit a revised document. Government will review revised document to verify adjudicated comments and provide approval within 15 working days.

BLOCK 10/12/13: The SVD will be provided prior to entering test acceptance.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A014

2. TITLE OF DATA ITEM

Software Installation Plan (SIP)

DI-IPSC-81428A

5. CONTRACT REFERENCE

SOW Para. 2.5.4

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

See Blk 16 REQUIRED ASREQ See Blk 16 ASREQ See Blk 16 B. COPIES

See Blk 16 D ASREQ See Blk 16 REG REPRO

BLOCK 7: Electronic notification suffices as LT.

BLOCK 8 & 13: PMW 770 will be the Approving Activity. The Government and the Contractor will schedule a Joint Technical Review within 5 working days after posting a draft version of the CDRL. The Contractor shall have 5 working days after the Joint Technical Review to incorporate comments and post a final version of the CDRL. The Government will have 5 working days to provide approval.

BLOCK 10, 12 & 13: Update as required.

BLOCK 12: The SIP shall be provided at EOE delivery.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A015

2. TITLE OF DATA ITEM

Software Test Plan (STP)

DI-IPSC-81438A (See Blk 16)

SOW Para. 2.5.4, 2.5.5

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

REQUIRED ONE/R See Blk 16 ASREQ B. COPIES

BLOCK 7: Electronic notification suffices as LT.

BLOCK 10 & 13: Initial test plans for subsequent prototype phases are due 3 months before scheduled testing begins.

B. EXHIBIT NO.

E. CONTRACT/PR NO.

A016

2. TITLE OF DATA ITEM

Software Test Procedures

DI-IPSC-81439A (See Blk 16)

5. CONTRACT REFERENCE

SOW Para. 2.5.4, 2.5.5

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

A. ADDRESSEE DRAFT FINAL

See Blk

D ASREQ/ See Blk 16 REG REPRO

BLOCK 7: Electronic notification suffices as LT.

BLOCK 10 & 13: Initial test procedures for subsequent prototype phases are due 2 months before scheduled testing begins.

BLOCK 12: Preliminary submission due 30 days prior to Test Readiness Review (TRR).

BLOCK 13: Adjudicated submission required 5 working days prior to…

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.