1. Transformational Government Framework John Borras Chair OASIS TGF Technical Committee

2. OASIS Overview  OASIS is a member consortium dedicated to building e-business systems’ interoperability specifications  Main focus is on applications of structured information standards (eg XML, SGML) but increasing focus on adoption of standards  Members of OASIS are providers, users and specialists of standards-based technologies  Include organisations, individuals, industry groups and governments  More than 600 member organisations, 5000+ individuals in 80 countries  Global, Not-for-profit, Open, Independent  Successful through industry and government wide collaboration  MOUs and Liaison Agreements with all major standardisation bodies, eg ISO, UN/CEFACT, CEN, W3C, etc.

3. What is Transformational Government? The definition of Transformational Government used within our TC is as follows: ”A managed process of ICT-enabled change in the public sector, which puts the needs of citizens and businesses at the heart of that process and which achieves significant and transformational impacts on the efficiency and effectiveness of government.”

4. e-Government – the lack of success No critical mass of users Wasted resources Duplicated IT expenditure Little impact on core public policy objectives ?

5. Costs / benefits of public sector IT Computerisation: databases and back office automation Computerisation: databases and back office automation eGov 1.0: Online Service Delivery eGov 1.0: Online Service Delivery eGov 2.0: Transformational Government eGov 2.0: Transformational Government Benefit realisation Fragmented Interoperable Integrated Citizen-focused Citizen-enabled Transformation Automation PCMainframeInternetCloud Enablers of change “Governments are shifting from a government-centric paradigm to a citizen- centric paradigm” Rethinking e-government services: user-centric approaches, OECD, 2009

6. Some features of this shift E-Government Transformational Government  Government-centric  Citizen-centric  Supply push  Demand pull  Government as sole provider of citizen services  Government also as convener of multiple competitive sources of citizen services  Unconnected vertical business silos  New virtual business layer, built around citizen needs, operates horizontally across government  “Identity” is owned and managed by government  “Identity” is owned and managed by the citizen  Public data locked away within government  Public data available freely for reuse by all  Citizen as recipient or consumer of services  Citizen as owner and co-creator of services  Online services  IT as capital investment  Multi-channel service integration  IT as a service  Producer-led  Brand-led Bolting technology onto the existing business model of government Focusing first on the business changes needed to unlock benefits for citizens, and only then on the technology

7. Key features which led to the OASIS TC  Builds on the experience of eGov practitioners over the last 10 years  Need for a Citizen-focused and business driven approach  Demonstrably leads to significant levels of citizen take-up  Has been shown to work in many different types of government:  National, state and city level  Deployed in Western Europe, Eastern Europe, Middle East, Far East and Australia  Will be standardised so it can be delivered by many partners and embedded in support tools

8. Target Audiences 1.Primarily intended to meet the needs of: n Ministers and senior officials responsible for shaping public sector reform and e-Government strategies and policies (at national, state/regional and city/local levels); n Senior executives in industry who wish to partner with and assist governments in the transformation of public services. 2.Secondary audiences : n Leaders of international organisations working to improve public sector delivery, whether at a global level (eg World Bank, United Nations) or a regional one (eg European Commission, Eris@); n Academic and other researchers working in the field of public sector reform; n Civil society institutions engaged in debate on how technology can better enable service transformation.

9. The TGF Primer

10. The TGF Pattern Language  Sets out the formal elements of the TGF  The normative references that will become the OASIS standard

11. What is a ‘Pattern Language’  A process for analysing recurrent problems  A mechanism for capturing those problems and archetypal solutions  A Pattern Language is readable and engaging whilst providing ‘hooks’ for further machine processing  It is not an ‘out-of-the-box’ solution but rather should be a rational collection of familiar patterns with which a team can work.  The pattern language provides a vocabulary, grammar, structure and plot – but each project has to write its own story…

12. Fit for Purpose for TGF ?  Pattern Language fits structure of TGF  Not too formal, prose based  Common repeatable structure  Allows cross-referencing and basic hierarchy of TGF parts  Easy to use  Transposing existing TGF Primer was relatively painless  Novel  Gives us all something to talk about in presentations  Proven  Pattern Language idea has already been transposed in IT-related areas (design patterns, requirements patterns)  Easy to grasp  Easier to explain that UML, RDF, etc (especially for managers)

13. Way Forward  OASIS TGF Technical Committee monthly meetings, developing further TGF products, see TC website  Version 1 of the Primer and Pattern Language published for 30 day Public Review, see TC website  References:  TC Website www.oasis-open.org/committees/tc_home.php?wg_abbrev=tgf  LinkedIn Group http://www.linkedin.com/groups?mostPopular=&gid=3677772  Introducing Pattern Languages www.PeterFBrown.com/Pages/PatternLanguages.aspx  Contact: johnaborras@yahoo.co.uk (TC Chair)johnaborras@yahoo.co.uk