• Login

The Business Simulation Laboratory -- War Games

Comprehensively configure and break the configuration until it cannot be broken any more and then comprehensively prepare the system and the business for operational deployment so that an exceptionally high value outcome is achieved with comprehensively mitigated risk

<<< PREVIOUS SECTION:  Guidance and Advisory Services

<<< PREVIOUS SUB-SECTION:  The Art of Project Leadership

<<< PREVIOUS SUB-SUB-SECTION:  Why Regular Communication with the CEO is Vital

NEXT SECTION:  Precision Configuration and Strategic Business Information Architecture >>>

Business Simulation Laboratory

The concept of the Business Simulation Laboratory derives from Dr Robertson's experience in setting up and operating a very complex suite of Engineering Laboratory tests for his PhD

The Business Simulation Laboratory is the ONLY way that a high value ERP implementation can be accomplished while at the same time eliminating risk to the business -- provided it is well designed, well implemented and well operated within the framework of a tough contractual environment as created by our Engineering Procurement approach

We offer a range of services with regard to advice with regard to the establishment and operation of a Business Simulation Laboratory as a critical component of any ERP or Business Information System Configuration


Following is some headline information about the Laboratory

Specification of the System Configuration Laboratory / Business Simulation Laboratory

This webpage sets out the Laboratory approach that is recommended.

The Laboratory approach that is set out here has been developed by James Robertson over several decades and is geared to minimizing commissioning risk and maximizing reliability in the final commissioned Business Information Systems solution.

 1.       Laboratory Definitions

The following terms are applied:


      1.1   Laboratory

A laboratory is a facility that provides controlled conditions in which scientific research, experiments, and measurement may be performed. (Wikipedia)

In the context of this document a System Configuration Laboratory is a room equipped with computers, visual aids, etc in which the configuration of a system is developed, refined and tested until it is stable and suitable for commissioning.  The Laboratory is also used to develop and test reports, training material, etc.  The goal of the Laboratory is that when the Laboratory work is completed the system is ready for deployment with a high certainty of a robust, reliable and sustainable outcome.


     1.2   Engineering

Engineering is the discipline, art, skill and profession of acquiring and applying scientific, mathematical, economic, social, and practical knowledge, in order to design and build structures, machines, devices, systems, materials and processes that safely realize improvements to the lives of people.

The American Engineers' Council for Professional Development has defined "engineering" as “The creative application of scientific principles to design or develop structures, machines, apparatus, or manufacturing processes, or works utilizing them singly or in combination; or to construct or operate the same with full cognizance of their design; or to forecast their behavior under specific operating conditions; all as respects an intended function, economics of operation and safety to life and property.” (Wikipedia)


     1.3   Prototype

A prototype is an early sample or model built to test a concept or process or to act as a thing to be replicated or learned from. (Wikipedia)

A prototype is a carefully and professionally constructed test sample of a system that in final form is intended to be put into economic operation by the developers (Robertson)

In the context of this document the entire configuration of all systems will be developed in Prototype form in the Laboratory until it reaches a point where it can be deployed in the business with a high level of certainty of a reliable and sustainable outcome.


     1.4   Implementation

Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy. (Wikipedia)

In the context of this document the Laboratory is a central component of the Implementation of the designated systems in the business.  The main characteristic of a Laboratory based implementation is that every aspect of the configuration is comprehensively tested in the Laboratory such that the deployment of the software in the business is a Commissioning rather than an implementation with the bulk of the Implementation undertaken in the Laboratory.


     1.5   Test

A test can be considered as a technical operation that consists of determination of one or more characteristics of a given product, process or service according to a specified procedure. (Wikipedia)

In the Laboratory approach every component of the configuration will be comprehensively tested using statistically representative data such that the configuration is proven to be reliable and dependable.  This is fundamentally from “User Acceptance Testing” insofar as it requires a much higher level of rigour and reproducibility.  Automated testing software may be used to run repetitive testing cycles.


     1.6   Walkthrough

In software engineering, a walkthrough or walk-through is a form of software peer review "in which a designer or programmer leads members of the development team and other interested parties through a software product, and the participants ask questions and make comments about possible errors, violation of development standards, and other problems". 

A walkthrough differs from software technical reviews in its openness of structure and its objective of familiarization. It differs from software inspection in its ability to suggest direct alterations to the product reviewed, its lack of a direct focus on training and process improvement, and its omission of process and product measurement. (Wikipedia)

1.6.1     Software Walk-through

In the context of the Laboratory approach a software walk-through is a systematic step by step practical demonstration of a piece of software directed at ensuring that the people present in the session gain a solid insight into the software and how it works directed at ensuring that the design work that follows is grounded in a solid understanding of how the software “machine” works.


1.6.2     Configuration Walk-through

A configuration walk-through is a systematic step by step practical demonstration of a piece of software configured to fit a particular element of the business using real data directed at ensuring that the configuration accurately fits the understanding of the people present in the walk-through with a view to ensuring a tight fit to the business.

2. Laboratory Principles

The following principles are applicable to the Configuration Engineering Laboratory:


1.1   Prototyping environment

The laboratory is a rigorous, carefully controlled prototyping and testing environment managed by a very senior and very practical manager who has a clear high level holistic view of how the entire solution fits together and who clearly understands the critical role of the laboratory.  This manager is to be supplied by the Implementer.


1.2   Representative data

The laboratory is populated with comprehensive, carefully selected representative data – perhaps 0.1% of the data that is in the live system but representative of all possible scenarios.

There are very specific principles to be applied in the selection of this data.  Selection of this data will be guided by the Project Facilitator.


1.3   Fully equipped

The laboratory is situated in a permanently assigned, well-appointed and well-furnished room with five to ten high performance workstations, a high performance server, high performance backup device  (to permit rapid roll back to previous test states), data projector, flip charts, white board, etc.


1.4   Automated testing software

The laboratory is to be equipped with automated testing software that will permit recording and playback of test scripts.


1.5   Life of project

The laboratory is established at the very start of the project and runs until the Data Warehouse and Business Intelligence environment are fully operational and the system has been fully commissioned.


1.6   Accurately model the real world

All configuration settings are tested in the laboratory until they accurately model the precise desired operation of the business and all required customization and custom development has been comprehensively and rigorously tested and accepted.

Executives and managers must be able to undertake structured facilitated walkthroughs of the laboratory configuration and see their business at all times – if it does not make sense to the executives and / or managers the process stops until the configuration has been modified so that it does make sense to them.


1.7   Break it till it breaks no more

The primary initial goal of the laboratory is to break the configuration and once it cannot be broken to optimize it, document it, develop training material and computer based training material (CBT) in it, use it as a training environment, use it for the testing of reports and establish the Data Warehouse operating against it.


1.8   Business Intelligence Development

A full set of management reports, dashboards, etc are to be developed and tested in the laboratory BEFORE production operation commences.


1.9   Standards, Policies and Procedures

A full set of operational standards, policies and procedures must be developed during the project and embedded in the training given in the laboratory and thereafter.


1.10  Computer Based Training Material

A full set of Computer Based Training material with regard to standard operating practices for all primary areas of business operation that uses the software must be developed in the laboratory and deployed as part of the final deliverable.


1.11  Basis of go-live certificate

The configuration does NOT go-live until it has been comprehensively tested in the laboratory and accepted by all senior project team members.

The go-live certificate will be issued at the end of a structured walkthrough of the entire configuration by the entire top management of the project – this walkthrough may take several days and may have to be suspended several times for adjustments.

If the top team are not satisfied with the results of the walkthrough further walkthroughs, will be held until all members of the top team are willing to accept the configuration.


1.12  Basis of live instance

The laboratory configuration forms the basis of the live instance of the software – the entire configuration is to be copied onto the production server and rigorously tested software used to clear out all transaction data files and reset all counters.

This reset software must be supplied and certified by the software vendor who shall be liable for damages should the reset software be found to be defective.

The final empty configuration will be reviewed and tested during a trial run of the start-up process in the Laboratory.


1.13  Goal of the Laboratory

The goal of the Laboratory is to ensure that the final live installation is an excellent fit to the business, that all staff are properly trained at go-live, that there are no surprises and that there is minimal well managed risk to the business on go-live.

1.14  Bill of Services

More details of the Laboratory are set out in the Bill of Services.

3. Laboratory Specification

The Laboratory is a well-equipped room with a full installation of all software components in which all aspects of the installation can be effectively tested.

The set-up of the Laboratory must be designed in such a way that all realistic scenarios and operational conditions can be simulated.  This may require additional workstations and child Laboratory installations at remote sites in order to fully test the performance of communication, etc at practical levels.

It is important that the workstations, server/s, network operate at peak efficiency so that testing can proceed quickly.  Testing relating to workstation, network and server performance must take place as a distinctly separate activity, maximum performance in the Laboratory is vital in order to ensure that testing proceeds as efficiently as possible and takes as little time of business and contractor personnel.

The room must be sufficiently large for an audience to be able to attend walk-throughs and there must be a data projector so that groups of people can participate in walk-throughs.

Other presentation aids such as flip charts and white boards must also be provided.

4. Laboratory Stages


    a. Detailed planning of integrated laboratory simulation programme - goal of the laboratory is to BREAK IT until IT cannot be broken

    b. Specify laboratory facility

    c. Procure equipment and establish laboratory facility

    d. Collate and consolidate detailed statistically significant test packs for each module into one integrated test pack


   a. Commission and test individual modules in the laboratory as they become available


    a.  Test integration of modules as they become available

    b.  Testing and acceptance of the integrated solution

       1.  Technical integration

          a.  Technical testing of integrated solution until the entire solution works technically - 3 iterations

          b.  Other activities necessary to get the integrated solution to a point where it can be utilized by the business team - 3 iterations

       2.  Business operational integration

          a.  Operational testing of the integrated solution until the entire solution works at a business operational level - 3 iterations

          b.  Other activities necessary to get the integrated solution to a point where it can be presented to executives - 3 iterations

    c.  Simulation and review of the integrated solution - first iteration

         1.  Comprehensive simulation of live operation with a small but statistically significant test data pack

         2.  Systematic presentation and walk-through of entire solution with executives

         3.  Other activities relative to first iteration

    d.  Simulation and review of integrated solution - second iteration

         1.  Revise, refine and optimize solution

         2.  Comprehensive simulation of live operation with small but statistically significant test data pack until ready to present to execs

         3.  Systematic presentation and walk-through of entire solution with executives

         4.  Other activities relative to second iteration

    e.   Simulation and review of integrated solution -- third iteration

          1.  Revise, refine and optimize solution

          2.  Comprehensive simulation of live operation with small but statistically significant test data pack until ready to present to execs

          3.  Systematic presentation and walk-through of entire solution with executives

          4.  Other activities relative to third iteration


     a.  Development of integrated reports - 3 iterations with Executive review

     b.  Development of integrated BI reports, models and dashboards - 3 iterations with executive review

     c.  Development of executive level strategic BI reports, models and dashboards - 3 iterations with executive review


    a.  Specify and configure workflows - iteration 1

        1.  Define workflows from executive level and document

        2.  Review and refine with management

        3.  Review and refine with operational personnel

        4.  Configure in the system

        5.  Walk-through

   b.  Specify and configure workflows - iteration 2

         1.  Define workflows from executive level and document

         2.  Review and refine with management

         3.  Review and refine with operational personnel

         4.  Configure in the system

         5.  Walk-through

   c.  Specify and configure workflows -- iteration 3

         1.  Define workflows from executive level and document

         2.  Review and refine with management

         3.  Review and refine with operational personnel

         4.  Configure in the system

         5.  Walk-through

   d.  Finalize and accept workflows

         1.  Management review

         2.  Executive review

         3.  Acceptance


   a.  Documentation of policies and standards - 3 iterations

   b.  Development of user manuals -- 3 iterations

   c.  Development of Computer Based Training material with tests and performance measures with executive review - 3 iterations

   d.  Other activities necessary to develop a comprehensive training environment for the enterprise


    a.  Training of Operational Personnel

         1.  Overall system operation, integration impacts - who is affected by what I do - how the whole system fits together

         2.  Policies, standards, protocols, escalation, authorities, etc - includes speed and accuracy of data capture for all personnel with significant keyboard input requirements

         3.  Touch typing test for all personnel responsible for significant keyboard input - touch typing classes for those who do not achieve a minimum standard of 20 words per minute at 99% accuracy - team must include an instructor

         4.  Training on CBT until reach required standard -- multiple repetitive cycles

         5.  Comprehensive operational simulation until all staff are trained to a level where they can migrate to new system easily - at least 3 iterations

         6.  Other training related activities for operational personnel

         7.  Declaration of operational readiness

    b.  Training of supervisory personnel

         1.  Overall system operation, integration impacts - who is affected by what I do - how the whole system fits together

         2.  Policies, standards, protocols, escalation, authorities, etc - includes speed and accuracy of data capture for all personnel with significant keyboard input requirements where applicable

         3.  Touch typing test for all personnel responsible for significant keyboard input - touch typing classes for those who do not achieve a minimum standard of 20 words per minute at 99% accuracy

         4.  Training on CBT until reach required standard where applicable - multiple repetitive cycles

         5.  Comprehensive training in conjunction with operational simulation until all supervisory staff are trained to a level where they can migrate to the new system easily - at least 3 iterations

         6.  Other training related activities for supervisory personnel

         7.  Declaration of supervisory readiness

   c.  Training of Managers

         1.  Overall system operation, integration impacts - who is affected by what I do - how the whole system fits together

         2.  Policies, standards, protocols, escalation, authorities, etc - includes speed and accuracy of data capture for all personnel with significant keyboard input requirements where applicable

         3.  Touch typing test for all personnel responsible for significant keyboard input - touch typing classes for those who do not achieve a minimum standard of 20 words per minute at 99% accuracy

         4.  Comprehensive training in conjunction with operational simulation until all managers are trained to a level where they can migrate to the new system easily - at least 3 iterations

         5.  Other training related activities for managers

         6.  Declaration of management readiness

   d.  Training of Executives

         1.  Overall system operation, integration impacts - who is affected by what others do - how the whole system fits together

         2.  Policies, standards, protocols, escalation, authorities, etc

         3.  Comprehensive training in conjunction with operational simulation until all executives are trained to a level where they can migrate to the new system easily - at least 3 iterations

         4.  Other training related activities for executives

         5.  Declaration of executive readiness


    a.  Declaration by each Implementer Team Leader

    b.  Declaration by each Business Team Leader

    c.  Declaration by Implementer Project Manager

    d.  Declaration by Implementer Project Director

    e.  Declarations by Client Heads of Departments

    f.  Declaration by Client Project Facilitator

    g.  Declaration by Client Contract Manager

    h.  Declarations by Client Divisional Heads

    i.   Declaration by Client Executive Sponsor

    j.   Approval by EXCO

    k.  Board approval

