24-E0013_OEHHA_RFI_SEHRS_Project.pdf

Event Number: 24-E0013

REQUEST FOR INFORMATION

Number: 24 -E0013

For

STATEWIDE EXTREME HEAT RANKING SYSTEM (SEHRS)

PROJECT

Release Date: November 6, 2024

Intentionally left blank

Table of Contents Request for Information (RFI) I. Introduction and Overview

A. Purpose of this RFI B. Key Action Dates C. RFI Response Instructions D. Contact Information E. Vendor Questions F. RFI Disclaimer

II. PROJECT DESCRIPTION

A. Background B. Current Environment C. Proposed Environment

III. ATTACHMENTS

Attachment – A Vendor Profile Attachment - B Rough Order of Magnitude (ROM) Cost Estimate Attachment - C Technical Environment Attachment – D System Implementation and Technical Support Attachment – E Optional Products and/or System Solutions Attachment – F Business Requirements Checklist Attachment - G See Separate Excel Document (Two Tabs)

Request for Information (RFI) DATE: November 6, 2024

TO: All Interested Parties

FROM: Office of Environmental Health Hazard Assessment, hereafter referred to as the State

SUBJECT: Event Number: 24-E0013

Introduction and Overview

This Request for Information (RFI) is being released by the Office of Environmental Health Hazard Assessment (OEHHA or ‘State’).The RFI is to solicit information and best practices from the vendor community in an effort to assist the State in determining what is currently available in the marketplace based on the objectives and requirements as described herein, and to approximate the dollars that may be needed to acquire the necessary information technology (IT) services.

A. Purpose of this RFI

The purpose of this RFI is to solicit information, suggestions, and best practices on the technical resources needed to transform and maintain a static website to a dynamic website as well as design, develop, deploy, and maintain a mobile application and their corresponding integrated data systems for the Statewide Extreme Heat Ranking System (SEHRS) project initiated by the OEHHA in the State of California. The ranking system will be designed to notify Californians that a heat event is occurring and identify resources to protect themselves. This ranking system will be a first-of-its-kind in the nation and is poised to further California’s leadership in mitigating and adapting to climate change. Both the SEHRS website application and mobile application are jointly known as CalHeatScore. Both applications must support business resiliency as it is integral to the business operation of the department and requires little or no downtime to remain in compliance with state and local regulations and guidelines. In addition to the health statistics, climate and temperature data, CalHeatScore will provide locally relevant information about upcoming heat events as well as locations of the nearest cooling locations (may be known as cooling centers, cooling stations or cool zones), urban tree canopies (UTC) or medical centers such as hospitals or urgent care clinics during a heat event.

A data system is a collection of programs and processes that extracts, modifies, stores and integrates information from various sources. The data sources used by OEHHA are temperature data from National Weather Service (NWS), climate data from National Oceanic and Atmospheric Administration (NOAA), public data hubs from Office of Emergency Services (OES) and health data statistics from Department of Health Care Access Information (HCAI). Due to confidentiality requirements, University of California, Los Angeles (UCLA) had been contracted to extract data and develop algorithms from data originating from the NOAA and HCAI data sources.

A cooling location is an established network of free, air-conditioned settings (such as libraries or community centers) across Counties in California that allow respite for older adults, persons with disabilities, or anyone looking to escape the extreme heat during the summer. Cooling locations are a way for residents to lower individual utility usage and help conserve energy for the whole community.

UTC are the layer of leaves, branches, and stems of trees that cover the ground when viewed from above. In urban areas, UTC are known to reduce the urban heat island effect, decreases heating/cooling costs, lowers air temperatures, diminishes air pollution, increases property values, encourages wildlife habitat, and provides aesthetic and community benefits such as improved quality of life

As the lead state agency for the assessment of health risks posed by environmental contaminants such as climate change, pesticides and carcinogens, OEHHA’s mission is to protect and enhance the health of Californians and our state’s environment through scientific evaluations that inform, support and guide regulatory and other actions. OEHHA’s Extreme Heat Ranking System processes will include data collection and dissemination as well as data warehouse processes and management. OEHHA does not possess the in-house technical capabilities to fully design and develop a dynamic website as well as create a mobile application and their corresponding data warehouses necessary for technical and program requirements.

