PRINTBOX LEARNING CENTRE

Complete tutorials & help

Role-specific, step-by-step guidance for setting up and operating PRINTBOX safely. You opened help from worker.

START HERE

Before your first transaction

1

Confirm identity

Use your own login and verify the active organisation.

2

Confirm access

Check package, role, employee link and operating scope.

3

Confirm masters

Use approved customers, products, materials, machines and rates.

4

Follow lifecycle

Create, submit, approve, release and reverse through governed actions.

END-TO-END FLOW

The authorised operational sequence

Enquiry → Engineering → Costing → Quotation / PO → Planning / MRP → Receiving / QC → Production → Final QC → Dispatch → Finance

Do not create downstream records to bypass a missing approval, credit decision, competency, safety check or quality disposition.

ROLE PLAYBOOKS

Detailed tutorials for every user

Open a guide, complete the steps in order, then use its direct workspace links. Visibility still follows your approved access.

OWNER

Owner / administrator

Build the organisation and access foundation before users transact.

  1. Confirm the account creator, organisation code, company story, contact details and branding.
  2. Select the tenant package and review enabled workspaces and capacity limits.
  3. Invite users by email; assign role, employee link, package and plant/warehouse/department scope.
  4. Create plants, warehouses, departments, machines, shifts and governed master data.
  5. Run System Health and Production Readiness; complete a realistic pilot and evidence-based UAT.
SALES

Sales / client service

Move an approved customer requirement into a controlled order.

  1. Choose the correct customer, plant and delivery context.
  2. Record enquiry title, product family, quantity, required date, source and next action.
  3. Request technical input and confirm the specification/artwork baseline.
  4. Create a governed costing version and quotation.
  5. Validate the customer PO, credit status and amendments before releasing the sales order.
ESTIMATOR

Estimator / costing

Create a transparent, version-controlled commercial baseline.

  1. Select the product/specification and order quantity.
  2. Confirm material, layout/yield, process routing, waste and rate sources.
  3. Enter machine, labour, outsourcing and freight assumptions.
  4. Compare scenarios and review the margin waterfall.
  5. Save the version with a reason and submit it through the approval action.
PLANNER

Planner / MRP

Turn released demand into a feasible, controlled production plan.

  1. Review released jobs, required dates and priorities.
  2. Run demand/material planning and resolve shortage signals.
  3. Create work orders and confirm operations, quantities and dependencies.
  4. Schedule against machine, shift, material, tooling, competency and maintenance constraints.
  5. Publish the plan and monitor forecast risk; never overwrite actual production progress.
STORES

Stores / purchasing

Receive and move material with complete lot and quality traceability.

  1. Work from an approved purchase order and line.
  2. Record warehouse, received quantity, supplier batch/reel and weight details.
  3. Create the internal lot/reel identity and retain certificate evidence.
  4. Send inspection-controlled material to QC and respect quarantine.
  5. Reserve and issue only released stock to authorised jobs; record every movement.
MANAGER

Production manager / supervisor

Run each shift using authorised jobs, capable people and ready machines.

  1. Review the current shift, assigned jobs, readiness, material and exceptions.
  2. Confirm worker competency and machine authorisation before assignment.
  3. Open the operation and brief targets, instructions, quality plan and safety controls.
  4. Monitor good, reject, rework and downtime entries; investigate exceptions.
  5. Approve controlled entries and complete an auditable shift handover.
WORKER

Worker / operator

Execute assigned work and record truthful production evidence.

  1. Sign in with your own identity and choose the intended organisation.
  2. Open only the assigned operation and confirm job, machine and target.
  3. Record good output, reject, rework and downtime when they occur.
  4. Report blockers, safety issues and quality deviations immediately.
  5. Submit the entry and wait for controlled approval or handover.
QUALITY

Quality / laboratory

Apply the approved inspection plan and evidence-led disposition.

  1. Select inspection type, reference, item, lot and calibrated instrument.
  2. Confirm sample size, characteristic, target and tolerances.
  3. Record the actual result and required evidence.
  4. Choose Pass, Hold or Reject from evidence—not production pressure.
  5. Create an NCR for deviation and release only through authorised disposition.
FINANCE

Finance / accounts

Reconcile authorised operational events before posting and closing.

  1. Review approved commercial, purchasing, production and dispatch events.
  2. Reconcile receivables, payables, stock and job-cost references.
  3. Post only balanced and authorised batches with source evidence.
  4. Compare realised cost and margin with the governed baseline.
  5. Close periods only after reconciliation; reopen through the controlled action.
PORTAL

Customer / supplier / partner

Collaborate through the external portal without internal factory access.

  1. Accept the company invitation using the intended email account.
  2. Choose the correct active company when you belong to more than one.
  3. Customers submit enquiries, decisions, POs, forecasts and complaints.
  4. Suppliers confirm RFQs/POs, ASNs, invoices and certificate evidence.
  5. Keep external company membership separate from employee roles and scope.

COMPLETE APPLICATION HANDBOOK

The PRINTBOX application bible

This reference documents all 82 operational workspaces. Start with the purpose, complete the prerequisites, follow the steps in order, and retain the stated evidence. Package, role and operating-scope controls still determine what you may open or change.

START HERE

Start Here

1 workspaces
SCR-NAV-001

Complete Product Navigator

See the complete PRINTBOX v8 operational catalogue in one place, including enabled and package-locked workspaces.

Who: All authenticated usersDevice: ResponsiveWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

See the complete PRINTBOX v8 operational catalogue in one place, including enabled and package-locked workspaces. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • 82 operational workspaces: review or complete this region in the context of the selected record.
  • 33 requirement epics: review or complete this region in the context of the selected record.
  • 264 canonical requirements: review or complete this region in the context of the selected record.
  • Enabled / locked state: review or complete this region in the context of the selected record.
  • Role & form-factor map: review or complete this region in the context of the selected record.
  • Package and access guidance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Complete Product Navigator, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are 82 operational workspaces, 33 requirement epics, 264 canonical requirements, Enabled / locked state, Role & form-factor map, Package and access guidance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Open workspace: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Filter enabled: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Show locked: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Configure access: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Title: the governed value shown or recorded for this workspace; verify it against the source record.
  • Group: the governed value shown or recorded for this workspace; verify it against the source record.
  • Role: the governed value shown or recorded for this workspace; verify it against the source record.
  • Feature: the governed value shown or recorded for this workspace; verify it against the source record.
  • Allowed: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

COMMAND & CONTROL

Command & Control

1 workspaces
SCR-OWN-001

Owner Command Centre

Executive command centre for plant health, sales, delivery risk, shortages, cash, quality, OEE and approvals.

Who: Owner / DirectorDevice: Desktop / TabletWorkflow: WF-ANA-01Control family: ANA
Why this workspace exists

Executive command centre for plant health, sales, delivery risk, shortages, cash, quality, OEE and approvals. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • KPI cards: review or complete this region in the context of the selected record.
  • Plant health: review or complete this region in the context of the selected record.
  • Sales pipeline: review or complete this region in the context of the selected record.
  • Jobs at risk: review or complete this region in the context of the selected record.
  • Material shortages: review or complete this region in the context of the selected record.
  • Cash & margin: review or complete this region in the context of the selected record.
  • Quality & OEE: review or complete this region in the context of the selected record.
  • Approvals & alerts: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Owner Command Centre, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are KPI cards, Plant health, Sales pipeline, Jobs at risk, Material shortages, Cash & margin, Quality & OEE, Approvals & alerts.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Drill down: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Subscribe: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Active Jobs: the governed value shown or recorded for this workspace; verify it against the source record.
  • Overdue Jobs: the governed value shown or recorded for this workspace; verify it against the source record.
  • Today Production: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quality Rate: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ANA-001 · PBX-ANA-002 · PBX-ANA-003 · PBX-ANA-004 · PBX-ANA-005 · PBX-ANA-006 · PBX-ANA-007 · PBX-ANA-008

COMMERCIAL

Commercial

3 workspaces
SCR-COM-001

Enquiry Workspace

Capture a qualified customer requirement and move it into engineering and costing without losing source evidence.

Who: Sales / Client ServiceDevice: DesktopWorkflow: WF-COM-01Control family: COM
Why this workspace exists

Capture a qualified customer requirement and move it into engineering and costing without losing source evidence. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Client & contact: review or complete this region in the context of the selected record.
  • Specification summary: review or complete this region in the context of the selected record.
  • Quantity & dates: review or complete this region in the context of the selected record.
  • Files & artwork: review or complete this region in the context of the selected record.
  • Activity: review or complete this region in the context of the selected record.
  • Qualification checklist: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Enquiry Workspace, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Client & contact, Specification summary, Quantity & dates, Files & artwork, Activity, Qualification checklist.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create enquiry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create costing: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Request technical input: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Hold / lose: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Enquiry Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Client Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Title: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Family: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Required Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-COM-001 · PBX-COM-002 · PBX-COM-003 · PBX-COM-004 · PBX-COM-005 · PBX-COM-006 · PBX-COM-007 · PBX-COM-008

SCR-CST-001

Costing Builder

Explainable estimate workspace with quantity, material/layout, process costs, waste, scenarios, margin waterfall and version control.

Who: EstimatorDevice: DesktopWorkflow: WF-CST-01Control family: CST
Why this workspace exists

Explainable estimate workspace with quantity, material/layout, process costs, waste, scenarios, margin waterfall and version control. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Specification: review or complete this region in the context of the selected record.
  • Layout & yield: review or complete this region in the context of the selected record.
  • Materials: review or complete this region in the context of the selected record.
  • Operations: review or complete this region in the context of the selected record.
  • Rate sources: review or complete this region in the context of the selected record.
  • Waste: review or complete this region in the context of the selected record.
  • Scenarios: review or complete this region in the context of the selected record.
  • Margin waterfall: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Costing Builder, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Specification, Layout & yield, Materials, Operations, Rate sources, Waste, Scenarios, Margin waterfall.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Calculate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Compare: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Save version: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit approval: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create quote: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Version Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Total Cost: the governed value shown or recorded for this workspace; verify it against the source record.
  • Selling Price: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-CST-001 · PBX-CST-002 · PBX-CST-003 · PBX-CST-004 · PBX-CST-005 · PBX-CST-006 · PBX-CST-007 · PBX-CST-008

SCR-SAL-002

Sales Order, Credit & Amendment Control

Control PO comparison, sales-order release, credit exposure, blanket/call-off demand and commercial amendments.

Who: Sales / FinanceDevice: DesktopWorkflow: WF-COM-01Control family: COM
Why this workspace exists

Control PO comparison, sales-order release, credit exposure, blanket/call-off demand and commercial amendments. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • PO comparison: review or complete this region in the context of the selected record.
  • Credit exposure: review or complete this region in the context of the selected record.
  • Sales order: review or complete this region in the context of the selected record.
  • Delivery schedule: review or complete this region in the context of the selected record.
  • Amendments: review or complete this region in the context of the selected record.
  • Cancellation liability: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Sales Order, Credit & Amendment Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are PO comparison, Credit exposure, Sales order, Delivery schedule, Amendments, Cancellation liability.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Compare PO: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release order: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve credit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Amend: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Order Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Client Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Customer Po: the governed value shown or recorded for this workspace; verify it against the source record.
  • Delivery Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Total Value: the governed value shown or recorded for this workspace; verify it against the source record.
  • Credit Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Po Comparison Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Production Release Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-COM-001 · PBX-COM-002 · PBX-COM-003 · PBX-COM-004 · PBX-COM-005 · PBX-COM-006 · PBX-COM-007 · PBX-COM-008

ENGINEERING

Engineering

5 workspaces
SCR-ENG-001

Product Engineering & Prepress

Control product revision, technical specification, artwork/dieline, BOM, route, QC plan and release evidence.

Who: Engineer / PrepressDevice: DesktopWorkflow: WF-ENG-01Control family: ENG
Why this workspace exists

Control product revision, technical specification, artwork/dieline, BOM, route, QC plan and release evidence. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Revision tree: review or complete this region in the context of the selected record.
  • Technical fields: review or complete this region in the context of the selected record.
  • Artwork & dieline: review or complete this region in the context of the selected record.
  • BOM: review or complete this region in the context of the selected record.
  • Route: review or complete this region in the context of the selected record.
  • QC plan: review or complete this region in the context of the selected record.
  • Approvals: review or complete this region in the context of the selected record.
  • Obsolete controls: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Product Engineering & Prepress, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Revision tree, Technical fields, Artwork & dieline, BOM, Route, QC plan, Approvals, Obsolete controls.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create product: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Clone revision: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Compare: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Family: the governed value shown or recorded for this workspace; verify it against the source record.
  • Revision: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ENG-001 · PBX-ENG-002 · PBX-ENG-003 · PBX-ENG-004 · PBX-ENG-005 · PBX-ENG-006 · PBX-ENG-007 · PBX-ENG-008

SCR-ART-001

Artwork, Proof & Preflight Inbox

Run artwork preflight, compare revisions, govern proof approval and block obsolete production files.

