Attachment 1_ CDRLs-DIDs.pdf

Title of Deliverable CDRL Number Corresponding DID Number

Due Date SOW Section

Program Management Plan

A001 STDO-PM-001 30 DAC 3.1

Program Status Report

A002 OST-PM-002 30 DAC 3.1.3

Document Library Index

A003 NA 30 DAC 3.1.4

Contract Funds Status Report

A004 STDO-PM-005 30 DAC 3.3

Meeting Minutes A006 FAA-PM-006 10 Days After Event

3.7

Post Award Meeting Minutes

A007 NA 10 Days After Event

3.7.1

Test and Evaluation Concept Briefing

A100 OST-TE-002 30 DAC 4.2

Data Accession List

A110 NA 60 DAC 10.0

Emerging Results Briefing

A121 NA As Directed by

SOW

7.0

System Evaluation Report

A122 SEIPT-TE-004 30 Days After Completion of Test

7.0

Quick Look Report A123 NA As Directed by

SOW

7.0

Test and Evaluation Plan

A130 OST-TE-001 30 DAC 4.4

Project Plan A150 DID-A150 30 DAC 3.1.5

Quality Management System (QMS)

E308 DI-E-008a With Proposal 3.6

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 2 of 2

A. Contract line Item No.

B. Exhibit

A

C. Category (Check appropriate one)

TDP TM Other

D. System/Item

Test and Evaluation Support

Services (TESS)

E. Contract/PR No.

F. Contractor

1. Data Item No.

A001

2. Title of Data Item

Program Management Plan (PMP)

3. Subtitle

4. Authority

STDO-PM-001

5. Contact Reference

SOW - paragraph 3.1

6. Requiring Office

TSA/OST

7. DD 250 Req‟d 8. APP Code 9. Distribution Statement Required 10. Frequency 11. As of Date (AOD)

LT A R/ASR

12. Date of First

Submission See Block 14

13. Date of Subsequent

Submission

15. Distribution

See Block 14

14. REMARKS: a. b. Draft c. Final Copies

Addressee Copies Reg. Repro

Block 8

If a submittal is disapproved, the data item shall be revised and re-submitted within 5 working days.

Block 10

Once approved by government, proposed changes shall be submitted

20 working days prior to required implementation date.

Block 12

30 DAC.

Block 15

The PMP shall be submitted in electronic form. The "Reg" electronic version shall be compatible with the Windows Office suite and a PDF version shall be provided as the "Repro" copy. A PDF version of the letter of transmittal (see Block 7 - LT) signed by the contractor's authorized approving official shall be provided.

COR

16. Total 2 1

G. Prepared By: H. Date I. Approved By J. Date

OST Approved

17. Price Group 18. Estimated Total Price

INSTRUCTIONS FOR COMPLETING FAA Template No. 59 (6/98) A. Contract Line Item No.. Contract Line Item Number (CLIN) associated with this Contract Data Requirements List (CDRL).

B. Exhibit. Exhibit identifier for this CDRL item.

C. Category. TDP, TM, or Other.

D. System/Item. System, item, project designator or name, or title of services being acquired that the data will support.