5. Laboratory Completion – Certificate of Readiness to Commence Live Operation

As noted above the final stage of any aspect of Laboratory operation is the issue of a Certificate of Readiness to Commence Live Operation.


This certificate must be progressively signed by all team members and includes a clear statement that the persons signing the Certificate are fully satisfied that the system is ready to be deployed in the business.


The goal of this certificate is to create a context in which no-one will sign the certificate until they are fully satisfied that the configuration is ready to be commissioned.

Standards for Custom Software Specification

Software Specification Standards


James Robertson


Following are outline standards for software specification to be read in conjunction with the Laboratory Specification.


1.1. Software Specification

Software will be specified as follows:

1.1.1. Verbal description – a structured English description of the piece of software and its application;

1.1.2. Screen layout -- a simple screen layout, can be done in Excel but must be to scale, setting out the relative positions of data fields, display values, buttons, check boxes, radio buttons, graphical display areas, text boxes, etc.  The layout must be annotated as necessary such that the operation of the screen is fully described;

1.1.3. Database table field specifications – listing of each database table including detailed field specifications;

1.1.4. Field entry, field exit and field attribute specification for every field and other programmatic element on the screen layout;

1.1.5. Structured English description of any complex processes initiated off the screen at a level that allows business personnel to confirm that this is the manner in which the process must work;

1.1.6. Full set of representative data to be used for test purposes -- this data must be provided in an Excel format laid out according to the database tables and fields in which the data will ultimately reside.  All validation lists must be fully populated.  The business must ensure that the test data is FULLY representative of every possible combination and permutation that can occur in the real world;

1.1.7. Any other information in order to fully define the operation of the software;

1.1.8. The Contractor is responsible for creating the above specification in collaboration with the Customer.  The Customer is responsible for supplying the test data in a template approved by the Contractor;

1.1.9. Customer and Contractor personnel must systematically work through the specification and test data looking for weaknesses and seeking to break the specification;

1.1.10.Both the Customer and the Contractor must sign a certificate to the effect that the specification is complete, has been thoroughly and systematically reviewed and meets the needs of the business before software development can commence.


1.2 Software Acceptance Testing

Software Acceptance Testing will take place in terms of the above specifications and using the test data referred to above in the Business Simulation Laboratory and in terms of the approach set out in the Laboratory Approach document.  Senior client personnel will be given the task of seeking to break the software until it can no longer be broken.

Once the software operates fully in accordance with the specification and is stable and reliable a certificate is to be issued and signed by both parties to confirm compliance with the specification and stability and reliability.


1.3 Software Polishing

It is so that in most cases, once software has been built and the business is able to engage with it in practice that refinements suggest themselves.  A portion of the planned time for development must be set-aside to allow for ONE iteration of refinement that is NOT according to the specification during the testing phase.


1.4 Variation Orders

Once a certificate of acceptance is issued any subsequent changes to the software will be regarded as a “variation order” and will require a cost estimate and budget approval outside the project budget.


2.  Reports

Reports will be specified as follows:

2.1. Report layout in Excel – if the report is of moderate or advanced complexity the report will be laid out in Excel using live data from the Laboratory Test Environment or the Live Environment once the system is running live;

2.2. The report specification will be accompanied by a verbal description of the purpose of the report and listing of the data tables and data fields within the tables which will provide the required data.  A comprehensive set of test data must exist;

2.3. Acceptance will be on the basis of inspection relative to the concept layout and confirmation that all values, totals, etc are correct under all reasonably foreseeable data variations.

2.4. Once the report has been accepted any changes must be performed in-house by the Customer’s personnel or will be subject to a Variation Order;


3.  Analytics and Business Intelligence

3.1. Analytics and Business Intelligence models will be either prototyped in Excel or in the available software tools using live data from the Laboratory Test Environment or the Live Environment once the system is running live.

3.2. The analytics or model specification will be accompanied by a verbal description of the purpose of the model and reference to the data tables and data fields within the tables which will provide the required data;

3.3. Acceptance of the analytics or model will be on the basis of inspection relative to the concept layout and confirmation that all values, totals, etc are correct under all reasonably foreseeable data variations.

3.4. Once the of the analytics or model has been accepted any changes must be performed in-house by the Customer’s personnel or will be subject to a Variation Order...


James Robertson

07 August 2014

Random Selection of Articles by Dr James Robertson

Cnf 062 How To Ensure That Software Assets Deliver

Key factors giving rise to business information system investment failure and critical components of ensuring a successful outcome with particular emphasis on executive custody and managing the factors causing failure and the critical factors for success
Sem 01 Why your Business Information System is NOT delivering and HOW to FIX it

A concise executive briefing directed at informing executives and senior managers with regard to the REAL issues in business information systems and the measures to take to obtain greater value from their existing investments
Std 019 Procurement: 10 Certificates for Use on the Project

A selection of tough Certificates designed to focus ALL parties attention on accountability for outcome, rigour and quality of work, create a platform for tough contractual responses in the event of non-performance.  Please consult your legal advisor in terms of exact wording in your jurisdiction