Who: Prepress / Client ServiceDevice: DesktopWorkflow: WF-ENG-01Control family: ENG
Why this workspace exists

Run artwork preflight, compare revisions, govern proof approval and block obsolete production files. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Artwork inbox: review or complete this region in the context of the selected record.
  • Preflight checks: review or complete this region in the context of the selected record.
  • Revision compare: review or complete this region in the context of the selected record.
  • Proof approval: review or complete this region in the context of the selected record.
  • Barcode/legal text: review or complete this region in the context of the selected record.
  • Plate/die release: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Artwork, Proof & Preflight Inbox, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Artwork inbox, Preflight checks, Revision compare, Proof approval, Barcode/legal text, Plate/die release.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Run preflight: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Compare revisions: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Internal approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Client approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Artwork Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Revision No: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Client Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Preflight Result: the governed value shown or recorded for this workspace; verify it against the source record.
  • Internal Approval Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Client Approval Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ENG-001 · PBX-ENG-002 · PBX-ENG-003 · PBX-ENG-004 · PBX-ENG-005 · PBX-ENG-006 · PBX-ENG-007 · PBX-ENG-008

SCR-ECR-001

Engineering Change & Revision Control

Assess cost, stock, jobs and client impact before releasing a new product/BOM/route/QC revision.

Who: Engineer / QualityDevice: DesktopWorkflow: WF-ENG-01Control family: ENG
Why this workspace exists

Assess cost, stock, jobs and client impact before releasing a new product/BOM/route/QC revision. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Change request: review or complete this region in the context of the selected record.
  • Impact analysis: review or complete this region in the context of the selected record.
  • Affected jobs: review or complete this region in the context of the selected record.
  • Stock obsolescence: review or complete this region in the context of the selected record.
  • Approval: review or complete this region in the context of the selected record.
  • Effective version: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Engineering Change & Revision Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Change request, Impact analysis, Affected jobs, Stock obsolescence, Approval, Effective version.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Assess impact: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Trial: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Change Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Revision: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Effective From: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ENG-001 · PBX-ENG-002 · PBX-ENG-003 · PBX-ENG-004 · PBX-ENG-005 · PBX-ENG-006 · PBX-ENG-007 · PBX-ENG-008

SCR-TOL-001

Tooling, Plates, Dies & Asset Life

Track tool revision, custody, condition, impression life, repair, storage and client ownership.

Who: Tool Store / PrepressDevice: Desktop / TabletWorkflow: WF-ENG-01Control family: ENG
Why this workspace exists

Track tool revision, custody, condition, impression life, repair, storage and client ownership. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Tool register: review or complete this region in the context of the selected record.
  • Revision match: review or complete this region in the context of the selected record.
  • Issue/custody: review or complete this region in the context of the selected record.
  • Usage counter: review or complete this region in the context of the selected record.
  • Inspection/repair: review or complete this region in the context of the selected record.
  • Recovery balance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Tooling, Plates, Dies & Asset Life, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Tool register, Revision match, Issue/custody, Usage counter, Inspection/repair, Recovery balance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Reserve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Return: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Inspect: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Tool Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Tool Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Location: the governed value shown or recorded for this workspace; verify it against the source record.
  • Condition Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ENG-001 · PBX-ENG-002 · PBX-ENG-003 · PBX-ENG-004 · PBX-ENG-005 · PBX-ENG-006 · PBX-ENG-007 · PBX-ENG-008

SCR-NPI-001

Sample Development & NPI

Control design brief, prototype, test, client feedback, tooling/development recovery and commercial release.

Who: Engineering / SalesDevice: DesktopWorkflow: WF-ENG-01Control family: ENG
Why this workspace exists

Control design brief, prototype, test, client feedback, tooling/development recovery and commercial release. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Design brief: review or complete this region in the context of the selected record.
  • Structure/dieline: review or complete this region in the context of the selected record.
  • Cost: review or complete this region in the context of the selected record.
  • Prototype: review or complete this region in the context of the selected record.
  • Test evidence: review or complete this region in the context of the selected record.
  • Client approval: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Sample Development & NPI, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Design brief, Structure/dieline, Cost, Prototype, Test evidence, Client approval.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create sample: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Request approval: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Commercial release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Family: the governed value shown or recorded for this workspace; verify it against the source record.
  • Revision: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ENG-001 · PBX-ENG-002 · PBX-ENG-003 · PBX-ENG-004 · PBX-ENG-005 · PBX-ENG-006 · PBX-ENG-007 · PBX-ENG-008

PLANNING

Planning

1 workspaces
SCR-PLN-001

Finite Planning Board

Sequence work against real machine, shift, material, tooling, manpower and maintenance constraints.

Who: Production PlannerDevice: Desktop / Large displayWorkflow: WF-PROD-01Control family: PROD
Why this workspace exists

Sequence work against real machine, shift, material, tooling, manpower and maintenance constraints. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Unscheduled jobs: review or complete this region in the context of the selected record.
  • Machine lanes: review or complete this region in the context of the selected record.
  • Shift capacity: review or complete this region in the context of the selected record.
  • Material readiness: review or complete this region in the context of the selected record.
  • Tool readiness: review or complete this region in the context of the selected record.
  • Skill availability: review or complete this region in the context of the selected record.
  • Dependencies: review or complete this region in the context of the selected record.
  • Risk alerts: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Finite Planning Board, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Unscheduled jobs, Machine lanes, Shift capacity, Material readiness, Tool readiness, Skill availability, Dependencies, Risk alerts.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Drag schedule: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Split: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Alternate machine: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Explode job: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Publish: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Machine Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Start: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned End: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PROD-001 · PBX-PROD-002 · PBX-PROD-003 · PBX-PROD-004 · PBX-PROD-005 · PBX-PROD-006 · PBX-PROD-007 · PBX-PROD-008

PLANNING & SUPPLY

Planning & Supply

3 workspaces
SCR-MRP-001

MRP Action Centre

Time-phase demand and supply, expose shortage pegging and turn recommendations into controlled purchase/transfer/substitution/reschedule actions.

Who: Planner / PurchaseDevice: DesktopWorkflow: WF-MRP-01Control family: MRP
Why this workspace exists

Time-phase demand and supply, expose shortage pegging and turn recommendations into controlled purchase/transfer/substitution/reschedule actions. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Demand / supply timeline: review or complete this region in the context of the selected record.
  • Projected balance: review or complete this region in the context of the selected record.
  • Shortage: review or complete this region in the context of the selected record.
  • Pegging: review or complete this region in the context of the selected record.
  • Suggested actions: review or complete this region in the context of the selected record.
  • Impacted jobs: review or complete this region in the context of the selected record.
  • Lead-time controls: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title MRP Action Centre, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Demand / supply timeline, Projected balance, Shortage, Pegging, Suggested actions, Impacted jobs, Lead-time controls.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Run MRP: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve PR: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Transfer: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Substitute: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reschedule: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Required Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Required Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Projected Available: the governed value shown or recorded for this workspace; verify it against the source record.
  • Shortage Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Recommended Action: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-MRP-001 · PBX-MRP-002 · PBX-MRP-003 · PBX-MRP-004 · PBX-MRP-005 · PBX-MRP-006 · PBX-MRP-007 · PBX-MRP-008

SCR-PUR-001

Purchasing & Subcontract Control

Convert shortages into PR/RFQ/PO/GRN and reconcile material sent to and returned from subcontract vendors.

Who: Purchase / PlannerDevice: DesktopWorkflow: WF-PUR-01Control family: PUR
Why this workspace exists

Convert shortages into PR/RFQ/PO/GRN and reconcile material sent to and returned from subcontract vendors. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Requisitions: review or complete this region in the context of the selected record.
  • RFQ comparison: review or complete this region in the context of the selected record.
  • Purchase orders: review or complete this region in the context of the selected record.
  • GRN/QC: review or complete this region in the context of the selected record.
  • Job-work material: review or complete this region in the context of the selected record.
  • Supplier scorecard: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Purchasing & Subcontract Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Requisitions, RFQ comparison, Purchase orders, GRN/QC, Job-work material, Supplier scorecard.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create PR: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue RFQ: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create PO: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve PO: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Receive GRN: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Inspect GRN: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Required Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Required Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PUR-001 · PBX-PUR-002 · PBX-PUR-003 · PBX-PUR-004 · PBX-PUR-005 · PBX-PUR-006 · PBX-PUR-007 · PBX-PUR-008

SCR-DMD-001

Demand, S&OP, MPS, ATP & CTP

Convert forecasts, blanket orders and constraints into executable supply plans and credible customer promise dates.

Who: Planner / Sales / OwnerDevice: DesktopWorkflow: WF-MRP-01Control family: MRP
Why this workspace exists

Convert forecasts, blanket orders and constraints into executable supply plans and credible customer promise dates. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Forecast: review or complete this region in the context of the selected record.
  • Blanket/call-off: review or complete this region in the context of the selected record.
  • S&OP gaps: review or complete this region in the context of the selected record.
  • MPS: review or complete this region in the context of the selected record.
  • ATP: review or complete this region in the context of the selected record.
  • CTP promise: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Demand, S&OP, MPS, ATP & CTP, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Forecast, Blanket/call-off, S&OP gaps, MPS, ATP, CTP promise.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Approve plan: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Consume forecast: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Promise date: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reschedule: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Recommendation Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Need By: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-MRP-001 · PBX-MRP-002 · PBX-MRP-003 · PBX-MRP-004 · PBX-MRP-005 · PBX-MRP-006 · PBX-MRP-007 · PBX-MRP-008

STORES & WAREHOUSE

Stores & Warehouse

4 workspaces
SCR-STR-001

Store Receiving

Scan receiving documents and create controlled lot/reel records with inspection and quarantine state.

Who: Stores / QCDevice: Mobile / TabletWorkflow: WF-INV-01Control family: INV
Why this workspace exists

Scan receiving documents and create controlled lot/reel records with inspection and quarantine state. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • PO / ASN scan: review or complete this region in the context of the selected record.
  • Supplier & item: review or complete this region in the context of the selected record.
  • Lot / reel identity: review or complete this region in the context of the selected record.
  • Weight / quantity: review or complete this region in the context of the selected record.
  • Photo evidence: review or complete this region in the context of the selected record.
  • Quarantine label: review or complete this region in the context of the selected record.
  • Incoming inspection: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Store Receiving, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are PO / ASN scan, Supplier & item, Lot / reel identity, Weight / quantity, Photo evidence, Quarantine label, Incoming inspection.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Receive: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Print label: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Send inspection: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-INV-001 · PBX-INV-002 · PBX-INV-003 · PBX-INV-004 · PBX-INV-005 · PBX-INV-006 · PBX-INV-007 · PBX-INV-008

SCR-STR-002

Material Issue

Issue only approved/reserved material to a job or operation with partial issue and substitution control.

Who: StoresDevice: Mobile / TabletWorkflow: WF-INV-01Control family: INV
Why this workspace exists

Issue only approved/reserved material to a job or operation with partial issue and substitution control. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Job scan: review or complete this region in the context of the selected record.
  • BOM demand: review or complete this region in the context of the selected record.
  • Reserved lots: review or complete this region in the context of the selected record.
  • Available alternatives: review or complete this region in the context of the selected record.
  • Quantity / weight: review or complete this region in the context of the selected record.
  • Return balance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Material Issue, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Job scan, BOM demand, Reserved lots, Available alternatives, Quantity / weight, Return balance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Partial issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Substitute request: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Return: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-INV-001 · PBX-INV-002 · PBX-INV-003 · PBX-INV-004 · PBX-INV-005 · PBX-INV-006 · PBX-INV-007 · PBX-INV-008

SCR-MAT-001

Reel, Sheet, Ink & Chemical Control

Control dimensioned materials, partial reels, offcuts, formulas, mix batches, chemicals, expiry and job issue/return.

Who: Stores / Ink KitchenDevice: Desktop / TabletWorkflow: WF-INV-01Control family: INV
Why this workspace exists

Control dimensioned materials, partial reels, offcuts, formulas, mix batches, chemicals, expiry and job issue/return. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Reels & sheets: review or complete this region in the context of the selected record.
  • Partial balances: review or complete this region in the context of the selected record.
  • Offcuts: review or complete this region in the context of the selected record.
  • Ink formulas: review or complete this region in the context of the selected record.
  • Mix batches: review or complete this region in the context of the selected record.
  • Chemical/SDS status: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Reel, Sheet, Ink & Chemical Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Reels & sheets, Partial balances, Offcuts, Ink formulas, Mix batches, Chemical/SDS status.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Receive: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Weigh return: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Mix batch: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Lot Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Warehouse Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-INV-001 · PBX-INV-002 · PBX-INV-003 · PBX-INV-004 · PBX-INV-005 · PBX-INV-006 · PBX-INV-007 · PBX-INV-008

SCR-INV-003

Physical Inventory & Cycle Count

Plan blind counts, recount variances, investigate causes and post controlled stock adjustments.

