DOC ROI
DOC ROI · REV OPERATIONS & SUPPLIER PORTAL

Rev Operations &
Supplier Portal

Turn governed orders and standard work into a visible operating system: configure Human, RPA, AI and robotic execution, measure productivity and customer response, govern suppliers and generate delivery-ready evidence.

Blank workspace · ready to start
Workspace controlsUse the example, start a new session or export the current view.

01 · Operational Inputs

Load the operating sources in process order. Every input keeps a direct reference to the DOC ROI pill where the data is created or governed.

CONTROL GATE · SOURCED INPUTS

Operational readiness

Load Example populates the source set and preserves its lineage for the demonstration case.

Orders ready for Operations

Financially released orders become the execution queue and can later run through the configured route.

OrderCustomerProductQtyOrder totalFinancial releaseOperations

02 · Productivity Setup

Select the operating model first. Clicking a model applies it immediately to the current service-order queue; there is no separate Apply action.

1 POINT = 1 STANDARD HOUR
Core rule. The baremo is the standard quantity of work. Technology changes the resource mix, supervision span and scalable capacity; it never erases the standard point.

Service-order result

The selected productivity model is applied immediately to every released service order and its Human / Digital point split is recalculated live.

MODEL APPLIED LIVE
OrderCustomerQtyProductivity modelRoute pointsHuman ptsDigital pts

Productivity baremo

Edit standard minutes or the economic rate. Standard points remain the common unit of work and feed both Warehouse execution and Delivery planning.

#Route stageTaskEvidenceStandard minPoints€/h€/unit

What each productivity indicator means

Read the model as capacity allocation, not as a redefinition of the standard work.

Standard work pointsThe baremo quantity of work. 1 point = 1 standard hour. Technology does not change it.
Human workloadThe share of standard work requiring a Human Operational Agent.
Digital workloadThe share executed by AI, automation, robotics or digitally assisted work.
Supervision capacityThe number of concurrent digital or robotic agents a human can supervise under the selected model.

03 · AI & RPA Productivity Workshop

Build, configure and test the operational productivity model directly on the warehouse Digital Twin. Drag capabilities onto route stages, tune their workload and economics in a movable configuration window, then run the order through the same circuit.

AI · RPA · ROBOTICS · PRODUCTIVITY
READY
IDEAL TEACHING WAREHOUSE · EDITABLE EXECUTION LAYER
RECEIVING DOCK
OUTBOUND PORT
Receiving & incoming control buffer
A
AISLE A · TRAVEL CORRIDOR
B
AISLE B · TRAVEL CORRIDOR
C
AISLE C · TRAVEL CORRIDOR
D
AISLE D · TRAVEL CORRIDOR
Packaging Room
PICK UP STAGING
PACK BENCH
DRAG → CONFIGURE → OK. Move route stages freely, drop capabilities onto a node, then run an order to illuminate the circuit.
The grey circuit is the configured route. During execution, the active segment turns blue and animated; completed segments turn green. The current node shows a spinner while work is being processed.

Route completeness

Each stage must have the capability to execute its physical or digital work. Hybrid and scalable stages also require visible human supervision.

Internal · Order Route Simulator

Execute one service order through the route exactly as configured in the Digital Twin. The circuit, Operational Agents, productivity and cost update while the order advances.

RUN ORDER · LIVE EXECUTION
Ready to validate.

Select an order and validate the route before execution.

Live productivity & economics

Productivity is standard work divided by human-equivalent work. The total economic envelope remains attached to the standard point while its allocation shifts between human execution and scalable digital capacity.

LIVE ORDER ROUTE · EXECUTION VIEW
RECEIVING DOCK
OUTBOUND PORT
Receiving & incoming control buffer
A
AISLE A · TRAVEL CORRIDOR
B
AISLE B · TRAVEL CORRIDOR
C
AISLE C · TRAVEL CORRIDOR
D
AISLE D · TRAVEL CORRIDOR
Packaging Room
PICK UP STAGING
PACK BENCH
Execution advances milestone by milestone. Active work spins; completed nodes and route segments turn green.

04 · Delivery Routing

Turn released customer orders into physical delivery routes. Prioritise recurrent customers through SPO, preserve arrival order for new customers, load real package volume into outsourced vehicles and calculate route points, time and cost before dispatch.

MADRID · LOAD · ROUTE · RUN

1 · Delivery planning assumptions

The current prototype uses a Madrid planning map by postcode and an editable road-distance factor. Values are planning assumptions, not a carrier tariff.

2 · Package output from Warehouse

Package dimensions become a Delivery input after Pick & Pack. The example uses editable planning dimensions and flags promotional packaging as a special package.

Standard package
××cm
Special / promotional package
××cm
Required source · order lineageCollections & Orders master file ↗
Required source · customer-facing templateSales · Product Experience HTML ↗
Master customer lineage not loaded.

3 · Delivery demand & SPO priority

Existing customers keep DOC ROI SPO priority. New customers remain visible as NEW and are sequenced by order arrival inside the route logic.

4 · Outsourced vehicle palette

Add a vehicle instance, then select it to open its characteristics and live cargo frame. Vehicle detail collapses completely when closed.

ACTIVE OUTSOURCED FLEETClick a vehicle to configure, load or reopen its route
0 VEHICLES
MADRID SERVICE MAPPostcode route canvas
MADRID HUB
SPO-1SPO-2SPO-3SPO-4NEWRETURN
Planning map: customer points are positioned from the delivery postcode/city in the loaded master file. Route distance uses a planning road factor over geographic distance; connect a mapping API later if production road-network routing is required.

5 · Driver Delivery Pack

Generate the vehicle-linked mobile assignment, goods handover, route agenda and customer delivery-close sheets. The licence plate is the operational key that connects vehicle → route → orders → delivery evidence.

MOBILE HTML · HANDOVER · SIGNATURE
CUSTOMER-FACING SOURCESales · Product Experience HTMLThe loaded example inherits brand colours, logos and product imagery from the Sales source. User uploads can replace the source HTML.Open Sales source ↗
LIVE PREVIEWVehicle assignment & delivery close

04 · Productivity & Satisfaction Report i

Connect execution evidence with post-order NPS to evaluate Operational Agents, service orders and development actions without losing the distinction between productivity and customer experience.

P · NPS · AGENT · ORDER · DEVELOPMENT
ACADEMIC IDEAProductivity and satisfaction answer different questions.P compares standard work with actual resource hours. NPS captures how the customer evaluated the completed order.
BRIDGEOrder ID connects the two evidence layers.The order is the safest operational bridge. Customer ID is used only as a fallback when it identifies a single order.
INTERPRETATIONAssociation is not causality.An agent can be associated with an order's NPS signal for teaching and management review, but the NPS result may reflect many parts of the experience.
MANAGEMENT OUTPUTClassify, then choose an action.The combined score supports a development action: Learning, Compliance or Excellence.

Route workload by Operational Agent i

Stacked workload by route stage for the current order mix.

Human agentDigital / AI agentRobotics / instrumentation

Executed order productivity & cost i

Each completed order shows its human/digital work split together with its economic envelope.

Operational Agent ledger i

Workload, supervision, scalable capacity and productivity signal.

Operational agentTypeModelStd pointsHuman-equivalent hCapacity factorProductivity index

Executed service orders i

Every completed simulator run is stored as an order-level productivity result.

OrderModelQtyPointsTime minHuman ptsDigital ptsCostRoute

Associated Order Quality Signal · NPS i

Import the post-order satisfaction file, join it to executed orders and create a transparent Productivity × Satisfaction score.

SOURCE · NPS ACTIVATION
1 · SATISFACTION INPUT

NPS evidence file i

WAITING FOR NPS

Request the NPS export after customers have had time to receive and evaluate their orders. The operational bridge is the order identifier.

order_id · customer_id · nps_date · nps_score · nps_class · comment
Open NPS Activation ↗
No NPS file loaded. Load Example provides solved order-linked NPS evidence.
2 · PRODUCTIVITY CLASSIFICATION

P bands around 1.00 i

LearningP < 1.001 point
ComplianceP = 1.002 points
ExcellenceP > 1.003 points
3 · SATISFACTION CLASSIFICATION

NPS classes i

Detractor0–61 point
Passive7–82 points
Promoter9–103 points
4 · SCORING MODEL

Productivity × Satisfaction i

EDITABLE
Score / 6 = 2 × [(P points × P weight) + (NPS points × NPS weight)]
5 · DEVELOPMENT ACTIONS

