SOW FOMS 2026.09.03_draft.pdf

Flight Program Operations Aircraft Engineering Team Oklahoma City, Oklahoma

Flight Operations Management

System (FOMS)

Statement of Work (SOW)

FOMS Mobile and Web Application Development

FOMS-270000

Updated 09/3/26

This document is prepared by:

Flight Program Operations Aircraft Engineering Team

P.O. Box 25082 Oklahoma City, OK 73125-502

1.0 General

1.1 Introduction

The Federal Aviation Administration (FAA), Flight Program Operations has an ongoing requirement to support FOMS mobile and FOMS web application overdevelopment to support these activities, we need highly skilled iOS, Java backend, Go backend, and React JS web developers.

The Flight Operations Management System (FOMS) mobile application provides increased flight crew productivity by aiding in the creation of required reports and providing timely information to crew members and flight program support staff. The FOMS web application suite supports managing Flight Program activity, including flight scheduling, planning, dispatch, surveillance, post flight processing, and dissemination of mission results.

1.2 Background

This requirement is a follow-on contract to ensure the continuation of the FOMS mobile application’s development and FOMS web application support. Due to the demands of our highly mobile workforce, FOMS mobile and the FOMS web application suite have been identified as critical tools that improve the efficiency of the flight crews flying the mission.

1.3 Requiring Office

Federal Aviation Administration (FAA), Flight Program Operations, Aircraft Engineering Team.

1.4 Scope

The scope of this work is to assist the FAA in developing and implementing custom FAA systems using Agile methodology. This may include developing defined “use cases” for the FOMS mobile application. It may also include related source data from the FOMS web application server that synchronizes with the FOMS mobile application and related data sources. The mobile application and its related source data must have the capability to provide crew members with an efficient and intuitive user interface to review data and accurately document mission activities and results. The FOMS mobile application must provide a seamless user experience while operating remotely on an iOS iPad device. The Contractor will perform the following tasks to support the delivery of the Use Cases.

Task 1: Program Management Support

Task 2: Mobile Development Support

Task 3: Web Application Development Support

1.5 References

Applicable sample documentation, directives and manuals will be made available to the contract employees to provide procedures, guidelines, and assistance. The Contractor must ensure all work is in full compliance with regulations expressed in the following procedures, orders, and programs unless otherwise directed by the Contracting Officer’s Representative

(COR):

FAA Acquisition Management Policy:

http://fast.faa.gov/AMP_TOC.cfm FAA Acquisition Toolset:

http://fast.faa.gov/ ID Badge Online Application:

Employee ID Badge (PIV Card) | My FAA Virtual Private Network (VPN) Access https://register.ftiharris.com iOS / C# Developer: VPN access as New User Registration – Non-FAA Java Programmer: VPN access as New User Registration – with FAA.gov email

Contractor & Industrial Security Program:

Order 1600.1F - Personnel Security Program

1.6 Period of Performance

The period of performance is one (1) one-year base and up to four (4) one-year option periods.

1.7 Place of Performance

The place of performance is at the Contractor’s facility, and onsite at FAA, the Mike Monroney Aeronautical Center (MMAC) in Oklahoma City (OKC), and Alliance Airport (AFW) in Fort Worth. In addition, situational telework is authorized.

1.8 Government Furnished Equipment/Information (GFP/GFI)

The Government will provide the contractor with office space, computer, printer, facsimile service, reproduction capability, internet access, and administrative support for the project as required, while working on-site at the MMAC. Telephone service for official use and local calls only will be provided to the contractor; all other calls shall be made at the contractor’s expense.

The contractor shall not use Government furnished material or equipment to work on projects other than those directed by this performance work statement. Government furnished equipment provided to the contractor will be returned to the Government in good working order.

The contractor will be given current task pertinent information, and other documentation or materials as required for conducting the tasks described hereunder. The Government retains the http://fast.faa.gov/AMP_TOC.cfm http://fast.faa.gov/ https://my.faa.gov/org/linebusiness/ash/programs/id_badge https://register.ftiharris.com/ https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentID/1040448 right to withdraw or reallocate these resources at any time, and without notice, during the performance of this contract.

1.9 Work Schedules and Overtime:

1.9.1 Work Schedules: Normal day shift hours are 0800 – 1630; however, contract personnel may provide services between 0600 – 1800. In cases of system restoration, support, short deadlines, training, etc., contract personnel may be required to work outside the normal service hours. Flexible work schedules comparable to government schedules may be used when approved by the requiring organization. The Contractor is responsible for ensuring all labor laws are adhered to and followed.

