Staff Attendance Recording System (StARS-MS)
StARS-MS is an integrated personnel management system for fire and rescue services. The system manages staff data and appliance availability, rostering, sickness management and reporting. It provides key management information for strategic planning and decision making.
- Integrated with mobilising systems (Vision, ProCAD)
- Integrated with HR systems (Cyborg, ResourceLink)
- Integrates with payroll systems via data extract
- Real time management reporting
- Recording of attendance, absence and sickness
- Supports the front line whilst delivering back office savings
- Single point of data capture
- Elimination of dual data entry and paper processing
- Quicker and more effective deployment of resources
- Real time view of resource availability
- Provides key management information, allowing strategic planning and decision-making
- Improves resilience and efficiency for both support and operational staff
- Improved workforce strategic planning of staffing levels and shortfalls
- Streamlines the process of managing personnel and resources
- Self administration and configuration
£5000 per licence per month
- Pricing document
- Skills Framework for the Information Age rate card
- Service definition document
- Terms and conditions
- Modern Slavery statement
Sequel Business Solutions Limited
020 3653 2198
|Software add-on or extension||No|
|Cloud deployment model||Public cloud|
|Email or online ticketing support||Email or online ticketing|
|Support response times||Depending on severity but normally within two hours of a support log being raised.|
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||9 to 5 (UK time), Monday to Friday|
|Web chat support||No|
|Onsite support||Onsite support|
Support is provided via a helpdesk between the hours of 9am-5pm Monday to Friday. The cost of this support is included in the product costs.
Support outside of these hours can be provided at additional cost.
A client account manager, service delivery manager and support team are available as part of the service.
|Support available to third parties||Yes|
Onboarding and offboarding
|Getting started||We provide on-site and online training and documentation.|
|End-of-contract data extraction||An extract of the data will be provided in CSV format.|
|End-of-contract process||There are no additional costs except for the extraction of data from the service database into CSV format.|
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||The application is available to be used on any internet browser, however it is best viewed on desktop or tablet devices|
|What users can and can't do using the API||
He API provides methods that provide the following functionality:
Teams/Employees for Shifts & Stations
The API is initiated upon request.
The API methods provide the full functionality required to complete those tasks and are available to be accessed/used whilst a subscription is held.
|API documentation formats||Open API (also known as Swagger)|
|API sandbox or test environment||No|
|Independence of resources||Each deployment for a client is ring-fenced and not part of a shared infrastructure.|
|Service usage metrics||No|
|Supplier type||Not a reseller|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||Up to Security Clearance (SC)|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||
|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||Another external penetration testing organisation|
|Protecting data at rest||
|Data sanitisation process||Yes|
|Data sanitisation type||
|Equipment disposal approach||Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001|
Data importing and exporting
|Data export approach||Data can be exported upon request.|
|Data export formats||CSV|
|Data import formats||CSV|
|Data protection between buyer and supplier networks||
|Data protection within supplier network||
Availability and resilience
The Microsoft Azure environment has a guaranteed availability of 99.9%. Refunds and service credits for not maintaining that level of availability can be discussed on a client by client basis.
More information on availability can be found in Microsoft's Online Service Terms at http://www.microsoftvolumelicensing.com/Downloader.aspx?DocumentId=13655
|Approach to resilience||Please see https://www.microsoft.com/en-us/cloud-platform/global-datacenters and https://www.microsoft.com/en-us/TrustCenter/|
|Outage reporting||Please see https://azure.microsoft.com/en-us/status/ and https://portal.azure.com/#blade/HubsExtension/ServicesHealthBlade|
Identity and authentication
|User authentication needed||Yes|
|Access restrictions in management interfaces and support channels||Claim and Role based authorisation.|
|Access restriction testing frequency||At least once a year|
|Management access authentication||
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||User-defined|
|Access to supplier activity audit information||Users contact the support team to get audit information|
|How long supplier audit data is stored for||User-defined|
|How long system logs are stored for||User-defined|
Standards and certifications
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||BSI|
|ISO/IEC 27001 accreditation date||29/02/2018|
|What the ISO/IEC 27001 doesn’t cover||N/A|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||29/09/2016|
|CSA STAR certification level||Level 3: CSA STAR Certification|
|What the CSA STAR doesn’t cover||None|
|Who accredited the PCI DSS certification||Coalfire Systems Inc|
|PCI DSS accreditation date||01/04/2016|
|What the PCI DSS doesn’t cover||N/A|
|Other security certifications||Yes|
|Any other security certifications||
|Named board-level person responsible for service security||Yes|
|Security governance certified||Yes|
|Security governance standards||CSA CCM version 3.0|
|Information security policies and processes||
An Information Security Management Program has been established to enable Microsoft Azure to maintain and improve its management system for information security. Through establishment of the ISMS, Azure plans for and manages protection of its assets to acceptable security levels based on defined risk management processes. In addition, Azure monitors the ISMS and the effectiveness of controls in maintaining the confidentiality, integrity and availability of assets to continuously improve information security.
The ISMS framework encompasses industry best-practices for information security and privacy. The ISMS has been documented and communicated in a customer-facing Information Security Policy, which can be made available upon request (customers and prospective customers must have a signed NDA or equivalent in place to receive a copy).
Microsoft Azure performs annual ISMS reviews, the results of which are reviewed by management. This involves monitoring ongoing effectiveness and improvement of the ISMS control environment by reviewing security issues, audit results, and monitoring status, and by planning and tracking necessary corrective actions.
|Configuration and change management standard||Supplier-defined controls|
|Configuration and change management approach||
Visual Studio Team Services to track changesets on the code base.
Impact assessment with regards to overall solution and design.
Security assessment when changing API methods.
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||
When providing the Antimalware solution for Virtual Machines, Azure is responsible for ensuring the service is highly available, definitions are updated regularly, that configuration through the Azure Management Portal is effective and that the software detects and protects against known types of malicious software. MCIO-managed hosts in the scope boundary are scanned to validate anti-virus clients are installed and current signature-definition files exist.
Vulnerability scans are performed on a quarterly basis at a minimum. Microsoft Azure contracts with independent assessors to perform penetration testing of the Microsoft Azure boundary.
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||
Microsoft Azure employs sophisticated software-defined service instrumentation and monitoring that integrates at the component or server level, the datacenter edge, our network backbone, Internet exchange sites, and at the real or simulated user level, providing visibility when a service disruption is occurring and pinpointing its cause.
Proactive monitoring continuously measures the performance of key subsystems of the Microsoft Azure services platform against the established boundaries for acceptable service performance and availability. When a threshold is reached or an irregular event occurs, the monitoring system generates warnings so that operations staff can address the threshold or event.
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||
Microsoft has developed robust processes to facilitate a coordinated response to incidents.
• Identification – System and security alerts may be harvested, correlated, and analyzed.
• Containment – The escalation team evaluates the scope and impact of an incident.
• Eradication – The escalation team eradicates any damage caused by the security breach, identifies root cause for why the security issue occurred.
• Recovery – During recovery, software or configuration updates are applied to the system and services are returned to a full working capacity.
• Lessons Learned – Each security incident is analyzed to protect against future reoccurrence.
|Approach to secure software development best practice||Conforms to a recognised standard, but self-assessed|
Public sector networks
|Connection to public sector networks||No|
|Price||£5000 per licence per month|
|Discount for educational organisations||No|
|Free trial available||No|