SBIS RFI-2_FAA Responses to Industry Questions_2021-08-10.pdf

Surveillance Broadcast and Information Services (SBIS) Request for Information (RFI)

Questions and Responses

Question from Industry Government Response

1 Is the FAA looking for any level of surveillance integration/interoperability among Oceanic, Remote and

CONUS Airspaces?

Please clarify whether each airspace type is to be considered a separate "surveillance service”.

If there are different and/or separate surveillance solution sources or services for Oceanic, Remote and CONUS areas, it is anticipated that there will be integration/interoperability through the surveillance processing and networking functionality.

2 Does the FAA have any insight yet as to the categories or specifics of the NIST Security Controls required for

FISMA High?

The SBIS tailored controls are planned for inclusion in the

SBIS draft SIR.

3 Does the FAA see the FISMA High requirements as applying to all of SBIS, including the underlying networks?

FISMA High requirements will apply to the SBIS solution and the underlying networks, if they are within the defined security boundary.

4 Does the FAA have a ConOps for the Security Operations of SBIS, including collaboration with FAA Information

Security organizations?

The SBIS ConOps is in development. The FAA is planning to have the SBIS ConOps available prior to the release of the SBIS draft SIR and security requirements included in the SBIS draft SIR.

5 What level of transparency is the FAA looking for with respect to monitoring of SBIS, including the network, from FAA facilities (e.g., NOCC)?

The FAA is looking for full transparency at the network level.

6 What are the high-level Program Objectives and Priorities

(e.g., J-0)?

The SBIS program objectives are to continue to provide

SBS services, provide enhancements and explore innovation areas described in the RFI Attachment 7 and 9.

We are looking for input from industry in innovations areas to help refine the priorities.

7 How important is global interoperability of ADS-B services to the FAA?

Global interoperability is important. The FAA has implemented both 1090MHz and 978MHz link technology solutions. SBIS solutions will need to accommodate global MOPS standards

8 Could the FAA please clarify if a satellite-based SBIS infrastructure is limited to only the oceanic and remote airspaces? Could the existing SBIS infrastructure be replaced by one that is satellite-based?

It is possible for other SBIS airspaces to be satellite based if the satellite-based technology meets (on its own or in conjunction with other technology), the SBIS requirements. Proposed technology must meet all functional and performance requirements.

9 Has the SBIS program entered the Concepts and

Requirements Definition (CRD) Phase of the AMS, or is it still pre-CRD?

The FAA is in the Concepts and Requirements Definition

(CRD) Phase of the AMS for the SBIS acquisition.

10 The SBIS RFI-2 is very broad in its potential scope, including NAS-wide capabilities to provide/augment NAS timing sources and augment NAS navigation systems. To help us best respond, can you tell us if this represents a change to the NAS Enterprise Architecture? If so, is it possible to obtain the latest versions of the updated portions of the NAS-EA?

SBIS does not represent a change in the NAS architecture at this point. The FAA is investigating future capabilities as part of the CRD phase of the AMS.

11 The SBIS RFI-2 asks for input on the potential relationship between SBIS and FENS and states that

“…FENS provides a means to satisfy some of the data communications needs for the SBIS program.” Can you provide us any insight into the program’s thinking regarding what data communications may not be satisfied by FENS, given the broad scope of FENS requirements?

The FAA provided a notional architecture of how FENS might satisfy some of the communication needs of SBIS during the Industry Day Event on July 28th. Vendors are encouraged to provide feedback on how FENS might be used to satisfy the communication needs of the SBIS program.

12 Recommend removing ROM until service acquisition approach, construct, and requirements are refined to allow for better financial fidelity. Initial ROM efforts have too great fluidity given changing parameters, assumptions, and requirements.

The FAA has requested ROM cost estimates to inform the

SBIS Investment Analysis Readiness Decision which is an initial stage in the acquisition process while requirements are being solidified. Industry has been provided templates and can tailor as needed based on the level of detail available for the submittal.

13 One constraint listed in Appendix 10 is Automation

Integration. Could the FAA provide a conceptual timeline for the implementation of automation system modifications to ingest a dual surveillance broadcast feed if needed to enable SBS to SBIS transition?

