Exhibit_A_CDRLs_Final.pdf

PDF 3 MB Posted Oct 24, 2019

Attached to: C-17 Terrain Awareness and Warning System (TAWS) Tool and Annual Database (DB) Sustainment
Solicitation number: FA8526-20-R-0003
Issued by: Department of the Air Force Materiel Command

About this file

From the source

Exhibit A: Contract Data Requirements List

View the file

Other files

File	Type	Posted
TAWS_SOW_19Sep2019.pdf	PDF	Oct 24, 2019
FA852620R0003.pdf	PDF	Oct 24, 2019

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.

CONTRACT DATA REQUIREMENTS LIST (CDRL)

Exhibit A

For the

C-17 Terrain Awareness and Warning System (TAWS) Tool and Annual Database (DB) Sustainment

CONTRACT:

03 September 2019

PREPARED BY THE

C-17 Program Branch, AFLCMC/WLMA

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

ROBINS AIR FORCE BASE, GA 31098-2428

TABLE OF CONTENTS

Contents

CONTRACT DATA REQUIREMENTS LIST (CDRL)

TABLE OF CONTENTS

CDRL GENERAL INSTRUCTIONS

ACRONYMS AND ABBREVIATIONS LIST

C-17 DISTRIBUTION MATRIX

PAPER COPY DELIVERY ADDRESSES

ITEMIZED CDRL List Exhibit A

CDRLs A001 – A015 .................................................................................... Error! Bookmark not defined.

CDRL GENERAL INSTRUCTIONS

1. SCOPE: This Contract Data Requirements List (CDRL) establishes the data to be delivered by the Contractor and the submittal, approval and distribution requirements of all the CDRL data items herein.

2. GENERAL: The Data Item Descriptions (DIDs) (DD Form 1664) specified in Block 4 of the corresponding CDRLs are all “active” at time of contract award and were extracted (or as found

in) the USG Document Automation and Production Service (DAPS) Web-based Database called Acquisition Streamlining and Standardization Information System (ASSIST) an the latest version of the DoD 5010.12-L Volume II, Acquisition Management System and Data Requirements Control List (AMSDL).

3. TAILORED DATA ITEMS: A slash (/) and the letter “T” (e.g. DI-MGMT-80368/T) added to the end of the DID number in Block 4 of the DD Form 1423 denotes that the DID has been tailored to comply with specific system/program requirements. Thereafter, the unique tailoring instructions are identified in Block 16 of each affected DD Form 1423.

4. MODIFICATIONS OF DATA REQUIREMENTS:

4.1. From time to time during the performance of this contract, the US Government (USG) Procuring Contracting Officer (PCO) unilaterally may change the place of delivery and the technical office for any line item of contract Exhibits (DD Form 1423) hereto, at no change in contract price, notwithstanding the provision of the “Changes” clause of the G3 contract. If there is a change in the place of delivery, the Contractor and the PCO may mutually agree to an extension of the data submittal requirement date.

4.2. From time to time during the performance of this contract, and being that the majority of data will be delivered electronically to the USG, the PCO unilaterally may increase or decrease the number of addresses and/or number of copies specified for any data item of the CDRL hereto, at no change in price provided that either the increase in the total number of copies for an individual line item of data shall not be greater than one hundred-fifty percent (150%) of the total number of copies initially specified in the CDRL or that (in the case of a decrease in delivery requirements) the decrease in the total number of copies for an individual item of data be greater than fifty percent (50%) of the total number of copies initially specified in the CDRL. In the event of an increase greater than such 150% or of a decrease greater than fifty percent (50%), the parties will negotiate any equitable adjustments.

4.3. Unilateral actions pursuant to paragraphs 4.1 and 4.2 above shall be by the issuance of a USG Procuring Contracting Officer’s Letter (PCOL) followed by a Supplemental Agreement to this contract which will reference the appropriate paragraph 4.1 or 4.2 above of these CDRL General Notes as its authority. Any action directed by this clause shall be put into effect by the Contractor beginning with the first submission of the particular data item or items immediately following receipt of the USG PCO’s direction by the Contractor.

4.4. Any other/subsequent changes to this CDRL package and not specifically pertaining to changes identified in paragraphs (a) and (b) above shall be proposed utilizing Proposed Contract Document Change Notices (PCDCNs) and submitted to the USG as an attachment to a Contract Change Proposal (CCP). Upon approval of the CCP (and the corresponding PCDCNs) by the USG, the PCDCNs shall be converted to approved CDCNs and be incorporated into the contract as part of the corresponding contract modification.

5. DATA SUBMITTALS AND SUBMITTAL APPROVALS: The following definitions apply to Block 8 of the DD Form 1423-1:

5.1. The use of an “A” in Block 8 indicates that government approval of the identified document is required to assure that the Contractor is sufficiently prepared to proceed to the next phase of the contract in addition to verifying compliance with the DID and CDRL requirements. The USG Office of Primary Responsibility (OPR) designated in Block 6 of the DD Form 1423 will be responsible for consolidating the evaluations performed by the data recipients with his own evaluation and respond through the PCO to the Contractor within forty-five (45) days after receipt of the data submittal unless specified otherwise within the CDRL.

