How I document, redesign and govern business processes. One manufacturing case, end to end: evidence classified, current state mapped, gaps registered, rules decided with owners, future state mapped with controls and the documentation handed over as a versioned process library.
Before and afterEvidenceCurrent stateDecisionsFuture stateRecord to reportDocumentation standardEngine builder and overhauler. Two plants, one repair depot, three legal entities. Live on Oracle Fusion Cloud Financials, Procurement, Inventory, Cost Management, Manufacturing and Order Management. The processes were never documented. The business runs steps outside the system and the ticket backlog grows. The job is to map what the business does, redesign it and govern it.
The whole redesign on one screen. The left column is what the evidence showed. The right column is what the six decisions produce. The two swimlanes below are the same process, procure to pay, before and after.
Figure 1. Before. Procure to pay, current state. Red badges are ticket counts. Five steps carry 261 of 412 tickets and two of them happen outside Oracle.
Figure 2. After. Procure to pay, future state. Gold diamonds are controls. Every decision has a named owner. Every hold has an owner and a clock.
| Step | Before | After |
|---|---|---|
| Create requisition | Requester emails the buyer. Buyer keys the purchase order after the fact. 31 tickets. | Requisition in Oracle. Approval rules by amount and cost center. Purchase order from the approved requisition. |
| Receive goods | Receipt in Oracle only when a purchase order exists. Otherwise a clipboard. 58 tickets. | Control: no purchase order, no receipt. Emergency receipts use a blanket purchase agreement per plant. |
| Match invoice | Three way match with tolerances at zero. Every variance is a hold. 67 tickets. | Tolerances set by the procurement director. Floor and ceiling by commodity. |
| Release hold | AP emails the buyer. Buyer emails the plant. Nobody releases. 44 tickets. | Price holds to the buyer. Quantity holds to the receiver. Three day SLA. Aging report daily. |
| Create accounting | Run at month end only. 39 tickets. | Nightly in draft, weekly in final. Exceptions cleared inside the week. |
| Accrue receipts | Accrue at period end. The job never runs. 22 tickets. | Accrue at receipt. Transfer from Receiving scheduled daily. Reconciliation weekly. |
Table 1. Procure to pay, step by step, before and after. Ticket counts are the evidence for each gap.
Every ticket was tagged on five dimensions: process, root cause class, business severity, Oracle object and map step. Most of the backlog is a few root causes reported many times. The classes separate people and process gaps from system defects, so each gap gets the right fix type.
Figure 3. Tickets by root cause class. More than half are training and process gaps.
Level 2 shows the five families and the Oracle modules under each. This is the table of contents for the process library. Every level 3 swimlane and level 4 work instruction hangs from one of these boxes.
Figure 4. Level 2 process families and the Oracle Cloud modules that carry them.
Procure to pay carried the most tickets, so it went first. The current state swimlane is Figure 1 above. Lanes are roles plus one lane for Oracle Cloud. Ticket counts sit on the steps. Each step with a badge becomes a line in the gap register.
| Step | Current state | Tickets | Gap |
|---|---|---|---|
| Create requisition | Requesters email the buyer. Buyer keys the purchase order. No requisition in Oracle. | 31 | No approval trail. Purchase order created after the goods arrive. |
| Receive goods | Dock receives in Oracle only when the purchase order exists. Otherwise the receipt is logged on a clipboard. | 58 | Receipt not in Oracle. No accrual. Inventory wrong. Invoice will fail match. |
| Match invoice | Three way match on. Tolerances at zero. Every price or quantity variance creates a hold. | 67 | Tolerances never set by the business. Holds have no owner. |
| Release hold | AP emails the buyer. Buyer emails the plant. Nobody releases. | 44 | No workflow. No SLA. Holds age past period end. |
| Create accounting | Create Accounting run at month end only. Errors found on the last day. | 39 | No daily run. Account rules missing for outside processing and for the depot cost center. |
| Accrue receipts | Accrue at period end selected. Create Uninvoiced Receipt Accruals never runs because Payables cannot close. | 22 | Circular block. Payables waits for holds. Accruals wait for Payables. |
Six decisions, one per gap. Each has a business owner and appears on the future state map as a control. The integrator builds to the decision and the acceptance criteria. This table is the change record for the process library.
| Decision | Rule | Owner |
|---|---|---|
| 1. No purchase order, no receipt. | Dock receives only against a purchase order line. Emergency receipts use a blanket purchase agreement per plant. | Plant manager |
| 2. Requisition in Oracle for every purchase. | Approval rules by amount and by cost center. | Controller |
| 3. Match tolerances set by the business. | Two percent price, five percent quantity, floor and ceiling by commodity. | Procurement director |
| 4. Hold release workflow. | Price holds to the buyer. Quantity holds to the receiver. Three day SLA. Aging report on the daily huddle. | AP manager |
| 5. Create Accounting nightly in draft, weekly in final. | Exceptions cleared inside the week. | Cost accountant |
| 6. Accrue at receipt. | Transfer Transactions from Receiving scheduled daily. Accrual reconciliation weekly. | Controller |
The future state swimlane is Figure 2 above. Every decision from step 4 is drawn as a gold control diamond. Every hand off has an owner. Level 4 work instructions are written from this map screen by screen. The training runs on them.
The same method applied to the second family. Open work orders, missing resource rates and month end only accounting runs were the gaps. The redesign moves that work to nightly jobs, daily exception review and a calendar with one owner per line.
| Step | Before | After |
|---|---|---|
| Close calendar | None. Finance starts the close when the last invoice arrives. | A calendar in the Oracle order with an owner per line. |
| Work order close | Work orders left open for weeks after completion. Scrap not recorded. | Complete within two days of last operation. Scrap at the operation. Weekly open work order report. |
| Resource rates | Rates loaded for the assembly plant only. | Rates for every plant and work center, reviewed each quarter. |
| Cost distributions | Run at month end. Errors surface on the last day. | Nightly. Exceptions cleared daily by the cost accountant. |
| Intercompany | Machining sells to assembly on a spreadsheet. | Transfer orders in Oracle. Transfer price per item class. |
| General Ledger | Never reached. | Closes on day five. |
Figure 5. The operating calendar that comes out of the record to report redesign. One owner per line.
Four levels. One notation per page. BPMN 2.0 for the swimlanes. The same standard on every engagement, so a new reader knows where to look.
Source, make, deliver, service, finance. One page for the CFO and the plant manager.
Procure to pay, order to cash, record to report, plan to produce, service and depot repair. Oracle modules named on each box.
BPMN 2.0 lanes by role plus an Oracle lane. Every decision, exception path, hand off and control drawn. Ticket counts on steps.
Screen by screen with the Oracle task name and the data required. The training and the support provider run on these.
Lucidchart for BPMN swimlanes with the Lucid MCP, so Claude drafts a map from an interview transcript and a ticket list. A private searchable process library over the engagement files. Oracle exception reports for the truth. Excel for the ticket analysis. A PPM dashboard that tracks each redesign from gap to decision, owner and measured result.
Business process reengineering, process management and process documentation for Oracle Cloud ERP. Remote, with travel.
chris.clark@clarkfamilyusa.comBack to the portfolio