SLED Opportunity · MICHIGAN · OAKLAND COUNTY
AI Summary
Oakland County Emergency Management seeks proposals for an emergency weather monitoring and alerting service providing real-time situational awareness and automated severe weather notifications to support operational decisions.
Solicitation for Emergency Weather Monitoring Services. Oakland County Emergency Management (OCEM) requires a weather monitoring and alerting solution that provides real-time situational awareness, automated severe weather notifications, and access to weather intelligence necessary to support operational decision-making. **Solicitation Type**: RFP - Request for Proposal (Formal) **Source ID**: PU.AG.USA.1328.C24145126 **Piggyback Contract**: No **Questions are submitted online**: Yes **Bid Submission Type**: Electronic Bid Submission **Owner Organization**: Oakland County Emergency Management (OCEM) **Solicitation Number**: Oak-0000001209 **Reference Number**: 0000430110 **Pricing**: Lump sum **Bid Documents List**: | Item Name | Description | Mandatory | Limited to 1 file | |---|---|---|---| | Bid Documents | Documents defining the proposal | No | No | **Questions and Answers**: | Question | Answer | |---|---| | OneRain Questions Please have customer confirm bid date. 26 July is a Sunday. Can we provide redlines to the draft contract (Attachment A)? What is meant by "applicable NWS products" in section 3.3? Watches/Warnings/Advisories? Will any data from County-owned environmental monitoring equipment (e.g. flood monitoring stations, rain gauges, etc.) be integrated into the system or just NWS data? Can we request 1 week extension. Thanks, Ted O'Connell ted.oconnell@aem.eco 508.566.7105 Answer: Answered in Addendum 3 | OneRain Questions Please have customer confirm bid date. 26 July is a Sunday. Can we provide redlines to the draft contract (Attachment A)? What is meant by "applicable NWS products" in section 3.3? Watches/Warnings/Advisories? Will any data from County-owned environmental monitoring equipment (e.g. flood monitoring stations, rain gauges, etc.) be integrated into the system or just NWS data? Can we request 1 week extension. Thanks, Ted O'Connell ted.oconnell@aem.eco 508.566.7105 Answer: Answered in Addendum 3 | | Clarifying customer support Section 5.0, 5.5: Please clarify whether '24/7/365 customer support' refers to technical/platform support only, or whether the County would also assign evaluation value to access to operational meteorologists for decision support during severe weather events. Answer: Answered in Addendum 3 | Clarifying customer support Section 5.0, 5.5: Please clarify whether '24/7/365 customer support' refers to technical/platform support only, or whether the County would also assign evaluation value to access to operational meteorologists for decision support during severe weather events. Answer: Answered in Addendum 3 | | Year 4/5 pricing clarification Section 1.1 and Attachment C: The contract is three years with two one-year options, but Attachment C requests pricing for Years 1–3 only. How will Option Year 4 and 5 pricing be established, and does Section 3.15's requirement that prices 'remain firm for the entire contract period' extend to option years? Answer: Answered in Addendum 3 | Year 4/5 pricing clarification Section 1.1 and Attachment C: The contract is three years with two one-year options, but Attachment C requests pricing for Years 1–3 only. How will Option Year 4 and 5 pricing be established, and does Section 3.15's requirement that prices 'remain firm for the entire contract period' extend to option years? Answer: Answered in Addendum 3 | | Pricing points clarification Section 3.7: Please clarify how the 30 Price Proposal points will be calculated: e.g., lowest three-year total receives maximum points with others prorated, or committee judgment. And please confirm whether the evaluated price is the sum of Years 1–3 from Attachment C, or some other dimension. Answer: Answered in Addendum 3 | Pricing points clarification Section 3.7: Please clarify how the 30 Price Proposal points will be calculated: e.g., lowest three-year total receives maximum points with others prorated, or committee judgment. And please confirm whether the evaluated price is the sum of Years 1–3 from Attachment C, or some other dimension. Answer: Answered in Addendum 3 | | 3.5 question item 3.5. What is defined as "historical severe weather data"? Answer: Answered in Addendum 3 | 3.5 question item 3.5. What is defined as "historical severe weather data"? Answer: Answered in Addendum 3 | | Pre-Bid queries by Netlink 1. 5.0 → 3.1 Platform Requirements: Can Oakland County confirm the expected number of Named Users, Concurrent Users, Administrator Users, and Mobile Application Users (iOS & Android)? 2. 5.0 → 3.1 Platform Requirements: Does Oakland County prefer an Unlimited User, Named User, Concurrent User, or Organization-wide licensing model? 3. 5.0 → 3.4 GIS Requirements: Approximately how many monitoring locations, facilities, critical assets, or GIS polygons will need to be configured initially? 4. 5.0 → 3.4 GIS Requirements: Which GIS formats will Oakland County provide (ESRI Shapefile, GeoJSON, ArcGIS Feature Services, KML/KMZ)? 5.5.0 → 3.4 GIS Requirements: Does Oakland County require integration with existing GIS platforms, Emergency Management Systems, CAD systems, or other County applications? If yes, please specify. 6.5.0 → 3.2 Weather Monitoring Capabilities: Is the County expecting weather information solely from vendor-provided sources, or are integrations with third-party weather feeds also required? 7.5.0 → 3.5 Historical Data Requirements: What historical weather data retention period is expected? 8.5.0 → 3.3 Alerting Requirements: Will Oakland County provide its own SMS gateway, or should vendors include SMS delivery costs within the proposal? 9. 5.0 → 3.3 Alerting Requirements: What is the estimated annual volume of SMS alerts, Email alerts, and Push Notifications? 10. 5.0 → 3.3 Alerting Requirements: Besides SMS, Email, and Mobile Push Notifications, are additional notification channels required? 11. 5.0 → 3.1 Platform Requirements: Is support required for Android, iOS, or both platforms, and will County-managed devices require deployment through an MDM solution? 12.5.0 → 3.1 Platform Requirements: Please confirm the preferred hosting strategy, including preferred cloud provider, deployment model (multi-tenant or dedicated), Government Cloud requirements, hosting region, Hybrid Cloud, On-Premise deployment, and data residency requirements. Answer: Answered in Addendum 3 | Pre-Bid queries by Netlink 1. 5.0 → 3.1 Platform Requirements: Can Oakland County confirm the expected number of Named Users, Concurrent Users, Administrator Users, and Mobile Application Users (iOS & Android)? 2. 5.0 → 3.1 Platform Requirements: Does Oakland County prefer an Unlimited User, Named User, Concurrent User, or Organization-wide licensing model? 3. 5.0 → 3.4 GIS Requirements: Approximately how many monitoring locations, facilities, critical assets, or GIS polygons will need to be configured initially? 4. 5.0 → 3.4 GIS Requirements: Which GIS formats will Oakland County provide (ESRI Shapefile, GeoJSON, ArcGIS Feature Services, KML/KMZ)? 5.5.0 → 3.4 GIS Requirements: Does Oakland County require integration with existing GIS platforms, Emergency Management Systems, CAD systems, or other County applications? If yes, please specify. 6.5.0 → 3.2 Weather Monitoring Capabilities: Is the County expecting weather information solely from vendor-provided sources, or are integrations with third-party weather feeds also required? 7.5.0 → 3.5 Historical Data Requirements: What historical weather data retention period is expected? 8.5.0 → 3.3 Alerting Requirements: Will Oakland County provide its own SMS gateway, or should vendors include SMS delivery costs within the proposal? 9. 5.0 → 3.3 Alerting Requirements: What is the estimated annual volume of SMS alerts, Email alerts, and Push Notifications? 10. 5.0 → 3.3 Alerting Requirements: Besides SMS, Email, and Mobile Push Notifications, are additional notification channels required? 11. 5.0 → 3.1 Platform Requirements: Is support required for Android, iOS, or both platforms, and will County-managed devices require deployment through an MDM solution? 12.5.0 → 3.1 Platform Requirements: Please confirm the preferred hosting strategy, including preferred cloud provider, deployment model (multi-tenant or dedicated), Government Cloud requirements, hosting region, Hybrid Cloud, On-Premise deployment, and data residency requirements. Answer: Answered in Addendum 3 | | Pre-Bid queries by Netlink 13. 5.0 → 4 Implementation & Configuration Services: Please confirm the required deployment environments (Development, QA, UAT, Production, Disaster Recovery, Sandbox) and whether separate cloud accounts, networking, databases, or Kubernetes clusters are required. 14. 5.0 → 3.1 Platform Requirements: Please confirm the County's Identity and Access Management requirements, including Active Directory, Azure AD/Entra ID, SAML, OAuth, Single Sign-On (SSO), Multi-Factor Authentication (MFA), and Role-Based Access Control (RBAC). 15. 5.1 Qualifications / 4.8 Compliance with Laws and Regulations: Please confirm the mandatory security and compliance standards applicable to the proposed solution (CJIS, NIST, SOC 2 Type II, ISO 27001, FedRAMP, HIPAA, etc.). 16.5.0 → 3.1 Platform Requirements: Please confirm the County's security requirements, including encryption at rest, encryption in transit, TLS version, secrets management, WAF, DDoS protection, vulnerability scanning, container image scanning, and penetration testing requirements. 17. 5.0 → 3.1 Platform Requirements: Please confirm the networking requirements, including public/private deployment, VPN connectivity, private endpoints, ExpressRoute/AWS Direct Connect, firewall, DNS, and static IP requirements. 18. 5.0 → 4 Implementation & Configuration Services: Please confirm the Disaster Recovery and Backup requirements, including RTO, RPO, backup frequency, retention period, replication strategy, failover approach, and disaster recovery testing frequency. 19. 5.0 → 3.5 Historical Data Requirements: Please confirm the database and storage requirements, including migration expectations, storage encryption, lifecycle policies, and data retention requirements. Answer: Answered in Addendum 3 | Pre-Bid queries by Netlink 13. 5.0 → 4 Implementation & Configuration Services: Please confirm the required deployment environments (Development, QA, UAT, Production, Disaster Recovery, Sandbox) and whether separate cloud accounts, networking, databases, or Kubernetes clusters are required. 14. 5.0 → 3.1 Platform Requirements: Please confirm the County's Identity and Access Management requirements, including Active Directory, Azure AD/Entra ID, SAML, OAuth, Single Sign-On (SSO), Multi-Factor Authentication (MFA), and Role-Based Access Control (RBAC). 15. 5.1 Qualifications / 4.8 Compliance with Laws and Regulations: Please confirm the mandatory security and compliance standards applicable to the proposed solution (CJIS, NIST, SOC 2 Type II, ISO 27001, FedRAMP, HIPAA, etc.). 16.5.0 → 3.1 Platform Requirements: Please confirm the County's security requirements, including encryption at rest, encryption in transit, TLS version, secrets management, WAF, DDoS protection, vulnerability scanning, container image scanning, and penetration testing requirements. 17. 5.0 → 3.1 Platform Requirements: Please confirm the networking requirements, including public/private deployment, VPN connectivity, private endpoints, ExpressRoute/AWS Direct Connect, firewall, DNS, and static IP requirements. 18. 5.0 → 4 Implementation & Configuration Services: Please confirm the Disaster Recovery and Backup requirements, including RTO, RPO, backup frequency, retention period, replication strategy, failover approach, and disaster recovery testing frequency. 19. 5.0 → 3.5 Historical Data Requirements: Please confirm the database and storage requirements, including migration expectations, storage encryption, lifecycle policies, and data retention requirements. Answer: Answered in Addendum 3 | | Pre-Bid queries by Netlink 20. 5.0 → 3.4 GIS Requirements / 3.3 Alerting Requirements: Please confirm the required integration interfaces, including REST APIs, API authentication, API rate limits, National Weather Service (NWS) integration, ArcGIS compatibility, and notification service providers (SMS, Email, Push Notifications). 21. 5.0 → 2 Scope of Work: Is this solution intended to replace an existing weather monitoring platform or operate alongside an existing solution? 22. 5.0 → 4 Implementation & Configuration Services: If replacing an existing solution, will historical weather data, GIS layers, user accounts, and alert configurations require migration? 23. 5.5 Customer Support: Please confirm the expected support SLAs for Critical, High, Medium, and Low priority incidents, and whether 24×7 support is required for production incidents only or also for user assistance. 24. 5.5 Customer Support: Please confirm the County's operational support expectations, including production support ownership, incident management, change management, maintenance windows, patch management, and escalation procedures. 25. 5.3 Training: Approximately how many County personnel require Administrator Training and End User Training, and what is the preferred delivery approach (onsite, virtual, or hybrid)? 26. 6.1 Project Milestones: Will GIS datasets, user accounts, and alert configurations be available immediately upon contract award to support the implementation timeline? 27.6.1 Project Milestones: Will Oakland County provide separate Development, Test, UAT, and Sandbox environments? 28. 6.1 Project Milestones: Will a designated County UAT approver be available throughout the testing period? 29.6.1 Project Milestones: Given the implementation timeline, does the County have a priority order for functional areas that must be delivered first, and is Go-Live expected as a single deployment or a phased implementation? Answer: Answered in Addendum 3 | Pre-Bid queries by Netlink 20. 5.0 → 3.4 GIS Requirements / 3.3 Alerting Requirements: Please confirm the required integration interfaces, including REST APIs, API authentication, API rate limits, National Weather Service (NWS) integration, ArcGIS compatibility, and notification service providers (SMS, Email, Push Notifications). 21. 5.0 → 2 Scope of Work: Is this solution intended to replace an existing weather monitoring platform or operate alongside an existing solution? 22. 5.0 → 4 Implementation & Configuration Services: If replacing an existing solution, will historical weather data, GIS layers, user accounts, and alert configurations require migration? 23. 5.5 Customer Support: Please confirm the expected support SLAs for Critical, High, Medium, and Low priority incidents, and whether 24×7 support is required for production incidents only or also for user assistance. 24. 5.5 Customer Support: Please confirm the County's operational support expectations, including production support ownership, incident management, change management, maintenance windows, patch management, and escalation procedures. 25. 5.3 Training: Approximately how many County personnel require Administrator Training and End User Training, and what is the preferred delivery approach (onsite, virtual, or hybrid)? 26. 6.1 Project Milestones: Will GIS datasets, user accounts, and alert configurations be available immediately upon contract award to support the implementation timeline? 27.6.1 Project Milestones: Will Oakland County provide separate Development, Test, UAT, and Sandbox environments? 28. 6.1 Project Milestones: Will a designated County UAT approver be available throughout the testing period? 29.6.1 Project Milestones: Given the implementation timeline, does the County have a priority order for functional areas that must be delivered first, and is Go-Live expected as a single deployment or a phased implementation? Answer: Answered in Addendum 3 | | Pre-Bid queries by Netlink 30. 6.1 Project Milestones: If a third-party weather data provider (e.g., NWS, radar, satellite provider) experiences an outage during testing, how will project acceptance and timelines be managed? 31. Attachment C – Pricing Sheet: May vendors propose optional premium capabilities outside the mandatory scope, provided they are separately priced? Answer: Answered in Addendum 3 | Pre-Bid queries by Netlink 30. 6.1 Project Milestones: If a third-party weather data provider (e.g., NWS, radar, satellite provider) experiences an outage during testing, how will project acceptance and timelines be managed? 31. Attachment C – Pricing Sheet: May vendors propose optional premium capabilities outside the mandatory scope, provided they are separately priced? Answer: Answered in Addendum 3 | **Addendums**: | Addendum | Date | Note | |---|---|---| | Addendum No. 1 | 07/17/2026 03:15 PM EDT | | | Addendum No. 2 | 07/24/2026 09:49 AM EDT | | | Addendum No. 3 | 07/28/2026 09:50 AM EDT | |
SLED stands for State, Local, and Education. These are solicitations issued by state governments, counties, cities, school districts, utilities, and higher education institutions — as opposed to federal agencies.
SamSearch Platform
AI-powered intelligence for the right opportunities, the right leads, and the right time.