6313_questions_responses.pdf
PDF 119 KB Posted
- Attached to
- Environmental Health and Safety (EHS) Solution
- Solicitation number
- S-44300-00018021
- Issued by
- Marion County, Oregon
About this file
This is a Questions and Responses document from Oregon State Hospital regarding RFP# S-44300-00018021 for an Environmental Health and Safety (EHS) Solution. The procurement seeks a cloud-based, SaaS-platform software system to manage incident reporting, inspections, risk assessments, audits, chemical management, regulatory compliance, training tracking, and reporting across the hospital's Salem and Junction City campuses. The solution must integrate with Oregon Workday, RLDatix internal incident tracking system, and VelocityEHS backend systems, with implementation required by July 1, 2027. Proposers were required to submit questions by September 28, 2026, with proposals due October 13, 2026 at 5:00 PM Pacific Time. The initial contract term is ten years with renewal options to a cumulative maximum of fifteen years. The anticipated Notice of Intent to Award is November 2, 2026, and proposals are firm offers valid for 180 days following the closing date.
The procurement requires proposers to demonstrate experience implementing EHS software for large-scale enterprises with scalability and interoperability needs, with minimum qualifications including three references from successful implementations within the last five years. Anticipated user licensing includes three administrators, approximately 17 EHS staff members managing records, and approximately 2,500 general staff submitting reports or completing assigned items. Historical data migration from VelocityEHS spans approximately ten years, covering approximately 70 storage locations and 4,000 chemical inventory items across both campuses. Data security requirements mandate compliance with NIST SP 800-53 Moderate controls, SOC 2 Type II, and ISO 27001, with FedRAMP or StateRAMP authorization acceptable as proof of compliance but not required. All Agency Data must be stored, accessed, and transmitted within the United States, with case-by-case approval for non-domestic access. Oregon suppliers receive a 5% price preference, and pricing proposals must include comprehensive subscription, implementation, support, and personnel costs with clearly detailed expenses and no hidden costs beyond those submitted.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 6313_RFP_EHS solution_final draft.pdf | ||
| Attachment E Pricing_updated.xlsx | XLSX spreadsheet | |
| 18021_Draft Addendum_1.pdf | ||
| 6313_Att B.docx | DOCX document | |
| 6313_RFP_Adden-1_EHS solution.pdf | ||
| 6313_Att E.docx | DOCX document | |
| 6313_Att F.docx | DOCX document | |
| 6313_Att C.docx | DOCX document | |
| 6313_Att D.docx | DOCX document | |
| 6313_Att G.docx | DOCX document |
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
RFP# S-44300-00018021 EHS Solution Solicitation
Item No.
Topic Question Response
Section 1.2, Schedule (p. 5):
target dates.
Does the Agency have a target go-live date, or a fiscal or accreditation deadline driving the implementation timeline?
Implemented by July 1, 2027
2 Integrations Please identify the interfaces, authentication methods, available APIs or file formats, integration frequencies, and systems of record for Oregon Workday, the internal incident-tracking system, safety-monitoring platforms, inventory systems, SSO, and any other required integrations.
• Oregon Workday for employee injury reporting
• RLDatix for internal incident reporting
• VelocityEHS for backend safety and injury record management
• VelocityEHS Chemical Management for
SDS and chemical inventory management
• Humantech Office Ergonomics
3 Section 2.4.2.2, System Integration (p.
9):
Please name the current internal incident tracking system(s). Is the Agency's intent for the new solution to replace that system, integrate with it on an ongoing basis, or migrate its historical data?
OSH intends to retain RLDatix and Workday for their reporting functions. If a new EHS platform is selected, it would replace the backend functions currently performed by VelocityEHS, and applicable historical data would be migrated. OSH also anticipates ongoing data exchange with RLDatix and Workday, with integration methods and scope to be finalized during implementation planning.
4 Migration Please identify each legacy source to be migrated and provide estimated record counts, date ranges, attachment volumes, file formats, retention requirements, and the parties responsible for extraction, cleansing, validation, and reconciliation.
VelocityEHS is the primary migration source, covering approximately 10 years of incident, injury, OSHA, assault, inspection/audit, observation, corrective action, task, chemical inventory, and ergonomics data. Record counts, attachment volumes, export formats, supplemental sources, and retention requirements will be confirmed during planning. OSH will manage data extraction and provide SMEs for data quality and validation. The contractor will support data mapping, cleansing, migration, and reconciliation, including verification of record counts, field accuracy, and attachment completeness. Final responsibilities and acceptance criteria will be established jointly during implementation
6 Section 2.4.2.2 and Section 2.4.3.5, Training Management
(pp. 9-10):
Which Oregon Workday modules are in use at OSH, including whether Workday Learning is used for training assignments or tracking?
Which way is data expected to flow (into the EHS solution, out of it, or both)?
OSH uses the Learning module to track employee training and the Safety Incident module to report work related injuries. The Safety Department has Safety Partner access to manage and follow up on those reports.
7 Scope of Work and Specifications
How is OSH currently collecting EHS information? (Page 7, Section 2.3.2, Purpose, and Pages 8-11, Section 2.4, Scope of Work/Specifications)
OSH uses the Learning module to track employee training and the Safety Incident module to report work related injuries. The Safety Department has Safety Partner access to manage and follow up on those reports.
8 Section 3.3.3, Price Proposal
(p. 15): pricing structure.
(a) The initial term is 10 years, but maintenance and support pricing is requested for up to 4 years. What pricing period should proposers use for subscription and support? (b) For a subscription (SaaS) solution, will the Agency accept a role-based rate card for implementation services in place of named-individual salary and fringe rates? (c) Please confirm that the equipment, supplies and warranty line items may be marked "not applicable" for a cloud subscription. **This
The Addendum updates the term ask and provides an updated and more comprehensive Exhibit E.
includes all inquiries related to the previously stated "Initial term of 10 years..."**
9 Commercial and Contract Terms
Section 1.1: The initial term is anticipated at 10 years, renewable to 15. Should pricing be held firm across the full term, or are annual escalations permitted (e.g., CPI or a fixed cap)?
Section 1.1 (Term) will be revised through an addendum to the RFP
10 Commercial and Contract Terms
Attachment E (Price Proposal) references equipment, supplies, warranty, and preventative maintenance, which read as hardware-oriented. For a cloud-based SaaS solution, how would the Agency like subscription, implementation, and support costs mapped onto the Price Proposal Form?
Answered in row 7
11 Commercial and Contract Terms
Section 3.3.3: The Price Proposal requires listing the name, title, salary/wage, and fringe rate for each individual performing the Work.
For a SaaS subscription where staffing is not billed hourly, please clarify the level of personnel-cost detail expected.
The proposed pricing must be comprehensive and inclusive of all activities, tasks, deliverables, and personnel identified in the Offeror’s proposal. Pricing shall reflect the full cost of performing the scope of work as described, including labor, materials, subcontractor services, project management, administrative support, and any other resources necessary to successfully complete the project. Offerors must ensure that all associated expenses are clearly detailed and accounted for, with no additional or hidden costs beyond those submitted in the pricing proposal. Section 3.3.3 will be revised through an addendum to the RFP.
12 Section 3.1.5, Other Requirements (p.
12):
For the minimum qualification of a proven track record implementing EHS software for organizations of similar size and complexity, please describe how the Agency will judge "similar." Will implementations covering a
Please follow the guidelines provided (as in section 2.4.3 per example), and using your professional judgement, submit your response based on your experience implementing EHS solutions for a large-scale subset of the functional areas in Section 2.4.3 (for example, incident management, safety inspections and corrective action tracking) at hospitals, health systems or public agencies satisfy this requirement?
enterprise needing a solution requiring scalability and interoperability with existing systems.
13 Section 3.3.2, References (p.
15).
Can a single reference cover multiple functional areas or sites? May reference forms (Attachment D) be sent by the reference directly to the SPC if they aren't received before Opening?
Use your professional judgement in providing references that will help OSH evaluate previous deployments of similar systems.
OSH prefers that all references be submitted with the RFP response. If all references cannot be included at that time, please indicate in your response who will submit the remaining references to SPC no later one week after closing.
14 Qualifications The RFP lists an "Executive Summary," "Administrative Proposal," and "Technical Proposal” as required elements but does not define their expected content. Please clarify the intended content of each and confirm whether the Project Implementation Plan and Emergency Downtime Plan should be placed within the Technical Proposal or submitted as standalone sections. (Pages 12-13, Section 3.2.1, Proposal Submissions)
Please use your professional judgment in structuring the Executive Summary, Administrative Proposal, and Technical Proposal.
15 Qualifications Where one entity is the Proposer and prime contractor and another entity is the identified EHS SaaS solution provider and implementation subcontractor, please confirm that the Proposer may demonstrate compliance with the applicable Section 3.1 Minimum Qualifications through the subcontractor's qualifications, experience, In response to the question regarding whether a Proposer may rely on the qualifications of an identified EHS SaaS solution provider and implementation subcontractor to meet the Minimum Qualifications, OSH requests the Proposer provides an overview explaining how the subcontractor’s system and qualifications satisfy the applicable requirements. OSH is not certifications, personnel, references, and capabilities (Pages 11–12, Section 3.1, Minimum Qualifications, specifically Sections 3.1.1–3.1.5).
accepting demonstrations at this stage of the process.
16 Section 2.4.3.6, Regulatory Compliance (p.
10).
Should OSHA 300/300A/301 records and healthcare assault logs be kept separately for each campus (each as its own establishment) or combined? Please also confirm which assault log format(s) apply, for example the reporting required under ORS 654.412-654.423.
OSHA 300/300A/301 records and healthcare assault logs should be maintained separately for the Salem and Junction City campuses, with each campus treated as its own establishment. The platform should also support consolidated reporting for hospital-wide analysis.
The applicable assault log is the Oregon OSHA Health Care Assault Log required under OAR 437-001-0706 and ORS 654.412–654.423, or an equivalent electronic log containing all required information. The platform should generate campus-specific logs and support export to Excel and PDF.
17 Section 2.4.2.4, Deployment & Implementation
(p. 9): data migration.
Please describe the historical data to be migrated: record types, approximate volumes, date range and current format.
Historical data is maintained in VelocityEHS and spans approximately 10 years, depending on record type. Records include incident and injury records, OSHA recordkeeping data, healthcare assault logs, inspections/audits, observations, corrective actions, task tracking, chemical inventory, and ergonomics records, along with associated attachments and supporting documentation.
Approximate record volumes will be confirmed during migration planning. Data will be provided through available VelocityEHS exports; export formats and attachment transfer methods will need to be validated.
18 Section 2.4.3.4, Chemical Management (p.
10).
Does OSH currently hold an SDS library subscription or chemical inventory system that the solution should integrate with or migrate from? About how many chemical products and storage locations are in scope?
OSH currently uses the VelocityEHS Chemical Management platform for SDS library and chemical inventory management, covering approximately 70 storage locations and 4,000 inventory items across the Salem and Junction City campuses.
OSH is open to either retaining the existing Chemical Management platform or transitioning to the selected solution, depending on functionality, cost, migration requirements, and operational impact.
Proposers should describe their capabilities for both integration with the existing platform and migration of chemical inventory data and associated SDS records.
19 Exhibit I, Requirements (p.
86) and Exhibit F, Subscription Terms (p. 83).
Exhibit I currently says "Requirements will be included here." Will Exhibit I be issued by Amendment? If so, will the Opening date be extended so proposers can respond to it? For Exhibit F, should proposers submit their standard subscription terms for negotiation?
Please note, Attachment A is for reference and will be further negotiated with the selected Proposer. For Exhibit I: these requirements will be discussed with the winning Proposer, as this relates to the requirements with the winning Proposer has/needs to integrate the solution. Exhibit F also will be negotiated with the winning Proposer.
20 Page 86, Attachment A, Exhibit I
What are the requirements in Exhibit I? Please note, Attachment A is for reference and will be further negotiated with the winning Proposer. Exhibit I: and Exhibit F will also be reviewed with the selected proposer, as their requirements relate to integration needs for the chosen solution.
21 Scope and requirements
Section 2.3.1 / 2.4: Does OSH currently use an EHS software platform? If so, which system, and what are the primary drivers for replacement?
Yes. OSH currently uses VelocityEHS. OSH is conducting this procurement to meet public contracting requirements and to evaluate available solutions against its operational and regulatory needs. Participation in this process does not necessarily indicate that the current platform will be replaced. This procurement is being conducted in accordance with OAR137-
047-0255 & OAR279B.055
22 Scope and requirements
Section 2.4.4: Do a meaningful number of staff lack a corporate email address or device, such that kiosk or no-login mobile reporting would be required?
Yes. This is required due to internet limitations. OSH also prefers an app-based system (see Section 2.4.4).
23 Integration Sections 2.4.2.2 and 2.4.3: For the required integrations with Oregon Workday and OSH's internal incident system(s), what integration depth is expected at go-live (e.g., HR/employee data import, incident data exchange), and what technical standards or APIs apply to each?
Full integration is required at Go-Live, unless the proposed solution is a phased approach.
24 Data Security and Residency (Exhibit J)
Exhibit J, Section 1.2.1: Is compliance with NIST SP 800-53 "Moderate," SOC 2 Type II, and ISO 27001 sufficient, or does the Agency require FedRAMP or StateRAMP authorization for the hosted solution?
FedRAMP or StateRAMP/GovRAMP authorization is one acceptable way to demonstrate compliance with the State's security requirements. However, these authorizations are not required if the vendor can otherwise demonstrate compliance with the applicable NIST SP 800-53 controls. While certifications such as SOC 2 Type II and ISO 27001 may help demonstrate the maturity of a vendor's security program, vendors should be prepared to show how their controls align with the relevant NIST SP 800-53 requirements.
25 Data Security and Residency (Exhibit J)
Exhibit J, Sections 2.4 and 4.1 require that Agency Data not be accessed from, stored, or transmitted outside the United States, including for support, maintenance, disaster recovery, and backup. Please confirm whether
Oregon State policy is to store and access data from domestic locations only. Approvals for non-domestic storage and access are on a case-by-case basis, and approval(s) are not guaranteed.
vendor technical support or administrative access provided from Canada would be permitted, or whether all such access must originate within the United States.
26 Page 9, Section 2.4.2.2, System Integration
What are the enterprise systems to integrate with? Workday, RL Datix, Velocity
27 System Integration
What is the safety monitoring platforms and inventory tracking systems already in-place (i.e.
existing legacy systems) that OSH would like to replace? (Page 9, Section 2.4.2.2, System Integration, second bullet)
Velocity/VHS nonexempt
28 System Integration
What is the hospital's internal incident tracking system? (Page 9, Section 2.4.2.2, System Integration, third and fourth bullets)
Incidents-RL Datix Ensure. Incidents in Workday. Injury in Velocity. compatibility with existing OSH systems, including Oregon Workday for employee data and the hospital’s internal incident tracking system.
29 4. Section 2.4.3, Functional Requirements
(pp. 9-11):
About how many users do you expect in each category below, across the Salem and Junction City campuses? (a) Administrators (b) Safety/EHS staff who manage records (c) General staff who submit reports or complete assigned items
It is anticipated that their will be 3 Administrators, approximately 17 staff members managing records, and approximately 2500 staff members who either submit reports, or complete the assigned items.
30 Users/Licensing Please provide the anticipated number of total employees, named users, occasional reporters, administrators, concurrent users, and mobile/offline users, and confirm whether the State prefers enterprise, named-user, concurrent-user, or another licensing structure.
This is dependent upon Proposer's system functionality.
File details come from the government source that posted it. Updated .