5.2. If Block 8 is left blank or there is an “N” (or an “N/A”) in this block then these data items are considered “Non-approval”; however, this does not relieve the Contractor of the responsibility of compliance with the applicable regulations, standards, procedures, etc. All data submissions are subject to USG review and approval by the procuring agency for departure of said compliance.

5.3. The USG will formally respond to the Contractor within forty-five (45) days after receipt for any data that has been determined by the USG as being deficient and/or technically disapproved.

Data submittal requirements shall not be considered to have been met until the procuring agency has determined that all contractual requirements have been satisfactorily met regarding the identified data.

5.4. When referring to numbers of days for frequency, submittals, and subsequent submittals – all days are recognized as “calendar” days unless otherwise stated elsewhere on the DD Form 1423.

5.5. Any reference to delivery requirements tied to SRR, SSR, PDR, and/or CDR refer to program level reviews only.

6. REVISIONS TO DATA SUBMITTALS AND RESUBMITTALS OF DATA:

6.1. Unless otherwise specified, data submittals that are disapproved by the USG, shall be revised and resubmitted by the Contractor within forty-five (45) days after receipt of the official USG PCO letter. If the Contractor determines that they cannot resubmit within the initial forty-five (45) days, then the USG shall be notified in writing before the initial time has expired and a new suspense date will be established.

6.2. Unless otherwise specified, data submittals that are approved contingent upon revision shall be revised and distributed within forty-five (45) days after receipt of the official USG PCO letter or as negotiated by the Contracting Officers. If the Contractor determines that they cannot resubmit within the initial forty-five (45) days, then the USG shall be notified in writing before the initial time has expired and a new suspense date will be established. If the resubmittal requirements identified in Block 16 of the DD Form 1423 are different than stated here, then the DD Form 1423 instructions shall take precedence.

6.3. When “R/ASR” OR “ASREQ” appears in Block 13 of the DD Form 1423 with no explanatory remarks in Block 16, then all revisions to the data will be resubmitted as necessary/required to maintain the data’s currency and accuracy.

7. DATA PREPARATION:

7.1. Data submitted by the Contractor shall conform to the quality requirements specified on the CDRL for each data item. If the data preparation instructions contained in Block 16 of the DD Form 1423 are different from the instructions contained in Block 10 of the DID, the DD Form 1423 instructions shall take precedence.

7.2. Data shall be delivered by one of the following methods unless otherwise specified on the DD Form 1423.

The order of preference is:

Electronic Notification/On-line Access Magnetic Media (i.e. floppy disks/CD-ROM/Magnetic tapes) Hard Copy/Paper

8. DOCUMENT MARKING:

8.1. Distribution Statements

8.1.1. Air Force Instruction AFI 61-201, titled “Management of Scientific and Technical Information (STINFO)” specifies that certain distribution statements be assigned on each technical document to control distribution by Government agencies such as the Defense Technical Information Center (DTIC). Documents must be marked on the cover page with an appropriate corresponding distribution statement prior to submittal. Block 9 of the DD Form 1423 annotates the relevant distribution statement applicable to the data to be submitted.

8.1.2. As annotated in Block 9 of the DD Form 1423, the following distribution and warning statements will apply to all data acquired under this contract:

“DISTRIBUTION STATEMENT C” – Distribution authorized to U.S Government Agencies and their contractors (justification); (date of determination). All other requests for this documentation shall be referred to the C-17 USG TAWS Program Manager (PM), AFLCMC/WLMBA, 235 Byron Street, Suite 19A, Robins AFB, GA 31098.

8.1.3. If an export warning is deemed required by the Contractor or the USG then include the following statement on the document:

“WARNING – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC, Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, USC, App 2401, et seq. Violations of these export laws are subject to severe criminal penalties. Dissemination shall be in accordance with provisions of DoD Instruction 5230.24.”

8.1.4. When it is not technically feasible to use the entire statement, an abbreviated marking may be used; a copy of the full statement is then added to the “Notice to Accompany Release of Export Controlled Data” required by DoD Directive 5230.24 (Enclosure 4 reference g). The abbreviated form is “Warning: Export-Controlled”.

8.1.5. The Contractor is not authorized to provide copies of any data acquired under a CDRL to activities who are not specifically identified in the distribution block of the CDRL without written Government approval from the C-17 Procuring Agency Configuration Management Office (AFLCMC/WLE (CM/DM), Robins AFB, GA 31098-2428).

8.1.6. Contractor Imposed Distribution Statements. Part 35, of the Federal Acquisition Regulations (FAR) stipulates control procedures for Contractor controlled technical information in which the government has limited rights. These procedures shall be followed as described in

AFI 61-204.

8.1.7. Destruction Notices for Limited-Release STINFO and Classified STINFO are as follows:

Limited-Release STINFO (Distribution Statement other than A):

“DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

Classified STINFO:

“DESTRUCTION NOTICE: Follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), Section 5-705, or DoD 5200.1-R, Information Security Program, Chapter VI”.

8.2. Restrictive Legends

8.2.1. Commercial Technical Data

