NEXV3 SIR Sect J_Att J02.docx

TABLE OF CONTENTS

693KA8-23-00005

J02-1

ATTACHMENT J02

CONTRACT DATA REQUIREMENTS LIST AND DATA ITEM DESCRIPTIONS

693KA8-23-00005

J02-21

No.

CLIN

No.

Para.

Page No.

2.0 GENERAL NOTES

All Data Item Description (DID) numbers contain the prefix “FAA-UVRT-” 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 training. CDRL numbers all use the same DID four digit-code.

All days are calendar days unless stated otherwise. All submitted electronic material must be in MS Office Professional Plus 2016 or later unless alternative software file format is approved by the Government.

All deliverables must be submitted with a separate cover letter as designated in Block 15 of the CDRL. The cover letter must be on the Contractor’s official company stationery and it must be signed by the Contractor’s designated Program Manager. All deliverables must also be submitted with a cover page. The cover 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 NEXCOM Version 3 (V3) UHF/VHF Radio 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 CAGE Code For [CDRL Title] use the Title of Data Item from CDRL Box No. 2. 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.

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

The “N” is assigned a value indicating the number of days, e.g., 30 DACA.

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

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

17. Price Group. Not used.

18. Estimated Total Price. Not used.

693KA8-23-00005

J02-2

12. Date of First Submission

Submission

30 DARC

15. Distribution

Block 10. Revisions are required when the work, procedures, or tasks being performed differs from the Government approved PMP. Date of submission is 15 days after changes are approved by the Government.

Block 12. The FAA will order the CLINs for the A001 (PMP), A004 (Initial IMS), A005 (QSP) and A006 (CMP) CDRLs simultaneously. The FAA will review the PMP, Initial IMS, QSP and CMP CDRLs concurrently. The Government review period is estimated to be 20 business days from the date of first submission.

Block 13. After receipt of Government comments, the Government estimates 6 hours of In-Process Reviews (IPRs), where an estimated 3 meetings (at up to 2 hours per meeting) will occur. These IPR hours are shared across CDRLs A001, A004, A005 and A006 in order to clarify Government comments made against the first submission of these CDRLs, help to ensure the approach taken to update the subsequent submission of the PMP CDRL will be on track for FAA approval, and maintain the 30 DARC period.

Block 13. For any additional subsequent submission of the PMP CDRL that may be required after the 30 DARC period, in order to fully incorporate Government comments, that subsequent submission is then due 15 DARC. If any changes are discovered after Government approval, see Block 10 remarks above.

AAQ-320

AJM-313

L/DE

L/DE

L/FE

L/FE

N/A N/A

AJM-313

17. Price Group

18. Estimated Total Price

3. Description/Purpose

AJM-313

7. Application/Interrelationship

10. Preparation Instructions

10.1 Format. Electronic deliveries shall be in .docx format and shall be compatible with MS Office Professional Plus 2016 or later unless 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 J02.

(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 in both paper and electronic media products unless otherwise approved by the Government.

(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. Provide an overview of the Contractor’s approach to program, technical, schedule, and risk control. Based on the authority of the program manager, distinguish 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; {03/03/2023}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

(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 (i.e., quality assurance events, configuration management milestones, testing, first accepted delivery, and final item acceptance). 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 Physical Configuration Audit (PCA) - 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: PCA 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 and procedures to be used in managing the contract. This section must reference any internal or external documents used by the Contractor (such as AS9100D) 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 C.3.2.2 and CDRL-A004 must be included as Appendix A of the PMP.

10. Schedule Management. This section must provide a detailed description of how the Contractor will implement an integrated and 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 previously identified.

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 when 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 the requirements of the Statement of Work using resources, FAA input requirements, and schedule updates.

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 C to the PMP.

4. Repair. For defective units requiring repair, the process must demonstrate compliance to Section C.3.6.7 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.6.7 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 C.3.2.3 and CDRL-A005 must be included as Appendix B of the PMP.

(g) Configuration Management. A Configuration Management Plan (CMP) IAW SOW Section C.3.3 and CDRL-A006 must be included as Appendix C of the PMP.

End of DID FAA-UVRT-A001

12. Date of First

Submission See Block 14.

15. Distribution

Block 10. The Contractor must keep this document updated as revisions occur. The Contractor must submit any updated documents to the FAA.

Block 13. Updates to this CDRL are due no later than 1 business day after close of the Contractor’s fiscal month following initial approval.

The CWBS must be maintained and updated to reflect Contractor’s changes in work scope up through In-Service Decision (ISD) and as ordered following ISD.

AAQ-320

AJM-313

L/DE

L/DE

L/FE

L/FE

N/A

AJM-313

17. Price Group

18. Estimated Total Price

3. Description/Purpose

3.1 This data item documents the CWBS.

AJM-313

7. Application/Interrelationship

10. Preparation Instructions

10.1 Format. Electronic deliveries must be compatible with MS Office Professional Plus 2016 or later unless alternative software is approved by the Government.

1. Cover Page. The CWBS must contain a cover page as described in Section 2.0 General Notes of Attachment J02.

a) Line Number. Enter the line number for each CWBS. Line numbers should be in sequence starting with 1.

b) CWBS Element. Enter the title of the CWBS Element (using the specific name or nomenclature, when applicable), intended to reflect the level. Level 1 is the total contract, Level 2, 3 etc., are successively lower levels of the program.

c) CWBS Code. Enter the CWBS code, if applicable.

d) Contract Line Item(s). Enter the number of the contract line item(s) which is (are) associated with the CWBS element, if applicable.

e) SOW paragraph number(s). Enter the paragraph number(s) from the SOW, if applicable.

(Continued)

11. Distribution Statement

Distribution authorized to U.S. Government agencies and their contractors; Administrative or Operational Use; {03/03/2023}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

CONTINUATION SHEET Page 2 of 2

FOR FAA-UVRT-A002

10.5 Format

CONTRACT

NO: ___________________________

DATE:

CODE

End of DID FAA-UVRT-A002

12. Date of First

Submission See Block 14.

15. Distribution

The CWBSD must be maintained and updated IAW the Contract Work Breakdown Structure (CWBS) CDRL-A002.

Block 10. The Contractor must keep this document updated as revisions occur. The Contractor must submit any updated documents to the FAA.

Block 13. Updates to this CDRL are due no later than one (1) business day after close of the Contractor’s fiscal month following initial approval.

The CWBSD must be maintained and updated to reflect Contractor’s changes in work scope up through In-Service Decision (ISD) and As Ordered following ISD.

AAQ-320

AJM-313

L/DE

L/DE

L/FE

L/FE

N/A

AJM-313

17. Price Group

18. Estimated Total Price

DATA ITEM DESCRIPTION

3. Description/Purpose

3.1 This data item documents the CWBS dictionary required to define and describe the elements in the CWBS.

AJM-313

7. Application/Interrelationship

10. Preparation Instructions

10.1 Format. Electronic deliveries must be compatible with MS Office Professional Plus 2016 or later unless alternate software is approved by the Government.

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

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

10.2 Content. The CWBS must contain a dictionary to define and describe the elements in the CWBS structure. The CWBS dictionary must describe the effort and tasks associated with every CWBS element and provide a complete description of the technical and cost content of each CWBS element. The definition must describe the efforts, tasks, tests, components, etc., that are included in the CWBS element by the Contractor.

End of DID FAA-UVRT-A003

11. Distribution Statement

Distribution authorized to U.S. Government agencies and their contractors; Administrative or Operational Use; {03/03/2023}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

12. Date of First

Submission See Block 14.

15. Distribution

Block A. 0054A, 0054B, 0054C, 6054A, 7054A, 8054A, 9054A, and 10054A.

Block 10: CDRL A004 Integrated Master Schedule (IMS) must be maintained and updated monthly until In-Service Decision (ISD) is achieved (i.e., 0054B) or As Ordered following ISD (i.e., 0054C). Delivery of Monthly or As Ordered A004 CDRLs must be provided no later than 15th of each month.

Block 12. Initial delivery of CDRL A004 must be Appendix A of the Program Management Plan (PMP) IAW CDRL-A001. The FAA will review the A001 (PMP), A004 (Initial IMS), A005 (QSP) and A006 (CMP) CDRLs concurrently. For schedule development purposes, the Government review period is estimated to be 20 business days from the date of submission.

Block 13. After receipt of Government comments, the Government estimates 6 hours of In-Process Reviews (IPRs), where an estimated 3 meetings (at up to 2 hours per meeting) will occur. These IPR hours are shared across CDRLs A001, A004, A005 and A006 in order to clarify FAA comments made against the first submission of these CDRLs, help to ensure the approach taken to update the subsequent submission of the Initial IMS CDRL will be on track for FAA approval, and maintain the 30 DARC period.

Block 13. For any additional subsequent submission related to the initial IMS CDRL (A004, 0054A) that may be required after the 30 DARC period, in order to fully incorporate Government comments, that subsequent submission is then due 15 DARC. Block 13. Updates related to FAA comments provided against any Monthly submissions of the IMS are to be incorporated within the next Monthly submission. Updates related to FAA comments provided against any As Ordered submissions of the IMS are due no later than 15 calendar DARC. The Government review period is estimated to be 15 business days from the date of first submission.

AAQ-320

AJM-313

L/DE

L/DE

L/FE

L/FE

N/A

AJM-313

17. Price Group

18. Estimated Total Price

3. Description/Purpose

3.1 The IMS serves as the Contractor’s internal schedule management tool and provides the Contractor a means to report schedule plan and status to the Government.

AJM-313

7. Application/Interrelationship

10. Preparation Instructions

10.1 Format. Microsoft Project 2016, or later, must be used to produce and update the IMS. The IMS can be in the Contractor’s format with the exception of some specified reference 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 J02.

(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 IMS must be delivered to the FAA in both paper and electronic media products unless otherwise approved by the Government.

(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 a graphic representation of time-phased activities and their logical relationships capable of being displayed in both Gantt and logic schedule format, including the critical path.

(b) The IMS, at a minimum, must identify all CDRL delivery dates, configuration management activities, quality control activities, integrated logistics support activities, and other major and critical milestones. The IMS must include all activities and activity inter-dependencies of the Contractor, subcontractors, and dependencies on the FAA for all parts of the contract in the SOW.

(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; {03/03/2023}. Other requests for this document must be referred to FAA AJM-313, Air Ground Voice Communications Team.

(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 executability. Additionally, within the near-term (defined as six (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 must be 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 six (6) months), most activities (80%) must be one (1) month or less in duration. If a contractor activity duration exceeds one (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.

(g) The Contractor must set aside certain reference fields for traceability purposes. These fields must be separate from Microsoft Project 2016, or later. User-defined fields and baseline fields must not interfere with schedule calculations. These fields must be set aside for each IMS activity:

1. Baseline Start. 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. 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) the Contractor must establish a baseline start 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 on a monthly basis 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 not 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 10.1(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.

End of DID FAA-UVRT-A004

12. Date of First

Submission

30 DARC

15. Distribution

Block 10. Revisions are required when the work, procedures, or tasks being performed differs from the Government approved QSP. Date of submission is 15 days after changes are approved by the Government.

Block 12. Initial delivery of CDRL A005 must be Appendix B of the Program Management Plan (PMP) IAW CDRL-A001. The FAA will review the A001 (PMP), A004 (Initial IMS), A005 (QSP) and A006 (CMP) CDRLs concurrently. The Government review period is estimated to be 20 business days from the date of submission.

Block 13. After receipt of Government comments, the Government estimates 6 hours of In-Process Reviews (IPRs), where an estimated 3 meetings (at up to 2 hours per meeting) will occur. These IPR hours are shared across CDRLs A001, A004, A005 and A006 in order to clarify FAA comments made against the first submission of these CDRLs, help to ensure the approach taken to update the subsequent submission of the QSP CDRL will be on track for FAA approval, and maintain the 30 DARC period.

Block 13. For any additional subsequent submission of the QSP CDRL that may be…