Fire & Emergency Medical Services Records Management System (FEMSRMS) BASE + 4 Option Years

THIS IS NOT A REQUEST FOR PROPOSAL. NO PROPOSALS ARE TO BE SUBMITTED IN RESPONSE TO THIS NOTICE. This notice is issued by NASA/ITPO to post a Statement of Work to solicit responses from interested parties. This document is for information and planning purposes and to allow industry the opportunity to verify reasonableness and feasibility of the requirement, as well as promote competition. Fire & Emergency Medical Services Records Management System (FEMSRMS) BASE + 4 Option Years NASA/ITPO is hereby soliciting information from potential sources for Fire & Emergency Medical Services Records Management System (FEMSRMS) BASE + 4 Option Years The National Aeronautics and Space Administration (NASA) ITPO seeking capability statements from all interested parties, including all socioeconomic categories of Small Businesses (SB) and Historically Black Colleges and Universities (HBCU)/Minority Institutions (MI) for the purposes of determining the appropriate level of competition and/or small business subcontracting goals for Fire & Emergency Medical Services Records Management System (FEMSRMS) BASE + 4 Option Years. Vendors are encouraged to demonstrate capabilities as a prime, subcontractor and/or teaming partner. The Government reserves the right to consider a Small Business, Small Disadvantaged Business (SDB), HUBZone, Veteran Owned Small Business (VOSB), Service-Disabled Veteran Owned Small Business, and Women-Owned Small Business (WOSB) set-aside based on responses received. Respondents are requested to provide informed input on realistic and appropriate SB subcontracting and/or participation goals for the specific requirement. This type of feedback supports NASA s market research and helps ensure the acquisition strategy is aligned with actual industry capability. Industry feedback is requested for: 1.SB Subcontracting goals; 2 Barriers that may limit SB participation, such as certifications, uniquetechnical requirements, security needs, specialized tools, or high-risk performance areas and/or 3.Strategies to increase SB participation, including: Breaking requirements into smaller components Identifying areas appropriate for subcontracting Considering teaming or mentor prot g approaches This RFI is not to be construed as a commitment by the Government, nor will the Government pay for the information submitted in response. The Government may 2 Rev.: 05/2026 not respond to questions/concerns submitted. The Government will use the information to finalize the RFP as necessary. All comments or questions must be submitted electronically via email to Kimberly Sandoz Kimberly.r.sandoz@nasa.gov and Cory Rasnic cory.t.rasnic@nasa.gov, no later than 8/03/2026 @ 6:00PM EST. When responding reference RFI # 80TECH26RFI0023. NASA Clause 1852.215-84, Ombudsman, is applicable. The Center Ombudsman for this acquisition can be found at: https://www.hq.nasa.gov/office/procurement/regs/Procurement-Ombuds-Comp-Advocate-Listing.pdf If a solicitation is released, then it and any additional documents will be available on Sam.gov. It is the offeror's responsibility to monitor this website for the release of the solicitation and amendments (if any). Potential offerors will be responsible for downloading their own copy of the solicitation and amendments, if any. The key details are summarized below: STATEMENT OF WORK (SOW) 1.General Information Project Title: Fire & Emergency Medical Services Records Management System (FEMSRMS) Agency/Organization: OCIO on behalf of the Office of Protective Services Requiring Activity: Procure a Commercial off the Shelf (COTS) Software as a Service (SaaS) solution for Fire and EMS Records Management Program Office: Office of Protective Services Date: July 2026 2.Background The NASA Office of Protective Services (OPS) fire departments require a robust, integrated, and secure Records Management System (RMS) to replace outdated, manual, and fragmented systems. Increasing emergency service demands have amplified risks and inefficiencies associated with spreadsheet-based record keeping, creating operational gaps that jeopardize firefighter safety, mission assurance, and Center readiness. Implementing a comprehensive RMS directly supports OPS s strategic commitment to safeguarding NASA personnel, infrastructure, and mission-critical operations. To ensure capital project delivery, improve oversight and reporting capabilities, and to mitigate risk, NASA requires a Commercial Off the Shelf (COTS) and Software as a Service (Saas) enterprise-level Fire and EMS solution that aligns with industry standards and is robust, integrated and secure. 3 Rev.: 05/2026 3.Objective NASA seeks to acquire a Commercial Off the Shelf (COTS) solution for Fire and EMS Records management system along with Professional Services for tailoring and implementation of such a system. The configured COTS solution shall be known as Fire & Emergency Medical Services Records Management System (FEMSRMS) NASA s objective with the acquisition of FEMSRMS is to implement and configure a COTS solution that will: Replace manual and fragmented fire and EMS Records Management Systems witha modern cloud-based solution that meets NASA OPS and OCIO requirements. Enable site consolidation for data sharing. Achieve cost savings through efficiencies gained from reducing the number ofsolutions maintained/supported. The contractor shall provide a cloud-based configured COTS offering, shall meet the technical and operational requirements herein, shall ensure integration with specified information technology (IT) systems and software, and shall operate and maintain FEMSRMS in accordance with industry best practices, Federal Regulations, and NASA guidelines and requirements. The contractor shall provide a solution that is Federal Risk and Authorization Management Program (FedRAMP) High Authorized at the time of contract award. The Government intends to achieve Agency Authority to Operate (ATO), in accordance with NPR 7120.7. 4.Scope 4.1 Functional Standards 4.1.1 The solution must be a COTS product and hosted in a cloud environment. 4.1.2 The FEMSRMS solution must provide the following capabilities: Incident reporting & fire documentation: create fire/incident reports andemergency response documentation with FRMS capture, NERIS v1connectivity and an NFIRS legacy crosswalk for reporting. ePCR & hospital data exchange: NEMSIS-compliant electronic patientcare reporting that is HIPAA-aware, includes a hospital handoff packet,and supports one-way digital transfer to receiving facilities. Integrated authentication & security: PIV-based integrated authenticationfor users. CAD ingestion & mobile responder/notifications: vendor-agnostic CADinterface (Central Square compatibility required), mobile respondercapability (notifications, incident access on any device), and offline-capable mobile cache with sync-on-reconnect for intermittent-connectivitysites (e.g., White Sands, Stennis). Pre-Incident Planning: Build actionable pre-incident plans for responsepersonnel. 4 Rev.: 05/2026 Connections to ESRI/ArcGIS for mapping, hydrant and water supplytracking Facility inspections, pre-plans, and ITM: mobile inspection and pre-planworkflows with deficiency tracking, Inspect-Test-Maintain (ITM)management, trend/reporting on inspection compliance. Personnel scheduling & rostering: centralized personnel records, roster andleave management, qualifications tracking, auto shift-coverage proposals,and automated staffing notifications. Training, virtual training & compliance: course catalog, completionrecords, certification-expiry alerts, virtual end-user training, and traininganalytics for compliance with applicable standards (e.g., NFPA, FAA,NASA where required). Exposure tracking & health/wellness: per-responder, per-incident exposurehistory, cancer-presumption alignment, and health/wellness documentationand reporting. Incident command & on-scene accountability: ICS form set, tacticalworksheets, resource tracking, action-item tracking, and personnelaccountability at incidents. Apparatus, equipment, fleet & asset management: asset register forapparatus and equipment, maintenance scheduling, OOS tracking, recallmanagement, inspections, and lifecycle/supply tracking. Narcotics & controlled-substance management: DEA-compliant chain-of-custody, witnessed waste, reconciliation, and controlled-substance trackingintegrated with asset/inventory controls. Investigations & evidence management: fire cause-and-origindocumentation with customizable investigation forms and full evidencechain-of-custody tracking. Events, activities & non-incident records: capture and report dailydepartmental activities and non-incident events. Data, analytics & reporting: incident analytics, compliance and inspection-trend reports, and exportable data for downstream use. Data migration & test environment: limited/legacy data import capabilityplus a separate non-production test/sandbox environment for training andconfiguration testing. 4.1.3 The…