Dr James A Robertson PrEng The Business Information Systems Doctor

Business Systems NOT delivering?

Call the Business Systems Specialist

Dr. James Robinson

Dr James A Robertson -- has been involved in the effective application of Business Information Systems, including but NOT limited to ERP, since 1987 and in the profitable and effective use of computers in Business since 1981.

Drawing on a diversity of experience, including formal military training in Quick Attack techniques at the Regimental Commander level, Dr Robertson has developed highly effective methods of investigating any sub-optimal Business Information Systems situation -- be it an established system or a stalled project or any other source of Executive frustration -- quickly and concisely diagnosing the root cause of the problem and prescribing concise practical actions that Business Executives can effectively act on see the Pulse Measurement page and also the Sample Reports page for redacted real reports.

He has also developed highly effective methods of strategically enriching systems to unlock the full potential of existing investments, see the Precision Configuration page and couples this to architecting small pieces of clever software that harness the full potential of your investment, see the Software page.

If you are having problems with your systems, your project or your IT Department, call The Business Systems Specialist

Business System Failure is RIFE -- we offer insight into why this happens AND WHAT is required to prevent it.

Failure is at epidemic levels with massive damage done to client companies -- if you are NOT aware of the extent of the problem please visit the About Failure page for a catalog of major failures running to billions of Pounds and Dollars.

All evidence indicates that the established players do NOT know how to deliver stable, reliable high value solutions that WORK.

There HAS to be a better way!

This website provides information relating to that way with a large collection of white papers, presentations, standards documents, etc that you can use to start bringing the situation under control

We also offer high level advisory services with regard to the application of the principles advocated on this website

We offer an ENGINEERING APPROACH to addressing these issues

Click here to read more about the Engineering Approach

By Engineering I mean the formal, structured, highly disciplined, highly systematic, highly practical approach that consistently delivers results in ALL areas of human endeavor where formally trained and certified engineers are the ONLY practitioners permitted to operate -- think large buildings, factories, motor vehicles, aircraft -- highly complex systems that work at a level that we take it for granted that they WILL work and where failure is all but unthinkable and, when it happens, attracts immediate public attention and rigorous investigation directed at ensuring that such failures are prevented in the future -- in fact, everything that the management consulting industry that implements complex software systems is NOT

This approach is discussed further on the Engineering Approach page.

Book -- The Critical Factors for Information Technology Investment Success

In 2003 I undertook an in-depth analysis of all the information and experience that I had gathered with regard to the factors giving rise to Business Information System failure including ERP and general IT and classified this information into a number of categories including "The Factors Causing Failure" and "The Critical Factors for Success" based on this I developed a two day Course "The Critical Factors for Information Technology Investment Success" which is still offered today.

Based on this I wrote the book of the same name, which is available in electronic form here for download:

Subscribe to our StratNews newsletter

Click here to send us an email subscribing to our free newsletter -- all articles posted by James Robertson will be emailed to you

Random Selection of Articles by Dr James Robertson

SNw 039 Strategic Essence: The Missing Link: Overview

Overview of the main points of the series of articles on strategic essence, strategic essence being "the essence of the organization and how it thrives" and focused on the "right things" for the organization to do and then on doing those things "right" in accordance of the definition given by Professor Malcolm MacDonald
Std 013 Procurement: 05 Software Schedule

The software schedule is a list of all functional software elements that it is assessed are required.  This is a basis for bidders to add and subtract the modules and products that they have to offer in order to make up the mosaic that constitutes the complete response to the requirement
The software schedule correlates directly with the Bill of Services and the two should be set up to align with one another
SNw 057 Business System Failure – HOW do you recognize it?

Many executives and managers do NOT know how to recognize business systems failure.  They have failed systems right at their finger tips, gauged by the standards advocated on this website, BUT they do NOT realize that they are at some level failures and, because they do NOT recognize failure they do NOT recognize either the need OR the opportunity to DO something about it
Cnf 072 The essence of managing I.T. Projects on time that meet expectation

The management of IT projects generally focuses on the wrong factors, it is vital to focus on the Critical Factors for Success and the Factors causing Failure and manage these effectively using multi-disciplinary teams that effectively balance the tension between cost, quality and time

Connect with James Robertson on LinkedIn

James has a very detailed profile on LinkedIn should you require further information about him.

You can also connect with him on LinkedIn at http://www.linkedin.com/in/DrJamesARobertsonERPDoctor

James has an open networking profile -- click on "Connect" and use email address James@LinkedIn-at-JARA.com.

Contact Us

You can contact us on

Email: James@James-A-Robertson-and-Associates.com

LinkedIn at http://www.linkedin.com/in/drjamesarobertsonerpdoctor

Facebook at https://www.facebook.com/james.a.robertson.393

Mobile: +44 (0) 776-862-2875

Landline: +44 (0) 207-059-0007

Fax: +44 (0) 844 774 4580

Articles by James A Robertson and Associates

There is a large body of white papers, articles and other content produced by Dr James Robertson available on this website

Please click here to visit the detailed listing of articles

