ATEPS II Draft SIR_Sections C - 02.28.23.pdf

PDF 1 MB Posted

Attached to
AAQ-410_ATEPS_II_ INDUSTRY Q&A UPDATE 7. 13. 23 Federal contract opportunity
Solicitation number
AAQ-410_ATEPS_II_DRAFT_SIR_SECTIONS_02282023
Issued by
Department of Transportation Federal Aviation Administration Headquarters

View the file

Other files for this federal contract opportunity

On GovTribe

Work with this file on GovTribe

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

Text version

DRAFT

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

SECTION C – Statement of work

TABLE OF CONTENTS

SECTION C – Statement of work

C.1 INTRODUCTION

C.1.1 Objective

C.1.2 Background

C.2 SCOPE

C.2.1 General

C.2.2 Contract Program Management

C.2.2.1 Program Manager

C.2.2.2 Program Management Support Costs

C.2.2.3 Staffing, Recruitment, and Workforce Development Plan

C.2.3 Transition

C.2.3.1 Transition In Plan

C.2.3.2 Transition Out Plan

C.2.4 Contract Management Reporting

C.2.4.1 Monthly Status Report (MSR)

C.2.4.2 Monthly Cost Report (MCR)

C.2.4.3 Monthly Contractor Tracking Report (MCTR)

C.2.4.4 Quarterly Program Management Reviews (PMR)

C.2.5 Meeting and Attendance

C.2.5.1 Post-Award Conference

C.2.6 Government Furnished Property

C.2.7 Data Deliverables

C.2.8 Applicable Documents

C.2.8.1 Applicable Documents Conflict Mitigation

C.2.9 Task Order (TO) Management

C.2.9.1 Task Order (TO) Management Costs

C.2.10 Quality Management Compliance

C.2.10.1 Quality Control/Quality Assurance

C.2.11 Security Requirements

C.3 CORE CAPABILITIES

C.4 FUNCTIONAL TASK AREAS

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

C.4.1 Program Management Support

C.4.2 Financial and Acquisition Management

C.4.3 Standards and Rulemaking

C.4.4 Systems Engineering Support

C.4.5 Software Engineering Support

C.4.6 Hardware Engineering Support

C.4.7 Human Factors Engineering Support

C.4.8 Information System Security Support

C.4.9 Safety Management Support

C.4.10 Implementation Support

C.4.11 Unmanned Aircraft Systems (UAS) and Emerging Technologies Support . 22

C.4.12 Testing Support

C.4.13 Configuration Management Support

C.4.14 Performance and Data Management Analysis

C.4.15 Meteorological Support

C.4.16 Training Assistance Support

C.4.17 Logistics Support

C.4.18 Facilities Support

C.4.19 Operational Support

C.4.20 Data Analytics

C.4.21 Strategic Planning Support

C.4.22 Management Development and Integration

C.4.23 Business Management Support

C.4.24 Risk, Issue, and Opportunity (RIO) Management Support

C.4.25 Communications Support

C.5 DELIVERABLES

C.6 TRAVEL

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

SECTION C – Statement of Work

C.1 INTRODUCTION

C.1.1 Objective The objective of the Air Traffic Engineering and Program Support (ATEPS) II contract is to obtain a broad set of technical and professional services to support operations in the Federal Aviation Administration’s (FAA) Air Traffic Organization (ATO) Program Management Organization (PMO).

C.1.2 Background The ATO is a Line of Business (LOB) within the Federal Aviation Administration (FAA), whose mission is to provide a safe, efficient, responsive air transportation system that serves the nation and supports the global aviation community. The PMO is one (1) of eight (8) service units comprising the FAA’s ATO. The PMO was formed to bring the majority of the FAA’s major acquisition programs, business solutions, and infrastructure programs under one umbrella, allowing for better cost controls and economies of scale, information sharing, consistent risk mitigation, and more effectively develop integrated teams and plans that span multiple lines of business, National Airspace System (NAS) systems, and operational communities.

The PMO participates in NAS management, development, engineering, and deployment activities through its four (4) directorates: Integrated Services & Analysis (AJM-1), Air Traffic Systems (AJM-2), Enterprise Services (AJM-3), and Surveillance Services (AJM-4).

• The Integrated Services & Analysis Directorate (AJM-1) focuses on program control, crosscutting analysis and integration, and special initiatives. AJM-1 strengthens the relationships of Mission Support Services, Aviation Safety, and the NextGen organizations, among other programs to ensure value for the operation and promised NextGen benefits for airspace users.

• The Air Traffic Systems Directorate (AJM-2) is responsible for developing, deploying, and operating systems that deliver safe and secure services to all segments of the NAS, including systems that support decision-making for air traffic flow managers and systems that provide services directly to pilots for improved safety and efficiency.

