Software & Integration

The complete system, not just the hardware

1. 1
   Physical capture

   Reads, scans, weights, prints, and confirmations arriving from devices at the point of work.

   Integration decides whether a physical event becomes a transaction in seconds or a spreadsheet at the end of the shift. The contract, the field mapping, and the failure behaviour matter more than the transport.

   How it is captured

   Device and application integration

   Hardware at the capture point

   • ·Readers, scanners, and mobile computers — Produce the events that have to reach the business system
   • ·Printers and encoders — Receive formats and data back from the business system
   • ·Fixed industrial scanners and vision — Send pass, fail, and read results from the line without an operator

2. 2
   Mobi software

   What Mobi does with what was captured

   Integrations covers the approved APIs, webhooks, files, and mappings between Mobi and your business systems. Mobi Inventory holds the operational records that the integration reads from and writes to.

   IntegrationsControlled ReleaseMobi InventoryAvailableDevicesControlled Release

   Current limits

   Integrations is Controlled Release and each interface is scoped, tested, and approved for a specific deployment. Customers do not directly change core product code or production data.

3. 3
   System of record

   Where the result has to land

   Each interface has a named owner, a documented payload, a retry and error path, and an agreed cutover. Arrowhead builds and tests to that contract before anything is switched on in production.

   Systems this connects to

   ERP · WMS · MES · EAM or CMMS · Business intelligence · Customer applications

   What you provide

   System owners and access, the interface specification or the API, a non-production environment, and the sign-off that the payload matches what the business needs.

4. 4
   Delivery and lifecycle

   Who builds it, who runs it, and who answers when it breaks

   1. Technical discovery
   2. Data contract
   3. Mapping and build
   4. Test environment validation
   5. Cutover
   6. Support boundary handover

   What Arrowhead supplies and configures

   • Technical discovery with the system and operations owners
   • The documented data contract and field mapping
   • Build, configuration, and error handling
   • Validation against a non-production environment
   • Cutover support and a documented support boundary

   What you provide

   • System-of-record owner, credentials, and API or interface documentation
   • A non-production environment to test against
   • Business rules, including what happens to a rejected record
   • Change windows and approval for production cutover

   When something stops working

   Arrowhead owns the interfaces it builds and the Mobi side of them. The customer's system owner keeps the system of record. The support boundary between the two is written down at handover rather than discovered during an incident.

What the proof actually shows

Every claim below is labeled with who produced it. Arrowhead delivering a system, a vendor publishing a result from another partner's deployment, a credential a third party issued us, software we run ourselves, a capability we offer, and a direction we have not shipped are different things, and they are labeled differently.

• Arrowhead-delivered result

  RFID data delivered into Curtiss-Wright's business intelligence tooling through APIs.

  Part of the system Arrowhead delivered with Xemelgo and Zebra Technologies; the tracking software was Xemelgo. Result published by Zebra Technologies.

  See the detail
• General capability

  Every interface is scoped, mapped, and tested in a non-production environment before cutover.

  This is Arrowhead's standard integration practice on Controlled Release deployments, not a customer-specific outcome.

  See the detail
• Future direction

  Customer-composed automation inside Mobi.

  Governed Extensions is Controlled Release for approved deployments. Compose and Extend remain future direction, with self-serve review, versioning, and support still to be defined.

  See the detail