[ARCHIVE] ACCC Communication with Participants

Note: This article is out of date and has been archived.

Please see the CDR participant portal guide and the CDR participant on-boarding guide for the latest information on ACCC communication with participants.

Archived Text

The ACCC will have the need to communicate with your organisation from the point in time you commence on-boarding through to active participation for a number of reasons.  Each Communication purpose tabled below explains who will be contacted and where the contact details for your organisation can be maintained.

Communication Purpose	Contact	System  Nominated/ Maintained in	Communication method	Comments
CDR ecosystem incidents	Agent licence	Service Management (Jira)	System notification (Jira) / Email / Phone	Where tickets have been raised by the participant alerting the ACCC to issues emerging in the ecosystem, from on-boarding commencement through to active and ongoing participation.
CDR Logo – CDR Trademark Licence Agreement	Legal Authority Contact	CDR Participant Portal | User Guide	Email / Phone	The ACCC will make contact if the terms in the Licence Agreement change or if there are any other changes to the CDR Logo. Refer Rule 5.12(1)(f)
Certificates (Agreements)	Legal Authority Contact	CDR Participant Portal | User Guide	Email / Phone	The ACCC will make contact if the terms in the Agreements change or if any other changes affect use of the certificates.  This communication purpose excludes technical configuration of the certificates.
Certificates (Technical)	Primary IT Contact (PITC)	CDR Participant Portal | User Guide	Email / Phone	The ACCC will use this communications method to make contact with a Primary IT Contact for the purpose of support, or to request an action of the PITC.  The ACCC will not utilise this method to transfer sensitive certificate related information or data.  Participant PITCs should utilise the CDR Participant Portal to action Certificate related requests.
Compliance and Enforcement	Primary Business Contact	CDR Participant Portal | User Guide	Letter / Email / Phone	Where there is a need for the ACCC CDR Compliance and Enforcement team to contact you about CDR compliance-related matters, from on-boarding commencement through to active and ongoing participation.
Conformance Test Suite	Primary IT Contact	CDR Participant Portal | User Guide	Email / Phone	Communication likely from on-boarding commencement through to active and ongoing participation.
Get Metrics	Primary IT Contact	CDR Participant Portal | User Guide	Email / Phone / Jira?	ACCC is unable to connect to the endpoints, identification of Data Quality issues etc.
On-boarding	Authorised Business Contacts / Authorised IT Contacts	CDR Participant Portal | User Guide	Email / Phone	Coordination of On-boarding and CTS activities through to activation on the CDR Register.
PRD Data Quality	Data Holder email address	CDR Participant Portal | User Guide	Email	This information is provided during on-boarding and appears in the ‘email’ field for the Data Holder once selected on the CDR Register find-a-provider page.  Applies to all Data Holder Brands for a Data Holder.
Reporting	Primary Business Contact	CDR Participant Portal | User Guide	Letter / Email / Phone	Explore issues with reporting for purposes of rule 9.4, including data inaccuracy or anomalies emerging in analysis on data collected. Refer Rule 9.4
Temporary direction to refrain from processing consumer data requests	Primary and Authorised Business Contacts; Primary and Authorised IT Contacts	CDR Participant Portal | User Guide	Trusted communications	This could stem from ecosystem wide issues such as a cyber attack, major issues with participant platforms, unplanned and extended outages, data breaches etc. Refer Rule 5.34
Temporary restriction on use of Register (DH)	Primary and Authorised Business Contacts; Primary and Authorised IT Contacts	CDR Participant Portal | User Guide	Trusted communications	This could stem from ecosystem wide issues such as a cyber attack, major issues with the platform, unplanned and extended outages etc. Refer Rule 5.33