What are the fundamental building blocks of my approach to ERP implementation?
1. Engineering approach is critical
Engineers do NOT design bridges to stand up, they design them NOT to fall down – the principle fundamentally underpins everything that I do – design for success by ENGINEERING AGAINST FAILURE – refer to my book on The Critical Factors for IT Investment Success and other writings
2. Strategic decision support is fundamental
Support for strategic decision support and strategic alignment are foundational – if this requirement is NOT met failure is guaranteed – requires a high level of executive engagement resulting in practical executive custody and an implementation that makes perfect sense to executives
3. Fundamental top down solution design
Fundamental first principles top down solution analysis and design that is precisely aligned strategically is the next component – this requires executive level strategic (fundamental) discovery of the essence of the business and how it thrives
4. Precision configuration founded on precision taxonomies
Strategic Engineered Precision configuration founded on Precision Taxonomies is the output of the previous step – developed in close consultation with the executives, managers and personnel of the client organization in order to accurately model the REAL complexity of the business
5. Iterative systematic walkthroughs of the configuration with the business
Repeated systematic structured walkthroughs of the configuration with the business in order to progressively develop and flesh out the operational aspects of the configuration -- must progress hand-in-hand with the previous point
6. Clever, focused, strategic custom development
As the configuration design unfolds identify opportunities for clever, focused custom development in order to more closely fit and optimize the solution to the essence of the business – small pieces of clever custom development can add HUGE value
7. Then optimize workflow (process), etc
Once the configuration is bedded down finalize workflow, approvals and other policy and process design elements and configure these using the logic of the hierarchies to facilitate this configuration and ensure precision
8. Encapsulate standards in Computer Based Training material
Once the configuration is bedded down document all operational standards, policies, processes, etc and encapsulate these in Computer Based Training material with performance measurement capability – ensure that all staff pass these tests before they are allowed to operate the software
9. Development in the ERP Implementation Laboratory
All of this takes place in a laboratory environment which is used for testing, training, development of reports, development of the data warehouse and business intelligence environment, etc until the entire configuration is fully tested and all staff are fully trained – THEN ONLY go-live
10. Ten to twenty year plus investment life objective
All of this should take place against a planned ten to twenty year or longer investment life objective with contractual and staffing measures, including “the Right to Maintain and Repair” in place in order to ensure that such a long life span is attainable
I look forward to the opportunity to discuss this with you -- James@James-A-Robertson-and-Associates.com