ArticleTagCloud for Articles Published by James A Robertson and Associates

7 steps to FIX your ERP      80:20 regarding software replacement      aborted projects      abstract      abstractness      accounting      actionable      adjudication      Advantage Data Transformer      advisory      agreement      all possible classifications      all reports      all software elements required      all spreadsheets      all tasks required to execute the project      Alpha Omega      analysis of data      analytics      animation      answers to the questions we have NOT yet thought to ask      Armscor      arrogant ignorance      art of strategic business information system project leadership      ASCO      attendance register      attorney      audit      audit cost reduction      bankrupt organizations      basis for achieving alignment      basis of payment      basis of pricing      better way      bid adjudication      bid adjudication score sheet      bid compliance      bid compliance checklist      bill of materials      bill of services      BIS      BIS failure      BIS success      boots in the mud      BPM      BPM dangerous      BPM distracting      BPM ineffective      brainstorming      break it until it does NOT break anymore      break it until it will NOT break any more      budget      budgeting      business engagement      business executives      business improvement      business information system      business information system failure      business information system success      business information system taxonomies      business information systems      business information systems procurement      business information systems projects      business integration      business intelligence      business intelligence models      business knowledge and experience      business participation      business process      business process mapping      business requirements focused      business requirements specification      business simulation laboratory      business systems      business systems laboratory      business understanding      by the book      care      case studies      case study      CEO      CEO -- project leader communication      CEO as custodian      CEO definite views      certificates      challenges      challenging presentations      change facilitation      change for strategic reasons      chart of accounts      classification schemes      clever software      client changing scope      client compact      clinical codes      coaching      Cobol      COBOL CAN be retained      Cobol still viable      code schemes      coding conventions and standards      cognitive span      collapse      communication      competitive advantage      competitive advantage through precision configuration      competitiveness      compiler      complexity      compliance      compliance checklist      comprehensive testing      Compuware      conference speaking      conferences      confidentiality      configuration      consultant NOT delivering what required      contract      contract certificates      contract law      contracting      contractors      corporate planning      cost      cost-quality-time      CPT 4      CPT4      critical factors      critical factors for IT investment success      critical factors for success      critical factors for technology success      critical human foundation      critical issues      critical issues analysis      critical requirements      CRM Risk Control      cubic business model      custom development      custom software      customer focused      data      data content      data engineering      data entities      data warehouse      DB2      definitions      design against failure      design and development      design for success      determination of strategic essence      determining strategy      diagnostic code      diamonds in the dust      differentiated      differentiation      diffusion of innovations      discovery      dislike of failure      dispute resolution      do NOT change systems because of alleged software redundancy      do things competitors could NOT do      document pack      Dr James A Robertson      Dr James A Robertson PrEng      dramatic benefits      dramatically improved strategic management information      driver of success      Dunning-Kruger effect      ease of use      economic collapse      economics      effective communication      effectiveness      efficiencies      efficiency      efficient filing of emails      eliminate light bidders      email      engineer against failure      engineered data      engineering      engineering approach      engineering approach to strategy      engineering failure      engineering laboratory      engineering services      engineering solution design      engineering techniques      enhance differentiators      enhance the differentiators      enhancing the value of your present investment      ensuring project success      enterprise resource planning      ERP      ERP configuration      ERP failure      ERP procurement      ERP success      ERP taxonomies      ERP value      essence IS different      essence of business      essence of the business and how it thrives      ethics      examples      exceptionally bad code design      executive briefing      executive briefings      executive custody      executive decision support      executive engagement      executive forum      executive frustration      expose hidden agendas      facilitation      factors causing failure      factors causing IT investment failure      factors causing technology failure      factors to manage for success      failure      failure to address soft issues      fashion      file table of contents      Financial Information System      financial information systems      financial management      fixing your ERP      focus for projects      folder design      foundation for delivery      full training      functional entities      future      Gantt Chart      gap analysis      general ledger      George Paton      go-live      go-live certificate      governance      governance = care      governance failure      group consolidation      Group Consolidation Chart of Accounts      growth      gut feel factors      hand holding      harshest judge of governance      hate failure      head count reduction      health management software      hierarchies      high level requirements      high road      high value      high value implementations      high value solutions      high value systems implementation      highly effective chart of accounts      holistic view of solution      how do you achieve executive custody      how the organization differentiates itself      how to      how to do it      huge opportunity      human foundation      hype      Hyperion      IBIS      ICD 10      ICD10      importance of executive custody      improved management information      in-box rules      incremental enhancement of existing systems      ineffectiveness      inefficiency      information required from third party suppliers      information technology      information technology failure      Information Technology Strategy      information technology success      Informix      in-house courses      innovative software solutions      innovator      inside head of CEO      insightful      instructions      intangible      integrated business information system      integrated view of business      integrity      intelligent data      interactive training material      interview      invitation to bid      isolated CEO = explosion      IT      IT and strategy      IT Audit      IT failure      IT governance      IT lies      IT management      IT mythology      IT non-performance      IT people who lie      IT personnel socialization      IT procurement      IT projects that fail      IT strategy      IT systems      IT systems procurement      IT the harshest judge of governance      James Robertson      Jof Nelson      key performance indicators      Kirsten Speer      knowledge management      laboratory      lack of an engineering approach      lack of precision configuration      lack of strategic alignment      lawyer      leadership      legal agreement      legislation      lies      list of required software      listen carefully      litigation      logical entities      loss information      low road      loyalty      MacDonald      maintain code schemes      maintenance      maintenance management      Malcolm McDonald      management      management information      managing contractors      manual      marketing hype      master data      master data classifications      master test data      mature facilitation      mature facilitator      measurable      measures of alignment      mentoring      Microsoft Outlook      misrepresentation      missing link      mistique      morals      Munich      mystique      mythology      new future state      New South Africa      no drill down      non-disclosure      NOT classic project management      obsolete is a fashion statement      obsolete software      old software IS viable      once software works it always works      on-line seminars      opportunities      opportunity to turn the economy around      organizing Microsoft Outlook      orientation of IT staff      own business experience      passion to enable clients to thrive      people are part of the system      personality matrix      planning      platform for a tough contract      precisio      precision      precision configuration      precision configuration advisory      precision configuration leadership      precision data      precision taxonomies      Predictive Index      preparatory steps      prescribed table of contents      presentation technique      presentations      preventing failure      preventing falure      preventing project failure      pricing      principles      problem statement      procedure code      process      processor ignorant of language      procurement      procurement timeline      professional speaker      Professional Speakers Association of Southern Africa      profitability      programming languages are for the programmer      project facilitation      project leader      project leader -- CEO communication      project leadership      project management      project management IT project management      projects      prove it works      PSASA      psychology      psychometrics      public conferences      public presentations      public speaking      Pulse Measurement      quality      REAL issues in Business Information Systems      REAL value      recognizing failure      redaction      reduced audit costs      reduced head count      reference documents      Reg Barry      regulatory body      relationship Almighty      relationship orientated      remediation of existing systems      Rennies Group      reports      reports not reliable      request for proposal      requirements specification      results orientated      RFP      right things      rigorous process      rigorous strategic planning      risk management      Robert Priebatsch      robust business information systems procurement      robust business systems procurement      robust contracts      robust procurement      robust solutions      SAICE      SAP ABAP is similar to COBOL      scheduling procurement      scientific professional      score sheet      screen design      seminars      SEPT      service orientated      Service Orientated Architecture      simple techniques to enhance business information systems value      simulation      sloppy configuration      SOA      socialization      software      software assets      software design      software does NOT wear out      software is instructions for the bricklayer      software schedule      software specification      software specification standards      solution experience      solution knowledge      South Africa      South African Institution of Civil Engineering      speaking      Spirit Led      standards      strategic      strategic advisory      strategic alignment      strategic analysis      strategic analysis and design      strategic business improvement      strategic custom development      strategic definition      strategic discovery      strategic driver      strategic driving force      strategic engineered precision configuration      strategic engineered precision taxonomies      strategic essence      strategic financial information      strategic gap analysis      strategic governance      strategic information      strategic management      strategic management information      strategic plan      strategic planning      strategic project leader      strategic snapshots      strategic software      strategic solution architect advisory      strategic solution architect leadership      strategic solution architecture      strategically designed chart of accounts      strategy      strategy defined      strategy focused planning      Strategy Snapshot Toolset      StratGap      StratSnap      strengthen differentiators      structured analysis      structured chart of accounts      substantial management information      succeed by engineering against failure      success      successful deployment      survive      system knowledge and experience      table of contents      tailored presentations      take notes      taxonomies      taxonomy      taxonomy software      technology      technology failure      technology issues      technology management      tender document pack      tender pack      tender pack table of contents      test data      testing      The Critical Factors for Information Technology Investment Success      the Critical Factors for Success      the essence of the business      the essence of the business and how it thrives      the essence of the organization and how it thrives      the factors causing failure      the first hour      The REAL Issues in Business Information System success      things right      third party suppliers      third world countries      thrive      time      tipping point      tough certificates      tough contract management      tough contracts      tough procurement      tough terms      training      training material      treatment code      understanding of data      understanding the engineering approach      Uniface      unlocking value      use different languages for new components      V3 Consulting Engineers      validation data      value      versus process      video      webinar      webinars      weighted factors      what is executive custody      what is strategy      what is the essence of this organization and how does it thrive      what to do      where is IT going      why executive custody is required      why the organization exists and how it thrives      why your business information system is NOT delivering and HOW to FIX it      why your ERP is NOT delivering and how to fix it      workflow      writer     