Who: Stores / AuditorDevice: Mobile / DesktopWorkflow: WF-INV-01Control family: INV
Why this workspace exists

Plan blind counts, recount variances, investigate causes and post controlled stock adjustments. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Count plan: review or complete this region in the context of the selected record.
  • Blind count: review or complete this region in the context of the selected record.
  • Recount: review or complete this region in the context of the selected record.
  • Variance: review or complete this region in the context of the selected record.
  • Investigation: review or complete this region in the context of the selected record.
  • Approved adjustment: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Physical Inventory & Cycle Count, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Count plan, Blind count, Recount, Variance, Investigation, Approved adjustment.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start blind count: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit count: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Recount variance: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve adjustment: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-INV-001 · PBX-INV-002 · PBX-INV-003 · PBX-INV-004 · PBX-INV-005 · PBX-INV-006 · PBX-INV-007 · PBX-INV-008

SHOP FLOOR

Shop Floor

4 workspaces
SCR-MGR-001

Manager Home

Current-shift command view for assigned jobs, team, readiness, exceptions, approvals and handover.

Who: Production ManagerDevice: MobileWorkflow: WF-PROD-01Control family: PROD
Why this workspace exists

Current-shift command view for assigned jobs, team, readiness, exceptions, approvals and handover. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Current shift: review or complete this region in the context of the selected record.
  • Assigned jobs: review or complete this region in the context of the selected record.
  • Ready to start: review or complete this region in the context of the selected record.
  • Material pending: review or complete this region in the context of the selected record.
  • In progress: review or complete this region in the context of the selected record.
  • Day-end pending: review or complete this region in the context of the selected record.
  • Exceptions: review or complete this region in the context of the selected record.
  • Handover: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Manager Home, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Current shift, Assigned jobs, Ready to start, Material pending, In progress, Day-end pending, Exceptions, Handover.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Open job: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Report issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve entries: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Open operation execution: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PROD-001 · PBX-PROD-002 · PBX-PROD-003 · PBX-PROD-004 · PBX-PROD-005 · PBX-PROD-006 · PBX-PROD-007 · PBX-PROD-008

SCR-MGR-002

Operation Execution

Run an operation with counter, output, material/tool, downtime, QC and completion controls.

Who: Manager / OperatorDevice: Mobile / TabletWorkflow: WF-PROD-01Control family: PROD
Why this workspace exists

Run an operation with counter, output, material/tool, downtime, QC and completion controls. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Job & operation: review or complete this region in the context of the selected record.
  • Target / balance: review or complete this region in the context of the selected record.
  • Material & tool: review or complete this region in the context of the selected record.
  • Counters: review or complete this region in the context of the selected record.
  • Good / reject / rework: review or complete this region in the context of the selected record.
  • Downtime: review or complete this region in the context of the selected record.
  • QC first piece: review or complete this region in the context of the selected record.
  • Evidence & sync: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Operation Execution, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Job & operation, Target / balance, Material & tool, Counters, Good / reject / rework, Downtime, QC first piece, Evidence & sync.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Pause: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Save entry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Request QC: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Complete: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PROD-001 · PBX-PROD-002 · PBX-PROD-003 · PBX-PROD-004 · PBX-PROD-005 · PBX-PROD-006 · PBX-PROD-007 · PBX-PROD-008

SCR-WRK-001

Worker Kiosk

Scan/PIN into only assigned work with large controls, safety acknowledgement, output and blocker reporting.

Who: WorkerDevice: Shared kiosk / MobileWorkflow: WF-WRK-01Control family: WRK
Why this workspace exists

Scan/PIN into only assigned work with large controls, safety acknowledgement, output and blocker reporting. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • PIN / QR: review or complete this region in the context of the selected record.
  • Assignment: review or complete this region in the context of the selected record.
  • Target: review or complete this region in the context of the selected record.
  • Instructions: review or complete this region in the context of the selected record.
  • Current output: review or complete this region in the context of the selected record.
  • Safety: review or complete this region in the context of the selected record.
  • Help / blocker: review or complete this region in the context of the selected record.
  • Offline / last sync: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Worker Kiosk, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are PIN / QR, Assignment, Target, Instructions, Current output, Safety, Help / blocker, Offline / last sync.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start / stop: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Quantity: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Defect: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Acknowledge: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-WRK-001 · PBX-WRK-002 · PBX-WRK-003 · PBX-WRK-004 · PBX-WRK-005 · PBX-WRK-006 · PBX-WRK-007 · PBX-WRK-008

SCR-SHF-001

Shift Handover & Andon

Transfer job, material, machine, quality, people and safety responsibility between shifts with acknowledgement.

Who: Supervisor / ManagerDevice: Mobile / Large displayWorkflow: WF-PROD-01Control family: PROD
Why this workspace exists

Transfer job, material, machine, quality, people and safety responsibility between shifts with acknowledgement. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Running jobs: review or complete this region in the context of the selected record.
  • Material state: review or complete this region in the context of the selected record.
  • Machine/tool: review or complete this region in the context of the selected record.
  • Quality exceptions: review or complete this region in the context of the selected record.
  • People: review or complete this region in the context of the selected record.
  • Safety/Andon: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Shift Handover & Andon, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Running jobs, Material state, Machine/tool, Quality exceptions, People, Safety/Andon.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Raise Andon: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit handover: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Acknowledge: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Escalate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PROD-001 · PBX-PROD-002 · PBX-PROD-003 · PBX-PROD-004 · PBX-PROD-005 · PBX-PROD-006 · PBX-PROD-007 · PBX-PROD-008

QUALITY

Quality

4 workspaces
SCR-QC-001

Inspection Entry

Execute sampling/test plans with instrument evidence and controlled disposition.

Who: QC / LabDevice: Tablet / DesktopWorkflow: WF-QLT-01Control family: QLT
Why this workspace exists

Execute sampling/test plans with instrument evidence and controlled disposition. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Lot / job: review or complete this region in the context of the selected record.
  • Sampling plan: review or complete this region in the context of the selected record.
  • Tests: review or complete this region in the context of the selected record.
  • Instruments: review or complete this region in the context of the selected record.
  • Results: review or complete this region in the context of the selected record.
  • Photos: review or complete this region in the context of the selected record.
  • Disposition: review or complete this region in the context of the selected record.
  • NCR / certificate: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Inspection Entry, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Lot / job, Sampling plan, Tests, Instruments, Results, Photos, Disposition, NCR / certificate.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Pass: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Hold: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reject: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create NCR: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Print certificate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Inspection Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reference Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reference Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Lot Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Sample Size: the governed value shown or recorded for this workspace; verify it against the source record.
  • Overall Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-QLT-001 · PBX-QLT-002 · PBX-QLT-003 · PBX-QLT-004 · PBX-QLT-005 · PBX-QLT-006 · PBX-QLT-007 · PBX-QLT-008

SCR-SPC-001

AQL, SPC & Quality Certification

Configure sampling, capture measurements, detect process drift and issue certificates only from approved test data.

Who: Quality / LabDevice: DesktopWorkflow: WF-QLT-01Control family: QLT
Why this workspace exists

Configure sampling, capture measurements, detect process drift and issue certificates only from approved test data. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Sampling plan: review or complete this region in the context of the selected record.
  • AQL severity: review or complete this region in the context of the selected record.
  • Measurements: review or complete this region in the context of the selected record.
  • Control charts: review or complete this region in the context of the selected record.
  • Defect Pareto: review or complete this region in the context of the selected record.
  • COA/COC: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title AQL, SPC & Quality Certification, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Sampling plan, AQL severity, Measurements, Control charts, Defect Pareto, COA/COC.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Calculate AQL plan: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Analyse SPC: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record inspection: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Hold: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Generate certificate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-QLT-001 · PBX-QLT-002 · PBX-QLT-003 · PBX-QLT-004 · PBX-QLT-005 · PBX-QLT-006 · PBX-QLT-007 · PBX-QLT-008

SCR-CLR-001

Colour Management & Print Consistency

Manage Lab/density targets, instrument validity, press-side readings, corrections and repeat-order colour consistency.

Who: Quality / PressDevice: Desktop / TabletWorkflow: WF-QLT-01Control family: QLT
Why this workspace exists

Manage Lab/density targets, instrument validity, press-side readings, corrections and repeat-order colour consistency. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Colour standard: review or complete this region in the context of the selected record.
  • Ink formula: review or complete this region in the context of the selected record.
  • First-sheet approval: review or complete this region in the context of the selected record.
  • Run readings: review or complete this region in the context of the selected record.
  • Instrument status: review or complete this region in the context of the selected record.
  • Repeat analysis: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Colour Management & Print Consistency, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Colour standard, Ink formula, First-sheet approval, Run readings, Instrument status, Repeat analysis.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Measure Delta E: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve first sheet: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Correct shade: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close run: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-QLT-001 · PBX-QLT-002 · PBX-QLT-003 · PBX-QLT-004 · PBX-QLT-005 · PBX-QLT-006 · PBX-QLT-007 · PBX-QLT-008

SCR-WST-001

Scrap, Waste & Recovery Control

Classify planned and abnormal waste, weigh/evidence scrap, control disposal/reuse and preserve cost impact.

Who: Production / Quality / StoresDevice: Desktop / MobileWorkflow: WF-QLT-01Control family: QLT
Why this workspace exists

Classify planned and abnormal waste, weigh/evidence scrap, control disposal/reuse and preserve cost impact. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Waste capture: review or complete this region in the context of the selected record.
  • Reason classification: review or complete this region in the context of the selected record.
  • Weighment: review or complete this region in the context of the selected record.
  • Disposition: review or complete this region in the context of the selected record.
  • Recovery value: review or complete this region in the context of the selected record.
  • Sustainability KPI: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Scrap, Waste & Recovery Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Waste capture, Reason classification, Weighment, Disposition, Recovery value, Sustainability KPI.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Record scrap: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve disposal: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reuse: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Post recovery: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reason: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Disposition: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-QLT-001 · PBX-QLT-002 · PBX-QLT-003 · PBX-QLT-004 · PBX-QLT-005 · PBX-QLT-006 · PBX-QLT-007 · PBX-QLT-008

MAINTENANCE

Maintenance

1 workspaces
SCR-MNT-001

Maintenance Workbench

Plan PM, handle breakdowns, spares, permits, calibration and post-maintenance release.

Who: MaintenanceDevice: Mobile / DesktopWorkflow: WF-MNT-01Control family: MNT
Why this workspace exists

Plan PM, handle breakdowns, spares, permits, calibration and post-maintenance release. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Assets: review or complete this region in the context of the selected record.
  • PM due: review or complete this region in the context of the selected record.
  • Breakdown queue: review or complete this region in the context of the selected record.
  • Spares: review or complete this region in the context of the selected record.
  • Permits: review or complete this region in the context of the selected record.
  • Calibration: review or complete this region in the context of the selected record.
  • History: review or complete this region in the context of the selected record.
  • Clearance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Maintenance Workbench, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Assets, PM due, Breakdown queue, Spares, Permits, Calibration, History, Clearance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Acknowledge: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Start: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue parts: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Machine Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Maint Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Priority: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-MNT-001 · PBX-MNT-002 · PBX-MNT-003 · PBX-MNT-004 · PBX-MNT-005 · PBX-MNT-006 · PBX-MNT-007 · PBX-MNT-008

FINISHED GOODS

Finished Goods

1 workspaces
SCR-FGD-001

FG & Pallet Builder

Build traceable bundles/cartons/pallets only from quality-released finished goods.

Who: FG StoreDevice: Mobile / TabletWorkflow: WF-FGD-01Control family: FGD
Why this workspace exists

Build traceable bundles/cartons/pallets only from quality-released finished goods. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Accepted batches: review or complete this region in the context of the selected record.
  • Packing specification: review or complete this region in the context of the selected record.
  • Bundles / cartons: review or complete this region in the context of the selected record.
  • Pallet: review or complete this region in the context of the selected record.
  • Labels: review or complete this region in the context of the selected record.
  • Location: review or complete this region in the context of the selected record.
  • Allocation: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title FG & Pallet Builder, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Accepted batches, Packing specification, Bundles / cartons, Pallet, Labels, Location, Allocation.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Pack: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Label: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Move: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Allocate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Batch Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Available Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quality Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Expiry Date: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-FGD-001 · PBX-FGD-002 · PBX-FGD-003 · PBX-FGD-004 · PBX-FGD-005 · PBX-FGD-006 · PBX-FGD-007 · PBX-FGD-008

DISPATCH

Dispatch

1 workspaces
SCR-DSP-001

Dispatch Console

Convert released FG into a controlled shipment with vehicle, transporter, documents, load plan and POD.

Who: DispatchDevice: Desktop / TabletWorkflow: WF-FGD-01Control family: FGD
Why this workspace exists

