betterfastercheaper - PowerPoint PPT Presentation

Title: betterfastercheaper


1
better/faster/cheaper

• A modular approach to e-government

2
todays purpose

• Describe how new technology is transforming the
  business of Government
• Talk about the role of the E-Government Unit in
  2003
• Describe the new LEGO architecture and how it can
  help you
• Show how one agency has successfully used this
  approach
• Showcase product offerings from Microsoft and IBM
  that may assist with LEGO building

3
agenda

• 900 - 920 Setting the stage - Brendan Boyle
• 920 - 940 The Service Delivery Architecture -
  Larry Holmes
• 930 - 1000 The LEGO architecture - Kent Duston
• 1000 - 1030 Coffee
• 1030 - 1130 Making LEGO work for you - Kent
  Duston
• 1130 - 1200 Case study - Department of Labour
  WorkSite
• 1200 - 100 Lunch
• 100 - 130 LDAP and SEE via LEGO - Mike Pearson
• 130 - 200 The XML LEGO construction kit - Kent
  Duston
• 200 - 300 Vendor session 1 - Microsoft and IBM
• 300 - 400 Vendor session 2 - IBM and Microsoft
• 400 - 430 Optional QA session

4
the shape of the day

• The first half of the morning will talk about the
  e-government strategy and objectives
• The second half of the morning will talk about
  how e-government tools support business
  objectives
• The first half of the afternoon will talk about
  tools and technologies
• The second half of the afternoon will be
  practical vendor sessions

5
attending the right sessions

• The morning sessions are for agency leaders and
  business unit managers
• Lunch is for everyone!
• The afternoon sessions are technically focused
• The vendor sessions are for IT strategists and
  architects

6
setting the stage

• Brendan BoyleDirectorE-Government Unit, State
  Services Commission

7
first principles

• E-government in New Zealand has three
  objectives
• Access to information, services and processes by
  2004
• Delivery of government services by 2007
• Transformation of the operation of government by
  2010
• These objectives are laid down in the
  e-government strategy
• This is the WHY of e-government

8
the service delivery architecture

• The Service Delivery Architecture shows how
  business processes can be delivered by
  e-government
• It is designed to be modular and flexible
• It deliberately does not contain details of
  technologies
• It is the WHAT of e-government

9
the LEGO architecture

• Today we are announcing a modular construction
  kit for agencies
• This architecture is designed to make it easier
  to build applications at a technical level
• It builds on e-GIF standards and many of the
  e-government initiatives of the last two years
• It is the HOW of e-government

10
fitting it together
e-government strategy
strategy
service delivery architecture
tactics
LEGO architecture
implementation
11
how EGU projects fit together

• Standards projects such as e-GIF and the web
  guidelines underpin the LEGO architecture
• Some projects -- such as SEE and portal
  components -- are available as LEGO blocks
• New projects such as the XML gateway will become
  LEGO components
• Large-scale initiatives such as e-procurement and
  authentication are currently independent of the
  LEGO architecture

12
the role of agencies in e-government

• Agencies build the systems and processes to
  fulfill the promise of e-government
• Agencies contribute to the governance of
  e-government and central projects
• Agencies contribute to the development of
  standards and -- as we will see -- the design of
  LEGO blocks

13
governance

• The LEGO architecture uses established governance
  structures
• Agencies are intimately involved in both the
  governance and direction of e-government
• The architecture depends heavily on e-GIF
  standards
• e-GIF has a sophisticated structure of governance
  and standards development

14
leveraging initiatives

• The LEGO architecture is an integrated part of
  the EGU work plan
• It builds on the initiatives of the last two
  years
• e-GIF standards
• Web accessibility guidelines
• Metalogue and the metadata project
• It leverages current and planned EGU
  infrastructure
• Agency initiatives
• The portal
• Shared workspaces
• SEE

15
benefits

• E-government initiatives are delivered by
  agencies, not just EGU
• The components will allow agencies to build
  better e-government applications faster, with
  more flexibility
• Use of the components is charged only on a
  marginal cost recovery basis
• This can make them dramatically cheaper than
  commercial and in-house alternatives
• Agencies can combine the components as they see
  fit, to meet their business goals

16
an example

• The Department of Labour WorkSite portal was
  developed using LEGO components from the EGU
  portal