• The Enterprise Services Directorate (AJM-3) develops, acquires, deploys, maintains, sustains, and improves navigation, communications, weather, and aeronautical information products and services for the NAS. Navigation Services covers projects in the following areas: Global Positioning System (GPS) Satellite-Based Augmentation, GPS Ground- Based Augmentation, Ground Systems, Lighting Systems, and Technical Support.

Communications Services provides communications and telecommunications services consistent with International Civil Aviation Organization (ICAO) standards required for air traffic control within the NAS. It provides communications infrastructure and services for the Department of Defense (DOD) to ensure interoperability with the NAS. Weather services provide sensor, processor, and distribution systems required to provide accurate forecasts for timely air traffic decisions. Through unique customer/client relationships and

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work customer-derived requirements, execution of full life-cycle service has the capability to define, design, build, deploy, commission, operate, support, and decommission communications, navigation, and weather services.

• The Surveillance Services Directorate (AJM-4) focuses on the surveillance systems that provide the complete picture of operations taking place in the NAS. These systems range from traditional ground-based radar to more advanced GPS based positioning systems.

To achieve the Agency Strategic Priority goals and organizational mission objectives, professional and technical support services are required to support the existing and future NAS initiatives. This Statement of Work (SOW) sets forth a broad set of technical and professional services required to support operations in the PMO and other FAA LOBs. Support is required for, but not limited to, the following mission critical programs: Air Traffic Management; Decision Support Systems;

Surveillance Services; Terminal Field Operations; EnRoute and Oceanic 2nd Level Engineering;

Communications, Information & Network Programs; Navigation Programs; Aviation Weather and Aeronautical Services; and Data Communications. These programs require ongoing maintenance, upkeep, and enhancements through transition, integration, and implementation of the NAS modernization and transition to the NextGen Air Traffic System.

C.2 SCOPE

C.2.1 General This effort will provide support to program management, system engineering and development, and implementation efforts for ATO’s NextGen programs and systems aimed at enhancing the safety, efficiency, and capacity of the NAS.

This SOW is comprised of distinct functional task areas that establish the scope of the contract.

These functional task areas may be grouped to support a range of technical, operational, management, and administration disciplines found in PMO’s portfolio of programs and programs of other FAA LOBs. Each directorate will identify program specific tasks and activities that require functional expertise to deliver. Requirements within the scope of the activities, tasks, and functional areas will be identified, defined, and aggregated under specific, individually funded Task Orders (TOs). A sampling of programs the Contractor must be expected to support are included in Attachment J-2, Examples of Programs to Support.

C.2.2 Contract Program Management The Contractor must manage the contract in accordance with the Standard Operating Procedures (SOPs) identified in Attachment J-3, Standard Operating Procedures. The SOP describes the PMO’s processes, including, but not limited to: resource and task requirements, subcontractor authorization, travel authorization, overtime (OT), other direct costs (ODCs), and invoice reviews, etc.

C.2.2.1 Program Manager The Contractor must appoint a Program Manager to have the overall responsibility, authority, and accountability for controlling and coordinating all work performed under this contract. The Contractor’s Program Manager must be the main point of contact to the FAA Program Manager

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work and the FAA Contracting Officer’s Representative (COR).

C.2.2.2 Program Management Support Costs Contract-level program management support costs (“PM Costs”) encompass support for contract-level management, directed proposal preparation, reporting requirements (see Section F.4, Deliverables, Delivery Schedule, and Delivery Format), and related travel and meeting attendance costs associated with the Contractor’s program management staff, as it relates to the overall management of this IDIQ contract. As a result, PM Costs are allocated among all TOs issued under this contract. Contractors may elect to recover PM Costs through an acceptable accounting practice as defined in the Contractor’s accounting policies and procedures.

C.2.2.3 Staffing, Recruitment, and Workforce Development Plan The Contractor must recruit, and staff qualified personnel to perform the efforts required under this contract in accordance with the Government-approved Staffing, Recruitment and Workforce Development Plan (CDRL C-0001). A finalized plan is required within fifteen (15) business days after contract award. This plan must describe the staffing and resources to be used in performance of the ATEPS II contract. The plan must include recruitment procedures and policies to be utilized to recruit and retain qualified personnel, including procedures used to meet the requirements of a newly awarded TO. The plan must describe employee benefits and incentive programs that induce long-term retention and employee continuity. The plan must address the source and availability of resources for utilization on this contract.

C.2.3 Transition The Contractor must recognize that the services under this contract are vital to the Government and must be continued without interruption and that, upon contract expiration, a successor, either the Government or another Contractor, may continue them.

C.2.3.1 Transition In Plan The Contractor must prepare a draft transition plan in response to the SIR that facilitates the accomplishment of a seamless transition from the incumbent to an incoming Contractor. A finalized transition plan is required within fifteen (15) business days after award. This plan must include a comprehensive description of the approach to migrating ATEPS II services from the concluding contract/Contractor to full performance under the new contract, referred to as the Transition In Plan (CDRL C-0002). The Contractor must describe the sequence of activities from the contract award through the full implementation of the contract services. The Contractor must specify actions they expect from the FAA during this period. The Contractor must address the transition of resources and personnel and describe how its transition approach will not negatively affect the current ATEPS I contract for services.