Convert released FG into a controlled shipment with vehicle, transporter, documents, load plan and POD. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Orders due: review or complete this region in the context of the selected record.
  • Available FG: review or complete this region in the context of the selected record.
  • Pick / allocate: review or complete this region in the context of the selected record.
  • Vehicle & transporter: review or complete this region in the context of the selected record.
  • Documents: review or complete this region in the context of the selected record.
  • Load plan: review or complete this region in the context of the selected record.
  • POD: review or complete this region in the context of the selected record.
  • Delivery status: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Dispatch Console, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Orders due, Available FG, Pick / allocate, Vehicle & transporter, Documents, Load plan, POD, Delivery status.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create shipment: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Load: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Dispatch: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Confirm delivery: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Dispatch Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Vehicle Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Pod Reference: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-FGD-001 · PBX-FGD-002 · PBX-FGD-003 · PBX-FGD-004 · PBX-FGD-005 · PBX-FGD-006 · PBX-FGD-007 · PBX-FGD-008

TRACEABILITY

Traceability

1 workspaces
SCR-TRC-001

Trace & Recall

Search any job/material/tool/WIP/FG/pallet/dispatch identifier and reconstruct genealogy and mass balance.

Who: Quality / ComplianceDevice: DesktopWorkflow: WF-TRC-01Control family: TRC
Why this workspace exists

Search any job/material/tool/WIP/FG/pallet/dispatch identifier and reconstruct genealogy and mass balance. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Identifier search: review or complete this region in the context of the selected record.
  • Genealogy graph: review or complete this region in the context of the selected record.
  • Locations: review or complete this region in the context of the selected record.
  • Shipments: review or complete this region in the context of the selected record.
  • Mass balance: review or complete this region in the context of the selected record.
  • Recall scope: review or complete this region in the context of the selected record.
  • Evidence: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Trace & Recall, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Identifier search, Genealogy graph, Locations, Shipments, Mass balance, Recall scope, Evidence.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Search: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Initiate recall: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Notify: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-TRC-001 · PBX-TRC-002 · PBX-TRC-003 · PBX-TRC-004 · PBX-TRC-005 · PBX-TRC-006 · PBX-TRC-007 · PBX-TRC-008

COLLABORATION

Collaboration

2 workspaces
SCR-POR-001

Customer Portal Home

Controlled customer collaboration for quotations, approvals, orders, production, dispatch, stock and complaints.

Who: CustomerDevice: Responsive webWorkflow: WF-POR-01Control family: POR
Why this workspace exists

Controlled customer collaboration for quotations, approvals, orders, production, dispatch, stock and complaints. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Quotes: review or complete this region in the context of the selected record.
  • Approvals: review or complete this region in the context of the selected record.
  • Orders: review or complete this region in the context of the selected record.
  • Production: review or complete this region in the context of the selected record.
  • Dispatch: review or complete this region in the context of the selected record.
  • Stock: review or complete this region in the context of the selected record.
  • Complaints: review or complete this region in the context of the selected record.
  • Files & messages: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Customer Portal Home, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Quotes, Approvals, Orders, Production, Dispatch, Stock, Complaints, Files & messages.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Upload PO: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Repeat order: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Complaint: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-POR-001 · PBX-POR-002 · PBX-POR-003 · PBX-POR-004 · PBX-POR-005 · PBX-POR-006 · PBX-POR-007 · PBX-POR-008

SCR-SUP-001

Supplier Portal Home

Controlled supplier collaboration for RFQ, PO confirmation, ASN, certificates, invoice and CAPA.

Who: SupplierDevice: Responsive webWorkflow: WF-PUR-01Control family: PUR
Why this workspace exists

Controlled supplier collaboration for RFQ, PO confirmation, ASN, certificates, invoice and CAPA. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • RFQ: review or complete this region in the context of the selected record.
  • Purchase orders: review or complete this region in the context of the selected record.
  • ASN / delivery: review or complete this region in the context of the selected record.
  • Certificates: review or complete this region in the context of the selected record.
  • NCR / CAPA: review or complete this region in the context of the selected record.
  • Invoices: review or complete this region in the context of the selected record.
  • Messages: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Supplier Portal Home, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are RFQ, Purchase orders, ASN / delivery, Certificates, NCR / CAPA, Invoices, Messages.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Quote: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Confirm: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • ASN: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Upload: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • CAPA: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PUR-001 · PBX-PUR-002 · PBX-PUR-003 · PBX-PUR-004 · PBX-PUR-005 · PBX-PUR-006 · PBX-PUR-007 · PBX-PUR-008

PLATFORM

Platform

7 workspaces
SCR-ADM-001

Configuration Studio

Govern fields, forms, workflows, approvals, statuses and notifications as effective-dated versions.

Who: AdministratorDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Govern fields, forms, workflows, approvals, statuses and notifications as effective-dated versions. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Definitions: review or complete this region in the context of the selected record.
  • Fields & forms: review or complete this region in the context of the selected record.
  • Workflow designer: review or complete this region in the context of the selected record.
  • Approvals: review or complete this region in the context of the selected record.
  • Statuses: review or complete this region in the context of the selected record.
  • Notifications: review or complete this region in the context of the selected record.
  • Effective versions: review or complete this region in the context of the selected record.
  • Change impact: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Configuration Studio, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Definitions, Fields & forms, Workflow designer, Approvals, Statuses, Notifications, Effective versions, Change impact.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Draft: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Publish: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Rollback: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Definition Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Definition Key: the governed value shown or recorded for this workspace; verify it against the source record.
  • Version No: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Effective From: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-SEC-001

Cybersecurity & Access Governance

Review identities, privileged access, incompatible roles, sessions/devices, exports and periodic access certification.

Who: Security / Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Review identities, privileged access, incompatible roles, sessions/devices, exports and periodic access certification. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Users & roles: review or complete this region in the context of the selected record.
  • MFA: review or complete this region in the context of the selected record.
  • Access reviews: review or complete this region in the context of the selected record.
  • Sessions/devices: review or complete this region in the context of the selected record.
  • Sensitive exports: review or complete this region in the context of the selected record.
  • Security events: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Cybersecurity & Access Governance, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Users & roles, MFA, Access reviews, Sessions/devices, Sensitive exports, Security events.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Revoke: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve access: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-DR-001

Backup, DR & Business Continuity

Govern backups, restore tests, RPO/RTO, offline/manual continuity and reconciliation drills.

Who: IT / Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Govern backups, restore tests, RPO/RTO, offline/manual continuity and reconciliation drills. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Backup status: review or complete this region in the context of the selected record.
  • Restore tests: review or complete this region in the context of the selected record.
  • RPO/RTO: review or complete this region in the context of the selected record.
  • Continuity scenarios: review or complete this region in the context of the selected record.
  • Offline reconciliation: review or complete this region in the context of the selected record.
  • Evidence: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Backup, DR & Business Continuity, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Backup status, Restore tests, RPO/RTO, Continuity scenarios, Offline reconciliation, Evidence.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start drill: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record restore: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve result: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Open action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-ORG-001

Multi-Company, Plant & Warehouse Control

Govern organisation hierarchy, local rates, ownership, transfers, shared masters and consolidated reporting.

Who: Owner / Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Govern organisation hierarchy, local rates, ownership, transfers, shared masters and consolidated reporting. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Legal entities: review or complete this region in the context of the selected record.
  • Plants: review or complete this region in the context of the selected record.
  • Departments: review or complete this region in the context of the selected record.
  • Warehouses: review or complete this region in the context of the selected record.
  • Shared masters: review or complete this region in the context of the selected record.
  • Inter-plant transfers: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Multi-Company, Plant & Warehouse Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Legal entities, Plants, Departments, Warehouses, Shared masters, Inter-plant transfers.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create plant: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assign scope: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Transfer: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Consolidate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Plant Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Legal Entity Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Warehouse Count: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Timezone: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-SYS-001

System Administration & Monitoring

Control business configuration, queues, storage, security events, feature packs, releases and system health.

Who: Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Control business configuration, queues, storage, security events, feature packs, releases and system health. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Business settings: review or complete this region in the context of the selected record.
  • Workflow settings: review or complete this region in the context of the selected record.
  • Queues: review or complete this region in the context of the selected record.
  • Storage/DB: review or complete this region in the context of the selected record.
  • Security events: review or complete this region in the context of the selected record.
  • Release health: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title System Administration & Monitoring, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Business settings, Workflow settings, Queues, Storage/DB, Security events, Release health.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Process queue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run health: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Configure: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Open incident: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Check: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Message: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-OBS-001

Product Operations & Observability

Monitor availability, latency, error rate, queue depth, sync lag, integrations, incidents, SLA and runbooks.

Who: SRE / Support / Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Monitor availability, latency, error rate, queue depth, sync lag, integrations, incidents, SLA and runbooks. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Metrics: review or complete this region in the context of the selected record.
  • Logs: review or complete this region in the context of the selected record.
  • Traces: review or complete this region in the context of the selected record.
  • Queues: review or complete this region in the context of the selected record.
  • Incidents/SLA: review or complete this region in the context of the selected record.
  • Runbooks: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Product Operations & Observability, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Metrics, Logs, Traces, Queues, Incidents/SLA, Runbooks.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Acknowledge incident: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run recovery: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Escalate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Check: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Message: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-DEV-001

Mobile Device, Kiosk & Offline Governance

Register devices, enforce kiosk policy, protect offline storage, sync, evidence, version and remote revocation.

Who: Platform / Factory AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Register devices, enforce kiosk policy, protect offline storage, sync, evidence, version and remote revocation. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Device master: review or complete this region in the context of the selected record.
  • Trust state: review or complete this region in the context of the selected record.
  • Kiosk policy: review or complete this region in the context of the selected record.
  • Offline queue: review or complete this region in the context of the selected record.
  • Evidence integrity: review or complete this region in the context of the selected record.
  • Remote revoke: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Mobile Device, Kiosk & Offline Governance, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Device master, Trust state, Kiosk policy, Offline queue, Evidence integrity, Remote revoke.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Register: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Block: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Revoke: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Force update: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Device Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Plant Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Device Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • App Version: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Seen At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Blocked At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

INTELLIGENCE

Intelligence

4 workspaces
SCR-ANA-001

Analytics Studio

Build governed self-service analytics using certified datasets, dimensions, measures, security and schedules.

Who: Analyst / ManagerDevice: DesktopWorkflow: WF-ANA-01Control family: ANA
Why this workspace exists

Build governed self-service analytics using certified datasets, dimensions, measures, security and schedules. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Dataset: review or complete this region in the context of the selected record.
  • Dimensions: review or complete this region in the context of the selected record.
  • Measures: review or complete this region in the context of the selected record.
  • Filters: review or complete this region in the context of the selected record.
  • Visual: review or complete this region in the context of the selected record.
  • Row security: review or complete this region in the context of the selected record.
  • Certification: review or complete this region in the context of the selected record.
  • Schedule: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Analytics Studio, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Dataset, Dimensions, Measures, Filters, Visual, Row security, Certification, Schedule.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Build: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Certify: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Share: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Schedule: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Dataset Key: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ANA-001 · PBX-ANA-002 · PBX-ANA-003 · PBX-ANA-004 · PBX-ANA-005 · PBX-ANA-006 · PBX-ANA-007 · PBX-ANA-008

SCR-AI-001

Documents, Knowledge & AI

Use source-linked document extraction, knowledge search, anomaly/prediction suggestions and human-controlled acceptance.

Who: Manager / AnalystDevice: DesktopWorkflow: WF-ANA-01Control family: ANA
Why this workspace exists

Use source-linked document extraction, knowledge search, anomaly/prediction suggestions and human-controlled acceptance. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Sources: review or complete this region in the context of the selected record.
  • Extraction queue: review or complete this region in the context of the selected record.
  • Confidence: review or complete this region in the context of the selected record.
  • Knowledge search: review or complete this region in the context of the selected record.
  • Suggestions: review or complete this region in the context of the selected record.
  • Approvals: review or complete this region in the context of the selected record.
  • Audit evidence: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Documents, Knowledge & AI, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Sources, Extraction queue, Confidence, Knowledge search, Suggestions, Approvals, Audit evidence.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Upload source: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Extract: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Accept / reject suggestion: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ANA-001 · PBX-ANA-002 · PBX-ANA-003 · PBX-ANA-004 · PBX-ANA-005 · PBX-ANA-006 · PBX-ANA-007 · PBX-ANA-008

SCR-OEE-001

OEE, OTIF & Factory KPI Cockpit

Monitor availability, performance, quality, changeover, delivery, WIP, productivity and realised-margin indicators.

Who: Owner / Plant HeadDevice: Desktop / Large displayWorkflow: WF-ANA-01Control family: ANA
Why this workspace exists

Monitor availability, performance, quality, changeover, delivery, WIP, productivity and realised-margin indicators. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • OEE: review or complete this region in the context of the selected record.
  • OTIF: review or complete this region in the context of the selected record.
  • Schedule adherence: review or complete this region in the context of the selected record.
  • First-pass yield: review or complete this region in the context of the selected record.
  • WIP ageing: review or complete this region in the context of the selected record.
  • Margin variance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title OEE, OTIF & Factory KPI Cockpit, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are OEE, OTIF, Schedule adherence, First-pass yield, WIP ageing, Margin variance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Drill down: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Compare plant: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Schedule: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ANA-001 · PBX-ANA-002 · PBX-ANA-003 · PBX-ANA-004 · PBX-ANA-005 · PBX-ANA-006 · PBX-ANA-007 · PBX-ANA-008

SCR-AIK-001

AI Knowledge, Extraction & Decision Intelligence

Search approved sources, review extracted documents, voice drafts, anomalies and human-controlled recommendations.

Who: Authorised Knowledge UserDevice: Desktop / MobileWorkflow: WF-ANA-01Control family: ANA
Why this workspace exists

Search approved sources, review extracted documents, voice drafts, anomalies and human-controlled recommendations. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Knowledge search: review or complete this region in the context of the selected record.
  • Source excerpts: review or complete this region in the context of the selected record.
  • Document extraction: review or complete this region in the context of the selected record.
  • Voice draft: review or complete this region in the context of the selected record.
  • Anomalies: review or complete this region in the context of the selected record.
  • Approval history: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title AI Knowledge, Extraction & Decision Intelligence, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Knowledge search, Source excerpts, Document extraction, Voice draft, Anomalies, Approval history.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Search: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Extract: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Accept/reject: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ANA-001 · PBX-ANA-002 · PBX-ANA-003 · PBX-ANA-004 · PBX-ANA-005 · PBX-ANA-006 · PBX-ANA-007 · PBX-ANA-008

OPERATIONS

Operations

1 workspaces
SCR-JOB-001

Job Cockpit

One job context joining commercial baseline, engineering, material, execution, quality, documents, audit and profitability.

Who: Planner / Manager / Quality / OwnerDevice: Desktop / TabletWorkflow: WF-PROD-01Control family: PROD
Why this workspace exists

One job context joining commercial baseline, engineering, material, execution, quality, documents, audit and profitability. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Overview: review or complete this region in the context of the selected record.
  • Specification: review or complete this region in the context of the selected record.
  • Costing: review or complete this region in the context of the selected record.
  • BOM & Material: review or complete this region in the context of the selected record.
  • Work Orders: review or complete this region in the context of the selected record.
  • Production Entries: review or complete this region in the context of the selected record.
  • Quality: review or complete this region in the context of the selected record.
  • Documents: review or complete this region in the context of the selected record.
  • Comments: review or complete this region in the context of the selected record.
  • Audit History: review or complete this region in the context of the selected record.
  • Profitability: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Job Cockpit, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Overview, Specification, Costing, BOM & Material, Work Orders, Production Entries, Quality, Documents, Comments, Audit History, Profitability.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Open: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reserve material: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • View operation: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Client Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Order Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Due Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PROD-001 · PBX-PROD-002 · PBX-PROD-003 · PBX-PROD-004 · PBX-PROD-005 · PBX-PROD-006 · PBX-PROD-007 · PBX-PROD-008

INTEROPERABILITY

Interoperability

5 workspaces
SCR-PWF-01

Print Workflow Release Console

Validate and release print tickets, destination and resources while preserving message traceability.

Who: Prepress / ProductionDevice: DesktopWorkflow: WF-PWF-01Control family: PWF
Why this workspace exists

Validate and release print tickets, destination and resources while preserving message traceability. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Job ticket: review or complete this region in the context of the selected record.
  • Artwork / revision: review or complete this region in the context of the selected record.
  • Destination: review or complete this region in the context of the selected record.
  • Resources: review or complete this region in the context of the selected record.
  • Validation: review or complete this region in the context of the selected record.
  • Acknowledgement: review or complete this region in the context of the selected record.
  • Message history: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Print Workflow Release Console, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Job ticket, Artwork / revision, Destination, Resources, Validation, Acknowledgement, Message history.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Validate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Retry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Quarantine: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Jdf Ticket Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Jmf Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PWF-001 · PBX-PWF-002 · PBX-PWF-003 · PBX-PWF-004 · PBX-PWF-005 · PBX-PWF-006 · PBX-PWF-007 · PBX-PWF-008

SCR-PWF-02

Workflow Exchange Exception Queue

Review failed, duplicate, incompatible or quarantined print-workflow exchanges with safe retry and investigation history.

Who: Admin / PrepressDevice: DesktopWorkflow: WF-PWF-01Control family: PWF
Why this workspace exists

Review failed, duplicate, incompatible or quarantined print-workflow exchanges with safe retry and investigation history. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Exception queue: review or complete this region in the context of the selected record.
  • Message direction: review or complete this region in the context of the selected record.
  • Connector: review or complete this region in the context of the selected record.
  • Reason: review or complete this region in the context of the selected record.
  • Payload checksum: review or complete this region in the context of the selected record.
  • Retry: review or complete this region in the context of the selected record.
  • Quarantine: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Workflow Exchange Exception Queue, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Exception queue, Message direction, Connector, Reason, Payload checksum, Retry, Quarantine.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Retry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Quarantine: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Resolve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Exception Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reason: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PWF-001 · PBX-PWF-002 · PBX-PWF-003 · PBX-PWF-004 · PBX-PWF-005 · PBX-PWF-006 · PBX-PWF-007 · PBX-PWF-008

SCR-INT-001

Integration Hub & Message Operations

Operate connectors, mappings, webhooks/events, retry queues, dead letters and reconciliation.

Who: IT / Integration OwnerDevice: DesktopWorkflow: WF-PWF-01Control family: PWF
Why this workspace exists

Operate connectors, mappings, webhooks/events, retry queues, dead letters and reconciliation. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Connectors: review or complete this region in the context of the selected record.
  • Health/latency: review or complete this region in the context of the selected record.
  • Mappings: review or complete this region in the context of the selected record.
  • Queue/backlog: review or complete this region in the context of the selected record.
  • Dead letters: review or complete this region in the context of the selected record.
  • Reconciliation: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Integration Hub & Message Operations, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Connectors, Health/latency, Mappings, Queue/backlog, Dead letters, Reconciliation.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Validate configuration: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Retry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reprocess: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reconcile: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Connector Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Protocol: the governed value shown or recorded for this workspace; verify it against the source record.
  • Plant Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Machine Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Heartbeat At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Success At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Error: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PWF-001 · PBX-PWF-002 · PBX-PWF-003 · PBX-PWF-004 · PBX-PWF-005 · PBX-PWF-006 · PBX-PWF-007 · PBX-PWF-008

SCR-IOT-001

Machine, Sensor & Instrument Connectivity

Register device gateways, map tags, validate telemetry trust, monitor heartbeat and preserve manual corrections.

Who: IT / Maintenance / QualityDevice: DesktopWorkflow: WF-PWF-01Control family: PWF
Why this workspace exists

Register device gateways, map tags, validate telemetry trust, monitor heartbeat and preserve manual corrections. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Devices: review or complete this region in the context of the selected record.
  • Gateways: review or complete this region in the context of the selected record.
  • Tag mappings: review or complete this region in the context of the selected record.
  • Telemetry quality: review or complete this region in the context of the selected record.
  • Heartbeat: review or complete this region in the context of the selected record.
  • Calibration: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Machine, Sensor & Instrument Connectivity, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Devices, Gateways, Tag mappings, Telemetry quality, Heartbeat, Calibration.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Register device: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Map tag: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Quarantine: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Connector Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Protocol: the governed value shown or recorded for this workspace; verify it against the source record.
  • Plant Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Machine Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Heartbeat At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Success At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Error: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PWF-001 · PBX-PWF-002 · PBX-PWF-003 · PBX-PWF-004 · PBX-PWF-005 · PBX-PWF-006 · PBX-PWF-007 · PBX-PWF-008

SCR-CNX-001

CAD, Prepress & RIP Connector Hub

Control authoritative file hand-offs, checksums, source-of-truth ownership and connector failure release blocks.

Who: Prepress / Integration OwnerDevice: DesktopWorkflow: WF-PWF-01Control family: PWF
Why this workspace exists

Control authoritative file hand-offs, checksums, source-of-truth ownership and connector failure release blocks. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • CAD: review or complete this region in the context of the selected record.
  • Preflight/proof: review or complete this region in the context of the selected record.
  • Imposition: review or complete this region in the context of the selected record.
  • RIP/CTP: review or complete this region in the context of the selected record.
  • Colour/barcode: review or complete this region in the context of the selected record.
  • File governance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title CAD, Prepress & RIP Connector Hub, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are CAD, Preflight/proof, Imposition, RIP/CTP, Colour/barcode, File governance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Import metadata: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Send job ticket: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Verify checksum: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Block release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Connector Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Protocol: the governed value shown or recorded for this workspace; verify it against the source record.
  • Plant Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Machine Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Heartbeat At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Success At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Last Error: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-PWF-001 · PBX-PWF-002 · PBX-PWF-003 · PBX-PWF-004 · PBX-PWF-005 · PBX-PWF-006 · PBX-PWF-007 · PBX-PWF-008

WAREHOUSE MANAGEMENT

Warehouse Management

2 workspaces
SCR-WMS-01

Warehouse Map & Capacity

Visualise warehouse topology, restrictions and capacity so invalid or over-capacity moves are blocked.

Who: WarehouseDevice: Desktop / TabletWorkflow: WF-WMS-01Control family: WMS
Why this workspace exists

Visualise warehouse topology, restrictions and capacity so invalid or over-capacity moves are blocked. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Warehouse hierarchy: review or complete this region in the context of the selected record.
  • Zones / racks / bins: review or complete this region in the context of the selected record.
  • Capacity: review or complete this region in the context of the selected record.
  • Restrictions: review or complete this region in the context of the selected record.
  • Utilisation: review or complete this region in the context of the selected record.
  • Putaway rules: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Warehouse Map & Capacity, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Warehouse hierarchy, Zones / racks / bins, Capacity, Restrictions, Utilisation, Putaway rules.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create location: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Recommend putaway: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Save pick face: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run replenishment: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review capacity: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Warehouse Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Zone Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Location Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Location Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Scan Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Pick Sequence: the governed value shown or recorded for this workspace; verify it against the source record.
  • Restricted: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-WMS-001 · PBX-WMS-002 · PBX-WMS-003 · PBX-WMS-004 · PBX-WMS-005 · PBX-WMS-006 · PBX-WMS-007 · PBX-WMS-008

SCR-WMS-02

Mobile Warehouse Task

Accept, scan and complete putaway, pick, replenish, count and move tasks with traceable exceptions.

Who: Warehouse OperatorDevice: Mobile / TabletWorkflow: WF-WMS-01Control family: WMS
Why this workspace exists

Accept, scan and complete putaway, pick, replenish, count and move tasks with traceable exceptions. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Task: review or complete this region in the context of the selected record.
  • From / to: review or complete this region in the context of the selected record.
  • Item / lot: review or complete this region in the context of the selected record.
  • Handling unit: review or complete this region in the context of the selected record.
  • Scan confirmation: review or complete this region in the context of the selected record.
  • Quantity: review or complete this region in the context of the selected record.
  • Exception reason: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Mobile Warehouse Task, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Task, From / to, Item / lot, Handling unit, Scan confirmation, Quantity, Exception reason.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Complete: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Exception: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Task Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Task Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Item Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Lot Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Source Location Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Destination Location Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Requested Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Completed Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Priority: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-WMS-001 · PBX-WMS-002 · PBX-WMS-003 · PBX-WMS-004 · PBX-WMS-005 · PBX-WMS-006 · PBX-WMS-007 · PBX-WMS-008

EXPORT & TRADE

Export & Trade

1 workspaces
SCR-EXP-01

Export Shipment Dossier

Manage export order/shipment, trade documents, container/seal and closure as one governed dossier.

Who: Export / CommercialDevice: DesktopWorkflow: WF-EXP-01Control family: EXP
Why this workspace exists

Manage export order/shipment, trade documents, container/seal and closure as one governed dossier. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Export order: review or complete this region in the context of the selected record.
  • Destination & currency: review or complete this region in the context of the selected record.
  • Incoterm: review or complete this region in the context of the selected record.
  • Document checklist: review or complete this region in the context of the selected record.
  • Container / seal: review or complete this region in the context of the selected record.
  • Customs / carrier: review or complete this region in the context of the selected record.
  • Cost & margin: review or complete this region in the context of the selected record.
  • Closure: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Export Shipment Dossier, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Export order, Destination & currency, Incoterm, Document checklist, Container / seal, Customs / carrier, Cost & margin, Closure.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create shipment: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Prepare documents: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Ship: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Export Shipment Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Export Order Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Container Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Carrier: the governed value shown or recorded for this workspace; verify it against the source record.
  • Customs Reference: the governed value shown or recorded for this workspace; verify it against the source record.
  • Shipping Bill Reference: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Departure: the governed value shown or recorded for this workspace; verify it against the source record.
  • Actual Departure: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-EXP-001 · PBX-EXP-002 · PBX-EXP-003 · PBX-EXP-004 · PBX-EXP-005 · PBX-EXP-006 · PBX-EXP-007 · PBX-EXP-008

AUDIT & COMPLIANCE

Audit & Compliance

2 workspaces
SCR-AUD-01

Audit Programme Calendar

Plan risk-based audits, scope, assignments and recurrence against applicable schemes and obligations.

Who: Quality / ComplianceDevice: DesktopWorkflow: WF-AUD-01Control family: AUD
Why this workspace exists

Plan risk-based audits, scope, assignments and recurrence against applicable schemes and obligations. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Programme: review or complete this region in the context of the selected record.
  • Calendar: review or complete this region in the context of the selected record.
  • Scope: review or complete this region in the context of the selected record.
  • Risk basis: review or complete this region in the context of the selected record.
  • Auditors: review or complete this region in the context of the selected record.
  • Applicable clauses: review or complete this region in the context of the selected record.
  • Status: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Audit Programme Calendar, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Programme, Calendar, Scope, Risk basis, Auditors, Applicable clauses, Status.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create programme: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Schedule audit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review coverage: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Programme Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Year No: the governed value shown or recorded for this workspace; verify it against the source record.
  • Scope: the governed value shown or recorded for this workspace; verify it against the source record.
  • Risk Basis: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-AUD-001 · PBX-AUD-002 · PBX-AUD-003 · PBX-AUD-004 · PBX-AUD-005 · PBX-AUD-006 · PBX-AUD-007 · PBX-AUD-008

SCR-AUD-02

Audit Execution & Findings

Execute audit checklist, capture evidence/findings and drive corrective action through verification.

Who: AuditorDevice: Desktop / TabletWorkflow: WF-AUD-01Control family: AUD
Why this workspace exists

Execute audit checklist, capture evidence/findings and drive corrective action through verification. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Audit header: review or complete this region in the context of the selected record.
  • Checklist: review or complete this region in the context of the selected record.
  • Evidence: review or complete this region in the context of the selected record.
  • Findings: review or complete this region in the context of the selected record.
  • Severity: review or complete this region in the context of the selected record.
  • Actions: review or complete this region in the context of the selected record.
  • Verification: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Audit Execution & Findings, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Audit header, Checklist, Evidence, Findings, Severity, Actions, Verification.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Start audit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue finding: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Verify: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Audit Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Audit Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Start: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned End: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-AUD-001 · PBX-AUD-002 · PBX-AUD-003 · PBX-AUD-004 · PBX-AUD-005 · PBX-AUD-006 · PBX-AUD-007 · PBX-AUD-008

CAPEX & ASSETS

CAPEX & Assets

2 workspaces
SCR-CAP-01

CAPEX Business Case

Request, compare, approve and track investment with benefits, risks and vendor alternatives.

Who: Plant / FinanceDevice: DesktopWorkflow: WF-CAP-01Control family: CAP
Why this workspace exists

Request, compare, approve and track investment with benefits, risks and vendor alternatives. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Business need: review or complete this region in the context of the selected record.
  • Options: review or complete this region in the context of the selected record.
  • Vendor bids: review or complete this region in the context of the selected record.
  • Investment: review or complete this region in the context of the selected record.
  • Benefits: review or complete this region in the context of the selected record.
  • Risk: review or complete this region in the context of the selected record.
  • Approval: review or complete this region in the context of the selected record.
  • Tracking: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title CAPEX Business Case, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Business need, Options, Vendor bids, Investment, Benefits, Risk, Approval, Tracking.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create request: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create business case: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Add vendor bid: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit approval: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Order: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Project Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Title: the governed value shown or recorded for this workspace; verify it against the source record.
  • Investment Amount: the governed value shown or recorded for this workspace; verify it against the source record.
  • Expected Annual Benefit: the governed value shown or recorded for this workspace; verify it against the source record.
  • Approved Budget: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Commissioning: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-CAP-001 · PBX-CAP-002 · PBX-CAP-003 · PBX-CAP-004 · PBX-CAP-005 · PBX-CAP-006 · PBX-CAP-007 · PBX-CAP-008

SCR-CAP-02

Commissioning Gate

Control FAT/SAT/trial, punch list and production/quality clearance before an asset is commissioned.

Who: Engineering / QualityDevice: Desktop / TabletWorkflow: WF-CAP-01Control family: CAP
Why this workspace exists

Control FAT/SAT/trial, punch list and production/quality clearance before an asset is commissioned. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Project: review or complete this region in the context of the selected record.
  • FAT / SAT: review or complete this region in the context of the selected record.
  • Trial results: review or complete this region in the context of the selected record.
  • Punch list: review or complete this region in the context of the selected record.
  • Safety: review or complete this region in the context of the selected record.
  • Quality: review or complete this region in the context of the selected record.
  • Training: review or complete this region in the context of the selected record.
  • Release: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Commissioning Gate, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Project, FAT / SAT, Trial results, Punch list, Safety, Quality, Training, Release.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Record test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Add readiness action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Pass test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Fail test: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Commission asset: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Project Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Test Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Test Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Result: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-CAP-001 · PBX-CAP-002 · PBX-CAP-003 · PBX-CAP-004 · PBX-CAP-005 · PBX-CAP-006 · PBX-CAP-007 · PBX-CAP-008

PRODUCT LIFECYCLE

Product Lifecycle

1 workspaces
SCR-EOL-01

Product Lifecycle Impact

Assess discontinuation impact on stock, jobs, tools, artwork, contracts and clients before run-out/archive/reactivation.

Who: Product / CommercialDevice: DesktopWorkflow: WF-EOL-01Control family: EOL
Why this workspace exists

Assess discontinuation impact on stock, jobs, tools, artwork, contracts and clients before run-out/archive/reactivation. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Product: review or complete this region in the context of the selected record.
  • Reason: review or complete this region in the context of the selected record.
  • Open jobs: review or complete this region in the context of the selected record.
  • Inventory impact: review or complete this region in the context of the selected record.
  • Tooling / artwork: review or complete this region in the context of the selected record.
  • Client commitments: review or complete this region in the context of the selected record.
  • Disposition: review or complete this region in the context of the selected record.
  • Reactivation: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Product Lifecycle Impact, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Product, Reason, Open jobs, Inventory impact, Tooling / artwork, Client commitments, Disposition, Reactivation.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Request EOL: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run out: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Archive: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reactivate review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Case Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reason: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-EOL-001 · PBX-EOL-002 · PBX-EOL-003 · PBX-EOL-004 · PBX-EOL-005 · PBX-EOL-006 · PBX-EOL-007 · PBX-EOL-008

RETURNABLE ASSETS

Returnable Assets

1 workspaces
SCR-RTA-01

Returnable Custody Scan

Issue, transfer, return, inspect and reconcile returnable pallets, crates and other pooled assets.

Who: Dispatch / StoreDevice: Mobile / TabletWorkflow: WF-RTA-01Control family: RTA
Why this workspace exists

Issue, transfer, return, inspect and reconcile returnable pallets, crates and other pooled assets. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Asset scan: review or complete this region in the context of the selected record.
  • Asset type: review or complete this region in the context of the selected record.
  • Current custody: review or complete this region in the context of the selected record.
  • Party: review or complete this region in the context of the selected record.
  • Expected return: review or complete this region in the context of the selected record.
  • Condition: review or complete this region in the context of the selected record.
  • Deposit / exposure: review or complete this region in the context of the selected record.
  • Pool balance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Returnable Custody Scan, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Asset scan, Asset type, Current custody, Party, Expected return, Condition, Deposit / exposure, Pool balance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Issue: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Transfer: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Return: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Inspect: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Count: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Asset Barcode: the governed value shown or recorded for this workspace; verify it against the source record.
  • Asset Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Current Location: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-RTA-001 · PBX-RTA-002 · PBX-RTA-003 · PBX-RTA-004 · PBX-RTA-005 · PBX-RTA-006 · PBX-RTA-007 · PBX-RTA-008

RIGID BOX PACK

Rigid Box Pack

2 workspaces
SCR-RGB-01

Rigid-Box Structure & Components

Define rigid-box style, grey-board/wrap components, dimensions, material, grain, operations and cosmetic requirements.

Who: EngineeringDevice: DesktopWorkflow: WF-RGB-01Control family: RGB
Why this workspace exists

Define rigid-box style, grey-board/wrap components, dimensions, material, grain, operations and cosmetic requirements. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Style: review or complete this region in the context of the selected record.
  • Dimensions: review or complete this region in the context of the selected record.
  • Components: review or complete this region in the context of the selected record.
  • Grey board: review or complete this region in the context of the selected record.
  • Wrapping paper: review or complete this region in the context of the selected record.
  • Groove / turn-in: review or complete this region in the context of the selected record.
  • Route: review or complete this region in the context of the selected record.
  • Cosmetic QC: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Rigid-Box Structure & Components, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Style, Dimensions, Components, Grey board, Wrapping paper, Groove / turn-in, Route, Cosmetic QC.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create style: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Add component: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve style: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create kit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Revise: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Style Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Style Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Revision No: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-RGB-001 · PBX-RGB-002 · PBX-RGB-003 · PBX-RGB-004 · PBX-RGB-005 · PBX-RGB-006 · PBX-RGB-007 · PBX-RGB-008

SCR-RGB-02

Rigid-Box Component WIP

Track kits, component preparation, trays/cells, curing, cosmetic QC and set completion.

Who: ProductionDevice: Mobile / TabletWorkflow: WF-RGB-01Control family: RGB
Why this workspace exists

Track kits, component preparation, trays/cells, curing, cosmetic QC and set completion. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Kit: review or complete this region in the context of the selected record.
  • Components: review or complete this region in the context of the selected record.
  • Input: review or complete this region in the context of the selected record.
  • Good / reject / rework: review or complete this region in the context of the selected record.
  • Worker cell: review or complete this region in the context of the selected record.
  • Curing: review or complete this region in the context of the selected record.
  • QC hold: review or complete this region in the context of the selected record.
  • Set completion: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Rigid-Box Component WIP, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Kit, Components, Input, Good / reject / rework, Worker cell, Curing, QC hold, Set completion.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Record output: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Start curing: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Request QC: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Complete set: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Kit Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Component Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Operation Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Input Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Good Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Reject Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Rework Quantity: the governed value shown or recorded for this workspace; verify it against the source record.
  • Curing Until: the governed value shown or recorded for this workspace; verify it against the source record.
  • Worker Cell: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-RGB-001 · PBX-RGB-002 · PBX-RGB-003 · PBX-RGB-004 · PBX-RGB-005 · PBX-RGB-006 · PBX-RGB-007 · PBX-RGB-008

LABEL PACK

Label Pack

2 workspaces
SCR-LBL-01

Label Construction & Roll Specification

Define construction, web, pitch, repeat, roll, tooling, variable data and packing requirements.

Who: EngineeringDevice: DesktopWorkflow: WF-LBL-01Control family: LBL
Why this workspace exists

Define construction, web, pitch, repeat, roll, tooling, variable data and packing requirements. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Construction: review or complete this region in the context of the selected record.
  • Web & substrate: review or complete this region in the context of the selected record.
  • Pitch / repeat: review or complete this region in the context of the selected record.
  • Labels across: review or complete this region in the context of the selected record.
  • Roll limits: review or complete this region in the context of the selected record.
  • Tooling: review or complete this region in the context of the selected record.
  • Variable data: review or complete this region in the context of the selected record.
  • Packing: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Label Construction & Roll Specification, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Construction, Web & substrate, Pitch / repeat, Labels across, Roll limits, Tooling, Variable data, Packing.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create construction: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create geometry: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Create specification: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Calculate web: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Spec Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Product Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Construction Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Geometry Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Labels Per Roll: the governed value shown or recorded for this workspace; verify it against the source record.
  • Splice Limit: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LBL-001 · PBX-LBL-002 · PBX-LBL-003 · PBX-LBL-004 · PBX-LBL-005 · PBX-LBL-006 · PBX-LBL-007 · PBX-LBL-008

SCR-LBL-02

Label Roll Inspection & Reconciliation

Reconcile roll production, camera/inspection results, splices, variable-data ranges, matrix waste and release state.

Who: QualityDevice: Tablet / DesktopWorkflow: WF-LBL-01Control family: LBL
Why this workspace exists

Reconcile roll production, camera/inspection results, splices, variable-data ranges, matrix waste and release state. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Production roll: review or complete this region in the context of the selected record.
  • Printed length: review or complete this region in the context of the selected record.
  • Inspection: review or complete this region in the context of the selected record.
  • Defects: review or complete this region in the context of the selected record.
  • Splices: review or complete this region in the context of the selected record.
  • Variable data: review or complete this region in the context of the selected record.
  • Matrix waste: review or complete this region in the context of the selected record.
  • Release: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Label Roll Inspection & Reconciliation, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Production roll, Printed length, Inspection, Defects, Splices, Variable data, Matrix waste, Release.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Record roll: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Inspect: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Hold: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reconcile: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Job Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Operation Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Output Roll Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Web Width Mm: the governed value shown or recorded for this workspace; verify it against the source record.
  • Label Pitch Mm: the governed value shown or recorded for this workspace; verify it against the source record.
  • Labels Across: the governed value shown or recorded for this workspace; verify it against the source record.
  • Planned Labels: the governed value shown or recorded for this workspace; verify it against the source record.
  • Camera Count: the governed value shown or recorded for this workspace; verify it against the source record.
  • Operator Count: the governed value shown or recorded for this workspace; verify it against the source record.
  • Matrix Waste M: the governed value shown or recorded for this workspace; verify it against the source record.
  • Splice Count: the governed value shown or recorded for this workspace; verify it against the source record.
  • Duplicate Count: the governed value shown or recorded for this workspace; verify it against the source record.
  • Inspection Result: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LBL-001 · PBX-LBL-002 · PBX-LBL-003 · PBX-LBL-004 · PBX-LBL-005 · PBX-LBL-006 · PBX-LBL-007 · PBX-LBL-008