Design of the proposed dynamic website and mobile development environment musts consider the high-level technical needs of such systems, specifically:

1. User authentication and enforcement of role-based access rights on database records

2. Ingestion of data submitted by authenticated users through a secure web interface

3. Storage solutions for the expected volume of data while considering the expected rate of growth in data volume in future years

4. Network capacity and infrastructure necessary to handle the rate of data submitted to the system

5. Computational capacity needed to effectively handle data processing operations within the turnaround time needed for continuous system operations

6. Data management infrastructure, including administrative consoles, to facilitate the compilation of numerous raw data submittals into a cohesive and meaningful output product

7. Quality assurance infrastructure for both real-time data validation as well as diagnostic tests to ensure the integrity of derived datasets, with configurable parameters and thresholds

8. Interactive web tools providing output products in tabular, graphical, map-based, and file-based formats

9. A user interface which supports real-time reporting, reviewing, editing, and managing of data submittals designed for a modern and streamlined user experience

10. Consistency with state and federal electronic reporting requirements, including the federal cross-media electronic reporting rule (CROMERR) and ADA compliance

11. Application programming interfaces (APIs) which allow the systems to query or be queried by other related systems in order to confirm or exchange information

12. Data structures and API endpoints that facilitate the efficient exchange of source-level records with other OEHHA systems storing related information on temperatures technology, health notifications, and rules

13. Geospatial functionality services including geocoding addresses, storing spatial data layers, performing spatial operations, and supporting web-based mapping applications

14. Storage and management of unstructured data and metadata to support exploratory work

15. The ability for the user interface text and labels to toggle between available alternative languages (translated and maintained by OEHHA) in select public facing web pages and help sections

Please reference the attached list of requirements for further details.

As information technology systems and infrastructure has evolved, it is desirable to look at the current state of infrastructure options to determine the best fit for such a system. Consideration should be given to all available software, platform, and infrastructure as a service option (e.g. on-premises or cloud-based), as well as any available commercial off-the-shelf solutions which could be utilized.

In addition to off-the-shelf solutions, interested parties are invited to describe other potential products and solutions, and to suggest strategies to assist OEHHA in determining if a Commercial Off the Shelf (COTS), Modified Off the Shelf (MOTS), integrated product set (i.e., integration of multiple products), or a custom solution would best address the required functions described in this RFI. Multiple products or solutions may be described in the RFI response and are encouraged.

Collective information provided by the vendor community may be used to develop or identify solution alternatives, specifications, and/or cost estimations necessary to acquire systems, solutions or software. The State understands that data provided in this RFI is not sufficient to enable detailed analysis and costing by Respondent. Please provide your best advice based on your experience with other organizations and initiatives of this kind. Responses to this RFI should adhere to the questions listed in the Attachments.

Completion of this RFI shall be performed at no cost to the State. The intent of this RFI is solely for information and planning purposes and does not constitute a solicitation. A contract will not be awarded based on this RFI.

Please read this RFI document thoroughly and adhere to the response submission guidelines.

B. Key Action Dates

Listed below are the RFI Key Action Dates and times (all times noted are Pacific Time) by which actions should be taken or completed.

Event Date / Time Release RFI Wednesday, 11/6/2024 Intent to Respond Due (Optional but encouraged) (Response Due Via Email)

Wednesday, 11/13/2024

Last Day to Submit Questions Due Wednesday, 11/20/2024 3 PM Release of Answers and/or Addenda Wednesday, 11/27/2024 RFI Response Due Date Wednesday, 12/11/2024 3 PM

C. RFI Response Instructions

1. Responses to this RFI must be submitted via e-mail, preferably in the native file format of

Microsoft Word, to the State’s contact listed in Section I.D. Contact Information, and must include the following information in the email subject line: 24-E0013 RFI OEHHA SEHRS Project.

2. Contact information including the name, title, address, phone number, and e-mail address of the primary contact person for the RFI.

3. Responses must be submitted by the date and time stated in the Key Action Dates.

4. Respondent must submit a signed cover letter with their response to the RFI that also includes a statement by the individual certifying the information in the response is true and accurate to the best of his/her knowledge at the time of submittal.

5. Respondent should respond to all applicable information in the Attachments A-F:

a. Attachment A - Vendor Profile

b. Attachment B - Rough Order of Magnitude (ROM) Cost Estimate

c. Attachment C - Technical Environment

d. Attachment D - System Implementation and Technical Support

e. Attachment E - Optional Products and/or System Solutions

f. Attachment F - Business Requirements Checklist

6. OEHHA is requesting Voluntary Cost Information from Respondent to this RFI. OEHHA understands that the costs provided are voluntary and non-binding. Cost information may be used to develop cost estimations and budgets. Respondent are encouraged to provide a general cost value (or range of costs) for each product or solution identified in the RFI Response.

D. Contact Information

Respondent must submit their written response, via e-mail to the State contact listed below:

Contact: Acquisitions Sections Agency: Office of Environmental Health Hazard Assessment (OEHHA) Email: Acquisitions.Sections@oehha.ca.gov Phone: (916) 327-8359

E. Vendor Questions

Respondent must submit questions regarding this RFI, via e-mail, by the specified date and time stated in the Key Action Dates to the email contact stated in Section D. Contact Information.

What to Include in an Inquiry

1. Include in the subject line of the e-mail: 24-E0013 RFI OEHHA SEHRS Project

2. Vendor name and contact, telephone number, e-mail address.

mailto:Acquisitions.Sections@oehha.ca.gov

3. A description of the subject or issue in question, or discrepancy found.

4. RFI section, page number, or other information useful in identifying the specific problem or issue stated in the question.

5. All questions will be responded to in writing (via e-mail) to all parties that have expressed an intent to respond to the RFI.

F. RFI Disclaimer

This RFI is strictly informative for OEHHA, and it is not a competitive bidding process. OEHHA is under no obligation to Respondent in any manner whatsoever. Neither this RFI nor any information provided by any Respondent hereto shall be deemed to create any legally binding agreement or obligations upon OEHHA. A response to this RFI is not an offer and cannot be accepted by OEHHA to form a binding contract. This RFI is solely designed to provide OEHHA with meaningful information to assist OEHHA with developing or identifying solution alternatives, specifications, and/or cost estimations necessary to acquire systems, solutions or software.

This RFI is issued for information and planning purposes only, and it does not constitute a solicitation. Responses to the RFI will not be returned. Respondents are solely responsible for all expenses associated with responding to this RFI. The State is not responsible for any expenses associated with responding to this RFI. OEHHA may consider vendor responses in developing specifications and requirements for development of the future solicitations for the SEHRS project, such as, but not limited to, a Request for Offer (RFO), Request for Quotation (RFQ), Invitation for Bid (IFB), Request for Proposal (RFP), action or other action.

The submission of a response does not constitute any commitment on the part of the Vendor.

However, the vendor agrees that the submitted information is correct to the best of the vendor’s knowledge. Also, the right to compete in future procurements is not affected in the event that the party chooses not to submit a response to this RFI. OEHHA is also interested in learning the reasons for not submitting a response and may reach out to Respondent who did not submit a response in this regard.

Respondent are advised that all documents submitted in response to this RFI will become the property of the State of California and will be regarded as public records under the California Public Records Act (CPRA) pursuant to Government Code Section 6250 et seq. and subject to review by the public. The intent of this RFI is to validate project objectives and requirements for possible future solicitations. Please do not include any confidential or proprietary information in responses to this RFI as it may be disclosed or be subject to the CPRA.

II. PROJECT DESCRIPTION

A. Background

The Office of Environmental Health Hazard Assessment (OEHHA), division of California Department of Environmental Protection Agency (CalEPA), is requesting information to transform a static website and develop a mobile application, both known as CalHeatScore, and the maintenance of both platforms post deployment, for the statewide extreme heat ranking system.

CalEPA, is a state cabinet-level agency within the government of California. The mission of CalEPA is to restore, protect and enhance the environment, to ensure public health, environmental quality, and economic vitality. OEHHA is the scientific adviser within CalEPA and provides the health effects assessments that assist regulatory decision makers within CalEPA, the California Department of Public Health (CDPH) and other internal agencies and non-governmental organizations such as California Department of Insurance (CDI), California Office of Emergency Services and scientific communities including non-governmental organizations (NGOs). The aforementioned agencies, together with the residents of California, broadcasting agencies and news media, are the expected users of the CalHeatScore.

