CDRL A006 Phase In Transition Plan.pdf

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

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 1 of 2

A. Contract line Item No. B. Exhibit C. Category (Check appropriate one)

TDP TM Other X E. Contract/PR No. F. ContractorD. System/Item

Flight Program Operations - Hangar 6 Aircraft Lease

3. Subtitle1. Data Item No.

A006

2. Title of Data Item

Phase In Transition Plan

4. Authority Contractor Format as agreed by Government

5. Contact Reference SOW Paragraphs 6.0 - 6.4, TEP

6. Requiring Office

AAQ/AJF

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

12. Date of First 13. Date of Subsequent

15. Distribution

a. b. Draft c. Final Copies Addressee Copies Reg. Repro

14. REMARKS:

The Phase-In Transition Plan will include the aircraft paint schedule, Contractor communication contact(s), notification of issues, any maintenance activities, and any other activities the Contractor performs on the aircraft prior to delivery.

The Phase-In Transition Plan will also include Sovereign Plus (CE-680+) initial qualification training and checkride costs for up to five FAA pilots and training for up to five FAA maintenance personnel, per SOW Paragraph 6.3.

The Phase-In Transition Plan will also include the services of a CE-680+ instructor pilot to provide up to 100 flight hours of time during the first six months after aircraft delivery in order for FAA pilots to gain initial operating experience in the CE-680+.

This contracted instructor pilot must be current and type-rated in the CE-680+, and available at the aircraft delivery date, per SOW Paragraph 6.4. All instructor hours for pre-flight and post-flight, travel and other hours should be taken into consideration in the phase in plan and how this will be accomplished. All travel expenses and other expenses should be addressed in this plan.

Deliver to:

Contracting Officer, or Contractor Officer's Representative via email. Email address of COR to be provided at award.

AAQ

AJF

1 1 1

16. Total

I. Approved By J. DateG. Prepared By:

Louis R. Volchansky, AJF-1240 H. Date

17. Price Group 18. Estimated Total Price not separately priced

At Proposal

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

INSTRUCTIONS FOR COMPLETING FAA Template No. 59 (6/98) (Mark Not Applicable sections as N/A)

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.