INSURANCE & RISK

Insurance & Risk

1 workspaces
SCR-INS-01

Insurance Claim & Enterprise Risk

Track policy, incident notice, evidence, survey, settlement/recovery and related enterprise risk treatment.

Who: Risk / FinanceDevice: DesktopWorkflow: WF-INS-01Control family: INS
Why this workspace exists

Track policy, incident notice, evidence, survey, settlement/recovery and related enterprise risk treatment. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Policy: review or complete this region in the context of the selected record.
  • Insured interest: review or complete this region in the context of the selected record.
  • Claim event: review or complete this region in the context of the selected record.
  • Evidence: review or complete this region in the context of the selected record.
  • Survey / query: review or complete this region in the context of the selected record.
  • Eligible loss: review or complete this region in the context of the selected record.
  • Recovery: review or complete this region in the context of the selected record.
  • Risk treatment: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Insurance Claim & Enterprise Risk, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Policy, Insured interest, Claim event, Evidence, Survey / query, Eligible loss, Recovery, Risk treatment.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Notify claim: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Submit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record survey: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Settle: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Claim Number: the governed value shown or recorded for this workspace; verify it against the source record.
  • Policy Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Event Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Event Date: the governed value shown or recorded for this workspace; verify it against the source record.
  • Claimed Amount: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-INS-001 · PBX-INS-002 · PBX-INS-003 · PBX-INS-004 · PBX-INS-005 · PBX-INS-006 · PBX-INS-007 · PBX-INS-008

LEARNING & COMPETENCY

Learning & Competency

1 workspaces
SCR-LMS-01

Competency Matrix & Authorisation

Define competency requirements and ensure only currently certified/authorised workers are eligible for machine assignments.

Who: HR / ProductionDevice: Desktop / TabletWorkflow: WF-LMS-01Control family: LMS
Why this workspace exists

Define competency requirements and ensure only currently certified/authorised workers are eligible for machine assignments. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Competencies: review or complete this region in the context of the selected record.
  • Role requirements: review or complete this region in the context of the selected record.
  • Courses: review or complete this region in the context of the selected record.
  • Sessions: review or complete this region in the context of the selected record.
  • Assessment: review or complete this region in the context of the selected record.
  • Certification: review or complete this region in the context of the selected record.
  • Machine authorisation: review or complete this region in the context of the selected record.
  • Expiry: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Competency Matrix & Authorisation, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Competencies, Role requirements, Courses, Sessions, Assessment, Certification, Machine authorisation, Expiry.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Create competency: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Schedule training: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assess: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Certify: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Suspend: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Competency Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LMS-001 · PBX-LMS-002 · PBX-LMS-003 · PBX-LMS-004 · PBX-LMS-005 · PBX-LMS-006 · PBX-LMS-007 · PBX-LMS-008

MARKETPLACE

Marketplace

1 workspaces
SCR-MKT-01

Marketplace Package Review

Review partner packages for compatibility, permissions, security, support ownership, licensing and controlled publication/install/rollback.

Who: Platform OperationsDevice: DesktopWorkflow: WF-MKT-01Control family: MKT
Why this workspace exists

Review partner packages for compatibility, permissions, security, support ownership, licensing and controlled publication/install/rollback. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Partner: review or complete this region in the context of the selected record.
  • Package: review or complete this region in the context of the selected record.
  • Version: review or complete this region in the context of the selected record.
  • Permissions: review or complete this region in the context of the selected record.
  • Compatibility: review or complete this region in the context of the selected record.
  • Security review: review or complete this region in the context of the selected record.
  • Entitlement: review or complete this region in the context of the selected record.
  • Installation / rollback: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Marketplace Package Review, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Partner, Package, Version, Permissions, Compatibility, Security review, Entitlement, Installation / rollback.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Submit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Publish: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Install: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Rollback: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Suspend: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Package Slug: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Partner Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-MKT-001 · PBX-MKT-002 · PBX-MKT-003 · PBX-MKT-004 · PBX-MKT-005 · PBX-MKT-006 · PBX-MKT-007 · PBX-MKT-008

GOVERNANCE

Governance

4 workspaces
SCR-TRACE-01

Requirement Traceability Cockpit

Trace every v8 requirement through screen, workflow, entity, API/event, formula, test, release and acceptance evidence.

Who: Product / QADevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Trace every v8 requirement through screen, workflow, entity, API/event, formula, test, release and acceptance evidence. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Requirement: review or complete this region in the context of the selected record.
  • User story: review or complete this region in the context of the selected record.
  • Screen: review or complete this region in the context of the selected record.
  • Workflow: review or complete this region in the context of the selected record.
  • Entity: review or complete this region in the context of the selected record.
  • API / event: review or complete this region in the context of the selected record.
  • Formula: review or complete this region in the context of the selected record.
  • Test: review or complete this region in the context of the selected record.
  • Release: review or complete this region in the context of the selected record.
  • Acceptance evidence: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Requirement Traceability Cockpit, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Requirement, User story, Screen, Workflow, Entity, API / event, Formula, Test, Release, Acceptance evidence.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Filter: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Open evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Run checks: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export matrix: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-GOL-001

Migration, UAT, Cutover & Go-Live

Execute migration reconciliation, calculation validation, role UAT, training, cutover, rollback and hypercare gates.

Who: Implementation / Business OwnersDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Execute migration reconciliation, calculation validation, role UAT, training, cutover, rollback and hypercare gates. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Migration: review or complete this region in the context of the selected record.
  • Calculation pack: review or complete this region in the context of the selected record.
  • 264 UAT: review or complete this region in the context of the selected record.
  • Training: review or complete this region in the context of the selected record.
  • Cutover: review or complete this region in the context of the selected record.
  • Go-live approvals: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Migration, UAT, Cutover & Go-Live, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Migration, Calculation pack, 264 UAT, Training, Cutover, Go-live approvals.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Run acceptance: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Attach evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve gate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Go live: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Title: the governed value shown or recorded for this workspace; verify it against the source record.
  • Category: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Result: the governed value shown or recorded for this workspace; verify it against the source record.
  • Checked At: the governed value shown or recorded for this workspace; verify it against the source record.
  • Approved At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-DPDP-001

Privacy & Data Governance

Operate data inventory, notices, processors, retention, rights requests, breach and grievance controls.

Who: Privacy / Platform AdminDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Operate data inventory, notices, processors, retention, rights requests, breach and grievance controls. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Data inventory: review or complete this region in the context of the selected record.
  • Notices: review or complete this region in the context of the selected record.
  • Processors: review or complete this region in the context of the selected record.
  • Retention: review or complete this region in the context of the selected record.
  • Rights requests: review or complete this region in the context of the selected record.
  • Breach/grievance: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Privacy & Data Governance, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Data inventory, Notices, Processors, Retention, Rights requests, Breach/grievance.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Register request: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Verify identity: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Request Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Subject Reference: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Due Date: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SCR-SDLC-001

Secure SDLC & Release Governance

Track design review, code/test gates, SBOM, migrations, signed release, rollback and post-release health.

Who: Engineering / SecurityDevice: DesktopWorkflow: WF-ADM-01Control family: ADM
Why this workspace exists

Track design review, code/test gates, SBOM, migrations, signed release, rollback and post-release health. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Threat model: review or complete this region in the context of the selected record.
  • Build gates: review or complete this region in the context of the selected record.
  • Tests: review or complete this region in the context of the selected record.
  • SBOM/dependencies: review or complete this region in the context of the selected record.
  • Release approval: review or complete this region in the context of the selected record.
  • Rollback: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Secure SDLC & Release Governance, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Threat model, Build gates, Tests, SBOM/dependencies, Release approval, Rollback.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Open release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Attach evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ADM-001 · PBX-ADM-002 · PBX-ADM-003 · PBX-ADM-004 · PBX-ADM-005 · PBX-ADM-006 · PBX-ADM-007 · PBX-ADM-008

SAFETY & EHS

Safety & EHS

1 workspaces
SCR-EHS-001

Safety & EHS Control Centre

Manage permits, incidents, hazards, corrective actions, inspections and controlled safety acknowledgements.

Who: EHS / PlantDevice: Desktop / MobileWorkflow: WF-EHS-01Control family: EHS
Why this workspace exists

Manage permits, incidents, hazards, corrective actions, inspections and controlled safety acknowledgements. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Incidents: review or complete this region in the context of the selected record.
  • Hazards: review or complete this region in the context of the selected record.
  • Permits: review or complete this region in the context of the selected record.
  • Inspections: review or complete this region in the context of the selected record.
  • Actions: review or complete this region in the context of the selected record.
  • Training / acknowledgement: review or complete this region in the context of the selected record.
  • Evidence: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Safety & EHS Control Centre, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Incidents, Hazards, Permits, Inspections, Actions, Training / acknowledgement, Evidence.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Report incident: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Issue permit: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Inspect: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close action: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-EHS-001 · PBX-EHS-002 · PBX-EHS-003 · PBX-EHS-004 · PBX-EHS-005 · PBX-EHS-006 · PBX-EHS-007 · PBX-EHS-008

GATE & LOGISTICS

Gate & Logistics

3 workspaces
SCR-LOG-001

Gate, Yard & Logistics Console

Coordinate vehicle entry, yard status, dock/dispatch readiness, freight evidence and transport events.

Who: Gate / DispatchDevice: Desktop / TabletWorkflow: WF-LOG-01Control family: LOG
Why this workspace exists

Coordinate vehicle entry, yard status, dock/dispatch readiness, freight evidence and transport events. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Gate queue: review or complete this region in the context of the selected record.
  • Vehicles: review or complete this region in the context of the selected record.
  • Visitors: review or complete this region in the context of the selected record.
  • Yard / dock: review or complete this region in the context of the selected record.
  • Load readiness: review or complete this region in the context of the selected record.
  • Transport documents: review or complete this region in the context of the selected record.
  • Exceptions: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Gate, Yard & Logistics Console, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Gate queue, Vehicles, Visitors, Yard / dock, Load readiness, Transport documents, Exceptions.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Check in: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assign bay: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release vehicle: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Record exception: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LOG-001 · PBX-LOG-002 · PBX-LOG-003 · PBX-LOG-004 · PBX-LOG-005 · PBX-LOG-006 · PBX-LOG-007 · PBX-LOG-008

SCR-YRD-001

Gate, Visitor, Vehicle & Yard Control

Control appointments, gate passes, weighbridge, seals, yard queues, docks and emergency muster.

Who: Security / Gate / LogisticsDevice: Desktop / MobileWorkflow: WF-LOG-01Control family: LOG
Why this workspace exists

Control appointments, gate passes, weighbridge, seals, yard queues, docks and emergency muster. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Visitors: review or complete this region in the context of the selected record.
  • Vehicle appointments: review or complete this region in the context of the selected record.
  • Gate pass: review or complete this region in the context of the selected record.
  • Weighbridge: review or complete this region in the context of the selected record.
  • Yard/dock queue: review or complete this region in the context of the selected record.
  • Seal/security: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Gate, Visitor, Vehicle & Yard Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Visitors, Vehicle appointments, Gate pass, Weighbridge, Yard/dock queue, Seal/security.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Check in: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Weigh: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assign dock: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Gate out: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LOG-001 · PBX-LOG-002 · PBX-LOG-003 · PBX-LOG-004 · PBX-LOG-005 · PBX-LOG-006 · PBX-LOG-007 · PBX-LOG-008

SCR-FRT-001

Transport, Freight & Delivery Control

Plan vehicles, compare freight, track route/POD, settle transporter bills and manage logistics claims.

Who: Dispatch / LogisticsDevice: DesktopWorkflow: WF-LOG-01Control family: LOG
Why this workspace exists

Plan vehicles, compare freight, track route/POD, settle transporter bills and manage logistics claims. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Transporter/lane: review or complete this region in the context of the selected record.
  • Freight bids: review or complete this region in the context of the selected record.
  • Vehicle plan: review or complete this region in the context of the selected record.
  • Tracking: review or complete this region in the context of the selected record.
  • POD: review or complete this region in the context of the selected record.
  • Settlement/claims: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Transport, Freight & Delivery Control, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Transporter/lane, Freight bids, Vehicle plan, Tracking, POD, Settlement/claims.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Request bid: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assign vehicle: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Track: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Settle: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-LOG-001 · PBX-LOG-002 · PBX-LOG-003 · PBX-LOG-004 · PBX-LOG-005 · PBX-LOG-006 · PBX-LOG-007 · PBX-LOG-008

FINANCE

Finance

2 workspaces
SCR-FIN-001

Working Capital & Profitability

Connect receivables, payables, inventory, job cash need and realised margin without hiding source assumptions.

Who: Owner / FinanceDevice: DesktopWorkflow: WF-FIN-01Control family: FIN
Why this workspace exists

Connect receivables, payables, inventory, job cash need and realised margin without hiding source assumptions. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Receivables: review or complete this region in the context of the selected record.
  • Payables: review or complete this region in the context of the selected record.
  • Inventory investment: review or complete this region in the context of the selected record.
  • Job cash requirement: review or complete this region in the context of the selected record.
  • Credit days: review or complete this region in the context of the selected record.
  • Freight / claims: review or complete this region in the context of the selected record.
  • Realised margin: review or complete this region in the context of the selected record.
  • Cash conversion: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Working Capital & Profitability, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Receivables, Payables, Inventory investment, Job cash requirement, Credit days, Freight / claims, Realised margin, Cash conversion.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Review exposure: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Drill to job: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Read every displayed label, status and reference in its business context before taking action.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-FIN-001 · PBX-FIN-002 · PBX-FIN-003 · PBX-FIN-004 · PBX-FIN-005 · PBX-FIN-006 · PBX-FIN-007 · PBX-FIN-008

SCR-FIN-002

Financial Integration & Realised Profitability

Reconcile operational events to accounting references and explain quoted, planned, production, dispatch and realised margin.

Who: Finance / OwnerDevice: DesktopWorkflow: WF-FIN-01Control family: FIN
Why this workspace exists

Reconcile operational events to accounting references and explain quoted, planned, production, dispatch and realised margin. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Posting map: review or complete this region in the context of the selected record.
  • Inventory valuation: review or complete this region in the context of the selected record.
  • Job waterfall: review or complete this region in the context of the selected record.
  • Claims/credits: review or complete this region in the context of the selected record.
  • Finance cost: review or complete this region in the context of the selected record.
  • Period close: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Financial Integration & Realised Profitability, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Posting map, Inventory valuation, Job waterfall, Claims/credits, Finance cost, Period close.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Reconcile: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Post batch: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Close period: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Reopen: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-FIN-001 · PBX-FIN-002 · PBX-FIN-003 · PBX-FIN-004 · PBX-FIN-005 · PBX-FIN-006 · PBX-FIN-007 · PBX-FIN-008

WORKFORCE

Workforce

1 workspaces
SCR-WFM-001

Workforce, Attendance & Incentives

Manage availability, skills, machine authorisation, attendance, output standards and quality-linked incentive calculation.

Who: HR / ProductionDevice: DesktopWorkflow: WF-WRK-01Control family: WRK
Why this workspace exists

Manage availability, skills, machine authorisation, attendance, output standards and quality-linked incentive calculation. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Employee master: review or complete this region in the context of the selected record.
  • Skills: review or complete this region in the context of the selected record.
  • Attendance: review or complete this region in the context of the selected record.
  • Standards: review or complete this region in the context of the selected record.
  • Productivity: review or complete this region in the context of the selected record.
  • Incentive review: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Workforce, Attendance & Incentives, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Employee master, Skills, Attendance, Standards, Productivity, Incentive review.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Assign skill: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve attendance: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Calculate incentive: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Freeze period: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Employee Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Name: the governed value shown or recorded for this workspace; verify it against the source record.
  • Department: the governed value shown or recorded for this workspace; verify it against the source record.
  • Role: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-WRK-001 · PBX-WRK-002 · PBX-WRK-003 · PBX-WRK-004 · PBX-WRK-005 · PBX-WRK-006 · PBX-WRK-007 · PBX-WRK-008

COMMERCIAL PLATFORM

Commercial Platform

1 workspaces
SCR-SAA-001

SaaS Tenant, Subscription & Lifecycle

Provision tenants, assign plans, meter entitlements, manage billing/renewal, white-label, partners and lifecycle.

Who: Platform Commercial AdminDevice: DesktopWorkflow: WF-SAA-01Control family: SAA
Why this workspace exists

Provision tenants, assign plans, meter entitlements, manage billing/renewal, white-label, partners and lifecycle. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Tenant lifecycle: review or complete this region in the context of the selected record.
  • Plans: review or complete this region in the context of the selected record.
  • Entitlements: review or complete this region in the context of the selected record.
  • Usage: review or complete this region in the context of the selected record.
  • Billing: review or complete this region in the context of the selected record.
  • Partner/SLA: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title SaaS Tenant, Subscription & Lifecycle, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Tenant lifecycle, Plans, Entitlements, Usage, Billing, Partner/SLA.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Provision tenant: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Assign plan: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Renew: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Suspend: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-SAA-001 · PBX-SAA-002 · PBX-SAA-003 · PBX-SAA-004 · PBX-SAA-005 · PBX-SAA-006 · PBX-SAA-007 · PBX-SAA-008

COMPLIANCE

Compliance

2 workspaces
SCR-PAS-001

Passport & Sustainability Export

Assemble versioned product/material/certification/sustainability data for controlled customer or machine-readable export.

Who: Compliance / SustainabilityDevice: DesktopWorkflow: WF-ESG-01Control family: ESG
Why this workspace exists

Assemble versioned product/material/certification/sustainability data for controlled customer or machine-readable export. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Product identity: review or complete this region in the context of the selected record.
  • Materials: review or complete this region in the context of the selected record.
  • Sustainability: review or complete this region in the context of the selected record.
  • Compliance: review or complete this region in the context of the selected record.
  • End-of-life: review or complete this region in the context of the selected record.
  • Export/API: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Passport & Sustainability Export, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Product identity, Materials, Sustainability, Compliance, End-of-life, Export/API.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Build profile: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Validate evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Export: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Withdraw: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ESG-001 · PBX-ESG-002 · PBX-ESG-003 · PBX-ESG-004 · PBX-ESG-005 · PBX-ESG-006 · PBX-ESG-007 · PBX-ESG-008

SCR-CMP-001

Industry Compliance Packs

Activate FSC/PEFC, food, pharma, automotive and customer-specific controls without claiming certification.

Who: Quality / ComplianceDevice: DesktopWorkflow: WF-AUD-01Control family: AUD
Why this workspace exists

Activate FSC/PEFC, food, pharma, automotive and customer-specific controls without claiming certification. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Pack activation: review or complete this region in the context of the selected record.
  • Mandatory records: review or complete this region in the context of the selected record.
  • Material controls: review or complete this region in the context of the selected record.
  • Line clearance: review or complete this region in the context of the selected record.
  • Certificates: review or complete this region in the context of the selected record.
  • Audit readiness: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Industry Compliance Packs, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Pack activation, Mandatory records, Material controls, Line clearance, Certificates, Audit readiness.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Activate pack: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Validate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Review: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Generate evidence: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Obligation Code: the governed value shown or recorded for this workspace; verify it against the source record.
  • Title: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Due Date: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-AUD-001 · PBX-AUD-002 · PBX-AUD-003 · PBX-AUD-004 · PBX-AUD-005 · PBX-AUD-006 · PBX-AUD-007 · PBX-AUD-008

OPTIMISATION

Optimisation

1 workspaces
SCR-GNG-001

Gang-Run & Nesting Optimiser

Compare compatible job groups, layouts, setup/material savings, cost allocation and execution risk.

Who: Estimator / PlannerDevice: DesktopWorkflow: WF-CST-01Control family: CST
Why this workspace exists

Compare compatible job groups, layouts, setup/material savings, cost allocation and execution risk. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Candidate jobs: review or complete this region in the context of the selected record.
  • Compatibility: review or complete this region in the context of the selected record.
  • Combined layout: review or complete this region in the context of the selected record.
  • Savings: review or complete this region in the context of the selected record.
  • Cost allocation: review or complete this region in the context of the selected record.
  • Risk/approval: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Gang-Run & Nesting Optimiser, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Candidate jobs, Compatibility, Combined layout, Savings, Cost allocation, Risk/approval.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Find candidates: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Compare: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve gang: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Release: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Scenario Type: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
  • Estimated Saving: the governed value shown or recorded for this workspace; verify it against the source record.
  • Created At: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-CST-001 · PBX-CST-002 · PBX-CST-003 · PBX-CST-004 · PBX-CST-005 · PBX-CST-006 · PBX-CST-007 · PBX-CST-008

SUSTAINABILITY

Sustainability

1 workspaces
SCR-ESG-001

Energy, Carbon & ESG Accounting

Capture energy/water/fuel, version emissions factors, allocate impact and produce evidence-backed sustainability outputs.

Who: Sustainability / OwnerDevice: DesktopWorkflow: WF-ESG-01Control family: ESG
Why this workspace exists

Capture energy/water/fuel, version emissions factors, allocate impact and produce evidence-backed sustainability outputs. Use it to keep this part of the business lifecycle in one governed record, with the user, organisation, operating scope, time and authorised transition preserved for audit.

Before you start
  • Sign in with your own account and confirm the active organisation.
  • Confirm this workspace and its required action are enabled by your package and role.
  • Confirm your employee link and plant, warehouse or department scope.
  • Collect the approved upstream record and truthful source evidence; do not use placeholders.
What you will see
  • Energy/fuel: review or complete this region in the context of the selected record.
  • Water: review or complete this region in the context of the selected record.
  • Emission factors: review or complete this region in the context of the selected record.
  • Carbon: review or complete this region in the context of the selected record.
  • Materials/circularity: review or complete this region in the context of the selected record.
  • Targets/reports: review or complete this region in the context of the selected record.
Step-by-step operating procedure
  1. Open and orient: verify the screen title Energy, Carbon & ESG Accounting, organisation and operating scope before selecting a record.
  2. Select the source: search by the business code or name and choose the approved upstream record. Never guess or type an internal database ID.
  3. Review current state: check status, ownership, dates, quantities, revisions, holds and linked evidence before editing.
  4. Complete the working regions: enter only observed or approved facts. Required areas on this screen are Energy/fuel, Water, Emission factors, Carbon, Materials/circularity, Targets/reports.
  5. Validate: check units, dates, totals, references and attachments; correct every validation message at its source.
  6. Save the controlled record: save once, wait for confirmation and note the record/reference number. Do not double-submit.
  7. Run the authorised transition: choose the action that matches the real event and confirm its prerequisites.
  8. Confirm completion: refresh the queue, verify the new status and downstream availability, and retain the audit/evidence reference.
Actions and what they mean
  • Record reading: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Approve factor: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Calculate: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
  • Publish statement: performs this controlled business transition. Use it only after reviewing the selected record, prerequisites and evidence; the server rechecks your authority.
Data you must understand
  • Id: the governed value shown or recorded for this workspace; verify it against the source record.
  • Status: the governed value shown or recorded for this workspace; verify it against the source record.
Successful completion
  • A record/reference is visible in the live queue or selected context.
  • The status matches the action actually completed.
  • The audit trail identifies the user, time, organisation and scope.
  • Required evidence is attached and the next authorised workspace can consume the record.
Stop and escalate when
  • The source record, revision, quantity, owner or organisation is wrong.
  • An approval, credit, competency, safety, quality or scope gate blocks progress.
  • The same request times out or fails after one safe retry.
  • A duplicate, conflicting status or unexpected downstream record appears.

Governed requirements: PBX-ESG-001 · PBX-ESG-002 · PBX-ESG-003 · PBX-ESG-004 · PBX-ESG-005 · PBX-ESG-006 · PBX-ESG-007 · PBX-ESG-008

TROUBLESHOOTING

When something is blocked

I am repeatedly asked to sign in

Confirm that your WordPress session is active. If the message says access is not enabled, do not sign in repeatedly—ask the organisation owner to review package, role, employee link and operating scope.

I cannot see a workspace or action

Open My profile and confirm the organisation and effective scope. The owner can review Packages & Access; a hidden action cannot be bypassed by typing its URL.

A record will not save

Read the validation message, confirm required fields and source status, then retry once. Preserve the record number, time and correlation/reference if support is needed.

I belong to more than one company

Select the intended active company before working. Customer and supplier memberships may coexist, but internal employee access remains separate.

What counts as evidence?

Use the workflow-requested certificate, measurement, approved source document, photo, signed approval or external reference. Never upload credentials, passwords or unrelated personal data.

NON-NEGOTIABLE CONTROLS

Five rules every user follows

Own identity

Never share credentials or approve for another person.

Correct scope

Check company, plant, warehouse and department first.

Lifecycle order

Use controlled transitions rather than editing system-owned status.

Real evidence

Record facts and actual events—not placeholders.

Escalate exceptions

Never bypass safety, quality, credit or approval gates.