2018-08-03 E-IDS AnswersToVendorQuestionsFromRFI_3.xlsx
XLSX spreadsheet 14 KB Posted
- Solicitation number
- 693KA7-18-R-00003
About this file
2018-08-03 E-IDS AnswersToVendorQuestionsFromRFI_3 (xlsx)
View the file
Other files
Show all 11
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
QuestionsAndAnswers
| # | Document | Location | Question from Industry - RFI#3 | FAA Response |
| 1 | Segment Interfaces | N/A | An E-IDS to WMSCR interface is listed. CSS-Wx Work Package 2 however is supposed to subsume the WMSCR system to at least some degree, possibly including distribution of PIREPs. Clarification may be needed for discerning between the interface capabilities of the two interfaces. | In Segment 1, Phase 2, E-IDS will submit PIREPs entered by Terminal controllers to WMSCR, using the WMSCR Publish PIREP Service, as defined in the Java Messaging Service Description Document (JMSDD) and the SSD. E-IDS will also receive a broader set of PIREPs from CSS-Wx, which is part of their Work Package (WP) 1 capability. |
In Segment 2 timeframe, which is expected to align with CSS-Wx WP2 timeframe, E-IDS will evolve to interface with CSS-Wx as needed to continue to submit and receive PIREPs. If CSS-Wx keeps the Publish PIREP Service intact when it subsumes WMSCR, E-IDS interface for PIREP submission may not be impacted. If CSS-Wx redefines the interface with which it receives PIREPs from other systems, PIREP submission part of E-IDS-CSS-Wx interface will have to change to conform to the new interface definition.
| 2 | Segment Interfaces | N/A | Does the FAA intend to provide detailed descriptions of the interfaces such as an interface requirements document prior to the release of the SIR? | Yes, these will be released in "Drop 2" of the Draft SIR. |
| 3 | Segment Interfaces | N/A | Table Entry "ACE-IDS" does not have a listed Capability Description | This is an artifact of pagination from page 1 to page 2. The left table cell contains "E-IDS to and from legacy IDSs including NIDS, IDS-4 and ACE-IDS", and the right table cell contains"Legacy Products". |
| 4 | Segment Interfaces | N/A | The NAS Cyber Management System (NCMS) provides several services to NAS systems which assist in the monitoring and archive of system cyber events. Does E-IDS require an interface to NCMS? | Yes, E-IDS will interface with NCMS as described in the SSD. |
| 5 | IESP and Hosted Subsystems | Section 1.1, para #2 | "The existing IESP footprint offers room for growth of currently fielded equipment." E-IDS could require significant capacity. Is a platform such as IESP prepared to be able to handle the load demands suggested in the E-IDS documentation? | The E-IDS supportability assessment was performed using VM requirements (CPU, RAM, Storage) provided by E-IDS PO. If the 'as built' resource requirements are higher, then IESP may need to be augmented by the E-IDS PO to provide the additional capacity. |
| 6 | IESP and Hosted Subsystems | Section 1.1, para #4 | A link is provided to workflows; however, the link does not appear to be accessible from the internet. Is the information located at the link significant to understanding of the IESP interface? | The link in the latest version of the draft IRD which was provided to the E-IDS Program Office should be accessible from the Internet, but may require an FAA domain account. The text is correct, but the associated URL got truncated during conversion to PDF. |
| 7 | IESP and Hosted Subsystems | Section 1.1, para #7 | Paragraph states that IESP hosted systems enter a memorandum of understanding regarding support levels that are provided by the first level support. Can the FAA provide an example of a MOA for IESP and/or the range of the agreed upon support subjects, and sample associated trainings for the support subjects. | There is no reference to MOAs in the latest draft version of this document that was provided to the E-IDS Program Office. |
| 8 | IESP and Hosted Subsystems | Section 3.4, para #1 | Section describes services available to IESP hosted systems, including CPU, Memory and Storage. In a virtualized environment, the available CPUs and memory are only as good as the implementing physical hardware. If IESP has been in operation for more than a year, the hardware may not be as quick as is necessary for a new system such as E-IDS. Will the FAA make available the physical hardware specification for the virtualized environments, if the FAA requires the contractors to use an existing virtualized environment such as IESP? | CPU & Memory: |
Each IESP Node has 8 HPE ProLiant BL460c Gen9 Server Blades, each with the following configuration:
2 x HPE BL460c Gen9 Intel Xeon E5-2680v4 (2.4GHz/14-core/35MB/120W) Processor 8 x HPE 64GB Quad Rank x4 DDR4-2400 CAS-17-17-17 Load Reduced Memory
Storage:
3Par StoreServ 7200C 2-Node Controllers with multiple M6710 Small Form Factor SAS drive enclosures per site.
| 9 | IESP and Hosted Subsystems | Section 3.4, para #1 | Section describes services available to IESP hosted systems including Remote access and Bandwidth. The hosted systems are required to provide IESP bandwidth requirements. Presumably this is so that IESP can coordinate purchase of additional bandwidth from FTI. A) Does bandwidth costs directly follow that of FTI, and B) Does the hosted system have options to have elastic bandwidth caps to meet spikes, or unusual short term demand? | Any required bandwidth upspeed is ordered by the hosted system Program Office using standard FTI processes. B - FTI does not support elastic bandwidth allocations, but does allow for bursting of %20 percent over the static bandwidth allocation to accommodate traffic spikes. |
| 10 | IESP and Hosted Subsystems | Section 3.4.6, para #1 | The paragraphs describe Yellow dog Update Modified (YUM) tool that is present in the Red Hat Enterprise Linux (and variants). The paragraph describes that each node is supplied with a YUMFTP VM. Does this YUMFTP VM have a predefined repository for the OS? If so, what OS and version? Is this OS maintained by IESP (e.g., security, patch and maintenance upgrades, or is the hosted system responsible for maintaining the packages? What is the size limitation of the VM? A complex hosted system can have packages that are multi-gigabytes in size and could exceed the size of a small VM. Does any other software run within the YUMFTP VM, or is it a simplified OS for support of updates only? | This was a typo that's being corrected in the final version of the IRD. IESP does not provide patching services. The hosted system will have to provision VMs to support this. |
| 11 | IESP and Hosted Subsystems | Section 3.7, para #1 | Operational IESPs are located at both ATL, and SLC NEMCs and backup each other. Do the IESPs follow a Hot-Hot strategy, or a hot-cold standby strategy? How do the IESPs maintain synchronization, or is it up to the hosted systems to perform synchronization? | IESP infrastructure in ATL and SLC is hot - hot. Application architecture and synchronization/replication is determined and implemented by the hosted system. |
| 12 | IESP and Monitored Subsystems | Section 3.2.1, para #1 | IESP monitors systems using HP Open View (HPOV). HPOV is a licensed product. How are license costs handled? Do the hosted Systems cover the costs of licenses, or is included with any costs associated with IESP Virtual Machines? | HPOV license costs to cover hosted system VMs are funded by the hosted system program. |
| 13 | IESP and Monitored Subsystems | Section 3.2.1.2, para #2 | Paragraph states that the NNMI licenses are based on device count. Are these licenses provided by IESP? | The IESP team does not provide licenses for these products. These will be provided either by the Prime Contractor or the FAA Program Office after the specific E-IDS software design has been determined. |
| 14 | IESP and Monitored Subsystems | Section 3.2.1.2, para #2 | Paragraph states that the NNMI events are stored for a minimum of 30 days, is there a maximum time for storage of events? | There is just a limit on how many events the DB can store, the limit is 100K. A monthly routine is run on NNMi to purge events. Informational and Normal events are retained for 3 months, while Warning, Minor, Major, and critical are kept for 6 months. |
| 15 | IESP and Monitored Subsystems | Section 3.2.1.2, para #2 | NNMI runs on a RHEL server. If NNMI is desired to be used, does a hosted system require an additional VM to run NNMI, or is NNMI a service provided by IESP? | Hosted systems are required to integrate into the existing IESP NNMi implementation. Integration is through ICMP, SNMP, and SNMP Trap. |
| 16 | IESP and Monitored Subsystems | General Question | General Question: Does the IESP - Monitored system require use of an IESP hosted system, or can it monitor systems which are not a part of the IESP infrastructure (e.g., bring your own hardware). | The IESP HPOV implementation can monitor hosted or non-hosted system components. |
| 17 | Capability Demo | General Question | Does the FAA envision conducting OCDs prior to the SIR release to inform its content, or as part of the final SIR evaluation? | Please refer to Section L of the Draft SIR. |
| 17 | Capability Demo | General Question | In terms of E-IDS Program objectives, what is the framework and scope of the OCD? | Please refer to Section L of the Draft SIR. |
| 17 | Capability Demo | General Question | Will every vendor be required to follow structured OCD guidelines (e.g., Phase 1 & 2 Functionality, Infrastructure, and Services, etc.), or will the OCDs be unbounded, leaving it up to the vendor to rack up source selection points by way of allocating demonstrated capabilities to Segment 1 and 2 E-IDS requirements? | Please refer to Section L of the Draft SIR. |
File details come from the government source that posted it.