Assembly Bill 2238 requires CalEPA to develop a statewide extreme heat ranking system. This task was subsequently delegated to OEHHA. The ranking system would be designed to notify Californians that a heat event is occurring and identify resources to protect themselves. This ranking system would be a first-of-its-kind in the nation and is poised to further California’s leadership in mitigating and adapting to climate change. For maximum accessibility, OEHHA is proposing the transformation of a static website to a dynamic website and the development of a mobile application that would communicate critical, time-sensitive information on extreme heat events to a wide audience.

The dynamic website and mobile applications will be populated with data from the listed sources but would be dissimilar in terms of functionality. For instance, the website would not have notifications nor offline capabilities. However, both platforms must be designed to provide maximum accessibility and compatibility. In addition to the extreme heat ranking, both applications would provide locally relevant information about upcoming heat events as well as locations of the nearest cool zone, urban tree canopy or medical centers such as hospitals or urgent care clinics during a heat event.

Here are the goals for the project:

Goal 1: Developing a statewide extreme heat ranking system for website and mobile application from various data sources.

a) This involves acquiring, preparing, and analyzing various data sets to be used by the Scientific Team at OEHHA. The data sources used by OEHHA are temperature data from National Weather

b) Service (NWS), climate data from National Oceanic and Atmospheric Administration (NOAA), public data hubs from Office of Emergency Services (OES) and health data statistics from Department of Health Care Access Information (HCAI). Due to confidentiality requirements, University of California, Los Angeles (UCLA) had been contracted to extract data and develop algorithms from data originating from the NOAA and HCAI data sources. The awarded Request for Proposal (RFP) solution provider would be given access to the data developed by UCLA.

c) OEHHA has experience in planning and coordinating external scientific review panels as well as public meetings/workshops. OEHHA intends to engage and consult with communities that have been most impacted by prior heat events to ensure that the system will meet their needs. Once the system has been finalized, OEHHA will need to host the tool and summarize the work through written reports, presentations, and other communication materials

Goal 2: Developing recommendations for thresholds or triggers for public policies to reduce the health impacts of heat. (OEHHA to deliver)

a) These thresholds or triggers would account for geographic and demographic variation in Californians’ susceptibility to heat to ensure that the triggers are protective across diverse populations.

Goal 3: Developing recommendations for metrics to measure the short-term and long-term impacts of heat on human health. (OEHHA to deliver)

a) This involves developing an evaluation plan and developing analyses to assess the effectiveness of the statewide extreme heat ranking system in reducing heat related illnesses and deaths.

b) This also includes planning and conducting equity analyses to assess whether health inequities are decreasing over time and how the system can be improved to better protect vulnerable populations.

Goal 4: Public engagement and communication. (OEHHA to deliver)

a) Many people are not aware of the health risks of heat and may not take precautions to reduce potential health impacts. The statewide extreme heat ranking system would help elevate the importance of this public health issue and provide appropriate thresholds and triggers to protect the most vulnerable populations.

b) A public communication plan, grounded in the state of the science, is required to focus on communities with populations that are most at risk of public health impacts from extreme heat events.

Goal 5: Providing consultation to the Integrated Climate Adaptation and Resiliency Program (ICARP) on the public communication plan. (OEHHA to deliver)

a) While ICARP would be the lead on the development of a public communication plan, OEHHA would provide consultation services and contribute to the implementation of various communication plans.

Goal 6: Transform a website from static to dynamic and develop a cross-platform browser agnostic mobile phone application, both named CalHeatScore, for the system.

a) The static website has already been designed and its domain name secured. However, it must be converted from a static website to a dynamic website that would be engaging to the users.

b) Use of smart phones has become commonplace, and a cross-platform browser agnostic smart phone application would enable the sharing of critical, time sensitive information to a wide audience. A weather application for the statewide extreme heat ranking system would effectively provide locally relevant information about upcoming heat events, tips for reducing heat exposures, and local resources such as cool zones.

Goal 7: Maintaining, updating, and improving the spatial and non-spatial components over time.

a) To ensure data quality, performance and reliability, data maintenance is paramount. The tasks that would constitute data maintenance include data quality and validation, data backup and recovery, data security and access control, data warehouse performance tuning, data documentation and metadata management and lastly, data warehouse testing and debugging.

B. Current Environment

This is a maiden project so no current environment exists.

The static website has already been designed and its domain name secured. However, it must be converted to a dynamic website that would be engaging to the users. The requirements for the dynamic website are outlined in Attachment F.

The creation of a non-monetized cross-platform mobile application, CalHeatScore and its maintenance after post-launch. The proposed requirements of the mobile application are outlined in Attachment F. The CalHeatScore mobile application allows users to understand current heat temperatures and understand the health impacts associated with extreme heat. CalHeatScore provides a comprehensive overview of the latest information on extreme heat rankings obtained from scientific algorithms, projected temperatures, and forecasts at specific locations. When used in conjunction with the accompanying educational material, the information can supplement local existing heat emergency response, adverse weather or emergency action plans with guidance on proactive actions to take, such as health-protective advice, planning and preparing for heat emergencies, determining the locations of the closest cooling centers, and may offer educational materials on nature-based solutions in the planning of daily work and school activities.

CalHeatScore will be obtaining their temperature data from publicly available data sources from National Weather Service (NWS), climate data from National Oceanic and Atmospheric Administration (NOAA), public data hubs from Office of Emergency Services (OES) and health data statistics from Department of Health Care Access Information (HCAI). Due to confidentiality requirements, University of California, Los Angeles (UCLA) had been contracted to extract data and develop algorithms from data originating from the NOAA and HCAI data sources. The successful contract awardee would be given access to the data developed by UCLA.

It is envisioned that all data would need to be processed and stored in a cloud-based data warehouse to enable real-time analytics and queries. In addition, CalHeatScore will link educational materials from California Department of Public Health as well as publish, on an annual basis, datasets from California Department of Health Care Access (HCAI) with the intention of including information relating to the following topics in the near future:

Medically underserved areas

Emergency healthcare facilities

Medically underserved population

Rate of hospitalization base on heat effects

Critical health advisory related to heat ranking threshold

Using information from the data warehouse, the successful contract awardee will coordinate Geographic Information Systems (GIS) efforts with OEHHA staff, access listed and suggested geospatial sets to enhance spatial analysis, perform geospatial analyses, integrate geographic database with archival documents and new field data, promote map and exhibit creation, develop visualization tools and tilers as well as execute data analysis and metrics.

In a parallel project, geospatial information related to CalHeatScore has been developed by a third-party vendor. This information may be repurposed with a collaborative agreement for the CalHeatScore mobile application project.

Figure 1. Current Architecture.

This is a maiden project so no current architecture exists.

C. Proposed Environment

Figure 1 shows the future architecture of SEHRS project. Data for new application is derived from public information sources. From these environments, data is loaded via APIs to pre-determined files. Query tools, search tools, and mapping tools are able to access the databases through a collection of primitive php-based web tools and Python programming language or any other technology stack that would align with OEHHA’s mobile application development goals. See Figure below.

D. Timeline

OEHHA

Please see Section I, sub-section B for key action dates. The timeline for responding to the Request for Information for the SEHRS project is five (5) weeks. See page 7 for more information.

OEHHA expects to complete the compilation of RFI responses within two (2) weeks of RFI close.

Evaluation of the RFI responses would be begin shortly thereafter. It is anticipated that it would take four (4) weeks to complete the evaluation.

E. Questions and Answers

Please see Section I, sub-section B for key action dates. Refer to this section if you are interested to correspond to the Office of Contracts & Business Unit at Acquisitions.Sections@oehha.ca.gov to obtain clarification on any aspect of the project. Responses for the questions received would be uploaded on a regular basis in the Questions and Answers segment of the RFI.

F. Budget

The budget range for this project is between $650,000 to $750,000. However, Respondents are invited to submit a response that includes a rough order cost breakdown for specific details pertinent to the solution development such as product design, software licenses, server fees, delivery requirements and engineering capabilities.

G. Requirements

See Attachment F for the project requirements. Project assumptions, constraints and dependencies must be clearly outlined in the RFI response.