Configure the response i

Productivity × NPS matrix i

Order counts across the two dimensions. Use the matrix to see where operational efficiency and customer experience diverge.

Operational Agent classification & development plan i

Aggregate executed orders by primary Operational Agent, calculate the weighted score and assign an editable development action.

Academic caution. NPS reflects the whole customer experience. The primary Operational Agent is used here as an analytical bridge, not as a causal attribution of the score.
Operational AgentTypeOrdersAvg PP bandNPS responsesAssociated NPSScore / 6ClassificationDevelopment action

Order-level evidence bridge i

Trace every classification back to the order and its execution/satisfaction evidence.

OrderCustomerPrimary agentPP bandNPSNPS classScore / 6Result

05 · Supplier Portal

One operational portal with two controlled perspectives: the buyer/company workspace and the supplier workspace.

BUYER VIEW · SUPPLIER VIEW

Purchase orders

Orders issued or ready for human approval.

POSupplierItemQtyValueLeadStatus

Supplier invoice register

Portal demonstration layer. Amounts are PO values until an accounting invoice source is connected.

SupplierReferenceExpected amountInvoice statePayment terms
DEMO PORTAL RECORD · not an accounting source of truth.
SUP

Supplier

Select a supplier.

Purchase orders received

POItemQtyValueRequired saleable dateStatus

SLA commitments & evidence

06 · Outputs & Evidence

Export the finished evidence package: executable order labels, productivity evidence, supplier records, the standalone Supplier Portal HTML and the delivery-ready handoff.

DOWNLOAD DOCK
QR

Operations Labels → Delivery · HTML

Printable order-label pack preserving the upstream Collections & Orders QR when that source is loaded. The example carries the exact 46 QR labels supplied with the exercise.

CSV

Operations Label Register

Structured order/QR register for Delivery, warehouse display or downstream printing systems.

P

Productivity Report

Route stage, standard work, human/digital workload, technology assignments and designed cost.

CAC

Delivery Event → Call Center

Minimal delivery-completion handoff. The order is not duplicated because the Call Center already owns its commercial context.

SLA

Supplier SLA Snapshot

Supplier commitments, target, rule, evidence requirement and current portal state.

PO

Purchase Order Register

Supplier, item, quantity, monetary exposure, lead time and approval status.

Delivery event ledger

The Call Center receives only the delivery event required to update service and Customer Area context.

OrderCustomer keyStatusDelivery timestampCall Center handoffCustomer Area
METHODOLOGY AT THE END OF THE JOURNEY

DIIIP explains why operational evidence creates value

Orders, workload, routes, suppliers and delivery evidence become structured inputs for measurable productivity, service quality and economic decisions.

D
Data

Orders, customer keys, SPO priority, baremos, SLA commitments, vehicle data, route events and delivery evidence.

I
Information

The data is structured by operational stage, agent, route, supplier, vehicle, order and delivery state.

I
Intelligence

Rules interpret productivity, economic guardrails, capacity, route priority and SLA compliance.

I
Insights

The workshop reveals where capacity is released, where cost accumulates and where an operational exception requires attention.

P
Personalization Actions

SPO, customer context and route evidence activate differentiated service, delivery and post-sale actions.

KAI·ROI EQUATION · CUSTOMER EQUITY

This operational system creates execution evidence for the KAI·ROI layer

The workshop does not redefine KAI·ROI. It creates structured operational evidence that can support productivity, ROI, Customer Equity and defensible management decisions.

The formal KAI·ROI structure remains sovereign; this tool focuses on execution evidence.

EXECUTIVE RESOURCE

The KAI·ROI Equation Book

A concise guide to understand how data, ROI, Customer Equity and strategic decisions connect inside the DOC ROI ecosystem.

Inside the document:
  • What the KAI·ROI Equation is
  • Why Customer Equity matters
  • How ROI becomes a decision system
  • Why data must be monetized with purpose
Access the KAI·ROI Equation →
`; } function dispatchNoteHtml(v){const d=driverPackData(v),th=d.theme,rows=d.seq.map(s=>`${s.index}${escHtml(s.p.order_number)}${escHtml(s.spo)}${escHtml(s.name)}${s.boxes}${escHtml(s.dimensions)}`).join('');return `${escHtml(th.brand)} · Dispatch Note · ${escHtml(v.plate||v.id)}
GOODS HANDOVER / DISPATCH NOTE