1.9.2 Overtime: When overtime work is required, the contractor must submit an overtime request via email at least 48 hours in advance of the anticipated start of the overtime work to the FAA Flight Program Operations (FPO) Program Management and Engineering Group for approval, with a copy (cc) to the Contracting Officer’s Representative (COR). The request should include the reason for the overtime, the personnel involved, estimated hours, and expected tasks to be completed. Overtime performed without prior approval from FPO may not be compensated.

All completed and approved overtime work must be summarized in the monthly status report detailing the work performed during the overtime period. This summary must include:

• Date(s) and time(s) of overtime worked

• Names of personnel involved

• Description of tasks completed

• Any issues encountered or resolved during overtime

Processing of overtime requests will be accomplished in accordance with the labor laws pertaining to overtime. The Contractor shall follow all labor laws for overtime.

2.0 Requirements - The Contractor must conduct the tasks described in the following sections.

2.1 Requirement Task 1 – Program Management Support

2.1.1 Task Order Management

The Contractor must provide program management support to ensure that identified tasks are performed efficiently, accurately, on time, and in compliance with the requirements. The Contractor must participate as a member of a government-led team as requested by the Contracting Officer’s Representative (COR). The Contractor must participate in a Kick-Off meeting between the FAA, COR, and Contractor to review SOW requirements and understand work scope and deliverables.

2.1.2 Monthly Status Reports

The Contractor must provide Monthly Status Reports (MSRs) based on the deliverables identified in this SOW. The Contractor must provide an MSR that documents the activities of the previous month and identifies planned activities for the following month. The Contractor must deliver the MSR to the COR, and the MSR must include, at a minimum, the following information:

Overview of work completed, work in progress, and work planned for each task

Hours expended by task, labor category, and personnel

Status of individual deliverables

Identification of risk areas with recommended remedial actions

Status of all outstanding risks identified in previous MSRs

Expended labor hours per labor category by Use Case defined in Appendix A

CLINs used during month

Cost/hours funded or apportioned by CLIN

Cost/hours used by CLIN

Projected date when 75% of funds are spent

Projected date when funds are exhausted

Funds/hours remaining by CLIN

Description of the staffing resources allocated to each task, i.e., staffing plan

Other direct costs (ODCs) estimated, used, and remaining by month

Summary of expenditures by resource and labor category for the monthly reporting period, as well as cumulative year-to-date totals for the performance period

Any additional information pertinent to the Government in administering the performance of this effort or as requested by the COR.

2.1.3 Program Management Review

The Contractor must meet quarterly with the PMO and COR for a Program Management Review (PMR) at a location selected by the COR. The PMR must include discussion of the following:

Vendor contract/Task Order information

Financial summary

Task Order staffing summary

Performance summary

Accomplishments

Delivery Order information

Delivery Order quad charts

Action Item summary

Subcontractor status, if any

The Contractor must provide all PMR materials at least 5 business days prior to the scheduled meeting. The Contractor must prepare and deliver PMR minutes including action items, issues, resolutions or specific FAA instructions no later than 5 business days.

2.1.4 System Information Security Support

The Contractor must provide support to the System Owner (SO) to assist in the compliance with ATO Cybersecurity Policy. The Contractor must assist in the development of documentation required by the ATO Information Security Program with input from AJF Subject Matter Experts (SME), FAA AIT and the ISSO. The Contractor must follow the templates and guidance that will be made available to the Contractor.

The ATO ISS Program has developed specific system level security procedural guidance. This guidance identifies the NIST 800-53 Rev 5 requirements associated with each procedure and provides the details for the types of information that will be required.

The Contractor must develop ATO documentation that meets DOT Department Cybersecurity Policy, Order 1351.37, as amended, and the DOT Departmental Cybersecurity Compendium, as amended; and FAA Order 1370.121 FAA Information Security and Privacy Program Policy, as amended, defines the FAA Information Security and Privacy Program and Policy. The level of documentation needed depends upon the security risk level assigned during the evaluation process, and whether the system has protected privacy information.

2.2 Requirement Task 2 – FOMS Mobile Development Support

The Contractor must provide support to the Program Office to perform the following Tasks in accordance with Use Cases identified in Appendix A – FOMS iPad App (iOS) Use Case Development Forecast.