The Contractor must describe plans to acquire and orient the required number of fully qualified personnel to the contract in a timely manner and must address risk mitigation for all identified risks, as well as address the need for any FAA guidance, assistance, or orientation deemed necessary during the transition period. The plan must address how knowledge transfer will be accomplished between the outgoing Contractor(s) to the incoming ATEPS II Contractor(s).

The transition plan must include a detailed schedule denoting all major transition activities. The

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

FAA anticipates a ninety (90) business day transition period to fully undertake ATEPS II work.

The schedule must reflect the proposed transition approach and address all significant Contractor and all FAA activities required for the planning and execution of the contract. The Contractor must also include with the schedule an assessment of schedule risks and mitigation activities. At a minimum, the schedule must include:

1. Program management process,

2. Points of contact,

3. Description of the Contractor activities expected for the planning and execution of the contract during the transition to include any recommended relocation of personnel,

4. Transition or placement of TO personnel,

5. Appropriate Contractor to Contractor coordination to ensure a seamless transition,

6. Identify schedules and milestones, and

7. Identify actions required of the Government.

C.2.3.2 Transition Out Plan The Contractor must prepare a Transition Out Plan no later than Ninety (90) business days prior to the end of the contract (CDRL C-0003). The transition out plan must include the transfer of Government Furnished Property (GFP), Government Furnished Information (GFI), and Government Furnished Equipment (GFE), furnished during the performance of the contract, back to the FAA. The plan must describe the contractor’s approach to ensuring a smooth, seamless transition to the successor Contractor at the conclusion of the ATEPS II contract.

The Contractor must furnish transition-out services Ninety (90) business days prior to contract expiration while continuing to fully provide the services required under the ATEPS II Contract.

Transition out services may include, but are not limited to:

• Knowledge transfer to the incoming service provider, and

• Providing necessary personnel records and all Contractor-maintained, Government-owned documentation developed or maintained under ATEPS II to the FAA, as requested by the

CO.

C.2.4 Contract Management Reporting

C.2.4.1 Monthly Status Report (MSR) The Contractor must respond to informal requests from Government points-of-contact via electronic mail (e-mail) or verbally, as applicable, regarding the status of Contractor-provided services and any issues affecting the delivery of services ordered under this contract. The Contractor must provide Monthly Status Reports (MSR) as CDRL C-0004 using the template in Attachment J-4. The MSR must: (1) summarize the services delivered the previous reporting period, including the current status of major events and milestones, (2) provide any risks being tracked from previous months or identified within this month and mitigation approaches, the Contractor’s analysis of those metrics, and any associated conclusions or recommendations and

(3) forecast of potential new requirements.

The content, format, and due date of the MSRs are designated in this section and the appropriate

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

CDRL. The Government will have the opportunity to respond to the MSR report within a mutually agreed period. Responses would normally be provided two weeks after submission by the Contractor. If it is necessary for the Contractor to provide additional information to Government representatives, this period may be extended as appropriate. Any discrepancies and/or significant issues must be addressed in the Program Management Reviews (PMRs).

C.2.4.2 Monthly Cost Report (MCR) The Contractor must provide Monthly Cost Reports (MCR) as CDRL C-0005. The MCR must use the template provided in Attachment J-5, beginning thirty (30) business days after contract award.

The MCR must cover all TOs. The MCR must provide a status of expenditures in relation to the proposed cost baseline and must be directly traceable to the invoices submitted by the Contractor identifying the work of personnel charged to a particular task.

C.2.4.3 Monthly Contractor Tracking Report (MCTR) The Contractor must provide Monthly Contractor Tracking Reports (MCTR), CDRL C-0006, of its entire staff and all subcontractor staffing using the template in Attachment J-6. The MCTR is due monthly, thirty (30) business days after contract award.

C.2.4.4 Quarterly Program Management Reviews (PMR) Program Management Reviews (PMR) will begin ninety (90) business days after contract award and continue quarterly as CDRL C-0007. The PMRs must address program accomplishments, technical, management, and cost issues as needed to reflect current issues, risks, and topics of interest. During PMRs, the Contractor must report on progress toward Directorate goals and report performance metrics in accordance with the reportable elements identified in the Government Quality Assurance Surveillance Plan (QASP), included in Attachment J-7. Briefing slides must be provided no later than five (5) business days prior to a PMR using the Quarterly PMR Briefing Template provided as Attachment J-8.

C.2.5 Meeting and Attendance As requested by the CO or COR, participate in technical or programmatic meetings at Government-designated facilities and/or the Contractor’s facilities. The Government will indicate whether participation must be in-person or whether it may be virtually, depending on the nature of the meeting. The personnel representing the Contractor must have the requisite knowledge and skills to discuss the topics identified on the meeting agenda.