The only changes envisioned would be for data ingestion of the additional feeds and adaptation for Service Volume monitoring. This would need to occur soon after service acceptance testing.

14 Item f identifies intent for reduction/elimination of TIS-B services. What is the date for TIS-B sunset being contemplated by the FAA?

Sunset of TIB-B is dependent on equipage rates and radar divestiture. The extent of reduction and/or elimination is not known at this time.

15 When is the FAA targeting the release of a draft SBIS

ConOps?

The SBIS ConOps is in development. The FAA is planning to have the SBIS ConOps available prior to the release of the SBIS draft SIR.

16 Could the FAA define and/or provide examples for

“critical system components” in the context of SBIS scope? Further, could the FAA clarify whether the intent of the statement “diverse set of suppliers” is to indicate multiple suppliers for each critical component?

The FAA does not have examples of critical system components at this time. In general, vendors must ensure the integrity of the SBIS supply chain such that all services, equipment, components and other supplies used to satisfy contract requirements are available when needed.

17 Could the FAA clarify the intended scope of enhancements in this area, above and beyond the requirements implemented in SBS?

The FAA expects to improve contingency and disaster planning and recovery by making data available to multiple Centers/TRACONs for transfer of ATC services during specific events and/or emergency situations.

18 What is the envisioned ASTERIX interface for the remote tower displays for surveillance ingest?

It is envisioned to be an ASTERIX CAT 062 format.

19 For remote airspace, is the FAA’s intent to leverage the same functional and performance requirements as defined for oceanic airspace (based on its title, the RFI

Attachment 9 covers draft Oceanic Requirements only)?

Yes. For remote airspace, it can be assumed the requirements defined in Attachment 9 are applicable.

20 Does FAA’s interest in potential support for UAT apply to both remote airspace and oceanic airspace?

Vendors are encouraged to provide feedback on the applicability of UAT for both oceanic and remote environments.

21 Could the FAA clarify (and address in the SBIS ConOps

AS-IS operations section) the current surveillance

Current surveillance processing and distribution capabilities not within current SBS scope but processing and distribution capabilities not within current

SBS scope but contemplated as being within the scope of

SPaN enhancements (e.g. ARTCC radar distribution, RDA and/or SDP functionality within automation systems, etc.)?

contemplated as being within the scope of SPaN enhancements include:

- Fused track data delivery to automation

- Support for additional surveillance services, for example for UAS/UTM and/or commercial space operators

- Remote towers

- Radar sensor backfeeds (cooperative data back to a PSR only)

22 There is overlap between the list in the Future SBIS

Enabled Applications section and the enhancements/innovations covered previously in the document

The list provided in the Future SBIS Enabled Applications section describes potential applications that might be enabled by the enhancements and innovations described in previous section of Attachment 7.

23 The main RFI document (Section IV Attachments List) lists Attachment 9 as being the Oceanic/Remote Service

Specification, but actual document title is Oceanic

Requirements. Is FAA’s intent to expand the scope of this document by adding requirements for remote airspace, or to have same requirements apply to both oceanic and remote airspace?

For remote airspace, it can be assumed the requirements defined in Attachment 9 are applicable to remote airspace.

24 ASTERIX CAT 048 and CAT 062 support is not included as one of the Oceanic requirements. Could FAA verify that this is not an oversight?

ASTERIX CAT 048 is not an Oceanic requirement. At a minimum, CAT 033 would be the primary data format for the Oceanic environment. The SBIS draft SIR will include, as appropriate, the required message sets for the

Oceanic requirements.

25 Could the FAA clarify whether the availability requirements specified cover the service path from aircraft antenna to FAA SDP where the reports are delivered?

The service provider will be required to meet the performance requirements for minimum equipped aircraft in all areas of the Service Volume.

26 For manned sites, are we able to ship equipment destined for implementation to the location?

Yes, for equipment destined for implementation at FAA facilities that are staffed, vendors will be able to ship to the location if necessary.

27 Does the FAA expect to handle inside wire work or will they expect the vendor to handle that?

Responsibility for inside wire work will be facility dependent. Vendors should assume FAA will conduct inside wire work at FAA locations.

28 Do install techs need special access or credentials to enter locations?

Installation technicians will be required to have an FAA escort when working in FAA facilities and/or credentialed with appropriate FAA badge.