8.2.1.1. Pursuant to DFARS 252.227-7015 and Clause H-122, “Identification and Assertion of use, Release, or Disclosure Restrictions for Technical Data and Computer Software,” for Contractor marking of Commercial Technical Data, the Contractor shall apply the following legends to deliverable data under this contract as follows:

UNRESTRICTED

This document contains Commercial Proprietary Technical Data. Use, Copying and/or Disclosure by the U.S. Government of the Technical Data contained herein is subject to the restrictions set forth in Subparagraph (b)(1) of DFARS 252.227-7015 Technical Data

– Commercial Items (Feb 2014)

UNRESTRICTED – Portion Marked

Those portions of the document marked with the symbol contain commercial proprietary Technical Data contained herein is subject to the restrictions set forth in Subparagraph (b)(1) of DFARS 252.227-7015 Technical Data – Commercial Items (Feb 2014)

8.2.2. Non-commercial Technical Data

8.2.2.1. Non-commercial technical data deliverables under the contract shall be marked in accordance with DFARS 252.227-7013 rights in Technical Data – Noncommercial Items (Feb 2014). Any deviation in the markings from those found in DFARS 252.227-7013 will be nonconforming.

8.2.3. Non-technical Data

8.2.3.1. Non-technical data deliverables under this contract shall be marked with the following:

THIS DOCUMENT CONTAINS PROPRIETARY AND COMMERCIAL

INFORMATION OF “Contractor Name Here”. DISCLOSURE TO OTHERS, USE OR COPYING WITHOUT EXPRESS AUTHORIZATION OF “Contractor Name Here” IS

STRICTLY PROHIBITED.

9. METHOD OF TRANSMITTAL:

9.1. In addition to DD 250 requirements (where applicable), all data transmittal requirements shall be listed in Block 7 of the DD Form 1423-1; regardless of the physical method of data submission (i.e., on-line access, magnetic media, paper copy, etc). The requirement for “LT” may be satisfied by delivery of an electronic message and shall convey all contractually required information, including signature (or recognized symbol). The letter of transmittal and email notification shall include as a minimum: reference to the contract letter number and date, program name, CDRL number, title/subtitle, DID, revision level, and any Contractor’s control number assigned to that data. The data itself shall also contain the above information. For paper copy submittals only, the Contractor shall include a complete list of addressees (as identified in Block 14 of the DD Forms 1423-1), annotating the recipients of the actual data and transmittal – document-only recipients, as well as number of copies distributed each. For electronic message notifications, the Contractor shall include in that notification a list of all the applicable required recipients (as identified in Block 14 of the DD Forms 1423-1).

9.2. Electronic CDRL Delivery notifications made prior to 12 noon EST will credited for same day delivery. Notification received after 12 noon EST will be credited with delivery on the next working day. Time delays in web server functions an email transmissions will not affect receipt of credit for electronic CDRL delivery

9.3. Unless otherwise specified in Block 16 of the DD Form 1423-1, data submittal date is interpreted as the date of letter of transmittal. If the scheduled delivery date of any data item falls on a weekend (Saturday or Sunday), or legal holiday, the next scheduled delivery date for the data item and tracking record shall reflect the following day after the weekend or legal holiday.

9.4. If any server that impacts CDRL delivery is down 48 consecutive business-day hours (not to include weekends or holidays), regardless of whether it is a C-17 WLMA or Contractor problem, the Contractor shall: make hard copy deliveries and send overnight (i.e., FedEx, UPS, etc.) to all Block 14 addresses, send an email (or fax) to the C017 WLMA DMO and affected Government agencies stating that the system is down with expected restoral time, and send an email (or fax) advising the availability of the data in Documentum.

9.5. For each data item in the CDRL, the Contractor shall clearly state in the final transmittal letter that this is the last submittal being made and that all contractual requirements concerning that data item have hereby been fulfilled.

9.6. Classified data shall be submitted in accordance with the Department of Defense (DoD) 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

9.7. Defense Technical Information Center (DTIC) applicable data shall be delivered and marked in accordance with the DID and CDRL requirements.

9.8. When the same documentation is required on multiple contracts, only one submittal per addressee will be made IAW Block 14 of the applicable DD Forms 1423. When updates are required on one contract and not any other, then all addressees will receive the updates to the documentation IAW the Block 14 distribution requirements spelled out for that affected contract CDRL; with that contract absorbing any cost of the damage.

9.9. The USG C-17 Procuring Agency Configuration Management Office (AFLCMC/WLE (CM/DM), Robins AFB, GA 31098-2428) and the assigned DCMA shall be notified of all CDRL submittals.

ACRONYMS AND ABBREVIATIONS LIST

1TIME One Time

ACA After Contract Award

ACL Access Control List

ACO Administrative Contracting Officer

ACPINS Automated Computer Program Identification Number System

AMC Air Mobility Command

AMSDL Acquisition Management Systems and Data Requirements Control List

ANNLY Annually

AOD As of Date

ASAP As Soon As Possible

ASREQ As Required

BLK 16 Refer to Block 16

CAIG Cost Analysis Improvement Group

CDR Critical Design Review

CDAS Contract Data Accounting System

CDRL Contract Data Requirements List

CPR Contract Performance Report

DAC Days after Contract Award

DAL Data Accession List

DAOD Days after As-of-Date

DCDR Days after Critical Design Review

