Replacement of NOAA OMAO's Shipboard Maintenance/Management Program

1. OverviewThe National Oceanic and Atmospheric Administration (NOAA) Office of Marine and Aviation Operations (OMAO) operates a fleet of diesel engine propelled and diesel electric propelled research vessels. Currently, there are 16 vessels in this fleet. The vessels support research and mapping for the National Marine Fisheries Service, National Ocean Service, Office of Atmospheric Research and the National Weather Service, as well as provide support to other Federal agencies. These research missions are time sensitive where the data must be collected at specific times during the sailing season to be meaningful. Properly scheduled maintenance is essential to ensuring that NOAA's vessels are operationally ready during the mission sailing season and helps to minimize the number of lost mission days. Effective Maintenance Management and Inventory and Logistics Management programs are central to NOAA's goal of maintaining mission ready vessels. The ships operate mainly in waters of the

US and its territories; however, routine and long term missions in foreign waters are not unheard of. Any application derived from this Request for Information (RFI) must be able to operate in a low bandwidth, high latency, and intermittent connectivity environments.2. DescriptionThe objective of this RFI is to obtain information from vendors who can provide an American Bureau of Shipbuilding (ABS)-approved Commercial Off-the-Shelf (COTS) replacement to NOAA‘s current Shipboard Maintenance System and Inventory and Logistics Management System. The proposed system should include, but is not limited to, Preventative Maintenance, Condition Monitoring, Maintenance History, Repair History, Inventory and Logistics Management, Afloat Document Management, and ad hoc and automated report generation. The maintenance management program shall be such that NOAA shall have administrative rights and training to make changes to the databases (add and delete items, change frequencies, set administrative controls over other NOAA users, etc). OMAO will need services to facilitate the conversion of the data stored in the current databases and migration of data from the current legacy system "SAMM" (Shipboard Automated Maintenance Management System) for each of NOAA's 16 ships to the new system.NOAA intends to fund a yearly software license, technical support, and software maintenance; upgrades shall be provided by the contractor at no additional cost to the Government. The information collected as part of this effort may help define the OMAO requirements for these services and as such we invite qualified and interested parties to submit written responses to this RFI by July 17, 2018 - 3:00 P.M. Eastern time, for our review. All responses shall be limited to 20 pages in length and should present information that will help further our understanding of the possible alternatives (i.e., hosted, cloud, etc.), strengths, associated risks, and likely time frames/potential savings of one solution over the other, etc., to migrate. In addition to the 20 pages, responders are welcome to submit additional marketing materials, as deemed necessary. Submitted responses will not be returned to the responding party. At this time, OMAO will not invite responders to present their response or any other material in support of this market research. Inquiries regarding this notice shall be submitted via email to Michelle.Blake@noaa.gov. Responders are requested to submit their inquiries, if any, in sufficient time for consideration prior to the response due date. Firms providing responses to this RFI are requested to submit responses via email to: michelle.blake@noaa.gov.This RFI solicits information solely for market research purposes. As such, it does not constitute a Request for Proposal (RFP) or a commitment to issue an RFP by OMAO; OMAO is not accepting offers at this time. The information provided by the responding party is not considered as an offer by the Government. This RFI does not commit OMAO or any other DOC agency to contract for any supply or service. Additionally, OMAO is not responsible for any administrative costs incurred by any responding party in response to this RFI. Proprietary information is not being solicited as part of this RFI.3. Information RequestedPlease consider the NOAA's OMAO requirements in Section 4 of this RFI framed within the high-level context. As part of the market research, the Government is interested in understanding any feedback the industry may have on the following topics so that this information might be utilized as part of developing a potential acquisition strategy and RFP.3.1 What is the most feasible solution for the NOAA prospective needs detailed in Section 4, and within the context of the OMAO background information? Please consider IT infrastructure security measures that are compatible with Department of Commerce and NOAA IT requirements (e.g., FedRamp certification), scaling, and overall interoperability.3.2 What are the major risks and collateral issues associated with this type of migration and how might they be mitigated?3.3 To increase the quality of the solution, what information/criteria should be requested in an eventual solicitation and why?3.4 What lessons learned/best practices from other similar efforts performed for federal agencies could be applied to this effort? Explain how they drive value to the agency and if they result in cost savings, or other factors such as improved security, capacity on demand, etc. Provided examples shall include agency and contact information.3.5 Please provide a high-level schedule to successfully affect the migration effort likely required for this initiative. Details of schedule should include:3.5.1 Data conversion of 16 ships3.5.2 Data Migration from SAMM to new Program3.5.3 Shore-based and shipboard based software and IT hardware procurement and installation3.5.4 Training of NOAA program users (shipboard)3.5.5 Training of NOAA program users (shore-based/administrators)3.6 What information would be needed to efficiently describe and price the appropriate solution in an RFP?3.7 Please provide a copy of your typical Service Level Agreement (SLA) including standard performance metrics and targets. The SLA example is not included in page limit.3.8 Please provide information on new/innovative service offerings and your ability to stand-up/deliver these services within the context of your recommended solution offering. The Government is interested in understanding the value of these IT resources, operational agility, data analytics, enabled by your offering.OMAO will use information from this market research to help it assess viable and innovative solutions.4. OMAO Prospective Needs4.1 The program at a minimum must include the following modules and support modular billing and design:· Planned/Preventative Maintenance· Equipment History and Repair· Condition Monitoring· Afloat Document Management· Hull and Deck Condition Monitoring· Inventory and Logistics Management· Trending and Reports (On Demand/ Near Real-time)· Work RequestsIn addition, the system must be capable of generating ship maintenance plans and condition monitoring baselines in accordance with ABS's Guide for Survey Based on Preventive Maintenance Techniques and complies with International Safety Management (ISM) Code sections 10.3 and 10.4.4.2 Disaster Recovery (DR). As part of its hosting/cloud related solution, OMAO needs a comprehensive DR solution at the infrastructure and systems/applications/data level. OMAO is interested in approaches that address equivalent services that could be provided for short-term or long-term disaster situations (loss of connectivity or data loss) when the primary servers are not available.4.3. IT Security. Being a Federal agency, DOC NOAA OMAO is subject to the National Institute of Standards and Technology (NIST) guidance including, but not limited to, NIST SP 800-53 (rev4). The system must support Role Based Access Control (RBAC); provide details of account access controls in your response to the RFI.Entities responding to this RFI are advised that any final solution that may result will be required to meet the requirements of the following at the moderate level at a minimum:· High or Moderate Risk Contracts -- 48 CFR Ch. 13 1352.237-70· Low Risk Contracts - 48 CFR Ch. 13 1352.237.71· National Security Contracts - 48 CFR Ch. 13 1352.237.72· Foreign National Visitor and Guest Access to Departmental Resource· FAR Subpart 4.19- Basic Safeguarding of Covered Contractor InformationSystems· FAR Clause 52.204-21· FAR Subpart 24.1-Protection of Individual Privacy· FAR Clause 52.224-1 "Privacy Act Notification"· FAR Clause 52.224-2 "Privacy Act"· FAR 39.101-Acquisition of Information Technology-General-Policy· FAR 39.105-Acquisition of Information Technology-General-Privacy· FAR 39.106- Acquisition of Information Technology-General-Contract Clause· FAR Clause 52.239-1 "Privacy or Security Safeguards"· FAR Subpart 27.4--Rights in Data and Copyrights· NIST 800-53 Rev 4 --Controls for moderate systems. DOC IT Security Manual. NOAA IT Security Manual. NOAA IT Security Policy4.3.1 OMAO interested in how sources would address security concerns during all phases of migration and consolidation, including an approach to network firewalls, network intrusion detection, system monitoring, operating system vulnerability scanning, enterprise compliance scanning, encrypting data at rest and in motion, and other forms of security measures to ensure information security.4.4. Migration Services and TimeframeOMAO would need migration services including: inventory collection; planning and designing the migration; conducting the migration; and processes and tools used to ensure minimum downtime and lowest risk. Training of future program users should also be included in this timeline. OMAO has drafted a migration timeline of 1 year for investment planning purposes but is interested in other approaches to a migration schedule. Basic migration needs to include the following:4.4.1 Collocation of legacy SAMM shore side physical servers if necessary (OMAO retains ownership/custody of their physical servers).4.4.2 Alternatives to maintain or enhance the current end user experience (e.g., no performance degradation onboard the vessels due to potential latency; bandwidth limitations at sea; no disruption to business processes; etc.). Respondents are encouraged to provide additional information as appropriate.5. Disclaimer and Important NotesAny organization responding to this notice should ensure that its response is complete and sufficiently detailed to allow the Government to evaluate the response provided in its totality. Respondents are advised that the Government has no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. After a review of the responses received, a pre-solicitation synopsis and solicitation may be published.6. ConfidentialityResponders shall not include proprietary, classified, confidential, or business sensitive information in their submission in response to this RFI. The Government reserves the right to use any non-proprietary technical information in any resultant solicitation(s).Contact Information: MICHELLE M BLAKE, Phone 757-441-3870, Email MICHELLE.BLAKE@NOAA.GOV Office Address :Norfolk Federal Building, 200 Granby Street Norfolk VA 23510 Location: Eastern Acquisition Division - Norfolk Set Aside: N/A