EXCORA
Demo ecosystem · Fictional dataProduct concept. Not a live network.

Why doesn't existing software do this?

Existing systems optimize within organizations. EXCORA is exploring coordination between them.

  • Forecasting systemknows predicted need
  • ATM monitoringknows machine condition
  • Smart-safe platformknows safe condition
  • CIT dispatchknows available service capacity
  • Bank operationsknows business priority

Each organization may hold only part of the operational picture. EXCORA's proposed role is to transmit a minimized, actionable signal between authorized counterparties without requiring either party to surrender its underlying system or dataset.

This is the interoperability problem EXCORA is researching. Some existing products may already address parts of it; the research is designed to find out.

Illustrative Product Concept

What would integration actually look like?

Source systems

  • ATM monitoring
  • Forecasting
  • Smart safes
  • Cash management
  • Bank operations
  • CIT systems

EXCORA

  1. Step 1: Normalize
  2. Step 2: Authorize
  3. Step 3: Minimize
  4. Step 4: Route
  5. Step 5: Respond
  6. Step 6: Audit
  7. Step 7: Measure

Authorized counterparties

  • Banks
  • CITs
  • Retailers
  • Cash centers
  • ATM operators
  • Technology providers

EXCORA does not need to own the underlying data or replace the systems that generate it.

EXCORA is being designed to work with existing and emerging industry identifiers, standards and data formats where appropriate. No integrations are live.

Fictional scenarios

With and without earlier coordination

Most of these are cases where earlier coordination does not help. They are included deliberately.

  • ATM ATL-184 · replenishment requirement

    Signal changed the outcome
    Without earlier coordination
    CIT Company learns of the need after its planning cutoff. Options narrow to an unscheduled visit or a later service.
    With earlier coordination
    CIT Company sees the need before the 3:00 PM decision deadline and accepts a planned service tomorrow morning.

    Earlier coordination changed the outcome in this fictional case.

  • ATM ATL-207 · device unavailable

    Signal changed the outcome
    Without earlier coordination
    A scheduled replenishment visit proceeds to a machine that cannot accept cash.
    With earlier coordination
    The carrier acknowledges the notice and the visit is held until the device returns to service.

    Value here is avoiding a mistimed visit, not requesting more service.

  • Mechanical ATM failure

    Signal did not change the outcome
    Without earlier coordination
    The machine fails. A technician is required.
    With earlier coordination
    The signal informs the carrier, but the constraint is the repair. The outcome is the same.

    A signal does not fix hardware.

  • Carrier has no available capacity

    Signal did not change the outcome
    Without earlier coordination
    The request is received late and cannot be accommodated.
    With earlier coordination
    The request is received early and still cannot be accommodated: capacity is the constraint.

    The source learns sooner, which is information, but service does not change.

  • Information known only after route lock

    Signal did not change the outcome
    Without earlier coordination
    Routes are committed before the need is known.
    With earlier coordination
    The signal arrives after the route is committed. Nothing can change today.

    Earlier delivery cannot help if the information itself is late.

  • Signal duplicates an already scheduled service

    Signal did not change the outcome
    Without earlier coordination
    Service was already planned.
    With earlier coordination
    Carrier responds Already scheduled. No operational change.

    Confirmation has some value; avoided cost does not.

  • Recipient cannot safely accommodate

    Signal did not change the outcome
    Without earlier coordination
    Request handled through usual channels.
    With earlier coordination
    Carrier responds Cannot accommodate · Security. The request is declined for reasons outside the signal.

    Safety and policy constraints remain with the recipient.

Which of these cases is most common in your operation?

What would be missing? Help us test whether this proposed workflow reflects how physical cash operations actually work. Nothing you do in this demo is recorded as research.

Participate in Research

This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.