Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Presentation Slides

276 views

Published on

  • Be the first to comment

  • Be the first to like this

Presentation Slides

  1. 1. Australian Government Architecture November 2007 Trevor Smallwood Department of Finance and Administration [email_address] 6215 1679
  2. 2. Agenda <ul><li>Who are we? </li></ul><ul><li>What have we done? </li></ul><ul><li>Why have we done it? </li></ul><ul><li>How will it make a difference? </li></ul>
  3. 3. About AGIMO <ul><li>The Australian Government Information Management Office (AGIMO), Department of Finance and Administration is working to make Australia a leader in the productive application of information and communication technologies (ICT) to government administration information and services. </li></ul><ul><li>AGIMO fosters the efficient and effective use of information and communications technology (ICT) by Australian Government departments and agencies.  It provides strategic advice, activities and representation relating to the application of ICT to government administration, information and services. </li></ul><ul><li>www.agimo.gov.au </li></ul>
  4. 4. Responsive Government <ul><li>Investing for Growth </li></ul><ul><li>Government Online </li></ul><ul><li>Better Services, BetterGovernment </li></ul><ul><li>Responsive Government </li></ul>
  5. 5. Capability Goal <ul><li>Our aim is to produce a portfolio of ICT assets that can be reused in new combinations across government agencies. The purpose is to improve citizen service , to better respond to government change, to improve government efficiency and to provide capabilities that will support future policy needs . </li></ul><ul><li>To do this we are developing an Australian Government service-oriented architecture to define the frameworks, components, standards, patterns and principles that will guide government investment decision-making and government project development. </li></ul><ul><li>We are also developing a series of frameworks, tools and governance structures that will support increased standardisation, reduced duplication and improved collaboration between agencies . </li></ul>
  6. 6. Governance Management Advisory Committee Secretaries’ Committee on ICT Business Process Transformation Committee CIO Committee AGSAWG
  7. 7. Australian Government Architecture Framework
  8. 8. Principles <ul><li>Cross-Agency Services Architecture Principles </li></ul><ul><li>Published in April 2007 </li></ul><ul><li>Summary of the principles </li></ul><ul><ul><li>Bi-fold brochure </li></ul></ul><ul><li>Full text of the principles </li></ul><ul><ul><li>agimo.gov.au </li></ul></ul>
  9. 9. Australian Government Architecture (AGA) <ul><li>Endorsed by CIOC </li></ul><ul><li>Published in June </li></ul><ul><li>Focus on: </li></ul><ul><ul><li>Service Reference Model (SRM) </li></ul></ul><ul><ul><li>Data Reference Model (DRM) </li></ul></ul><ul><ul><li>Technical Reference Model (TRM) </li></ul></ul><ul><li>Full text of the Reference Models </li></ul><ul><ul><li>Hard copy reference </li></ul></ul><ul><ul><li>agimo.gov.au </li></ul></ul><ul><li>Funding proposals for 2008/09 will be mapped to the SRM </li></ul>Note!
  10. 10. Reference Models - SRM Services level 2
  11. 11. NPP’s, Business Cases Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Business Case This is a paaper that has been written to demonstrate What a document looks like When it is written up and produced On an etremely small type face, but it will show people looking at this slide that it does represent a document covered with text The structure of the document is not at all obvious but I may become clearer Google News Alert for: 'enterprise architecture','soa' Putting the A into SOA is a vital step Computerworld New Zealand - Auckland,New Zealand Having (and following) an enterprise architecture can also avoid a classic mistake: treating SOA as a departmental issue. SOA is too big to tackle all at ... See all stories on this topic Java Feature — The Holy Grail of Database Independence Map Analyse Finance - AGA and NPPs Why no business capability? 12 Opportunity for service reuse? Why no data involved?
  12. 12. New Policy Proposals Business Cases Project C Project B Project A Capability Assessments ICT Investment Proposals Projects Implemented Solutions Capabilities Re-use, shared services, patterns, templates Gaps, overlaps Patterns, templates Mapping Investments
  13. 13. Sample Budget Assessment
  14. 14. Decision-making Yesterday Today Tomorrow Opportunity Possibility Project Management Architecture Program Management Strategy Operations Review Portfolio Management Demand
  15. 15. Reactive Proactive Capability Welfare Policy Example Perspective Yesterday Today Tomorrow Era Policy/Technology Continuum Policy Strategy Safety Net Participation Attainment Policy Target Policy Driver Customer Focus Delivery Output Delivery Structure Value Model Application Architecture Technology Focus Locus of Contact Delivery Provisioning Symptoms Barriers Causes Poverty Economy Well-being Circumstance Behaviour Responsibility Payments Referrals Pre-emptions Central Local Virtual Value Chain Value Shop Value Network Procedural Service Oriented Event Driven Database Connectivity Embedded Processing Agency Provider Nodes Individual Assessment Service Offer Orchestration Preventive
  16. 16. Using the Reference Models <ul><li>Common language for classification of ICT asset base’ </li></ul><ul><li>Project footprint, revealing work impact, relevance to priorities and need for cooperation and collaboration. </li></ul><ul><li>Asset footprint, revealing health and supporting change impact assessment. </li></ul><ul><li>Strategy footprint revealing strategic needs and gaps on the ICT asset-base. </li></ul><ul><li>Investment footprint, showing investment strengths, weaknesses, overlaps and gaps. </li></ul><ul><li>Strategy repository holding principles, standards and patterns to be implemented to meet future strategic needs. </li></ul><ul><li>Communication tool to discuss impacts and implications with stakeholders. </li></ul><ul><li>Knowledge footprint, to be used with “customers” and stakeholders to reveal knowledge gaps in necessary information to complete a strategy or project. </li></ul>
  17. 17. Services & Reuse More Generic More Generic Government Service Inbound Services Eg. Registration Authentication Circumstances Eg. Case Management Compliance Eg. Notification Payment More Specific Assessment Services Review Services Outbound Services
  18. 18. Services & Reuse Presentation Orchestration Resources More Flexible More Stable
  19. 19. 3 rd Parties On Phone On Line Event Service On Site Event Process Management (back office) Government Business Process Management Community Access Point Service Finder Intensive Service Assisted Service Self Service Safety-net Participation Responsible Government Service Delivery Blueprint 1 2 3 4 5 6 7 No-one left out No Wrong Door One Stop Shop Self Service Straight-through Service Event Automated Service Lead Agency A Lead Agency B Agency C Agency Z Org 1 Org n Employment Health International Travel Justice Education Welfare Security
  20. 20. <ul><li>The individual outcomes layer (1) represents a high level view of recipient behaviours that recognises variant abilities and also policy vision. There are people who will not be able to look after themselves and will need a safety net . These are typically people with severe disabilities, deprivations or strong anti-social proclivities. There are people who lack motivation and/or skills to look after themselves and will need assistance and encouragement to participate in the society and the economy. The majority of people are capable and willing to be responsible in their relationship with government policy and programs. Harnessing this responsibility will help improve efficiency, effectiveness and satisfaction while at the same time releasing resources for more intensive work. </li></ul><ul><li>The quality of service layer (2) defines the service delivery value that the strategy offers Australians and our visitors. Qualities of service are strongly focussed on the capabilities of people represented in the individual outcomes layer. At the intensive end, we need to ensure that no one is left out. We need to help those who can get on their own two feet with a little assistance, we need to give control to those who want to be in control and we should make things as convenient and automated as is efficient and effective. </li></ul><ul><li>The service type layer (3) lists the four main approaches available for service delivery. These relate closely with the individual outcomes and quality of service layers and make optimal use of the channel layer for their different approaches. This could also be called the delivery strategy layer and it represents core ideas in the strategy. </li></ul><ul><li>The channel layer (4) represents the different ways of interacting with people and exchanging information. It includes the usual set of on-site, on-phone and online channels. It does not specifically include on-paper, though the strategy will need to allow for paper for some time. It also includes an automated back-office channel. This might be considered as a version of on-line, but is mentioned separately as it is not a personal channel – it is organisation to organisation – automatically updating information that changes in one organisation with another that has a legitimate and approved interest in that information. Agencies are venturing into these updates now, eg getting earnings data on a weekly basis from employers. </li></ul>
  21. 21. <ul><li>The Government Business Process Management layer (5) is the core element of the model that connects agencies and channels together and permits interoperability, service continuity and consistency. This layer represents the design and definition of government business processes as well as the technology needed to support their sharing and integration. It does not include the processes or systems themselves. They remain with their responsible agency. This is the layer that should be the key focus of the Business Process Transformation Committee (BPTC). In architecture terms, this is where the business reference model (BRM) sits, though elements of the BRM will reside with agencies. In technology terms it also represents the orchestration layer and services platform for a whole of government service oriented architecture (SOA). </li></ul><ul><li>The agency layer (6) recognises the role and accountabilities of individual agencies in the strategy. Agencies are responsible for specific processes and make these available as services in the process management layer. They also use services provided by other agencies. This is one reason why agencies need to adopt SOA </li></ul><ul><li>The portfolio layer (7) is a sample of the portfolio interests that can served by this strategy and demonstrates how they might fall in across the elements of the strategy. </li></ul>

×