The level of success of developed Use Cases identified in Appendix A is determined by number of versions tested before it is acceptable for deployment to the mobile environment.

FAA personnel will test each version delivered to FAA.

A measurement of success is that each beta version will pass FAA beta testing and be acceptable for deployment with no more than three (3) beta versions requiring testing. If stability or operational deficiencies are still found after more than three (3) beta versions are tested, a formal technical interchange will be called to investigate the issues influencing the deliverable.

The requirements for each Use Case identified in Appendix A are assigned via COR to the contractor via Jira Software. This Agile project management tool supports agile methodology.

The development team will be striving for 6-week iterations in most cases. Some more complex use cases will take longer and have multiple iterations. Agile boards and Jira will be used to monitor the level of success and completion.

The Contractor must develop and deliver the software based on the Use Cases identified in Appendix A by performing the following tasks:

Collaborate with system analysts to analyze problem areas and postulate feasible solutions system analysis and design areas for large scale, complex systems

Develop and design software applications based on Use Cases using Apple industry standards and .Core Data framework and .Swift programming language

Develop and design software applications based on C# and .NET use cases using Entity framework, Windows Presentation Foundation (WPF) industry standards.

Provide systems analysis, design, documentation, and implementation assistance on problems, which require in-depth, state-of-the-art knowledge of a specialized information engineering discipline for effective implementation

Analyze and assess the technical requirements and the feasibility of proposed Use Case modifications or concepts

Review current hardware environment and make recommendations concerning any changes and/or additions to the existing hardware requirements

Review document application architecture for each Use Case assigned to be compatible within industry standard mobile environment

Perform System implementation by loading active data in the FAA test environment

Collaborate with Flight Program development team for technical advice on how to maximize efficiency in application development, deployment timing and consistency

Deliver software applications and implementation of the Use Cases using the Success Criteria identified below

The success criterion is that the application must meet the requirements for the iteration under development as agreed upon at the Formal Technical Interchange Meeting

Develop and maintain iPad/Flight Inspection Airborne Processing Application (FIAPA) applications as defined in Appendix A

Monitor crash reports and user interactions reported in Crashlytics to develop solutions that improve software reliability

At the initiation of each Use Case and as required during development, a formal technical interchange meeting will be held with users, the development team, and the Contractor.

Government will create Meeting minutes that include:

• Use Case being developed

• Solution selected

• Design methods

• Specific tasks to be assigned

• Estimated programming time for each task

• Target Date for beta test

• Respond to refactoring of code to maintain system compliance with current manufacture and FAA cybersecurity requirements.

The Contractor must review and edit, using tracked changes, the Formal Technical Interchange meeting minutes to confirm understanding of the work using the applicable references, manuals, and handbooks identified in the Reference Section 2.

2.3 Requirement Task 3 – FOMS Web Development Support

The level of success of developed Use Cases identified in Appendix B – Web Application (Java) Use Case Development Forecast is determined by number of versions tested before it is acceptable for deployment to the web environment. FAA personnel will test each version delivered to FAA.

A measurement of success is that each beta version will pass FAA beta testing and be acceptable for deployment with no more than three (3) beta versions requiring testing. If stability or operational deficiencies are still found after more than three (3) beta versions are tested, a formal technical interchange will be called to investigate the issues influencing the deliverable.

The requirements for each Use Case identified in Appendix B are assigned via COR to the contractor via Jira Software. This agile project management tool supports agile methodology.

The development team will be striving for 6-week iterations in most cases. Some more complex use cases will take longer and have multiple iterations. Agile boards and Jira will be used to monitor the level of success and completion.

The Contractor must provide support to the FOMS Program Office to perform the following Tasks in accordance with Appendix B – Web Application (Java) Use Case Development Forecast.

Collaborate with system analysts to analyze problem areas and postulate feasible solutions system analysis and design areas for large scale, complex systems;

Develop and design software applications based on Use Cases using Java industry standards;

Provide systems analysis, design, documentation, and implementation assistance on problems, which require in-depth, state-of-the-art knowledge of a specialized information engineering discipline for effective implementation;

Analyze and assess the technical requirements and the feasibility of proposed Use Case modifications or concepts;

Review current hardware environment and make recommendations concerning any changes and/or additions to the existing hardware requirements;

Review document application architecture for each Use Case assigned to be compatible within industry standard mobile environment;

Perform System implementation by loading active data in the FAA test environment;

Collaborate with Flight Program development team for technical advice on how to proceed to maximize efficiency in application development, deployment timing and consistency; and

Develop and maintain existing Java based applications as defined in Appendix B.

Familiarity with DevOps software: Jenkins, Ansible Tower, Docker, Ant and Jfrog;

At the initiation of each Use Case and as required during development, a formal technical interchange meeting will be held with users, the development team, and the Contractor.

Government will create Meeting minutes that include:

• Use Case being developed

• Solution selected

• Design methods

• Specific tasks to be assigned

• Estimated programming time for each task; and

• Target date for beta test

• Respond to refactoring of code to maintain system compliance with current manufacture and FAA cybersecurity requirements.

The Contractor must review and edit, using tracked changes, the Formal Technical Interchange meeting minutes to confirm understanding of the work using the applicable references, manuals, and handbooks identified in the Reference Section 2.

This will result in a schedule that will be monitored and compared to monthly reports provided by the Contractor and will be discussed at each PMR. A formal technical exchange meeting may be called if an issue needs prompt attention.

Meeting minutes of all formal Technical Interchange meetings will be provided to the COR and maintained in the contract file.

Deliver software applications and implementation of the Use Cases using the Success Criteria identified below; and

The success criterion is that the application must meet the requirements for the iteration under development as agreed upon at the Formal Technical Interchange Meeting.

3.0 Key Deliverables, Milestones, and Schedule

This section describes 1) the products and tangible results that are expected from each task contained in the previous section, 2) the date each deliverable is due, and 3) the Government acceptance criteria. The Contractor must verify that all submitted deliverables conform to applicable FAA policies, standards, and guidelines as listed in Section 2 of this SOW and any specific formatting requirements as directed by the COR.

All days are business days unless otherwise specified. The Government’s Initial Review of each deliverable is performed in accordance with the “Initial Review” terms listed in the Acceptance Criteria section below. The definitions for the terms are as follows:

Please select and include one of the following in the “Acceptance Criteria” box for each deliverable.

Technical Performance Execution (TPE): Task activities performed with little to no re-work/re-performance required.

Schedule Compliance (SC): Contractor provides deliverables on due dates and meets project milestones or schedules.

Deliverable Quality (DQ): Deliverables are complete, accurate and compliant with task

Cost Control (CC): Successful delivery of task requirements within originally specified estimated cost.

The following provisions and the applicable SOW Section(s) (as listed in the Acceptance Criteria for each deliverable in the table below) govern the FAA’s final acceptance of each deliverable:

Task End Result/Deliverable Due Date Acceptance Criteria

1 Kick Off Meeting Minutes

2 days after Kick Off Meeting

Initial Review: SC, DQ

Kick Off Meeting Minutes capture all relevant topics discussed, summarize contractor’s understanding of work scope, and SOW requirements.

Contractor format acceptable, meets COR approval of content, and is prepared in accordance with SOW Section 3.1.1.

Task End Result/Deliverable Due Date Acceptance Criteria

1 Monthly Status Reports (MSRs)

10th day of 1st full month following Task Order start.

Every 10th day of each month thereafter

The MSRs are accurate, complete, submitted on time in the COR approved format and is prepared in accordance with SOW Section 3.1.2.

1 Quality Control Plan

(QCP)

10 days after Task Order start;

Updates per Section 3.1.4.

The QCP is accurate, complete, submitted on time in the COR approved format and is prepared in accordance with SOW Section 3.1.3.

1 Program Management Review (PMR) Documentation

As required by Section 3.1.7

PMR Documentation is accurate, complete, submitted on time in the COR approved format and is prepared in accordance with SOW Section 3.1.4.

2, 3 Edited Formal Technical Interchange Meeting Minutes

2 days after receiving formal technical interchange Meeting Minutes from Government.

Initial Technical Interchange Meeting Minutes updated in accordance with SOW Sections 3.2. and 3.3.

Submitted on time and meets COR approval of content.

Following Technical Interchange, meeting minutes will focus on Use Case/Issue being discussed.

Task End Result/Deliverable Due Date Acceptance Criteria

2 iPad App (iOS) Developed Use Cases identified in Appendix A

In accordance with Appendix A and schedule as a result of Mobile Development Technical Interchange Meeting and documented in FAA provided Meeting Minutes.

The Mobile Developed Use Cases per Use Cases identified in Appendix A are accurate, complete, submitted on time in the COR approved format and is prepared in accordance with Section 3.2.