E. Contract/PR No. Procurement Instrument Identification Number (PIIN) (i.e., the contract number, the Purchase Request (PR) number, the screening Information Request (SIR) number, or other appropriate designator.

F. Contractor. Contractor’s name.

G. Prepared by. Preparer’s organization responsible for preparing the CDRL.

H. Date. Date the form was prepared.

I. Approved by. Office responsible for approving the CDRL. The approving official’s signature appears on the last page of exhibit.

J. Date. The date the CDRL was approved.

1. Data Item No. The 4-character Exhibit Line Item Number (ELIN). The first position consists of the exhibit identifier and the remaining positions are assigned sequentially.

2. Title of Data Item. The title of the Data Item Description (DID) cited in item 4.

3. Subtitle. Further identification of the data item to supplement the title, if required.

4. Authority (Data Acquisition Document No.) DID identification number where detailed preparation instructions are provided.

5. Contract Reference. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

6. Requiring Office. The technical office having responsibility for ensuring the technical adequacy of the data.

7. DD 250 Required.

8. APP Code. Identification, by entry of an “A,” of a requirement for advance written approval prior to final distribution of an item of data. An “A” in this item indicates that one or more draft submittals are required. Item 14 will show length of turn-around time for the contractor to resubmit the data after

Government approval/disapproval has been issued.

9. Distribution Statement Required.

10. Frequency. The frequency of data submittal. Entries in this item are explained in Table 1. If the data is of a recurring type, it is to be submitted at the end of the reporting period established in this item unless otherwise indicated in item 14.

Table 1. Data Submittal Frequency Codes

CODE FREQUENCY CODE FREQUENCY

ANNLY Annually ASGEN As generated

ASREQ As required BI-MO Every two months

BI-WE Every two weeks CP/RQ Change pages as required

DAILY Daily DFDEL Deferred delivery

MTHLY Monthly ONE/R One time with revisions

OTIME One time (does not include draft submissions QRTLY Quarterly

R/ASR Revisions as required SEMIA Every six months

WEKLY Weekly “N”TIME Multiple separate submittals (2time, 3time, etc.)

See Item #14 Requirement is described in item #14. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in item #14.

11. As of Date. Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered to indicate the number of calendar days prior to the end of the reporting period, established in item 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at 15 days before the end of the month, quarter, or year, depending upon the frequency established in item 10; a “0 or blank” would place the “as of” date at the end of each month, quarter, etc.

12. Date of First Submission. Due date for initial data submission. This is normally the postage date or date the data is delivered to the Contracting Officer or keyed to a specific event or milestone, using a code from Table 2.

Table 2. Data Submission Codes

Code Definition Code Definition

ASGEN As generated ASREQ As required

DFDEL Deferred delivery “N”DAC Days after contract award

“N”DACM Days after contract modification “N”DARP Days after reporting period

“N”DARC Days after receipt of comments “N”DTC Days after test completion

NLT No later than EOC End of contract

EOM End of month EOQ End of quarter

See item #14 Use to indicate requirement is described in item 14. Used in lieu of other codes where such are inadequate to define requirement or used in addition to other codes when amplification is included in item 14.

The “N” is assigned a value indicating the number of days, e.g., 30 DAC

13. Date of Subsequent Submission. Due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 2.

14. Remarks. Contains all pertinent information not specified elsewhere and any amplification of other items on this format (e.g., DID tailoring, approva criteria and authority, inspection and acceptance clarification, distributions statements, specific submission instructions, explanation of reproducible copy and delivery requirements, alternative medium for delivery of the data item, etc.)

15. Distribution. Addressees and the number of draft and final copies (regular or reproducible) to be provided to each. FAA facility designator and/or office symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. When reproducible copies (e.g., magnetic diskettes/tape, vellum, negative, etc.) are required, an explanation will be provided in item 14. If deferred delivery is required, amplification will be given in item 14.

16. Total. Total number of draft and final (regular/reproducible) copies required.

17. Price Group. Not used. 18. Estimated Total Price. Not used.

DATA ITEM DESCRIPTION

1. TITLE 2. IDENTIFICATION NUMBER

Program Management Plan (PMP) STDO-PM-001

3. DESCRIPTION/PURPOSE

3.1 The Program Management Plan (PMP) shall describe the Contractor's management organization to include interrelationships between the Contractor, major subcontractor(s) and the contracting activity.

3.2 The PMP will be an all inclusive management plan that provides details of the specific techniques, tasks, and procedures to be used for monitoring contract management and performance, configuration control, data management, production management, and cost control.

3.3 The PMP documents the Contract Work Breakdown Structure (CWBS) and its extension by the Contractor.

3.4 The PMP provides the contracting activity a basis for reviewing and evaluating of performance, and for determining contractual compliance.

4. APPROVAL DATE (YYMMDD) 5. OFFICE OF PRIMARY RESPONSIBILITY (OPR) 6a. DTC APPLICABLE 6b. GIDEP APPLICABLE

7. APPLICATION/INTERRELATIONSHIP

7.1 This DID shall be the basis for the Contractor's management approach to program technical, schedule, and cost control.

7.2 The PMP shall be consistent with data products generated for the direction, coordination, and control of system engineering, interface management, configuration management, quality assurance, and production management.

8. APPROVAL LIMITATION 9a. REFERENCES 9b. AMSC NUMBER

10. Preparation Instructions

10.1 CONTENT. The Program Management Plan shall describe the Contractor‟s organization, program planning and scheduling tools and techniques, program tracking and control methods, resource management, production planning and management, and subcontractor management methods.

10.2 FORMAT. The Program Management Plan (PMP) shall be prepared in the Contractor's format and include, as a minimum, the following sections:

10.3 INTRODUCTION. This section shall be divided into two sections describing the purpose and scope of this document.

11. DISTRIBUTION STATEMENT

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

DATA ITEM DESCRIPTION STDO-PM-001

10. Preparation Instructions (Continued)

10.3.1 Purpose. This paragraph shall describe the purpose of the PMP in terms of its relationship to the management of the project, and performing the contract tasks outlined in the SOW.

10.3.2 Scope. This section shall contain programmatic and technical background on the system; an overview of the Contractor‟s approach to program technical, schedule, and cost control; authority of the program manager; and the relationship of the PMP to other programmatic policies, procedures, and planning documents; and methods of incorporating changes into the PMP

10.4 PROGRAM MANAGEMENT. This section shall provide information on the Contractor‟s management organization, internal management policies and procedures, an overall integrated program schedule, relationships with Government personnel and agencies, and roles and responsibilities of management entities within the organization.

10.4.1 Management Organization. Present a company organizational chart(s) and sufficient supplemental narrative to fully describe all organizational levels, plans and activities.

This chart shall be hierarchical in nature and should delineate clearly all major area responsibilities and management positions. Provide a chart of the program organization to be used in performance of the contract. Provide a narrative describing how the Contractor shall fully integrate the management of all elements of the project.

Identify key technical and management personnel who will be assigned to the project.

If the project includes subcontractors, provide organizational information about the subcontractor and include subcontractor organizational elements in the project organization chart.

10.4.2 Roles and Responsibilities. Discuss the authority of all responsible management positions identified by the organizational description. This description shall include the role of the project manager to direct, control, and commit resources to adequately fulfill their responsibilities.

10.4.3 Policies and Procedures. Describe internal policies and procedures to be used in managing the contract.

10.4.4 Relationships. Describe the working relationships the Contractor will establish with the

STDO.

10.4.5 Subcontract Management. Describe the approach to managing subcontractor activities. Include in the approach the organizational relationship maintained between the prime and subcontractors and methods of requirement flow-down and activity progress reporting back to the prime Contractor. Describe subcontractor and supplier rating systems used to select subcontractors and describe the approach to maintaining quality from products produced by subcontractors.

10.5 CONTRACT WORK BREAKDOWN STRUCTURE. The PMP shall include the CWBS.

The complete work breakdown structure (WBS) will serve as a basis for program and technical planning, scheduling, cost estimating, resource allocations, performance management, configuration management, and status reporting. The CWBS shall identify all subcontracted elements or tasks and shall include an index and dictionary.

10.5.1 CWBS Index. The CWBS shall contain the data elements listed below:

Line number for each CWBS sequential starting with 1.

Title of the CWBS element (using the specific name or nomenclature, when applicable), intended to reflect the level. Level 1 is the total contract. Levels 2, 3, etc.

are successively lower levels of the program.

CWBS code.

- Contract line item(s) associated with the CWBS element,

- Statement of work (SOW) paragraph numbers(s).

10.5.2 CWBS Dictionary. The CWBS dictionary shall describe the effort and tasks associated with every CWBS element. Provide a complete description of the technical and cost content of each CWBS element. The definition shall describe the efforts, tasks, tests, components, etc., that are included in the CWBS element by the Contractor.

10.6 SCHEDULE. Present a baseline schedule and processes for control of the schedule.

10.6.1 Baseline Schedule. Present a Baseline Master Integrated Project Schedule (BMIPS) that shall include all formal reviews and audits, all key programmatic and technical events, and the preliminary and final submission of all documentation identified in the Contract Data Requirements Lists (CDRLs). Include developmental and production processes discussed in the plan. The schedule shall show task dependencies and interrelationships and shall be tied to the WBS and CWBS. Schedules shall be presented in summary, intermediate, and detailed levels tied to CWBS work elements.

10.6.2 Summary master schedules. A graphical display of top-level program activities and key milestones that depict major work activities in an integrated fashion at the summary level of the CWBS.

10.6.3 Intermediate schedules. A graphical display of top-level program activities and key milestones that depict major work activities in a major CWBS element.

10.6.4 Detailed schedules. A graphical display of detailed activities and milestones that depict work activities in a particular CWBS element.

10.6.5 Schedule Management. Provide a detailed description of how the Contractor will implement a fully integrated, defined, planning and control system. The description shall include discussion of interrelationship of tasks, and tracking criticality of tasks. If subcontractor(s) are used, similar information shall be presented and shall include a discussion on how Contractor and subcontractor schedules shall be integrated and updated.

10.7 RESOURCE PLANNING. Provide a detailed description of how the Contractor will allocate and plan resources to meet the delivery requirements of the project. Discuss any resource planning tools used for this purpose.

10.8 METRICS. Describe the management indicators (metrics) that will be used to track contract performance and contract work breakdown structure (CWBS) activities throughout the contract life cycle. Include description of contract metrics used to monitor cost and schedule progress.

10.9 RISK MANAGEMENT. Describe the internal approach and method for the identification, assessment, and mitigation of program risks. This approach should include provision for identifying risk areas, assessing risk factors, assigning appropriate resources to reduce risk factors, identifying and analyzing alternative actions available, identifying the most promising alternatives, and planning for implementation of risk reduction. Document the internal risk identification and reduction procedure in a risk reduction action feedback flow diagram. Identify and assess each possible area of risk to the program, applying the internal risk reduction procedure. Describe your procedures to develop a plan of action to mitigate risk when management indicators (metrics) show a deviation of 10% or greater between planned and actual indicators.

10.10 DATA MANAGEMENT. Describe the organization, procedures, and tools to be used to ensure that all data deliverables required by the contract are made in a timely manner. Identify the individual responsible for integrating and maintaining the total data management effort. This effort shall involve monitoring, reporting, status accounting, and cross matrixing (e.g., Government change requirements versus implemented changes) of all changes to, additions of, or deletions of CDRL contents.

The Contractor's procedures for controlling the generation, receipt, approval, storage, and delivery of subcontractor data as well as its inclusion in status accounting shall be also be described.

10.11 CONFIGURATION MANAGEMENT PLAN. This section shall describe the Contractor‟s configuration management (CM) Plan, how the contractor‟s CM program is organized, how it will be conducted, and the methods, procedures and controls used to assure effective configuration, identification, change control, status accounting, and audits of the total configuration, including hardware, software and firmware.

10.11.1 Configuration Management Phasing And Milestones. This section shall describe and graphically portray the sequence of events and milestones for implementation of CM in phase with major program milestones and events, including:

a. Release and submittal of configuration documentation in relation to program events (e.g., technical reviews);

b. Establishment of internal developmental configuration and contractual baselines;

c. Implementation of internal and Government configuration control;

d. Establishment of configuration control boards;

e. Implementation of a status accounting information system and provision of reports/or access to the status accounting information; and

f. Conduct of configuration audits.

10.11.2 Configuration Identification. This section shall describe the Contractor's procedures for meeting the requirements of SOW paragraph 2.6, including:

a. Selection of CIs;

b. Establishment and management of developmental configuration including document, drawing and software development libraries and corrective action process;

c. Establishment of contract baselines, definition of the configuration documentation required for each and graphic illustration of configuration documentation relationships;

d. Engineering release and correlation of manufactured products; and

e. Assignment and application of configuration identifiers including document numbers, nomenclature, serial numbers and part number to hardware; and software identifiers to software and firmware.

10.11.3 Configuration Control. This section shall describe the Contractor's procedures for meeting the requirements of SOW paragraph 2.6, including:

a. Functions, responsibility, and authority of configuration control boards;

b. Classification of changes, and the level of authority for change approval/concurrence;

c. Processing of Class I Engineering Change Proposals (ECPs) and Value Engineering Change Proposals (VECPs);

d. Processing of Class II ECPs;

e. Processing of Requests for Deviations and Waivers;

f. Processing of Specification Change Notices (SCNs); and

g. Processing of Notices of Revision (NORs)

10.11.4 Configuration Status Accounting. This section shall describe the Contractor's procedures including:

a. The Contractor‟s methods for collecting, recording, processing and maintaining data necessary to provide contractual status accounting information via reports and/or data base access;

b. Description of reports/information system content related to, as applicable:

- Identification of current approved configuration documentation and configuration identifiers associated with each CI;

- Status of proposed engineering changes from initiation to implementation;

- Results of configuration audits; status and disposition of discrepancies;

- Status of requests for critical and major deviations and waivers;

- Traceability of changes from baseline documentation of each CI; and

- Effectively and installation status of configuration changes to all CIs at all locations.

c. Methods of accessing the accounting information systems and/or frequency of reporting and distribution.

d. Description of the tool used to accomplish status accounting.

10.11.5 Configuration Audits. This section shall describe the Contractor's approach to meeting the requirements of SOW paragraph 2.6, including: plans, procedures, documentation, and schedules for functional and physical configuration audits; and format for reporting results of in-process configuration audits.

10.12 QUALITY CONTROL, PERFORMANCE EVALUATION, AND CONTRACTUAL

COMPLIANCE. This section shall discuss Contractor and major subcontractor(s) methods and concepts for continuous quality control, performance evaluation, and contractual compliance.

10.12.1 Special Boards, Teams, and Working Groups. Discuss the purpose and responsibilities of all special boards, teams, or working groups to be used by the Contractor to control technical or managerial performance.

10.12.2 Reviews and Reporting. Describe plans for all formal and informal reviews and reporting to the Government.

10.12.3 Systemic Improvement. Describe the approach to systemic improvement of products.

Include in the discussion the approach to supplying quality products and making continuous improvement to critical processes controlled by the organization. Describe the tools and techniques that are used or planned for use on this contract. Include any discussion of relevant experience in the area of systemic improvement.

10.13 PRODUCTION MANAGEMENT. This section shall discuss Contractor and major subcontractor(s) methods and concepts for employing facilities, tooling, and manpower resources to produce the system/equipment.

10.13.1 Manufacturing Methods and Production Flow. Provide a production flow utilizing a goes-into chart, tree chart or equivalent to detail the process for manufacturing and assembly in terms of key operations or assembly points showing individual and total lead times from the procurement of raw material to delivery of the end item.

10.13.2 Make or Buy. This section shall identify each item and rationale for all major make/buy decisions and identify single or sole source suppliers with a backup plan, long lead materials, any critical materials and vendor control.

10.13.3 Capability and Capacity. This section shall describe the data and information used to determine the Contractor and subcontractor(s) capability and capacity to meet schedule requirements. The Contractor shall provide data indicating ability to meet the production rate and quantity for the system. Manufacturing risks and the systems used to track suppliers progress and to detect/correct potential delivery problems shall also be addressed. Provide a list of all subcontractors and major vendors indicating the services/materials to be supplied by each.

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 10 of 2

Services

A002

2. Title of Data Item

Program Status Report

3. Subtitle

4. Authority

OST-PM-002

5. Contact Reference

SOW - paragraph 3.1

6. Requiring Office

TSA/OST

7. DD 250 Req‟d 8. APP Code 9. Distribution Statement Required 10. Frequency 11. As of Date (AOD)

LT NA MTHLY 0

12. Date of First

Submission See Block 14

13. Date of Subsequent

Submission

14. REMARKS: a. b. Draft c. Final Copies

Addressee Copies Reg. Repro

Block 12

30 DAC

Block 13

20th of calendar month. If 20th falls on a non-workday, due next contractor work day.

Block 15

Shall be submitted in paper form with the cover page signed by the contractor's authorized approving official.

The PSR shall be submitted in electronic form. The "Reg" electronic version shall be compatible with the Windows Office

COTR

G. Prepared By: H. Date I. Approved By J. Date

OST OST Approved

A. Contract Line Item No.. Contract Line Item Number (CLIN) associated with this Contract Data Requirements List (CDRL).

B. Exhibit. Exhibit identifier for this CDRL item.

C. Category. TDP, TM, or Other.

D. System/Item. System, item, project designator or name, or title of services being acquired that the data will support.

E. Contract/PR No. Procurement Instrument Identification Number (PIIN) (i.e., the contract number, the Purchase Request (PR) number, the screening

Information Request (SIR) number, or other appropriate designator.

F. Contractor. Contractor’s name.

G. Prepared by. Preparer’s organization responsible for preparing the CDRL.

H. Date. Date the form was prepared.

I. Approved by. Office responsible for approving the CDRL. The approving official’s signature appears on the last page of exhibit.

J. Date. The date the CDRL was approved.

1. Data Item No. The 4-character Exhibit Line Item Number (ELIN). The first position consists of the exhibit identifier and the remaining positions are assigned sequentially.

2. Title of Data Item. The title of the Data Item Description (DID) cited in item 4.

3. Subtitle. Further identification of the data item to supplement the title, if required.

4. Authority (Data Acquisition Document No.) DID identification number where detailed preparation instructions are provided.

5. Contract Reference. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

6. Requiring Office. The technical office having responsibility for ensuring the technical adequacy of the data.

7. DD 250 Required.

8. APP Code. Identification, by entry of an “A,” of a requirement for advance written approval prior to final distribution of an item of data. An “A” in this item indicates that one or more draft submittals are required. Item 14 will show length of turn-around time for the contractor to resubmit the data after Government approval/disapproval has been issued.

9. Distribution Statement Required.

10. Frequency. The frequency of data submittal. Entries in this item are explained in Table 1. If the data is of a recurring type, it is to be submitted at the end of the reporting period established in this item unless otherwise indicated in item 14.

Table 1. Data Submittal Frequency Codes

CODE FREQUENCY CODE FREQUENCY

ANNLY Annually ASGEN As generated

ASREQ As required BI-MO Every two months

BI-WE Every two weeks CP/RQ Change pages as required

DAILY Daily DFDEL Deferred delivery

MTHLY Monthly ONE/R One time with revisions

OTIME One time (does not include draft submissions QRTLY Quarterly

R/ASR Revisions as required SEMIA Every six months

WEKLY Weekly “N”TIME Multiple separate submittals (2time, 3time, etc.)

See Item #14 Requirement is described in item #14. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in item #14.

11. As of Date. Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered to indicate the number of calendar days prior to the end of the reporting period, established in item 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at

15 days before the end of the month, quarter, or year, depending upon the frequency established in item 10; a “0 or blank” would place the “as of” date at the end of each month, quarter, etc.

12. Date of First Submission. Due date for initial data submission. This is normally the postage date or date the data is delivered to the Contracting Officer or keyed to a specific event or milestone, using a code from Table 2.

Table 2. Data Submission Codes

Code Definition Code Definition

ASGEN As generated ASREQ As required

DFDEL Deferred delivery “N”DAC Days after contract award

“N”DACM Days after contract modification “N”DARP Days after reporting period

“N”DARC Days after receipt of comments “N”DTC Days after test completion

NLT No later than EOC End of contract

EOM End of month EOQ End of quarter

See item #14 Use to indicate requirement is described in item 14. Used in lieu of other codes where such are inadequate to define requirement or used in addition to other codes when amplification is included in item 14.

The “N” is assigned a value indicating the number of days, e.g., 30 DAC

13. Date of Subsequent Submission. Due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 2.

14. Remarks. Contains all pertinent information not specified elsewhere and any amplification of other items on this format (e.g., DID tailoring, approva criteria and authority, inspection and acceptance clarification, distributions statements, specific submission instructions, explanation of reproducible copy and delivery requirements, alternative medium for delivery of the data item, etc.)

15. Distribution. Addressees and the number of draft and final copies (regular or reproducible) to be provided to each. TSA facility designator and/or office symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. When reproducible copies (e.g., magnetic diskettes/tape, vellum, negative, etc.) are required, an explanation will be provided in item 14. If deferred delivery is required, amplification will be given in item 14.

Program Status Report (PSR) OST-PM-002

3. DESCRIPTION/PURPOSE

The Program Status Report shall include contractor data for costs, schedule, technical, and status of deliverables. Problems/risks in the contractor's functional areas shall be identified and the resolution/mitigation efforts described.

4. APPROVAL DATE (YYMMDD) 5. OFFICE OF PRIMARY RESPONSIBILITY (OPR) 6a. DTC APPLICABLE 6b. GIDEP APPLICABLE

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

10. Preparation Instructions:

CONTENT. The Contractor shall report their progress in a monthly PSR. The PSR will address cost, schedule, performance, deliverable status, risks, work performed, problem encounters, pending issues and work planned for the next period.

FORMAT. The Program Status Report shall be submitted to the Government in paper form with the cover page signed by the contractor's authorized approving official. An electronic version of the paper submittal shall also be submitted in MS Word format.

APPROVAL. The Contractor shall submit the monthly PSR to the Government for their review.

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 13 of 2

Technical Engineering and

Management Support Services

A003

2. Title of Data Item

Document Library Index (DLI)

3. Subtitle

4. Authority

See Block 14 for content requirements

5. Contact Reference

SOW - paragraph 3.1.4

6. Requiring Office

TSA/STDO

7. DD 250 Req‟d 8. APP Code 9. Distribution Statement Required 10. Frequency 11. As of Date (AOD)

LT MTHLY 0

12. Date of First

Submission

30 DAC

13. Date of Subsequent

Submission

10 DARP

Block 4

The Document Library Index (DLI) shall include a list of documents contained in the digital Program Document Library.

Block 15

The DLI shall be submitted in electronic form with the cover page signed by the contractor's authorized approving official. The "Reg" electronic version shall be compatible with the Windows Office suite.

A PDF version of the letter of transmittal (see Block 7 - LT) signed by the contractor's authorized approving official shall be provided.

G. Prepared By: H. Date I. Approved By J. Date

A. Contract Line Item No.. Contract Line Item Number (CLIN) associated with this Contract Data Requirements List (CDRL).

B. Exhibit. Exhibit identifier for this CDRL item.

C. Category. TDP, TM, or Other.

D. System/Item. System, item, project designator or name, or title of services being acquired that the data will support.

E. Contract/PR No. Procurement Instrument Identification Number (PIIN) (i.e., the contract number, the Purchase Request (PR) number, the screening

Information Request (SIR) number, or other appropriate designator.

F. Contractor. Contractor’s name.

G. Prepared by. Preparer’s organization responsible for preparing the CDRL.

H. Date. Date the form was prepared.

I. Approved by. Office responsible for approving the CDRL. The approving official’s signature appears on the last page of exhibit.

J. Date. The date the CDRL was approved.

1. Data Item No. The 4-character Exhibit Line Item Number (ELIN). The first position consists of the exhibit identifier and the remaining positions are assigned sequentially.

2. Title of Data Item. The title of the Data Item Description (DID) cited in item 4.

3. Subtitle. Further identification of the data item to supplement the title, if required.

4. Authority (Data Acquisition Document No.) DID identification number where detailed preparation instructions are provided.

5. Contract Reference. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

6. Requiring Office. The technical office having responsibility for ensuring the technical adequacy of the data.

7. DD 250 Required.

8. APP Code. Identification, by entry of an “A,” of a requirement for advance written approval prior to final distribution of an item of data. An “A” in this item indicates that one or more draft submittals are required. Item 14 will show length of turn-around time for the contractor to resubmit the data after Government approval/disapproval has been issued.

9. Distribution Statement Required.

10. Frequency. The frequency of data submittal. Entries in this item are explained in Table 1. If the data is of a recurring type, it is to be submitted at the end of the reporting period established in this item unless otherwise indicated in item 14.

Table 1. Data Submittal Frequency Codes

CODE FREQUENCY CODE FREQUENCY

ANNLY Annually ASGEN As generated

ASREQ As required BI-MO Every two months

BI-WE Every two weeks CP/RQ Change pages as required

DAILY Daily DFDEL Deferred delivery

MTHLY Monthly ONE/R One time with revisions

OTIME One time (does not include draft submissions QRTLY Quarterly

R/ASR Revisions as required SEMIA Every six months

WEKLY Weekly “N”TIME Multiple separate submittals (2time, 3time, etc.)

See Item #14 Requirement is described in item #14. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in item #14.

11. As of Date. Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered to indicate the number of calendar days prior to the end of the reporting period, established in item 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at

15 days before the end of the month, quarter, or year, depending upon the frequency established in item 10; a “0 or blank” would place the “as of” date at the end of each month, quarter, etc.

12. Date of First Submission. Due date for initial data submission. This is normally the postage date or date the data is delivered to the Contracting Officer or keyed to a specific event or milestone, using a code from Table 2.

Table 2. Data Submission Codes

Code Definition Code Definition

ASGEN As generated ASREQ As required

DFDEL Deferred delivery “N”DAC Days after contract award

“N”DACM Days after contract modification “N”DARP Days after reporting period

“N”DARC Days after receipt of comments “N”DTC Days after test completion

NLT No later than EOC End of contract

EOM End of month EOQ End of quarter

See item #14 Use to indicate requirement is described in item 14. Used in lieu of other codes where such are inadequate to define requirement or used in addition to other codes when amplification is included in item 14.

The “N” is assigned a value indicating the number of days, e.g., 30 DAC

13. Date of Subsequent Submission. Due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 2.

14. Remarks. Contains all pertinent information not specified elsewhere and any amplification of other items on this format (e.g., DID tailoring, approva criteria and authority, inspection and acceptance clarification, distributions statements, specific submission instructions, explanation of reproducible copy and delivery requirements, alternative medium for delivery of the data item, etc.)

15. Distribution. Addressees and the number of draft and final copies (regular or reproducible) to be provided to each. FAA facility designator and/or office symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. When reproducible copies (e.g., magnetic diskettes/tape, vellum, negative, etc.) are required, an explanation will be provided in item 14. If deferred delivery is required, amplification will be given in item 14.

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 15 of 2

A004

2. Title of Data Item

Contract Funds Status Report

3. Subtitle

4. Authority

STDO-PM-005

5. Contact Reference

SOW - paragraph 3.3

6. Requiring Office

TSA/OST

7. DD 250 Req‟d 8. APP Code 9. Distribution Statement Required 10. Frequency 11. As of Date (AOD)

NA NA MTHLY 0

12. Date of First

Submission See Block 14

13. Date of Subsequent

Submission

BLK 14

Block 12

30 DAC

Block 13

20th of calendar month. If 20th falls on a non-workday, due next contractor work day.

Block 15

Shall be submitted in electronic form with the cover page signed by the contractor's authorized approving official. The electronic form shall be compatible with the Windows Office suite.

G. Prepared By: H. Date I. Approved By J. Date

STDO OST Approved

A. Contract Line Item No.. Contract Line Item Number (CLIN) associated with this Contract Data Requirements List (CDRL).

B. Exhibit. Exhibit identifier for this CDRL item.

C. Category. TDP, TM, or Other.

D. System/Item. System, item, project designator or name, or title of services being acquired that the data will support.

E. Contract/PR No. Procurement Instrument Identification Number (PIIN) (i.e., the contract number, the Purchase Request (PR) number, the screening

Information Request (SIR) number, or other appropriate designator.

F. Contractor. Contractor’s name.

G. Prepared by. Preparer’s organization responsible for preparing the CDRL.

H. Date. Date the form was prepared.

I. Approved by. Office responsible for approving the CDRL. The approving official’s signature appears on the last page of exhibit.

J. Date. The date the CDRL was approved.

1. Data Item No. The 4-character Exhibit Line Item Number (ELIN). The first position consists of the exhibit identifier and the remaining positions are assigned sequentially.

2. Title of Data Item. The title of the Data Item Description (DID) cited in item 4.

3. Subtitle. Further identification of the data item to supplement the title, if required.

4. Authority (Data Acquisition Document No.) DID identification number where detailed preparation instructions are provided.

5. Contract Reference. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

6. Requiring Office. The technical office having responsibility for ensuring the technical adequacy of the data.

7. DD 250 Required.

8. APP Code. Identification, by entry of an “A,” of a requirement for advance written approval prior to final distribution of an item of data. An “A” in this item indicates that one or more draft submittals are required. Item 14 will show length of turn-around time for the contractor to resubmit the data after Government approval/disapproval has been issued.

9. Distribution Statement Required.

10. Frequency. The frequency of data submittal. Entries in this item are explained in Table 1. If the data is of a recurring type, it is to be submitted at the end of the reporting period established in this item unless otherwise indicated in item 14.

Table 1. Data Submittal Frequency Codes

CODE FREQUENCY CODE FREQUENCY

ANNLY Annually ASGEN As generated

ASREQ As required BI-MO Every two months

BI-WE Every two weeks CP/RQ Change pages as required

DAILY Daily DFDEL Deferred delivery

MTHLY Monthly ONE/R One time with revisions

OTIME One time (does not include draft submissions QRTLY Quarterly

R/ASR Revisions as required SEMIA Every six months

WEKLY Weekly “N”TIME Multiple separate submittals (2time, 3time, etc.)

See Item #14 Requirement is described in item #14. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in item #14.

11. As of Date. Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered to indicate the number of calendar days prior to the end of the reporting period, established in item 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at

15 days before the end of the month, quarter, or year, depending upon the frequency established in item 10; a “0 or blank” would place the “as of” date at the end of each month, quarter, etc.

12. Date of First Submission. Due date for initial data submission. This is normally the postage date or date the data is delivered to the Contracting Officer or keyed to a specific event or milestone, using a code from Table 2.

Table 2. Data Submission Codes

Code Definition Code Definition

ASGEN As generated ASREQ As required

DFDEL Deferred delivery “N”DAC Days after contract award

“N”DACM Days after contract modification “N”DARP Days after reporting period

“N”DARC Days after receipt of comments “N”DTC Days after test completion

NLT No later than EOC End of contract

EOM End of month EOQ End of quarter

See item #14 Use to indicate requirement is described in item 14. Used in lieu of other codes where such are inadequate to define requirement or used in addition to other codes when amplification is included in item 14.

The “N” is assigned a value indicating the number of days, e.g., 30 DAC

13. Date of Subsequent Submission. Due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 2.

14. Remarks. Contains all pertinent information not specified elsewhere and any amplification of other items on this format (e.g., DID tailoring, approva criteria and authority, inspection and acceptance clarification, distributions statements, specific submission instructions, explanation of reproducible copy and delivery requirements, alternative medium for delivery of the data item, etc.)

15. Distribution. Addressees and the number of draft and final copies (regular or reproducible) to be provided to each. TSA facility designator and/or office symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. When reproducible copies (e.g., magnetic diskettes/tape, vellum, negative, etc.) are required, an explanation will be provided in item 14. If deferred delivery is required, amplification will be given in item 14.

Form Approved

OMB NO. 0704-0188

1. TITLE

CONTRACT FUNDS STATUS REPORT (CFSR)

2. IDENTIFICATION NUMBER

STDO-PM-005

3. DESCRIPTION/PURPOSE

3.1 The Contract Funds Status Report (CFSR) is designed to supply funding data about contracts for: (a) updating and forecasting contract funds requirements, (b) planning and decision making on funding changes to contracts, (c) developing funds requirements and budget estimates in support of approved programs, (d) determining funds in excess of contract needs and available for deobligation, and (e) obtaining rough estimates of termination costs.

4. APPROVAL DATE (YYMMDD)

5. OFFICE OF PRIMARY RESPONSIBILITY (OPR)

6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE

7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

7.2 This DID shall be used in conjunction with the project master schedule and the Cost/Schedule Status Report DID, STDO-

PM-003.

7.3 Contractual Application. The COTR will review reporting requirements at least annually and change them, if necessary.

(Continued on page 2)

8. APPROVAL LIMITATION

9a. APPLICABLE FORMS

9b. AMSC NUMBER

10. PREPARATION INSTRUCTIONS

10.1 Format. Contractor formats should be substituted whenever they contain all the required data elements at the specified reporting levels in a form suitable for TSA management.

10.2 Content. The CFSR shall contain the following information:

10.2.1 Item 1 - Contract Number. Enter the assigned contract number and the latest modification number on which contractual agreement has been reached.

10.2.2 Item 2 - Contract Type. Enter the type of contract as identified in FAR Part 16 (e.g., Cost Plus Fixed Fee (CPFF), Fixed Price Incentive (FPI), etc.).

10.2.3 Item 3 - Contract Funding For. Enter the applicable type as follows:

Multi-Year Procurement (MYP) Incrementally Funded Contract (INC) Contract for a Single Year (SYC)

10.2.3.1 For FY. For contracts which are financed with funds appropriated in more than one fiscal year, a report is required for each fiscal year's funds where the separate year's funds in the contract are associated with specific quantities of hardware or services to be furnished. The fiscal year(s) being reported will be shown in this block and that year's share of the total target prices (initial and adjusted) will be shown in Items 9 and 10.

(Continued on page 3)

11. DISTRIBUTION STATEMENT

Distribution Statement A: Approved for public release; distribution is unlimited.

DD Form 1664, APR 89 Previous editions are obsolete Page 1 of 7

Block 7, Application/Interrelationship (Continued)

7.3.1 Level of Reporting. If a contract is funded with a single appropriation, a single line entry at the total contract level should be considered for CFSR reporting. Reporting by line item or WBS element will be limited to only those items or elements needed to support funds management requirements. A reduced level of reporting may be implemented on contracts (a) with a dollar value between $250,000 and $1,000,000 (constant FY dollars); (b) that are for time and material; or (c) for which only limited funding requirements information is needed.

7.3.2 Multiple Appropriations. Where two or more appropriation sources are used for funding a single contract, contractors will segregate funds data by appropriation accounting reference. The procuring agency will supply the appropriation numbers applicable to individual line items or WBS elements. If a single line item or WBS element is funded by more than one appropriation, methods for segregating and reporting such information will be negotiated and specified in the contract.

7.3.3 Electronic Data Interchange. The American National Standards Institute (ANSI) X12 standard (transaction set 839), or the United Nations Electronic Data Interchange For Commerce, Administration and Transport (EDIFACT) equivalent, will be used for EDI transmission.

7.4 Frequency and Submission. The CFSR will be a contractual requirement as set forth in the Contract Data Requirements List (CDRL). Unless otherwise provided in the contract, the CFSR will be prepared as of the end of each calendar quarter or contractor accounting period nearest the end of each quarter.

The required number of copies of the CFSR will be forwarded within 25 calendar days after the "as of" date of the report, or as otherwise specified in the contract. In the event of exceptional circumstances which call for increased frequency in reporting, such frequency will not be more often than monthly and will be negotiated and specified in the contract.

7.5 Explanations of Terms.

7.5.1 Open Commitments. For this report, a commitment represents the estimated obligation of the contractor (excluding accrued expenditures) to vendors or subcontractors (based on the assumption that the contract will continue to completion).

7.5.2 Accrued Expenditures. For this report, include recorded or incurred costs as defined within the Allowable Cost, Fee and Payments Clause (FAR 52.216-7) for cost type contracts or the Progress Payments Clause (FAR 52.232-16) for fixed price type contracts, plus the estimated fee or profit earned.

Such costs include:

7.5.2.1 Actual payments for services or items purchased directly for the contract.

7.5.2.2 Costs incurred, but not necessarily paid, for storeroom issues, direct labor, direct travel, direct other in-house costs and allocated indirect costs.

7.5.2.3 Progress payments made to subcontractors.

7.5.2.4 Pension costs provided they are paid at least quarterly.

7.5.3 Termination Costs. Although this report is prepared on the basis that the contract will continue to completion, it is necessary to report estimated termination cost by government fiscal year and generally by more frequent intervals on incrementally funded contracts. The frequency will be dependent on the funding need dates (i.e., quarterly) and should be compatible with the contract funding clauses, Limitation of Funds clause (cost type contracts) or Limitation of Obligation clause (fixed price type contracts).

Te…