As requested by the Government, the Contractor must prepare and submit agendas (CDRL C- 0008), minutes (CDRL C-0009), and presentation materials for meetings and reviews. Support of meetings includes the Contractor’s conduct of the Post Award Conference. Agendas must be provided three (3) calendar days prior to any meetings. Meeting minutes must be provided within five (5) calendar days following any meetings.

C.2.5.1 Post-Award Conference The Contractor must participate in a post-award conference that will be held within thirty (30) business days after contract award. The purpose of the post-award conference is to aid both the Contractor and the Government in achieving a clear and mutual understanding of all contract requirements and identifying and resolving potential problems. The CO is responsible for

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work establishing the time and place of the conference and will notify the appropriate Government representatives and the Contractors. The conference may be conducted at a location within the Washington, DC, commuting area at the Government’s discretion. The Contractor further agrees to attend post-award conferences on TOs as required. The TO post-award conferences will establish work level points of contact for the TO, determine the TO administration strategy, roles and responsibilities, and ensure prompt payment and TO close-out.

C.2.6 Government Furnished Property All Government Furnished Property (GFP), to include information, material, and equipment, will be specified within the individual TO. If Task Orders are performed in Government provided facilities, the FAA will provide access to Government controlled facilities, equipment, and materials for daily business use of staff to accomplish the functions described within this SOW.

This includes, but is not limited to: office space, laptop computers, desktop computers, desk phones, shared printers, office supplies, and requisite consumable materials.

The Contractor must use government-furnished property (GFP) solely for purposes related to the execution of work required within the scope of the ATEPS II contract. The Contractor must establish and enforce procedures that: (1) safeguard, maintain oversight and control, and (2) prevent unofficial or unauthorized use of all GFP within its control.

The FAA will provide the Contractor with all necessary information to perform all services described in this SOW.

C.2.7 Data Deliverables Specific technical data requirements may be included in the individual TO issued under this contract.

C.2.8 Applicable Documents In providing the ATEPS II services required under this contract, the Contractor must comply with the applicable FAA orders, directives, and policies. Applicable AMS policy/guidance, FAA/DOT orders, process guidelines, military standards, or other relevant documents will be specified and identified as references within the individual TOs.

The Contractor is responsible for reviewing all applicable documents and understanding their impact on the delivery of the required services. Applicable documents are subject to revision, and it is the Contractor’s responsibility to ensure that the most current version of each document is used and that new applicable documents are adopted. FAA orders and notices can be found at:

https://www.faa.gov/regulations_policies/orders_notices/. FAA orders referenced in this SIR include:

• 9550.8, Human Factors Policy,

• 1370.121, FAA Information Security and Privacy Program & Policy,

• 1600.1, Personnel Security Program,

• 1600.2, Classified National Security Information (CNSI) and,

• 1600.75, Protecting Sensitive Unclassified Information (SUI).

https://www.faa.gov/regulations_policies/orders_notices/

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

C.2.8.1 Applicable Documents Conflict Mitigation

If the requirements of this SOW and the referenced applicable documents are in conflict, this SOW has precedence over all documents referenced herein.

If the Contractor identifies a potential conflict between any referenced applicable documents or sections of this SOW, the Contractor must advise the FAA Contracting Officer (CO) for resolution.

If the Contractor believes any revision to an applicable document is cause for an adjustment to the contract, the Contractor must immediately notify the CO.

C.2.9 Task Order (TO) Management

Task Order management is a mandatory element for all TOs placed under this contract. Task Order management must provide the appropriate program management and project control necessary to manage the work; ensure that the cost, schedule, and quality requirements for each TO are continually tracked, and the status communicated to the FAA, and ensure that each TO is successfully completed.

When the FAA orders work under this contract, it will issue individually funded TOs that identify and define specific requirements within the Functional Areas listed in Section C.4. The Contractor, in response to TOs issued under this contract, must furnish the necessary personnel, supplies, materials, data, equipment, facilities, travel, and other services to successfully satisfy the requirements of specific individual Task Orders.

C.2.9.1 Task Order (TO) Management Costs

(a) Administrative TO Management costs encompass administrative support for efforts performed under a TO and include responsibilities such as TO invoicing, contract and subcontract management, resume and deliverables submissions, TO travel requests, administration of Government Furnished Property or Government Furnished Information, TO financial reporting, and TO close-out support.

(b) Technical TO Management costs encompass direct labor for the technical performance of a TO and include performance management responsibilities such as TO staffing and oversight, TO schedule and cost compliance, quality control of deliverables, directing subcontractor performance, and maintaining customer relations.

(c) Contractors may elect to recover these administrative and technical TO management costs through a customary accounting practice as defined in the Contractor’s accounting policies and procedures. Any such recovery practice must be included in the buildup of the Contractor’s fully burdened labor rates and not allocated to any separate cost element under the TO, including ODCs.

