Implementation

The architecture is integral to the e-government strategy. Alignment with the strategy requires alignment with the architecture. Use of the architecture is enhanced by a clear understanding of the requirements and obligations on agencies, EGU, and central agencies to collaborate in making it work.

Parts of the architecture are already technology standards in the e-GIF. The e-GIF, as a framework of standards, has been developed or implemented by individual and joint agency e-government initiatives. Implementing the architecture is progressive, not retrospective. Agencies need to align their new initiatives accordingly.

In the short term, implementation steps now needed are:

1. Finalise the initial design.

2. Gain necessary understanding and buy-in - educate agencies in the architecture, including providing an easy to use architecture document, using pictures and succinct examples that describe principles, standards and processes

3. Establish the governance arrangements - service delivery architecture cannot exist in a vacuum. A strong governance structure is essential to the development and implementation of an enterprise e-government architecture. Strong executive support; concise, updated documentation; and close alliance with the governance process are critical to successfully implementing the e-government architecture.

4. Embed the architecture into key decision processes, such as Treasury decision making on investment proposals - the decision process must use the architecture as part of the e-government project approval process. Architectural review and compliance ensures that projects adhere to the architectural principles and standards and use shared services - that is, moving away from silo-based development of duplicative infrastructure.

This will be achieved using a reference group drawn the state sector. Their role will be to finalise design and governance arrangements and assist with helping the sector to understand and use the architecture. This group will be composed of senior department business leaders, education, external business representatives and CIO's. In addition, consideration would be given to including advocacy groups such as citizen advocacy group(s) and business users group(s) in order to tie architecture development to customer needs.

In the longer term, the implementation steps are:

1. Progressive implementation at agency level - There should be a set of procedures to follow for architectural review, compliance certification and the waiver process. However, primary responsibility for evaluating compliance should be on the system builder, not an oversight group. This also encourages builder feedback to the architecture group, which in turn drives positive changes to the architecture itself.

2. Maintenance of and evolving the architecture - Create a process to evolve and maintain the architecture, including a process for different agencies to cooperate on architectural frameworks and delivering components (current and new) that will enable future e-government initiatives, or both (depending on budgetary constraints and other political and operational priorities).