Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF JUNE 26, 2014 FBO #4597
SOURCES SOUGHT

70 -- RFI OMAO Fleet Information System

Notice Date
6/24/2014
 
Notice Type
Sources Sought
 
NAICS
511210 — Software Publishers
 
Contracting Office
Department of Commerce, National Oceanic and Atmospheric Administration (NOAA), Western Acquisition Division-Boulder, 325 Broadway - MC3, Boulder, Colorado, 80305-3328, United States
 
ZIP Code
80305-3328
 
Solicitation Number
OMAO_FleetInformationSystem
 
Archive Date
7/31/2014
 
Point of Contact
Susan L Labovitz, Phone: (303) 497-7943, Suzanne A Romberg-Garrett, Phone: 303-497-5110
 
E-Mail Address
susan.labovitz@noaa.gov, suzanne.garrett@noaa.gov
(susan.labovitz@noaa.gov, suzanne.garrett@noaa.gov)
 
Small Business Set-Aside
N/A
 
Description
U.S. Department of Commerce National Oceanic & Atmospheric Administration Office of Marine and Aviation Operations Fleet Information System REQUEST FOR INFORMATION 1.0 INTRODUCTION: The National Oceanic & Atmospheric Administration (NOAA) Office of Marine and Aviation Operations (OMAO) is seeking information from interested parties to determine availability of commercial off-the-shelf (COTS) products that meet the attached requirements for a Fleet Information System (FIS). OMAO will utilize FIS to improve the transparency, accessibility, and reliability of organizational data sourced from stakeholders with variable levels of connectivity over a broad geographical distribution. The purpose is to support improved decision making for managing the NOAA ship and aircraft fleet. FIS is intended to be a distributed enterprise information system that fully integrates multiple legacy data systems to capture and display fleet management data in an interactive dashboard format. The intent of this request for information (RFI) is to identify and evaluate COTS systems that potentially meet, or could be modified to meet the requirements. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. Please note, response to this notice is for NOAA's informational and planning purposes only and is issued in accordance with FAR Provision 52.215-3 provided at: http://www.acquisition.gov/far/current/html/52_215.html#wp1144503. No solicitation document exists at this time. Consideration for a potential acquisition may occur in or after FY14. Issuance of this notice does not constitute any obligation on the part of the Government to procure these items or services to issue a solicitation. In addition, the Government is under no obligation to pay for information submitted in response to this RFI, and responses to this notice cannot be accepted as offers. Any information that the vendor considers proprietary should be clearly marked as such. Response to this notice is NOT mandatory to be eligible to receive any potential solicitation. NOAA may conduct additional market research through additional RFIs, requesting interested party's capability briefings, and other means. If a solicitation is released, it will be synopsized on the Federal Business Opportunities (FedBizOpps) website. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement. Interested parties are invited to submit responses to this notice (see Section 4.0 Information Requested, for a list of RFI questions). Responses should include a brief capability statement outlining the party's qualifications. Responses should also contain: the organization's name, address, point of contact(s), telephone number, and fax number. Also, submit evidence documenting not to exceed 3 experiences on projects similar to FIS described below in Section 2.0 Background Information. Include the project title, dollar value, a short description, and point of contact(s) with contact information. All information received in response to this notice will be safeguarded accordingly. Non-disclosure statements will be signed by non-government advisors who view the responses to this notice. Responses to this notice will not be returned. NOAA will NOT be eliminating any organization from any potential subsequent competitions based on the results of this RFI process. Microsoft Word format using 11 point Times New Roman font is the preferred format for submission. Adobe PDF is also acceptable. NOAA must receive the submissions by email no later than 3:30 PM EST, July 11, 2014 at the following email address: susan.labovitz@noaa.gov. For questions regarding this RFI you may also contact the contracting specialist at: Name: Susan L. Labovitz Address: U.S. Department of Commerce - NOAA 325 Broadway, SOU6 Boulder, CO 80305 Telephone: 303-497-7943 2.0 BACKGROUND INFORMATION: 2.1 FIS Overview FIS is envisioned to be an enterprise level information system for the organization, management and display of enterprise data. It should interface various levels of the OMAO management organization and the data available regarding material condition and performance of fleet assets (human and mechanical capital). The intent of FIS is to improve the efficiency and effectiveness of the organization by providing the ability to gain business insight through the application of performance management and analytical tools against a set of manual processes and data maintained in a diverse set of OMAO and NOAA data and information systems. This fleet management capability will provide decision makers with actionable understanding of platform and mission readiness, enabling critical insight into the performance and status of mission support functions. FIS will improve the transparency, accessibility, and reliability of enterprise data to support improved decision making in both its mission and business operations. Because NOAA/OMAO currently uses a diverse set of multidisciplinary systems, it is important that FIS have the following attributes: ● Utilize, if possible, a cloud computing architecture as defined by the National Institute of Standards and Technology (NIST) ● Comply with the Federal Information Security Management Act (FISMA) ● Enable a phased implementation of functions and features ● Enable transfer of data from existing disparate databases 2.2 FIS Requirements 2.2.1 Coordination of Management Data (receive, interpret) ● Must integrate data from multiple disparate sources listed below (currently, some of the data sources necessary for FIS are automated, while others would require manual entry until an automated system could be integrated): ○ Mission readiness and utilization performance tracking and analysis: ■ Shipboard daily activity log ■ Ship readiness report ■ Material condition monitored by: ● Shipboard Automated Machinery Management System ● Machinery casualty/repair, currently tracked using an Intelex database ■ Fleet scheduling ● Currently using an interactive on-line prioritization system ■ Online cruise evaluation reports ○ Personnel: ■ Personnel Readiness Database (future asset) ● To contain data such as name, pay grade, contact info, fitness for duty status, duty location, training requirements and training status, certificates and license/qualifications and their status, etc. ■ Crew augmentation tracking spreadsheet ■ Department of Commerce web-based time and attendance system ○ Budget tracking and analysis: ■ Currently only high level information managed by a data base used by NOAA finance office to monitor fiscal expenditures. Has report generating capability and exports data in comma delimited Excel format ■ Ship Obligation Log (ob-log) spreadsheets from each ship 2.2.2 Dashboard Display of Management Data, Mission Readiness, and General Status Information ● Must have a user friendly graphical interface to display information in a meaningful and easy to interpret way, and on an as needed basis ○ Ship and aircraft readiness information ■ Detail on justification/reason for readiness status ■ Personnel readiness information. i.e. - Total headcount, vacancies, and rates of attrition, retention, and staff augmentation, operational manning status for each center and each asset, and trends/indicators, including percent medically fit for duty, and hiring action cycle time ○ Organizational metrics and trends: ■ Current operational accomplishment: actual sea days for ships or flight hours for planes, vs. planned for the operating year ● Mission metrics such as # of miles surveyed or research stations accomplished ■ Safety trends (accidents and incidents) ■ Asset readiness trends ○ Information systems status and IT security risk posture ○ Searchable employee rosters and billet lists ○ Budget & Finance Information: ■ Allocations, obligations, commitments, and variances for each level of the organization, from individual unit to CFO ■ Financial trends and indicators ■ Analytical functions such as planned vs actual spending and average cost per day figures ○ Engineering & Maintenance Information ■ Aggregated number of Fleet Inspection Items (deficiencies) per center and asset ■ Inventory of mission systems/sensors ■ Engineering trends and indicators, e.g. Casualty Reports issued, and percent overdue ○ Asset Allocation Information ■ Current status of the fleet scheduling process, including milestones ■ Fleet and Aircraft allocation plans for the current, previous, and subsequent operating year ■ Number and nature of ancillary projects in each allocation plan ■ Capability matrix for each ship and aircraft ■ Ship time requests received ■ Ship and aircraft maintenance schedules ○ Operational information: ■ Ship tracker ■ Department of State travel advisories ■ Status of port clearances ○ Customer service information ■ Aggregated customer feedback ratings for each center, asset, and project ■ Product data management monitoring (referring to data collected in service of OMAO's customers) ● Product data timeliness, accuracy, and reliability. Pipeline information for each center and asset ● Product data trends and indicators, e.g. days since last submission ○ Safety & Environmental Information ■ incident and near miss metrics ■ Safety and environmental trends and indicators, e.g. lessons learned submitted, rate of incidents ■ Catalogue of individual incidents, including links to the accident report and lessons learned report 3.0 ADDITIONAL REFERENCE DOCUMENTATION: • The FIS User Requirements Document is 148 pages long. It is available upon request from Susan Labovitz at susan.labovitz@noaa.gov or Suzanne Romberg Garrett at Suzanne.Garrett@noaa.gov. 4.0 INFORMATION REQUESTED: OMAO is conducting market research and intends to collect responses from industry experts in maritime fleet management software. The information collected will help OMAO plan implementation of FIS. Response shall be no more than 15 pages and shall include the following: 4.1 Company Profile • Include the company name, address, point of contact(s), telephone number, fax number, and size of business. • Tell us about your organization, submit a capability statement outlining (summarizing) your qualifications. • Provide experiences providing similar systems engineering and software development support designing of complex systems (not to exceed 3). 4.2 Questions 4.2.1 COTS Availability and Compatibility with Data Sources Q1: Please provide your recommendation for a COTS solution to the FIS need on the basis of fiscal and technical merit, with a life-cycle cost estimate for adoption and implementation vice development and build out of a purpose built system. ● Please address the following in your recommendation: ○ Architecture and engineering of proposed system (i.e. distributed vs centralized) ○ Operational and maintenance requirements ○ Proposed deployment ○ Systems integration ○ Compatibility with portable devices Q2: Given the nature of the data sources which will feed FIS, would you advise a version of FIS which is a stand-alone replacement of legacy databases, with FIS having customer service tool functionality (i.e. - single source data entry portal for all divisions of OMAO), or a version of FIS which simply coordinates the data from disparate sources and displays it as a provider of decision making information only? Please describe your rationale for this recommendation in terms of cost/benefit, given that some of the current sources of data fall outside of OMAO control, and that life-cycle funding is uncertain. 4.2.2 Support for New and Emerging Technologies Q1: Please describe any NEW (emerging) technologies that are likely to become available for commercial use between 2014-2017 that you believe will be important for OMAO to be aware of. Q2: There is a presidential directive to maximize use of cloud-based technology. Are there any cloud-based options available for FIS? If so, are they FISMA compliant? 4.2.3 Performance Metrics Q3: FIS is envisioned to be an IT-based system that provides data and decision support tools, and increases the value of data for users by enabling integration and interoperability that otherwise may not be possible for systems that are designed and built for specific applications. What would you propose as best practices for performance metrics for such an integrated system? How would you propose to measure customer satisfaction for this system? 4.2.4 Governance Q4: OMAO is implementing a Baldrige Criteria based governance approach. How would your recommendation fit this approach? What other governance might you suggest? Q5: Please address the following w/r/t your recommendation: ● Standards or best practices on which system is/would be based ● Accessibility and security, considering the fact that many users will be deployed on ships, and that much of the data in the system is sensitive and must meet FISMA compliance standards ● Management of system 4.2.5 Acquisition Alternatives Q6: OMAO is considering the following as possible acquisition alternatives. Please provide a brief supporting statement on your recommendation. ● Government owned application ● Contractor owned and licenced to Gov ● Contractor owned, subscription based ● Industry design and build (Government hosted) ● Outsource - industry design and build (industry hosted) ● Other innovative approaches from organizations/stakeholders in sharing costs and benefits that you would recommend. 4.2.6 Questions Considered But Not Planned to be Submitted Q7: Please advise if there is anything you feel is an important consideration that we have not addressed in our questions or requirements.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/DOC/NOAA/MASC/OMAO_FleetInformationSystem/listing.html)
 
Record
SN03404023-W 20140626/140625021712-e4a0f311c1a379322c1b04536ccaea81 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.