WCM - Operational Switching
WCM - Operational Switching
WCM - Operational Switching
A collaboration of:
SAP at DWR
WCM at DWR
Questions
Slide 4
ELECTRICAL Hazards
WATER Hazards
WCM at DWR
What were the issues?
2006 Replacement of homegrown Mapper database
OP2 = WCM LOGGING = ?
Safety Concerns
Scared of SAP
Different Terminology
OTHER
WCM at DWR
What we did/didnt do in 2006:
Old System:
Approvals = Mapper
Switching = Excel
Logging = Mapper
New System:
Approvals = WCAs
Sign on/off = WCDs
Switching = Excel
Logging = Z Programs
Icon connections
Multi or Single line
ALV Functionality
Traffic Light Status
Slide 9
WCA:
Simple Screens
Permit Process for
Approval
Full history
Workflows/e-mails
DWR added links to
other Z Programs
Slide 10
WCD:
Simple Screens
Permit Process for
Worker Sign On/Off
Full history
Workflows/e-mails
Slide 12
WCM at DWR
Customized Reports and Print Forms
Adobe used for
all printed forms
Custom Report to
overcome SAP
date range and
status issues
Slide 13
Logging at DWR
Unit Status
Logging
tracks complete
unit history
Links to post
automatically in
Ops Log.
General log
entries occur all
day
Slide 14
Operational Log
Midnight Reporting from SAP
Portal/Adobe Interactive Forms
All Unit Status Entries
All Operational Log Entries
List of Active Clearances (WCDs)
List of Current Unit Statuses
WCAs and WCDs
Operations staff GUI mapped to
client with no time out
This is our LEGAL document
Slide 15
Stage 1
Stage 2
Stage 3
Stage 4
Stage 5
Stage 6
Slide 16
Master Data
WCM uses Structural Lists
All equipment used for switching must
be listed and unique
Equipment master data needs to be
linked to special classification
Equipment must be mapped in
Configuration to Operational Class and
possible conditions (e.g. Open/Closed,
On/Off). WCC8
Slide 17
Slide 18
Pump B Repair
Valve X
Slide 19
Slide 20
Placement/Removal Forms
Used to perform
switching/sign on/off
Color coordinated
Carries over long
text based on
triggers
Kept at ACC
Mobile Devices will
be used in future!
.
Slide 21
Slide 23
Key Points
o Since October less than 5 issues with system statewide (all user error)
and no Operational near miss or miss issues due to switching!
oWCM Can be implemented in stages and/or Plant by Plant
oPlants can be configured differently
oSystem can be customized lots of user exits
oProject relies on master data Dev/QA must be refreshed from Prod
oMust be tested extensively in development
Slide 24
Key Points
oMaster Data needs to be updated in Production before testing in Dev
oMaster data has to be mapped in SPRO separately in each client
oTerminology is learned in a few days
o2 Day Training Sessions with 6 month access to sandbox
Slide 25
QUESTIONS
Slide 26
Wendy Underhill
State of California Department of Water Resources
[email protected]
A collaboration of: