DNTS SIR Sect J2 - CDRLs and DIDs.pdf

Dedicated Network Telecommunications System (DNTS) SIR 693KA8-24-R-00007

Page J2-1

PART I - SECTION J2

Contract Data Requirements List (CDRL) and

Data Item Descriptions (DIDs)

Page J2-2

CONTRACT DATA REQUIREMENTS LIST (CDRL) INDEX

CLIN # CDRL # TITLE DID # SOW PARA.

0020 A001 Program Management Plan FAA-DNTS-A001 C.3.1.2

0021* A002 Integrated Master Schedule FAA-DNTS-A002 C.3.1.3

0022 A003 Quality System Plan FAA-DNTS-A003 C.3.1.4

0023 A004 Configuration Management Plan FAA-DNTS-A004 C.3.2.3

0024* A006 Configuration Status Accounting Report (CSAR) FAA-DNTS-A006 C.3.2.6

0025* A007 Agenda FAA-DNTS-A007 C.3.1.6

0026* A008 Minutes FAA-DNTS-A008 C.3.1.6

0027* A005 Engineering Change Proposal (ECP) FAA-DNTS-A005 C.3.2.7

0028* A009 Monthly Program Status Report (MPSR) FAA-DNTS-A009 C.3.1.5

0030 L001 Integrated Support Plan FAA-DNTS-L001 C.3.3.3

0031* L002 Logistics Management Information (LMI) Data

Products

FAA-DNTS-L002 C.3.3.5

0032 L003 Final Breakdown Structure (FBS) FAA-DNTS-L003 C.3.3.6

0033 L004 Tools and Test Equipment List (TTEL) FAA-DNTS-L004 C.3.3.7

0034* L005 Monthly Repair Status Report (MRSR) FAA-DNTS-L005 C.3.3.8.2

0035 L007 FAA Scanning Process Pilot Run Report FAA-DNTS-L007 C.3.3.12.10

0036* L008 Diminishing Manufacturing Sources and Material

Shortages Report

FAA-DNTS-L008 C.3.3.10

0040 M001 Personnel Qualification Report (PQR) FAA-DNTS-M001 C.3.3.11.4

0041 M002 Commercial-Off-the-Shelf (COTS) Training

Materials Report

FAA-DNTS-M002 C.3.3.11.5

0042 M003 Training Development Plan (TDP) FAA-DNTS-M003 C.3.3.11.6

0043 M004 Task and Skills Analysis (TASA) Report FAA-DNTS-M004 C.3.3.11.7

0044 M005 Course Design Guide (CDG) FAA-DNTS-M005 C.3.3.11.8

0045 M006 Student Achievement Tests FAA-DNTS-M006 C.3.3.11.9

0046 M007 WBT Theory of Operations and Maintenance Course FAA-DNTS-M007 C.3.3.11.10

0047 Instructor Led Training (ILT) Lab Course Training

Material

C.3.3.11.11

0048 L006 Technical Instruction Book FAA-DNTS-L006 C.3.3.9

0049 M008 Classroom Training Material FAA-DNTS-M008 C.3.3.11.11

0050 T001 Contractor Master Test Plan FAA-DNTS-T001 C.3.4.2

0051 T002 Contractor Verification Requirements Traceability

Matrix (CVRTM)

FAA-DNTS-T002 C.3.4.2.1

0052 T003 Test Tool Accreditation Plan (TTAP) FAA-DNTS-T003 C.3.4.2.2

0054 T004 Factory Acceptance Test (FAT) Plan FAA-DNTS-T004 C.3.4.3.1

0055 T005 Factory Acceptance Test (FAT) Procedures FAA-DNTS-T005 C.3.4.3.2

0056 T006 Test Readiness Review (TRR) Briefing Package FAA-DNTS-T006 C.3.4.3.3

0057 T007 Factory Acceptance Test (FAT) Report FAA-DNTS-T007 C.3.4.3.4

0058 T009 Production Acceptance Test (PAT) Plan FAA-DNTS-T009 C.3.4.5.1

0059 T010 Production Acceptance Test (PAT) Procedures FAA-DNTS-T010 C.3.4.5.2

0060* T011 Production Acceptance Test (PAT) Report FAA-DNTS-T011 C.3.4.5.3

0061 T012 Production Unit Test (PUT) Plan FAA-DNTS-T012 C.3.4.6.1

0062 T013 Production Unit Test (PUT) Procedures FAA-DNTS-T013 C.3.4.6.2

0063* T014 Production Unit Test (PUT) Report FAA-DNTS-T014 C.3.4.6.3

0064 T008 DNTS Product Familiarization FAA-DNTS-T008 C.3.4.4.2

*Indicates CLINs that are included in Option Periods, Contract Years 4 through 10. The first character of the CLIN will change to correspond to the Contract Year. For example, CDRL A002, Integrated Master Schedule, will be CLIN 3021 in Contract Year 4, and

CLIN 4021 for Contract Year 5, etc.

Page J2-3

2.0 GENERAL NOTES

All DID numbers contain the prefix “FAA-DNTS-” followed by a four-digit code starting with one letter followed by three digits.

The letters in the code are “A” for management, “T” for test, “L” for logistics, and “M” for training. CDRL numbers all use the same

DID four digit-code. The only exception is A009. This uses an FAA standard DID.

All days are calendar days unless stated otherwise. All submitted electronic material must be in designated Microsoft Office Suite

2010 unless alternative software is approved by the Government. Unless otherwise noted, the Government will review within thirty calendar days (30) from the date of submission.

All deliverables must be submitted with a cover page; deliverables submitted in .xlsx (Excel) format must use the first tab (worksheet) for the cover page. This page must contain the document control number in the upper right-hand corner. In the center of the page, these words must appear in the following format:

[CDRL Title]

For The

Airport Cable Loop (ACL) Dedicated Network Telecommunications System (DNTS)

Contract No. TBD

CDRL Sequence No. [XXXX] [Version (Draft or Final)]

[Date of Document - Day Month Year]

Prepared For:

Federal Aviation Administration

Prepared by:

Contractor name and address

Contractor’s Unique Entity ID (SAM.gov)

For [CDRL Title] use the Title of Data Item from CDRL Box No. 4. For [XXXX] use the Data Item No. from CDRL Box No. 1. For

[Version (Draft or Final)] indicate the version number and whether the submission is a draft or final. For [Date of Document (Day

Month Year)] indicate the document date in the format shown.

The CDRL form uses FAA Template No. 59. There is an instruction sheet (3.0) below that describes the contents of each block. It also lists the ACRONYMS or “CODE” used in the appropriate blocks. The DIDs use FAA Template No. 60. There are no special instructions for DIDs.

3.0 CONTRACT DATA REQUIREMENTS LIST DESCRIPTIONS

A. Contract Line Item No. Contract Line Item Number (CLIN) associated with this Contract Data Requirements List (CDRL). Only the base period CLIN is listed in the CDRL and DID. As noted in Section 1.0 Contract Data Requirements List (CDRL) Index, the first character of the astericked CLINs will change during option periods to correspond to the Contract Year.

B. Exhibit. Exhibit identifier for this CDRL item. (Not Used)

C. Category. TDP, TM, or Other. (Not Used)

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.

1. Data Item No. The 4-character Contract Line Item Number (CLIN). 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. Letter Required. Letter of Transmittal 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. An “R” indicates Review.

Page J2-4

9. Distribution Statement Required. For technical data, specify requirement for Contractor to mark the appropriate distribution statement on the data.

DISTRIBUTION A. Approved for public release: distribution unlimited.

DISTRIBUTION B. Distribution authorized to U.S. Government agencies (reason) (date of determination). Other requests for this document must be referred to (controlling FAA office).

DISTRIBUTION C. Distribution authorized to U.S. Government agencies and their contractors (reason) (date of determination). Other requests for this document must be referred to (controlling FAA office).

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 0; 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

“N” DARO Days after receipt of order “N” DACA 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 DACA.

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

Page J2-5

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. For distribution codes see Table 3.

Table 3. Data Distribution Codes

CODE DEFINITION

DE Draft Electronic

DP Draft Paper

FE Final Electronic

EA Electronic Alert

FP Final Paper

L Cover Letter

N/A Not Applicable

A distribution List giving the full mailing and electronic address for each addressee follows:

AAQ-320 Attn: Contracting Officer – TBD

ATC Communications Contracts

Federal Aviation Administration

800 Independence Avenue, SW

Washington, DC 20591

Email: TBD

AJM-313 Attn: TBD

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

17. Price Group. Not used.

18. Estimated Total Price. Not used.

Page J2-6

CONTRACT DATA REQUIREMENTS LIST (CDRL) Page 1 of 1

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

TDP TM Other

D. System/Item E. Contract/PR No. F. Contractor

Dedicated Network

Telecommunications System

(DNTS)

Error! Reference source not found.

1. Data Item No. 2. Title of Data Item 3. Subtitle

A001 Program Management Plan

4. Authority 5. Contract Reference 6. Requiring Office

FAA-DNTS-A001 SOW C.3.1.2 AJM-313

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

Yes A. C AS REQ

12. Date of First

Submission 60 DARO 13. Date of Subsequent

Submission

30 DARC

15. Distribution

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

Addressee Copies Reg. Repro

AAQ-320

AJM-313

L/DE

DE

L/FE

FE

N/A

16. Total 2 2 N/A

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

17. Price Group

18. Estimated Total Price

Page J2-7

DATA ITEM DESCRIPTION Page 1 of 4

1. Title 2. Identification Number

Program Management Plan FAA-DNTS-A001

3. Description/Purpose

3.1 This data item describes the Contractor’s management organization, assignment of functions, duties, and responsibilities, management procedures and reporting requirements for the conduct on contractually imposed tasks, projects, or programs.

3.2 The Program Management Plan (PMP) must provide details of the specific techniques, tasks, and procedures to be used for monitoring contract management and performance, configuration control, data management, quality control, production management, identified necessary equipment; engineering; logistics support; maintenance/operator training; spares provisioning and maintenance program; and the documentation for implementation, maintenance, and operation of the DedicatedNetwork Telecommunications

System (DNTS).

3.3 The PMP provides the basis for reviewing and evaluating Contractor performance and for determining contractual compliance.

4. Approval Date (YYYY/MM/DD) 5. Office of Primary Responsibility (OPR) 6a. DTC Applicable 6b. GIDEP Applicable

AJM-313

7. Application/Interrelationship

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

7.2 The PMP 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, installation management, identifying necessary equipment; engineering; logistics support; maintenance/operator training; spares provisioning and maintenance program; and the documentation for implementation, maintenance, and operation of the DNTS.

8. Approval Limitation 9a. References 9b. AMSC Number

10. Preparation Instructions

10.1 Format. Electronic deliveries must be as specified in Section J2 2.0 General Notesunless alternative software is approved by the

Government. The PMP must be prepared in the Contractor’s format, on standard letter size paper, with pages sequentially numbered, and conform to the following:

(a) Cover Page. The PMP must contain a cover page as described in Section 2.0 General Notes of Attachment J2.

(b) Record of Review and History Page. This page must include the review and approval dates of all changes to the PMP.

(c) Descriptive Material. As 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 PMP must be delivered to the FAA As specified in

Block 15 of the CDRL.

(d) Table of Contents and Acronyms List. The PMP must include a table of contents and a definition list of all acronyms used.

(10.2 Specific Contents. The following sections must be explicitly identified in the PMP:

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

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

Continued)

11. Distribution Statement

Distribution authorized to U.S. Government agencies and their contractors; Administrative or Operational Use; {insert Contract

Award (CA) date}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

Page J2-8

CONTINUATION SHEET Page 2 of 4

FOR FAA-DNTS-A001

(c) Program 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.

1. Program Manager. The Contractor must specify an individual who serves as the Program Manager and must manage the contract using the PMP.

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

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

4. Personnel. The plan must list the Key Personnel staffing of the Contractor’s management office that directs the contractual tasks, as well as projects, programs and assists in completing the contract. The list must include the identity, background, and work experience of the personnel assigned to fill these positions.

5. 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. The phase identification is left to the Contractor to determine, but must consider contract award through final delivery (quality assurance events, configuration management milestones, testing, first accepted delivery, and final item acceptance to name a few). An example of phases for staffing may be:

Phase 1: Contract Award to Factory Acceptance Testing (FAT) - to include activities for the Post Award

Conference, Configuration Management and Quality Control Audits/Validation, Provisioning Guidance Conference, Training Guidance Conference, Logistics (labeling/scanning, shipping, training, and repair) establishment, test planning (Procedure Development and Execution), and contract deliverables development and updates.

Phase 2: FAT to Production Acceptance Testing (PAT) - to include activities for the Configuration Management and

Quality Control Audits, Logistics (labeling/scanning, shipping, training, and repair), establishment of Product

Baseline, Test Planning (Procedure Development and Execution), and contract deliverables development and updates. The Product Baseline includes the Functional Configuration Audit (FCA) and Physical Configuration

Audit (PCA).

Phase 3: PAT to First Delivery - to include activities for the Configuration Management and Quality Control Audits, Logistics (labeling/scanning, shipping, training, and repair), test execution, and contract deliverable updates.

Phase 4: First Delivery to Final Delivery - to include activities for the Configuration Management and Quality

Control Audits, Logistics (labeling/scanning, shipping and repair), test execution, and contract deliverable updates.

6. Policies and Procedures. This section must describe the internal policies, standard business practices (including Earned

Value Management), and procedures to be used in managing the contract. This section must reference any internal or external documents used in by the Contractor (such as ISO 9001:2000) in the execution of the contract.

7. Relationships. This section must describe the working relationships the Contractor will establish with the Government

(FAA) and any subcontractors supporting the procurement of the equipment. These relationships must identify any actions that are required to comply with the contract such as component delivery from a subcontractor or review responses from the FAA

8. Subcontractor Management. This section must 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 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.

9. Schedule. An Integrated Master Schedule (IMS) In accordance with (IAW) SOW section C3.1.2 and CDRL A002 must be included as Appendix A of the PMP.

Page J2-9

CONTINUATION SHEET Page 3 of 4

10. Schedule Management. This section must provide a detailed description of how the Contractor will implement an integrated, defined, planning and control system for schedule management. 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.

11. Resource Planning. This section must 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.

This must correlate to the phasing of staffing identified previously.

12. Risk Management. This section must describe the internal approach and method for the identification, assessment, and mitigation of program risks. This approach must 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. This section must describe the

Contractor’s procedures to develop a plan of action to mitigate risk. This section must describe classifying risks against their likelihood and consequences (impact). Likelihood must be defined by five levels that range from A to E. E is classified as near certain (mitigations or workarounds do not exist), D is highly likely (mitigation does not exist but workaround might work), C is likely (may mitigate or workarounds are likely to resolve), B is low (mitigation in place with minimal oversight required), and A is not likely (mitigation in place and risk is avoided). Consequences must be defined by five levels that range from 1 to 5 as to the impact on technical, schedule or costs items. 5 is classified as high that would result in unsuccessful contract execution, 4 is significant and jeopardizes successful contract execution, 3 is moderate with limited impact to contract execution, 2 is minor impact, and 1 is low impact.

13. Action Item Management. This section must describe the approach and methodology for identification and tracking of action items that arise from Government meetings, comments to deliverables, and correspondence. An Action Item

Register must be developed in contractor format that is used to track action items and follow the process and procedures identified in Programmatic Tracking and Reporting.

14. Problem Tracking: This section must describe the process for identifying and tracking problems with regard to risks, action items, and contract execution and requirements. Problems must be tracked by the Contractor whenever they are identified. Risks and action item identification is previously detailed. Problems with contract execution and requirements that result from software, hardware, documentation, or quality and configuration management failures must be tracked by the Contractor. This section must describe how the data will be used and tracked to maintain a status of the contract.

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

1. Manufacturing Methods and Production Flow. This section must provide a production flow utilizing a 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.

2. Capability and Capacity. This section describes the data and information used to determine the Contractor and subcontractor(s) 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. The Contractor must provide a list of all subcontractors and major vendors indicating the services/materials to be supplied by each. The

Contractor must also describe the capability to establish and maintain a depot level support function for the nationwide deployment of the equipment.

(e) Logistics Management. This section describes the process and procedures used for shipping contract deliverables, training management, control of Logistics Management Information (LMI), and repair (warranty and non-warranty) actions.

1. Marking, Packaging, and Shipping. This section must describe the labeling/scanning, shipping process for initial contract deliverables and for defective unit to and from the Contractor facility. For delivery requirements (labeling/scanning, packaging and marking), the Contractor must describe how it does or will comply with the requirements of Section D of the contract.

2. Training Management. This section must include a description of training management activities. It must identify how existing training materials are planned to be developed to comply with FAA Order 3000.22 using resources, FAA input requirements, and schedule updates.

Page J2-10

CONTINUATION SHEET Page 4 of 4

3. LMI Control. This section must include a description of how the Logistic Management Information (LMI) will be updated based on a change to the FAA Product Baseline. This must correlate to information presented in the Configuration

Management Plan, Appendix B to the PMP.

4. Repair. For defective units requiring repair, the process must demonstrate compliance to section C.3.5.8 of the contract.

This includes procedures for initiation of a repair request and shipping from the FAA (FOB Destination) to the Contractor repair facility. It includes the management of the FAA Form 4650-10, maximum repair time in compliance with H.3.e, and shipment to the FAA in compliance with C.3.5.8 of the contract. The FAA Form 4650-10 must be returned to the

