-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFR: Secondary Data Holder unable to determine Customer Present #602
Labels
Comments
This was referenced Jul 26, 2023
Feedback from AEMO and reflections on recent conversations during the previous maintenance iteration call:
|
This was referenced Feb 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The Shared Responsibility for Energy section specifies:
While the definition of this header states:
Meanwhile the NFRs state that there are different SDH Performance Requirements are variable for certain present vs. not present calls:
![image](https://private-user-images.githubusercontent.com/4291448/256172177-75ddf1e8-f456-4eb7-8475-213f1123596f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxOTQxODMsIm5iZiI6MTcxOTE5Mzg4MywicGF0aCI6Ii80MjkxNDQ4LzI1NjE3MjE3Ny03NWRkZjFlOC1mNDU2LTRlYjctODQ3NS0yMTNmMTEyMzU5NmYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYyNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MjRUMDE1MTIzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MGE0NzUzYzMyMDdmZGQ1NDEzMDc5NjIyNTI4YzkxNDM3YzA1NmY0ZGNmODczMGVkYzMzZWI1ZTAyMDIxYjhiNSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.J_fLAPQp2DmQQ8ELVeBKGFwY3DXIXSrDO30LIFK99Eo)
Primary Data Holders therefore end up in a situation where Customer Present calls are effectively all Unattended threshold for the SDH. This creates a situation where the primary and secondary data holders do not have aligned expectations resulting in misaligned statistical expectations and consequential reporting characteristics.
Note: I've created this pretty quickly for consideration in this MI and therefore have not had a chance to pass this through Biza.io's Data Standards Committee.
Area Affected
Change Proposed
Introduce an
x-cds-customer-present
header with a booleantrue
/false
value for all calls to Secondary Data HoldersThe text was updated successfully, but these errors were encountered: