SOURCES SOUGHT
58 -- Enterprise Terminal Facilities Request for Information (RFI)
- Notice Date
- 4/8/2008
- Notice Type
- Sources Sought
- NAICS
- 517410
— Satellite Telecommunications
- Contracting Office
- US Army C-E LCMC Acquisition Center - DAAB07, ATTN: AMSEL-AC, Building 1208, Fort Monmouth, NJ 07703-5008
- ZIP Code
- 07703-5008
- Solicitation Number
- W15P7T-08-X-XXXX
- Response Due
- 5/8/2008
- Archive Date
- 7/7/2008
- Point of Contact
- Vernay Salas, 732-532-1257
- Description
- REQUEST FOR INFORMATION (RFI) SOURCES SOUGHT FOR INTEGRATED TERMINAL ELEMENT MANAGEMENT SYSTEM (EMS) 1.Purpose Project Manager, Defense Communications and Army Transmission Systems (PM DCATS), Fort Monmouth, NJ, is seeking information for a solution that would enable the integration of all subsystems at Enterprise Terminal Facilities (ETF) under a single management platform leveraging commercial Element Management System (EMS) technologies. PM DCATS provides worldwide support for theJoint Warfighters by providing dedicated strategic satellite ground components and long haul terrestrial microwave communication systems, technical control facilities, command center upgrades, and deployed forces infrastructure. Large and small businesses that are experienced in providing turn-key satellite systems and associated support services for the satellite terminals specified below are encouraged to respond to this RFI. As illustrated in Figure 1, fixed site, DoD ETFs are composed of many subsystems collocated in a single site. Major components include the antenna, antenna control and tracking, transmit and receive subsystems, modems, switching, multiplexing and cryptographic baseband equipment, timing reference, and power. The current approach to terminal management is fragmented between RF and baseband management, and is designed around circuit based requirements. ETFs currently employ an Integrated Control Console (ICC) to manage baseband subsystems along with a Control, Monitor and Alarm (CMA) system to manage terminal RF components. As many legacy subsystems are replaced with new systems via technology refresh cycles, PM DCATS is interested in commercial EMS solutions that can be leveraged to create an integrated management capabilitythat can replace the ICC and interface with the CMA. As DoD networks migrate to an Everything-over-IP architecture, the focus of network management shifts from circuits to networks. Along with this shift, comes the ability to monitor traffic and correlate network behavior with the performance of supporting physical layer media. For satellite communications, this provides tremendous insight into the utilization of limited satellite resources and the ability to troubleshoot and optimize performance onan end-end basis for the IP over satellite network. The integrated solution described in this RFI is intended to support the management of all subsystems at the ETF to meet network-wide policies, Service Level Agreements (SLA) and associated performance requirements for user traffic transiting the terminal facility It is necessary that the Terminal EMS implementation be cost effective, leveraging COTS products, and scalable so that the cost and capability scale with the size of terminal it is supportingand number of elements it is managing per instantiation. For DoD installations, the number of elements to be managed can vary from hundreds to thousands of elements. Terminal EMS should also be scalable to support multiple RF terminals at a single physical location. 2.High Level Requirements for the Terminal EMS capability: Functional Requirements The terminal EMS is needed to consolidate the management of many diverse components and subsystems into a single platform fulfilling the role of Element Management within the Telecommunications Management Network (TMN) model. According to the TMN model, the Element Management Layer (EML) includes functions for the handling of individual network elements. At each layer in the TMN, the management system provides Fault, Configuration, Accounting, Performance, and Security (FCAPS) functions. For the Terminal EMS, appropriate FCAPS capabilities would be provided as they relate to Enterprise Terminal subsystems. This includes alarm management, handling of information, backup, logging, and maintenance of hardware. The Terminal EMS must manage multiple pieces of equipment from different vendors, and across different physical interfaces including Ethernet and serial. Northbound interfaces will support higher level and centralized management functions including Network Management (e.g. at the TNC as illustrated in Fig 1) and centralized Satellite resourcemanagement (e.g. at the WSOMS as illustrated in Fig 1). Through the northbound interface, the Terminal EMS will interact with the Network Management Layer (NML) systems to include performance management, provisioning, policy based management, inventory, configuration and logistics, to name a few.. The information flows both ways on the northbound interface, over which the terminal EMS sends performance and status data, and receives policies and configuration data, as an example. It is anticipated that this bi-directional northbound interface could potentially support remote operation of lights-out facilities. The Terminal EMS will function as part of a larger telecommunications network architecture. Within the telecommunications industry, standards are being developed to create an open architecture for integration of multiple EMS and NMS systems. The New Generation Operations Systems & Software (NGOSS) project within the TM Forum is a central part of this standardization effort. In consideringsolutions for the terminal EMS, NGOSS and related standards should be used to the greatest extent possible. This is expected to include the use of service oriented architectures. Key features and capabilities: a.Integrated User Interface. TheTerminal EMS solution must integrate all subsystem components to provide configuration and monitoring functionality from a single user terminal accessible locally as well as remotely. Secure out of band connectivity must be provided for remote operations. The system will be operated by Government or contractor personnel and will include application software to provide a graphical user interface with conventional pull-down menus to enable system configuration, operation, troubleshooting, and real time system status. Appropriate protocols should be supported for local loading or retrieval of software for equipment being managed. b.Views: The user interface must provide a graphical representation of the satellite terminal. The equipment view must displaya physical representation of components and subsystems. The functional view must display a schematic representation. The views must be customizable to user requirements to provide a User Defined Operating Picture (UDOP). c.Key Features. Utilize an open standards approach to interface (e.g. XML) with all legacy and future terminal subsystems is a critical requirement. Providing a web-services interface is critical to ensure network centric operation. Support FCAPS functionality and TMN hierarchy. The solution must support policy based network management as a policy enforcement point for subsystem elements within the enterprise terminal. d.Compliance. The solution should support Service Oriented Architecture (SOA) concepts and be scalable to meet future user demand. The solution should be NGOSS compliant. The solution must meet GIG initiatives for network centric transformation and management elements and networks. e.Security. The System will need to meet all applicable network certifications, security policies, and accreditations, for example: DoD IA Certification and Accreditation Process (DIACAP), DODI 8510.01/ DODI 8500.2 and AR 25-2 Information Assurance (IA). User authentication must be provided. Multiple users with different privilege levels must be supported. Authentication options can include: multi-factor authentication (ie biometrics, tokens, passwords), repeated authentication for critical tasks, several authentications in a serial manner, Role based access control authentication and user authentication as separate steps, or varying degrees of confidence in the authentication depending on the criticality of actions performed. The initial vision of Terminal EMS is for it to be a black system utilizing a CDS to interface with northbound systems with the possibility of migrating to support a full red/black separation capability. PM DCATS is particularly interested in information regarding an implementation that provides a cross domain solution to support information flow between classified and unclassified information systems. It is recognized that the use of a CDS may increase the security requirements for systems connected on either end. f.Alarm collection, reporting and management: Alarms must be collected from each component of the satellite terminal and must be logged, and reported with the appropriate priority. Alarm filtering and correlation must also be provided to support fault isolation and root cause analysis. g.Provisioning and pre-provisioning: The Terminal EMS must configure and provision equipment as required. Configuration information must be locally stored so operation is restored if a piece of equipment is replaced without connection to north bound management systems. Pre-provisioning should allow equipment to be logically added and configured before the equipment is physically installed. Once the equipment is installed and connected to the EMS, it is configured and provisioned automatically through the network element manager. h.Performance Monitoring and Reporting: At a minimum, performance monitoring and reporting will be provided for weather, RF noise margins, power levels, data rates, capacity, and dropped packets.. A key performance metric will be transport of packets in accordance with Quality of Service (QoS) markings. DOD uses DiffServ Code Points to mark traffic to ensure that high priority and/or delay sensitive packets are treated appropriately. The solution should be capable of supporting enforcement of user SLAs. A full performance monitoring and reporting capability must be provided for all components. The Terminal EMS solution must be able to ping various systems to determine active component configurations, including plug in modules, to manage configuration and inventory. i.Diagnostics and testing: Diagnostics and testing of individual components and systems must be managed. Loop back and automated measurements must be preformed to support system turn up or fault isolation. j.Database Backup and restore: The Terminal EMS solution data base shall contain a complete configuration and state of the satellite terminal. The data base must be robust, secure and able to be backed up and restored locally and remotely. Depending on security requirements, it may be necessary to separate system software from audit logs in data backups. k.Software download and management: The solution must be able to store, and download software to configure and upgrade system components. Multiple versions of software must be managed. l.Northbound interface: Provide a standards based interface for northbound management systems (e.g. SOA, XML, SNMP). Pass through connection is required between selected subsystems directly to a northbound system. The Northbound interface must be secure and protected in both directions via firewall and protected from viruses. The Northbound interface should be capable of providing all data relevant to ETF operations, in accordance with information sharing policies for DoD network-centric operations. m.Event logging: Logs and traces must be stored for retrieval to resolve faults and errors. n.MIB support: Equipment MIBs shall be supported and MIB proxy service provided for equipment without a native MIB. o.Extensibility and Scalability: Modularity and architecture must support the addition of new equipment and subsystems in the future with minimum cost and development effort. The solution must cost effectively support small sites and scale to support larger facilities. Support for NGOSS compliant interfaces is desired to ensure the interoperability in a multi-vendor OSS environment. 3.Future Desired Upgrades: a.Unattended Operation. The web services enabled single user interface shall support unattended operation with the intent to support full operations for a lights-out facility. In this scenario, there is no local staff to operate the terminal. b.Facility and Environmental Management: The facility may be unattended and require environmental monitoring and control of temperature and antenna deicing. 4.Services The applicable services to be provided in conjunction with the Integrated Management of Enterprise Terminal Subsystems solution include: system integration and administrative support; operation; maintenance; verification and acceptance testing; Integrated Logistics Support; telecommunications security; engineering; Configuration Management; site surveys; system and facility installation; facilities, terminals, and support equipment. 5.Information Requested Interested companies should furnish the following information: a.Name, address, and Contractor and Government Entity (CAGE) code of your company. b.Point of Contact (Name address, phone number, and e-mail). c.Identify current products your company offers which most closely match the capabilities specified above. d.Available product brochures, specification sheets, photographs, illustration and technical descriptions that describe your companys current products that most closely match these capabilities. e.An optional White Paper (no more than 20 pages in length) describing how your companys products and technical expertise could produce and deliver such a capability. f.An identification of your companys past and current customers to which your company provided similar products and services, including a customer/company name and point of contact, phone number, and address/e-mail where they can be contacted. g.Indicate if your company would be willing to conduct a one or two day demonstration of your products technical capabilities. h.Pricing structure for small, medium and large site implementations, including licensing, maintenance, upgrades, and integration. i.Provide input relative to the timeframe needed for customizing your product to meet stated Terminal EMS capabilities. 6.Disclaimer This RFI is for informational purposes only and does not obligate the Government to implement or acquire any EMS capability, equipment or service addressed in any information received, or change any acquisition strategy. This RFI does not obligate the Government for cost reimbursement for preparation of response. 7.Points of Contact Please furnish the above requested information not later than 10 April 2008. Submit your response in Adobe Acrobat.pdf or Microsoft Office files via the CECOM Interactive Business Opportunities Page (IBOP) at the following address: https://www.abop.monmouth.mil. General administrative questions should be directed to Jay Hicks via e-mail at Jay.Hicks@us.army.mil or by phone at (732) 532-2162 or Dave Khalil viae-mail at Dahesh.Khalil@us.army.mil or by phone at (732) 532-6603. Any party interested in obtaining the drawing (figure 1) should contact Vernay Salas, either eletronically at Vernay.Salas@us.army.mil.or telephonically at (732)532-2193..
- Web Link
-
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=6cfa555dd952ffd827af9a9ecf96e91b&tab=core&_cview=1)
- Place of Performance
- Address: US Army C-E LCMC Acquisition Center - DAAB07 ATTN: AMSEL-AC, Building 1208 Fort Monmouth NJ
- Zip Code: 07703-5008
- Zip Code: 07703-5008
- Record
- SN01549999-W 20080410/080408223316-6cfa555dd952ffd827af9a9ecf96e91b (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |