Attachment_2_-_CDRLs.pdf

OMB Control No. 2120-0595 (DD Form 1423-1) FAA Template No. 59 (6/98)

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 1 of 1 A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A001

2. Title of Data Item

Program Management Plan

3. Subtitle

N/A

4. Authority

OAPM-ILS-001

5. Contract Reference

PWS – C.7.1, of Part C

6. Requiring Office

OAPM

7. DD 250 Req’d

LT

8. APP Code

A See Block 14

9. Distribution Statement Required

A

10. Frequency

ONE/R

11. As of Date (AOD)

12. Date of First Submission

See Block 14

13. Date of Subsequent Submission

See Block 14

15. Distribution

See Block 14

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

Block 4 The Program Management Plan (PMP) shall be prepared in accordance with the referenced Data Item Description. For requested information that is described in detail in other CDRL deliverables (Quality Management system, etc.), the appropriate paragraph in the PMP shall include sufficient detail to indicate a full understanding of the requirement.

Block 8 If a submittal is disapproved, the data item shall be revised and re-submitted within 15 business DARC.

Block 10 Once approved by the COR, proposed changes shall be submitted 20 business days prior to required implementation date.

Block 12 The initial PMP shall be submitted to the Government with the Contractor’s technical proposal (Volume I). The Contractor shall submit their PMP for approval within 30 calendar days of contract award.

Block 13 The PMP shall be reviewed and updated semi-annually to reflect up-to-date information and plans depicting the current maintenance activities and implementation. If the PMP is updated, the revised data item shall be submitted within 200 calendar days of the current version. If no update is required, then the Contractor shall notify the Government of the date the review was completed and use that date to plan review.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. The PMP shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the PWS. The CDRL shall be delivered with a cover letter signed by the Contractor’s authorized approving official.

Addressee Copies Reg. Repro

CO

COR

16. Total 2

OMB Control No. 2120-0595 (DD Form 1423-1) FAA Template No. 59 (reverse) (6/98)

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

OAPM 03/08/2013

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, approval 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.

A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A002

2. Title of Data Item

Program Status Report

3. Subtitle

N/A

4. Authority

OAPM-ILS-002

5. Contact Reference

PWS - C.7.4, of Part C

6. Requiring Office

OAPM

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

LT A See Block 14 A MTHLY 0

12. Date of First Submission

30 DAC

13. Date of Subsequent Submission

10 DARP

15. Distribution

See Block 14

14. REMARKS:

Block 4 The Program Status Report (PSR) shall be prepared in accordance with the referenced Data Item Description.

Block 13 Monthly submissions shall be delivered by the 10th calendar day of each month. If the 10th falls on a weekend or observed Federal Holiday, the submission is due the next weekday.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. The PSR shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the Performance Work Statement. The CDRL shall be delivered with a cover letter signed by the Contractor’s authorized approving official.

a. b. c. Final Copies

Addressee Copies Reg. Repro

CO

COR

OAPM

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, approval 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.

OMB Control No. 2120-0595 (DD Form 1423-1) FAA Template No. 59 (6/98

A. Contract line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A003

2. Title of Data Item

Requirements Traceability Report

3. Subtitle

N/A

4. Authority

OAPM-ILS-003

5. Contact Reference

PWS – C.7.5, of Part C

6. Requiring Office

OAPM

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

LT A See Block 14 A MTHLY 0

12. Date of First Submission

30 DAC

13. Date of Subsequent Submission

10 DARP

15. Distribution

See Block 14

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

Addressee Copies Reg. Repro

Block 4 The Requirements Traceability Report (RTR) shall be prepared in accordance with the referenced Data Item Description.

Block 13 Monthly submissions shall be delivered by the 10th calendar day of each month. If the 10th falls on a weekend or observed Federal Holiday, the submission is due the next weekday.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. The RTR shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the Performance Work Statement (PWS). The CDRL shall be delivered with a cover letter signed by the Contractor’s authorized approving official.

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, approval 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.

A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A004

2. Title of Data Item

Transportation Security Equipment Database

3. Subtitle

N/A

4. Authority

OAPM-ILS-004

5. Contract Reference

C.7.6, of Part C

6. Requiring Office

OAPM

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

LT A See Block 14 A MTHLY 0

12. Date of First Submission

30 DAC

13. Date of Subsequent Submission

5 DARP

15. Distribution

a. b. Draft c. Final Copies

The Transportation Security Equipment (TSE) Database shall be prepared in accordance with the referenced Data Item Description.

Block 13 Monthly submissions shall be delivered by the 5th calendar day of each month. If the 5th falls on a weekend or observed Federal Holiday, the submission is due the next weekday.

Block 15 The TSE Database shall be delivered by CD or DVD, or via secure electronic means, with a Letter of Transmittal signed by the Contractor’s authorized approving official. E-mail notification of delivery will be sent to the CO, COR, and the COR designated recipients as directed. The TSE Database shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with C.3, of Part C, Performance Work Statement.

The Contractor shall also maintain a secure, password protected TSE Database accessible by designated Government personnel as specified in the contract.

Addressee Copies Reg. Repro

CO

COR

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, approval 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.

A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one) TDP TM Other

D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A005

2. Title of Data Item

Program Document Library Index

3. Subtitle

N/A

4. Authority

OAPM-ILS-005

5. Contact Reference

PWS – C.7.7, of Part C

6. Requiring Office

OAPM

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

LT A See Block 14 A MTHLY 0

12. Date of First Submission

30 DAC

13. Date of Subsequent Submission

10 DARP

15. Distribution

a. b. c. Final Copies

The Program Document Library (PDL) Index shall be prepared in accordance with the referenced Data Item Description.

Block 13 Monthly submissions shall be delivered the 10th calendar day of the month following the reporting period. If the 10th falls on a weekend or observed Federal Holiday, the submission is due the next weekday.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. The PDL Index shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the Performance Work Statement. The CDRL shall be delivered with a cover letter signed by the Contractor’s authorized approving official.

Addressee Copies Reg. Repro

CO

COR

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, approval 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.

A. Contract line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A006

2. Title of Data Item

Subcontractor Management Report

3. Subtitle

N/A

4. Authority

OAPM-ILS-006

5. Contact Reference

PWS - C.7.8, of Part C

6. Requiring Office

OAPM

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

LT A See Block 14 A ONE/R 0

12. Date of First Submission 13. Date of Subsequent Submission 15. Distribution

30 DAC ASREQ See Block 14

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

Addressee Copies Reg. Repro

Block 4 The Subcontractor Management Report shall be prepared in accordance with the referenced Data Item Description.

Block 12 If a submittal is disapproved, the data item shall be revised and re-submitted within 15 business DARC.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. The Subcontractor Management Report and copies of Subcontractor/Partnering Agreements shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the Performance Work Statement. The CDRL shall be

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, approval 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.

A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP TM Other D. System/Item

TSE ILS Services E. Contract/PR No.

TBD

F. Contractor

TBD

1. Data Item No.

A007A

2. Title of Data Item

Meeting Agenda and Presentation Mat.

3. Subtitle

N/A

4. Authority

OAPM-ILS-007A

5. Contact Reference

PWS - C.7.9, of Part C

6. Requiring Office

OAPM

7. DD 250 Req’d

LT

8. APP Code

A See Block 14

9. Distribution Statement Required

A

10. Frequency

ASREQ

11. As of Date (AOD)

12. Date of First Submission

ASREQ

13. Date of Subsequent Submission

ASREQ

15. Distribution

See Block 14

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

Addressee Copies Reg. Repro

Block 4 The Meeting Agenda and Presentation Materials shall be prepared in accordance with the referenced Data Item Description.

Block 13 The agenda and presentation materials shall be submitted 5 business days prior to the scheduled meeting.

Block 15 The Government will determine method of submission, e.g. password protected Web site, email, disk, etc. If a Web site is utilized then an e-mail notification of CDRL posting will be sent to the CO, COR, and the COR designated recipients as directed. Meeting Agenda and Presentation Materials shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with Paragraph C.3 of the Performance Work Statement. The CDRL shall be delivered with a cover letter signed by the Contractor’s authorized approving official.

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, approval 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.