FAA documenting the repair action necessary to return the defective unit to service.

(f) Quality Control, Performance Evaluation, and Contractual Compliance. A Quality System Plan (QSP) IAW SOW section

C3.1.3 and CDRL A003 must be included as Appendix B of the PMP.

(g) Configuration Management. A Configuration Management Plan (CMP) IAW SOW section 3.2 and CDRL A004 must be included as Appendix C of the PMP.

Page J2-11

Telecommunications System

(DNTS)

A002 Integrated Master Schedule

4. Authority 5. Contract Reference 6. Requiring Office

FAA-DNTS-A002 SOW : C.3.1.3 AJM-313

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

Yes A C See Block 14.

12. Date of First

See Block 14

13. Date of Subsequent

See Block 14.

Addressee Copies Reg. Repro

Block 10: The Integrated Master Schedule (IMS) must be maintained and updated monthly through In Service Decision (ISD) and As Ordered following ISD.

Block 12: Initial delivery IAW CLIN A0020 must be with Program Management

Plan (PMP) (CDRL A001)

Block 13: Subsequent submissions or updates to this CDRL are due no later than

15 calendar DARC. Subsequent submissions must be fully “statused” to the end of the previous month

For schedule development purposes, the Government review period will be ten (10) calendar days from the date of submission.

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

Page J2-12

DATA ITEM DESCRIPTION Page 1 of 2

Integrated Master Schedule FAA-DNTS-A002

3. Description/Purpose

3.1 The Integrated Master Schedule (IMS) serves the Contractor’s internal schedule management needs and provides the Contractor a means to report schedule plan and schedule status to the Government.

4. Approval Date (YYYY/MM/DD) 5. Office of Primary Responsibility (OPR) 6a. DTC Applicable 6b. GIDEP Applicable

AJM-313

7. Application/Interrelationship

7.1 This Data Item Description (DID) is the basis for the Contractor’s IMS.

7.2 The IMS must be the Contractor’s integrated network logic schedule depicting the flow of work and the task interdependencies necessary to accomplish the program objectives from contract award to In Service Decision (ISD). The IMS must be planned in sufficient detail to evaluate schedule progress and assess the impacts of schedule changes. Sufficient detail is defined as one or two week durations for near term activities (6 months from time-now) and one month for activities further out (past 6 months from time-now) The Contractor must use the IMS as their program schedule tool to manage the project. The IMS must identify the critical path.

7.3 This DID contains the format and content preparation instructions for the IMS to be submitted by the Contractor, as required, by

SOW paragraph C.3.1.2.

10.1 Format. Microsoft Project 2003, or later, must be used to produce and update the IMS. The IMS must be the Contractor’s working schedule and, therefore, can be in the Contractor’s format with the exception of some specified reference (text) fields for traceability. These fields are described in 10.2.

(a) Cover Page. The IMS must contain a cover page as described in Section 2.0 General Notes of Attachment J2.

(b) Record of Review and History Page. This page must include the review and approval dates of all changes to the IMS.

(c) Descriptive Material. As 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 material, if provided, will be included in addition to the IMS. The IMS must be delivered to the FAA as specified in Block 15 of the CDRL.

(d) Acronyms List. A list of all acronyms used with their definitions must be delivered along with the IMS.

10.2 Content. The IMS must contain the following:

(a) The IMS must be a Program Evaluation Review Technique (PERT) network capable of producing graphic representation of time-phased activities and their logical relationships. The IMS must be capable of being displayed in both Gantt and logic schedule format, including the critical path.

(b) The IMS, at a minimum, must include all activities and activity interdependencies of the Contractor, Sub-Contractors, and dependencies on the FAA for all parts of the contract in the SOW. This includes key CDRL deliveries, configuration management activities, integrated logistics support activities, and other major and critical milestones.

(c) The IMS must contain all contractually specified milestones and deliverables, identifying all Government Furnished Equipment

(GFE) or Government Furnished Information (GFI) required to meet those milestones and deliverables. All contractor schedule information delivered to the FAA or presented at program reviews must originate from the IMS.

(d) The IMS must include formal quality control, program management, and configuration management reviews and audits, all key programmatic and technical events, and the preliminary and final submission of all documentation, hardware, and software identified by a Contract Line Item Number (CLIN).

(Continued)

11. Distribution Statement

Distribution authorized to U.S. Government agencies and their contractors; Administrative or Operational Use; {insert Contract

Award (CA) date}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

Page J2-13

CONTINUATION SHEET Page 2 of 2

FOR FAA-DNTS-A002

(e) The IMS must be risk adjusted and supported by risk analysis with appropriate mitigating factors identified. The IMS must be detailed sufficiently that critical and high risk efforts are identified and planned realistically to assure excitability. Additionally, within the near-term (defined as 6 months from time now), it is expected that most activities will be defined in one or two week durations. If a month passes, without any status required, this IMS network will be at an insufficient level of detail. The description must include a 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 are integrated and updated.

(f) The IMS must be extended and expanded as the contract or project unfolds and additional insight is needed (for example, rolling wave detail planning or scope changes). In the near-term (time-now plus 6 months), most activities (80%) must be 1 month or less in duration. If a Contractor activity duration exceeds 1 month, in the near term as defined above, the activity must be broken out into smaller duration activities. Since this is the Contractor’s working schedule, the FAA anticipates that

Contractor activities and constraints will be changed, added or deleted as the IMS is further defined. Restrictions apply only to

FAA milestones. It is understood that negative float may result as the schedule evolves and FAA milestones are not moved until agreement on new FAA milestone dates are determined.

(g) The Contractor must set aside certain reference fields for traceability purposes. These fields must be separate from Microsoft

Project 2003, or later, calculated fields and the baseline fields must not interfere with schedule calculations. These fields must be set aside for each IMS activity:

1. Baseline Start. After the Integrated Baseline Review (IBR) or prior to commencement of any project as appropriate, all

IMS activities must be baselined with an original plan. This field must be populated with the baseline start date for each

IMS activity. This field must not be changed without FAA approval. As the Contractor defines new activities (rolling wave) the Contractor must establish a baseline start date at the time the activity is identified.

2. Baseline Finish. After the IBR or prior to commencement of any project as appropriate, all IMS activities must be baselined with an original plan. This field must be populated with the baseline finish date for each IMS activity. This field must not be changed without FAA approval. As the Contractor defines new activities (rolling wave or changed approach) the Contractor must establish a baseline finish date at the time the activity is identified.

3. Text Fields. Set aside text fields (as many as required) to explain logic changes over time or changes in technical approach as the program progresses.

10.3 Schedule Updates. The Contractor must update and submit the IMS monthly through ISD. The IMS must be submitted in

Microsoft Project including all activities and dependencies at the lowest level (the submittal will show all activities indented under similar tasks). Additionally, the IMS must be the same working schedule used by the Contractor. There must not be two schedules – one for Contractor purposes and one for FAA purposes. Any deviation from this requirement will constitute an unacceptable submittal:

(a) Since this is a Contractor working tool, provided to the FAA on a monthly basis, there are not restrictions on changes to:

1. Activity durations

2. Dependency changes

3. Activity deletions or additions (other than agreed to FAA milestones)

(b) Because there are no restrictions, regarding changes, the Contractor will submit a brief description of any changes that impact, or threaten to impact, a Government controlled milestone. (See item c.) At a minimum, schedule updates must include:

1. Monthly status recorded against each activity, including actual start and finish dates or latest estimated planned start and finish dates.

2. Actual start and actual finish dates, as recorded, must not be later than the status date.

3. Any activity changes such as duration changes, activity deletions, or activity additions

Page J2-14

Telecommunications System

(DNTS)

A003 Quality System Plan

4. Authority 5. Contract Reference 6. Requiring Office

FAA-DNTS-A003 SOW : C.3.1.4 AJM-313

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

Yes A C AS REQ

See Block 14

30 DARC.

Addressee Copies Reg. Repro

Block 12: Initial delivery must be with the Program Management Plan (PMP)

(CDRL A001)

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

Page J2-15

Quality System Plan FAA-DNTS-A003

3. Description/Purpose

3.1 The Quality System Plan (QSP) describes the Contractor’s specific implementation of the quality management system needed to comply with FAA contract requirements. The QSP describes quality objectives, procedures and processes consistent with the requirements of ANSI/ISO/ASQ SAE/ AS9100D. The QSP also addresses specific additional quality requirements contained herein.

3.2 This QSP provides the Government contracting activity a basis for assessment of the quality system and evidence of the

Contractor’s intent to comply with the contract quality requirements.

4. Approval Date (YYYY/MM/DD) 5. Office of Primary Responsibility (OPR) 6a. DTC Applicable 6b. GIDEP Applicable

AJM-313

7. Application/Interrelationship

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

