Start with the deal.
Connect the lifecycle.
PDS configures a robotic lease proposal in its office equipment dealer software. Submission sends the proposal and robot asset details to GreatAmerica Financial Services for underwriting.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Robotics lease proposal
Build the deal once. Approved asset data becomes the shared starting point for fleet operations, service, ERP usage and end-of-life recovery.
Lease proposal details
DraftProposal data package
Structured handoffUnderwrite the deal.
Authorize the asset.
GreatAmerica reviews the dealer-submitted proposal. Approval is the gate that releases the robot asset record to the operating ecosystem.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Underwriting review
Review the submitted terms and record a simulated underwriting decision. Approval unlocks the data handoff to all downstream platforms.
Application snapshot
Not submittedDecision workflow
Demo simulationApproval is the trigger for WALM to distribute the normalized asset record to Acumatica ERP, Crickets CHIRP and LaborCloud.
One approval.
Three synchronized systems.
WALM routes approved robot asset data to ERP, fleet management and field service simultaneously. Each destination has its own role while sharing the same asset identity.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Asset activation & fan-out
Approval triggers parallel delivery. WALM records acknowledgements and keeps the cross-system lifecycle status visible.
Acumatica ERP
QueuedCommercial asset record
Asset register, customer, contract and monthly RWU accounting.
Crickets CHIRP
QueuedRobot fleet management
Fleet identity, telemetry and operational usage data.
LaborCloud
QueuedField service operations
Robot asset data plus PDS location data and LaborCloud technician data.
WALM distribution ledger
One event · Three acknowledgements| Destination | Responsibility | Event | Delivery | Asset key |
|---|---|---|---|---|
| Acumatica ERP | Asset master + contract | AssetApproved | Waiting | — |
| Crickets CHIRP | Fleet identity | AssetApproved | Waiting | — |
| LaborCloud | Service asset | AssetApproved | Waiting | — |
Robots generate work.
Usage becomes evidence.
Crickets CHIRP manages the deployed robot fleet, records operational activity and sends usage measurements to Acumatica for monthly Robot Work Unit accounting.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Fleet operations console
Review robot identity and generate a sample monthly usage batch. The batch is sent to Acumatica for validation and RWU posting.
Robot fleet register
CHIRP| Asset | Model | State | Tasks |
|---|---|---|---|
| RB-2048 | AMR Navigator X2 | Operational | 1,284 |
| RB-2049 | DeliveryBot Pro | Operational | 986 |
| RB-2050 | CleanBot Autonomous | Maintenance | 712 |
Monthly usage package
Not generatedTurn robot activity
into a monthly work unit.
Acumatica receives the approved asset master and CHIRP's monthly usage batch, validates the data, records RWU quantity and prepares a period posting.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Robot Work Unit posting
Usage is associated with the robot asset and reporting period. This demo illustrates the workflow, not a live accounting integration.
Robot usage subledger
Monthly period| Period | Asset | Source | Tasks | Adjustments | RWU total | ERP state |
|---|---|---|---|---|---|---|
| No CHIRP batch received. Generate one on the CHIRP screen. | ||||||
Five years later,
the asset data still matters.
At lease maturity, GreatAmerica sends robot identity and accumulated usage data to Arcoa to initiate a controlled decommission workflow.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Lease end & asset disposition
Simulate the time jump to lease maturity. The retirement package contains asset identity, lease reference, usage summary and condition notes.
Asset retirement package
Not releasedRetirement lifecycle gate
Control pointProduction should use contract dates, disposition authorization and chain-of-custody controls.
Retire the robot.
Recover useful components.
Arcoa receives the one-unit decommission order and asset/usage package from GreatAmerica. The robot is inspected and disassembled into reusable parts and PCB assemblies.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
One unit in. Recoverable parts out.
Record receipt, complete teardown and route recovered control PCBs to Hytec Repair Services for refurbishment.
Decommission receipt
Awaiting unitRecovered component manifest
Illustrative yield| Component | Qty | Disposition |
|---|---|---|
| Control PCB assembly | 2 | Route to Hytec |
| Drive motor module | 2 | Inspect / stock |
| Lidar sensor assembly | 1 | Test / stock |
| Battery pack | 1 | Recycling review |
| Chassis / brackets | 1 lot | Material recovery |
Update the electronics.
Extend parts life.
Arcoa routes recovered PCBs to Hytec. Hytec updates chips, installs approved firmware and verifies each board before returning it to the service-parts supply chain.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
PCB refurbishment bench
Track intake, chip update, firmware installation and quality checks. Accepted boards return to PDS inventory.
Repair traveler
Awaiting dispatchPCB batch record
Serialized components| Board ID | Work performed | Firmware | QC | Disposition |
|---|---|---|---|---|
| PCB-2048-A | Pending | — | Pending | Hold |
| PCB-2048-B | Pending | — | Pending | Hold |
The lifecycle closes.
The parts stay in circulation.
Refurbished PCBs and recovered components return to PDS as service-parts inventory. WALM links the original leased robot to the parts recovered from it.
Data lineage · where every field comes from and goes
Field-level handoff| Data element | Source system | Destination system | When / purpose |
|---|
Demo data is simulated in this browser. In production, each row maps to an API/event payload and should carry an asset ID, timestamp, correlation ID and delivery status.
Recovered parts are ready for the next repair.
The original robot is decommissioned, but value continues through tested, traceable components. PDS can allocate accepted parts to future field service jobs.
Parts received into stock
Inventory ledger| Part / batch | Qty | Condition | Stock status |
|---|---|---|---|
| PCB-RB2048-01 | 2 | Refurbished | Awaiting QC |
| Drive motor module | 2 | Recovered / inspect | Awaiting receipt |
| Lidar sensor assembly | 1 | Recovered / test | Awaiting receipt |
Lifecycle data lineage
WALM recordEvery handoff can be tracked against the original robot asset ID and lease reference.
Lease proposal and asset identity
Shared asset master and operating setup
Usage records and monthly RWU
Decommission and PCB refurbishment
Refurbished service parts returned to stock
End-to-end handoff log
| Time | From | To | Event / data | Status |
|---|