Questions_Answers_ NOTAMS_Industry_Roundtable.pdf
PDF 207 KB Posted
- Solicitation number
- Not on record
About this file
This document contains questions and answers from an industry roundtable held by the Federal Aviation Administration to discuss modernizing the NOTAM and Aeronautical Information systems and services. The roundtable focused on gathering industry feedback to help define requirements for a new integrated digital solution. The FAA is pursuing a challenge-based acquisition and expects to release a final Statement of Objectives in Q2 FY24. It will invite concept papers from offerors and plans to discuss proposed solutions and provide a sample problem to demonstrate extensibility. The goal is to award a prototype project later in FY24 to develop an initial capability for managing temporary aeronautical data events through an expandable architecture that can eventually incorporate all aeronautical information management.
View the file
Other files
Show all 14
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
QID Question text Answer Group with Other Questions (List QID)
Question Source Document Page Reference Paragraph
001 What urgencies are your highest priorities to tackle quickly, assuming resilience solves the problem that the January 20th event caused?
The objective is not to update the existing system(s) but to develop a new integrated aeronautical information solution.
As mentioned in the SOO, the initial capability could be managing the lifecycle of temporary events that result in the issuance of NOTAMs as long as the platform can be expanded to manage the static state of aeronautical features.
Slido
002 is faa empowered to relieve lengthy SDLC req's to apply modern development practices (agile) so that innovative approaches can be develop an incremental. soln?
We are looking at new ways of software development leveraging industry best practices.
Slido
003 There have been a number of allusions to moving fast - does the FAA have an ideal timeline for deployment?
The timeframe for deployment is dependent upon the approach proposed in the concept papers. We look forward to hearing from you on innovations and strategies that meet the FAA’s objectives and support timely delivery and transition into the NAS.
Slido
004 Malcolm, you mention modern development principles. Is it key for FAA to maintain control of the system, will you buy SaaS product that the vendor controls?
We are open to hearing any suggestions or ideas you may have.
Slido
005 What is your target timeframe to deploy a system (even with partial functionality) (MVP)?
The timeframe for deployment is dependent upon the approach proposed in the concept papers. We look forward to hearing from you on innovations and strategies that meet the FAA’s objectives and support timely delivery and transition into the NAS.
Slido
006 Is the FAA thinking about this as a clean-sheet design or something that hews more closely to an update and modernization?
A new and innovative integrated aeronautical information solution is envisioned.
Slido
007 Natesh mentioned "truly trustworthy". Existing government driven V&V processes take a long time. What are the thoughts around speeding up the processes?
The approach described here is stating our business objectives rather than detailed requirements. The government goes through validation and verification (V&V) processes to ensure system reliability and performance measures are evaluated and met.
Slido
008 Agile development of newer systems requires agile acquisition/procurement vehicles. Is the FAA looking at changing the procurement practices to meet the needs
The FAA is considering the use of a Challenge Based Acquisition (ChBA) potentially resulting in an other transaction agreement(s) or contract(s).
Slido
009 What is the difference between this and the ongoing FNS Sustainment?
The FNS Sustainment project began a few years ago with the aim of consolidating the two existing NOTAM systems into a single NOTAM repository. The project also entails transitioning off old hardware and moving to a virtual platform.
The primary goal of this new effort is to position the FAA for the future by creating an integrated aeronautical information solution that goes beyond NOTAMs, to provide a real-time standards-based data management platform utilizing the advancements in technology to make the system more efficient, reliable, and sustainable for the future.
Slido
010 How is the FAA approaching this acquisition with regard to commercial product available off the shelf versus tradition custom development by System Integrators?
We are open to hearing any suggestions or ideas you may have.
Slido
011 How much ICAO compliant you want the future system to be? The main goal is to develop a digital system that can capture both permanent and temporary changes as events and transmit them using globally recognized standards such as AIXM. It is important to consider transforming these digital data into the current FAA format, ICAO, and plain language to ensure compatibility and ease of transition.
Slido
012 NOTAMs is a public data provider; what does this mean for compliance if the data is now public domain? How will FAA separate Govt data from public?
The management of aeronautical information, including NOTAMs, must comply with relevant FAA policies and regulations. Therefore, it should be considered during the design and development of the solution.
Slido
Question Source Document Page Reference Paragraph
013 You have said that you want the new NOTAMS system ASAP.
Does the FAA have a timeline or deadline to sunset the legacy system?
The current system is old, however we can't sunset it until a new solution is in place. We are interested in how we can do it as fast, innovative, and creatively as possible.
Slido
014 Is anyone thinking about the downstream problem of people not reading NOTAMs, or not receiving NOTAMs that come through during a cross-country flight?
Yes, this is a concern to the FAA because it creates issues for pilots and air traffic control.
Slido
015 Has the faa engaged or been directed to engage external groups like the US digital devices team to bring their modern sw dev practices practices to NOTAMs?
The FAA is gathering information around all aspects of the acquisition to inform the final acquisition strategy and approach.
Slido
016 the SOO referred to short term data (i e NOTAMs) and longer term data (i e all of the rest of AI) . Does the AIM concept include functionality of AIMM program?
The overarching goal is to develop an integrated solution capable of facilitating real-time, standards-based aeronautical information management. While the ultimate aim is a comprehensive system, the initial phase could involve the implementation of the NOTAM module or the management of dynamic data. It is crucial that, even in this initial delivery, the underlying architecture and solution are designed with expandability in mind. This ensures seamless integration and expansion to accommodate the static counterpart of NOTAM data in subsequent phases.
Slido
017 What NOTAM policy changes are in progress to relieve the legacy system burden on the new system requirements ?
The NOTAM Policy undergoes regular reviews and updates to ensure that accurate and timely data is available to the user community. The goal is to have a digital solution that enables real-time capture, management, and distribution of aeronautical information. However, the system should also provide current products like NOTAMs to facilitate a smooth transition.
Slido
018 Is the MVP concept also financed as part of the V&V acquisition Strategy ?
The FAA is gathering information around all aspects of the acquisition to inform the final acquisition strategy and approach.
Slido
019 The criticality/complexity of the new NOTAM require a solution by a large vendor with proven experience in moving mission-critical data flawlessly. Do U agree?
As stated in the industry round table session, the FAA is open to all potential approaches to developing the NOTAM and AI Solution.
Slido
020 The language of 7930.2 has been taught to Controllers and Pilots for eons. Plain language requires cultural change and union negotiations. Is this considered?
Transition is a crucial aspect of the solution. While digital data and plain language are necessary to move forward, the current approved NOTAM format is also required to continue operations and enable a seamless transition.
Slido
021 What are the most significant actions that faa is doing on this procurement to apply innovative approaches & are those actions expected to achieve objectives?
We have embraced a challenge-based acquisition approach to actively encourage innovative proposals from the industry to achieve the NOTAM and AIM objectives as described in the SOO. Your suggestions and ideas are not only welcome but integral to the success of this collaborative initiative.
Slido
022 Working backwards, keeping pilots informed of impacts to their route is the aim (pun intended). Are you considering change to the pilot’s electronic flight bag?
The objective is to develop an integrated aeronautical information solution that could serve as the basis for future modernization of downstream systems and applications.
Slido
023 Why is this a hard problem? There are no shortage of tech companies (Netflix, YouTube, etc.) that move way more data, way faster
From a pure technology and data perspective, this isn't a hard problem. NOTAMs are essentially just event based aeronautical information - real time, standards-based information management is the key.
That said, should not underestimate the challenges of transition and making changes to the NAS. Pilots are used to seeing things a certain way. This is not just a new app to be deployed. Change in the NAS has to be managed carefully and smartly. There are also complexities driven by how the NAS operates today.
36 Slido
Question Source Document Page Reference Paragraph
024 Is the FAA considering expanding the use case of NOTAMs/AIM to encompass new entrants such as UAS operators, UAM, etc.
We are open to hearing any suggestions or ideas you may have.
Slido
025 Sometimes commercial mapping systems will be inaccurate.
What assurances or cross-checks will be used if commercial geo services will be embedded?
We cannot underestimate data quality and reliability requirements. Data modeling and quality standards from ICAO must be taken into consideration in the future system as well.
Slido
026 John seems to be saying the existing process is fine, don't change it? Is that contradictory to modern technologies and automation?
During Industry Day, it was discussed that the policy behind NOTAMs (7930.2) is reviewed and updated on a regular basis. The aim is to have a modern and integrated solution that is in line with this policy. The goal is to have a fully digital solution that allows capturing and encoding changes into a digital message. However, the FAA also recognizes the need for a transition period where the textual NOTAM formats are supported. Therefore, the concept of transforming to policy-compliant NOTAM formats using the digital message as a foundation was discussed.
Slido
027 Is the FAA modifying the current FNS/USNS system to implement ICAO NOTAMs prior to new system?
The NOTAM format is governed by the FAA’s NOTAM Policy (7930.2); therefore the timing for implementing the ICAO format will depend on policy publication and the operational viability of the available solution.
27, 124 Slido
028 Can you please prioritize answering the questions that industry has ranked?
While providing the required information during Industry Day, we made every effort to answer the questions to the best of our ability. Responses to all questions received are provided in this document.
Slido
029 Architecturally, is the current FAA AIM Environment a monolith?
What's the underlying infrastructure footprint look like?
During Industry Day, it was presented that there are more than a dozen independent systems in place to manage their respective data sets. These systems vary in architecture, with some following a monolithic design that are over two decades old, while others have adopted a service-oriented architecture pattern. Most legacy systems run on Oracle/Sun SPARC hardware.
74, 91, 107, 112, 113 Slido
030 You mention siloed technologies and programs but we also see siloed teams (techops, ajm). Is FAA looking to modernize dev process and integrate teams?
Collaboration between FAA Program Management Organization (PMO), Technical Operations, and others is critical in developing and operating AIM systems. This will continue with the proposed activity.
Slido
031 Reference to voice translation ideas: since this isn’t fully viable in other domains (e.g. healthcare) is it ready for NOTAMs? How would you plan for it?
Planning for future innovations and technologies can start with the foundational design and data approach. Adoption of some technologies will also need careful planning and software assurance considerations prior to deployment in the NAS. We look forward to innovative ideas from industry.
Slido
032 How many NOTAMs user interactions are there per year? NOTAMs are classified into Domestic, FDC, Military, and international categories. In 2022, the NOTAM system processed 3.83 million NOTAMs. However, weather significantly affects NOTAMs, causing fluctuations. These numbers reflect the current state and are expected to increase based on observed trends.
Slido
033 One of the largest challenges the NOTAM system has today is the number of NOTAMs in the system. What is being done to fix issues like this that currently exist?
Modern systems process a large number of transactions, making the volume of NOTAMs insignificant in comparison.
However, the challenge lies in the textual nature of NOTAMs which makes it difficult for pilots and other consumers to retrieve relevant information. This is why a fully digital solution is necessary to ensure that consumers can quickly access the information they need, regardless of the volume of NOTAMs.
52, Slido
Question Source Document Page Reference Paragraph
034 How do you define "workflows" and "business" rules contextually and how do these affect actual consumption and usage?
Workflows refer to the flows of data and decisions throughout the system - and may include automation as well as human interaction.
Refer to question 88 for information on business rules.
88, 89 Slido
035 How much data, on average needs to be processed? Monthly, Annually?
In 2022, annual NOTAM volume was 3.83M. NOTAM volume fluctuates seasonally. In 2022, it ranged from approximately 255K to 445K with a monthly average of 320K.
Slido
036 What constraints or limitations or boundaries do you foresee for transition?
See response to question 23 for high-level considerations for transition within the NAS.
23 Slido
037 AIM Enhancement 1 looks set to modernize the ACS. How will you ensure this work is consistent with creation of the new NOTAMs system?
We need to ensure the requirements for AIM and ACS is part of the overall Aeronautical Information modernization. The FAA wants feedback on what makes sense.
Slido
038 Are there any business objectives or service levels you envision besides that the system shall be innovative? What are business objectives behind the buzzwords?
Compliance with FISMA high requirements is necessary for the NOTAM solution. Given the criticality of aeronautical information and especially NOTAMs, a 99.99% availability requirement should be considered during the design of the solution and its supporting infrastructure. Additionally, the FAA is open to understanding from industry how we should be thinking about service levels. Operationally, any real-time changes to the NAS need to be made available to everyone who needs it to support efficient and safe airspace operations.
Slido
039 Do you plan the full transition from FAA domestic NOTAM format to ICAO NOTAM format prior or during or after the new system implementation or not at all?
Refer to response to question 27. 39, 124 Slido
040 How will the Government ensure NAS requirements and use cases are represented in any future solution? Do you have all the requirements/use cases identified?
The FAA has defined our objectives for the future solution in the SOO.
Slido
041 Following up on Natesh’s comments, what are the expectations of the FAA for the technology system provider to support or manage the NAS transition?
The transition of the NOTAM solution into the NAS is a critical consideration for a future solution. The FAA anticipates a partnership with the future vendor. Specifics of supporting that transition may vary based on the solutions proposed and would be determined in the future.
Slido
042 We've talked a lot about the FAA learning from industry on the approach. What does industry need to learn from the FAA in order to make this a success.
The FAA's objective, as detailed in the Statement of Objectives (SOO), serves as a framework. We anticipate that this framework will inspire the industry to present innovative proposals, positioning the FAA strategically for the future.
Slido
043 The faa can't solely rely on industry innovations to achieve objectives. What innovative changes will faa make to equally apply innovation to meet objectives?
FAA's commitment to innovation is reflected in its technical vision and challenge-based acquisition approach presented during Industry Day. FAA welcomes feedback from the industry.
Slido
044 Melissa previously mentioned COTS or custom software is on the potential roadmap, however Malcolm just mentioned solely COTS. What is the FAA looking at?
We are open to hearing any suggestions or ideas you may have.
Slido
045 What will be the next step? (Schedule wise) As mentioned during Industry Day, a final SOO will be released with the request for concept papers with a target of
Q2 FY24.
Slido
046 Malcolm, “at least what it does today” ties your hands. If you reinvent communicating with pilots to ensure understanding, don’t you want to start elsewhere?
This is focused on outcomes and operational context - not specifics of the technology or design. Essentially, the future NOTAM and Aeronautical Information solution(s) need to provide information to the users so that can safely arrive at their destination.
Slido
047 the FAA wants something quick. Also, the selection is challenging acquisitions. The question is: do you foresee a timeframe for the selection process?
Per the industry round table discussion, the FAA is currently planning on entering into the first phase of the acquisition in the 2nd quarter of FY24.
Slido
Question Source Document Page Reference Paragraph
048 For Malcolm: instead of changing the wheel on the bus, should we be driving the bus onto a hovercraft?
We look forward to innovative ideas from industry. Slido
049 It sounds like the FAA would like to remove human in the loop as much as possible, how will you plan to ensure the FAA’s safety mission is met with new tech?
We are open to hearing any suggestions or ideas you may have.
Slido
050 To Angel: LOVE this. Some of us vendors may need to get together to seember best solutions. Can you please insert a matchmaking day (just before concept paper)?
The FAA is considering potential Match Making sessions as part of creating and encouraging strong partnerships for this acquisition.
Slido
051 For the concept papers, will companies who are currently at the FAA have an advantage over newer entrants in terms of brand recognition and the “trust factor”?
The FAA is pursuing a full and open competition for this effort aso all vendors will have the same opportunity with a focus on innovation.
Slido
052 The problem isn't transferring 3.8M NOTAMS, but that pilots must READ them all & comprehend the impact on a flight.
Wouldn't reducing the number be vital?
See response to related question 33 on NOTAM volume. 33, Slido
053 Kudos to FAA to think out of the box in terms of acquisition approach.
Thank you, no question presented. Slido
054 give us a week and some coffee! !USA 11/001 FAA YOU CAN TAKE MORE THAN A WEEK
FOR AN INNOVATIVE DIGITAL AIM SOLUTION :-)
Slido
055 what’s the potential for impacting the timeline if the government funding is impacted due to legislative delays. There are many unknowns related to potential legislative delays. Assessment of specific impacts to the challenge-based acquisition timeline presented during the NOTAM and Aeronautical Information Industry Day will depend on details of any potential legislative delays.
Slido
056 Timeline looks great. In fact, we should look at doing it faster. We are open to hearing any suggestions or ideas you may have.
Slido
057 Given the increasing reliance on this information for critical safety of life applications (e.g. auto landing) is there a target software assurance level?
We cannot compromise on the quality and integrity of the data. More specific details will be determined as we move through the process.
Slido
058 Could vendors submit multiple concepts? Yes, if the concepts are significantly differentiated. Multiple submissions that represent small variations are discouraged.
Additional guidance will be provided for concept submissions as part of the initial acquisition activities.
Slido
059 Some agencies, especially GSA, have done demo challenges for years. Possible to collaborate with them on process and evaluation points?
See question 15 Slido
060 Is the brand new administrator holding the modernization of everything we've spoken about today as a key priority of his tenure?
Slido
061 Any requirements to prime? Product experience, facility clearance, etc? Would a small be able to prime?
See question 15 Slido
062 Which question would you have liked to answer and we (industry) forgot to ask?
The industry covered a wide range of topics and questions.
Thank you for actively participating.
Slido
063 In reference to infrastructure, what changes does the FAA perceive for modernizing the infrastructure for NOTAMS I.e multiple locations across U.S. etc.
Refer to response to question 97. 97, 98 Slido
064 Will the faa consider giving industry a design to cost target?
Budget is a big challenge we keep hearing this week.
See question 15 Slido
065 Angel to support AQN timelines we recommend that you consider the "advisory downselect" process. Does the faa anticipate using that type of down-select process?
See question 15 Slido
066 Is the FAA providing the underlying infrastructure for the future system, e.g. a digital platform or equivalent? Or is it left for the suppliers to propose one?
We are open to hearing any suggestions or ideas you may have.
Slido
067 Limitations inherent to the appropriation and funding processes have impeded innovation for years. How will FAA mitigate those?
See question 15 Slido
068 This process is similar to the Other Transaction Authority procurements OTA run by the DOD for their Telco modernization- similar to RPP process.
No question presented. Slido
Question Source Document Page Reference Paragraph
069 Other agencies have faced similar challenges. Has the FAA reached out to others in Govt to harvest lessons learned, re sys dev/impl as well as the acq process?
See question 15 Slido
070 What does the FAA currently spend on NOTAMS? The NOTAM system is managed by multiple organizations, each handling different aspects such as management, testing, maintenance, etc. Due to the involvement of various organizations, it is challenging to provide a single cost estimate. The proposed aeronautical information solution aims to integrate independent legacy systems for enhanced data management efficiency, leveraging technological advancements to create a more reliable and cost-effective solution. Therefore, comparing the costs of operating the current legacy systems may not be the most meaningful metric when evaluating the proposed solution's economic viability.
Slido
071 Design to cost: great questions! When will we see NOTAMs reflected in the budgets?
Slido
072 What is the foreseen policy on the IPRs of the future solutions? Slido
073 We appreciate all the flexibility and openness, thank you all! Thank you for taking part and for the industry's active engagement.
Slido
074 Need better understanding of background -- heard FORTRAN, Assembly, … is this running on a mainframe? X.86?
We provide some background on the current NOTAM system architecture in question 29. The specifics of the current hardware and software are less important compared to the modern concepts we are looking for. During Industry Day we asked industry what additional information industry would need to formulate your concept paper.
29, 91, 91, 107, 112, 113 Live from Industry Day
075 Initial RFI was focused on NOTAM modernization. The SOO expands the scope to complete Aeronautical Information (AI) Modernization. Is NOTAM modernization still an FAA’s Priority?
Yes, NOTAM modernization is still a priority – the objectives around an expandable architecture that supports NOTAM functionality first with future phases to include AI address this.
Vendors from SAM (Pre Industry Day)
076 Can FAA share the procurement strategy and timelines? Is FAA considering a single procurement to include all phases or multiple procurements?
The FAA will provide additional procurement strategy information once the first phase of the acquisition has been initiated. Per the industry round table discussion, the FAA is currently planning on entering into the first phase of the acquisition in the 2nd quarter of FY24.
Vendors from SAM (Pre Industry Day)
077 In case, the procurement strategy and timeline is currently not available. Can FAA share when such information might be shared?
The FAA will provide additional procurement strategy information once the first phase of the acquisition has been initiated. Per the industry round table discussion, the FAA is currently planning on entering into the first phase of the acquisition in the 2nd quarter of FY24.
Vendors from SAM (Pre Industry Day)
078 During the RFI stage, FAA had expressed a strong preference for COTS solution. Is FAA still considering a COTS based solution as part of NOTAM/AI modernization?
Yes, the FAA is interested in a range of innovative options from industry that address the high-level objectives for a future AIM/NOTAM solution.
Vendors from SAM (Pre Industry Day)
079 Please provide clarification on the FAA's intent for the new NOTAM hosting & development environment. Will the FAA provide the hosting / development environment as GFE in time for the new program or will the Offeror bring 100% of the solution?
As described in the SOO, the future solution should use a modern scalable and elastic architecture that operates reliably across diverse hosting environments. The solution should prioritize consistency, portability, and efficiency in resource utilization while also supporting swift, secure, and flexible deployment and scaling in an agile and dynamic IT landscape.
The FAA is looking forward to ideas and recommendations from industry on the delivery model and environment.
115, Vendors from SAM (Pre Industry Day)
080 Is there a NAS plan to stand up a single consolidated data repository within the OpIP?
We are looking forward to ideas and recommendations from industry in the concept papers.
116 Vendors from SAM (Pre Industry Day)
Question Source Document Page Reference Paragraph
081 Please provide clarification and definition of the FAA's "contemporary service delivery model". What are the features and service outcomes the FAA is looking for in this model?
What are the Service Level Agreement (SLAs) the FAA is contemplating? What are the major business objectives?
Please see responses to questions 38 and 79 as well as the FAA objectives in the SOO for related information.
38, 79, 117 Vendors from SAM (Pre Industry Day)
082 Please define the level of systems availability required for the new system.
Our current requirement is for 4-9’s or 99.99% availability. 118 Vendors from SAM (Pre Industry Day)
083 Is the modernization / replacement of existing legacy NOTAM systems involved in origination and distribution in scope of the potential procurement?
The future NOTAM and Aeronautical Information solution will support the full scope of the current operational needs.
119, Vendors from SAM (Pre Industry Day)
084 Will the FAA NAS Security policies and orders apply to the new NOTAM system?
Yes, FAA security policies will apply for future solution(s) integrated into the NAS.
120, Vendors from SAM (Pre Industry Day)
085 Could you provide insights around the projected timeline for this effort?
Per the industry round table discussion, the FAA is currently planning on entering into the first phase of the acquisition in the 2nd quarter of FY24.
Vendors from SAM (Pre Industry Day)
086 What Aggregate Size of the Data Volume for the System? Refer to response to question 35. 35, Vendors from SAM (Pre Industry Day)
087 Is a "Clear Text" NOTAM Unstructured? If Not, How Would it be Defined?
A "clear text" or non-digital NOTAM does not have all of its data elements fully encoded in the AIXM model. For instance, the NOTAM condition would be a single text block. Note, the basic elements of a NOTAM (e.g. Accountability, Location, Effective Date, Expiration Date, NOTAM Condition, etc.) can and should be captured within structured AIXM data elements for both digital and non-digital NOTAMs in the future system.
Vendors from SAM (Pre Industry Day)
088 When the FAA refers to "rules", are they specific to AIXM processing (e.g. XML Schemas) or are they specific NOTAMS rules not covered by the existing AIXM 5.1 Business Rules v.0.91?
Business rules span a range of types in the context of the NOTAM system. Some examples include the business rules related to AIXM 5.1 specification, NOTAM policy, and digital NOTAM event specifications (or scenarios).
89, 34 Vendors from SAM (Pre Industry Day)
089 What specific business rules will the FAA assign to the NOTAMS system?
Refer to response to question 35. 88, 34 Vendors from SAM (Pre Industry Day)
090 For integration purposes, what are the current Single Sign-On authentication solutions?
The FAA has an enterprise wide SSO platform, MyAccess. Vendors from SAM (Pre Industry Day)
091 What are the mixture of software components, multiple standalone databases, and the legacy infrastructure components that are in the current system environment?
We provide some background on the current NOTAM system architecture in question 29. The specifics of the current hardware and software are less important compared to the modern concepts we are looking for.
29, 74, 107, 112, 113 Vendors from SAM (Pre Industry Day)
092 What are the nine (9) tools for originating NOTAMS and the seven (7) tools for distributing NOTAMS?
The current NOTAM ecosystem is comprised of two systems:
the NOTAM System and the Legacy NOTAM System. There are mulltiple origination and distribution interfaces, both human and machine, from each of the current NOTAM systems. Refer to slide 18 from the NOTAM Industry Day slides for a conceptual diagram.
Vendors from SAM (Pre Industry Day)
093 Which (and in what order, if known) existing and future FAA systems, services, infrastructure, and programs to be integrated into the new NOTAMS system?
This would be dependent on the approach and timing of the proposed solution(s). We are open to hearing any suggestions or ideas you may have.
Vendors from SAM (Pre Industry Day)
094 When is the anticipated date for the release of the draft RFP?
This might be known at the industry day, but I am going to ask anyway.
Per the industry round table discussion, the FAA is currently planning on entering into the first phase of the acquisition in the 2nd quarter of FY24.
Vendors from SAM (Pre Industry Day)
095 Will the FAA consider non-NOTAMS related aeronautical information work as a plausible exception for Past Performance.
(Ex. A contract with DoD or any other agency conducting aeronautical information work other than the FAA).
The FAA will provide details around what is required for past performance reporting once the first phase of the acquisition has beenn initiated.
Vendors from SAM (Pre Industry Day)
Question Source Document Page Reference Paragraph
096 How many years of PP (Past Performance) are the FAA looking for the contractor to have?
See question 95. Vendors from SAM (Pre Industry Day)
097 What geographical areas are the FAA planning to utilize for the NOTAM centers?
The specific geographic locations wil be determined dependent upon the proposed solution(s). We are open to hearing any suggestions or ideas you may have.
98, 63 Vendors from SAM (Pre Industry Day)
098 Will these facilities need to be newly constructed, or will they be an extension of the regional offices?
Refer to response to question 97. 97, 63 Vendors from SAM (Pre Industry Day)
099 Will the FAA give the contractor the aeronautical information to load into to the contractor COTS product or can the contractor provide that airport survey data for a one complete solution to the FAA?
The FAA is the official source of published Aeronautical Information. We are open to hearing any suggestions or ideas you may have regarding non-published Aeronautical Information.
Vendors from SAM (Pre Industry Day)
100 Can the FAA provide more information regarding the estimated timeframe and planned acquisition timeline for each phase in the multi-phased challenge-based process outlined in slide 32?
Specifically:
1. When is the final SOO expected to be released?
2. When is the anticipated release date of the Request for Vendor Concept Paper addressing the SOO?
3. Following the submission of concept papers, when does the FAA plan to invite candidates for discussions on proposed solutions, including the sample problem and Government Furnished Information?
4. What is the expected timeline for the release of the Request for Prototype Proposal (RFPP), and when will the final award for solution development be made?
See Question 18 18 Vendors (Post Industry Day)
FINAL NOTAM and Aeronautical Information Roundtable.pdf
23 Proposed Challenge Based
Acquisition Approach
101 At which stage of the challenge process will the FAA allocate funding to support the initiative? Specifically, will the FAA provide funding for the prototype phase to facilitate vendors in developing a prototype?
See Question 18 18 Vendors (Post Industry Day)
FINAL NOTAM and Aeronautical Information Roundtable.pdf
23 Proposed Challenge Based
Acquisition Approach
102 We recommend that the FAA allows respondents flexibility in submitting responses for the Vendor Concept Paper in various formats, including, at a minimum, MS Word, MS PowerPoint, or other interactive interfaces.
Noted. Vendors (Post Industry Day)
FINAL NOTAM and Aeronautical Information Roundtable.pdf
23 Proposed Challenge Based
Acquisition Approach
103 Can the FAA provide details on the specific type of contractual agreement to be issued (e.g., Fixed-Price Contract, Cost- Reimbursement Contract, Time and Materials Contract) and are there any requirements expected, given the nature of the solution development?
See Question 18 18 Vendors (Post Industry Day)
FINAL NOTAM and Aeronautical Information Roundtable.pdf
32 Proposed Challenge Based
Acquisition Approach
104 FAA requests a storage approach that allows for up to 3 years of AI and NOTAM data immediately accessible by external systems and users for analysis or visualization. Can FAA provide an estimate of the size of the current data environment and potential data volumes over time?
The purpose of this requirement is to ensure that the solution meets the requirements of the Pilot's Bill of Rights. In 2022, the NOTAM system processed approximately 3.8 million NOTAMs. The actual amount of storage required will depend on the architecture used to support a completely digital solution. This will include considerations such as storing geospatial data, representing the data in AIXM, and transforming it into various textual formats to comply with NOTAM policy. (Will revise once we get some storage estimates from NAIMES)
Vendors (Post Industry Day)
NOTAM DRAFT
SOO
9 AI Data Management
105 There is a requirement that allows integration with Single Sign- On authentication solutions with support for protocols like Security Assertion Markup Language (SAML), OAuth, OpenID Connect etc. Is there a SSO solution in place today? Is there a data governance solution that FAA would like to leverage
The FAA's Identity Access Management (IAM) (MyAccess) system uses Okta to enable single sign-on. By supporting the aforementioned standards, the system can seamlessly integrate with any IAM solution implemented within the FAA.
While no specific data governance solution has been identified, the FAA employs Collibra within its EIM platform.
Vendors (Post Industry Day)
NOTAM DRAFT
SOO
9 User Administration
Question Source Document Page Reference Paragraph
106 There is a requirement that states, "Provides a graphical representation of AI and NOTAM data within the human interface." Can we interpret this to mean providing a graphical representation of data within a User Interface that can be accessed via screen? Does the FAA envision an interface for mobile devices as well?
The solution should consider the visualization of temporal geospatial data across various devices, ensuring accessibility on multiple platforms, including mobile devices.
Vendors (Post Industry Day)
NOTAM DRAFT
SOO
11 Distribution
107 Can the FAA provide additional details on the current AIM System (i.e., code, database type, cloud vs on prem, Technology Platforms, etc.)?
We provide some background on the current NOTAM system architecture in question 29. The specifics of the current hardware and software are less important compared to the modern concepts we are looking for.
29, 74, 91, 112, 113 Vendors (Post Industry Day)
FINAL NOTAM and Aeronautical Information Roundtable.pdf
16 FAA Current AIM Systems
Environment
108 1. Would FAA consider providing industry a NOTAM readers room containing relevant documentation for the FAA’s current NOTAM environment before FAA releases the updated SOO. We have identified the below information for potential inclusion in a NOTAM readers room:
a. Existing as-is technical infrastructure, tech stack, and baseline technical design and architecture documentation
| b. | Existing CONOPS |
| c. | Existing User Scenarios and business rules |
| d. | Current NOTAM data model |
| e. | Current interface (users and systems) design description (IDD) |
and Interface requirements specification (IRS), and data exchanged between NOTAM and these interfaces
| f. | Current set of test cases to verify NOTAM functionality/features |
| g. | Identity and Access Management (IAM) and Identify, Credential, |
and Access Management (ICAM) standard, services and requirements for the new NOTAM system
h. Current and future Integration and technical requirements/services for data management and data sharing
i. Current and future Integration and technical requirements/services for cybersecurity
| j. | Current list of approved software and lifespan of the licensing |
| k. | Current list of prioritized defects |
| l. | Current NOTAM user guide and workflow |
| m. | List of acceptable MVP requirements for the new system |
| n. | Service Level Agreement or KPI for the current system, MVP and |
the future system
| o. | List of prioritized future improvements and enhancements |
| p. | FAA data, cybersecurity and UX strategy that the new NOTAM |
system will have to comply with
The FAA will consider this recommendation and provide more information once a decision has been made.
109, 110 Vendors (Post Industry Day)
109 2. Would FAA consider providing industry an AIM readers room containing relevant documentation for the FAA’s current AIM environment before FAA releases the updated SOO.
a. How many tools or systems are in the current AIM environment?
b. See Q1 (a-p) for the list of AIM documentation for potential inclusion in an AIM readers room
See question 108. 108, 110 Vendors (Post Industry Day)
110 3. Would FAA consider allowing industry 45-60 days to review the materials in the NOTAM and AIM readers rooms prior to the release of the updated SOO?
See question 108. 108, 109 Vendors (Post Industry Day)
111 4. We understand that based on the NOTAM industry day the FAA anticipates allotting 30 days for industry to prepare concept papers following the release of the SOO. Would FAA consider allocating at least 45 calendar days for industry to prepare concept papers since FAA is permitting multiple concepts from the same team.
See Question 18 18 Vendors (Post Industry Day)
112 5. In the NOTAM environment, what specific hardware is considered end of life?
We provide some background on the current NOTAM system architecture in question 29. The specifics of the current hardware and software are less important compared to the modern concepts we are looking for.
29, 74, 91, 112, 113 Vendors (Post Industry Day)
Question Source Document Page Reference Paragraph
113 6. In the NOTAM environment, what specific software is considered end of life?
We provide some background on the current NOTAM system architecture in question 29. The specifics of the current hardware and software are less important compared to the modern concepts we are looking for.
29, 74, 91, 107, 112 Vendors (Post Industry Day)
114 7. What manual intervention is required on the current NOTAM and AIM systems?
There are several areas of manual intervention for non-digitally originated NOTAMs today, including review and edit by Flight Services and the US NOTAM Office.
Vendors (Post Industry Day)
115 Please provide clarification on the FAA's intent for the new NOTAM hosting & development environment. Will the FAA provide the hosting / development environment as GFE in time for the new program or will the Offeror bring 100% of the solution?
Refer to response for question 79 79, Vendors (Post Industry Day)
116 Is there a NAS plan to stand up a single consolidated data repository within the OpIP?
Refer to question 80 80 Vendors (Post Industry Day)
117 Please provide clarification and definition of the FAA's "contemporary service delivery model". What are the features and service outcomes the FAA is looking for in this model?
What are the Service Level Agreement (SLAs) the FAA is contemplating? What are the major business objectives?
Refer to question 81. 81 Vendors (Post Industry Day)
118 Please define the level of systems availability required for the new system.
Refer to question 82. 82 Vendors (Post Industry Day)
119 Is the modernization / replacement of existing legacy NOTAM systems involved in origination and distribution in scope of the potential procurement?
Please refer to question 83 83, Vendors (Post Industry Day)
120 Will the FAA NAS Security policies and orders apply to the new NOTAM system?
Refer to question 84. 84, Vendors (Post Industry Day)
121 The FAA should consider issuing an annual affordability profile / budget targets to ensure offerors bring innovative solutions that support the ongoing FAA budget constraints. This will focus offerors on technical solutions and help the FAA avoid race to the bottom pricing.
Noted. Vendors (Post Industry Day)
NOTAM & AI
Information
Industry Roundtable
31 Challenge Based Acquisition Approach
122 The FAA states a preference for "non-proprietary" solutions and "open-source". Can the FAA provide a definition of what "Proprietary means" to baseline the industry?
The goal is a vendor-neutral solution adhering to open standards, avoiding dependency on a specific vendor.
Vendors (Post Industry Day)
NOTAM & AI
Information
Industry Roundtable
28, 32 Implementation Approach
123 Does the FAA envision a solution that analyzes temporary and permanent AI to automatically purge lapsed termprary / NOTAM conditions and update permanent structures?
Maintaining an audit trail of changes is integral to Aeronautical Data Quality. The AIXM temporality model, encompassing permanent and temporary events, facilitates accurate representation of feature status at any given time. Adopting these, the AIXM temporality model ensures a comprehensive temporal record.
Vendors (Post Industry Day)
Slide 8
124 (Deferred at Round Table discussion but still a question) When in the procurement process will ICAO formats be adopted for NOTAMs (before or after the new system is developed and procured)?
Refer to response to question 27. 27, 39 Vendors (Post Industry Day)
Slide 10
125 The temporality model is exhaustively described, as you point out, in the AIXM standard. Is it a current or future objective of the FAA (in coordination with ICAO) to adapt new technology tools to manage temporality with time- and transaction- based services?
The goal is to adopt a globally harmonized AIXM model to encode aeronautical information and manage the various events the features go through in their lifecycle. If any other solutions or services are available, the FAA is open to considering them, and they can be proposed as part of the concept paper.
Vendors (Post Industry Day)
Slide 13
126 Other than expense/cost of licenses, what evaluation factors will apply to solutions that leverage open source and open standards vs. proprietary technologies?
See question 15. 15 Vendors (Post Industry Day)
Slide 15
127 Is commitment to a total solution operated as SaaS considered to have a risk of vendor lock-in?
We are open to hearing any suggestions or ideas you may have.
Vendors (Post Industry Day)
Slide 19
128 Given that the AIM support contract DTFAWA14C00049R is set to expire 10/2024, will there be a corresponding or coordinated procurement to achieve these AIM modernizations? Are any of them expected with the modernization of the ACS in AIM/M E-1 (apparently projected for release ~12/2023)?
See Question 18 18 Vendors (Post
Slide 21-22
Question Source Document Page Reference Paragraph
129 Integration goals are somewhat broad; for purposes of Concept Papers, can we please request that the "sample problems" mentioned on Slide 32 include the most important ones that will be evaluated and that you believe will demonstrate the extensibility of the solutions to accommodate?
See Question 18 18 Vendors (Post Industry Day)
Slide 26
130 For a Section B / pricing requirement, will you consider narrowing the solution type to a price-comparable model? Since SaaS, PaaS, and custom/on-prem solutions will have different cost components can you please describe how you might evaluate two or more solution types for price and cost?
See question 15. 15 Vendors (Post Industry Day)
Slide 29
131 For evaluation and selection from amongst the prototypes, can you please describe anything you have planned for evaluators of the solutions? Will the panel include people from other agencies/DoD, airlines, or other external Stakeholders?
See question 15. 15 Vendors (Post Industry Day)
Slide 32-33
132 Have you considered the prevailing Architecture Evolution Strategy (AES) tenets for the creation, deployment, and maintenance of the NOTAMs solution?
The FAA's Automation Evolution Strategy (AES) is a service-based architecture framework designed to realize an info-centric National Airspace System (NAS). Embracing AES tenets will establish a robust foundation for the integrated aeronautical information solution.
Vendors (Post Industry Day)
No slide reference
133 Is there any concern, rule, or limitations to proposing “AIM/NOTAMs as a Service” solutions?
No. We are open to hearing any suggestions or ideas you may have.
Vendors (Post
Questions
File details come from the government source that posted it. Updated .