Technical specification process

A technical specification provides IT system and application information affecting participants as a result of a rule change or a project. It communicates the design and implementation timeline so participants can plan their IT resources to update their own systems.

Technical specifications are related to releases. The pre-production and production release dates determine the projects going into the release. Therefore, a release can contain multiple projects.

AEMO Australian Energy Market Operator's process for producing a technical specification: 

• Based on the Solution Architecture Design and Requirements, the initial draft of the technical specification is published to the participants.
• Once the Design is complete, an updated version of the document is published.
• The technical specification undergoes multiple revisions monthly with design, development, testing, and timeline updates.

• The FAQ chapter of technical specifications is based on participant questions after the MSUG Market Systems User Group meetings.

  The technical specification document is the source of truth during the project lifecycle.

• To maintain a single-source of truth during the project, content deliverables such as online help and the API Application Programming Interface; a set of clearly defined methods of communication between various software components. reference are only published on the pre-production release date.
• The final technical specification version is published at the production release once the content deliverables become the source of truth.
• Participants can ask questions or provide feedback in MSUG Meetings or logging a call to AEMO's support hub.