DI Data Item

DID Data Item Description

DMO Data Management Office

ECMS Electronic Contract Management System

ECP Engineering Change Proposal

EOM End of Month

ES Equipment Specialist

FCA Functional Configuration Audit

FQ Fiscal Quarter

FY Fiscal Year http Hyper Text Transport Protocol https Hyper Text Transport Protocol Secure

IAW In Accordance With

IPT Integrated Product Team

LOC Life of Contract, contract life shall be deemed to end upon date of delivery to the Government of the last item delivered hereunder.

LT Letter of Transmittal

MAC Months after Contract Award

MIP Material Improvement Program

MTHLY Monthly

N/A Not Applicable

NLT Not Later Than

OEM Original Equipment Manufacturer

ONE/R One Time - With Revisions

PCA Physical Configuration Audit

PDR Preliminary Design Review

PCO Procuring Contracting Officer

POC Point of Contact

PWS Performance Work Statement

QRTLY Quarterly

SCN Specification Change Notice

SOW Statement of Work

SRD System Requirements Document

STR Status Report

USAF United States Air Force

WEKLY Weekly

TRR Test Readiness Review

C-17 DISTRIBUTION MATRIX

DISTRIBUTION

ADDRESS EMAIL ADDRESS POC CDRL

AFLCMC/WLMA CDRL

DMO wralc.lth.cdrldmcm@us.af.mil TBD All CDRLs

PAPER COPY DELIVERY ADDRESSES

DISTRIBUTION

ADDRESS PHYSICAL ADDRESS POC CDRL

AFLCMC/LZPEM

ATTN: AFLCMC/LZPEM

285 Cochran Street Robins AFB, GA 31098-1669

TBD

A008 (DRAW)

A030 (EDT)

A031 (BOM)

AFLCMC/WLE, C-17

AFLCMC/WLMA

660 Eleventh Street Robins AFB, GA 31098-2428

TBD A005

ITEMIZED CDRL List A001 – A015

Data Item Requiring Office Authority/Title/Subtitle SOW Paragraph

A001 AFLCMC/WLMC

DI-AVCS-80700A/T

Computer Software Product End Items

C-17 TAWS

3.1

A002 AFLCMC/WLMC

DI-MGMT-81468/T

Contract Funds Status Report (CFSR)

C-17 TAWS

3.1

A003 AFLCMC/WLMC

DI-SESS-80639D

Engineering Change Proposal (ECP)

C-17 TAWS

3.2

A004 AFLCMC/WLMC

DI-SESS-80640D

Request for Variance (RFV)

C-17 TAWS

3.2

A005 AFLCMC/WLME

(C-17 Engineering)

DI-MISC-80508B/T

Technical Report – Study/Services

C-17 TAWS

3.1, 3.2, 3.3, 3.4

A006 AFLCMC/WLME

(C-17 Engineering)

DI-MGMT-81453B-T

Data Accession List (DAL)

C-17 TAWS

4.5.2

A007 AFLCMC/WLMC DI-IPSC-81433A/T

Software Requirements Specification (SRS)

C-17 TAWS

3.2, 3.3

A008 AFLCMC/WLMC DI-MISC-80508B/T

Technical Report – Study/Services

C-17 TAWS

3.3, 3.5, 4.5.2

A009 AFLCMC/WLMC DI-IPSC-81442A/T

Software Version Description (SVD)

C-17 TAWS

3.3

A010 AFLCMC/WLMC

DI-IPSC-81440A/T

Software Test Report (STR)

C-17 TAWS

3.4

A011 AFLCMC/WLMC

DI-MISC-80508B/T

Technical Report – Study/Services

C-17 TAWS

4.6

A012 AFLCMC/WLMC

DI-MGMT-81334D/T

Contract Work Breakdown Structure (CWBS)

C-17 TAWS

4.3

A013 AFLCMC/WLMC

DI-IPSC-81443A/T

Software User Manuals (SUM)

C-17 TAWS

3.3

A014 AFLCMC/WLMC

DI-MGMT-82135

Risk Management Framework (RMF) Security Authorization Package C-17

3.8.5

A015 AFLCMC/WLMC

DI-MGMT-81861A/T

Integrated Program Management Report (IPMR)

C-17 TAWS

4.2

CDRLs A001 – A015 (Following This Page)

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved 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 the burden, to the 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. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER AVCS

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A001

2. TITLE OF DATA ITEM

Computer Software Product End Items

3. SUBTITLE

C-17 TAWS

4. AUTHORITY (Data Acquisition Document No.)

DI-AVCS-80700A/T

5. CONTRACT REFERENCE

SOW Para 3.1

6. REQUIRING OFFICE

AFLCMC/WLMC

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ONE/R

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

Block 4: Contractor format is acceptable as long as the content, intent, and data required by DI-AVCS-80700A/T is satisfied.

Military Standards and Specifications are for guidance only. The contractor shall maintain the latest software releases at a Government designated location. To allow for the installation, building, and testing of the software, the Contractor shall deliver all of the following items for Interim (a.k.a. FQT) and Final releases.

1. Source code, including Interface definitions (e.g., IDL, WSDL, interops, etc)