C.2.10 Quality Management Compliance The Contractor is responsible for ensuring the quality of all work efforts and deliverables, cost

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work control, and adherence to schedules.

C.2.10.1 Quality Control/Quality Assurance The Contractor’s PMO must include a Quality Control/Quality Assurance (QC/QA) function that is responsible for assessing and maintaining the quality of services and products provided under this contract. The Contractor must prepare and submit a Quality Management Plan (QMP) (CDRL C-0010) in response to the SIR, which describes the QC/QA systems and processes used to measure and ensure the quality of ATEPS II services and products. A finalized transition plan is required within fifteen (15) business days after award.

The QC/QA must be completed in accordance with applicable FAA orders and policies referenced in the individual TOs and as specified in Section C.2.8. The Contractor must implement and maintain QC/QA systems and processes that comply with the Government-approved QMP.

The Contractor must analyze the quality measurements, advise the Government when deficiencies and negative trends are identified, and provide the Government with a plan to improve quality in those areas in the Monthly Status Report (C-0004). The Contractor must take corrective action to improve quality based on the plans provided in CDRL C-0010.

C.2.11 Security Requirements Security Requirements applicable to the work performed under each TO may be identified within the individual TO. Additional security clearances may be needed for specific TOs. Candidates identified for performance under those TOs must hold or be eligible to obtain the requisite security clearance.

C.3 CORE CAPABILITIES

The following, in alphabetical order, are descriptions of the Core Capabilities. Some Core Capabilities are techniques that the Contractor will be required to use when performing tasks within the functional areas and/or expertise or capabilities that the Contractor should provide to successfully perform the FAA’s requirements. Core Capabilities are intended to be applied consistently with the scope of the contract and the task orders issued through it. The FAA reserves the right to add, remove, or revise Core Capabilities during the life of the contract.

1. Airspace Design and Analysis: Technical knowledge and experience in airspace analysis, design/redesign, test, procedure development, and configuration recommendations.

2. Air Traffic Management (ATM) Automation: Technical knowledge and experience in NAS ATM automation systems to include awareness of international system development trends and latest developments.

3. Air Traffic Rules and Procedures: Technical and operational knowledge and experience in current procedures and policies, and technical and operational experience in developing proposed rules and procedures related to Air Traffic operations in the NAS.

4. Avionics Systems: Technical knowledge and experience in the systems engineering and testing activities of avionics systems, their functions, capabilities and interface

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work requirements, and associated standards compliance requirements.

5. Business Process Re-engineering: Technical knowledge and experience in identifying inefficiencies, including duplication within an organization, making recommendations for improvement, and establishing relationships with other organizations.

6. Communications: Technical knowledge and experience in ground, air, and satellite-based communication systems, standards, policies, and procedures.

7. Cost Benefit Analysis: Technical knowledge and experience in preparation of rough order of magnitude (ROM) cost-benefit analysis and the conducting of life cycle cost and benefit analyses for individuals and grouping of concepts commensurate with the scope and level of maturity of the concept.

8. Data Analytics: Technical knowledge and experience associated with analyzing, systematically extracting information from extreme volumes of data, a broad variety of data types, and the different rates at which the data needs to be processed and analyzed.

9. Enterprise Architecture Products: Technical knowledge and experience in the development of Enterprise Architecture products in the area of aviation.

10. Human Factors: Technical knowledge and experience to identify the physical, cognitive, and social behavior characteristics of human interactions within the aviation system environments.

11. Information Technology: Technical knowledge and experience in the development, implementation, and life cycle support of information systems used in NAS and non-NAS Systems.

12. Integrated Laboratories: Technical knowledge and experience in the design, development, operation, and maintenance of integrated aviation laboratories and testbeds.

13. Investment Analysis: Technical knowledge and experience in providing Investment

Analysis cost studies for large scale government type programs.

14. Modeling and Simulation: Technical knowledge and experience in the design, development, testing, and execution of modeling and simulation using appropriate/validated tools. Focused on the development of foundational methods and tools for addressing problems characterized as system-of-systems. Establishment of an effective frame of reference, crafting of a common lexicon, and study of various modeling and simulation techniques, including probabilistic robust design (including uncertainty modeling/management), agent-based modeling, network theory, object-oriented simulations, and tools for capturing the interaction of requirements, concepts, and technologies.

15. NAS Air Traffic Facilities: Technical knowledge and experience in the operations, ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work maintenance, and certification of various types, kinds, and functions of NAS Air Traffic facilities.

16. Navigation: Technical knowledge and experience in ground, air, and satellite-based navigation systems, standards, policies, and procedures.

17. Operational Concept Development and Validation: Technical knowledge and experience of the activities performed to support concept development and validation.

Concept development is characterized as the process that describes, evaluates, and prepares a proposed capability, technology, or procedure. Validation activities help quantify and qualify the operational feasibility and expected benefits of the concept.

18. Program Management: Technical knowledge, experience, and activities in the management of scope, cost, schedule, quality, and stakeholder requirements.

