-
Notifications
You must be signed in to change notification settings - Fork 10
Description
Description:
The system shall not impose any technical or functional constraints on the ability of PnC stakeholders — including OEMs, CPOs, and eMSPs — to freely choose which pool provider(s) they want to interact with. The architecture must allow participants to subscribe to and operate with the pool of their choice.
Use Case:
An OEM or eMSP wants to register or manage contracts via a specific pool operator (e.g., for commercial or regional reasons). The system must enable this without technical bias or architectural limitations.
Current Status
Conceptually supported in OPNC 1.0, but some internal mechanisms may unintentionally constrain the freedom of choice (e.g., contract prioritization logic). (?)
Pool choice flexibility is critical for interoperability (IOP) across the ecosystem.
Discussion Points
- How is contract prioritization handled currently in OPNC?
- Is there a standard way to present multiple contracts to the customer in a consistent and neutral way?
- Can all stakeholders verify that their pool subscription choices are respected by the current implementation?