${escHtml(th.brand)} · ${escHtml(v.id)}

Vehicle cargo release

The driver acknowledges receipt of the cargo listed below for the assigned route.

Licence plate${escHtml(v.plate||'PENDING')}
Driver${escHtml(v.driverName||'PENDING')}
Stops${d.m.stops}
Route cost${money(d.m.total)}
${rows}
#OrderSPOCustomerBoxesPackage
Warehouse release · name / signature / date
Driver receipt · name / signature / date
`} function deliverySheetsHtml(v){const d=driverPackData(v),th=d.theme;return `${escHtml(th.brand)} · Customer Delivery Sheets${d.seq.map(s=>`
DELIVERY & CUSTOMER ACCEPTANCE

${escHtml(v.plate||v.id)} · ${escHtml(v.driverName||'Driver')}

${escHtml(s.p.order_number)}

${escHtml(s.name)}
${escHtml(s.address)}
${escHtml(s.product)}
SKU ${escHtml(s.sku)} · Qty ${s.qty} · ${escHtml(s.dimensions)}
Delivery evidence
SPO ${escHtml(s.spo)} · Route ${escHtml(v.id)} · Stop ${s.index} · Route cost share ${money(s.costShare)}
Driver handover
Driver signature / timestamp
Customer acceptance
Customer signature / timestamp / incident note
`).join('')}`} window.downloadDriverMobileHTML=function(){const v=selectedVehicle();if(!v)return toast('Select a vehicle first.');if(!v.plate)return toast('Add the vehicle licence plate before generating the driver app.');downloadHtml(`DOC_ROI_DRIVER_${v.plate.replace(/[^A-Za-z0-9_-]+/g,'_')}.html`,driverMobileHtml(v))} window.downloadDispatchNoteHTML=function(){const v=selectedVehicle();if(!v)return toast('Select a vehicle first.');downloadHtml(`DOC_ROI_DISPATCH_NOTE_${(v.plate||v.id).replace(/[^A-Za-z0-9_-]+/g,'_')}.html`,dispatchNoteHtml(v))} window.downloadCustomerDeliverySheetsHTML=function(){const v=selectedVehicle();if(!v)return toast('Select a vehicle first.');downloadHtml(`DOC_ROI_CUSTOMER_DELIVERY_SHEETS_${(v.plate||v.id).replace(/[^A-Za-z0-9_-]+/g,'_')}.html`,deliverySheetsHtml(v))} const d1=document.getElementById('downloadDriverAppBtn'),d2=document.getElementById('downloadDispatchNoteBtn'),d3=document.getElementById('downloadDeliverySheetsBtn');if(d1)d1.onclick=window.downloadDriverMobileHTML;if(d2)d2.onclick=window.downloadDispatchNoteHTML;if(d3)d3.onclick=window.downloadCustomerDeliverySheetsHTML; /* Extend route/master outputs with licence plate and driver identity. */ const baseDeliveryRouteRows=window.deliveryRouteRows; window.deliveryRouteRows=function(){return baseDeliveryRouteRows().map(r=>{let v=deliveryVehicleById(r.route_id);return {...r,licence_plate:v?.plate||'',driver_id:v?.driverId||'',driver_name:v?.driverName||'',driver_phone:v?.driverPhone||''}})}; const baseBuildMaster=window.buildMasterTraceabilityRows; window.buildMasterTraceabilityRows=function(){return baseBuildMaster().map(r=>{let v=r.delivery_route_id?deliveryVehicleById(r.delivery_route_id):null;return {...r,delivery_licence_plate:v?.plate||'',delivery_driver_id:v?.driverId||'',delivery_driver_name:v?.driverName||'',delivery_driver_phone:v?.driverPhone||''}})}; /* Delivery planner now always refreshes the selected-vehicle and driver-pack frames. */ const baseRenderDeliveryPlanner=window.renderDeliveryPlanner; window.renderDeliveryPlanner=function(){ensureSalesState();baseRenderDeliveryPlanner();renderSelectedVehicleWorkspace();renderDriverPack()}; /* Initial refinement. */ ensureSalesState();renderDriverPack(); })();