19. Program Planning & Financial Analysis: Technical knowledge and experience in providing support to large organizational programs pertaining to planning and financial analysis.

20. Requirements Definition: Technical knowledge and experience in defining requirements for aviation-related systems and activities.

21. Security: Technical knowledge and experience in researching, designing, and developing policies, procedures, standards, and systems to ensure the security of the NAS.

22. Standards Development: Technical knowledge and experience in the development and implementation of both national and international technical aviation standards (e.g., FAA, Radio Technical Commission for Aeronautics (RTCA), and International Civil Aviation Organization (ICAO) standards).

23. Surveillance: Technical knowledge and experience in ground-based, air-based, and satellite-based surveillance systems, standards, policies, and procedures.

24. System Safety: Technical knowledge and experience with FAA and International Safety

Risk Management/Safety Management Systems (SRM/SMS).

25. Unmanned Aircraft Systems (UAS) Operations: Technical knowledge and experience with the operations of all classes of UAS and the ability to analyze and recommend strategies for the integration of UAS into NAS operations.

26. Weather: Technical knowledge and experience associated with detection, collection, processing, analysis, and dissemination of weather and the integration of weather data into automated decision-aiding systems to support weather avoidance.

C.4 FUNCTIONAL TASK AREAS

Twenty-five (25) top-level functional task areas are expected to be addressed within TOs issued

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work under the ATEPS II contract.

The functional task areas of the SOW, segmented by business size, are as follows:

(a) Unrestricted Large

1. Program Management Support,

2. Financial and Acquisition Management Support,

3. Standards and Rulemaking,

4. Systems Engineering Support,

5. Software Engineering Support,

6. Hardware Engineering Support,

7. Human Factors Engineering Support,

8. Information Systems Security Support,

9. Safety Management Support,

10. Implementation Support,

11. UAS and Emerging Technologies Support,

12. Testing Support,

13. Configuration Management Support,

14. Performance and Data Management Analysis,

15. Meteorological Support,

16. Training Assistance Support,

17. Logistics Support,

18. Facilities Support,

19. Operational Support, and

20. Data Analytics.

(b) Small Business Set-Aside:

21. Strategic Planning Support, and

22. Management Development and Integration Support.

(c) Small Disadvantaged Business (SDB) Set-Aside:

23. Business Management Support.

(d) Small Disadvantaged Business (SDB) Set-Aside:

24. Risk, Issue, and Opportunity Management.

(e) Small Disadvantaged Business (SDB) Set-Aside:

25. Communications Support.

The Contractor must provide support for the functional task areas listed below as initiated on specific TOs.

C.4.1 Program Management Support The Contractor must provide support for FAA program activities associated with business and administrative planning, organizing, directing, coordination, controlling, and approval actions designed to accomplish overall program objectives, as required by the FAA. Contractor will

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work support task activities involving all aspects of program management within the Four (4) directorates. Tasks include both assistance with the management and contract administration of ATEPS II TOs awarded to the Contractor and the establishment, management, and maintenance of assigned goals.

The Contractor must establish and maintain a program management organization to manage all Contractor resources, personnel, subcontractors, and activities involved in the performance of the Contract. Activities in this task area include, but are not limited to:

a. Assist in Work Breakdown Structure (WBS) management.

b. Assist in schedule development and maintenance.

c. Provide program plan development and maintenance assistance.

d. Provide technical input for the development of Requests for Information (RFI) or Market

Surveys.

e. Provide technical input for the analysis and screening of FAA information requests, either from other FAA organizations or exterior stakeholders.

f. Perform cost and schedule risk assessments. Sources of information that can be used for cost and schedule risk identification include system engineering documentation, lease-buy analysis, life-cycle cost analysis, schedule networks, schedule analysis, baseline cost estimates, requirements documents, lessons learned, trade analysis, and technical analysis of complex computer, Air Traffic Control (ATC), surveillance network, communication and navigation capabilities.

g. Provide recommendations for safety risk management issues.

h. Assist in the development of the products required for the investment analysis phases of PMO

Programs.

i. Provide program data management for Program Management Reserve Tracking and

Reporting.

j. Provide technical input for program planning documents such as screening information requests, agreements, or cost estimates.

k. Provide technical input for the development of program plans and implementation strategies.

l. Provide technical input for the development of agreements such as:

1. Directorate Level Agreements (DLA),

2. Service Level Agreements (SLA),

3. Interagency Agreements (IA) and Intra-Agency Agreement (IAA),

4. Memoranda of Agreement (MOA),

5. Other Transaction Agreements (OTA), and

6. Memoranda of Understanding (MOU) between FAA Program Offices and other

FAA/Federal/state/local government agencies, airlines, and private organizations.

m. Perform business process re-engineering, including development of As-Is Analysis, To-Be

Analysis, and Alternatives Analysis, to make recommendations to improve existing processes and procedures for organizations within and related to the PMO.