Search Articles

Table of Contents


About Dr James A Robertson PrEng -- The Business Systems Doctor -- and Other Topics

Catalogue of Major Business Information System Failures

About the Engineering Approach

James Robertson's Value Add

Attributes of a HIGH VALUE solution

Recognizing Business System Failure

The Critical Human Foundation

Old Software IS Viable

From South Africa

Competencies of Dr James A Robertson PrEng

About Professor Malcolm McDonald

Table of Contents

About my relationship with the Almighty Creator, Yah the Eternally Self-Existing

Comments relating to the Business Systems Industry and other topics

Testimonials and other positive material regarding James Robertson

Reference Articles

List of Articles

Article Catalogue

Achieving High Value Business Information System outcomes

Executive Custody -- What is it and HOW do you get it?

The REAL Issues in Integrated Business Information System Success

Part 1: Introduction

Part 2 -- Mythology and Lack of Executive Custody

Part 3 – Strategic Alignment and Precision Configuration

Why your ERP is NOT delivering and HOW to FIX it

IT Project Management

Pulse Measurement

CEO Anthony Lee Comments on his experience of the Pulse Measurement

No Charge Guarantee on the Pulse Measurement Service

Examples of Pulse Measurement Outcomes

Critical questions regarding the Pulse Measurement™

The Pulse Measurement Workflow

The Critical Factors for Business System (ERP+) Investment Success in the Pulse Measurement

Indicative Pulse Measurement Durations

What is a JAR&A Pulse Measurement?

Survival of the fittest – why it makes sense to measure the pulse of your business

Examples of Pulse Measurement Outcomes over 24 years

Sample Pulse Measurement Reports


Strategic Essence: The Missing Link in Business Information Systems

Strategic Essence: Overview

Strategic Essence: Part 1 -- Strategy Defined

Strategic Essence: Part 2 -- Differentiation

Strategic Essence: Part 3 -- The Essence IS Different

Strategic Essence: Part 4 -- The Essence should be the Point of Departure

Strategic Essence: Part 5 -- Discovering Strategic Essence

Strategy -- the Essence of the Business: What is it and how do you develop actionable strategic plans?

Simple Steps to Increase the Strategic Value of your ERP Investment

Free Strategic Snapshot Toolset and Manual

A strategy focused planning system beyond traditional budgeting

Tough IT and ERP Procurement and Contracting that Works

Robust Business Systems Procurement

Part 1 -- Introduction

Part 2 -- Bill of Services, Laboratory, Go-live Certificate, etc

Part 3 -- Executive Engagement, Bid Compliance, Adjudication and other matters

Procurement Documents

Guidance and Advisory Services

The Art of Project Leadership

Why Regular Communication with the CEO is Vital

The Business Simulation Laboratory

Precision Configuration and Strategic Business Information Architecture

Precision Configuration based on Strategic Engineered Precision Taxonomies

The JAR&A Cubic Business Model

Highly Structured Strategic Chart of Accounts -- a Vital Element of your Corporate Information Arsenal

The Product Catalogue -- an Essential Element of any Precision Configuration

Attributes -- answers to the questions you have NOT yet thought to ask

Case Studies of Notably Successful Projects with high value Precision Configuration

092 Doing things differently and better -- ASCO Case Study 2-- BPM Summit 2013

088 Strategic ERP Invesment -- ASCO Case Study -- Service Management Conference and Exhibition Africa

026 Information Architecture and Design of FIS for Rennies Group -- Financial Information Systems Conf

018 CRM Risk Control: Designing and Implementing an Integrated Risk Mgmt Sys -- Integrated Risk Mgmt Conf

011 V3 Consulting Eng: Benefits of MIS to Professional Practice -- SAICE 15th Ann Conf on Computers in Civil Eng

Strategically Enriching your Business Information Systems

Part 1 -- Introduction

Part 2 -- Principles of Data Engineering

Part 3 -- Steps in applying these recommendations

Simple Steps to increase the strategic information value yield from your Business Systems Investment

The Full JAR&A Taxonomy Manual

Part 1: Introduction, Problem Statement, Definitions and Examples

Part 2: Why Use JAR&A, Required Knowledge and Experience, Cubic Business Model and Chart of Accounts and Taxonomy Software

Part 3: How to do it, Case Studies and White Papers and other References

Example General Ledger Manual

Business Process -- Irrelevant, Distracting and Dangerous

The RIGHT Approach

Custom Strategic Software Design and Oversight of Construction

Standards for Custom Software Specification

What IS Software?

IT Effectiveness

Organizing Outlook

Critical Factors for I.T. Success

A Moral and Ethical Dilemma -- Systems that Fail

Case Studies examining Business Information System failures

The BBC Digital Media Initiative Debacle

The Bridgestone -- IBM Conflict

Speaking and Training

Showcase of Conference Presentations

Most Viewed Presentations

Briefings and Seminars

Why your ERP/BIS is NOT delivering and HOW to FIX it

ERP and IT Procurement that Delivers Results

The Critical Factors for IT and ERP Investment Success

Other Seminars

Conferences and Public Presentations

Conferences 80 to 99 -- 2009 to Present

Conferences 60 to 79 -- 2005 to 2009

Conferences 40 to 59 -- 1996 to 2005

Conferences 20 to 39 -- 1994 to 1996

Conferences 01 to 19 -- 1989 to 1994

On-Line Seminars (Webinars)

Webinar on Preparing and Presenting Webinars

Contacting James A Robertson and Associates Limited