Skip to content.
|Networking government in New Zealand.
You are here: Home » About e-govt » E-government Strategy » Strategy update - June 2003 » E-government programme - planning information

E-government programme - planning information

Main E-government Unit activity

During 2003/04 the Unit will have five main areas of activity:

  • progressing major development projects;

  • implementation and uptake of the service delivery architecture.

  • operating and enhancing e-government infrastructure;

  • developing e-government policy and strategy; and

  • relationship management and support for agencies.

Major development projects

The Unit will undertake the following major project activity:

Authentication

  • consult agencies and other stakeholders about options for authentication;

  • recommend to Ministers the choice of authentication solution(s); and

  • begin to implement the chosen approach(es) for authentication.

Shared workspace

  • operate pilot workspaces to evaluate user needs and technology requirements;

  • complete the business case for shared workspace; and

  • progressively implement production versions of shared workspace tools from July 2003 onwards.

Electronic procurement (GoProcureTM )

  • run first-phase operations with pilot agencies and evaluate options for further roll out.

Implementation and uptake of service delivery architecture

The service delivery architecture now sits at the heart of the e-government programme. It is the key to both better delivery of service, and better use of taxpayer's resources. Its development and widespread uptake is now fundamental to the work of the E-government Unit. There are two challenges here:

  • building it in a way that involves agencies and allows their diverse operational requirements to be reflected in the architecture; and

  • getting widespread uptake of the architecture by agencies.

Over the next 12 months the E-government Unit and agencies will:

  • test and refine the architecture;

  • build components of the architecture or sponsor their development;

  • develop ongoing governance arrangements for the architecture; and

  • identify strategies and opportunities to use the architecture to take offline services online, and integrate services where appropriate.

Operating and enhancing e-government infrastructure

The Unit has responsibility for operating some of the shared infrastructure that underpins the e-government programme. Currently, this infrastructure includes:

  • the Portal;

  • MetalogueTM (the metadata collection and metadata management tools);

  • S.E.E. (the Secure Electronic Environment);and

  • e-GIF (the Interoperability Framework).

During the year, the following activity is scheduled:

Portal & MetalogueTM

  • bed-in and operate current version of the government portal;

  • leverage the portal infrastructure;

  • enhance MetalogueTM;

  • moderate the .govt.nz domain;

  • further development of the portal;

  • expand the metadata collection; and

  • improve the metadata collection processes.

S.E.E.

  • develop and implement S.E.E. Mail version 2; and

  • manage process of continued agency uptake of S.E.E. Mail.

e-GIF

  • support the operation of e-GIF Management Committee;

  • facilitate the operation of e-GIF working groups; and

  • ensure the overall value of the e-GIF is maintained and enhanced.

E-government policy and strategy

There is an ongoing requirement for e-government policy and strategy. During the year the Unit will be developing policy and/or strategy around:

  • governance;

  • funding of e-government (especially on how to value e-government initiatives);

  • rationalising and consolidating government ICT infrastructures, applications and data to deliver better quality services, and improved value from taxpayer's funds;

  • research and evaluation on:

    • the success of the e-government programme;

    • agency e-government activity;

    • future directions for the e-government strategy and programme; and

    • the e-government contribution to improving public management.

  • the need for a channel strategy;

  • linkages to e-commerce and digital opportunities initiatives; and

  • participation.

Relationship management and support for agencies

This is a major part of the Unit's work. During the year, there will be a focus on:

  • continuing to manage relationships and communications with government agencies (Public Service, State sector and local government) and other e-government stakeholders (e.g. community organisations, Māori, business organisations, ICT suppliers, media);

  • increasing the number of agencies and the range of people in each agency that the Unit works with;

  • brokering relations and facilitating clusters of agencies working on e-government where appropriate; and

  • working to identify and leverage all-of-government opportunities and benefits from specific e-initiatives undertaken by agencies.

Work programme for agencies and the E-government Unit

