Repeatable Analytic Process

Repeatable Analytic Process (RAP) is not intended to produce specific analytic results, but to standardize the manner in which analytic results are produced and documented. RAP is engineered on the premise that consistency is more important than perfection. The rationale behind this approach is simply that consistency - as opposed to inconsistency, leads not just to repeatability, but also to enhanced logic and understanding and easier error detection and correction. Consistency also increases the quality of analytic results while reducing both the cost of initial analytic projects and the marginal cost of subsequent projects.

There are two critical success factors for the RAP:

1. All RAP-based analytics must be based on the RAP Protocol. This protocol is a data standard whose purpose is to ensure analytics are based on shared, structured data from authoritative sources.

2. All RAP-based analytics must be documented with an Analytic Line of Sight (ALS).

The process depicted below shows an overview of the three fundamental parts to the RAP:

The main process (orange) which identifies analytic projects, requires the line of sight be determined before the analysis is conducted, executes the analysis, validates the line of sight as it was actually used, and delivers the products;
The Analytic Line of Sight or analytic view (blue) is similar to an SOW and specifies the questions to be addressed, the steps planned to address the questions, the rules and assumptions to be used in each step and the source data, and
The analytic protocol (green) which specifies the data standards to be followed in the analysis.

The keys to repeatability are:

Consistency in documentation of what is termed the "Analytic Line of Sight".
Consistency in source data and business rules.