Implementation in Theory & Practice

Slides:



Advertisements
Similar presentations
Implementing a Behavior Based Safety Process at Rockwell Automation
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Ginnie Mae MISMO Adoption Update Tamara Togans and Nicole Jackson Ginnie Mae January 13, 2014 MISMO Winter 2014 Summit The MISMO Winter 2014 Summit Education.
ITIL: Service Transition
Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
1. Failure is when users do not feel they get what they paid for. 2. Failure is when the overall organization fails to adopt the solution.
Systems Analysis and Design Kendall & Kendall Sixth Edition
RIAS PHASE II Oracle General Ledger, Financial Reporting and Data Warehouse 6/27/2015.
Health Informatics Series
System Development Life Cycle (SDLC)
Tim Harris| Western Computer
Design, Implementation and Maintenance
GroupLink’s everything HelpDesk The Novell Integrated Service Desk Que Mangus Marketing Manager
MARCH 2010Developed by Agency Human Resource Services, DHRM1 Organizational Design What Is It? Organizational Design is the creation of roles, processes,
SCC EHR Workshop for Contractors: Implementation Considerations May 25, 2011.
Enterprise Architecture
Kickoff Meeting Jam 11/18/2011 © Copyright All rights reserved.
Charting a course PROCESS.
Privileged and Confidential Strategic Approach to Asset Management Presented to October Urban Water Council Regional Seminar.
Systems Analysis and Design: The Big Picture
How to Manage the Organizational Change LaMarsh & Associates, Inc.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 21 – 9 – 2011 College Of Computer Science and Information, Information Systems.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
Tyson’s Approach to Organizational Change Management
Roles and Responsibilities
N By: Md Rezaul Huda Reza n
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
James A. O'Brien, and George Marakas Management Information Systems, 9 th ed. Boston, MA: McGraw-Hill, Inc., 2009 ISBN: McGraw-Hill/Irwin.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Name Class.  Review of Implementation Process  Identify Critical Success Factors  Define Change Management (big picture)  Define Role of Corporate.
Managed Print Services. MyOffice PrinterServices HardwareSoftwareTonerPartsLabor Consultative Services Level 1 & 2 Help Desk Triage Increase efficiencies.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
1. 2 Business Process Reengineering (BPR) “the fundamental rethinking and redesign of processes to achieve dramatic improvements in critical, contemporary.
BUSINESS PROCESS REENGINEERING & ERP
IT Requirements Management Balancing Needs and Expectations.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
10 Important Criteria for Change Management Success Karen Korb TELUS Health Solutions November 23, 2009.
Systems Analysis and Design
Glen Fields - Final Project Presentation. What Sets CSI Apart... GBA 573 Consultants Company Background Located in San Diego, CA 5 Engineering Consultants.
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
Project Portfolio Management Business Priorities Presentation.
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
Chapter 10 Innovation and Change. Purpose of the Chapter Discuss how organizations change How managers can direct the innovation and change process Discuss.
Are you ready for Evergreen? Is Evergreen ready for you?  Test server  Gap analysis  Gaps: software dependent? Workflow dependent?  Are gaps major.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Sage ERP X3 Standard Edition Methodology
Sage North America Sage ERP X3 Standard Edition|Solution Overview Solution Objectives and Configuration Methodology and Project Quality Plan.
Managing Challenging Projects Presented to the class of: Dr. Jane Mackay M.J. Neely School of Business.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Tyler Implementation Kick-Off Aaron Joyal, PMP Financials Project Manager.
Continual Service Improvement Methods & Techniques.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Patricia Alafaireet  Lecture 2 – Implementation and go-live strategies Data conversion Communication Planning Downtime.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Patricia Alafaireet Patricia E. Alafaireet, PhD Director of Applied Health Informatics University of Missouri-School of Medicine Department of Health.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
NIH Change Management Program Change Management Program Overview March 8,
Anytime, Anywhere Access Benefits Functionality Work Order Administration Dispatch Work Order Work Order Details New Work Order Additional Functionality.
ITIL: Service Transition
Systems Analysis and Design in a Changing World, 4th Edition
Project life span.
System Development Life Cycle (SDLC)
System Development Life Cycle (SDLC)
Description of Revision
Systems Analysis and Design
System Development Life Cycle (SDLC)
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Implementation in Theory & Practice

Implementation The Theory The Practice Remedies The Promises of CMMS The Implementation Process Roles & Responsibilities The Philosophy of CMMS The Practice Costs of Implementation Barriers to Successful Implementation Resistance to Change & Rejection Falling Short of the Goals “Feeding the Monster” Remedies Effective Training Continuing Improvement

Implementation Implementation Defined: The post-sales process of guiding a client from purchase to use of the software they’ve purchased.

Implementation Goals Improved Efficiencies: Key Performance Indicators: Critical equipment availability Mean time between failures (MTBF) Maintenance backlog Equipment downtime Criticality Cost Analysis Trend Analysis Improved Efficiencies: Asset Management Work Management Scheduled Preventative Maintenance Maintenance Cost Tracking Automated & Advanced Reporting Systems Integrations Organizational Communications Process Improvement

Implementation Process Analysis Design Configuration Deployment Operation Knowing what you need to do 5 Stages of Implementation Determine how to do it with new tools Adapting the New Tools This could be a ‘formal’ or ‘informal’ process Adopting the New Tools These could be applied in a phased approach, department-by-department or process-by-process Getting it Done

Knowing what you need to do Implementation Process Analysis Design Configuration Deployment Operation Analysis = Preliminary Knowledge Transfer Sales Transfer to Implementation ‘Diagnostic’ (RFP, sales & purchasing) chore results in a Scope Of Work. Kickoff Meeting on-site: Comprehensive Product Overview Lucity demo Discussion of CMMS Discussion of hardware/network requirements Evaluate current client business processes… the ‘general’ work flow within an organization “Codify” work into Lucity’s Work Flow Setup codes Understand goals of CMMS and needed output – begin with the end in mind Knowing what you need to do Nothing decided here is written in stone

Knowing how to do it with the new tools Implementation Process Analysis Design Configuration Deployment Operation Design = Identifying Means of Managing Process Requirements Design Specifications vs. Existing Tools Auto-Notifications Specialized filter functionality Spring clean-up & other special processes Filters for ‘informal’ work routing Formal Work Routing Custom Integration Design Identify weaknesses in existing client data Keep the end goals and needs in mind Knowing how to do it with the new tools Design process may be formalized or not

Implementation Process Analysis Design Configuration Deployment Operation Configuration = Application of What’s Been Learned Software Installation Data Migration Improve existing data first (if necessary and possible) Convert existing Data – iterative process of re-conversion & review Schedule data load upon final approval Software Configuration Administrative training (Lucity Web, GIS admin, etc.) Configuration by both Implementer & Client Admin(s) Typical chores: Security, Dashboards Configure with end goals in mind Adapting the New Tools The devil is in the details

Implementation Process Analysis Design Configuration Deployment Operation Deployment = Change Management Testing the New System Are we achieving our goals? Tweaking the New System Transition to the New System  Go-Live End-User Training Schedule for Launch Final Data Migration Launch Support Follow-up Training & Ongoing End-User Support Adopting the New Tools “Nothing diminishes anxiety faster than action.” -Walter Anderson

Implementation Process Analysis Design Configuration Deployment Operation Operation = Using of New Tools After Launch Effort Observe & Guide System Usage Provide Users Feedback & Support Capitalize on CMMS: Maintenance Reporting (KPIs) Asset Reporting (Cost Analysis) Process Improvement = Ongoing Analysis Getting it Done “To improve is to change; to be perfect is to change often.” - Churchill

Roles & Responsibilities Implementation Team Implementer & Implementation Support Client Project Manager CMMS Champion Internal Trainer CMMS Administrator IT Administrator GIS Admin (GIS Support) Departmental Representatives (and Subject Matter Experts) Director (or organizational representative)

Implementation Reality NO ‘Typical’ Implementation: Client Variability Goals Roles (Personnel) Moving Targets Clients & Industry Software (best practices) No two clients are the same Various types, sizes Changing industry Changing software = changing best practices

Barriers & Keys to Success “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions - Silos Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions - Silos Public Notifications Scope Creep (changing Goals) Admin Reporting Resource Availability Checking Authorities Reporting Call-Center Implementation & Dispatch Streamlined Year-End Reporting Inventory Management Modelling SCOPE CREEP Everything we CAN do Time Management More Departments Interdepartmental Coordination & Standardization Accountability Reporting Best Management Practices Additional Data Sources

Barriers & Keys to Success Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos “The Devil is in the Details” Communication is Key Example: Trade-Offs in Data Capture: Inspections vs. Work Orders Unrealistic Expectations (falling short of Assumptions) Unrealistic Expectations Every time an Inspection module is adopted, it means one record per asset inspected over and above time tracking in WOs.

Barriers to Success “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos Implementation Roles Lucity Side (Implementer): Project Management Management Consulting Data Conversion System Configuration Integrations Coordinator IT Administrator Trainer Client Side Client Project Manager CMMS Champion Software Administrator IT Administrator GIS Admin (GIS Support) Departmental Representatives (and Subject Matter Experts) Director (or organizational representative) Internal Trainer Costs of Implementation (lacking Resources) Costs – resource requirements ROLES Implementer wears several hats Client-side demands lots of functions, but we cannot control the resources IT Cowboys

Barriers & Keys to Success Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos Resistance to Change: He who rejects change is the architect of decay.  - Harold Wilson If you want to make enemies, try to change something.  - Woodrow Wilson Change Management: It may be hard for an egg to turn into a bird: it would be a jolly sight harder for it to learn to fly while remaining an egg.  - C. S. Lewis Lack of User Buy-In; Fear of Change & Resistance to Change Lack of Buy-In / Resistance to Change Resolution: have a Management representative in the room Empower users that are quick adopters Threaten to walk away

Barriers & Keys to Success Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos Implementation Defined: an Exercise in Putting the Cart Before the Horse Start by understanding your business processes Reconciling Work Management with Real-Life Work Reconciling Work Management with Real-Life Work - Understanding business processes

Barriers & Keys to Success Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos “Approximately 70% of all CMMS implementations fail” - statistic from the internet Scope Creep (changing Goals) Unrealistic Expectations (falling short of Assumptions) Costs of Implementation (lacking Resources) Lack of User Buy-In; Fear of Change & Resistance to Change Reconciling Work Management with Real-Life Work Reconciling Organizational Divisions – Silos IT GIS Fleet CustServ Reconciling Organizational Divisions – Silos Reconciling Divisions – SILOS Lucity is enterprise software One Department vs. Another One plant vs. another Remedy: Top-down and Consistent Management P U B L I C W O R K S

Keys to Success Training & Practice Benefits: User Buy-In & System Adoption User Insight Speed, Time and Money Uniformity of Data-entry Demonstrates Organizational Commitment Means: Demonstrate specific benefits to employees Respond to Push-Back Internally Director’s Backing / Representative Mock Go-Lives = Excellent Pre-Launch Practice Insight: know WHY it’s being done better understanding of not only how to use the CMMS effectively but also why they are using it Well-trained administrators can deploy the CMMS within their maintenance organization quickly, efficiently and effortlessly, just as well-trained maintenance technicians can use the CMMS to its full potential. CMMS users need to be trained on workflow, CMMS administration, report generation, data extraction and data analysis. Otherwise, it will become a daily data-entry exercise where garbage in equals garbage out and eventually the CMMS fails. When considering a CMMS, be sure to inquire about the training options. Most vendors provide onsite or online training. Others offer video tutorials, training workshops or recorded webinars. Keep in mind that training is an ongoing process throughout the lifetime of the CMMS. Send your maintenance team to refresher webinars and knowledge-transfer workshops to help reinforce best practices. During training workshops, attendees may become aware of certain modules and features that could be deployed in their organizations to make their workflow more efficient. Whether you choose free or paid training options, invest in the time upfront to get your employees properly trained, because training makes the difference between CMMS success and failure. Your technicians and maintenance supervisors will be the ones using the CMMS on a daily basis, so they need to know what they are doing from the start. With the proper training, your CMMS can become an invaluable tool to your organization.

Keys to Success Project Elements for Success:  More Implementation! Make knowledge transfer a mantra Consistent support from the top Minimal or Manageable software customization Realistic Project Scope S.M.A.R.T. Goals: Specific Measurable Attainable (Identify responsible party) Realistic Timely A well-managed project & launch plan Clear & realistic data conversion strategies Maximize Project Visibility Maximize User Participation Break Down Silos Leverage it  Ongoing Improvement Make knowledge transfer a mantra Watching things get done isn’t enough… must engage & do setup during the implementation Consistent project support from the top. Director’s representative in the room Minimal software customization. Use the tools at hand Prevents future headaches with support Document whatever IS customized Realistic Scope. x A well-managed project & launch plan Clear data conversion strategies. Strategies were carefully thought out and implemented with a range of solutions from systemic fixes to manual changes. Clean data at go live smoothed the implementation. Reward team players. Front line employees who participated in the project were rewarded through promotions and opportunities to transfer to other departments to broaden their skill sets. Create a sense of community. Two years working long hours, negotiating process design and business requirements broke down silos and forged working relationships that will support the organization for decades to come. IT  More Implementation!

Implementation at Lucity: Looking forward… Project Plans and timelines Standardized Scope Implementation Teams & Specialist Roles Tools to Streamline Implementations “Pre-packaged” Implementations Potential for regular management of SaaS installations