Skip to main content
Zemerc
Resources · implementation

One application, one accountable team, and one governed record.

Adopting an industrial application requires a defined set of decisions about ownership, validity, approval, migration and operation of the underlying record. The implementation sequence is structured around those decisions.

0
Implementation phases from scope through live use and optional expansion
0
Decision gates between phases
0
Application enters live use at the end of the initial implementation sequence

Implementation depends on client decisions as well as delivery work

The application can enforce who may change a record, what makes an entry valid, who may approve it and how corrections are controlled. Those rules must first be defined by the organisation responsible for the record.

How it is structured

6 phases, each closed by a defined gate.

A gate confirms that a required decision or artefact exists, such as an agreed record model, approved hierarchy or defined cut-over point. The next phase proceeds only when the required evidence is in place.

  1. Scope

    Define the governed record in scope and the boundary around it.

    What it settles
    • The class of record in scope and the part of the organisation accountable for it
    • Which existing systems remain in place
    • What must be demonstrable at the end of implementation and to whom
    Gate: One named governed record crossing one explicit boundary one accountable team and one stated boundary
  2. Structure

    Set up the hierarchy and master structures on which governed records depend.

    What it settles
    • The hierarchy from organisation, site, project or asset down to the level at which work is performed
    • Shared master entities such as equipment, personnel, organisations and locations use consistent identifiers where required
    • Roles, organisation scope and identity, because later access controls depend on them
    Gate: A hierarchy the responsible team recognises as its operating structure
  3. Rules

    Configure the controls the application will enforce.

    What it settles
    • Approval routes and segregation of duties enforced through authorised identities rather than informal practice
    • Controlled templates and revisions so executed records remain traceable to the version in force
    • Identify configuration that must be locked after approval where the application requires it
    Gate: Approved record-governance rules enforced by the application
  4. Migration

    Decide which historical records will migrate and which will remain in the existing system of record.

    What it settles
    • Which historical records migrate and which remain in their current system of record
    • Define how migrated records are marked so their provenance remains explicit.
    • The agreed point from which the application becomes authoritative for the governed record
    Gate: A stated cut-over date and a clear provenance rule
  5. Live period

    Run the application on representative or live work and compare derived positions with supporting records.

    What it settles
    • Whether office and field users operate from the same governed record where relevant
    • Whether each derived figure can be traced to its supporting records
    • Which figures the application deliberately does not produce and why
    Gate: Derived figures the responsible team is prepared to rely on and defend
  6. Widen

    Decide whether another application is required for a separate operational need.

    What it settles
    • Whether another team has an independent requirement for another application
    • Which named record, if any, must cross an application boundary
    • What remains outside the application boundary
Optional expansion

A second application is adopted only when another operational requirement justifies it.

There is no mandatory portfolio rollout. When another team adopts an application, the same implementation discipline is applied again. Integration is introduced only where a defined record genuinely crosses between the two areas of work.

  • Each application is configured around the structures and controls of its own accountable team.
  • Where applications exchange information, a named governed record crosses an explicit boundary rather than creating a shared application dependency.
  • An application that is never adopted creates no dependency for the applications that are in use.
Who is involved

Four implementation roles, with most responsibilities remaining client-owned.

The people who own, maintain and approve the record provide the decisions needed to validate the implementation.

  • Client responsibilities

    Record owner

    The current record owner helps define what constitutes a valid record and whether derived positions are acceptable.

  • Client responsibilities

    Approver

    The current authorised approver helps define segregation-of-duties requirements for the implemented workflow.

  • Client responsibilities

    Field users

    Field users who enter operational data where the work occurs are essential to validating whether the governed record works in practice.

  • Zemerc responsibilities

    Application team

    The Zemerc application team configures the product against agreed structures and explains supported and unsupported outcomes.

What implementation does not require

Four things the implementation model is designed to avoid.

The implementation model is designed to avoid unnecessary platform-wide transformation, forced portfolio adoption and process change that is unrelated to the record in scope.

  • No mandatory portfolio-wide rollout

    Implementation is application-specific. There is no phase in which the full portfolio must be adopted because no Zemerc application requires that.

  • No customer-specific software fork

    Applications are configured rather than customer-forked so clients remain on the supported product line.

  • No replacement of effective systems without a defined need

    Existing systems that continue to meet requirements can remain in place. Each Zemerc application governs a defined class of record and does not require unrelated systems to be replaced.

  • No figure without a supportable basis

    Migration does not create missing history. Where no supporting record exists for a period, that limitation remains explicit.

Discuss a first application

Bring one register, project or asset. The relevant application and the first implementation decisions can then be identified from the governed record and its controls.