n. Assist with communications management internally within the FAA, externally with stakeholder organizations, and other Government oversight organizations.

1. Assist with coordination of all responses to media requests.

2. Collection, consolidation, and categorization of information for FAA to disseminate to

FAA oversight stakeholders.

3. Identify and support industry events that best disseminate information about PMO

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work program activities to gain broad ranging acceptance of the programs within the FAA and outside stakeholders.

4. Assist in the preparation of reports and publications, visual graphics, and video clips.

o. Provide program and technical input to assist the FAA’s development of responses to audits and external organization oversight. This may include, but is not limited to, providing program documentation review, management, and feedback. Documentation may include advisory circulars, handbooks, and manuals, enterprise architecture products and amendments, program requirements documents, initial business case, plan for final investment analysis, etc.

p. Assist in managing and tracking technical and program requirements.

q. Support and coordinate AJM business plan development, maintenance, and reporting.

r. Develop automated workflows and advanced features in a Knowledge Sharing Network (KSN) based on SharePoint to support process improvements.

s. Assist in Joint Resources Council (JRC) documentation preparation.

t. Support briefing development.

u. Provide technical writing expertise for the development of technical engineering studies and analysis of system technologies.

v. Support the performance of business case analyses, including Office of Management and

Budget (OMB) Exhibit-300 A & B Capital Assest Plan and Business Case Summary documentation and Exhibit 53.

w. Prepare for and participate in meetings, including weekly tactical and strategic meetings, internal program reviews, and sector reviews.

x. Provide technical assistance for the following Knowledge Management (KM) activities, which include, but are not limited to:

1. When appropriate Government approvals are obtained, assist in the planning and scheduling of conferences and meetings, including the administration of background and support material, arranging facilities and coordinating accommodations, providing organization and administrative/clerical support, and post-meeting activities.

2. Take and prepare minutes of all project meetings attended.

3. Arrange and facilitate meetings in coordination with the Government.

4. Assist in preparation of correspondence, including coordination of signatures.

y. Develop and maintain a Knowledge Services Network (KSN) document repository.

z. Develop automated workflows and advanced features in KSN to support process improvements.

aa. Assist in alternative analysis studies.

bb. Perform gap analysis studies. A gap analysis identifies the missing components of existing processes and procedures needed to meet the proposed Safety Management Systems (SMS) requirements.

cc. Assist in designing and developing operational use cases and their integration as part of the program office requirements management, change request management, and overall configuration management functions. Perform performance-based management: performance information for PMO systems (such as ADS-B, etc.) may be used by the FAA to monitor the progress of the programs and make decisions about planning objectives and resource usage.

The performance-based management system may encompass providing support in the following activities:

1. Development of a performance framework.

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

2. Technical analysis in key performance areas.

3. Identification of performance measures.

4. Development of performance of information gap analysis.

5. Fusion capability management.

6. Support of Quality Reliability Officer's radio station and service volume audits.

7. Implementation of measurement strategy.

8. Development of performance report(s).

9. Development of continuous monitoring plan.

10. Assessment of lessons learned, refinement of the approach to incorporate lessons learned, and management thereof.

C.4.2 Financial and Acquisition Management The Contractor must support FAA financial and acquisition management and planning activities.

Contractor will support tasks and activities involving a full range of investment analysis activities, including the analysis, formulation, documentation, and maintenance of business plans and the formulation, presentation, and assistance with the execution of the budget and the Acquisition Management System (AMS) acquisition processes.

The Contractor must provide assistance to the FAA with programs and initiatives in the performance of financial management. Activities in this task area include, but are not limited to:

a. Provide program-level financial management assistance, cost estimating, and assistance with validation, financial planning, analysis, and documentation for the budget and procurement planning as agreed on by project managers and other designated organizations.

b. Apply qualitative and quantitative methods to conduct analyses, financial assessments, manage schedules, costs, and activities. Develop analytical products that provide cost estimates as needed.

c. Analyze planned activities and identification of critical paths.

d. Prepare and develop Earned Value Management (EVM) analyses.

e. Use automated financial systems such as e2, REGIS, DELPHI, PRISM, and similar financial tools to ensure effective financial control and develop financial plans and facilitate program reviews.

f. Review and coordinate budget documents, for example, Resource Planning Documents, Capital Investment Team Products, White Sheets, Capital Investment Plans, and Operations Review Board Products.

g. Assist with the Acquisition Quarterly Program Review (AQPR) preparation sessions.

Ensure that the senior Leadership has all team products required to effectively present all necessary status information.

h. Resolve problems and deliver effective work products efficiently throughout the year.

Provide monthly status reports and project completion to ensure policy compliance and alignment with requirements of projects and/or other work activities.

i. Assist with Business Plan Goal planning, tracking, and closeout.

j. Prepare cost -benefit or financial analysis.

k. Assist and maintain integrated group travel plan; assist with A5 funding requirements.

