Statement of Work 12.19.2024 MP V2.0.docx

DOCX document 72 KB Posted

Attached to
MARKET SURVEY/CAPABILITY ASSESSMENT FOR MAINTENANCE OF GOVERNMENT-OWNED SOFTWARE TOOLS
Solicitation number
6973GH-25-S-00001
Issued by

About this file

This is a Statement of Work (SOW) for maintenance of government-owned software tools, accompanied by a related market survey/capability assessment pre-solicitation notice from the FAA's Franchise Acquisition Services. The SOW outlines requirements for maintaining and enhancing six government-owned tools used for Coded Instrument Flight Procedures (CIFP), including the ARINC Tailoring Tool, ILS-1 Arc Maneuver Tool, CIFP Editor Tool, CIFP Build Tool, CIFP QC Tool, and CIFP Integs Tool. The contract period includes a one-year base period with four one-year options.

The market survey responses are due by January 10, 2025, at 5:00 PM CST. The NAICS code is 518210 with a $40M size standard. Vendors must provide capability statements detailing their services, past performance, years in business, and implementation strategy, along with comments on the draft SOW and a ROM estimate. Work must be performed offsite at contractor facilities within the US, with no travel authorized. The contractor must provide personnel with SQL and C# programming expertise and ARINC 424 coding knowledge. While the competition type is undetermined, the agency is considering both full and open competition and small business set-asides, including 8(a) opportunities. The contractor will handle both routine maintenance (tasks under 40 hours) and over-and-above services for major enhancements requiring more than 40 hours of work.

View the file

On GovTribe

Work with this file

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

Text version

STATEMENTOF WORK

Maintenance of Government Owned Tools

1.0 GENERAL

The Federal Aviation Administration (FAA), Aeronautical Information Services (AJV-A) provides services to ensure the standard development, evaluation, and certification of airspace systems, aeronautical data/products, and equipment for customers worldwide. Aeronautical Information Services designs and develops Instrument Flight Procedures (IFP’s), publishes aeronautical charts and digital products for air carrier and general aviation pilots for use throughout the United States and around the world. Aeronautical Information Services manages aeronautical data in support of the NASR in support of the 28-day aeronautical data subscriber files, National Flight Data Digest (NFDD) and the Federal Notice to Airmen (NOTAM) System.

2.0 SCOPE OF WORK

As a result of the FAA Air Traffic Organization (ATO) Operation Plan goals to improve safety and increase capacity within the National Airspace System (NAS), the FAA requires engineering services to support the Coded Instrument Flight Procedures (CIFP) requirements.

3.0 PLACE OF PERFORMANCE

Work shall be performed offsite at the contractor’s facility located within the United States.

4.0 PERIOD OF PERFORMANCE

The period of performance for the resulting contract is a one-year base period and up to four one-year option periods.

5.0 TASK 1 - MAINTENANCE AND ENHANCEMENT OF GOVERNMENT OWNED TOOLS

The Contractor must maintain and provide minor enhancements for the following government owned tools as requested by the Aeronautical Information Services COR. Minor enhancements are defined as simple changes/corrections/updates to the tools that require 40 hours or less to accomplish. This includes any unforeseen issues relating to the build of the CIFP to include, but not limited to, the support for continuity of operations and maintenance of CIFP Integrity Checks. Major enhancements or updates requiring more than 40 hours to complete will be performed as Over and Above requirements.

5.1 ARINC Tailoring Tool - converts standard P3 files into tailored files to support the FAA Flight Inspection Program. The tool can convert a single P3 file or multiple files located in a specified directory. These tailored P3 files make it possible to store, in an airborne Flight Management System (FMS), both current and future versions of the same terminal procedure.

5.2 ILS-1 Arc Maneuver Tool - creates P3 files which will be added to Flight Inspection Services Custom Database and loaded on any Flight Management System (FMS). These P3 files will provide the capability for the FAA Flight Inspection Program to fly arcs using the FMS, from the localizer antenna for every front and back course ILS, LDA, and SDF contained in Flight Inspection Services AIRNAV database, in order to flight check them according to the US and Pans Ops specifications.

5.3 CIFP Editor Tool is a simple tool in form and function that allows the FAA the capability to create, modify, and output SIAPs, STARs and DPs in the P3 text file format for inclusion in the CIFP.

5.4 CIFP Build Tool – is a C#.NET production application that ingests and updates new and revised data for the CIFP, running QC tests, allowing for manual editing, and generating the final product.

5.5 CIFP QC Tool - is a C#.NET application that analyzes ARINC 424 files (packet and full) and displays error messages when the coding in the file violates one or more Integrity and Validation Checks (Integs). The Integs will be stored in a database which can be modified to ensure the appropriate Integs are run.

