TxM 013 Section 1.11 What is different about the JAR&A ERP Implementation approach Created by James on 6/26/2013 5:20:34 PM
Following is an analysis of what is different about the JAR&A approach to ERP implementation.
The goal of this approach is a MUCH higher quality outcome for the same or less total cost to exceptionally high standards. Long term operating benefits are exponentially greater than traditional techniques and system operating costs are considerably lower.
1. Engineered solution
Critical factors engineering approach (model the real world) – Architect–Consulting Engineer model from building construction industry – high level of thought leadership and accountability – design for success by engineering against failure – engineers design bridges NOT to fall down.
2. Top down strategic executive approach
Executive level strategic view – essence of the business and how it thrives – driven top-down – high level of business engagement, education, involvement, organization wide, management of change, focus on decision support.
3. Precision configuration
Precision engineered strategic configuration to unique standards developed by JAR&A built on precision taxonomies – far superior to anything I have seen elsewhere.
4. Configuration management software
Use of rule based software to help with configuration and maintenance of taxonomies and configuration and to assist with on-going management of the operation of the ERP and Data Warehouse as precision machines.
5. Maximize use of permanent staff
Use of high quality temporary staff to free up permanent staff to do everything possible on the project. Limit use of contractors, use high value consultants only.
Rigorous laboratory approach – representative data samples, extreme value cases, break it till it will not break anymore, test alternative configuration scenarios, document, CBT, train, develop reports, establish data warehouse BEFORE going live.
7. Cubic business model
Scalable cubic business model to model the entire enterprise flexibly with the ability to report flexibly for Governance and management purposes – flows through into a governance and reporting philosophy with high levels of ownership and delegation. Scalable for acquisitions.
8. Decision support, analytics and modelling
Emphasis on facilitating high value decision making rippling through to all aspects of the configuration and implementation and including comprehensive reporting and analytics BEFORE go-live, including data warehouse and business intelligence – REAL BI.
9. High operating standards and training
Comprehensive training, computer based training, education of staff, standards, disciplines, typing, etc BEFORE allowed to use the system.
All the above taken together represent something that I have not seen done elsewhere, I have heard people use language that at some level sounds like this but it is not in practice.
Having said this, I have never had the opportunity to tackle a full scale project end to end in accordance with the above principles and so there is still learning involved but I am confident that the overall outcome will more than warrant the risk.
The comment feature is locked by administrator.