ehs is second generation - c2e2.org part presentation i. 1st gege e at oneration ehs‐is issues...
TRANSCRIPT
EHS‐ISSecond GenerationSecond Generation
C2E2C2E2EH&S Campus Technology WorkshopUniversity of Massachusetts Amherst
April 14th 2011April 14th, 2011
PresenterJohn Dahlstrom, Chief Technical Lead
Yale University EHS ‐ [email protected]
Co‐PresenterDes Nolan PresidentDes Nolan, President
ABC Systems, Inc. ‐ [email protected]
4 Part Presentation4 Part Presentation
I. 1st Generation EHS‐IS Issues and Visualizing/ . Ge e at o S S ssues a d sua g/Finding a 2nd Generation Solution (EHS Integrator)
hII. EHS Integrator Screenshots – An Overview
III. Survey/Inspection and the Find‐And‐Fix process
IV. Software Engineering Principals Applied To Building EHS Integrator
Part I
1st Generation EHS‐IS Issues
and aand a
2nd Generation Solution
1st Generation EHS‐ISl l d d l lMultiple Individual 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 timey y
• Customers expectations aren’t being met:– Want to know why your systems are in the stone age– Want to know why your systems are in the stone age
– Why can’t they go to one place to enter all their data
• The next slide illustrates current challenges• The next slide illustrates current challenges
Visualizing A Solution2nd G ti EHS IS2nd Generation EHS‐IS
A i l i d i h A S i• A single integrated system with Area Suites– EnvironmentalOccupational– Occupational
– Research Safety
• A system that providesA system that provides– One place to maintain data– One‐stop‐shopping for all customersp pp g– An easy means to add new modules for new needs– Ability to release new features to all applications
Plus Advanced Features• System‐wide metrics
M lti l l tf Wi d b bil• Multiple platform: Windows, web, mobile
• Easy deployment over the internet/intranet
• Can be run remotely over the internet
Solution Paths Explored lBy Yale EHS
• University IT was to do as part of YaleNext projectUniversity IT was to do as part of YaleNext project– YaleNext = Effort to rewrite many university systems
– Six months of documenting EHS “as‐is” and “to‐be”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 YaleNext workEHS eventually designated as non priority YaleNext work
– YaleNext project wound‐up due to state of economy
• Request‐for‐Info doc built from YaleNext workRequest for Info doc built from YaleNext work– 30 page doc detailing high level requirements
– Sent to 16 vendors seeking a responseSent to 16 vendors seeking a response
Commercial VendorsCommercial Vendors• Nine responders
h l f f l k– BioRAFT, Chemical Safety Software, Click Commerce, InfoEd, Intelex, Key Solutions, Onsite Systems, Quantum Compliance Systems, Sivco, Woodard & p y , ,Curran
• Seven non‐responders– 3E, EH&E, Enviance, ESP, ESS, Image Wave ProcessMap,
• Their reported features were rated by function• Their reported features were rated by function– Authorizations, Dashboard, Inventory, Inspections, Mobility, PI Profile, Waste, Integratability, etc.y, , , g y,
Final AssessmentFinal Assessment
• No single solution was found to beNo single solution was found to be comprehensive enough for Yale EHS
• Buying multiple new products offered Yale EHS d h iEHS no advantages over their current systems
• No promising solution appeared to be under development that was worth waiting forp g
Then, A Solution Emerged“ ll b i h l i id ”“Collaborate With A 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 , p gsolution
– After exploring the alternatives, Yale EHS decided to collaborate with ABC Systems, Inc. to get their ultimate y , gsolution
• EHS Integrator is the product of this collaboration– Its under active development at Yale University ‐ 50% doneIts under active development at Yale University 50% done– Technical lead is being provided by ABC Systems, Inc.– EHS Domain experts being provided by Yale EHSOth Y l N EHS li it id i i it– Other Yale Non‐EHS compliance units are considering using it
– Current design, positions it to be re‐used by other universities
EHS Integrator Status
AREA SUITES APPLICATIONS (MODULES)
Research Safety* Activity RegistrationInspectionsInventory TrackingLab SignageLab SignageRadiation PET Registration
Environmental Biomedical WasteRadiation Waste**
Occupational Worker Safety (OSHA 300 plus)Business Continuity**
ALL AREAS Core University Data(re‐usable functionality)
yCore Principal ProfileConstruction/Renovation Project TrackingDashboard (Data Metrics)Incident Reporting**Incident Reporting**Safety and Compliance CalendarTraining Management and Exposure Tracking**
EHS‐IS In TransitionEHS IS In Transition
A DB d i ifi d t• Access DBs now manage domain specific data
• EHS Integrator– Manages consolidated data
– Is target for all brand new modules
– Is target for replacement modules for Access DBs
• EHS Integrator / Access Applications Linkedg / pp– Business rules respected both application types
EHS Integrator Consolidates Data• Redundantly managed data from 15 Access DBs
C U i it D t• Core University Data– 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,
Part IIPart II
EHS IntegratorEHS Integrator ScreenshotsScreenshots ‐An Overview
Workspace & access to all applicationsWorkspace & access to all applications
EHS Integrator Applicationsg pp(Others Exist: Business Continuity, Incidents, Safety & Compliance Calendar, Worker Safety)
Core University Data ‐ FormsCore University Data Forms
Core University Data ‐ LookupsCore University Data Lookups
Area/Lab Safety – reuses core dataArea/Lab Safety reuses core data
Principal Profile –d f b h lreuses data from both applications
Principal list query form h blhas customizable views
Principal list query form h ffwith Type, Staff, Areas, & Activity
Principal list form reports/exportsPrincipal list form reports/exports
Principal list reporth b l fwith same basic options as list form
Principal list report h ffwith Type, Staff, Areas, & Activity
Principal list form h f lwith Activity Type filtering
Principal Profile detail formith A ti iti W k A C t t d A i t twith Activities, Work Areas, Contacts and Assistants
Part IIIPart III
S /I tiSurvey/Inspection
d thand the
Fi d A d FiFind‐And‐Fix
process
Step 1: Add issue to new surveyStep 1: Add issue to new survey
Step 2: PI gets email noticeStep 2: PI gets email notice
Step 3: PI/Lab Super. logs onto webStep 3: PI/Lab Super. logs onto web
Step 4: PI/Lab Supervisor sees issueStep 4: PI/Lab Supervisor sees issue
Step 5: PI/Lab Supervisor respondsStep 5: PI/Lab Supervisor responds
Step 6: EHS Manager gets email noticeStep 6: EHS Manager gets email notice
Step 7: EHS Manager reviews responseStep 7: EHS Manager reviews response
Step 8: Survey is completed / closedStep 8: Survey is completed / closed
Part IV
Software Engineering PrincipalsSoftware Engineering PrincipalsApplied To Building EHS Integrator
(An Adaptable System)(An Adaptable System)
Accessible And Well DocumentedAccessible And Well Documented
A ibl P bli f k th t ff• Accessible: Public open framework that offers– Templates for smart mobile business components
– With built‐in validation authorization & business logic– With built‐in validation, authorization & business logic
– Compiled solutions are web deployable/executable
• Well Documented– Framework has 850 page book & public support formsp g p pp
– ABC Systems, Inc. has a 100 page manifesto providing• Technical overview of how to organize system
S d d h i 50% f ll d b d• Standards that permit 50% of all code to be generated
Best Software PracticesBest Software Practices
• Coding standards– Permits code generation of raw code– Makes maintenance and evolution easier– Reduces effort to port (whenever such is needed)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 modulesModules can be assembled into Area Suites– Modules can be assembled into Area Suites
– Area Suites can be brought together to form entire systems
Built Usingd lModern 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 elementsg p
– Flesh‐out pragmatic details via a series of use cases
– Build with best software practices for easy enhancing
Layered Software ArchitectureLayered Software Architecture
/ /• Forms (Windows/Web/Mobile)
• Business Components (business logic)
D t A /St•Data Access/Storage
Area Suites formed fromformed from
Modules
Laboratory Safety Suite
Registration
ModuleTraining Module
Inspection
ModuleInventory Module
EHS System formed fromformed from
Area Suites
EHS System
Environmental
Suite
Occupational
SuiteLaboratory Safety SuitsSuite Suite y