The development software must provide the functionality described in the use case, conform to the references, manuals, and handbooks specified in the applicable TIM minutes, and be acceptable for deployment.

Web Application (Java) Developed Use Cases identified in Appendix B

In accordance with Appendix Band schedule because of Mobile Development Technical Interchange Meeting and documented in FAA provided Meeting Minutes.

Java Developed Use Cases are accurate, complete, submitted on time in the COR approved format and is prepared in accordance with Section 3.3.

The development software must provide the functionality described in the use case, conform to the references, manuals, and handbooks specified in the applicable TIM minutes, and be acceptable for deployment.

4.0 Resource Requirements

4.1 Senior I Computer Scientist/Systems Analyst (Mobile Development) (.95 FTE)

More than 8 relevant years of IT experience, including 8 years of experience developing mobile applications, preferably design and development experience of iOS applications for iPhone and iPad.

Minimum Bachelor’s in Computer/Engineering/Aviation. Master’s in Computer/Engineering/Aviation preferred. Master’s degree in Computer/Engineering/Aviation can be substituted for 1 year of experience. Experience developing code using current iOS, Swift language, Git, Github, Objective C, Xcode IDE, XCTest/XCUITest, and Core Data is required.

4.2 Senior I Computer Scientist/Systems Analyst (Web Development) (1 FTE)

More than 8 relevant years of IT experience, including 8 years of experience developing web applications. Minimum Bachelor’s in Computer/Engineering/Aviation. Masters in Computer/Engineering/Aviation preferred. Master’s degree in Computer/Engineering/Aviation can be substituted for 1 year of experience. Experience developing code using Java, JavaScript (React JS), Go Lang, SQL/PLSQL, Oracle DB, Linus Command Line, CSS, HTML 5, Maven, RESTful, Spring framework, and Hibernate.

4.3 Intermediate II Computer Scientist/Systems Analyst (Web Development) (3 FTE)

More than 5 relevant years of IT experience, including 5 years of experience developing web applications. Minimum Bachelor’s in Computer/Engineering/Aviation. Masters in Computer/Engineering/Aviation preferred. Master’s degree in Computer/Engineering/Aviation can be substituted for 1 year of experience. Experience developing code using Java, JavaScript (React JS), SQL/PLSQL, CSS, HTML 5, Maven, RESTful, Spring framework, and Hibernate is required.

Experience in Go Lang, Oracle DB, and Linus Command Line are preferred.

4.4 Program Manager (1 FTE)

Minimum of 15 relevant years of program management experience. Minimum Bachelor’s degree in Computer/Engineering/Aviation. Masters in Computer/Engineering/Aviation preferred. Master’s degree in Computer/Engineering/Aviation can be substituted for 1 year of experience. Project Management Professional (PMP), Portfolio Management Professional (PfMP), Program Management Professional (PgMP) or equivalent preferred.

4.5 Senior I Computer Scientist/Systems Analyst (1 FTE)

4+ years of hands-on experience with software application design, development, testing, and engineering duties as required. 4+ years of experience with C#, .NET (core or framework) required.

Entity framework, Windows Presentation Foundation (WPF) experience preferred. Minimum Bachelor’s in software engineering. Masters in software engineering preferred.

Master’s degree in software engineering can be substituted for 4 years of experience. Experience with aviation systems, Agile and/or federal software development environments preferred.

i

1. Appendix A – Mobile Application Use Case Development Forecast

Mobile Application Use Case Development Priority

Task Title

FOMS Use Cases

(Mobile Application)

TASK Transition 1 Transition Vendor will be afforded labor hours for 30-days. Contractor will become familiar with business rules and application infrastructure.

TASK Enhancement 1 Itinerary The user will be presented with a listing of all of the itineraries to which they are assigned. From this list, they will have the ability to select an itinerary and download it to the device for editing.

TASK Enhancement 2 Risk Assessment All Flight Program Users will have the ability to submit Risk Assessments prior to flight release.

TASK Enhancement 3 DFL The user will be able to complete an off-line daily flight log DFL based on the existing itinerary. The DFL will be available for offline use while in flight and will emulate the features of the web daily flight log. Basic features for creating and syncing a DFL with the server will be implemented first. New feature will be added to eventually cover all of the features of the online DFL form.

TASK Enhancement 4 Datasheets The user will be able to view relevant datasheets attached to the Itinerary. Support for additional data in various formats will be developed and added as needed.