• It was completed in 8 weeks
• Costs were kept to less than 100K
• Savings of 500K in development and data
  gathering were realised immediately
• Savings of 18K per annum are being made by
  sharing infrastructure
• WorkSite has unquantified savings in annual data
  maintenance

17
using LEGO

• Public Service agencies can use the components as
  of right
• The terms of use are covered in a standard
  Memorandum of Understanding
• Components can be run on agency hardware and
  systems where appropriate
• Costs are recovered on a marginal basis only
• Agencies can submit their own components and
  modify existing components

18
key points

• Todays session is about how you can leverage the
  LEGO components
• While this is a new announcement, it builds on
  the activities of EGU over the last few years
• It is a way for agencies to design and implement
  systems at lower cost whilst ensuring they are
  standards compliant
• The architecture is a toolkit, not a collection
  of finished applications
• Its use is optional, not mandatory

19
an aside from our Minister

• AMD has recently contacted the Government asking
  for consideration in the issuing of RFPs
• Current RFPs are apparently specifying Intel
  processors
• AMD have asked that RFPs specify Intel or
  equivalent processors
• The Minister has asked that I pass this
  recommendation along to you

20
the service delivery architecture

• Larry Holmes
• Senior Advisor
• E-government Unit, State Services Commission

21
todays environment
22
fitting it together
e-government strategy
strategy
service delivery architecture
tactics
LEGO architecture
implementation
23
(No Transcript)
24
what this gives us/implies

• Framework for business process design
• Tells us how business systems are to be
  structured
• Tells us how components operate and interact
• Promotes interoperability between dissimilar
  business processes
• Encourages standardisation while maintaining
  autonomy
• Implies and provides migration path from today
  to where we need to be tomorrow

25
the LEGO architecture

• Kent DustonPortal Business ManagerE-government
  Unit, State Services Commission

26
session agenda

• Overview of the LEGO components
• A closer look at the Search component
• Coffee
• Current components
• Planned components
• How new components are built
• Labour market portal case study
• Lunch

27
defining LEGO

• The components are part of a toolkit that allows
  agencies to build solutions
• The components are based on e-GIF and web
  guidelines
• They are built using industry standards such as
  XML, LDAP and HTTP
• They can be operated by EGU as a service, or
  operated by the agency as infrastructure

28
the components
Web Services
Collaboration Workflow
Gateway Services
Value-added services
Web Guidelines
Core services
Technical Messaging Services
Service Metadata
LDAP Services
Authentication
E-GIF Framework
29
the components

• Some components -- such as search engine and SEE
  -- are available today
• Some components -- such as the XML gateway --
  will be built in the near future
• We expect agencies to contribute components that
  address common business issues
• Once components are certified under e-GIF they
  can be made available to all agencies

30
example - the search component

• This component was developed by EGU as a
  by-product of developing the portal
• Its powered by the Autonomy search engine
• Agencies can call the search functionality from
  their own sites
• The process of using it is invisible to the
  end-user on the website
• Costs are allocated against marginal usage
• This means there are no capital charges for
  hardware or software licensing

31
example - the search component
32
benefits

• Agencies can use an operational search engine
  after performing a few configuration steps
  faster days or weeks rather than months of
  installation and configuration
• No need to license software cheaper avoids
  hundreds of thousands of dollars of capital
  charges for hardware and software
• State of the art search technology better
  more powerful and sophisticated than cheaper
  alternatives

33
how it works
34
commercial arrangements

• The overall license agreement is held by the
  Crown, although negotiated by SSC
• For public sector agencies there are no
  additional licensing requirements
• A Memorandum of Understanding governs the usage
  of the system
• Each agency only pays for its actual, incremental
  usage as measured by the system hosters
• This is re-charged from SSC to the agency
• The MOU is flexible and can easily accommodate
  changing requirements

35
using search

• Contact EGU and discuss your requirements
• Work through the Memorandum of Understanding and
  agree its terms with SSC
• Implement the code changes within your website to
  access the search engine
• Test the code against the EGU development/testing
  environment
• Once youre happy, activate the system on your
  website
• Authorise the invoice when it arrives!

36
summary

• The building blocks provide modular functionality
  without the need for capital investment
• Using a building block is much faster and easier
  than having to implement a complete system from
  scratch
• You only pay for incremental usage
• You can make use of a building block without
  having to build up lots of expertise in
  specialist technologies