2. For components with public interfaces to be used by other developers:

a. Programmers reference manual with examples for public interfaces

b. Class diagrams where applicable

c. XML Schema and Schematron files

d. Database schema definitions

e. Unified Modeling Language (UML) source as available

f. Dependency diagrams as available

3. Distribution package and source code of public domain tools used in the software

4. List of all software components with the following information:

a. Purpose and function

b. Interfaces provided

c. Language/version for each module

5. Items required to build the software, at a minimum:

a. List of commercial, public domain, and open source software (including code quality scanning tools(s), such as HP Fortify)required to create the build environment and the recommended order of installing these on the build machine

b. Products and source from list described in “5a.” not restricted by licensing

c. Build scripts (to include scripts related to code quality scanning tools)

d. Procedures to build from this source delivery (including recommended order of installing products to create the build environment)

e. Detailed instruction on setting up of build environment (e.g.

visual studio options, system path, code quality scanning tool(s) options, etc)

f. A snapshot of all the file directories required to build the software on a second machine (just prior to executing the script to compile and build the software, use common compression tools, e.g.

zip, rar, to create)

AFLCMC/WLMA

CDRL DMO 1 1 1

MEARS 1 1 1

15. TOTAL 2 2 2

G. PREPARED BY

AFLCMC/WLMBA, C-17 Logistics Manager

H. DATE I. APPROVED BY

AFLCMC/WLME, C-17 Data Manager

J. DATE

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 3 Pages

17. PRICE GROUP

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER AVCS

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

16. REMARKS (Continued)

6. Items required to install the software, at a minimum:

a. Installation scripts and procedures

b. Products and data required to install and run the application(s)

c. One version with debug “On” and one version with debug “Off.”

7. Items used to test the software and required to repeat the tests, at a minimum:

a. Description of unit tests which indicate the modules under test and the functional requirements tested (the test report/results should also be included)

b. Unit testing tools / drivers, their source code, build instructions and descriptions of how to install and use them and interpret results

c. Automated unit tests and associated items to run the tests (e.g. source code, data, stubs / drivers, templates)

d. Integration testing tools / drivers, their source code, build instructions and descriptions of how to install and use them and interpret results

e. List of code quality scanning tools used by the developer. Include the drivers, data files, tool settings, and installation instructions for the code quality scanning tools.

8. Items that comprise Software Developer’s Kit (SDK) type material, at a minimum:

a. Interface Design Description (IDD)

b. Software Programmer’s Guide

c. Security stubs or guidance to developers related to flexibility required to create new JMPS products that integrate with this product

d. Items created by the contractor during period of performance which help other developers simplify integration to this JMPS product

9. Items to facilitate maintenance

a. Source file history (the history of changes to the source code)

1. For Engineering releases, with DR fixes, the contractor shall deliver the products listed under 1, 5, 6 (debug version not required), and 8 (extensions to existing products).

2. Item 9 above shall be delivered with the final release only.

Block 7: The contractor shall submit a Provisional DD250 (Material Inspection and Receiving Report) with the interim release submittal and a Final DD250 with the Final release in accordance with the Inspection and Acceptance clause in Section E of the Delivery Order.

Block 8: The Government shall provide a notice of acceptability or unacceptability within 30 days of the submission. The Government shall not provide a notice of acceptability for Engineering or Beta releases.

Block 9: Documentation will be marked with Distribution Statement C and Destruction Notice, unless otherwise directed by the program manager.

Distribution Statement C: Distribution authorized to U.S. Government Agencies and their contractors;

Administrative/Operational Use; 05 June 2019. Other requests for this document shall refer to the C-17 AFLCMC/WLMBA, 235 Byron Street Suite 19A, Robins AFB, GA 31098.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Block 12 and 13: Engineering releases, Interim (a.k.a. FQT) and Final releases shall be delivered in accordance with the Government approved IMS with the following guidance:

a. Engineering and Final releases should be scheduled to allow for defect verification and feedback to the developer prior to the final release.

b. Interim releases shall be delivered within 30 days of completion of FQT

c. Final releases shall be submitted to the Government for acceptance upon satisfactory completion of software performance in MPE Operational Testing (OT). The full delivery shall include all updates which occurred between the interim delivery along with a description of all changes

Block 14: Submissions shall be via electronic media in a format acceptable to the Government.

No hardcopies of source code are required for submission

Interim release SW shall be delivered to the WR-ALC/WLMBA, CPIN Manager, 235 Byron St, Suite 19A, RAFB, GA 31098

DD FORM 1423-1, FEB 2001 Page 2 of 3 Pages

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER AVCS

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

16. REMARKS (Continued) Final versions to be sent to WR-ALC/WLMC and to The Boeing Company, Attn: Configuration Management, 4060 N Lakewood Blvd, Long Beach, CA 90808-1700

DD FORM 1423-1, FEB 2001 Page 3 of 3 Pages

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A002

2. TITLE OF DATA ITEM

Contract Funds Status Report (CFSR)

3. SUBTITLE

C-17 TAWS

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81468/T

5. CONTRACT REFERENCE

SOW Para 3.1

6. REQUIRING OFFICE

AFLCMC/WLMC

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

MTHLY

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

BLK 16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