5.6 CIFP Integs Tool - is a C# .NET application that updates the CIFP_INTEGS database table with the latest SQL Integrity Checks. This tool requirements document also covers the design of the CIFP_INTEGS table and identification of the SQL Integrity Checks.

5.7 CIFP Integs SQL – is a .SQL file that contains the definitions of all the SQL Integrity Checks in the CIFP_INTEGS database. This file would be executed by the CIFP Integs Tool.

6.0 TASK 2 - OVER AND ABOVE SERVICES

Over and Above (O&A) Services are necessary in support of current and evolving requirements that impact the usefulness of the CIFP and other aeronautical data products. These requirements are unknown at this time, therefore, are not explicitly defined above. This includes support requiring more than 40 hours to complete. The government shall provide a description of the over the above work to be accomplished and the contractor shall provide a proposal for the work to be completed. If agreed upon, the government will issue a separate delivery/task order for any O&A work to be accomplished. Examples of O&A tasks include but are not limited to:

6.1 Major enhancements to existing tools

6.2 New Releases of ARINC 424 /424A coding rules and/or criteria changes

6.3 IT Compliance such as server changes and infrastructure modifications

7.0 TRAVEL NOT AUTHORIZED

No travel expenses are authorized during performance of the contract. All work is to be performed off-site and any meetings will be conducted remotely.

8.0 GOVERNMENT RESPONSIBILITIES:

The Government will provide information and access as necessary to complete the tasks contained in the SOW.

· A copy of the CIFP file will be provided to the Contractor by Aeronautical Information Services as required. The Government will provide the updated CIFP file via online File Transfer Protocol (FTP) access or network drive access.

· FAA will provide the Contractor access to Aeronautical databases necessary to fulfill the requirements of the contract.

· FAA will provide all required forms (such as 8260) to support the contract.

· FAA will provide the Contractor team FTI Remote Access Capability (FRAC) access as needed in support of contract requirements.

· FAA will provide the Contractor with FAA email addresses as needed to support the contract.

9.0 GOVERNMENT FURNISHED ITEMS

The FAA will provide system access for off-site work in accordance with established FAA security policies, standards, regulations, and rules of conduct. The FAA will provide the appropriate procedures, guidelines, standards, reference materials, and system/application documentation.

Aeronautical Information Services will provide the Contractor with access to the AIRNAV / NASR / IFP Fix database to support the FAA data requirements.

List of current GFP:

FRAC tokens

The FRAC token must be collected immediately from prior Contractor employees and the FAA must be notified within 1 business day. The Contractor must return the FRAC access token(s) to the COR within 30 calendar days.

10.0 CONTRACTOR FURNISHED ITEMS

The Contractor must provide qualified personnel, with expertise in SQL and C# programming languages, and familiarity with ARINC 424 Coding, NASR TXT and CSV Subscriber Files. The contractor must provide all required space, facilities, materials, and equipment necessary for the successful performance of this Statement of Work. The Contractor is responsible for providing supervision of all of its personnel providing services under this SOW.

11.0 ACRONYMS

ARINC Navigation Data Base (NDB) is an established industry development group. AIP – Aeronautical Information Publications AIRNAV - Flight Inspection Database maintained by FAA AIRAC – Aeronautical Information Resources & Control AIS – Aeronautical Information Services ARINC - Aeronautical Radio, Inc. ATO - Air Traffic Organization CO - Contracting Officer COB – Close of Business COR -Contracting Officer's Representative CIFP – Coded Instrument Flight Procedures DAFIF – Digital Aeronautical Flight Information File (DoD Format) DoD – Department of Defense DP - Departure Procedure ERAM – En Route Automation and Modernization FAA - Federal Aviation Administration FMS - Flight Management System FRAC – FTI Remote Access Capability FTP - File Transfer Protocol GFP – Government Furnished Property HP – Holding Pattern IAP – Instrument Approach Procedure IFP- Instrument Flight Procedures ILS - Instrument Landing System ISO – International Organization for Standardization JAD – Joint Application Development LDA - Localizer Directional Aid LOC - Localizer NAS – National Airspace System NASR - National Airspace Systems Resource NGA - National Geospatial-Intelligence Agency NFDC – National Flight Data Center NFDD – National Flight Data Digest NOTAM – Notice to Airmen P3 – ARINC 424 per Procedure Packet QC – Quality Control NDB - Navigation Data Base RNAV – Area Navigation RNP - Required Navigation Performance SIAP - Standard Instrument Approach Procedure SDF - Simplified Directional Facility SOW – Statement of Work STAR - Standard Terminal Arrival VPC - Visual Procedure Check Tool WP - Waypoint XML – Extensible Markup Language image1.wmf

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