Attachment J-2 Contract Data Requirements List And Data Items Description 11-26-2024.docx

TABLE OF CONTENTS

ATTACHMENT J-2

CONTRACT DATA REQUIREMENTS LIST AND DATA ITEMS DESCRIPTION

This page intentionally left blank.

CONTRACT DATA REQUIREMENTS LIST INDEX

WSIC Screening Information Request Part III – Lists of Documents, Exhibits and Other Attachments SIR No. 693KA8-25-R-00002 Section J – List of Attachments

DESCRIPTION OF CDRL FORMS

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

Item B Exhibit: Exhibit identifier for this CDRL item.

Item C Category: This block provides the category of the item to be provided by the contractor. Other categories besides the Technical Data Package or Technical Manual can be Provisioning, Configuration Management, Test Plans, etc.

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

Item 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 designators.

Item F Contractor: Contractor’s name.

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

Item H Date: Date the form was prepared.

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

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

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

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

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

Block 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 Section C paragraph.

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

Block 7 DD 250: Not Used.

Block 8 Approval 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.

Block 9: Distribution Statement Required

Block 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.

WSIC Screening Information Request Part III – Lists of Documents, Exhibits and Other Attachments SIR No. 693KA8-25-R-00002 Section J – List of Attachments

Table 1. Data Submittal Frequency Codes

See Item #14 Requirement is described in #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.

Block 11 As of Date: The 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.

Block 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

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. Unless otherwise stated, “days” refers calendar days.

Block 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.

Block 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.). Unless otherwise specified, all documentation must be in Microsoft Office 2000 or Adobe Acrobat 6.0.

C. Category (Check appropriate one)

CLIN-001

TDP

TM

Other

D. System/Item

Weather Systems Integration Contract

1. Data Item No.

2. Title of Data Item

3. Subtitle

Program Plan

4. Authority

5. Contract Reference

6. Requiring Office

DID-001

3.1.1

FAA HQ, AJM-331

11. As of Date (AOD)

See Block 14.

12. Date of First Submission With Proposal

13. Date of Subsequent Submission

14. REMARKS:

G. Prepared By:

FAA HQ, AJM-331

C. Category (Check appropriate one)

CLIN-002

TDP

TM

Other

D. System/Item

Weather Systems Integration Contract

1. Data Item No.

2. Title of Data Item

3. Subtitle

Meeting Agenda

4. Authority

5. Contract Reference

6. Requiring Office

DID-002

3.1.4

FAA HQ, AJM-331

11. As of Date (AOD)

ASREQ.

14. REMARKS:

G. Prepared By:

FAA HQ, AJM-331

C. Category (Check appropriate one)

CLIN-003

TDP

TM

Other

D. System/Item

Weather Systems Integration Contract

1. Data Item No.

2. Title of Data Item

3. Subtitle

Meeting Minutes

4. Authority

5. Contract Reference

6. Requiring Office

DID-003

3.1.4

FAA HQ, AJM-331

11. As of Date (AOD)

ASREQ

14. REMARKS:

G. Prepared By:

FAA HQ, AJM-331

C. Category (Check appropriate one)

CLIN-004

TDP

TM

Other

D. System/Item

Weather Systems Integration Contract

1. Data Item No.

2. Title of Data Item

3. Subtitle

Monthly Program Management Report

4. Authority

5. Contract Reference

6. Requiring Office

DID-004

3.1.2, 3.4.3.1, 3.4.5.2

FAA HQ, AJM-331

11. As of Date (AOD)

MTHLY

13. Date of Subsequent Submission

14. REMARKS:

Block 10: End of calendar month after post-contract award meeting.

Block 12. Within 10 days after the end of the month in which the post- contract award meeting was held.

Block 13. Submittal within 10 days after the end of the month. Government will provide comments/approval within 14 days after receipt. Contractor must update report, as required, within 14 days after receipt of Government comments.