37
questions?
38
coffee break
39
contacts

• Business stuff Kent Duston
• Kent.duston_at_portal.govt.nz
• DDI 04 495 2855
• Technical stuff Ferry Hendrikx
• Ferry.hendrikx_at_portal.govt.nz
• DDI 04 495 2845

40
session agenda

• Current components
• Planned components
• How new components are built
• Labour market portal case study
• Lunch

41
current components

• Search engine that will allow searching across
  Internet, Extranet and Intranet sites
• Metadata repository that contains information on
  central government and local government services
• Shared workspaces (in prototype form) that allow
  inter-agency collaboration
• Mailing list application that allows subscribers
  to participate in e-mail discussions
• SEEmail that allows agencies to send and receive
  secure inter-agency e-mail

42
planned components

• LDAP services that provide directory capabilities
  for applications
• XML gateway that allows structured data
  interchange between applications
• Production shared workspaces
• Inter-agency workflow that allows agencies to
  collaborate in shared business processes
• Government news syndication that provides a
  single point of update for Internet news releases

43
the specifics - search engine

• Powered by Autonomy
• Can search across Internet, Extranet and Intranet
  sites
• Can be configured to operate within a closed
  user group
• Uses HTTP and XML as the interface
• Supports natural language and keyword searching
• Requires no hardware investment by the agency
• Cost recovery model is pay-per-search
• Expect costs of tens to hundreds of dollars per
  month

44
service metadata

• More than 3,500 records have been collected
  across central and local government
• Most public-facing government services are
  described
• Can be filtered and presented as necessary to
  suit the needs of different audiences
• Kept up to date by individual agencies as part of
  their portal charter obligations
• Uses HTTP and XML as the interfaces
• Cost recovery model is pay-per-record-accessed
• Expect costs of tens of dollars per month

45
prototype shared workspaces

• Toolbox for inter-agency collaboration
• Users can extend outside government to foster
  collaboration between agencies and stakeholders
• Includes mailing list, discussion groups, secure
  document sharing and project resource sharing
• Has authentication capabilities
• Based on commercial web-based software components
  and open standards
• Cost recovery model is still under discussion
  with prototype users
• Full productionisation will follow the budget

46
mailing list server

• Available as part of the shared workspace suite,
  can be configured as a stand-alone service
• Allows people to subscribe and unsubscribe from
  e-mail lists
• Is moderated and users are authenticated to stop
  spam and re-mailing
• Supports attachments but doesnt re-mail them for
  efficiency
• Based on commercial web-based software and uses
  open standards
• Cost recovery model is pay-per-list
• Expect costs of tens of dollars per month

47
SEE (Secure Electronic Environment)

• SEE is a technical toolkit, not a finished
  application
• It is made up of SEEmail and SEEkey
• Both are based on open standards but must be
  implemented by agencies to suit their individual
  architecture
• The secure mail transport and strong
  authentication allow agencies to build encrypted
  messaging
• The components can certify both individuals and
  agencies
• The heart of security is authentication and SEE
  provides a dependable way of achieving this

48
LDAP services

• This is a planned component, available Q1 2003
• Based on the SEE LDAP schema
• Acts as a central agency address book, containing
  core information about agencies and their public
  address information
• Agencies can link their own LDAP directories to
  the core directory
• Agencies control what information is publicly
  available in their directories
• The service is free of charge

49
XML gateway

• This is planned component, available in prototype
  Q1 2003, production Q2 2003
• Allows agencies to interchange data without the
  cost and complexity of point-to-point links
• First use will be for agencies wanting to get
  metadata in and out of the Metalogue system
• Built on commercial products from Microsoft and
  IBM
• The vendor sessions this afternoon will cover how
  this system will work

50
the LEGO architecture

• Kent DustonPortal Business ManagerE-government
  Unit, State Services Commission

51
session agenda

• Overview of the LEGO components
• A closer look at the Search component
• Coffee
• Current components
• Planned components
• How new components are built
• Labour market portal case study
• Lunch

52
defining LEGO

• The components are part of a toolkit that allows
  agencies to build solutions
• The components are based on e-GIF and web
  guidelines
• They are built using industry standards such as
  XML, LDAP and HTTP
• They can be operated by EGU as a service, or
  operated by the agency as infrastructure

