Not an account. A view into the same fictional network, limited to what Example Technology Co. 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.
Example Technology Co. may send
Example Technology Co. → XYZ Bank
Permitted
- Permitted: Forecast exception
- 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: Raw device telemetry
- Not permitted: Forecasting models
- Not permitted: Other clients' data
No reverse permission: XYZ Bank cannot send signals to Example Technology Co. in this example.
Example Technology Co. → ABC Retail
Permitted
- Permitted: Forecast exception
- Permitted: Asset identifier or token
- Permitted: Priority
- Permitted: Need-by time
- Permitted: Decision deadline
- Permitted: Confidence band where relevant
Not permitted
- Not permitted: Raw device telemetry
- Not permitted: Forecasting models
- Not permitted: Other clients' data
No reverse permission: ABC Retail cannot send signals to Example Technology Co. in this example.
This interactive environment demonstrates the proposed EXCORA workflow. Organizations, events, responses and outcomes shown here are fictional and do not represent production deployments.