This section sets out the joint work programmes for agencies and the E-government Unit to June 2005. It should be read alongside Charts A and B. Chart A [PDF, 50KB] provides an overview of the work streams and their relationship to one another. Chart B [PDF, 50KB] shows how agencies are expected to respond or contribute to the work streams. Each work stream is identified with a reference number in the tables below and on the charts.

The major work streams of the programme are described briefly below and in more detail on the e-government website (http://www.e-government.govt.nz/). This does not, of course, describe entirely what each agency should or may do with regard to e-government. Much of that detail will be specific to individual agencies, and integrated into their future planning.

Agency and E-government Unit (EGU) responsibilities in the work streams to June 2005 are set out below. The need for agencies to plan for this work, and for the E-government Unit to consult with stakeholders, is implied.

In some cases, ongoing management and operation of relationships, services, and infrastructure is currently identified as a responsibility of the E-government Unit to work in conjunction with lead agencies. The governance work to be carried out in coming months will determine what organisational structures and ownership arrangements are required.

 

Work streams

Agency Responsibilities

EGU Responsibilities

1

Strategy

Ongoing development of E-government Strategy

  • Participate in consultation (as required).

  • Endorse all-of-government strategies (as required).

  • Incorporate e-government into agency business plans (annually).

  • Contribute to the development and common understanding of e-government (ongoing).

  • Consult SSC over alignment of e-initiatives with the E-government Strategy.

  • Deliver revised E-government Strategy and work programmes:

    • Updated e-government work programme (by June 2004)

    • Updated E-government Strategy (by June 2005)

  • Assist agencies with business planning and strategy development (as required).

2

Policy development

Develop policy on governance and operational arrangements for e-government initiatives and on funding of e-government initiatives.

Investigate the feasibility and need for a channel strategy.

Investigate participation issues and opportunities.

Examine the scope and feasibility of rationalising and consolidating government ICT infrastructures, applications, and data to deliver better quality services, and improved value from taxpayer's funds.

  • Contribute to the development of governance arrangements (ongoing).

  • Some agencies will become lead agencies for hosting specific elements of e-government infrastructure.

  • Some agencies will become lead agencies for specific elements of the ongoing governance or operations portfolio, including identifying funding requirements and sources (as required).

  • Contribute agency views and information to policy development processes.

  • Develop policy advice on

    • governance and operational arrangements for e-government initiatives and infrastructure,

    • funding of e-government initiatives

    • the feasibility and need for a service delivery channel strategy

    • opportunities to address issues around participation

    • the scope and feasibility of rationalising and consolidating government ICT infrastructures, applications and data to deliver better quality services, and improved value from taxpayer's funds.

  • Implement policies where required.

3

Research and evaluation: Evaluate the success of the e-government programme and agency initiatives.

Undertake research to inform the e-government programme, and to inform policy advice on the public management system.

  • Share relevant e-government research with e-government networks (ongoing).

  • Provide input into the e-awareness tool to inform evaluation of e-government progress (as required).

  • Demonstrate alignment of agency initiatives with the e-government strategy where appropriate (ongoing).

  • Develop facility for effectively sharing research across government.

  • Improve the e-awareness information-gathering tool to inform the evaluation of e-government progress.

  • Report on e-government uptake to Ministers and agencies (ongoing).

  • Develop and operate a framework for evaluating the alignment of agency e-government initiatives with the e-government strategy.

4

Service delivery architecture

Develop, test, and implement a service delivery architecture for government.

Identify opportunities for government services to be brought online and integrated where appropriate.

  • Contribute to the refinement and testing of the service delivery architecture (as required).

  • Contribute to the ongoing maintenance and development of the service delivery architecture (as required).

  • Use the service delivery architecture to inform:

    • how services are presented to people (User services & guidance);

    • how service delivery is actually electronically enabled (Service enabling tools); and

    • how agencies connect to one another and their customers (Connection tools).

  • Identify and prioritise services for delivery online and incorporate in business plans and other relevant accountability documents where appropriate (ongoing).

  • Implement online delivery of appropriate services (ongoing).

  • Refine and test the service delivery architecture (ongoing).

  • Work with agencies to identify opportunities to expand online service delivery across the public sector (ongoing).

  • Support agencies in using the service delivery architecture.

5

Shared Workspace

Pilot secure electronic shared workspaces for projects and policy development across government agencies, and scale up to production systems (if required and funded).

  • Participate in pilot studies as required (June 2003 onwards).

  • Use shared workspaces (when implemented).

  • Manage and evaluate pilots (to June 2004).

  • Implement shared workspace application (ongoing).

6

Authentication

Develop and implement an all-of-government framework for online authentication to ensure government services delivered over the Internet are going to the right person and their privacy is protected.

  • Contribute to detailed design of the agreed authentication solution (to March 2004)

  • Use solution developed by the EGU (contingent on Cabinet approval and business needs of agencies) (from April 2004).

  • Detailed design of agreed authentication solution (from June 2003).

  • Build and implement agreed solution (from April 2004).

7

E-procurement

Evaluate viability of GoProcure as electronic purchasing sysem for government.

  • Participate (phase 1 agencies) in e-procurement Phase 1 pilot.

  • Assess procurement practices and future requirements, including participation in syndicated procurement, use of electronic tender systems, online catalogue access and fulfilment, full integration of e-procurement systems with corporate financial and logistics systems (ongoing).

  • Adopt procurement best practices; identify opportunities for leading or using syndicated procurement (ongoing).

  • Adopt the all-of-government e-procurement solution (contingent on phase 1 results).

  • Provide overall project management and support to agencies during Phase 1 pilot.

  • Facilitate uptake of best practice procurement and syndicated procurement (ongoing).

  • Advise Ministers on whether to proceed to rollout or not.

8

S.E.E.

Implement S.E.E. Mail v2 to facilitate the secure exchange of email between agencies.

Support agency initiatives using S.E.E. Mail, PKI and Directory.

  • Implement S.E.E. Mail v2 (by August 2003).

  • Use S.E.E. PKI when deploying digital certificates to authenticate government employees using government business applications (as required).

  • Ensure that directory developments are consistent with the S.E.E. Directory policy.

  • Scope linkages to all-of-government directory (when required).

  • Integrate business applications and systems with directory where applicable (when required).

  • Provide support and advice to agencies implementing S.E.E. Mail (ongoing).

  • Manage supplier accreditation (ongoing).

  • Maintain S.E.E. PKI policy framework.

  • Build directory to support portal operations.

9

Portal and Metalogue Operate and further develop the New Zealand Government web portal (www.govt.nz).

Grow and leverage Metalogue and other portal components to support the development and implementation of sector portals and other e-government infrastructure by sectors, clusters and agencies.

  • Adopt Service Level Agreements (SLAs) with the EGU for portal operations.

  • Adopt trust and privacy charters for the operation of the portal.

  • Populate Metalogue with descriptions of services and information resources using NZGLS metadata standard and thesaurus terms (ongoing).

  • Enhance portal (ongoing).

  • Provide system and processes for agencies to capture and manage NZGLS metadata centrally.

  • Facilitate ongoing collection of metadata by agencies (ongoing).

10

Interoperability Framework

Support the ongoing development and operation of the E-government Interoperability Framework (e-GIF).

  • Use the interoperability framework to guide the design and implementation of service delivery, business systems, and information that crosses agency boundaries (ongoing).

  • Contribute to the ongoing development of the interoperability framework (as required).

  • Form, lead and contribute to interoperability working groups to develop standards to address interoperability issues (as required).

  • Ensure ongoing development and management of the interoperability framework (ongoing).

  • Support and facilitate the formation and work of interoperability working groups (as required).

  • Address emerging interoperability issues (ongoing).

  • Support Interoperability Management Committee (ongoing).

[ Previous ]