Scan once. Resolve the operating context.
Authenticate the operator, choose Receiving or Tool Crib, then scan a public/demo barcode or QR code, or enter a controlled synthetic identifier. Receiving accepts PO 1001-1010. Tool Crib accepts TOOL-SYN-2001-2005.
Receiver / operator session
Every controlled action must be attributable to an authenticated operator. Production target: Tosoh Microsoft Entra SSO mapped explicitly to the authorized IFS user/person identity and IFS Received By context.
Device readiness
Run device check, start an authenticated session, then start the scanner camera.
Authenticated actor and RBAC
Synthetic role sign-in demonstrates the target paper trail. Production identity would use Tosoh-approved enterprise SSO and explicit mapping to the authorized IFS user/person identity.
Register Arrivals context
TRACEBridge mirrors the observed IFS vocabulary, then presents it as one vertical operating context after exact scan/search resolution.
Receive
Human confirmation remains explicit. TRACEBridge aligns to the observed IFS Receive dialog while keeping IFS authoritative.
Observed IFS Receive fields — synthetic values
· ·
Inspection / MRB gate
TRACEBridge routes workflow and evidence; authorized Quality roles retain disposition authority.
Label and physical verification
Rendering is not completion. Physical output must be verified against expected identity before notification eligibility.
Requisitioner notification
The target notification is released only after required documentation and operating gates are satisfied and the authoritative state is reconcilable.
Tool Crib digital custody and return control
Replace paper sign-out with an attributable custody transaction: authenticated Tool Crib/Supervisor operator + approved borrower proximity badge + tool + work reference + checkout timestamp + return-by policy + return condition. Payroll/timekeeping is outside TRACEBridge scope.
Borrower proximity badge
The badge identifies the borrower; the signed-in Tool Crib/Supervisor session authorizes the transaction. Production should use an IT-approved proximity/forklift badge mapping and must not import payroll/timekeeping data or alter access-control permissions.
Checkout / return
Return-time enforcement / Supervisor exception
Timed return policy is tool-class configurable. A hard-overdue worker lock can block additional checkout; return is always permitted. A Supervisor exception is one-use, reason-required, and audited. Final Tosoh policy remains an approval item.
Current synthetic custody journal
IFS-compatible view preferences
The review now mirrors the observed IFS List View pattern: Default mode or manual Available fields ⇄ Selected fields configuration. Presentation never changes IFS data, validation, permissions, or mandatory compliance fields.
List View settings / Column Chooser
Compatibility boundary
IFS-compatible semantic layout and observed receiving vocabulary; no Granite packages, IFS credentials, or production connection.
Any thin inside component should use approved Granite components/tokens and the IFS customer-solution lifecycle.
IFS system-of-record boundary
Procurement → Receipt → Register Arrivals → select/resolve source → Receive. TRACEBridge uses this observed vocabulary as the compatibility target while reducing repeated search and horizontal reorientation.
Physical scan → authenticated TRACEBridge actor → Register Arrivals context → human receive confirmation / Split Receipt when applicable → approved IFS API/action → authoritative receipt → reconciliation → print/physical verification → approved requisitioner notification.
Microsoft Entra enterprise sign-in → TRACEBridge RBAC → explicit authorized IFS user/person mapping → IFS Received By correlation → auditable action.
Authenticated Tool Crib operator → approved borrower proximity/forklift badge mapping → tool scan → calibration/condition/time-policy gate → approved enterprise master/API → authoritative custody/status update → return evidence → audit/reconciliation. The badge is borrower identity only; it is not payroll/timekeeping or privileged authentication.
Approved notification event → Microsoft Graph / Teams or Outlook channel → delivery result → TRACEBridge audit correlation. No M365 tenant connection exists in this build.
Read-only TEST/UAT lookup using approved test records, followed by controlled action validation only if authorized. No production writes or direct database access requested.
TRACEBridge Guide / FAQ
The review assistant answers only from approved embedded FAQ content. No external AI service is called.
Does TRACEBridge replace IFS?
No. IFS remains the authoritative enterprise system of record. TRACEBridge is an outside operational orchestration and assurance layer.
How does TRACEBridge align with Register Arrivals?
The review mirrors observed IFS receiving concepts such as Source Ref 1/2/3, Source Part Description, Source Ref Type, Source UOM, Requisitioner, Status, Qty to Receive, Qty to Inspect, Received By, dates, receipt reference, print selections, and Split Receipt. All review values are synthetic.
How is Split Receipt handled?
The receiver explicitly chooses a smaller receive quantity. TRACEBridge shows the remaining quantity and preserves human confirmation; it does not silently modify the authoritative PO or receipt.
How does the Column Chooser work?
Default mode uses TRACEBridge recommended receiving fields. Manual mode provides Available and Selected field lists with add/remove/reorder controls. Required traceability fields remain selected. Production cross-device preferences would require an approved authenticated profile service.
How is the requisitioner handled?
The requisitioner/requester is part of the resolved receiving context. A production notice is eligible only after required documentation and workflow gates are satisfied and authoritative IFS state is reconcilable.
How is user identity handled?
The review build simulates identity and RBAC. Production should use Tosoh-approved enterprise SSO and explicit mapping to the authorized IFS user/person identity so Received By and the paper trail can be reconciled.
How would Teams notifications work?
Microsoft 365/Teams is a candidate enterprise notification channel. Production use requires Tosoh-approved Microsoft Entra/Graph permissions, tenant policy, app/integration design, security review, and TEST/UAT. This build sends nothing externally.
How does Tool Crib proximity-badge custody work?
An approved proximity/forklift badge identifies the borrower through an IT-owned reader and credential mapping while an authenticated Tool Crib or Supervisor session authorizes the transaction. TRACEBridge does not require payroll/timekeeping data, does not use the badge for Supervisor authority, and does not alter door or forklift access rights.
What happens after a barcode scan?
In this synthetic review build, a decoded public/demo barcode is mapped to controlled synthetic data. In an authorized enterprise pilot, approved identifiers would resolve against Tosoh-approved IFS/API mappings.
Synthetic audit evidence
This review records only in-memory synthetic events for the current browser session. The target model correlates actor, role, IFS identity/reference, receiving state, split quantities, worker custody, return policy, exceptions, and notification outcome.