TASK Enhancement 5 PDF Management Phase The user will be able to share and sync PDFs with other crew members and the server.

Task:

Provide a solution for viewing PDFs in an alternate presentation for low-light situations.

TASK Enhancement 6 Maintenance Perform multiple tasks to keep running FOMS Mobile efficiently in the real time like upgrade code based on iPadOS upgrades, architecture changes, and third-party tool integration handling like Analytics.

TASK Development 1 Unit Testing Unit testing will be added into the mobile application’s code base. This will allow our team to thoroughly test our application in a fraction of the time that it now takes.

Furthermore, it would prevent many of the issues that seem to show up without warning and further eliminate much of the rework that would have to be done.

TASK Development 2 Dispatch Working on adding dispatch arrival.

TASK Development 3 Messaging Capabilities The user will be able to communicate in real time with the

Service Center via APN messaging. Messaging capabilities will be included in all previously and newly developed features where they are able to enhanced user experience.

TASK Development 4 Include other Missions Users from other flight missions within Flight Program Operations will be able to utilize the FOMS iOS application.

This will require assigning proper roles and permission to flight crew members within FOMS and FOMS Mobile.

Tasks:

• Connect all Flight Program crewmembers, (current application only connect to one flight mission.)

• Provide solution for access differences between users

TASK Development 5 Aircraft Fuel Capture and submit information required to automate fuel reconciliation.

Tasks:

• Provide solution for the need to update and synchronize fuel data with ground system

• Complete each assigned task as they are generated

TASK Development 6 Aircraft Logbook Capture and submit aircraft logbook information and reconcile with Flight Program Aircraft Management System

(FPAMS).

ii

Tasks:

• Provide an aircraft logbook entry and reconciliation user interface.

• Complete each assigned task as they are generated

TASK Development 7 Flight Operations Reference Application

(FORA)

FORA app is planned to have training for four applications (so far and is Scalable for multiple applications as per the need) used by these operations: Jeppsen Aviator App, FOMS Mobile App, Aero App and Flight Activities.

The goal is to create a reference application for multiple applications so that we can reduce the time spent by users in finding any relevant information in different places.

Task:

Each application in FORA will have three types of help information shared with our users. This information would be in the form of videos, URLs and FAQs with reference material in the form of PDFs.

TASK Development 8 iOS Toolchain and Language Modernization

Maintain the FOMS Mobile code base on currently supported Apple development tooling and languages so that annual Xcode and iPadOS releases can be absorbed without disruption to the flight crews.

• Migrate remaining legacy Objective-C components to Swift.

• Consolidate third-party dependency management onto a single supported tool.

• Adopt current Apple user interface frameworks as older frameworks are deprecated.

TASK Development 9 Automated User Interface and Regression Testing

Extend the automated testing effort beyond unit tests to include automated user interface and end-to-end regression testing across supported iPad hardware and iPadOS versions, reducing the manual test burden of each release.

• Develop automated user interface tests for core mission workflows.

• Establish a repeatable regression suite executed prior to each release.

TASK Development 10 Identity, Authentication, and Access Modernization

Align FOMS Mobile authentication with current FAA enterprise identity standards, including multi-factor authentication and enterprise single sign-on, and keep crewmember roles and permissions on the device consistent with the FOMS ground system.

• Implement multi-factor authentication and enterprise single sign-on on the device.

• Maintain consistent role and permission handling between FOMS Mobile and FOMS.

• Complete each assigned task as they are generated.

TASK Development 11 Expanded Capabilities Various tasks to be identified as development continues and FOMS iOS’ usage and adoption into Flight Program Operations’ workflows evolves.

iii

2. Appendix B – FOMS Web Application Use Case Development Forecast

Web Application Use Case Development Priority

Task Title

FOMS Use Cases (Web Application)

TASK Transition 1 Transition Vendor will be afforded labor hours for 30-days. Contractor will become familiar with business rules and application infrastructure.

TASK Transition 2 Transition Out and Turnover

At the conclusion of the period of performance, the vendor will provide knowledge transfer and turnover support to the Government or to a successor contractor.

Tasks:

• Deliver current system, build, and deployment documentation.

• Provide knowledge transfer sessions covering business rules and application infrastructure.

• Support the successor through the transition period.

TASK Enhancement 1 Flight Inspection Tracking System (FITS)

Flight inspection object and task management. User interface to create, manage and disseminate flight inspection status and costs associated with reimbursable inspections.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

• Assist in upgrading third-party and open-source components and in remediating published vulnerabilities as they are identified.

TASK Enhancement 2 Flight Management / Daily Flight Log

(FMDFL)

User interface for dispatch, flight following and post flight processing.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

• Assist in upgrading third-party and open-source components and in remediating published vulnerabilities as they are identified.

TASK Enhancement 3 Flight Inspection Scheduling Tool

(FIST)

A geographical representation of inspection tasks, and user interface to create and manage flight inspection itineraries.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

• Assist in upgrading third-party and open-source components and in remediating published vulnerabilities as they are identified.

TASK Enhancement 4 Mission Planner User interface to manage the scheduling of aircraft, crew and mission assignments.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

iv

TASK Enhancement 5 Flight Inspection Report Processing (FIRPS)

User interface to create, manage and disseminate flight inspection reports.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

• Assist in upgrading third-party and open-source components and in remediating published vulnerabilities as they are identified.

TASK Development 6 Fuel Billing and Reconciliation (FBR)

User interface to manage fuel billing tickets, invoices, and the reconciliation of fuel purchases.

Tasks:

• Resolve defects reported against this web module.

• Provide production support, configuration changes, and data corrections.

• Complete small user-requested enhancements that do not warrant a dedicated task.

• Assist in upgrading third-party and open-source components and in remediating published vulnerabilities as they are identified.

TASK Development 1 FOMS Integration With Camp

Since the TRAX maintenance application is being replaced with a new CAMP maintenance application, we need to create new APIs to communicate with CAMP. This would allow us to retrieve data such as current aircraft times and Not To Exceed times. In addition, look at the possibility of implementing the capability to incorporate the maintenance Not To Exceed times to the FOMS planner, allowing us to schedule around maintenance actions.

Task:

Assist in developing new APIs for CAMP integration with FOMS.

TASK Development 2 Maintain Current FAA- Approved Java Baseline

Keep the FOMS web modules java versions updated to avoid security risks.

Task:

Assist in converting FITS, FMDFL, FIST, FIRPS and FBR to JDK26 initially. Update to later versions as they become available.

TASK Development 3 Web User Interface (UI) Asset Refractor

To keep up with the changes within the IT industry, the FOMS team will need to restructure the existing code without changing its external behavior. This will improve code readability and reduce complexity as code styles change in the future. We will standardize FOMS with more current technology.

Task:

Assist in restructuring existing UI code to Stay Current with New Technology.

TASK Development 4 Replace Java Server Pages (JSP) in all FOMS web modules

Replace JSPs to improve overall application security.

Task:

Update FITS, FMDFL, FIST, FIRPS and FBR to use a current, FAA-approved JavaScript framework (initially ReactJS) for all web pages currently being served up as JSPs.

v

TASK Development 5 Rewrite Inspection Object and Task Web Pages

The inspection object and task web pages (including search, view, and edit pages) have become an unmaintainable, tangled mess of logic that requires more work than just upgrading the web framework component.

Task:

Assist in rewriting the inspection object and inspection task web pages.

TASK Development 6 Create an Interface Between FOMS and RMLS for Relaying Scheduling Results of Flight Inspections

Remote Monitoring and Logging System (RMLS) is used by Tech Ops to manage NAS components, systems, and services. Integrating FOMS and RMLS will use Maintenance Information Exchange Model (MIXM) data exchange schemas to publish flight inspection scheduling information and results to the SWIM application. MIXM working group has funding available to pay for integration work with MIXM and SWIM. This integration will allow an interface between FOMS and RMLS (Air Force system for NAVAIDs) for requesting flight inspections by the Air Force and relaying the scheduling/results of flight inspections back to the Air Force.

Task:

Assist in developing new APIs for RMLS integration with FOMS.

TASK Development 7 Provide Capability to add Military Procedure Packages to FOMS

Military procedures are currently added to a KSN site. We would like the military procedures to be available within FOMS.

Task:

Assist in providing an interface in FOMS to upload military procedures and make them available to FOMS and FOMS Mobile.

TASK Development 8 Automating the Process of KMZ File Hosting and Indexing

The KMZ files are vector graphics, which represent the PDF obstacle trapezoids and controlling obstacles. NGA Aero is being modified to ingest KMZ files, which will be used to verify obstacle clearance for new and amended instrument procedures. The use of KMZ files will reduce procedure development time for AIS. In addition, it will provide each flight inspector a vector overlay on their iPad during flight inspection missions, enhancing the flight inspection mission.

