Not an account. A view into the same fictional network, limited to what ABC Retail would be authorized to see. Illustrative Product Concept.
Fictional example permissions · not a production configuration
Permission is bilateral and purpose-specific. Each direction of a relationship is configured separately, and the originating organization decides which signal categories may go to which counterparty, for which purpose. Everything else stays with the organization that holds it.
ABC Retail may send
ABC Retail → CIT Company
Permitted
- Permitted: Earlier pickup requested
- Permitted: Skip or reschedule service
- Permitted: Service requirement changed
- Permitted: Device unavailable
- Permitted: Asset identifier or token
- Permitted: Priority
- Permitted: Need-by time
- Permitted: Decision deadline
- Permitted: Confidence band where relevant
Not permitted
- Not permitted: Store cash positions
- Not permitted: Sales data
- Not permitted: Smart-safe contents
- Not permitted: Store security arrangements
Reverse direction configured separately: CIT Company may send 2 categories back.
ABC Retail may receive
- CIT Company
Service requirement changed · Service cannot be accommodated as requested
Never includes: route information, crew information, security credentials and procedures, other customers' activity.
- Example Technology Co.
Forecast exception
Never includes: raw device telemetry, forecasting models, other clients' data.
This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.