|
Blogs
My colleagues and I have almost daily conversations on a key topic: what should be the scope of a system, and what instead should be left to pen-and-pencil (or even Excel-based) methods? Here is our train of thought - would love to hear your views on it!
Systems often do not compete with other systems vendors, and instead the jostle with: a) people walking around with cookbooks (e.g. "the top 10 things to ensure your plant is safe") b) people with spreadsheets doing 80/20 jobs once a year (e.g. collecting all "high-absence" employees IDs and comparing them with the healthiness of the buildings they are in, to determine if there is a case for buildings refurbishment) c) pure training and behavior change initiatives (e.g. "what you gotta to do to save energy).
To recap - what we think being the watershed for system-based management as opposed to the above methods:
This applies to a number of situations - from energy and carbon, to environmental health and safety, to supply chain, to product management, to human resources. Gianni Giacomelli Gianni is head of strategy for sustainability at SAP.
| |||||||||||||||||||||||