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.

Download/display Word Perfect


Published on

  • Be the first to comment

  • Be the first to like this

Download/display Word Perfect

  1. 1. MSIS Taskforce on Sharing of Software and Methods <ul><ul><li>Report and application of the GSBPM </li></ul></ul>M.H.J. Vucsan ITDG 13-14 oct 2008
  2. 2. Contents <ul><li>The taskforce and its mission </li></ul><ul><li>Recommendations for MSIS </li></ul><ul><li>Recommendations for ESSnet </li></ul><ul><li>The GSBPM and its possible application </li></ul>
  3. 3. MSIS taskforce in context Conference European Statisticians MSIS (Management of Statistical Informations Systems) (UNECE + Eurostat/OECD) Taskforce on Sharing and Colloboration
  4. 4. Taskforce on sharing (and collaboration)‏ <ul><li>Membership </li></ul><ul><ul><li>Canada (Karen Doherty, </li></ul></ul><ul><ul><li>Italy (Carlo Vaccari), </li></ul></ul><ul><ul><li>Netherlands(Marton Vucsan) (chair), </li></ul></ul><ul><ul><li>Norway(Rune Gl ø ersen), </li></ul></ul><ul><ul><li>United Kingdom(Jan Jones), </li></ul></ul><ul><ul><li>Eurostat(Leonhard Maqua, Antonio Consoli), </li></ul></ul><ul><ul><li>OECD (Lars Thygesen), </li></ul></ul><ul><ul><li>UNECE (Steven Vale), </li></ul></ul><ul><ul><li>UNIDO (Valentin Todorov). </li></ul></ul>
  5. 5. Taskforce on sharing (and collaboration)‏ <ul><li>Mandate (short)‏ </li></ul><ul><ul><li>report on the scope and models for sharing statistical software, tools and components between different organizations. This report will also provide the Terms of Reference for an ESSnet to set up collaborative networks </li></ul></ul>
  6. 6. Driving forces behind taskforce <ul><li>Eurostat and integration of statistics </li></ul><ul><li>interoperability is getting to be very important (SOA, ESB etc.) </li></ul><ul><li>Shrinking budgets... </li></ul><ul><li>Open standards and open source are gaining momentum </li></ul>
  7. 7. Inhibitors for sharing (1)‏ <ul><li>Business architecture mismatch </li></ul><ul><ul><li>Explicit or implicit </li></ul></ul><ul><ul><li>Different production logistics </li></ul></ul><ul><li>Information architecture mismatch </li></ul><ul><ul><li>Data/Metadata conflicts </li></ul></ul><ul><ul><li>Process incompatibilities </li></ul></ul><ul><li>Platform mismatch </li></ul><ul><ul><li>vendor lock-in </li></ul></ul><ul><ul><li>SOA versus non SOA </li></ul></ul>
  8. 8. Inhibitors for sharing (2)‏ <ul><li>Information shortage: what is available and who to contact </li></ul><ul><li>FUD: can this product be trusted, will it last for several years, support etc. </li></ul><ul><li>Missing operational aids like contract templates etc. </li></ul><ul><li>Licencing is difficult to understand </li></ul><ul><li>Limited access to colloboration tools for developers </li></ul>
  9. 9. Mission of the taskforce <ul><li>Ensure long lasting attention and care (governance) to all initiatives on sharing and colloboration with respect to IT and architecture between members </li></ul><ul><li>As a first step create high level requirements for an ESSnet on common architecture and sharing of software. </li></ul>
  10. 10. Report of the taskforce <ul><li>Strategic approach </li></ul><ul><ul><li>Use MSIS decision power as part of CES to facilitate sharing with manpower / funding. </li></ul></ul><ul><ul><li>Establishment of MSIS Sharing Advisory Board </li></ul></ul><ul><li>Tactical approach </li></ul><ul><ul><li>Recommendations for an ESSnet to be carried out </li></ul></ul>
  11. 11. Sharing Advisory Board <ul><li>Workhorse of MSIS </li></ul><ul><li>Proposals for maintenance and follow up of the architecture task of ESSnet </li></ul><ul><li>Proposals for maintenance and funding of shared software </li></ul><ul><li>Review and report to MSIS on ongoing activities. </li></ul><ul><li>5 or 6 active members, membership 2 yr </li></ul>
  12. 12. Recommendations for ESSnet <ul><li>Common architecture outlines </li></ul><ul><ul><li>Business/information/technical </li></ul></ul><ul><li>Inventory of existing shared software </li></ul><ul><ul><li>To be used by Sharing Advisory Board </li></ul></ul><ul><li>Tools for cooperation </li></ul><ul><ul><li>Information portal </li></ul></ul><ul><ul><li>Repository </li></ul></ul>
  13. 13. Recommendations for ESSnet <ul><li>Common architecture outlines </li></ul><ul><ul><li>Adaptable to change </li></ul></ul><ul><ul><li>Common integration rules </li></ul></ul><ul><ul><li>Support for Open and Propietary solutions </li></ul></ul><ul><ul><li>Modular itself </li></ul></ul><ul><ul><li>Integration of existing software </li></ul></ul><ul><ul><li>First step to strategic goal of interoperability and easy interchange of solutions </li></ul></ul>
  14. 14. Now what about the GSBPM <ul><li>Adoption will harmonize the terminology and perception of the statistical process </li></ul><ul><li>The modular nature of it will enable support of pluriform implementation </li></ul><ul><li>Create a basis for sharing of methods and software </li></ul><ul><li>Needs to be operationalized into a working Enterprise Architecture </li></ul>
  15. 15. Bridging the gap to IT <ul><ul><ul><li>Translate process view to layered view </li></ul></ul></ul><ul><ul><ul><ul><ul><li>abstraction level driven </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Add layers down to infrastructure </li></ul></ul></ul><ul><ul><ul><ul><ul><li>Here is where implementaion begin to differ </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Ensure strict isolation between layers </li></ul></ul></ul><ul><ul><ul><ul><ul><li>Each layer its own meta? </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Possibly use Open Source methods and tools </li></ul></ul></ul><ul><ul><ul><ul><ul><li>Archimate? ( </li></ul></ul></ul></ul></ul>
  16. 16. Questions