React Accessibilty

React NaPTAN Editor

An easy to use tool that allows an authority to manage its NaPTAN data, receive information on where updates are required from operators and other sources, and add new fields like accessibility and serviced organisation information (eg Term dates) using a self checking ‘WiKi’ type process.

Features

  • Easy NaPTAN update process
  • Includes accessibility information via WiKi – no work overhead
  • Can include serviced organisation dates – WiKi process
  • Acts as term date record
  • Automated update process from operators using React Timetable Compiler
  • Managed stop approval process
  • Includes bus stop WiKi

Benefits

  • Easy to use, simple interface
  • Crowd sourced/WiKi approach to supplementary information
  • Term dates and accessibility data and stop information
  • Simple stop updates process and export
  • Crowd sources WiKi style accessibility and location stop data

Pricing

£5000 per licence per year

Service documents

G-Cloud 11

630957580189786

React Accessibilty

Russell Gard

07909535533

tenders@react-access.com

Service scope

Service scope
Software add-on or extension No
Cloud deployment model
  • Public cloud
  • Private cloud
  • Hybrid cloud
Service constraints None
System requirements
  • Browser based
  • Platform agnostic

User support

User support
Email or online ticketing support Email or online ticketing
Support response times Within 24 hours Monday - Friday.
User can manage status and priority of support tickets Yes
Online ticketing support accessibility None or don’t know
Phone support Yes
Phone support availability 9 to 5 (UK time), Monday to Friday
Web chat support No
Onsite support Yes, at extra cost
Support levels Support availability:
working days for calls,
24/7 by email
Standard support response times 8 Business Hours
Account Manager with monthly performance reporting.
Support available to third parties Yes

Onboarding and offboarding

Onboarding and offboarding
Getting started We will create the initial user account on the system and can assist the buyer if required through the process of obtaining data feeds and importing the data .
Training can be provided by screen share or onsite if required.
If VPNs data connections are a requirement then we will set these up for the user.
Service documentation Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction The user can export the data update information through the reporting interface.
End-of-contract process We will end access to the data updating API .

Using the service

Using the service
Web browser interface Yes
Supported browsers
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
  • Opera
Application to install No
Designed for use on mobile devices Yes
Differences between the mobile and desktop service The services are provided though a responsive designed site.
Some aspects are more easily used on a desktop / large screen due to the volume of information being presented.
Accessibility standards None or don’t know
Description of accessibility The interface has been designed with AA accessibility in mind but has not been tested.
Accessibility testing None
API Yes
What users can and can't do using the API We provide an API for providing and updating data into the system. This allows bus stop data and timetable data to be updated automatically.
This API will be used by ourselves as part of updating data from the NaPTAN service.
API documentation Yes
API documentation formats
  • Open API (also known as Swagger)
  • PDF
API sandbox or test environment No
Customisation available Yes
Description of customisation Reports on data updates can be customised using an online interface.
Any user with permissions can customise.

Scaling

Scaling
Independence of resources Service impact for each user and ATCO area are is a known quantity.
For each area added we increase system resource.
Customers can be created on a specific instance to ensure separation on request for an additional sum.

Analytics

Analytics
Service usage metrics Yes
Metrics types Login audit data
data updates
Reporting types
  • Regular reports
  • Reports on request

Resellers

Resellers
Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Staff screening not performed
Government security clearance Up to Baseline Personnel Security Standard (BPSS)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations Yes
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency At least once a year
Penetration testing approach In-house
Protecting data at rest Physical access control, complying with another standard
Data sanitisation process Yes
Data sanitisation type Deleted data can’t be directly accessed
Equipment disposal approach A third-party destruction service

Data importing and exporting

Data importing and exporting
Data export approach The user can export the data update information through the reporting interface.
Data export formats CSV
Data import formats
  • CSV
  • Other
Other data import formats NAPTAN XML

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks TLS (version 1.2 or above)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway

Availability and resilience

Availability and resilience
Guaranteed availability Critical - Any fault affecting the supply of information to more than one feed (e.g. server fault, general communications fault) - within 2 days hours. This will be defined as not being met where either: (i) Resolution takes longer than 2 days, or (ii) Resolution takes less than 2 days hours but the System becomes unavailable again within 1 working day from the time of resolution.

Important - Any faults affecting the provision of information to a single customer - within three (3) working days. This will be defined as not being met where either: (i) Resolution takes longer than three (3) working days, or (ii) Resolution takes less than three (3) working days but the System becomes unavailable again within one (1) working day from the time of resolution.

Standard offered SLA is 99% availability.

Refunds based on service credits against future month charges where Critical Faults not resolved in agreed times at rate of 3% per full day of service unavailable beyond SLA.
Approach to resilience Provided upon request.
Outage reporting Service outages are reported through the fault management system.
headline information is available through a service status page.
email alerts can be configured where requested.

Identity and authentication

Identity and authentication
User authentication needed Yes
User authentication Username or password
Access restrictions in management interfaces and support channels Access to service features are controlled by functional permission groups and individual organisation controls for both management and support interfaces.
Access restriction testing frequency At least every 6 months
Management access authentication Username or password

Audit information for users

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 Between 6 months and 12 months

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification No
ISO 28000:2007 certification No
CSA STAR certification No
PCI certification No
Other security certifications No

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance certified No
Security governance approach Accountability is to the Board who regularly review the information security risk register.
Regular testing of compliance and reviews of system configuration against a baseline take place.
Information security policies and processes The Managing Director has overall responsibility for Information security and governance.
Included in induction and on-boarding process.
Awareness and update briefings held.
Regular testing of compliance and reviews of system configuration take place.

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Our software and infrastructure are under configuration management.
The software is fully version controlled with ability for roll back.
Our Fault Management system is used to track all changes to implemented systems and manage the processes, customer access to the FMS allow for full visibility of a systems history.
Before sign off, all changes are reviewed for governance, security, operational and functionality.
Vulnerability management type Supplier-defined controls
Vulnerability management approach We undertake regular review of published statements for any threats to core IT systems.
We are members of specialist transport trade groups for domain specific awareness. Security forms part of regular customer reviews to enable customer specific threats to be identified.
Security updates to operating system and related components including off the shelf software are configured to automatically install.
The information governance process includes risk assessment of security threats.
Protective monitoring type Supplier-defined controls
Protective monitoring approach Regular reviews of system usage incl user logins, system automatically reports above defined levels of increased system use.
Any potential or actual compromise becomes a critical incident with immediate response with customer and Director involvement.
Critical incident management is available 24/7.
Regular reviews of system usage incl user logins, system automatically reports above defined levels of increased system use.
Any potential or actual compromise becomes a critical incident with immediate response with customer and Director involvement. Critical incident management is available 24/7.
First response is to make system inaccessible, where possible leaving it running for any forensic analysis needed.
Incident management type Supplier-defined controls
Incident management approach Common incidents have FAQ and standardised responses in place.
All customers have access to a fault management system which is the preferred route for reporting.
Incident updates are published through the fault management system.

Secure development

Secure development
Approach to secure software development best practice Supplier-defined process

Public sector networks

Public sector networks
Connection to public sector networks No

Pricing

Pricing
Price £5000 per licence per year
Discount for educational organisations No
Free trial available No

Service documents

pdf document: Pricing document pdf document: Skills Framework for the Information Age rate card pdf document: Service definition document pdf document: Terms and conditions
Service documents
Return to top ↑