7.2 This DID is used when a QSP is required and the Contractor is responsible for limited system development (modified NDI software and NDI/COTS hardware components).

7.3 This data item description is intended for use with SAE/ AS9100D, Quality Management Systems – Requirements.

7.4 Formal third party registration of the Contractor to SAE/ AS9100D is not required.

7.5 Contractors that have achieved formal third party registration to SAE/ AS9100D are not relieved from requirements for delivering the QSP. Contractors must provide an acceptable Quality System Plan that fully meets the requirements described herein.

7.6 The Contract Data Requirements List (CDRL) (DD 1423 or equivalent) will specify whether deliverable data are to be delivered on paper or electronic media; and whether the document is to be in a given electronic form (such as ASCI or compatible with a specified word processor or other support software).

8. Approval Limitation 9a. References 9b. AMSC Number

Reference: SAE / AS9100D

Source: Society of Automotive Engineers (SAE)

International

400 Commonwealth Drive

Milwaukee WI 53203

Warrendale, PA 15096

(877) 606 - 7323 web - http://www.sae.org email – CustomerService@sae.org

10.1 General Instructions.

(a) Format. Contractor format is acceptable. The QSP must be written in a format the follows the structure of SAE/ AS9100D (as defined and supplemented in Section 10.2). If an established plan or manual is used that is based on other similar standards

(e.g. previous version of AS9100, etc.) it is not necessary to rewrite the plan to reflect the structure of AS9100D. However, a matrix must be provided cross-referencing each paragraph of SAE/ AS9100D and the locations in the QSP where the elements are covered.

(b) Alternate Presentation Styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.

(Continued)

11. Distribution Statement

Distribution authorized to U.S. Government agencies and their contractors; Administrative or Operational Use; {insert Contract

Award (CA) date}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

Page J2-16

FOR FAA-DNTS-A003

10.2 Content. The QSP must be on standard letter size paper, with pages sequentially numbered, and contain the following:

(a) Cover Page. The QSP must contain a cover page as described in Section 2.0 General Notes of Attachment J2.

(b) Record of Review and History Page. This page must include the review and approval dates of all changes to the QSP.

(c) Descriptive Material. As 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 QSP must be delivered to the FAA as specified in

Block 15 of the CDRL.

(d) Table of Contents and Acronyms List. The QSP must include a table of contents and a definition list of all acronyms used.

10.3 Specific Content. The numbers shown follow the format and structure of SAE/ AS9100D. For example, Section 4.1 references (and may supplement) QSP requirements from SAE/ AS9100D Paragraph 4.1. The corresponding QSP paragraph may be numbered 4.1 to follow the structure of the ISO standard. Within this DID, the term ‘Contractor’ is equivalent to ‘organization’ as defined in SAE/ AS9100D. Within this DID, the term ‘product’ refers to developed hardware/software, NDI hardware/software, and modified NDI hardware/software. For all content requirements, the Contractor must describe how their Quality Management System

(QMS) meets the requirements of SAE/ AS9100D and the additional requirements as stated in this DID. If requirements are covered in other plans submitted by the Contractor (e.g. Software Development Plan, Configuration Management Plan), the applicable plan

(including applicable section and paragraph number) can be cross-referenced in the QSP.

(a) Section 4.1 General Requirements. SAE/ AS9100D requirements must be addressed and their application to Contractor’s organization and processes must be explained.

(b) Section 4.2.1 Documentation (General). SAE/ AS9100D requirements must be addressed. The Contractor Quality

Management System documentation must be defined as required by this paragraph. In addition, the Contractor must have documented procedures to address: Design and Development; Purchasing; Production and Service; Customer Property;

Preservation of Product, to include Handling, Storage, and Packaging; and Control of Monitoring and Measuring Devices.

(c) Section 4.2.3 Control of Documents. SAE/ AS9100D requirements must be addressed in addition, documented procedures as additionally required by this DID must be controlled in the same manner.

(d) Section 4.2.4 Control of Records. SAE/ AS9100D requirements must be addressed, in addition, the Contractor must control records for the documented procedures as additionally required by this DID. The QSP must address the availability of records for evaluation by the customer or the customer’s representative. The Contractor must establish and maintain records, which provide evidence that the product has been inspected and/or tested. These records must show clearly whether the product has passed or failed the inspections and/or tests according to defined acceptance criteria. Where the product fails to pass any inspection and/or test, the procedures for control of nonconforming product must apply. Records must identify the inspection authority responsible for the release of product.