53
the components
Web Services
Collaboration Workflow
Gateway Services
Value-added services
Web Guidelines
Core services
Technical Messaging Services
Service Metadata
LDAP Services
Authentication
E-GIF Framework
54
the components

• Some components -- such as search engine and SEE
  -- are available today
• Some components -- such as the XML gateway --
  will be built in the near future
• We expect agencies to contribute components that
  address common business issues
• Once components are certified under e-GIF they
  can be made available to all agencies

55
example - the search component

• This component was developed by EGU as a
  by-product of developing the portal
• Its powered by the Autonomy search engine
• Agencies can call the search functionality from
  their own sites
• The process of using it is invisible to the
  end-user on the website
• Costs are allocated against marginal usage
• This means there are no capital charges for
  hardware or software licensing

56
example - the search component
57
benefits

• Agencies can use an operational search engine
  after performing a few configuration steps
  faster days or weeks rather than months of
  installation and configuration
• No need to license software cheaper avoids
  hundreds of thousands of dollars of capital
  charges for hardware and software
• State of the art search technology better
  more powerful and sophisticated than cheaper
  alternatives

58
how it works
59
commercial arrangements

• The overall license agreement is held by the
  Crown, although negotiated by SSC
• For public sector agencies there are no
  additional licensing requirements
• A Memorandum of Understanding governs the usage
  of the system
• Each agency only pays for its actual, incremental
  usage as measured by the system hosters
• This is re-charged from SSC to the agency
• The MOU is flexible and can easily accommodate
  changing requirements

60
using search

• Contact EGU and discuss your requirements
• Work through the Memorandum of Understanding and
  agree its terms with SSC
• Implement the code changes within your website to
  access the search engine
• Test the code against the EGU development/testing
  environment
• Once youre happy, activate the system on your
  website
• Authorise the invoice when it arrives!

61
summary

• The building blocks provide modular functionality
  without the need for capital investment
• Using a building block is much faster and easier
  than having to implement a complete system from
  scratch
• You only pay for incremental usage
• You can make use of a building block without
  having to build up lots of expertise in
  specialist technologies

62
questions?
63
coffee break
64
contacts

• Business stuff Kent Duston
• Kent.duston_at_portal.govt.nz
• DDI 04 495 2855
• Technical stuff Ferry Hendrikx
• Ferry.hendrikx_at_portal.govt.nz
• DDI 04 495 2845

65
session agenda

• Current components
• Planned components
• How new components are built
• Labour market portal case study
• Lunch

66
current components

• Search engine that will allow searching across
  Internet, Extranet and Intranet sites
• Metadata repository that contains information on
  central government and local government services
• Shared workspaces (in prototype form) that allow
  inter-agency collaboration
• Mailing list application that allows subscribers
  to participate in e-mail discussions
• SEEmail that allows agencies to send and receive
  secure inter-agency e-mail

67
planned components

• LDAP services that provide directory capabilities
  for applications
• XML gateway that allows structured data
  interchange between applications
• Production shared workspaces
• Inter-agency workflow that allows agencies to
  collaborate in shared business processes
• Government news syndication that provides a
  single point of update for Internet news releases

68
the specifics - search engine

• Powered by Autonomy
• Can search across Internet, Extranet and Intranet
  sites
• Can be configured to operate within a closed
  user group
• Uses HTTP and XML as the interface
• Supports natural language and keyword searching
• Requires no hardware investment by the agency
• Cost recovery model is pay-per-search
• Expect costs of tens to hundreds of dollars per
  month

69
service metadata

• More than 3,500 records have been collected
  across central and local government
• Most public-facing government services are
  described
• Can be filtered and presented as necessary to
  suit the needs of different audiences
• Kept up to date by individual agencies as part of
  their portal charter obligations
• Uses HTTP and XML as the interfaces
• Cost recovery model is pay-per-record-accessed
• Expect costs of tens of dollars per month

70
prototype shared workspaces

• Toolbox for inter-agency collaboration
• Users can extend outside government to foster
  collaboration between agencies and stakeholders
• Includes mailing list, discussion groups, secure
  document sharing and project resource sharing
• Has authentication capabilities
• Based on commercial web-based software components
  and open standards
• Cost recovery model is still under discussion
  with prototype users
• Full productionisation will follow the budget

71
mailing list server

• Available as part of the shared workspace suite,
  can be configured as a stand-alone service
• Allows people to subscribe and unsubscribe from
  e-mail lists
• Is moderated and users are authenticated to stop
  spam and re-mailing
• Supports attachments but doesnt re-mail them for
  efficiency
• Based on commercial web-based software and uses
  open standards
• Cost recovery model is pay-per-list
• Expect costs of tens of dollars per month

72
SEE (Secure Electronic Environment)

• SEE is a technical toolkit, not a finished
  application
• It is made up of SEEmail and SEEkey
• Both are based on open standards but must be
  implemented by agencies to suit their individual
  architecture
• The secure mail transport and strong
  authentication allow agencies to build encrypted
  messaging
• The components can certify both individuals and
  agencies
• The heart of security is authentication and SEE
  provides a dependable way of achieving this

73
LDAP services

• This is a planned component, available Q1 2003
• Based on the SEE LDAP schema
• Acts as a central agency address book, containing
  core information about agencies and their public
  address information
• Agencies can link their own LDAP directories to
  the core directory
• Agencies control what information is publicly
  available in their directories
• The service is free of charge

74
XML gateway

• This is planned component, available in prototype
  Q1 2003, production Q2 2003
• Allows agencies to interchange data without the
  cost and complexity of point-to-point links
• First use will be for agencies wanting to get
  metadata in and out of the Metalogue system
• Built on commercial products from Microsoft and
  IBM
• The vendor sessions this afternoon will cover how
  this system will work

75
inter-agency workflow

• Planned component, available in prototype Q2
  2003, production Q3 2003
• Allows agencies to build complex workflows that
  operate both within and between agencies
• Based on Lotus Domino Workflow technology
• Completely web-based, with core servers hosted by
  Datacom
• First use will be metadata workflows within the
  Metalogue system
• Agencies have control over workflows and business
  rules
• Costs are still being worked out

76
news syndication

• Planned component, prototype available in Q1
  2003, production in Q2 2003
• Allows agencies to have their news stories
  automatically harvested by search engine
• Stories are then aggregated and published through
  the XML gateway
• Stories need to be in RSS/NewsML format as per
  proposed e-GIF standard
• No cost to agencies to have their stories
  harvested
• No cost to agencies wanting to subscribe to the
  news feed

77
getting more information

• Current and planned services will have a Fact
  Sheet describing them, published by EGU
• These Fact Sheets are under development and will
  be progressively released over the next few
  months
• A draft MOU covering the commercial aspects is
  available now
• If youre interested in using any of the
  services, contact me in the first instanceKent
  DustonDDI 04 495 2855E-mail kent.duston_at_portal.g
  ovt.nz

78
services summary

• There are a range of services available
• These can be used by agencies at minimal cost to
  extend their in-house capabilities
• The services can be combined into completed
  systems in whatever manner agencies see fit
• There will be a steady stream of new components
  released throughout 2003

79
building new components

• Most of the components weve described so far
  have been built by EGU
• This is because of expedience, not philosophy
• We expect a great many components to be
  contributed by agencies
• This will give the Government the greatest
  leverage from its IT expenditure

80
building a new component

• Many agencies have developed systems that are
  potentially useful to others
• These systems can be standardised and distributed
  as LEGO components
• Sometimes the agency can continue with
  maintenance and development of the system
• Sometimes the agency may want to hand maintenance
  and future development to the community
• Either the agency or an external party can host
  and operate the system for others

81
step 1 build the system

• Agencies are building systems all the time that
  address common business needs
• These should be built in accordance with the
  e-GIF standards and Web Guidelines
• Agencies can consider making them available to
  others at the point of design
• EGU can provide advice on how best to
  generalise the system for wider government use
• There are generally few costs associated with
  doing this

82
step 2 certify the system

• Once the system is complete, it needs to be e-GIF
  certified and documented
• This is so other agencies know how to use it and
  integrate it
• EGU will assist the agency with shepherding the
  component through the e-GIF process
• EGU will assist with preparing a Fact Sheet on
  the component and notifying the wider community
  about it

83
step 3 work out the details

• The agency will have to decide whether they wish
  to host the system for other agencies
• If not, the hosting and maintenance will have to
  be arranged with an external service provider
• The agency will have to decide how the system
  will be maintained and developed in the future
• This framework will need to be incorporated into
  a standard MOU for the component
• EGU can provide the technical and commercial
  assistance necessary to work through this process