Drupal govdays presentatie_v2
- 1. Drupal as a ServiceinFlanders’ public administrationvincent.sennesael@dar.vlaanderen.bejan.dobbelaere@hb.vlaanderen.be
- 12. Figures560+ websites370 webmasters/publishers1 à 2 websitesA lot of CMS’es
- 14. Roughestimates<oversimplified>560 websites*30.000 euro=16.800.000 euro</oversimplified>http://tiny.cc/miogt
- 17. Drupal as a Servicehttp://www.flickr.com/photos/gaborhojtsy/279354242/
- 21. CasesDrupal as a ServiceJan Dobbelaere HP/Belgacom
- 22. Citizen’s Portal and Contact Center 1700www.vlaanderen.be and 1700 Business NeedSolutionClient (Expected) OutcomeSignificant reduction in operating cost
- 23. Less dependency on one single (commercial) supplier
- 24. Increased flexibility to support new initiatives
- 25. Minimum disruption of operational activities
- 26. Performant and Scalable System (availability 99.9%)
- 27. Go-live : May 2012
- 28. D6 PoC & D7 implementation
- 30. Rethinking and simplifying Information Architecture
- 31. # Integrations (Siebel, Datawarehouse, Electronic Publications, Products & Services catalogue (IPDC), Rights & Subsidies (rechtenverkenner),...)
- 32. Content Migration (Migrate v2)
- 33. Replacement of current CMS system (Fatwire 6.2) to service 2 channels :
- 34. www.vlaanderen.be and m.vlaanderen.be the citizen’s gateway for all information related to the Flemish government
- 35. Contactcenter 1700 : provide the contact center agent with a knowledge management system ChallengesIntegration with flanders.be – one Multilingual Portal (NL,FR,DE, EN)
- 36. Modelling multi-channel in DrupalPublication Database publicaties.vlaanderen.beBusiness NeedSolutionClient (Expected) OutcomeSignificant saving in investment cost
- 37. Increased flexibility to support new initiatives
- 38. Go-live : Nov 2011
- 39. Proof of Concept (in D6)
- 40. Übercart to handle order process (front-office) and order handling (back-office)
- 41. Added some custom modules to support additional features
- 42. Widget and gadget library to support easy integration
- 43. Replacement of out-dated legacy application (Java 1.4 – Struts)
- 44. Back-office : decentralised publication and order management
- 45. Front-office : website where cival servants and citizens can view and/or order publications (free and paid)
- 46. Easy integration with other with other websitesChallengesDecentralised publication and order management
- 47. Promote the usage of online documents
- 48. Integrate into numerous of applications with minimal effortInternationaal Vlaandereniv.vlaanderen.be + sites of Flemish representativesBusiness NeedSolutionClient (Expected) OutcomeSignificant saving in investment cost
- 49. Increased flexibility to support new initiatives
- 50. Maximum reuseof other initiatives
- 51. Go-live : May 2012 and June 2012
- 52. Analysis and study about the new structure
- 53. D7
- 54. Eye for multi-lingual environment
- 55. Offering a framework which allows the user of adding additional features
- 56. Replacement of # out-dated legacy application (iPublish and Fatwire 6.2) with one platform
- 57. Integration of iv.vlaanderen.be and the representative sites
- 58. Integration of www.flanders.be / www.flandre.be / www.flandren.be / www.ontdekvlaanderen.be and www.vlaanderen.be into one portalChallengesOrganisational thinking versus useability
- 59. Diverse target audience to be served through one portal site
- 60. Broad spectrum of stakeholdersIntergov Product and Services Catalogue Joint initiative between local government and regional governmentBusiness NeedSolutionClient (Expected) Outcome1 (open) datasource for all public products and services used by all govenrmentalentitities
- 61. Go-live : 2012
- 64. Integration with producers and consumers
- 65. Central overview of all governemental product- and services, detailed general information and subsidies with a reference to the decentralised source
- 66. Implementation of an intergovernmental product- and services catalogue that can be used
- 67. Single reference point of all governamental services
- 68. To be used by all governemental entities in their communication ChallengesOrganisational thinking versus useability
- 69. Broad spectrum of stakeholders
- 70. Gathering of very decentralised informationCulture, Youth, Sports and Mediawww.cjsm.vlaanderen.be - 17 different websitesBusiness NeedSolutionClient (Expected) OutcomeIncreased coherence and homogeneity of the different websites
- 71. Cost efficient
- 72. Better support and maintenance model to support new initiatives
- 73. Maximum integration with other initiatives
- 74. Go-live : (platform ready + one site implemented) Sept 2011
- 78. Iterative approach (to increase buy-in)
- 79. Drupal 7
- 80. Training of the users
- 81. Delivering one framework ready for future development
- 82. Implementation of one common CMS Platform to replace # systems supporting 17 different websites
- 83. Integration of these 17 different websitesChallengesHeterogenity of the different sites
- 84. ‘Empowerment’ of the authors versus the need for quality controlLitigations Constitutional Court of BelgiumIntranet websiteBusiness NeedSolutionClient (Expected) OutcomeWeb-application with limited funds
- 86. Easy to use backoffice
- 87. Go-live : ASAP - Website ready: in testing phase
- 88. D6
- 89. Maximum use of standard Drupal and modules
- 90. Use of Solr to search on content of electronical documents
- 91. Migratie v.1 to migrate the data
- 92. Opening up information about the Litigations Constitutional Court of Belgium and its cases to civil servants
- 93. Replace legacy system (Java 1.3)
- 94. Migrate the old information to the new oneChallengesIntegration with LDAP
- 95. Helping and steering the client towards a simple and flexible solutionExtranet SitesThe civil servant’s portal – departemental sites - newsportalBusiness NeedSolutionClient (Expected) OutcomeAgile CMS platform with the emphasis on distribution of news and ‘social’ interaction and collaboration between civil servants
- 96. Improved alignment between different stakeholders
- 98. Go-live : study ready July 2011 – implementation in 2012
- 99. Proof of Concept (D7) to demonstrate :
- 100. Single Sign On
- 101. Content Migration
- 102. Personalisation
- 103. Content Sharing
- 105. Wireframes
- 106. Defintion phase 2 (semweb)
- 107. Building the business case
- 108. Buy in from all stakeholders
- 109. Generic / specific information
- 110. Governance structure
- 111. Architectural setup
- 112. New cost structure
- 113. Replacement of legacy CMS system (iPublish - 2006)
- 114. Creation of an agile CMS platform
- 115. Introducing collaboration and civil servant’s interactionChallenges
- 116. Drupal as a ServiceWork in ProgressThe team's vision on what to achieve period 2011 - 2013Strategic Choices and Initiatives
- 117. Sharing Experiences and Best Practices
- 118. Implementation and/or supporting entitities with their implementation
- 119. Keep systems running - continuously improve – help desk – training DaaSDurpal as a ServiceStrategic Board
- 120. Drupal Vo Community
- 122. Drupal Operations OfficeSaaSSoftware as a Service“Ready for useage”~ Drupal GardensFlexibility to some extendDrupal environment – preinstalled and preconfigured – access to GIT / Search / ...Quick start but with flexibility to extend / enhancePaaSPlatform as a ServiceSelection of Infrastructure Building Blocks Maximum flexibility with no worries about hardware, servers, storage, networkIaaSInfrastructure as a Service
- 123. Roadmap for DaaSOngoing Projects...PublicationDatabaseFlandersVlaanderen.beExtranetalternative for iPublishBusiness caseDrupal as a ServiceDetailed and operational processes to cover all services needed.Encompasses :- Hosting
- 124. - Development
- 125. - Support
- 126. - Training Services
- 127. - Drupal Operations
- 129. - Service CatalogueDrupal Platform – version 1.0DaaSoperatioalSept 2011Assessment of needs based on current and future projectsAsses reusable and generic componentsDefine # disttributionsJanuari 2013
- 130. Drupal as a ServiceThe challenges ahead of us
- 131. our
Editor's Notes
- #10: 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