(e) Section 5.1 Management Commitment. SAE/ AS9100D requirements must be addressed.

(f) Section 5.2 Customer Focus. SAE/ AS9100D requirements must be addressed.

(g) Section 5.3 Quality Policy. SAE/ AS9100D requirements must be addressed.

(h) Section 5.4 Quality Planning SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs. In addition, when changes to the QMS are planned and implemented, this QSP must be updated to reflect such changes.

(i) Section 5.5 Responsibility, Authority and Communications. SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs. The QSP must describe the management structure responsible for operation of the QMS. In addition to defining the responsibilities and authorities within the organization, top management must ensure that personnel who verify work affecting quality have the organizational freedom and authority from persons directly responsible for developing products or executing process within the project to:

1. Initiate action to prevent the occurrence of any nonconformity relating to product, process, and quality system;

2. Identify and record any problems relating to the product, process, and quality system;

3. Initiate, recommend, or provide solutions through designated channels:

Page J2-17

CONTINUATION SHEET Page 3 of 4

4. Verify the implementation of solutions;

5. Control further processing, delivery, or installation of nonconforming product until the deficiency or unsatisfactory condition has been corrected.

(j) Section 5.6 Management Review. SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs.

Review input must include provisions for customer feedback and recommendations for improvement from the customer quality assurance representative.

(k) Section 6 Resource Management. SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs.

(l) Section 7.1 Planning for Product Realization. SAE/ AS9100D requirements must be addressed for this paragraph. Planning must address requirements for all documented procedures required by this DID. Other related contract plans (e.g.

configuration management plan, test plan) must be identified in this section and interrelationship(s) with the QSP must be explained.

(m) Section 7.2.1 Determination of Requirements Related to the Product. SAE/ AS9100D requirements must be addressed for this paragraph. Requirements review must incorporate applicable contract review activity.

(n) Section 7.2.2 Review of Requirements Related to the Product. SAE/ AS9100D requirements must be addressed for this paragraph. Requirements review must incorporate applicable contract review activity and must consider acceptance criteria.

Review must include consideration of applicable interface requirements.

(o) Section 7.2.3 Customer Communication. SAE/ AS9100D requirements must be addressed for this paragraph. The paragraph must address implementation of effective communications with customer quality assurance representative.

(p) Section 7.3 Design and Development. SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs.

The Contractor must establish and maintain documented procedures (for modified configuration items) to assure that design and development activity conforms to specified requirements. Design and development validation must consider contract acceptance criteria.

(q) Section 7.4 Purchasing. SAE/ AS9100D requirements must be addressed for this paragraph and subparagraphs. The

Contractor must establish and maintain documented procedures to assure that purchased products conform to specified requirements. The Contractor must ensure that incoming product is inspected or verified on receipt as necessary to assure conformance to specified requirements. The customer must have access to all Contractor facilities necessary to determine product conformance. Verification by the customer must not absolve the Contractor of responsibility to provide acceptable product.

(r) Section 5.1 Control of Production and Service Provision. SAE/ AS9100D requirements must be addressed for this paragraph.

The Contractor must plan and control the production, installation and servicing processes that directly affect product quality and must ensure that such processes are carried out under controlled conditions. The Contractor must establish and maintain documented procedures to assure that such controlled conditions meet specified requirements.

(s) Section 7.5.2 Validation of Production and Service Provision. SAE/ AS9100D requirements must be addressed for this paragraph.

(t) Section 7.5.3 Identification and Traceability. SAE/ AS9100D requirements must be addressed for this paragraph.

(u) Section 7.5.4 Customer Property. SAE/ AS9100D requirements must be addressed for this paragraph. The Contractor must establish and maintain documented procedures to assure that customer property is properly controlled.

(v) Section 7.5.5 Preservation of Product. SAE/ AS9100D requirements must be addressed for this paragraph. The Contractor must establish and maintain documented procedures for handling and storage of the product. The Contractor must provide methods for packaging and handling deliverable end-item(s) to prevent damage or deterioration. The Contractor must use designated storage areas or stock rooms for deliverable end-item(s) to prevent damage or deterioration, pending use or delivery.

The Contractor must control packing, packaging and marking processes for deliverable end-item(s) as necessary to ensure conformance to specified requirements.

(w) Section 7.5.6 Control of Monitoring and Measuring Devices. SAE/ AS9100D requirements must be addressed for this paragraph. The Contractor must establish and maintain documented procedures to assure monitoring and measuring devices are correctly maintained and calibrated as needed to assure…