Task:

Assist in automating the process of verifying published and unpublished procedures from KMZ files.

TASK Development 9 Standardize Passengers and Qualified Non- Crewmembers

Aircraft Operations is requesting a new enhancement to standardize how users manage Passengers and Qualified Non-Crewmembers within FOMS, for all mission Authorizations, Itineraries, and Dispatches.

Task:

Assist in enhancing FOMS to standardize how users manage Passengers and Qualified Non-Crewmembers.

vi

TASK Development 10 Automate Calculation of Crews Based on CFR

135.267 Rest Periods

This item will automate the calculation of crews getting the required rest periods every month and calendar quarter. In addition, calculate hours as defined in CFR 135.267.

Task:

Assist in automating the calculation of crews getting the required rest periods every month and calendar quarter. In addition, calculate hours as defined in CFR 135.267.

TASK Development 11 Tracking Military and International SIAPs For Use on Datasheets

Need the ability to retrieve certain data from the military for use on the datasheets. This would require several API’s to be created to connect to new data shells that would store this information.

Task:

Assist in developing web APIs to allow data shells to be created in FOMS for tracking military and International SIAPs.

TASK Development 12 Flight Check Schedule Reporting Updates

Make additional changes requested by air traffic controllers to the flight activity map.

Task:

Assist in making changes identified by air traffic controllers to the flight activity map.

TASK Development 13 Rework AIRNAV Integration from Database to Web Services

Currently we are retrieving objects such as airports, runways, and NAVAIDS from AIRNAV through database views, which is a direct link to AIRNAV’s database. We need to change this to link to connect to AIRNAV through new APIs. This will provide better flexibility with data and a more secure connection.

Task:

Assist in developing new APIs for AIRNAV data integration with

FOMS.

TASK Development 14 FIRPS Report Distribution

Enhance FIRPS to be able to distribute reports to military personnel.

TASK Development 15 Security Documentation Produce security documents required for authority to operate (ATO).

Tasks:

• Create PTA

• Create SCD

• Create SSP

Create ISCP TASK Development 16 Automated Test Coverage and Build Pipeline Modernization

Establish automated unit, integration, and regression test coverage for the FOMS web modules and modernize the build and deployment pipeline. This coverage is a prerequisite for safely executing the large-scale user interface refactor and page rewrite tasks.

Task:

Assist in developing automated test coverage for the FOMS web modules and in modernizing the associated build and deployment pipeline.

vii

TASK Development 17 Cross-Module Data Integration Remediation

Several FOMS modules exchange data by reading and writing shared database tables directly rather than through defined service interfaces.

This creates defects that are difficult to isolate and that can interrupt daily flight operations.

Task:

Assist in refactoring shared database dependencies into governed application programming interfaces and in standardizing data conventions across the FOMS modules.

TASK Development 18 Data Retention, Archiving, and Performance

Implement a data retention and archival strategy for aging operational data and address the associated database and query performance.

TASK Development 19 Reporting and Data Analytics

Develop consolidated operational and management reporting across the FOMS modules.

Task:

Assist in developing data extracts, reports, and dashboards for Flight Program Operations management.

TASK Development 20 Continuity of Operations Support

Support periodic disaster recovery and contingency plan exercises for the FOMS applications.

Tasks:

• Support failover and recovery testing.

• Remediate findings identified during contingency exercises.

TASK Development 21 Documentation and Training Materials

Maintain system documentation, user guides, and training materials as FOMS functionality changes during the period of performance.

Task:

Assist in updating FOMS system documentation, user guides, and training materials.

TASK Development 22 Expanded Capabilities Various tasks to be identified as development continues and as Flight Program Operations' workflows and requirements evolve.

5.0 Advertisements, Publicizing Awards, and Releases

a. The Contractor must not refer to this contract in commercial advertising or similar promotions in such a manner as to state or imply that the product or service provided is endorsed or preferred viii by the Federal Government or is considered by the Government to be superior to other products or services.

b. All advertisements, releases, announcements, or other publication regarding this contract or the agency programs and projects covered under it, or the results or conclusions made pursuant to performance, must be approved by the Contracting Officer. Under no circumstances shall the Contractor, or anyone acting on behalf of the Contractor, refer to the supplies, services, or equipment furnished pursuant to the provisions of this contract in any publicity, release, or commercial advertising without first obtaining explicit written consent to do so from the Contracting Officer.