Operations Contingency Tool (OCT)

*Amendment 3: Operational Contingency Tool (OCT) Request for Information The purpose of this Amendment is to invite the previous respondents to this Market Survey to hold follow-on discussions with the FAA in reference to OCT program. If you did not respond previously respond to this Market Survey, the FAA will not hold follow-on discussions with you in reference to the OCT program. The previous respondents that wish to have follow-on discussions must submit the questions/clarifications to Keturah Stroy [email protected] and Patrick Weare [email protected] NLT, Thursday, July 29, 2021. The FAA will then contact respondents to schedule a date and time to hold discussions. The FAA anticipates holding discussions the week of August 9 through August 13th. *Amendment 2: Operational Contingency Tool (OCT) Request for Information The purpose of this Amendment is the following: Remove the note under Section VII regarding the FAA Order 1370.121, FAA Information Security and Privacy Program & Policy. The FAA will not be releasing this document as part of this Market Survey/RFI. Revise the response date to Friday, April 30, 2021 at 2:30p EST. All other content remains unchanged. Operations Contingency Tool (OCT) REQUEST FOR INFORMATION (RFI) This Market Survey/Request for Information (RFI) is being issued in accordance with the Federal Aviation Administration (FAA) Acquisition Management System (AMS) Policy at 3.2.1.2.1. The AMS applies to the FAA in place of the Federal Acquisitions Regulation (FAR) and various other provisions of Federal acquisition law. Disclaimers This is not a Screening Information Request (SIR) nor a Request for Offer (RFO). The FAA is not seeking or accepting unsolicited proposals. Respondents are advised that the FAA will not pay for any information received or for administrative costs incurred in preparing a response to the Market Survey/RFI. Any costs associated with responding to this survey are solely at the interested vendor’s expense. The FAA does not intend to publish the results of this Market Survey/RFI. The following disclaimers also apply to this Market Survey/RFI: (1) The FAA is not seeking marketing material; (2) Any information and materials submitted in response to this announcement will not be returned; (3) The FAA is generally not seeking proprietary material. If the respondent feels there is a benefit to providing certain proprietary material, they must mark it as such, and they are responsible for its security in transport; (4) Any and all material submitted – whether proprietary or not – may be used to develop FAA’s acquisition strategy. If respondents do not want specific information used in this manner, then such information should not be submitted; (5) Providing a response to this Market Survey neither qualifies respondents for, nor excludes respondents from, responding to a resulting SIR, if any; (6) The responses to this Market Survey will be used for information purposes only and will not be released, except as required under the Freedom of Information Act (FOIA). Proprietary information that is appropriately marked will be protected in accordance with FOIA. (7) The Attachments (DRAFT OCT Section C - Statement of Work, DRAFT Attachment J-1 Contingency Application Requirements (CAR), and DRAFT Attachment J-2 Enterprise Information Management (EIM) Data Platform Overview) to this Market Survey/RFI are not final documents and are intended for informational purposes only. The FAA reserves the right to revise these draft documents based on comments received. Any and all subsequent revisions to the aforementioned documents remains solely at the Government’s discretion. (8) An acquisition strategy has not been determined at this time. I. PURPOSE The FAA is soliciting Industry interest and capability to provide solutions to meet the requirements to deliver an Operations Contingency Tool (OCT) application. The purpose of this RFI is to explore solutions to satisfy the requirements identified in the DRAFT OCT Section C Statement of Work and DRAFT Attachment J-1 Contingency Application Requirements (CAR). This Market Survey/RFI will assist the FAA to: • Validate the feasibility of acquiring a Commercial-off-the-Shelf (COTS) application and the amount of customized development to satisfy the requirements to deliver an OCT application • Determine the quantity of potential Offerors • Determine if the requirements can be met by small business, and • Refine its acquisition strategy and requirements The principal North American Industry Classification System (NAICS) codes for this effort being considered are the following: 518210 Data Processing, Hosting, and Related Services 541511 Custom Computer Programming Services 541513 Computer Facilities Management Services 541519 Other Computer Related Services II. INTRODUCTION As operational contingency planning is a key component to ensure safety and continuity of services in the National Airspace System (NAS), the Federal Aviation Administration (FAA) establishes requirements and responsibilities for the development, implementation and exercising of Operational Contingency Plans (OCPs). Comprehensive and coordinated planning between air traffic control facilities, stakeholders, and organizations that support the NAS can avert disruptions or mitigate their impact to safe and reliable service to the flying public. The FAA Directorate of Operational Readiness plays an important role in preparing the FAA to efficiently and safely manage operational disruptions to include: • Providing guidance and review of operational contingency plans (OCPs) • Maintaining and improving methods/systems to manage and share OCPs • Identifying and influencing development of Next Generation Air Transportation System (NextGen) technologies to improve the ability of the FAA to reduce effects of air traffic control (ATC) service disruptions • Ensuring procedures for contingency are available and that training is provided and performed III. CURRENT OCP APPLICATION The FAA currently utilizes a FAA-owned application called Automated Contingency Tool 2 (ACT2) as a repository of the OCPs for each ATC facility. ACT2 is the primary means of sharing, coordinating, and accessing OCPs across the NAS. Currently, the the existing tool has the following limitations: • Insufficient guidance and training for design and development of OCPs • No coordination of OCPs with impacted and support facilities referring to a rigorous process enacted to track , review and approval by those users responsible of developing and approving OCPs. • Lack of OCP developer access to up-to-date information (e.g., frequencies, landlines, surveillance sites) • Significant workload impact due to manual efforts to report events FAA has determined that ACT2 is not capable of meeting the current and future anticipated needs for operational contingency planning, and a replacement system is necessary. IV. FUTURE OCP APPLICATION The future OCP application, herein referred to as the OCT application, will enable data-driven contingency operations and improve the efficiency planning, execution, post-event analysis, and training during all operational contingency level (OCL) events. The OCT application will also: • Improve access to OCPs to increase efficiency during execution of a contingency event • Improve coordination to reduce time for airspace users to re-establish communication with other ATC facilities • Improve coordination during a contingency event to facilitate the re-establishment of services from alternate ATC facilities more efficiently • Increase readiness of personnel and facilities to cope with the expected or unexpected loss of an ATC facility outage through OCP exercise support • Improve support for post-event analyses, such as assistance in lessons learned reporting and trend analyses The FAA anticipates that the OCT application will utilize FAA Cloud Services (FCS), which will provide core Infrastructure as a Service (IaaS) on the FAA FedRamp certified Government Cloud (GovCloud) operated by Amazon Web Services (AWS). The OCT Application will also utilize the Enterprise Information Management (EIM) Platform-as-a-Service (PaaS) and Data-as-a-Service (DaaS), which provides common enterprise information management components that can be reused and built upon. V. MARKET SURVEY/RFI SUBMITTAL INFORMATION The FAA requests the following information from interested vendors: 1. Capability Statement that demonstrates your firm’s solution and capability to meet OCT requirements to include the following: a. Services provided by your firm b. Relevant past experience information to include customer, point of contact, dates, description of the work, project value and your firm’s participation (Prime, subcontractor, or supplier) c. Identify any relevant certifications such as Capability Maturity Model Integration (CMMI), International Organization for Standardization (ISO), and Information Technology Infrastructure Library (ITIL) or others d. Potential teaming approach (e.g., Prime, Subcontractor, Supplier) 2. Completed Business Declaration Form (attached) 3. Responses to the following questions: a. Are the requirements (i.e., Draft SOW, Draft Attachment J-1) sufficiently detailed to allow you to propose and price your solution? If not, what additional information is needed in the Draft SOW, Draft Attachment J-1) or Draft Attachment J-2? b. Discuss the maturity of your solution and the amount of adaptation and customization necessary to satisfy OCT requirements. c. Discuss the types, capabilities, description, sources and amount of Open Source software utilized in your solution. d. Does your solution include customizable templates that are tailorable to meet user needs? Please explain. e. Does your solution support the development of automated workflows? If so, please explain these capabilities and any limitations. If it does not support development of automated workflows, please identify how those capabilities may be added and what limitations may apply. f. Does your solution support an open application program interface (API) for interfacing to other applications? Please explain. g. Discuss any user limitations associated with your solution to include, but not limited to, the maximum number of simultaneous users. h. Discuss any training (e.g., user, system admin, SW maintenance) provided to enable different users of the solution to effectively utilize and maintain the solution. Contrast the existing capabilities with the SOW and associated requirements, and what development is needed to satisfy the training needs identified. i. Describe your experience providing your solution to Federal Government clients in Cloud-based environments (e.g., Private, Government and/or Public). j. Has your solution ever been certified based upon NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations? If so, at what system impact characterization (high, moderate, low)? If the solution was based on Federal Government cloud services, please identify the FEDRAMP provider or certification information. k. What type of licensing agreements do you offer for your solution? Please provide software license terms and conditions if the solution includes licensing agreements. l. What software maintenance agreements do you offer for your solution? m. Do you provide a software development kit (SDK) as part of your solution? Please explain the SDK purpose, function, and capabilities. n. What interfaces do you support to import and export data to/from the vendor’s OCT solution? o. What technical documentation is needed to fully utilize, operate and maintain your solution? p. What software development process and methodology would you utilize to satisfy the OCT requirements? Please provide feedback on the identified software development requirements contained in the Statement of Work. q. Please provide a high-level rough order magnitude (ROM) to satisfy the OCT requirements. Please utilize the SOW when providing ROM estimates. NOTE: ROM information will be used for planning and budgetary purposes only. This is not a request for proposal and does not constitute any sort of pricing agreement. r. What were the most important considerations in choosing your solution? Please explain. VI. SUBMISSION INSTRUCTIONS Interested parties must provide their responses in writing. Interested parties should include their organization point(s) of contact, title(s), telephone number(s), email address(es), and mailing address in their submission. Responses should be no more than 25 pages long, single spaced, 12-point Times New Roman font and must be in MS Word format. Please limit company background information to one page. The FAA may offer interested vendors the opportunity to demonstrate their solution. Interested vendors must express their interest at the time of their RFI response. The FAA may request one-on-one discussions in which respondents to this Market Survey may be invited to discuss their responses in more detail. If contacted, respondents’ participation is voluntary, but would be appreciated. Responses must be submitted electronically no later than April 30, 2021 at 2:30pm, EST to the Contracting Officer, Mr. Patrick Weare at [email protected] and Contract Specialist, Mrs. Keturah Stroy at [email protected]. Any proprietary or confidential information contained in the Market Survey submissions must be appropriately marked. VII. ATTACHMENTS 1) DRAFT OCT Section C - Statement of Work 2) DRAFT Attachment J-1 Contingency Application Requirements (CAR) 3) DRAFT Attachment J-2 Enterprise Information Management (EIM) Data Platform Overview 4) Business Declaration Form