Block 4: Supplemental instructions (Refer to DD FORM 1586)

a) Item 11 column a: Reporting shall be by each Contract Line Item Number (CLIN).

b) Item 11, column b: Enter appropriations, subhead, and project unit for each line item as specified on the contract appropriation data sheet e.g. 1791506/41AP/1050.

c) Item 12 rows a, b, and c Columns 2 through 9 shall include monthly projected amounts through the remainder of the contract.

d) In DD Form 1586, Block 15, Remarks, enter separately, if applicable, 1) the amount of profit/fee, overrun/under run, and the cost sharing ratio, and 2) reconcile variances between Row 12c, Total, and Row 13, Forecast of Billings, for all entered periods.

Block 7/8: On-Line electronic disposition will be provided by the Government in EVM CR.

Block 9: Distribution Statement C: Distribution authorized to U.S.

Government Agencies and their contractors; Administrative/Operational Use; 05 June 2019. Other requests for this document shall refer to the C-17 AFLCMC/WLMBA 235 Byron Street, Suite 19A, Robins AFB, GA 31098.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Block 11: As of Date for all submissions shall be coincident with the close of the associated accounting month.

Block 12: The first submission shall be NLT Twelve (12) days after the close of the first full accounting month after contract award.

Block 13: Subsequent submission shall be required NLT Twelve (12) days after the close of each accounting month, thereafter.

Block 14: Submissions shall be via electronic media in MS EXCEL format or other format acceptable to the Government.

MEARS 1

AFLCMC/WLMA

CDRL DMO 1

15. TOTAL 0 2 0

G. PREPARED BY

AFLCMC/WLMBA, C-17 Logistics Manager

H. DATE I. APPROVED BY

AFLCMC/WLME, C-17 Data Manager

J. DATE

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 1 Pages

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A005

2. TITLE OF DATA ITEM

Technical Report - Study/Services

3. SUBTITLE

C-17 TAWS

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B/T

5. CONTRACT REFERENCE

SOW Para 3.1, 3.2, 3.3, 3.4

6. REQUIRING OFFICE

AFLCMC/WLME

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

QTRLY

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

BLK 16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

Block 4:

Report should be in accordance with the attached Enterprise Measurement Template. The Enterprise Measurement Specification – Guide is available for additional metric reporting clarification.

Military Standards and Military Specification are for guidance only.

The Management Metric Report shall provide the Government the information used by the contractor to internally track, report, and manage Product development, integration, test, quality, function, and performance relative to the contractor processes/procedures and contractual Technical Requirements Documents, Capability Description Documents (CDDs), and System/Software Requirements Documents (S/SRDs).

The requirements herein, shall be flowed down to major (as defined in the Contractor’s Procurement System) first tier subcontractor(s).

The Prime Contractor shall incorporate Subcontractor SMRs in the Prime Contractor SMR, and include the Subcontractor SMRs as an attachment to the Prime Contractor SMR.

The Metric Report, as a minimum, shall include:

A. Software Size (planned vs. actual) B. Software Development Schedule C. Software Defects (tracking problem reports) D. Software Requirements Definition and Stability (adds/deletes/mods over time) E. Software Development Staffing (actual vs. planned; turnover) F. Software Progress (actual design/code/test vs. planned) G. Software Root Cause Analysis Metrics

Block 8:

Government will provide notice of acceptance/non-acceptance, with comments not more than Thirty (30) days after receipt of each submission.

Block 9: Distribution Statement C: Distribution authorized to U.S.

Government Agencies and their contractors; Administrative/Operational Use; 05 June 2019. Other requests for this document shall refer to the C-17 AFLCMC/WLMBA, 235 Byron Street, Suite 19A, Robins AFB, GA 31098.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Block 10: Note to DO IPT, this report is Monthly for DOs with a value of $25M and above, including priced options; Quarterly for less than $25M

Block 11: As Of Date for all submissions shall be coincident with the close of the associated accounting month.

MEARS 1

AFLCMC/WLMA

CDRL DMO 1

15. TOTAL 0 2 0

G. PREPARED BY

AFLCMC/WLMBA, C-17 Logistics Manager

H. DATE I. APPROVED BY

AFLCMC/WLME, C-17 Data Manager

J. DATE

18. ESTIMATED

TOTAL PRICE

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 2 Pages

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

16. REMARKS (Continued) Block 12: Date of first submission shall be Twelve (12) days after the close of the first full accounting month after contract award.

Block 13: Subsequent submissions Twelve (12) days after the close of the associated accounting month, thereafter.

Block 14: Submissions shall be via electronic media in a format acceptable to the Government.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER MGMT

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A006

2. TITLE OF DATA ITEM

Data Accession List (DAL)

3. SUBTITLE

C-17 TAWS

4. AUTHORITY (Data Acquisition Document No.)

DI-MGMT-81453B/T

5. CONTRACT REFERENCE

SOW Para 4.5.2

6. REQUIRING OFFICE

AFLCMC/WLME

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

QTRLY

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

N/A

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

Block 4: Contractor format is acceptable. Military Standards and Military Specification are for guidance only. All documents created during the course of software development shall be included on the DAL and made available to the Government upon request.

Block 9: Distribution Statement C: Distribution authorized to U.S.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Blk 12: First Submission due NLT 3 (three) full accounting periods DAC, coincident with associated CDRL submission

Blk 13: Quarterly, the contractor shall submit a delta DAL.

Annually and at the end of the contract, the contractor shall submit a complete DAL.

Blk 14: Submissions shall be via electronic media in a format acceptable to the Government.

MEARS 1

AFLCMC/WLMA

CDRL DMO 1

15. TOTAL 0 2 0

G. PREPARED BY

AFLCMC/WLMBA, C-17 Logistics Manager

H. DATE I. APPROVED BY

AFLCMC/WLME, C-17 Data Manager

J. DATE

18. ESTIMATED

TOTAL PRICE

Form Approved OMB No. 0704-0188

A. CONTRACT LINE ITEM NO. B. EXHIBIT

C. CATEGORY:

TDP TM OTHER IPSC

D. SYSTEM/ITEM

C-17 TAWS Tool and Database Sustainment

E. CONTRACT/PR NO.

TBD

F. CONTRACTOR

TBD

1. DATA ITEM NO.

A007

2. TITLE OF DATA ITEM

Software Requirements Specification (SRS)

3. SUBTITLE

C-17 TAWS

4. AUTHORITY (Data Acquisition Document No.)

DI-IPSC-81433A/T

5. CONTRACT REFERENCE

SOW Para 3.2, 3.3

6. REQUIRING OFFICE

AFLCMC/WLMC

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

ONE/R

12. DATE OF FIRST SUBMISSION

BLK 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

11. AS OF DATE

N/A

13. DATE OF SUBSEQUENT

SUBMISSION

BLK 16

Draft

Final

Reg Repro

16. REMARKS

Block 4: Use attached format for CDRL submission. No other format will be acceptable without prior Government approval.

Block 8: The Government will provide a notice of acceptability, or a notice of unacceptability with specific comments, not more than 30 days after receipt of each submission.

Block 9: Distribution Statement C: Distribution authorized to U.S.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Block 12: Draft submittal due 30 days prior to SRR.

Block 13: Final due 30 days prior to CDR

Block 14: Submissions shall be via electronic media in a format acceptable to the Government.

MEARS 1 1

AFLCMC/WLMA

CDRL DMO 1 1

15. TOTAL 2 2 0

G. PREPARED BY

AFLCMC/WLMBA, C-17 Logistics Manager

H. DATE I. APPROVED BY

AFLCMC/WLME, C-17 Data Manager

J. DATE

18. ESTIMATED

TOTAL PRICE

Mission Planning Enterprise Measurement Specifications

Version 4.0 Date: l1/28/2012

Configuration Identifier: 914-01-001-4.0

Kevin E. Porter Author Kevin.E.Porter@saic.com mailto:Kevin.E.Porter@saic.com

Enterprise Measurement Specification v4.0

CIN: 914-01-001

2 | P a g e

Record of Change

Version Date Pages Affected Type of Change

1.0 All Initial

2.0 5/5/2011 Page 1 and 2 Update the title page, contents, and provided additional clarifications within the measures

3.0

PRE-CCB

DRAFT

09/30/2011 All Enhancements to existing specifications

Added Agile/Scrum Development metrics

3.3 10/17/11 7,10,11,13, 20,22,24,28,31 (Change title to <NAME> format and not specific programs)

15(title)

Updated to reflect comments prior to CCB

3.4 10/18/11 Incorporate comments from CCB Reviewers

3.5 8/09/12 All Incorporate comments from lessons learned from implementing v3.4

3 | P a g e

Table of Contents

Measurement Specification Overview

Table Overview

Waterfall Development Specifications

Table W1-1 - Development Schedule

Table W1-2 - Development Progress (Design, Coding, and Testing)

Agile /Scrum Development Specifications

Table A1-1 - Release Cumulative Flow

Table A1-2 - Release Burn-up / S- Curve

Table A1-3 - Velocity

Table A1-4 - Test Coverage

Common Development Specifications

Table C1-1 - Requirements Definition and Stability (SSS)

Table C1-2 - Requirements Definition and Stability (SRS)

Table C1-3 - Staffing

Table C1-4 - Software Size

Table C1-5 - Software Defects

4 | P a g e

Measurement Specification Overview

The Enterprise Measurement Specification addresses Mission Planning informational needs and the USAF ‘Revitalizing the

Software Aspects of Systems Engineering’ memorandum. The Enterprise Measurement Specification provides the structure for the Mission Planning measurement practitioners providing information on data collection and analysis. The metric program has been developed using the Program Management Constraint as the structure to ensure a robust examination of execution of each program. This structure is developed according to the following four attributes:

1. Scope

2. Time (Schedule)

3. Cost (Staffing and ODCs)

4. Quality (IVV&E)

As referenced in the Mission Planning Enterprise Measurement and Reporting Plan (E-MP), the purpose of collecting measures is to provide decision makers with information to make critical decisions, aiding them in the ability to meet organizational and program quality and process performance objectives. This specification will satisfy the decision maker’s needs regardless of whether the program follows Agile/Scrum or Waterfall development methodologies. The table below identifies each required measure to report based on the specified lifecycle methodology:

Information Category Waterfall Development

Measures

Agile Development

Measures

Common Development

Measures

Product Size and Stability

(SCOPE)

• Requirements

Definition and

Stability (SSS)

• Requirements

Definition and

Stability (SRS)

Schedule and Progress

(TIME)

• Software Development

Schedule

• Software Progress

• Release Cumulative

Flow

• Release Burn up / S-

Curve

• Velocity

Resources and Cost

(COST)

• Staffing

Product Quality

(QUALITY)

• Test Coverage • Software Defects

Product Size and Stability

• Software Size

5 | P a g e

Table Overview

The remaining content of this document is comprised of a series of tables that describes the metrics required in the CDRL

A007 documents. These tables are allocated to three sections; Waterfall Development Specifications, Agile/Scrum

Development Specifications, Common Development Specifications. The structure for these metrics is modeled after the

“Measurement Information Model” from the Practical Software Measurement text (reference: publisher Addison-Wesley

Professional; 2001) (ISO/IEC 15939 standard) and used substantially throughout the measurement community. Each table within these sections has 9 parts as described below:

1. Information Need o States why this measurement is needed and what the user needs to know in order to make informed decisions.

2. Measurable Concept o State what the logical grouping of information needs are and the supporting text from the USAF

Memorandum “Revitalizing the Software Aspects of Systems Engineering”

3. Entities and Attributes o State where the entities are derived from in the process or product elements of a project such as project tasks, plans/estimates, resources, and deliverables. The attributes used of the entities are provided that are the property or characteristic of an entity that is quantified to obtain a base measure.

4. Base Measure Specification o States what the description is of the attributes which are to be collected and measured. This part of the specification provides details for the following measurement descriptions: measurement method, type of method, scale, type of scale, and unit of measure.

5. Derived Measure Specification o States a measure which is derived as a function of two or more measures. This is optional and may be useful for further analysis.

6. Indicator Specification o Provides a sample of the measurement charts to be provided. A separate excel-based template is available for the detailed indicators.

7. Data Collection Procedure (for each Base Measure) o State what the details are for the following items for each base measure: frequency of data reporting, responsible individual, phase or activity in which data is collected, tools in data collection, verification and validation, and the repository for the data.

8. Data Analysis Procedure (for each Indicator) o States the descriptive sections for the indicators identified in the ‘Data Collection Procedure’ although these details support each indicator as opposed to each base measure.

9. Additional information o Provides any additional guidance on variations of the measure.

As an organization begins their development, they self-identify which development methodology they will be using. The following table identifies which measurement tables apply to their development and are required in their CDRL A007.

Waterfall Development Agile/Scrum Development

Table C1-1 - Requirements Definition and Stability (SSS)

Table C1-2 - Requirements Definition and Stability

(SRS)

Table W1-1 - Development Schedule

Table W1-2 - Development Progress

Table C1-3 - Staffing

Table C1-4 - Software Size

Table C1-5 - Software Defects

Table C1-1 - Requirements Definition and Stability (SSS)

Table C1-2 - Requirements Definition and Stability

(SRS)

Table A1-1 - Release Cumulative Flow

Table A1-2 - Release Burn-up / S- Curve

Table A1-3 - Velocity

Table A1-4 – Test Coverage

Table C1-3 - Staffing

Table C1-4 - Software Size

Table C1-5 - Software Defects

6 | P a g e

7 | P a g e

Waterfall Development Specifications

Table W1-1 - Development Schedule

Information Need Description

Information Need Are projects within the enterprise meeting their plan?

Information Category Schedule and Progress

Measurable Concept

Milestone Performance

Schedule Indicator

“Revitalizing the

Software Aspects of

Systems Engineering”

USAF Memorandum

Guidance [Sept 20, 2004]

Software schedules should be planned to at least the function or CSCI level for each spiral.

Increment, or block, and should be re-evaluated at major program milestones or whenever requirements are changed. Planned and actual schedules should be tracked continuously from the start through the completion of development. Software schedules should provide insight into the start and completion dates as well as progress on detailed activities associated with requirements, design, coding, integration, testing, and delivery of software products.

Software development schedule durations are measured in months. Like effort, estimated software development schedules are determined primarily from software size, but also depend on other factors such as developer team capability, tool capability, requirements stability, complexity, required reliability, and software testing methods and tools.

Late or poor quality deliveries of low level software products are indicators of overall program schedule risk. Schedules should be examined for excessive parallel activities that are not realistic when resources such as staff or integration labs are considered, excessive overlap of activities where dependences exist, or inconsistent detail or duration with similar tasks.

Entities and Attributes

Relevant Entities Schedule

Attributes Tasks

Base Measure Specification

Base Measures

1. Planned Task Duration (in days)

2. Actual Task Duration (in days)

Measurement Methods

1. Subtract the Planned start date from the end date for tasks per development phase

2. Subtract the Actual start date from the end date for tasks per development phase

Type of Method

1. Subjective

2. Objective

Scale integer from one to infinity

Unit of Measurement Days of duration (day = 8 hours)

Derived Measure Specification

Derived Measure None

Measurement Function N/A

8 | P a g e

Analysis

Model

This measure…

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.