INSPIRE Spatial Data Infrastructure Solution Architecture Basic Solution Profile

Transcription

1 INSPIRE Spatial Data Infrastructure Solution Architecture Basic Solution Profile Gate 1 Date: 06/09/2013 Version: 2.0 Security Classification: Malta Infor mation Technology Agency

2 01. Submission Details Project Name Target Completion Date INSPIRE Spatial Data Infrastructure t yet established. Submission Name and Surname Ministry / Department / Organisation Title (CTO / CIO / Officer / IMU / Supplier) Jennifer Busuttil TSG - MITA Solutions Architect jennifer.busuttil@gov.mt Telephone Supplier Name and Surname Organisation Godwin Caruana CTO - TSG - MITA Godwin.V.Caruana@gov.mt Telephone Client Name and Surname Ministry / Department / Organisation Gatt Matthew Head of EU Fund Prog & Digital Outreach - MITA matthew.j.gatt@gov.mt Telephone Solution Architecture Document Template Version: 7.0 Page 2

3 02. Basic Solution Profile Change Log Any moderate or significant changes to the solution design must be resubmitted to TSG for review and approval prior to making any actual implementation change(s). In most cases, the review and approval of any changes would be performed internally within TSG. tes: Use of a word proce ssing automated change tracking feature is required when resubmitting this document in order to simplify the review and approval process. Once a version of the document has been approved, then that version of the document should be saved for archival purposes. Prior to submitting a new version of the document, all prior tracked changes should be accepted. This process for resubmission can then be repeated as many times as necessary until the final approval has been issued. Failure to resubmit change s for review and approval could result in a recommendation by TSG that the project approval status be reconsidered. If there are any questions a s to whether or not a change is substantive enough to warrant review and approval, please send an on eau.mita@gov.mt for clarification. Maintain a summary of changes in the table below. 2.1 Change Log Summary Description Version Date Initial version /10/2012 Revision of the initial version to update any changes made to the technology stack /09/2013 Solution Architecture Document Template Version: 7.0 Page 3

