SCMS Targeted Market Research Questionnaire.xlsx
XLSX spreadsheet 28 KB Posted
- Solicitation number
- 70FA3127I00000001
- Issued by
-
Federal Emergency Management Agency
About this file
This file is a Targeted Market Research Questionnaire designed to evaluate commercially available Software-as-a-Service (SaaS) supply chain management solutions for FEMA's Supply Chain Management System (SCMS) modernization initiative. The questionnaire is organized into four sections: System Architecture, Security, and Core Functional Capability; Commercial Availability; Requirement Modification, Phasing, and Optional Capabilities; and Rough Order of Magnitude Estimate.
Section A requests detailed responses regarding technical architecture, including contingency planning for system outages, browser and mobile device compatibility, cloud-to-on-premises integration capabilities, and security protocols such as PII protection, HTTPS certification, and vulnerability management. The security portion also addresses dedicated support staff availability and infrastructure protection. Section A's functional capability questions assess whether solutions can manage FEMA-owned assets and partner resources, capture and track commercial shipments with web-based carrier rate portals, provide in-transit visibility across multiple transportation modes, support pre-assembled inventory kits, accommodate just-in-time bulk disaster response logistics, and manage transportation booking and payment processing. Section B asks vendors to confirm capability areas with yes/no responses across nineteen functional domains, including order and request management, inventory visibility, warehouse management, field-site fulfillment, transportation management and procurement, partner and state portals, EDI/API integration, in-transit visibility, parcel tracking, reporting and dashboards, mobile scanning, FedRAMP and identity management security, Section 508 accessibility compliance, continuity and scalability for 400 to 1,000 concurrent users, and training and support services. Section C requests identification of requirements requiring material customization or phasing, with recommendations for modification, option designation, government-furnished services, third-party integration, or custom development. Section D requests a non-binding Rough Order of Magnitude estimate spanning a base period and four option periods, detailing one-time implementation costs, recurring SaaS and hosting costs, operations and maintenance, cybersecurity and compliance support, help desk and training, and optional surge support, along with implementation timeline, principal assumptions, and three major cost drivers.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SCMS RFI 1.3.pdf | ||
| SCMS Vendor Streamlined Profile Matrix.xlsx | XLSX spreadsheet | |
| SCMS Draft Statement of Work 1.1.pdf | ||
| Appendix A Industry Comments Questions and Clarification Matrix.xlsx | XLSX spreadsheet |
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
A. System Architecture, Securit A. System Architecture, Security, and Core Functional Capability
The following questions seek information on the technical architecture, security posture, and core supply chain functionality of commercially available SaaS solutions. Please provide concise responses and identify any material assumptions, dependencies, integrations, configuration, or customization required.
| Category | Question | Response | |
| 1 | System Architecture | What type of contingency planning does the system have in place to ensure continuity of operations, in the event of a geographic, system or server outage? | |
| 2 | System Architecture | Does the system support all major browsers? | |
| 3 | System Architecture | Does the system support a fully compatible and functional mobile interface that can be used on all commonly used mobile device platforms (including Android, iOS, and Microsoft)? | |
| 4 | System Architecture | Does the platform provide a cloud solution to deploy an application layer that can integrate with an on-site solution for the data layer? | |
| 5 | Security Protocols | Does the solution have dedicated support staff willing to discuss security concerns if requested by FEMA? | |
| 6 | Security Protocols | How does the system protect personally identifiable information (PII) found in patron and circulation data (i.e. encryption, etc.)? | |
| 7 | Security Protocols | Does the system operate with an HTTPS certificate, and what other relevant security certifications does it hold? | |
| 8 | Security Protocols | How does the system protect from introducing vulnerabilities to an existing security infrastructure? | |
| 9 | System Functionality | What are the standard functions of the system, and which software modules support supply chain management? | |
| 10 | System Functionality | Does the system have the capability to manage the entire supply chain including FEMA owned assets and resources as well as those provided by Partners in other federal agencies and non-governmental organizations (NGOs)? | |
| 11 | System Functionality | Does the system have the capability to capture, plan, manage, and track shipments requiring commercial transportation, and does it include a web-based portal for shippers to attain contract transportation rates from carriers (if yes, please explain)? | |
| 12 | System Functionality | How does the system provide in-transit visibility and location updates in standard truck transportation as well as situations using other modes of transportation, including air transport and/or container ships, etc.? | |
| 13 | System Functionality | Does the system allow for kits of related systems to be pre-associated together and held in inventory as a package and then quickly and easily shipped together? | |
| 14 | System Functionality | Does the system accommodate a model of logistics where commodities are held in inventory and maintained in a high state of readiness, and then large bulk orders are shipped very quickly when a disaster occurs? | |
| 15 | System Functionality | Does the system have the capability to schedule and book transportation for assets and commodities with FEMA approved transportation service providers, and allows completed transportation moves to be promoted for payment through a third-party vendor? |
B. Commercial Availability B. Commercial Availability
Identify whether your existing commercial SaaS supply chain management solution can meet the following FEMA capability areas.
| Capability Area | Questions | Response | |
| 1 | TRL | Identify your existing commercial SaaS supply chain management solution Technology Readiness Level, a TRL of 8 is preferred | |
| 2 | Other | Identify our existing commercial SaaS supply chain management solution FedRAMP authorization status and impact level, and any material security, accessibility, licensing, or third-party dependencies associated with the solution | |
| Capability Area | Questions | Response (Yes/No) | |
| 3 | Order and request management | Create, approve, source, fulfill, update, cancel, and close disaster logistics requests and orders. | |
| 4 | Inventory visibility | View on-hand, available, in-transit, allocated, and received inventory across FEMA and authorized partner locations. | |
| 5 | Warehouse management | Receive, put away, cycle count, pick, load, ship, label, and manage pallet-, lot-, expiration-, and asset-level inventory. | |
| 6 | Field-site fulfillment | Support mobile receiving, shipping, ASN updates, proof of delivery, and field inventory management. | |
| 7 | Transportation management | Plan, tender, track, and manage commercial transportation, carriers, bills of lading, costs, and shipment status. | |
| 8 | Transportation procurement | Collect, manage, and load carrier rates, manage bids, and support capacity-finder or spot-bid activities. | |
| 9 | Vendor and partner portal | Allow authorized vendors and partners to view orders, create ASNs, provide shipment information, and upload documents. | |
| 10 | State portal | Allow authorized state users to receive FEMA commodities and manage authorized state-level logistics transactions. | |
| 11 | EDI, API, and web-service integration | Exchange orders, ASNs, shipment status, tracking, and other logistics data with FEMA systems, vendors, carriers, and partners. | |
| 12 | In-transit visibility and mapping | Display shipment, trailer, asset, GPS, and facility location and status information. | |
| 13 | Parcel tracking | Integrate with major parcel carriers for tracking, delivery updates, and parcel visibility. | |
| 14 | Reporting, dashboards, and alerts | Produce ad hoc reports, scheduled reports, dashboards, alerts, and data exports. | |
| 15 | Mobile and scanning capability | Support approved mobile devices, barcode/QR scanning, radio-frequency devices, and field transactions. | |
| 16 | Security and identity management | Support FedRAMP, PIV/SSO, multifactor authentication, role-based access, logging, encryption, and audit requirements. | |
| 17 | Section 508 accessibility | Support applicable Section 508 and WCAG Level A and AA accessibility requirements. | |
| 18 | Continuity and scalability | Support alternate processing, disaster recovery, 400 concurrent users, and potential surge to 1,000 users. | |
| 19 | Training and support | Provide training environment, training materials, help desk, and operations and maintenance support. |
C. Requirement Modification, Ph C. Requirement Modification, Phasing, and Optional Capabilities
Identify any SCMS requirements that would require material customization, create significant cost or schedule risk, or limit FEMA’s ability to use an existing commercial product or service. For each identified requirement, recommend whether it should be modified, phased, treated as an option, or addressed through a Government-furnished service or third-party integration. Add rows as needed.
| Requirement or Capability Area | Reason Commercial Solution Cannot Meet Requirement As-Is | Recommended Approach: Modify, Phase, Option, Government-Furnished Service, or Third-Party Integration, or Custom Development | Expected Benefit or Impact | |
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 |
D. Rough Order of Magnitude Est D. Rough Order of Magnitude Estimate
Provide a non-binding ROM range for the anticipated base period and each option period. Include estimated one-time transition, implementation, configuration, data migration, and integration costs; annual recurring SaaS, hosting, operations, maintenance, cybersecurity, and support costs; and optional surge or extended-hours support, if applicable.
Also provide the estimated implementation timeline through operational readiness, principal assumptions, and three major cost drivers. FEMA is not requesting a formal quote, certified cost or pricing data, detailed labor rates, or a binding commitment.
| Cost Category | Base Period | Option Period 1 | Option Period 2 | Option Period 3 | Option Period 4 | Five-Year Total | Assumptions / Notes |
| One-time transition, implementation, configuration, data migration, and integration | $ - 0 | ||||||
| SaaS subscription, licensing, and cloud hosting | $ - 0 | ||||||
| Operations and maintenance support | $ - 0 | ||||||
| Cybersecurity, FedRAMP, continuous monitoring, and compliance support | $ - 0 | ||||||
| Help desk, training environment, and user support | $ - 0 | ||||||
| Optional surge or extended-hours support | $ - 0 | ||||||
| Other, if applicable | $ - 0 | ||||||
| Total ROM Range | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | TRUE |
| Additional Information | Response |
| Estimated timeline from award through operational readiness | |
| Primary pricing model | |
| Principal assumptions used to develop the ROM | |
| Major cost driver 1 | |
| Major cost driver 2 | |
| Major cost driver 3 | |
| Assumed annual escalation, if any | |
| Capabilities or costs excluded from the ROM | |
| Optional services included in the ROM, if any |
File details come from the government source that posted it. Updated .