EHS IS. EH&S Campus Technology Workshop University of Massachusetts Amherst April 14 th, 2011

Transcription

1 EHS IS Second Generation C2E2 EH&S Campus Technology Workshop University of Massachusetts Amherst April 14 th, 2011 Presenter John Dahlstrom, Chief Technical Lead Yale University EHS Co Presenter Des Nolan, President ABC Systems, Inc.

2 4 Part Presentation I. 1 st Generation e EHS IS S Issues and Visualizing/ Finding a 2nd Generation Solution (EHS Integrator) II. EHS Integrator Screenshots An Overview III. Survey/Inspection and the Find And Fix process IV. Software Engineering Principals Applied To Building EHS Integrator

3 Part I 1 st Generation EHS IS Issues and a 2nd Generation Solution

4 1 st Generation EHS IS Multiple l Individual d System Silos Some major issues with silo systems are Extra effort to maintain and use redundant data Takes more time to repeatedly develop features Features can only be introduced to a system at a time Customers expectations aren t being met: Want to know why your systems are in the stone age Why can t they go to one place to enter all their data Thenextslideillustratescurrent illustrates challenges

5

6

7 Visualizing A Solution 2 nd Generation EHS IS A single integrated system with iharea Suites Environmental Occupational Research Safety A system that provides One place to maintain data One stop shopping pp for all customers An easy means to add new modules for new needs Ability to release new features to all applications

8 Plus Advanced Features System wide metrics Multiple l platform: ltf Windows, web, mobile Easy deployment over the internet/intranet Can be run remotely over the internet

9 Solution Paths Explored By Yale EHS University IT was to do as partof YaleNext project YaleNext = Effort to rewrite many university systems Six months of documenting EHS as is and to be Various name and re orgs changes for YaleNext project EHS eventually designated as non priority YaleNextwork YaleNext project wound up due to state of economy Request for Info doc built from YaleNext work 30 page doc detailing high level requirements Sent to 16 vendors seeking a response

10 Nine responders Commercial Vendors BioRAFT, Chemical Safety Software, Click Commerce, InfoEd, Intelex, Key Solutions, Onsite Systems, Quantum Compliance Systems, Sivco, Woodard & Curran Seven non responders 3E, EH&E, Enviance, ESP, ESS, Image Wave ProcessMap, Theirreported reported features were rated by function Authorizations, Dashboard, Inventory, Inspections, Mobility, PI Profile, Waste, Integratability, etc.

11 Final Assessment No single solution was found to be comprehensive enough for Yale EHS Buying multiple new products offered Yale EHS no advantages over their current systems No promising solution appeared to be under development that was worth waiting for

12 Then, A Solution Emerged Collaborate With iha Solution Provider ABC Systems, Inc. the chosen software solution provider Was working on an open adaptable EHS solution Yale EHS used a couple of ABC s modules to solve immediate needs, with the intention of replacing them with their final solution After exploring the alternatives, Yale EHS decided to collaborate with ABC Systems, Inc. to get their ultimate solution EHS Integrator is the product of this collaboration Itsunder active development at Yale University 50% done Technical lead is being provided by ABC Systems, Inc. EHS Domain experts being provided by Yale EHS Other Yl Yale Non EHS compliance units are considering i using it Current design, positions it to be re used by other universities

13

14 EHS Integrator Status AREA SUITES Research Safety* Environmental Occupational ALL AREAS (re usable functionality) APPLICATIONS (MODULES) Activity Registration Inspections Inventory Tracking Lab Signage Radiation PET Registration Biomedical Waste Radiation Waste** Worker Safety (OSHA 300 plus) Business Continuity** Core University Data Core Principal Profile Construction/Renovation Project Tracking Dashboard (Data Metrics) Incident Reporting** Safety and Compliance Calendar Training Management and Exposure Tracking**

15 EHS IS In Transition Access DBs now manage domain specific data dt EHS Integrator Manages consolidated data Is target for all brand new modules Is target for replacement modules for Access DBs EHS Integrator / Access Applications Linked Business rules respected both application types

16 EHS Integrator Consolidates Data Redundantly managed data from 15 Access DBs Core University it Data Dt Buildings reduced from 1,054 to 541 names Rooms reduced from 8,726 to 6,378 rooms 300,000 building / room references repointed Core Principal Profile Principal Investigators Their labs, research assistants, lab supervisors Activities for PIs, their labs and assistants

17 Part II EHS Integrator Screenshots An Overview

18 Workspace & access to all applications

19 EHS Integrator Applications g pp (Others Exist: Business Continuity, Incidents, Safety & Compliance Calendar, Worker Safety)

20 Core University Data Forms

21 Core University Data Lookups

22 Area/Lab Safety reuses core data

23 Principal Profile reuses data from both applications

24 Principal list query form has customizable views

25 Principal list query form with Type, Staff, Areas, & Activity

26 Principal list form reports/exports

27 Principal list report with same basic options as list form

28 Principal list report with Type, Staff, Areas, & Activity

29 Principal list form with Activity Type fl filtering

30 Principal Profile detail form with Activities, Atiiti Work kareas, Contacts t and Assistants t

31 Part III Survey/Inspection and the Find And Fix d process

32 Step 1: Add issue to new survey

33 Step 2: PI gets notice

34 Step 3: PI/Lab Super. logs onto web

35 Step 4: PI/Lab Supervisor sees issue

36 Step 5: PI/Lab Supervisor responds

37 Step 6: EHS Manager gets notice

38 Step 7: EHS Manager reviews response

39 Step 8: Survey is completed / closed

40 Part IV Software Engineering Principals Applied To Building EHS Integrator (An Adaptable System)

41 Accessible And Well Documented Accessible: Public open framework kthat t offers Templates for smart mobile business components With built in validation, authorization & business logic Compiled solutions are web deployable/executable Well Documented Framework has 850 page pg book & public support forms ABC Systems, Inc. has a 100 page manifesto providing Technical overview of how to organize system Standards d that permit 50% of all code to be generated

42 Best Software Practices Coding standards Permits code generation of raw code Makes maintenance and evolution easier Reduces effort to port, (whenever such is needed) Loosely coupled software architecture Technical concerns separated into layers Functional items into modules Composition focused Robust re usable components can be formed into modules Modules can be assembled into Area Suites Area Suites can be brought together to form entire systems

43 Built Using Modern Development Processes Agile iterative development for better solution fit Use EHS functional/technology domain experts Evolve over each cycle with regular course corrections Fit validated via regular releases of working software Develop highly reusable components Use modeling experts to create re usable elements Flesh out pragmatic details via a series of use cases Build with best software practices for easy enhancing

44 Layered Software Architecture Forms (Windows/Web/Mobile) / Business Components (business logic) Dt Data Access/Storage

45 Area Suites formed from Modules Laboratory Safety Suite Registration Module Training Module Inspection Module Inventory Module

46 EHS System formed from Area Suites EHS System Environmental Occupational Laboratory Suite Suite Safety Suits