l. Analyze and prepare the life-cycle cost and benefits of programs and their component projects, both collectively and individually.

m. Estimate variations of life-cycle cost and benefits due to changes in technical, design, ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work configuration, schedule, support, interface, and implementation parameters.

n. Track project costs against current and future budgets.

o. Assist in the development and population of a cost-benefit model that will break out dollars by appropriation, WBS element, and time phase by fiscal year.

p. Support cost risk analysis.

q. Develop cost-benefit estimates that identify the basis of estimate (BOE), proposed Level of

Effort (LOE) by task, methodologies employed by WBS element, and time-phase in both constant and current year dollars.

r. Support for the Capital Planning Investment Control (CPIC) requirements, including aiding with the OMB Exhibit 300A & B and Exhibit 53. This effort must also include assisting in updates of the OMB Information Technology (IT) Dashboard tool.

C.4.3 Standards and Rulemaking The Contractor must support the FAA in the development of certification standards, equipage requirements, and operational rules/guidance for the installation and use of system avionics.

Typical standards and regulatory documents include, but may not be limited to, Technical Standard Orders (TSOs) for avionics development, Notices of Proposed Rulemaking (NPRMs) that establish equipage and operational requirements, and Advisory Circulars that provide guidance to avionics developers, installers and operators. This support includes outline assistance in the development and management of program standards, with a focus on ensuring international harmonization and interoperability. Activities in this task area include, but are not limited to:

a. Technical and Subject Matter Expert(s) (SME) to support Radio Technical Commission for Aeronautics (RTCA) Committees and participate in international working groups.

b. Provide outreach briefings and attend agency and industry meetings, conferences, and forums as necessary.

c. Coordinate with all applicable FAA lines of business in the development of Advisory Circulars.

d. Interface with FAA NextGen and Operations Planning Services (ATO-P) international group to provide program office representation.

e. Assist in developing and updating documentation associated with FAA Action Plans (APs) (e.g., Terms of Reference (TOR) and work plans).

f. Assist in developing and submitting applicable regulatory documents for avionics and associated systems.

g. Provide support for Automatic Dependent Surveillance-Broadcast (ADS-B) in aviation rulemaking.

h. Provide support to Equip 2020 efforts to ensure the commercial aircraft fleet equip to support ADS-B rule.

i. Support in global harmonization through international deployment and/or limited implementation of U.S.-based NextGen technology solutions.

j. Support the coordination of standards and regulatory documents with applicable professional organizations, such as RTCA.

k. Provide support for the development of NPRMs, including avionics equipage mandates and operational rules.

l. Participate in working groups with FAA program offices, ATO, the Aviation Safety (AVS) organization, and other U.S. and international stakeholders.

ATEPS II Screening Information Request (SIR) Part I – The Schedule SIR No. XXXX Section C – Description/Specifications/Statement of Work

C.4.4 Systems Engineering Support The Contractor must support all activities associated with planning, managing, supporting, executing, and maintaining system engineering processes, programs, and work. The Contractor must support all aspects of systems engineering task activities involving the design and development, testing, installation, implementation, integration, and transition of systems, components, and equipment, as required by the FAA.

The Contractor must support the FAA with the transition from current ATC capabilities to improved ATC capabilities techniques, as well as with NextGen capabilities that require a wide variety of system engineering activities. These activities may encompass the development of milestones such as completion/approval of technical standards, definition of surveillance-automation interfaces, formulation and validation of aircraft separation standards, approval of system safety and risk management plans, computer-human interface design consensus acceptance, and system configuration baseline. The Contractor must establish a surveillance strategy for the NAS that integrates across all surveillance programs and supports the establishment of a comprehensive surveillance roadmap. Activities in this task area include, but are not limited to:

a. Manage and track technical and program requirements.

b. Develop system designs to reflect system requirements.

c. Perform separation standards analysis.

d. Participate in separation standards working groups involving other services within the ATO, AVS organization, and other stakeholder groups.

e. Develop system test plans and provide support for system tests utilizing these plans.

f. Evaluate critical and essential service implementations.

g. Monitor technical performance measures and other system and service metrics for the critical and essential services.

h. Monitor compliance with critical and essential services and other program specifications and definition of critical and essential services functional architecture.

i. Develop hardware and software systems to support surveillance, traffic flow, and automation platforms.

j. Construct proof-of-concept models, prototypes, and/or initial capabilities of NextGen systems.

k. Perform target level-of-safety assessments and collision risk modeling and development of separation standards analyses.

l. Provide technical input for modifications to ICAO and FAA standards and procedures for reduced separations in Oceanic airspace.

1. Perform avionics equipment upgrades as necessary to meet the evolving requirements of NextGen.

2. Assess 1030 MHz or 1090 MHz Radio Frequency impact on current and future surveillance infrastructure.

3. Provide technical assistance in planning, facility, and system development/integration activities and assist in the development of:

i. Requirements…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .