TxM 001 Taxonomy Handbook -- Introduction Created by James on 6/26/2013 12:51:41 PM
The James A Robertson and Associates
Taxonomy Handbook
How to unlock exceptional value
From your ERP, IBIS, Data Warehouse or Business Intelligence
Investment
Supporting exceptional decisions that enable your organization to THRIVE
A new, different and FAR BETTER approach to information system configuration
By
Dr James A Robertson PrEng
The ERP Doctor
This article contains the introduction to the Taxonomy Handbook, whilst the rest of the Handbook is reflected in the articles following, flowing from TxM002 to TxM070, and in the same numbering as the Table of Contents given below:
Table of contents
Introduction and copyright
A word of caution
Definition of precision content engineering
Table of contents
Section 1: Problem statement, why read this, history
1.1 Why you should read this
1.2 Typical needs
1.3 Problem description
1.4 What is a Strategic Engineered Precision Taxonomy (SEPT) to JAR&A Standards?
1.5 History of the JAR&A Strategic Engineered Precision Taxonomy (SEPT) approach?
1.6 What is NOT a Strategic Engineered Precision Taxonomy?
1.7 Taxonomy principles
1.8 The desired end-state
1.9 Why Taxonomy coding is important
1.10 Differentiators
1.11 What is different about the JAR&A ERP Implementation approach
1.12 Why use the JAR&A approach?
1.13 Key Benefits of the JAR&A SEPT approach to system and data warehouse configuration
1.14 The REAL cost of SEPT Versus the REAL cost of conventional solutions And the REAL value of SEPT
Section 2: Definitions and examples
2.1 What is the JAR&A Strategic Engineered Precision Taxonomy (SEPT) approach?
2.2 Definitions of Strategy
2.3 What is a strategic taxonomy?
2.4 What is an engineered taxonomy?
2.5 What is a precision taxonomy?
2.6 The case for Strategic Customization
2.7 Defining the taxonomy approach
2.8 Comparison between a full-house ERP SEPT re-implementation and a Data Warehouse SEPT implementation
2.9 SEPT Examples
Section 3: Why JAR&A, Who is James Robertson, required Knowledge and Experience
3.1 Why not do it yourself without JAR&A?
3.2 Introducing Dr James Robertson, PrEng -- The ERP Doctor
3.3 James Robertson's knowledge and experience as applied to taxonomy development
3.4 Knowledge and experience required for a senior SEPT taxonomist
3.5 The Factors Causing Integrated Business Information System (IBIS) Investment Failure
3.6 The Critical Factors For Integrated Business Information System (IBIS) Investment Success
3.7 There ARE visible differences in quality of taxonomies
Section 4: Important principles
4.1 How to give executives REAL information
4.2 The Power of an Executive with a Blank Sheet of Paper
4.3 Why ERP can make the blood boil
4.4 The CEO MUST be the custodian of ERP
4.5 Understanding strategy and how ERP fits in
4.6 Risks and common mistakes when developing taxonomies and configuring systems
4.7 Risks and common mistakes when developing Group-Wide Charts of Accounts
4.8 What is an IT Pulse Measurement?
4.9 Defining an ERP Implementation Engineering Laboratory
Section 5: The cubic business model and group chart of accounts
5.1 The JAR&A SEPT Cubic Business Model and Group-Wide Chart of Accounts
5.2 Benefits of developing group wide Precision strategic master taxonomies and data attributes to JAR&A standards
5.3 Key Components of JAR&A SEPT Cubic Business Model and Group-Wide Chart of Accounts
5.4 Suggested basis of attribution of overheads and production costs in a cubic business model environment
Section 6: Why taxonomy software?
6.1 Why Taxonomy and Configuration Management software is necessary
6.2 What is the JAR&A taxonomy software?
6.3 Why use the JAR&A taxonomy software?
6.4 Further information on the use of software to develop and manage Taxonomies and Precision Configuration
6.5 Benefits of taxonomy software
Section 7: How to do it
7.1 The challenge
7.2 The opportunity
7.3 The essence of the solution
7.4 Complexity
7.5 Preparatory steps for a SEPT project
7.6 Strategic Engineered Precision Taxonomies and Configuration Getting from where you are to where you want to be
7.7 Design and development stages
7.8 Categories of lists
7.9 Important questions about any data
7.10 Steps in developing a hierarchy
7.11 Steps in coding a hierarchy
7.12 Coding steps
7.13 Critical implementation considerations
7.14 Conventions and standards
Section 8: Case studies and white papers
8.1 V3 ERP Implementation case study
-- headlines
-- paper
8.2 CRM Risk Control case study
-- headlines
-- paper
8.3 Rennies Group General Ledger case study
-- headlines
-- paper
8.4 African Sales Company case study
-- headlines
-- paper
Section 9: Other references
9.1 Why your IT project may be riskier than you think Harvard Business Review
-- headlines
-- paper
9.2 19 out of 20 ERP implementations do NOT deliver what was promised -- Financial Mail
-- headlines
-- paper
9.3 Most organizations are NOT making better decisions than they did five years ago – Gartner
-- headlines
-- paper
Section 10: Conclusion
---oOo---
Introduction and copyright
The JAR&A Taxonomy Handbook is a compilation of short articles which provide an introduction to the Strategic Engineered Precision Taxonomy (SEPT) approach to Enterprise Resource Planning (ERP), Data Warehouse (DW) and Business Intelligence (BI) solutions for business. These technologies collectively form something that I term the Integrated Business Information System or IBIS).
We sincerely believe that this approach is the missing link and next frontier in business information systems.
This document is very much a work in progress and DRAFT
It is a combination of marketing and technical articles, some recent, some of some vintage that have been put together to provide a more comprehensive view of the picture that I see
Thus sections are not necessarily in the best sequence, some items may be redundant, wording may not be clear or may not be as diplomatic as it should be
You have received a copy because I felt it would be relevant to you at this time but I ask that you will take account of the above points and feel free to let me have feedback both negative and positive.
James Robertson
09 November 2011
Tel: 0027-(0)11-251-6644
Email: James@JamesARobertson.com
Copyright
This manual is the intellectual property of James A Robertson and Associates and may not be reproduced or distributed without the express permission of Dr James Robertson
A word of caution
The techniques presented in this manual have been developed over decades.
It is only recently that I have come to fully understand just how different this approach is to the traditional methods.
During the last two decades I have consistently seen that people readily grasp the concepts but fail to get the detail right.
It is vital to recognize that exceptionally well designed taxonomies and configuration will serve the organization well for decades if well maintained and the commercial strategic value of these hierarchies to the organization will be huge.
In terms of overall life time cost of ownership it costs MUCH more to develop and operate sub-standard taxonomies and configuration and, unless you really understand the fine details of what is contained in this manual you will never know that what you have is sub-standard.
I strongly recommend that you engage with me, at the very least in terms of the high level solution architecture, training and periodic review in order to obtain the true value of this approach in your organization.
I look forward to working with you.
James Robertson
Definition of precision content engineering
The definition of information content in a way that is structurally (taxonomically) fundamentally meaningful to human beings who understand the business and the translation of this content into structured codes which faithfully and accurately reflect human understanding of the REAL WORLD in a way that the computer can manipulate with minimal human intervention so that the computer system appears to be intelligent.
[MAKERATING]
The comment feature is locked by administrator.
Return