IKON Operations Engine · Architecture Draft

Where promise becomes product.

Every accepted order enters one controlled production system. Materials, machines, people and information move together until a complete product leaves the factory exactly when promised.

On time · Every time · Right first time

Factory Control TowerEngine running

Demand signalApproved order

Engine targetR110m capacity

Release standardComplete & correct

The finished promiseCorrect product. Complete order. Committed date.

Right first time →

ControlOne plan. One priority.

FlowNo waiting. No surprises.

QualityBuilt in, not inspected in.

ImproveEvery loss feeds the next cycle.

Leader guide · from vision to traction

How to use the Engine Builder

The Engine Builder turns leadership thinking into a shared departmental vision, then gives the Seats, Data and Rocks GPTs the right context to convert that vision into execution.

What this tool is

A living vision and workshop platform. It shows what each departmental engine must become, what is missing today and what leadership may choose to build next.

What this tool is not

It is not the project-management system and it does not replace Strety. Seats, measurables, Issues and Rocks move into the appropriate GPT and then into the execution rhythm.

01

Vision Meeting

Define the department’s one-year vision: its purpose, desired future state, current reality, problems, capabilities and dependencies. Record the meeting.

02

Draft the Engine

Use the transcript to build the engine visual, component blueprints and proposed one-year finished state.

03

Pre-Quarterly Workshop

Leadership reviews each component, challenges the thinking and decides what must be built within the next 12 months or sooner.

04

Edit and Record

Edit the workshop blocks live. Add missing points, remove what does not belong and record the complete discussion.

05

Approve the Vision

Combine the original transcript, workshop transcript and edits. Update the engine and separate decisions from unresolved issues.

06

Build the Seats

Define the Seats and accountabilities required by the approved engine before discussing who should occupy them.

07

Build Data and Rocks

Choose the numbers that prove the engine works, then select the few quarterly Rocks that close the most important gaps.

08

Execute and Improve

Run the quarter in Strety, surface Issues, capture learning and feed material changes back into the engine vision.

The GPT sequence

Seats → Data → Rocks

Always follow this order. Rocks cannot be assigned properly until accountability is clear, and priorities should be informed by the numbers that expose the biggest gaps.

First

Seats GPT

Upload the approved engine pack and transcripts.

Define the Seats required
Set five major accountabilities
Clarify handoffs and capacity gaps
Define the Seat before the person

Output: approved Seats and accountabilities

Second

Data GPT

Add the approved Seats output to the engine context.

Select leading and lagging indicators
Give every number an owner
Set reporting frequency
Identify where baselines are required

Output: departmental Scorecard and outcome measures

Third

Rocks GPT

Use the engine, Seats and Data outputs together.

Identify the most important gaps
Select only a few quarterly priorities
Give every Rock one owner
Write a measurable Definition of Done

Output: focused 90-day Rocks ready for Strety

Do not try to build the whole engine in one quarter. The pre-quarterly identifies the 12-month destination. Quarterly planning selects the few parts that matter most now.

What leaders need

Workshop handoff checklist

Before the workshopRead the engine vision and relevant component blueprints. Bring corrections, missing issues and practical evidence.

During the workshopChallenge the content, edit the blocks and agree what the engine must look like within one year.

After the workshopProvide the original Architecture transcript, workshop transcript, edited blueprint and approved engine context.

Before executionComplete Seats first, Data second and Rocks third. Transfer the approved outputs into Strety.

Source of truth

Documents

Documents used to build and validate the Operations Engine.

Operations Architecture Transcript

Meeting held 18 August 2026 with Dominic Pedreiro, Morgan Fourie and Gordon Harrison. Primary source for the six-component structure, current constraints and machine-capacity discussion.

IKON V/TO

Provides the R44m one-year revenue plan, R110m three-year picture and R500m longer-term ambition.

Operations Scorecards & Rocks

Current evidence includes productivity, internal losses, lead times, quality failures, packaging defects, skills matrices and the Factory Feasibility Study.

EOS / Traction

Provides the operating discipline for Scorecards, L10s, Issues, Core Processes, Seats and quarterly Rocks.

Working status

This is a working proposal created from the Architecture Meeting. Leadership must validate the one-year finished state, component boundaries, targets, ownership and unresolved Issues before the engine becomes the approved Operations source of truth.

Leadership validation required