H. Scope

OEHHA welcomes responses from interested parties on the project scope below. All interested parties should elaborate in detail the segment(s) which they can fulfill as well as the budget and timeline they anticipate completing their project. Respondents which are unable to fulfill all components of the project scope must outline their collaboration methodology or strategy in developing a successful partnership with another Respondent to ensure successful execution of project.

a. Transform a static website to a dynamic website

b. Creation of a non-monetized cross-platform browser agnostic mobile application

c. Maintenance of the website and mobile applications post deployment

For project scope item #a: The static website had already been designed and its domain name secured. However, it must be converted to a dynamic website that would be engaging to the users.

The requirements for the dynamic website are outlined in Attachment F.

For project scope item #b: The creation of a non-monetized cross-platform browser agnostic mobile application, CalHeatScore and its maintenance after post-launch. The requirements of the mobile application are outlined in Attachment F. The CalHeatScore mobile application allows users to understand current heat temperatures and understand the health impacts associated with extreme heat. CalHeatScore provides a comprehensive overview of the latest information on extreme heat rankings obtained from scientific algorithms, projected temperatures, and forecasts at specific locations. When used in conjunction with the accompanying educational material, the information can supplement local existing heat emergency response, adverse weather or emergency action plans with guidance on proactive actions to take, such as health-protective advice, planning and preparing for heat emergencies, determining the locations of the closest cooling centers, and may offer educational materials on nature-based solutions in the planning of daily work and school activities.

CalHeatScore will be obtaining their temperature data from publicly available data sources from National Weather Service (NWS), climate data from National Oceanic and Atmospheric Administration (NOAA), public data hubs from Office of Emergency Services (OES) and health data statistics from Department of Health Care Access Information (HCAI). Due to confidentiality requirements, University of California, Los Angeles (UCLA) had been contracted to extract data and develop algorithms from data originating from the NOAA and HCAI data sources. The Respondent would be given access to the data developed by UCLA.

It is envisioned that all data would need to be processed and stored in a cloud-based data warehouse to enable real-time analytics and queries. In addition, CalHeatScore will link educational materials from California Department of Public Health as well as publish, on an annual basis, datasets from California Department of Health Care Access (HCAI) with the intention of including information relating to the following topics in the near future:

Medically underserved areas

Emergency healthcare facilities

Medically underserved population

Rate of hospitalization base on heat effects

Critical health advisory related to heat ranking threshold

Using information from the data warehouse, the Respondent will coordinate Geographic Information Systems (GIS) efforts with OEHHA staff, access listed and suggested geospatial sets to enhance spatial analysis, perform geospatial analyses, integrate geographic database with archival documents and new field data, promote map and exhibit creation, develop visualization tools and tilers as well as execute data analysis and metrics.

In a parallel project, geospatial information related to CalHeatScore has been developed by a third-party vendor. This information may be repurposed with a collaborative agreement for the CalHeatScore mobile application project.

As it is anticipated that users will be using addresses to search, here are the desired functionalities for mobile search filters:

1. Autocomplete

2. Autofill

3. Address

3.1. Address Geocoding

3.1.1. Sub Address

3.1.2. Point Address

3.1.3. Street Address

3.1.4. Street Address Intersection

3.1.5. Street Address Extension

3.1.6. Business Marker

3.1.7. Street Name

3.1.8. Locality

3.1.9. Zip Codes

3.1.10. Zip Codes Tabulation Areas

3.1.11. Zip Codes with 4-digit extension

3.1.12. Point of Interest

3.1.13. Census Tracts

3.1.14. Coordinates

3.1.15. Latitude/Longitude

3.1.16. AddBldg (reference to name of building)

3.1.17. City, State

3.1.18. County

Since there is information which would be displayed using spatial data, here are the desired functionalities of the map styles filters available to users.

1. Streets

2. Satellites

3. Hybrid

4. Topo

5. Gray

6. Dark Gray

7. Oceans

8. National Geographic

9. Terrains

10. Open Street Maps (OSM)

OEHHA will rely on the guidance of all Respondents regarding the correct technology stack to provision the API as long as the API development facilitates seamless data transfer, improves operational efficiency, enhances user experiences, adheres to security and scalability and contributes to flexibility and adaptability when services and technology evolve.

Key features of the mobile application must include:

1. Real Time temperature readings

2. Real Time geolocations and directions for hospitals, cooling centers

3. A visual indicator of the current heat ranking and associated risk levels specific to user’s geographical location

4. Infographics can be in any of these formats – donut chart, pictograms, maps, bar chart, histogram, bubble chart, gauge chart

5. Precautionary recommendations specific to heat ranking-associated risk levels

6. An interactive, daily forecast, occurring every 24 hours beginning at 0001 hours to 2359 hours of the same day, of CalHeatScore heat values, risk levels, and recommendations for planning outdoor work activities

7. Users will use the different mobile search filters as outlined in Category H on Page 12, to determine location and retrieve temperature and humidity controls information

8. Signs and symptoms and first aid for heat-related illnesses

9. Personalized alerts that notify users when the temperature is above a certain range

10. Geolocation based technology that is balanced with mobile application security and privacy

11. Accompanying data to help users make health-based decisions and protect themselves from extreme heat

12. Locations of nearest hospitals, urban tree canopies, cooling locations also known as cooling stations, cooling centers, cool zones

13. Driving directions to nearest hospitals, urban tree canopies, cooling locations also known as cooling stations, cooling centers, cool zones

14. Presence of Feature Toggles

15. Availability of a second language at the time of deployment and the future ability to expand on the number of languages

For project scope item #c: Because the journey of the mobile app does not end at its launch, Respondents are requested to elaborate on how they plan to assist OEHHA with the following types of website and mobile application maintenance activities post-deployment:

1. Emergency Maintenance

• This refers to unforeseen problems that occur unexpectedly and require immediate attention

2. Perfective Maintenance

• Refers to proactively responding to feedback and modifying app source code to enhance user experiences

3. Adaptative Maintenance

• This involves the update of app to ensure compatibility with new operating systems, hardware upgrades or changes to software environment

4. Preventive Maintenance

• This refers to preempting potential errors and reducing the app’s complexity to improve its maintainability by code restricting, code optimization and updating of documents

5. Corrective Maintenance

• This relates to the issues surrounding design, coding and application logic to ensure the app functions as desired.

III. ATTACHMENTS

Attachment – A Vendor Profile

1. Identify the Company Name, address, city, state, and zip code, telephone, and fax numbers.

2. Identify the name, title, address, phone and fax numbers, and email address of the primary contact person for this RFI.

3. Provide a brief overview of your company including number of years in business, number of employees, nature of business, and description of clients.

4. Identify any parent corporation and/or subsidiaries, if applicable.

5. Give a brief description of your company’s product(s), system(s), service(s), etc. that may be relevant to this RFI. Include the date of the first installed site or first service provided.

6. List any industry awards/recognition that you have received.

Indicate the total number of installations in the last 10 years, and list them by the year of installation and the total number of users.

Attachment - B Rough Order of Magnitude (ROM) Cost Estimate

Level of Effort/Rough Order of Magnitude (LOE/ROM) Check the appropriate LOE/ROM designation (all are expressed in terms of person hours for the combined roles detailed below):

Small 0 – 4,999

Medium 5000 – 9,999

Large 10,000 – 19,999

Jumbo 20,000 – 30,000

Vendor Defined Enter LOE/ROM

Implementation and Initial Configuration Labor/Services/Fees Insert additional lines as needed. Information below is suggested information only.

Check the appropriate LOE/ROM designation (all are expressed in terms of person hours for the combined roles detailed below):

List the major roles/tasks needed to implement the Solution. Insert additional lines as needed.

Estimated Range of cost for total implementation services, based upon metrics below.

ROLE/TASKS

(Please add, remove and elaborate on task lines for each Role and estimate the number of hours needed per Task and by Role. The Roles provided do not necessarily represent all Roles that may be required to perform the necessary work.)

Estimated range of labor hours for project

Project Manager

Business Analyst

Database Administrator Systems Architect Trainer Front End Developer (User Interface Modules, System Admin Module) Back End Developer (DBA, Middleware) Network / Infrastructure Engineering Security and Identity Management Testing QA/QC and User Acceptance Testing (UAT preparation and execution, UAT testers provided by OEHHA)

