The Business Simulation Laboratory

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

1. ESTABLISHMENT OF LABORATORY

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

2. TESTING OF INDIVIDUAL MODULES

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

3. TEST INTEGRATION

  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

4. DEVELOPMENT AND TESTING OF INTEGRATED REPORTS AND BI MODELS, ETC

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

5. SPECIFICATION, CONFIGURATION, TESTING, REFINEMENT AND DOCUMENTATION OF INTEGRATED WORKFLOWS / OPERATING PROCEDURES - 3 ITERATIONS

  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

6. DEVELOPMENT OF TRAINING MATERIALS

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

7. TRAINING

  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

8. FORMAL DECLARATION OF READINESS TO COMMENCE LIVE OPERATION - ISSUE CERTIFICATE OF 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. Software

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

From Here:

<<< PREVIOUS SECTION: Guidance and Advisory Services

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

Random Selection of Articles by Dr James Robertson

Cnf 081 Insights of Knowledge Management in a Global Recession

A discussion of the importance of Precision Configuration as a vital component of unlocking the full value of business information system investments as part of a Knowledge Management culture

SNw 046 The Real Issues in BIS: Part 2 -- Mythology and Lack of Executive Custody

Information Technology Mythology, the wide spread of marketing hype driving misrepresentation of the business information systems environment coupled with lack of integrity and other factors that result in the industry generally failing to deliver on its promises, together with Executive Custody, the ownership of integrated Business Information Systems by the CEO of the business are discussed

TxM 026 Section 2.9 SEPT Examples

TxM 056 Section 7: How to do it

CIO 003 The Challenge of I.T.

SNw 019 A moral and ethical dilemma, systems that fail

SNw 032 Understanding strategy and how ERP fits in

Prd 008 Stages of a Strategic Engineered Precision Taxonomies Chart of Accounts

Web 05 Organizing Microsoft Outlook

A comprehensive explanation of how to set-up Microsoft Outlook to organize your emails in a manner that makes it easy to handle the full diversity and complexity of emails that executives and managers typically receive

Prd 026 Factors impacting time and budget

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
James@James-A-Robertson-and-Associates.com

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

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

CIO 004 Not very Intelligent

TxM 060 Section 7.4 Complexity

Prd 029 Essential characteristics and drivers of the proposed JAR&A Financial Analytical Suite™?

Prd 005 What are the essential components of Value Creation through Precision Configuration, Based on Precision Taxonomies?

TxM 022 Section 2.5 What is a precision taxonomy?

Std 018 Procurement: 09 Table of Contents of Submission

The Table of Contents of the Tender Submission is prescribed in detail in order to ensure that different bids can be lined up against one another and accurately compared

TxM 019 Section 2.2 Definitions of Strategy

Prd 003 An upside-down view of ERP implementation? NO!

Std 003 Example General Ledger Manual

A redacted version of an actual manual for a JARandA Chart of Accounts for a small manufacturing company. This manual gives a comprehensive picture of how the Chart of Accounts is structured, how the Cubic Business Model works and the reporting and other opportunities that the design provides

TxM 069 Section 7.13 Critical implementation considerations