CDRL_A024_Parts_Obsolescence_Management_Plan.doc

DOC document 64 KB Posted

Attached to
Explosive Detection Sytsem (EDS) Performance Based Logistics (PBL) Federal contract opportunity
Solicitation number
70T04018R9CAP3024
Issued by
Department of Homeland Security Transportation Security Administration

About this file

CDRL A024 Parts Obsolescence Management Plan

View the file

Other files for this federal contract opportunity

Other files attached to Explosive Detection Sytsem (EDS) Performance Based Logistics (PBL), newest first.
File Type Posted
70T04018R9CAP3024_Amendment_0002.pdf PDF
EDS_PBL_RFP_Questions_7.25.18.pdf PDF
Attachment_D-6_QASP.DOC DOC document
EDS_PBL_RFP_Questions.pdf PDF
70T04018R9CAP3024_Amendment_0001.pdf PDF
RFP_70T04018R9CAP3024.pdf PDF
Attachment_D1_DIDs.zip ZIP file
Attachment_D1_CDRLs.zip ZIP file
Attachments_D2_D10.zip ZIP file
Attachments_F1_F7.zip ZIP file

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

CONTRACT DATA REQUIREMENTS LIST (CDRL)

A. Contract Line Item No.

TBD

B. Exhibit

A C. Category (Check appropriate one)

TDP FORMCHECKBOX

TM FORMCHECKBOX

Other FORMCHECKBOX

D. System/Item

TSE PBL Services E. Contract/PR No.

TBD

F. Contractor

1. Data Item No.

A024

2. Title of Data Item

Parts Obsolescence Management Plan (POMP)

3. Subtitle

N/A

4. Authority

OAPM-ILS-024

5. Contract Reference

PWS Paragraph C.4.3

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
A
ONE/R
0

12. Date of First

Submission

30 DAC
13. Date of Subsequent

Submission

ASREQ

15. Distribution

See Block 14

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

Block 12

The initial POMP shall be submitted to the Government 30 DAC.

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

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

The POMP shall be reviewed and updated annually if necessary to reflect up-to-date information and plans depicting the current maintenance activities and implementation.

Block 13

If the POMP is updated, the revised data item shall be submitted within 20 working days from end of review.

Block 15

The POMP shall be submitted in electronic format compatible with Microsoft Office Suite in accordance with paragraph C.2.4 of the PWS. CDRL submittal will be sent to the CO, COR, and the COR designated recipients as directed. 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

G. Prepared By:
H. Date
I. Approved By
J. Date
OAPM
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.

OMB Control No. 2120-0595

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

File details come from the government source that posted it.