Block 15. All electronic deliveries must be without restrictions that would prevent the Government from reproducing or editing the information.

Electronic deliveries must be submitted via a secure online internet based web site that is vendor managed in .doc or .docx format and/or compatible with:

· Microsoft Office Suite ’2010

· Microsoft Project ‘2010

· Adobe Acrobat Reader

G. Prepared By:

FAA HQ, AJM-331

C. Category (Check appropriate one)

CLIN-005

TDP

TM

Other

D. System/Item

Weather Systems Integration Contract

1. Data Item No.

2. Title of Data Item

3. Subtitle

Trip Report

4. Authority

5. Contract Reference

6. Requiring Office

DID-005

3.6

FAA HQ, AJM-331

11. As of Date (AOD)

ASREQ

13. Date of Subsequent Submission

14. REMARKS:

G. Prepared By:

FAA HQ, AJM-331

1. Title

2. Identification Number

Program Plan

DID-001

3. Description/Purpose

3.1 This data item describes the contractor’s management organization, assignment of functions, duties, and responsibilities to include interrelationships between the prime Contractor, major subcontractor(s) and the contracting activity, management procedures and reporting requirements for the conduct on contractually imposed tasks, projects, or programs.

3.2 The Program Plan (PP) will provide 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 PP provides the contracting activity a basis for reviewing and evaluating contractor performance, and for determining contractual compliance.

FAA HQ, AJM-331

7. Application/Interrelationship

7.1 This DID must be the basis for the Contractor’s management approach to ensuring adherence to program technical, schedule, and cost objectives.

7.2 The PP must be consistent with data products generated for the direction, coordination, and control of system engineering, interface management, configuration management, quality assurance, production, system test, packaging/shipping, and installation management.

N/A

10. Preparation Instructions

10.1 Format. Electronic deliveries must be in .docx format and must be compatible with MS Office unless alternative software is approved by the Government. The PP must be prepared in the contractor’s format and conform to the following::

a. Identification. The plan must be identified with the preparing office or contractor’s title, the identifying numbers or designation of the Contract/Procurement Request, the identity of the project, and the Government activity issuing the controlling contract.

b. Descriptive Material. As may be needed to clarify or explain matter in the text, the plan may include descriptive material, sketches, drawings, photographs, table forms, graphs, worksheets, charts, etc. The PP must be delivered to the FAA in both paper and electronic media using MS Office products unless otherwise approved by the Government.

c. Table of contents and document size. The PP must be on standard size paper, and it must not exceed 30 single-sided, single-spaced pages. The pages must be sequentially numbered. The plan must include a table of contents and a definition list of all acronyms used.

10.2 Content. The PP must cover the organizational structure, program management methodology, personnel, resource management, program planning and scheduling tools and techniques, production planning and management, subcontractor management, and reports as described herein. As a minimum, other subjects to be included are described in the following sections:

a. Purpose. This paragraph must describe the purpose of the PP in terms of its relationship to the management of the project and performing the contract tasks outlined in the Statement of Work (SOW).

WSIC Screening Information Request Part III – Lists of Documents, Exhibits and Other Attachments SIR No. 693KA8-25-R-00002 Section J – List of Attachments

10. Preparation Instructions (Cont.)

b. Scope. This section must contain programmatic and technical background on the system; an overview of the Contractor’s approach to program technical, schedule, cost, and risk control; authority of the program manager; and the relationship of the PP to the other programmatic policies, procedures, and planning documents.

c. Contract Management. This section must 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.

d. Management Organization. Present a company organizational chart(s) and sufficient supplemental narrative to fully describe all organizational levels and activities. This chart must be hierarchical in nature and should delineate clearly all major area responsibilities and management positions. Provide a similar chart of the program organization to be used in performance of the contract. If the project includes major subcontractors, provide organizational and functional information about the subcontractor.

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

