Drupal govdays presentatie_v2

1,025 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,025
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Time:1Budget:1 Ownership:1Financing Model:1 Operating Model:1Vo-theme:1Vo-modules:1Governance:1Community:1Contribute:1Strategic Choices:1Drupal or not Drupal:1Effectiveness:1Deployment:1Awareness:1Scalability:1Performance:1Migration:1http://www.wordle.net/compose
  • Drupal govdays presentatie_v2

    1. 1. Drupal as a Service<br />in<br />Flanders’ public administration<br />vincent.sennesael@dar.vlaanderen.be<br />jan.dobbelaere@hb.vlaanderen.be<br />
    2. 2. Communications Departement<br />
    3. 3. Kris Peeters<br />Minister-President<br />public communications<br />
    4. 4.
    5. 5.
    6. 6. Geert Bourgeois<br />ViceMinister-President<br />ict & e-gov<br />
    7. 7. Geert Bourgeois<br />ViceMinister-President<br />ict & e-gov<br />
    8. 8.
    9. 9.
    10. 10. vlaanderen.be<br />Launched in 1996<br />
    11. 11.
    12. 12. Figures<br />560+ websites<br />370 webmasters/publishers<br />1 à 2 websites<br />A lot of CMS’es<br />
    13. 13. http://tiny.cc/miogt<br />
    14. 14. Roughestimates<br /><oversimplified><br />560 websites<br />*<br />30.000 euro<br />=<br />16.800.000 euro<br /></oversimplified><br />http://tiny.cc/miogt<br />
    15. 15. Capability Maturity Model<br />
    16. 16.
    17. 17. Drupal as a Service<br />http://www.flickr.com/photos/gaborhojtsy/279354242/<br />
    18. 18. Drupalhostingarchitecture<br />
    19. 19.
    20. 20. Service<br />Operations<br />Strategy<br />
    21. 21. Cases<br />Drupal as a Service<br />Jan Dobbelaere HP/Belgacom<br />
    22. 22. Citizen’s Portal and Contact Center 1700<br />www.vlaanderen.be and 1700 <br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Significant reduction in operating cost
    23. 23. Less dependency on one single (commercial) supplier
    24. 24. Increased flexibility to support new initiatives
    25. 25. Minimum disruption of operational activities
    26. 26. Performant and Scalable System (availability 99.9%)
    27. 27. Go-live : May 2012
    28. 28. D6 PoC & D7 implementation
    29. 29. Useability Asessment
    30. 30. Rethinking and simplifying Information Architecture
    31. 31. # Integrations (Siebel, Datawarehouse, Electronic Publications, Products & Services catalogue (IPDC), Rights & Subsidies (rechtenverkenner),...)
    32. 32. Content Migration (Migrate v2)
    33. 33. Replacement of current CMS system (Fatwire 6.2) to service 2 channels :
    34. 34. www.vlaanderen.be and m.vlaanderen.be the citizen’s gateway for all information related to the Flemish government
    35. 35. Contactcenter 1700 : provide the contact center agent with a knowledge management system </li></ul>Challenges<br /><ul><li>Integration with flanders.be – one Multilingual Portal (NL,FR,DE, EN)
    36. 36. Modelling multi-channel in Drupal</li></li></ul><li>Publication Database <br />publicaties.vlaanderen.be<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Significant saving in investment cost
    37. 37. Increased flexibility to support new initiatives
    38. 38. Go-live : Nov 2011
    39. 39. Proof of Concept (in D6)
    40. 40. Übercart to handle order process (front-office) and order handling (back-office)
    41. 41. Added some custom modules to support additional features
    42. 42. Widget and gadget library to support easy integration
    43. 43. Replacement of out-dated legacy application (Java 1.4 – Struts)
    44. 44. Back-office : decentralised publication and order management
    45. 45. Front-office : website where cival servants and citizens can view and/or order publications (free and paid)
    46. 46. Easy integration with other with other websites</li></ul>Challenges<br /><ul><li>Decentralised publication and order management
    47. 47. Promote the usage of online documents
    48. 48. Integrate into numerous of applications with minimal effort</li></li></ul><li>Internationaal Vlaanderen<br />iv.vlaanderen.be + sites of Flemish representatives<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Significant saving in investment cost
    49. 49. Increased flexibility to support new initiatives
    50. 50. Maximum reuseof other initiatives
    51. 51. Go-live : May 2012 and June 2012
    52. 52. Analysis and study about the new structure
    53. 53. D7
    54. 54. Eye for multi-lingual environment
    55. 55. Offering a framework which allows the user of adding additional features
    56. 56. Replacement of # out-dated legacy application (iPublish and Fatwire 6.2) with one platform
    57. 57. Integration of iv.vlaanderen.be and the representative sites
    58. 58. Integration of www.flanders.be / www.flandre.be / www.flandren.be / www.ontdekvlaanderen.be and www.vlaanderen.be into one portal</li></ul>Challenges<br /><ul><li>Organisational thinking versus useability
    59. 59. Diverse target audience to be served through one portal site
    60. 60. Broad spectrum of stakeholders</li></li></ul><li>Intergov Product and Services Catalogue <br />Joint initiative between local government and regional government<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>1 (open) datasource for all public products and services used by all govenrmentalentitities
    61. 61. Go-live : 2012
    62. 62. Study, Study, ...
    63. 63. Information Analysis
    64. 64. Integration with producers and consumers
    65. 65. Central overview of all governemental product- and services, detailed general information and subsidies with a reference to the decentralised source
    66. 66. Implementation of an intergovernmental product- and services catalogue that can be used
    67. 67. Single reference point of all governamental services
    68. 68. To be used by all governemental entities in their communication </li></ul>Challenges<br /><ul><li>Organisational thinking versus useability
    69. 69. Broad spectrum of stakeholders
    70. 70. Gathering of very decentralised information</li></li></ul><li>Culture, Youth, Sports and Media<br />www.cjsm.vlaanderen.be - 17 different websites<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Increased coherence and homogeneity of the different websites
    71. 71. Cost efficient
    72. 72. Better support and maintenance model to support new initiatives
    73. 73. Maximum integration with other initiatives
    74. 74. Go-live : (platform ready + one site implemented) Sept 2011
    75. 75. Business needs gathering
    76. 76. Site structure rethinking
    77. 77. Useability assessment
    78. 78. Iterative approach (to increase buy-in)
    79. 79. Drupal 7
    80. 80. Training of the users
    81. 81. Delivering one framework ready for future development
    82. 82. Implementation of one common CMS Platform to replace # systems supporting 17 different websites
    83. 83. Integration of these 17 different websites</li></ul>Challenges<br /><ul><li>Heterogenity of the different sites
    84. 84. ‘Empowerment’ of the authors versus the need for quality control</li></li></ul><li>Litigations Constitutional Court of Belgium<br />Intranet website<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Web-application with limited funds
    85. 85. Flexible solution
    86. 86. Easy to use backoffice
    87. 87. Go-live : ASAP - Website ready: in testing phase
    88. 88. D6
    89. 89. Maximum use of standard Drupal and modules
    90. 90. Use of Solr to search on content of electronical documents
    91. 91. Migratie v.1 to migrate the data
    92. 92. Opening up information about the Litigations Constitutional Court of Belgium and its cases to civil servants
    93. 93. Replace legacy system (Java 1.3)
    94. 94. Migrate the old information to the new one</li></ul>Challenges<br /><ul><li>Integration with LDAP
    95. 95. Helping and steering the client towards a simple and flexible solution</li></li></ul><li>Extranet Sites<br />The civil servant’s portal – departemental sites - newsportal<br />Business Need<br />Solution<br />Client (Expected) Outcome<br /><ul><li>Agile CMS platform with the emphasis on distribution of news and ‘social’ interaction and collaboration between civil servants
    96. 96. Improved alignment between different stakeholders
    97. 97. Maximised content sharing
    98. 98. Go-live : study ready July 2011 – implementation in 2012
    99. 99. Proof of Concept (D7) to demonstrate :
    100. 100. Single Sign On
    101. 101. Content Migration
    102. 102. Personalisation
    103. 103. Content Sharing
    104. 104. Business requirements gathering
    105. 105. Wireframes
    106. 106. Defintion phase 2 (semweb)
    107. 107. Building the business case
    108. 108. Buy in from all stakeholders
    109. 109. Generic / specific information
    110. 110. Governance structure
    111. 111. Architectural setup
    112. 112. New cost structure
    113. 113. Replacement of legacy CMS system (iPublish - 2006)
    114. 114. Creation of an agile CMS platform
    115. 115. Introducing collaboration and civil servant’s interaction</li></ul>Challenges<br />
    116. 116. Drupal as a Service<br />Work in Progress<br />The team's vision on what to achieve period 2011 - 2013<br /><ul><li>Strategic Choices and Initiatives
    117. 117. Sharing Experiences and Best Practices
    118. 118. Implementation and/or supporting entitities with their implementation
    119. 119. Keep systems running - continuously improve – help desk – training </li></ul>DaaS<br />Durpal as a Service<br /><ul><li>Strategic Board
    120. 120. Drupal Vo Community
    121. 121. Drupal Project Office
    122. 122. Drupal Operations Office</li></ul>SaaSSoftware as a Service<br />“Ready for useage”~ Drupal Gardens<br />Flexibility to some extend<br />Drupal environment – preinstalled and preconfigured – access to GIT / Search / ...<br />Quick start but with flexibility to extend / enhance<br />PaaS<br />Platform as a Service<br />Selection of Infrastructure Building Blocks <br />Maximum flexibility with no worries about hardware, servers, storage, network<br />IaaS<br />Infrastructure as a Service<br />
    123. 123. Roadmap for DaaS<br />Ongoing Projects<br />...<br />Publication<br />Database<br />Flanders<br />Vlaanderen.be<br />Extranetalternative for iPublish<br />Business case<br />Drupal as a Service<br />Detailed and operational processes to cover all services needed.<br />Encompasses :<br /><ul><li>- Hosting
    124. 124. - Development
    125. 125. - Support
    126. 126. - Training Services
    127. 127. - Drupal Operations
    128. 128. - Governance Structure
    129. 129. - Service Catalogue</li></ul>Drupal Platform – version 1.0<br />DaaSoperatioal<br />Sept 2011<br />Assessment of needs based on current and future projects<br />Asses reusable and generic components<br />Define # disttributions<br />Januari 2013<br />
    130. 130. Drupal as a Service<br />The challenges ahead of us<br />
    131. 131. our<br />

    ×