NTTA
- Implementation team made up of business and IT
- Purchased in 12/10, Phase 2/10, plan to go live in 7/10. Our goal is purchased 1/10, Pilot 6/10 & go live 9/10
- Uses Sharepoint to for content management. Sharepoint appears to be very popular among proliance users.
- Use ISO 9001 process for continual improvement and user satisfaction. Plan -- Do -- Check -- Act -- http://www.iso.org
- Uses Cognos 8.3 for reporting. We have an issue with using a third party reporting tool in a hosted environment. We are in process of moving away from Cognos to SQL Reporting Services.
- Performance metrics are used - e.g. turnaround time on submittals, RFI's
- Design metrics to support objectives and be actionable to drive behavior
- Keep documentation simple - flow charts work well
- Uses ITIL Version 3 on implementation - http://itsm.fwtk.org/v3.htm
- Look to have a Proliance SME at each key location
- They did a timeline on their implementation - Weston should do same.
Simon
- Continual education is key
- Just in time learning
- Usually do it early in morning for 90 minutes max
- 180 projects use it
- Integrate with JD Edwards, their ERP
- Uses Excel for entry to support use
- Focus training on only what users need to know
- Real goal is YAC - Yards after Catch - basically how much users can do with training after receiving it
- Boot camp for new hires
- Views are powerful way to get users data
- Quick reference guides developed and popular
Other points I heard... Nothing in this session was new, but served as a refreshing reminder.
ReplyDeleteNTTA:
- Make sure you prioritize what needs to be done. (must have vs. nice to have).
- Documentation should scale with the size and scope of the project.
- Differentiate between process issues and technical (application) issues.
Simon Group:
- In training give an overview, but emphasize what the audience needs to know. Give hands-on relevant examples.
- When do people learn? When they want to!
- Plan on refresher training.
- Training will likely be requested by users over time
- Be patient and supportive. Learning and efficient use is not a sprint!
Also...
ReplyDelete- Process Ownership and agreed-to flowchart documentation of the process is key to adapting tools to business processes
- Process Flowcharts capture inputs, transformation (review and approvals), and outputs
-Process Flowcharts are turned into Application Tool Technical Flowcharts which diagram how the tool is integrated into the business process, and shows:
o Process Flow
o Roles
o Other required Inputs/Actions
o EPDMS workflow actions
o Notifications
- Another key to impementation is to be sure you train people on concepts to be sure they can customize their ability to easily "see" information in the system and find what they are looking for, including:
o Custom views
o ACR views
o Floating Column Headers
o Teach them to be a "Master of their computer" - this system does not limit their ability to customize the ability to filter, view, or search anything they have rights to access
o