f. Personnel. The plan must list the personnel staffing of the contractor’s management office that directs the contractual tasks, projects, and programs and assist in completing the contract. The list must include the identity, background, and work experience of the personnel assigned to fill these positions. As a minimum, the experience of personnel listed must be IAW the requirements in Section H.1.

g. Staffing. The plan must also describe the staffing required for proper accomplishment of each contractual task by skill type, level, and number of personnel. This description must include a chart depicting the projected variations in staffing levels planned for each project phase.

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

i. Relationships. Describe the working relationships the Contractor will establish with the Government (FAA) and any subcontractors supporting the procurement of the equipment.

j. Subcontractor 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.

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

l. 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. Preparation Instructions (Cont.)

m. 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. Describe contractor procedures to develop a plan of action to mitigate risk.

n. 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 must 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 ICDRL 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 must be also described.

o. Quality Control, Performance Evaluation, and Contractual Compliance. This section must discuss Contractor and major subcontractor(s) methods and concepts for continuous quality control, performance evaluation, and contractual compliance.

p. Production Management. This section must discuss Contractor and major subcontractor(s) methods and concepts for employing facilities, tooling, and manpower resources to produce the system/equipment.

q. 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.

r. Capability and Capacity. This section describes the data and information used to determine the Contractor capability and capacity to meet schedule requirements. The Contractor must provide data indicating ability to meet the production rate and quantities required for the system. Manufacturing risks and the systems used to track suppliers' progress and to detect/correct potential delivery problems must also be addressed. Provide a list of all subcontractors and major vendors indicating the services/ materials to be supplied by each.

1. Title

2. Identification Number

Meeting Agenda

DID-002

3. Description/Purpose

3.1 This Data Item describes the agenda information concerning joint contractor/Government conferences required to manage the acquisition of system/equipment, related items and services.

3.2 The agenda sets forth the place, time, date, purpose, location and objective of each forthcoming conference or meeting.

FAA HQ, AJM-331

7. Application/Interrelationship

7.1 This Data Item Description (DID) is applicable to all contracts for system/equipment related items and services.

7.2 This DID satisfies the requirements of applicable procurement documents cited in the contract by SOW paragraph 2.1.4

10. Preparation Instructions

10.1 Format. A separate agenda in contractor’s format is required for each proposed meeting or conference and must be transmitted by electronic mail. Electronic deliveries must be in .doc format and must be compatible with MS Office unless alternative software is approved by the Government.

10.2 Content. The agenda must include the following, where applicable:

a. The purpose and objective of the meeting or conference,

b. The recommended meeting or conference location, date and duration,

c. A daily chronological listing of each major topic or subtopic to be discussed and the time schedule to be devoted to each topic,

d. A recommended list of activities to be represented and identification of their responsibilities,

e. A recommended list of subcommittees to be established during the meeting or conference and the proposed activity representation for each subcommittee,

f. Reference to and brief description of the results of previous meetings or conferences on the same idea,

g. Location, schedule and purpose or subject area to be covered by each subcommittee,

h. Name of government chairperson and co-chairperson of meeting or conference and designated activity representative to act as subcommittee chairman,

i. Administrative notes as required to indicate lodging, meals, transportation and administrative services available to conference attendees,

j. Complete list of all documentation to be available for review,

k. Brief description of progress on actions or problems identified at previous meetings or conferences.

l. Other pertinent information such as forms to be used, identification of any deviations or waivers, security classification, clearance requirements, etc.

11. Distribution Statement

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

1. Title

2. Identification Number

Meeting Minutes

DID-003

3. Description/Purpose

3.1 This Data Item describes documentation of technical information and data required to record joint contractor/government decisions and agreements reached during minutes or conferences, formal reviews, inspections or audits.

FAA HQ, AJM-331

7. Application/Interrelationship

7.1 This Data Item Description (DID) is applicable to all contracts for system/equipment related items and services.

7.2 This DID satisfies the requirements of applicable procurement documents cited in the contract by SOW paragraph 3.1.4

10. Preparation Instructions

10.1 Format. Minutes of each meeting or conference must be prepared in contractor format and must be transmitted by electronic mail. Electronic deliveries must be in .doc format and must be compatible with MS Office unless alternative software is approved by the Government.

10.2 Content. The minutes must include the following, where applicable:

a. A title page containing the following:

1. Title – type of meeting and date

2. Identification of system/equipment, training courses, contract number, etc.

3. Space for signatures of the designated representatives of the contractor and procuring activity

4. The name of the contractor and address to which the procuring activity should send acknowledgements of receipt/comments) Reference to and brief description of the results of previous meetings on the same idea,

b. The purpose and objective of the meeting or conference.

c. The meeting or conference location.

d. A summary of the discussions, decisions, agreements reached and the directions of the meeting or conference or individual subcommittees thereof.

e. A list of attendees, phone numbers, e-mail addresses, activity represented, as appropriate.

f. Copies of action item sheets for each action to be implemented as a result of the meeting or conference.

g. An updated copy of the meeting or conference to reflect the actual agenda for the meeting or conference as conducted.

h. The required elements of information specified by the meeting or conference chairperson which are applicable to the type of conference/meeting conducted and other data and information as mutually agreed between the contractor and procuring activity.

11. Distribution Statement

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

1. TITLE

PROGRESS AND STATUS REPORT

2. IDENTIFICATION NUMBER

DID-004

3. DESCRIPTION/PURPOSE

3.1 The Progress and Status Report provides the Government the Contractor's assessment of the contractual effort for the month of the report. It provides progress updates on the various work activities to be performed by the Contractor and on upcoming activities planned by the Contractor.

3.2 The report must include updates on all active TASK 2 – HARDWARE AND SITE KIT PRODUCTION, TASK 3 - INTEGRATED LOGISTICS SUPPORT, and TASK 4 – IMPLEMENTATION SUPPORT activities.

7. APPLICATION/INTERRELATIONSHIP

7.1 The report will be organized to provide progress and status by contract task and CLIN.

10. PREPARATION INSTRUCTIONS

10.1 The Progress and Status Report must cover the Contractor's efforts as well as any subcontractor's efforts. The contractor must use Microsoft Word and/or Microsoft Excel to track and report the status of the program.

10.1 The report must be organized to include:

10.1.1 A general summary of the status of the contract activities, including work accomplishment during the reporting period, tasks or CLINs started or completed during the reporting period, problems or issues encountered during the reporting period and proposed solutions, and updates on any outstanding issues from previous reporting periods.

10.1.2 The following data must be provided for each active CLIN for activities under TASK 2 – HARDWARE PRODUCTION:

10.1.2.1 CLIN identification number and description, including quantity of mods, assemblies, or site kits to be produced and total contracted cost.

10.1.2.2 For the reporting period: number of mods, assemblies, or site kits completed (FAT passed), invoiced to the Government, and paid for by the Government.

10.1.2.3 Cumulative totals for: number of mods, assemblies, or site kits completed (FAT passed), invoiced to the Government, and paid for by the Government.

10.1.2.4 The funding amounts both invoiced and received for the reporting period and cumulatively.

10.1.2.5 A graphical presentation of the data provided in 10.2.2.2 and 10.2.2.3 by month

10.1.2.6 The expected number of mods, assemblies, or site kits to be completed (TAF passed) during the next reporting period.

10.1.3 A separate section must report on the following data for TASK 3 – INTEGRATED LOGISTICS SUPPORT activities:

10.1.3.1 A summary of the progress on activities detailed in contract sections 2.3.1 Initial FAALC Depot Spares, 2.3.2 Contractor Depot Spares Inventory, 2.3.3 Depot Level Supply Support, 2.3.5 Parts Obsolescence Reporting, and 2.3.7 Transition of Contractor Depot Spares to FAALC must be included on an as-needed basis.

10.1.3.2 A section titled “Maintenance and Reliability Reporting” will contain information on all hardware LRU failures and repairs to allow for the generation of statistics on reliability, availability, and maintainability.

10.1.3.2.1 All hardware LRU failure maintenance actions must report the following information:

a. Part number/NSN

b. Serial number (if applicable)

c. Part description

d. Date of request for repair

e. Site associated with LRU

f. Date of LRU shipment

g. Failure analysis of LRU

10.1.3.2.2 Each calendar quarter (3 months) a cumulative report of all hardware LRU failures must be included with an analysis of the LRU reliability, availability, and maintainability.

10.1.3.3 As described in section 2.3.6 Stock Tracking and Reporting, an Inventory Report (in Microsoft Excel format) providing the following information must be included:

10.1.3.3.1 Part 1 of the Inventory Report will provide the following information on the GFE provided to the Contractor:

a. Part number/NSN

b. Part description

c. Quantity provided as GFE

d. Quantity currently on hand in Fully Usable condition

e. Quantity currently on hand in any condition other than Fully Useable (e.g., Reparable Stock)

f. Quantity sent to FAA field sites

10.1.3.3.2 Part 2 of the Inventory Report will provide the following information on the Contractor Depot Spares:

a. Part number/NSN

b. Part description

c. Quantity currently on hand in Fully Usable condition

d. Quantity currently on hand in any condition other than Fully Useable (e.g., Reparable Stock)

e. Due-in quantity (from FAA field site)

f. Minimum stock level quantity required

10.1.3.4 A section titled “Delivery/Shipping Support” must provide the following information on all shipments to field sites:

a. Part number/NSN of item(s) shipped

b. Item description (e.g., individual item, LRU, assembly, AWOS Kit, etc.)

c. Serial Number(s) (if applicable) – serial numbers of all sensors, CDP computers, DCPs, CDP racks, etc.

d. Date shipped

e. Project Control Number (PCN)

f. Ship to point-pf-contact

g. Address shipped to

h. Site identifier of FAA field site where item is to be installed

10.1.4 A separate section must report on the following data for each active task order under TASK 4 – IMPLEMENTATION SUPPORT activities:

10.1.4.1 Task Order number and description, including scope of work to be provided, start date, expected task duration, expected completion date, and total contracted Not To Exceed cost.

10.1.4.2 The work accomplished on the task order during the reporting period.

10.1.4.3 The current status of work activities as of the end of the reporting period.

10.1.4.4 The plan for work activities for the following month.

10.1.4.5 The costs incurred on the task order activities during the reporting period.

10.1.4.6 The costs invoiced to and payment received from the Government on the task order during the reporting period.

10.1.4.7 The cumulative costs incurred, invoiced, and payments received on the task order during the reporting period.

10.1.4.8 A graphical presentation of the task order costs incurred, invoiced, and received for the reporting period and cumulatively (see Sample Report format) by month.

10.2 Use of graphs, charts, photographs, illustrations, and other materials is encouraged when useful.

1. Title

2. Identification Number

Trip Report

DID-005

3. Description/Purpose

The Trip Report must include the travel details, work performed, and related costs of the trip being reported.

FAA HQ, AJM-331

7. Application/Interrelationship

This DID is applicable to all trips billed to the Government under this contract.

10. Preparation Instructions

10.1 Format. The contractor must provide a report, covering all travelers, for every trip billed to the Government.

10.2 Content. The report must contain, as a minimum, the following:

a. Detailed travel information including: destination, mode of travel, place of accommodation, and number of days on per diem

b. Detailed cost information for the travel described.

c. Summary of the trip including: purpose of the trip, identification of the individuals on the trip, identification of the installation site(s) or meeting attended, and general description of the work performed. If the trip covered work at more than one site, the travel costs must be allocated to the individual sites, as appropriate.

d. Details of any expenses incurred in addition to those described as required in paragraph a) above. These costs must be allocated to a specific installation site.

e. Details of any problems or issues that were encountered on a per site basis.

11. Distribution Statement

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