Other: Please Describe

TOTAL ESTIMATED LABOR HOURS RANGE:

Other Hardware/Infrastructure Component Estimated Initial Implementation

Estimated Annual Ongoing Cost Range for

Cost Range for Project

Maintenance, Operation, and Support

TOTAL ESTIMATED HW/Infrastructure COSTS

RANGE:

Answers and Assumptions Used in Cost Estimate Please answer, in as much detail as possible, OEHHA’s questions (1-5) below.

Also, please provide details pertaining to the assumptions, expectations, and/or performance parameters used as the basis of the cost estimate.

OEHHA’s QUESTIONS and VENDOR’S RESPONSE/ANSWERS:

1. What is the estimated timeframe that the solution will take to build and implement, based on the cost estimates and stages outlined in section 3 above? Are the stage durations feasible?

2. What dependencies are there for this implementation?

3. Is the cost estimate based on an agile, phased, waterfall or hybrid development and implementation methodology? Explain the SDLC that would be used.

4. Are there any requirements that would preclude you from competing should an RFP be released? If yes, what suggested changes would allow you to compete?

5. Are the goods, products or services you’ve identified in your RFI response available on a Federal GSA or State of CA LPA? If yes, please identify the contract type, name and number.

6. The estimated cost for this effort is currently at a range of $650,000 to $750, 000. Please provide your estimated cost for the services requested and if possible, provide a rough order breakdown of these costs. Please provide separate cost estimates indicating building of the application with mandatory as well as desirable features and one with only the mandatory features. These details will assist OEHHA in further dialogue with participating Respondent.

Respondents which are unable to fulfill all components of the project scope are encouraged to outline their collaboration methodology or strategy in developing a successful partnership(s) with other Respondents to ensure successful execution of the project.

VENDOR’S ASSUMPTI ONS:

What assumptions has the Vendor made in preparing a response to this RFI ((include use of third-party vendors and auxiliary contracts?)

1. {List All Assumptions Here}

Attachment - C Technical Environment

HARDWARE, SOFTWARE, AND NETWORK AND

INTERFACE QUESTION VENDOR RESPONSE

1. Are there any license enforced hardware limits?

2. What is the routing table capacity?

3. What is the oversubscription ratio?

4. Do you provide legacy hardware support?

5. What type of APIs will be provided?

6. What type of API technologies are being used?

7. What platforms and applications have you successfully integrated with?

8. How do you authenticate using the API?

9. What future features are you incorporating into their API and what are the expected delivery schedules?

10. Is there a SDK?

11. Are there integrations with certain data sources that your company would recommend for a solution like this?

12. How do you ensure the security of the software you develop?

13. Are you familiar with and able to comply with industry-specific regulations?

Attachment – D System Implementation and Technical Support

PROJECT TRANSITION QUESTION VENDOR RESPONSE

1. Please describe the approach to facilitate different levels of testing from unit, regression, performance, and user acceptance test. Would you facilitate testing tools or another method to demonstrate the solution is delivered with quality while meeting the requirements put forward in this RFI?

2. Please describe how the solution address disaster recovery implementation and procedures

3. Please provide information on the approach you follow for ensuring proper system installation, deployment, and how system upgrades are handled.

4. Please provide the execution approach you follow when facilitating usability, administrative, and support training on the solution?

Attachment – E Optional Products and/or System Solutions

SYSTEM PROPOSAL QUESTION VENDOR RESPONSE

1. Description of Hardware

2. Description of Software

3. Description of Training provided

4. Estimated System Cost (ballpark)

5. Estimated Cost of Ongoing Support (ballpark)

Attachment – F

Business Requirements Checklist

Refer to the following Requirements Checklist. A response to each checklist item is required. Brief comments may be entered in the table. Assign one of the following Availability Codes to each item:

No Selection A – Feature is available and installed B – Feature is available but not yet installed C – Feature is currently under development (indicate anticipated date of availability) D – Feature is not available.

Review the attached Business Requirements and respond accordingly to the Business Requirements Checklist below. Included is a brief list of commonly used headings for system business requirements.

See separate document for Attachment G - Excel Sheet - RFI Business Requirements.