Engagement Structure

Engagement Structure - We work with our clients in a number of different capacities, depending upon the requirements, project timelines, and resource availability.  The high-level project plan below maps the project phases and deliverables for several concurrent governance initiatives:  GRC Systems Engineering for SAP Change Management and SAP Security Profile Development,  Process Architecture Maps, Process Modeling, Prototyping, and an ERM Metrics Life Cycle.

The following are general guidelines for estimating the LOE and elapsed time required for the various service scenarios:

Process Engineering

Process Engineering Requirements Workshop: 3-5 days LOE, 1-3 days on-site.  Initial requirements, process taxonomy, prototype design, high level project plan,  and Architecture Maps

Process Engineering Requirements and Prototyping:  3-5 days Requirements and 1-2 weeks Prototyping per Process Area.  This combines the Requirements Workshop with full Prototyping.  Depending on the complexity of the operations, process maturity,  and the state of existing documentation, the goal is to complete 1-3 prototype iterations.

ERM & GRC

ERM, GRC Program Design: 1-2 weeks LOE over 3-4 week elapsed time for small and medium project complexity; 3-4 weeks LOE for large scale complexity over an elapsed time period of 6-8 weeks.

GRC Systems Engineering:  1-2 weeks for Prototyping/Requirements, 2-3 weeks Beta, Implementation per Process Area, 1-2 weeks Validation, and 1-2 weeks per quarter for recurring Compliance & Regulatory Validation (as required).

Data Governance 

Data Governance Programs:  These projects depend on the scope, complexity, nature and extent of regulatory requirements, and existing project team resources. One way we approach the scoping effort is to have 1-2 Days Requirements Workshop and to identify the suite of Process Engineering Services required to fulfill the objectives.  A high-level project plan is used in conjunction with the Architecture Maps to facilitate a “Go/No-Go” decision for each phase.

ERM Metrics Life Cycle:  2-4 weeks Design and Requirements, 1-3 months Beta, 1-2 months Validation.

Sarbanes Oxley

SOX Program Deployment Services:  2-3 months Prototyping/Requirements, Beta, and Implementation,  1-2 months Validation, 1-2 weeks per quarter recurring MSA Validation (as required).  Time requirements are less for program updates and more for green field deployments.

PDLC and SDLC Review Boards -  1-2 days per month or quarter for small – medium deployments, 3-5 days per month (or per quarter) for large scale projects.

Taxonomy Development and Technical Writing

Taxonomies:  Depends on the scope of the global domain, but, if for example, you take a taxonomy for Data Governance, then: 1-2 weeks Requirements, 4-6weeks Modeling, and 4-6  weeks Mapping, per Process Domain.
Technical Writing: Policy, Guidelines, Standards: 2-3 weeks per Process Area over a 4-6 week elapsed time period.  We have an extensive library of templates, which we can prototype rather quickly.  However, there is usually extensive customization required, no matter how proud we are of our library.

Training - We incorporate transfer of knowledge and training within our core service offerings, usually in Workshop mode.  However, we can provide stand-alone training in 1-2 day segments.