4 03. Basic Solution Profile The Basic Solution Profile Section has been designed to capture only the most essential information required for the Initial Project Approval High Level Business Scope of Solution Busine ss Context Checklist Business Description: A European Spatial Data Infrastructure will assist in policy-making across boundaries which may have an impact on the environment. Therefore the spatial information considered under the directive is extensive and includes a great variety of topical and technical themes. The purpose of this project is to abide with the INSPIRE directive which came into force on 15 May 2007 and will be implemented in various stages, with full implementation required by INSPIRE is based on the infrastructures for spatial information established and operated by the 27 Member States of the European Union. The Directive addresses 34 spatial data themes needed for environmental applications, with key components specified through technical implementing rules. This will enable the sharing of environmental spatial information among public sector organisations and better facilitate public access to spatial information across Europe. INSPIRE should be based on the infrastructures for spatial information that are created by the Member States. The components of those infrastructures include: metadata, spatial data themes (as described in Annexes I, II, III of the Directive), spatial data services, network services and technologies, agreements on sharing, access and use, coordination, monitoring mechanisms, processes and procedures. The text of the INSPIRE Directive is available from the INSPIRE web site ( INSPIRE is based on a number of common principles: Data should be collected only once and kept where it can be maintained most effectively. It should be possible to combine seamless spatial information from different sources across Europe and share it with many users and applications. It should be possible for information collected at one level/scale to be shared with all levels/scales; detailed for thorough investigations, general for strategic purposes. Geographic information needed for good governance at all levels should be readily and transparently available. Easy to find what geographic information is available, how it can be used to meet a particular need, and under which conditions it can be acquired and used. Solution Architecture Document Template Version: 7.0 Page 4

5 3.1.2 EU Initiative/Obligations: Is the creation of the solution mandated by EU laws/directives/initiatives? o Which EU laws/directives/initiatives mandate the creation of the solution? Directive 2007/2/EC of the European Parliament Mission Criticality (in the context of Government s business): Is the creation of the solution mandated by local laws/directives? o Which local laws/directives mandate the creation of the solution? Given that the implementation is enforced via an EU Directive, it is automatically enforced via the local transposition. What are the repercussions of not implementing the solution? Failure to fulfil the obligations under that directive the Government is to pay penalties. Example: Penalties, disruption to Government s ICT/Business strategy. Clearly provide the necessary documentation to substantiate your case. By when does the solution need to be live / available for use? The current work focuses on the initial operating capability for discovery, view and download services. The INSPIRE Directive stipulates the following timeline: 09-v Jun Jun v Dec Dec-2012 Discovery and view services operational Member States shall provide the Download Services with initial operating capability Member States shall provide the Transformation Services with initial operating capability Implementation of Commission Regulation (EU) 1089/2010 of 23 vember 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services for Newly collected and extensively restructured Annex I spatial data sets available Download services operational Transformation services operational Provide reason why the solution is required to be live / available for use by this date: Deadlines are stipulated by the EU Directive 2007/2/EC and regulations resulting from the commitology process Monetary Value/Budget Allocated: NOTE: If breakdown of the below values is available, kindly attach with the submission. Capital Expenditure (CAPEX): Such as: procurement, deployment, etc. Operational Expenditure (OPEX): Such as: maintenance and support, recurring license costs, etc. Solution Architecture Document Template Version: 7.0 Page 5

6 o Specify the number of years on which OPEX was calculated: Kindly also highlight the budget sources funding the solution: MITA has been assigned the legal obligation to provide this infrastructure and will resource this from its own funds. N.B. Budget sources can also be referred to a pre-defined contract. In this case kindly highlight the number of hours being utilised Solution Scope: International: Inter-governmental: Solution which will be shared or is common amongst governments; implemented across EU member states. Government Wide: Interdepartmental: Solution which will be shared or is common amongst local Government departments. Local: Departmental: Solution which will be only used by the specific Government department Solution Delivery: Solution is to be delivered all at once: Solution is to be delivered over time:. There are three different Annexes which include different spatial data themes that need to be implemented. Details on the phases still have to be defined Solution Major Milestones: Specify the solution major milestones together with their respective target delivery date within the table below: The INSPIRE Directive stipulates the following timeline: 09-v Jun Jun v Dec Dec-2012 Discovery and view services operational Member States shall provide the Download Services with initial operating capability Member States shall provide the Transformation Services with initial operating capability Implementation of Commission Regulation (EU) 1089/2010 of 23 vember 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services for Newly collected and extensively restructured Annex I spatial data sets available Download services operational Transformation services operational Solution Architecture Document Template Version: 7.0 Page 6

7 03.2 Basic Solution Checklist Disclaimer: Any technologies listed below have been provided solely for convenience, the information provided is not intended to be exhaustive nor does it indicate product endorsement by TSG Project Type: New Solution: Upgrade Solution: Solution Migration: Either migration of solution from one hosting environment to another OR migration of server from one data centre to another Solution Interactions: Government to Citizen (G2C): Services offered to the public. Government to Business (G2B): Services offered to the third party organizations which are not controlled by the Government. Government to Government (G2G): Services intended to be used by ministries, Government departments and/or entities. Government to Other Government (G2OG): Services that will be used by other Governments, such as other EU member states. Solution Architecture Document Template Version: 7.0 Page 7

8 3.2.3 Business Domain Information Classification: What is the classification of the information which will be retained by the solution: The solution can have more than one applicable classification. Confidential Significant impact if information is disclosed to unauthorised recipients. In this regard the following is recommended: Data should be encrypted at rest, All point-to-point communication channels should be encrypted, 2-factor Authentication should be used, Should not be published publicly over the internet, Preferably hosted on infrastructures which are governed by ISO (or similar) certifications Restricted Undesirable consequences if information is disclosed to unauthorized recipients In this regard the following is recommended: If data is stored on shared tenancy storage then it should be encrypted at rest, Outside MAGNET communication should be encrypted. Negligible impact if information is disclosed to unauthorised recipients. Public This information is available to the general public. Security Classification Select Indicate which information is classified under the respective category including the respective key business scenarios / Insert Confidential Restricted Public Data is public subject to appropriate license restrictions on download and reuse as stipulated by the respective data owner. Is the solution going to process / store personal information? Example: use of credit card details during a payment process, processing/storing of health related information, etc. Solution Architecture Document Template Version: 7.0 Page 8

9 3.2.4 ICT Policies/Directives: Highlight any deviations (providing detailed description) to the Policies /Directives found in the following URL: Part of the technology being used to provide the spatial infrastructure consists of two open source portals which do not fully abide with the branding obligations as defined in CIMU S0051 Website Standard. Furthermore the stack uses spatial data standards which are not listed in the Adopted Specifications Policy. Such as: GMICT X 0071:2010 Adopted Specifications, CIMU S0051 Website Standard, CIMU P 0012:2003 Third party Web hosting services Policy Estimated Total Number of Consumers that will be using the solution: Total number of consumers: By Audience: Total Number Citizen Government Employees Businesses (Private Sector) Other: 1. Data owners will need to provide the metadata pertaining to a specific data theme and enter the respective data through the portal. Data Owners involve different government and public entities Member States of the European Union. 3. Given that this setup will be public facing it shall be accessible by the general public t defined NOTE: For solutions were functionality will be delivered overtime specify amounts by implementation phase. Solution Architecture Document Template Version: 7.0 Page 9

10 3.2.6 Estimated Total Number of Concurrent Consumers that will be making use of the solution: Total number of concurrent consumers: By Audience: Total Number Citizen Government Employees Businesses (Private Sector) Other: The number of requests processed in parallel for the view, download and discovery services is limited to 50. While the minimum number of simultaneous requests to a transformation service to be served in accordance with the quality of service performance criteria shall be 5 requests per second. (Source: UriServ/ LexUriServ.do?uri=CELEX: 32010R10 88:EN:NOT) t defined NOTE: For solutions were functionality will be delivered over time specify amounts by implementation phase Estimated Annual Consumer Growth Rate: Percentage consumer growth rate: By Audience: Percentage Citizen t defined Government Employees Businesses (Private Sector) Other: NOTE: For modular delivery specify amounts by implementation phase. Solution Architecture Document Template Version: 7.0 Page 10

11 3.2.8 Solution Availability: Specify the required uptime for the solution: Availability % Unscheduled Downtime (Over a non leap Year) / 99% (Two Nines) 3.65 Days 99.9% (Three Nines) 8.76 Hours 99.99% (Four Nines) Minutes % (Five Nines) 5.26 Minutes Specify other (if any) Specify other (if any) NOTES: - The specified downtime is the exact yearly period whereby the solution is allowed to be unavailable based on the respective availability percentage. - Any solution being hosted within Government s data centres requiring an availability of 99.9% or more per annum should be implemented in a redundant fashion across both data centres. - Please indicate how the SLA shall be monitored. You may make use of the following Service Availability Calculator for a quick calculation in terms of un-scheduled downtime and guaranteed uptime. In addition, this tool features actual availability representation when introducing scheduled downtime. TEC-TPL-Service Availability Calculator-v1.0.xls Recovery Time Objectives (RTO): What is the maximum acceptable length of time from the occurrence of a downtime, that may elapse before the lack of business functionality severely impacts its beneficiary/beneficiaries: Such information is not being defined. MTBF (Mean Time Between Failure): What is the minimum acceptable length of time between two consecutive failures, that is acceptable to the business? Such information is not being defined. IMPORTANT: When compiling the Service Level Agreement (SLA) for solutions, It is recommended that the above values are clearly identified, i.e.: (a) Availability, (b) Recovery time objectives and (c) MTBF. By having these specified and articulated in the service contract, the business owner may ensure minimal impact from possible failures. For example: 99% availability with a maximum RTO of five hours and having an MTBF of 2 days. What are the repercussions if the solution fails? Consumers will not be able to view, download, or discover spatial data. For example the above must gauge whether the solution has financial, health, political, etc. repercussions. Highlight any peaks and troughs of the service being rendered? The performance in normal situation represents periods out of peak load. It is set at 90 % of the time. Solution Architecture Document Template Version: 7.0 Page 11

12 3.2.9 Production Hours of Operation: Audience Citizen 24 X 7 rmal Business Hours Extended Business Hours (e.g. 8:00 to 17:00) / / Specify the hours / Government Employees Businesses (Private Sector) EU Member State Users Solution Delivery Model/Business Model: Traditional: As a Service: Subscription based. NOTE: Prior to considering cloud based offerings it is appropriate that the following considerations are evaluated: Please refer to Cloud Considerations check list: Considerations-v2%200.pdf. Solution Architecture Document Template Version: 7.0 Page 12

13 Target Hosting Environment: Shared egovernment Web Hosting Environment managed and supported by MITA: This applies for existing solutions only i.e. solution updates/upgrades. Segregated Environment at the Government Data Centres managed by MITA: This applies for existing solutions only i.e. solution updates/upgrades. Service Hosting Catalogue TYPE 2 - refer to service hosting catalogue: Segregated Environment at the Government Data Centres managed by 3 rd parties: o o o Computing resources provided by MITA: Service Hosting Catalogue TYPE 1B - refer to service hosting catalogue: Computing resources not provided by MITA: Service Hosting Catalogue TYPE 1A - refer to service hosting catalogue: 3rd Party Supplier Organization: NOTE: This is subject to approval i.e. involving business negotiations and appropriate discussions with the respective stakeholders. Hosting managed and supported at 3 rd parties: Shared: Dedicated: The organization providing: o Hosting: o Management and support: The country: o Where the data shall be residing: o From where the service shall be rendered: NOTE: All options above are governed by OPM Circular 29/ June Reviewing the ICT Operations of Government. NOTE: If more than one hosting mode is selected please supply more information about the role of each hosting layer. Solution Architecture Document Template Version: 7.0 Page 13

14 Solution Usage of Government Shared Services: mybills: Shared Service handling online government payments. myforms: Shared Service for creating electronic forms and the respective workflows for the delivery of citizen centric eservices. mgov: Shared alerting services used to deliver Short Message Services (SMS) and notifications. eid: A shared service which allows citizens and businesses to identify themselves via the government s Web portal or telephone contact centre to securely access any number of available e-services, regardless of which organization provides the service. CDR: Shared Service providing access to Corporate Data. Corporate Identity: A Shared Service for the provision of Identity to the Public Administration. Additional information can be found at the following URL: Kindly highlight any usage peaks of the service/s being consumed Solution Usage of External Services: Identify and specify any interactions required with external services: Service Name Service Provider NOTE: For Gate 2 approval the respective service contract that includes the respective service consumption mechanism must be included. (Service Contract Template Appendix A). Solution Architecture Document Template Version: 7.0 Page 14

15 Shareable characteristics of the Solution: Is the solution going to share resources (data, processes, etc.) with other external services/solutions? o What resources will be shareable? o Which external services/solutions are going or already make use of these sharable resources (if already known)? Service Name Service Provider o How do you plan to share these resources (if already known)? Principles: - Any shareable resources should be exposed through appropriate machine readable mechanisms in an industry standard fashion, using open standards and interoperable engineering principle/practices. - Specifically in the context of domain data, ownership is considered to rest within the respective legally empowered authority/authorities, unless explicitly otherwise indicated. As a matter of preference, any machine to machine (solution to solution) interaction between data consumers and providers must happen directly between the consumer and the specific information system storing and processing such domain data Solution Architecture Document Template Version: 7.0 Page 15

16 03.3 Functional Solution Description The Spatial Infrastructure solution will provide the following functionality; a) Discovery services search for spatial data sets and spatial data services on the basis of the content of corresponding metadata, and display the metadata content; b) View services as a minimum, display, navigate, zoom in/out, pan, or overlay spatial data sets and display legend information and any relevant content of metadata; c) Download services enabling copies of complete spatial data sets, or of parts of such sets, to be downloaded The INSPIRE View Services allow users and computer programs to view spatial datasets; 1. Get View Services Metadata: Get metadata about a specific view service; 2. Get Map: Returns a map for a specified area; 3. Link View Service: Allows the linking of view services together. (Source: eu/documents/network_servic es/tec hnicalguidance_viewservices_v3.1.p df) The INSPIRE Discovery Services allow users and computer programs to search for spatial datasets and services based on their metadata records; 1. Get Discovery Service Metadata: Provides all necessary information about the Discovery Service and describes service capabilities; 2. Discover Metadata: Allows requesting INSPIRE metadata elements of spatial data sets and services from a Discovery Service; 3. Publish Metadata: Allows editing of INSPIRE metadata elements of resources in the Discovery Service (push or pull metadata mechanisms). Editing meaning insert, update and delete; 4. Link Discovery Service: Allows the declaration of the availability of a Discovery Service for the discovery of resources through the Member State Discovery Service while maintaining the resource metadata at the owner s location. (Source: eu/documents/network_servic es/tec hnicalguidance_discoveryservic es_v 3.1.pdf) The INSPIRE Download Services describes the following four download operations that must be implemented; 1. Get Download Service Metadata 2. Get Spatial Dataset 3. Describe Spatial Dataset 4. Link Download Service (Source: eu/documents/network_servic es/tec hnical_guidanc e_download_service s_3.0.pdf) te: Narrative describing the functional design of the solution must be provided immediately following the diagram(s). Solution Architecture Document Template Version: 7.0 Page 16

17 03.4 Conceptual Solution Design Description Provide a diagram (or diagrams) with corresponding narrative that depicts an accurate description of the conceptual design for the entire solution. The design must document how each of the requirements specified in the functional design will be conceptually ac complished. The conceptual design must align with the Principles, Practices, and Standards that are published in the and portals respectively. te: The diagram below has been provided for illustrative purpose s only. PSOs should delete the diagram provided and supply information specific to the solution requesting approval. INTERNET Firewall / Reverse Proxy GOVERNMENT DATACENTERS Open GIS Stack MT SANDBOXED ENVIRONMENT te: Narrative describing the conceptual design of the solution must be provided immediately following the diagram(s). Solution Architecture Document Template Version: 7.0 Page 17