View OS by emapsite
View OS is a hosted map and search service for OS data in the Public Sector/One Scotland Mapping Agreements (PSMA/OSMA) including OS MasterMap Topography Layer and all AddressBase flavours. Data-as-a-Service (DaaS) for digital mapping, View OS supports deployment to multiple platforms, OGC standards (WMS/WMTS/WFS) and GIS and web mapping APIs.
- Ordnance Survey digital licensed mapping and address data
- Web Map Services (WMS) for OS data
- Web Map Tile Services (WMTS) for OS data
- Multiple projections including MasterMap for Google
- Web Feature Services (WFS) for OS data
- Address level gazetteer search
- Includes OS Open Data
- Backed by Service Level Agreement
- ISO9001/27001 certified
- Customisable and extensible - see View Custom service
- Ideal for PSMA and OSMA members
- Ideal for OS Open Data access
- Enterprise level performance and scalability assured
- Integrate web mapping into non-GI/mapping applications
- Eliminates need for local hosting
- Integrate digital mapping into multiple applications
- Supports feature level interrogation
- Configurable search options - address, street, postcode
- Fully scalable to support seasonal demands such as SPS/CAP
£125 per unit per month
- Education pricing available
- Free trial available
- Pricing document
- Skills Framework for the Information Age rate card
- Service definition document
- Terms and conditions
- Modern Slavery statement
|Software add-on or extension||No|
|Cloud deployment model||Public cloud|
View OS is limited to Ordnance Survey data; the service can be extended and customised under the View Custom by emapsite service.
View OS is available under a tiered subscription model based on actual consumption/usage.
|Email or online ticketing support||Email or online ticketing|
|Support response times||
4 hour response time
ticket number assigned in internal ticketing system from email
|User can manage status and priority of support tickets||No|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Yes, at extra cost|
SLA includes 4 support levels at no additional charge:
Inquiry regarding a routine technical issue; information requested on application capabilities, navigation, installation or configuration; bug affecting a small number of users. Acceptable workaround available; standard support hours
System performance issue or bug affecting some but not all users. Short-term workaround is available, but not scalable; standard support hours
Major functionality is impacted or significant performance degradation is experienced. Issue is persistent and affects many users and/or major functionality. No reasonable workaround available; extended support hours via email and phone messaging alerts inc weekends
Critical production issue affecting all users, including system unavailability and data integrity issues with no workaround available; extended support hours via email and phone messaging alerts 24*7
In addition all customers have a named account manager who will act as a conduit to appropriate technical, integration and cloud support resources.
|Support available to third parties||Yes|
Onboarding and offboarding
1. Every organisation is registered in our database
2. At least one organisation member of staff needs to be registered in our database
3. Every user for every organisation should be registered; each person is given a unique username and password
4. Each user will be required to authenticate themselves with their username and password when accessing the Services for the first time whenever they invoke the service from within their application
5. Any organisation can register additional users at any time
6. Any new PSMA/OSMA signatory will need to be forwarded to emapsite by the appropriate Contract Manager and the above process replicated
|End-of-contract data extraction||
Service migration of specific APIs is limited owing to nature of a model built on highly optimised web service components delivering content from very specific geographic data stacks. The services are highly interoperable and extensible, for example to other data stacks.
User data extraction includes the facility to retrieve all user interaction and user generated data including transaction logs and database schemas as applicable; any such data would typically be provided as CSV or XML.
Subject to audit requirements emapsite will purge and destroy consumer data from any computers, storage media or storage devices at the end of a subscription period.
Indicative time for de-provisioning (to close and off-board any service) is one week (though contractual obligations may have a different term in relation to cancellation of service).
Typically 3 months notice is required unless there is a material and persistent breach of any of the obligations agreed under a Call Off or other Contract under the G-Cloud framework or if a change of control of the Supplier causes conflicts of interest or other competition issues.
There are no additional costs at termination.
Using the service
|Web browser interface||Yes|
|Application to install||No|
|Designed for use on mobile devices||Yes|
|Differences between the mobile and desktop service||No difference|
|What users can and can't do using the API||
The View OS API is not exposed directly to customers but is configured upon request for each PSMA/OSMA member owing to the need to validate PSMA/OSMA membership.
PSMA/OSMA members can select which OS data layers they wish to include in their selected View service and can change that at any time.
|API sandbox or test environment||Yes|
|Description of customisation||
Choice of OS layers can be customised within View OS by emapsite.
Other third party layers can be added to the same API via the View Custom by emapsite service.
|Independence of resources||Like most platforms we rely on over-provisioning for each service in line with the number of users and patterns of usage, spinning up additional resources as necessary for any specific service. In addition owing to typical usage levels we separate the WMS/WFS and the WMTS requests onto discrete hardware. Tile size constraints form part of the service level agreement.|
|Service usage metrics||Yes|
|Metrics types||Overall service usage levels per customer organisation broken down by service type (WMS, WMTS, WFS) and product if required.|
|Reporting types||Regular reports|
|Supplier type||Not a reseller|
|Staff security clearance||Staff screening not performed|
|Government security clearance||Up to Baseline Personnel Security Standard (BPSS)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||United Kingdom|
|User control over data storage and processing locations||No|
|Datacentre security standards||Supplier-defined controls|
|Penetration testing frequency||Less than once a year|
|Penetration testing approach||Another external penetration testing organisation|
|Protecting data at rest||Other|
|Other data at rest protection approach||Secure containers, racks or cages|
|Data sanitisation process||Yes|
|Data sanitisation type||Deleted data can’t be directly accessed|
|Equipment disposal approach||In-house destruction process|
Data importing and exporting
|Data export approach||XML or CSV on request.|
|Data export formats||
|Other data export formats||Xml|
|Data import formats||
|Other data import formats||
|Data protection between buyer and supplier networks||Legacy SSL and TLS (under version 1.2)|
|Data protection within supplier network||Legacy SSL and TLS (under version 1.2)|
Availability and resilience
Internal auditing shows WMS/WMTS/WFS availability at 99.85% on 24*7*365 basis and 99.95% on a working hours basis.
emapsite offers a service credit package upto 10% of the per service delivery period contract value; this is assessed according to details agreed in the customer service level agreement and typically provides for a credit for failure to deliver required services to the agreed availability level for the specified service delivery period.
|Approach to resilience||
To ensure high resilience and security emapsite’s infrastructure is hosted at ISO27001 certified Equinix’s latest Tier 3+ datacentre facility near Heathrow. Access to the data centre is controlled by access cards, visual and biometric identification, CCTV, breach alarms and controlled physical barriers. The data centre has fully redundant power with UPS and diesel generators and is serviced by multiple high speed low latency fibre. Access is secured via customer specific API key with full session and user logging.
- Dual zone, single site facility
- Multiple servers including 16-bay blade servers
- Two switches in each zone
- Duplicated firewalls
- All servers are dual power supply from independent power sources
- Virtualised cloud model
- Load balancing by service with a failover/heartbeat redundancy model
- All key data on RAID-10 arrays
- Arrays replicated in each zone
- Original source media stored securely off-premise
- Load balancing allows for atomic switch over to new front-end, back-end or database servers
|Outage reporting||Continuous monitoring using Pingdom, nagios and other bespoke tools all linked to text and email alert system.|
Identity and authentication
|User authentication needed||Yes|
|User authentication||Username or password|
|Access restrictions in management interfaces and support channels||No user access to management interfaces by default. All requests for change to interfaces are authenticated independently prior to roll out.|
|Access restriction testing frequency||At least once a year|
|Management access authentication||Dedicated link (for example VPN)|
Audit information for users
|Access to user activity audit information||Users contact the support team to get audit information|
|How long user audit data is stored for||At least 12 months|
|Access to supplier activity audit information||Users contact the support team to get audit information|
|How long supplier audit data is stored for||At least 12 months|
|How long system logs are stored for||At least 12 months|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||Certification International|
|ISO/IEC 27001 accreditation date||14/07/2014|
|What the ISO/IEC 27001 doesn’t cover||
From the Quality and Infosec Manual:
"To the extent that there need be exclusions:
• While the Company has a number of staff on home-working contracts it is satisfied that those contracts and the stipulations therein exclude additional teleworking controls (A.6.2.2 of ISO27001:2013).
• The Company is satisfied that system architecture including RAID storage, dual zones, load balancing, clustering and virtualisation together with near real time database mirroring make traditional formal “backup” procedures redundant (A12.3)"
|ISO 28000:2007 certification||No|
|CSA STAR certification||No|
|Who accredited the PCI DSS certification||Security Metrics|
|PCI DSS accreditation date||16/02/2017|
|What the PCI DSS doesn’t cover||Storage of credit card details.|
|Other security certifications||No|
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||ISO/IEC 27001|
|Information security policies and processes||
A number of internal processes are subject to internal audit on an annual basis including data separation. In addition the following policies are integral elements of emapsite's Integrated Quality and Information Security Management Systems Assurance Manual underpinning the relevant controls within the Statement of Applicability:
- Access Control
- Business Continuity
- Change Management
- Data Security and Separation
- Impact Statement
- Incident Management
- Information Asset Management
- Information Classification
- Information Systems Security
- Operations Security
- Patch Management.
The policies inform system architecture and monitoring.
emapsite's Assurance Committee (AC) meets twice yearly to review the approach to risk and the currency of the controls and policies that surround that risk appetite and any specific new risks. The AC reports to the Board annually.
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
The change control process includes the following phases:
• Logged Change Requests giving full tracking in code repository
• Identification, prioritisation and initiation of change
• Proper authorisation of change (Impact Statement as applicable to identify potential infosec issues )
• Requirements analysis
• Inter-dependency and compliance analysis (to consider infosec impacts)
• Impact Assessment
• Change approach
• Change testing
• User acceptance testing and approval
• Implementation and release planning
• Change monitoring
• Defined responsibilities
• Emergency change classification parameters.
|Vulnerability management type||Supplier-defined controls|
|Vulnerability management approach||Annual risk assessment process identifies threats (physical damage, natural events, loss of essential services, compromise of information, technical failure, unauthorised action and compromise of functions as well as HR centred risks) and vulnerabilities (hardware, software, network, personnel, site, organisation) to create the basis for high level scenario modelling and risk treatment process. At the same time perimeter and network monitoring tools together with WSUS and equivalent patching routines ensure day to day threat mitigation. Systems administrator oversight together with triggers and automation streamline processes while suppliers and industry sources provide topical information.|
|Protective monitoring type||Supplier-defined controls|
|Protective monitoring approach||Information classification is used to determine whether any data supplied by users and customers is high impact level data (in line with GPG13). Systems monitoring including access control logs and exception monitoring of external requests (for example for SQL injection or PPTP VPN login attempts from suspicious places) provides an understanding of how our IT systems is being used or abused by internal or external agents.|
|Incident management type||Supplier-defined controls|
|Incident management approach||
For some common possible events we have pre-defined mitigation processes including auto screensaver for unlocked laptops and encrypted hard drives.
Incidents must be reported and logged. Those dealing with security incidents shall:
• analyse and establish the cause of the incident and take necessary steps to prevent recurrence
• ongoing reporting to all affected parties
• identify problems arising from the incident and to prevent/reduce further impact
• ensure all system logs are securely maintained
• ensure only authorised personnel have access to systems and data
• ensure all corrective and preventative measures are implemented and monitored for effectiveness
|Approach to secure software development best practice||Supplier-defined process|
Public sector networks
|Connection to public sector networks||No|
|Price||£125 per unit per month|
|Discount for educational organisations||Yes|
|Free trial available||Yes|
|Description of free trial||
Free trial includes access to all PSMA/OSMA data included in the standard service.
Trials can run for up to 3 months for non-production purposes.