Even though we say this will be unique for each customer, we do also outline some possible general approaches below to give you some reference points for thinking about the matter. In all we discuss: 1) a full blown roll-out, 2) a vertical stack for a given safety program, and separately a focus on initially launching either 3) inspection or 4) inspection/ compliance functionality. Besides the narrative given below, you can also look at the Adoption Matrix to see a summary list of suitable components for each approach.
Sidebar: Custom Configuration / Settings
EHSIntegrator has configurable options at many levels so it can be tailored to your needs, regardless, of whether you are following a custom or general adoption approach.
- System User Roles can be set to only show desired modules or components.
- Or assigned to specific users to control what they can see or edit.
- Particular activities can be matched to people/places to set compliance requirements.
- Many entities have type data tables with a different options.
- New types can be defined for many entities to influence system behaviors.
- All query screens have many options you can set to get custom views/results.
- The global config table has 100+ parameters that can be used to tweak processes.
- The platform’s open architecture allows it be easily interfaced with other systems.
General Adoption Strategies (that you can also customize)The three suggested General Adoption Strategies are described very briefly in separate sections below. For additional information you can click on the Matrix link at the bottom of the page to see a table of all possible module/sub-component options for each strategy, or you can click on the following link to get a single document that consolidates all adoption spec sheets, which contain some additional information: [More details (PDF)]
2) Vertical Stack
The "Vertical Stack" adoption strategy assumes you may want to roll-out a vertical stack of EHSIntegrator functionality to just one major EHS Safety Program permanently, or just initially before other EHS sections of the department get the same.
For example we have a client that has a department that does nothing by Radiation and because of the systems configurability they are able to see a version of the system that appears to do nothing but service the Radiation Safety Program's needs. Also see the sample presentation "Vertical Stack - Biological Safety" for a description of the benefits of using the system for Biological Safety.
3) EHS Inspector
4) EHS Compliance
The core Principal Profile module can be used to identify which labs need to be inspected and what in them needs to be examined. The system will help to ensure any observed issues are tracked from initial identification through final resolution by the parties to which they are assigned.
Training requirements and current compliance can be identified by relating data for Assistants from the core Principal Profile and Training modules and cross-referencing that with data linked between the Exposure and Training modules.