NOT PROTECTIVELY MARKED North Yorkshire Police Specification for the Procurement of a Mobile Asset Utilisation and Deployment System (MAUDS) Contents Section 1 - Overview Introduction Overview Requirements Section 2 – Business Requirements Phase 1 – Critical Functionality Areas Phase 2 1. Improved Resource Management 2. Tasking and Briefing 3. Integration with Existing NYP Systems 4. Efficient Fleet Management 5. Safety Improvements 6. Management Information 7. Future Proofing 8. Technical Considerations 9. Command and Control Requirements 10. Implementation and Rollout Section 3 – Further Considerations Appendix A – Existing Infrastructure NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 1 of 29 NOT PROTECTIVELY MARKED NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 2 of 29 NOT PROTECTIVELY MARKED Section 1 – Overview 1. Introduction 1.1 Following a review of operational policing services and the development of a new Operational Policing Model (OPM), North Yorkshire Police Service are keen to source a solution and work with a supplier who is capable of upgrading their current Mobile Asset Utilisation and Deployment System(MAUDS) infrastructure and work with the service to embed a range of functionality that will support the OPM. Suppliers are requested to review and respond to this ITT document detailing how they would provide the appropriate functionality, where relevant providing examples of how this has been delivered in other organisations. Or, if the relevant functionality is not yet within your product set how and when you propose to have this available. 2. Context 2.1 NYP covers an area 3200 sq miles having a population of approx. 800,000, and is the largest single police service area in the country. We are consistently one of the safest services in the country and work hard to maintain this position. The service employs approx 1390 police officers and 1000 police staff, including 180 PCSOs, and like most other public sector organisations is working hard to deliver continued levels of service against a back drop of reducing funding. This has required the service to look at all areas of the organisation and modify how we do things, utilising technology to its best possible advantage. This is an on-going process and the upgrading of the MAUDS system is a key element of this. 2.2 Alongside the police officer and staff numbers the service currently has 502 vehicles. The majority of NYP’s fleet would be within the scope of the MAUDS project. However, there must exist the ability to turn officer and vehicle tracking off, when these are engaged in some operational situations. 2.3 Being a geographically large and rural county there are significant areas that suffer from poor mobile data connectivity on such as 3G/4G and in some of the more remote areas there is limited Airwave TETRA connectivity. 2.4 NYP want to embed a more tasking orientated culture into their deployment processes. Previously technology has not supported this, thus relying on officers to volunteer to attend an incident rather than a controller having all the information they need to be able to confidently task a resource. 2.5 The Service is also currently in the early stages of a mobile data project with the intention of rolling out a mobile data solution to the vast majority of operational officers, PCSOs and some staff. Any MAUDS solution must be compatible with industry standard mobile technologies, devices and their Operating Systems i.e. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 3 of 29 NOT PROTECTIVELY MARKED Android, IoS and Windows. Appendix A shows a diagram detailing the current technical topology of the existing MAUDS solution. 2.6 Many of the service police stations are located in rural areas as is the current service headquarters. Details of these can be provided if required. 3. Requirements 3.1 The service have conducted significant research into current MAUDS technologies, including engagement with other forces who are using the technology and the operational improvements and cashable benefits they have been able to achieve. This information has then been used internally to inform NYP’s development and design of the new OPM. Listed below are the requirements, from a MAUDS system, that the service has identified as being key enablers to driving improvements in operational policing, raising customer satisfaction levels and ensuring NYP are delivering the most effective possible policing service. 3.2 NYP require potential suppliers to respond to this ITT, identifying how they can assist the organisation in delivering its new OPM and achieving the expected operational and financial benefits. The proposed solution should be specified from a perspective that the successful supplier will be providing a complete solution to NYP to include: all associated hardware, and any fitting costs as detailed in section 8 Technical Considerations all associated software initial training interfaces consultancy support (implementation, rollout and after sales support) data migration upgrades and consultancy as required with other suppliers (these may include Northgate for mapping, Steria for Storm, APD for Tetra Gateway (TGW) and Cortex) to ensure full integration with our existing systems any other associated services required for a successful deployment of the technology configuration of the backhaul of data over 3G/4G, a potential for multi-telcos SIM cards, associated car mount antennas and the sizing and scoping of the actual data channel from vehicle to data centre This list is not exhaustive and further details are provided in Section 2. NYP would also be interested in a hosted and managed solution (that was fully PSNP compliant), if this is a service that you offer, please provide costing’s on a separate table provided in Appendix A – pricing schedule. Not being able to provide this service will not disadvantage your submission and does not form part of the scoring process. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 4 of 29 NOT PROTECTIVELY MARKED 3.3 The financial information provided in your tender should be broken down to individual costs per element of the solution. 3.4 Section2, Business Requirements section of this document identifies the key areas of functionality and benefits that NYP expect to achieve from their investment in a MAUDS solution. The section is broken into 10 key activity areas . 3.5 Section 2 of the specification details the areas of functionality that NYP require to be demonstrated. Each of these consists of: Overview of current processes Expected benefits NYPs Requirements and Supplier Responses – complete the supplier response sections detailing how you would deliver the stated element of functionality NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 5 of 29 NOT PROTECTIVELY MARKED Section 2 – Business Requirements Phase 1. Critical Functionality Area for NYP The subject areas and questions in the following table are considered critical areas of functionality required by NYP and will be reviewed and scored on a Pass / Fail basis. A suppliers inability to satisfy these areas of functionality will result in their submission being deemed unsuitable and will not be progressed further in the assessment process. This section is Phase 1 of the evaluation process and, in some cases, similar information may be required to be provided in other responses. 1.1 Resource Management Detail how your solution can assist NYP with improving its resource management, and its ability to assist officers in the field (400 words max.) 1.2 Tasking and Briefing Detail how your solution delivers and manages a tasking process, this should include the capability for officers to be able to accept or reject a task and for this to be logged and tracked. In addition to the tasking process detail any functionality that your solution delivers to assist with ‘location aware’ officer briefings (400 words max.) 1.3 Management Information Detail what Management Information your solution currently provides and how this can be used to help NYP improve operational effectiveness. Provide details of the reports that are available from your solution ‘out of the box’. (400 words max.) Phase 2, responses will only be assessed and scored if suppliers’ responses Pass the Phase 1 evaluation process above. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 6 of 29 NOT PROTECTIVELY MARKED Items 2 – 11 are the scored elements of the specification, and will only be assessed if suitable responses are received to the critical functionality areas above. Phase 2. 1. Improved Resource Management - This section represents 8% of the total score 1.1 Current Processes NYP have existing MAUDS technology, that was originally installed in the early 2000’s. This can be interrogated at a unit level, but lacks the tools to aggregate and analyse activity and movements at a force level. 1.2 Expected Benefits Evidence based analysis of resource usage and attendance at location targets Be able to demonstrate officer attendance at given patrol targets internally and to the public Enable controllers and commanders to deploy operational resources more effectively by balancing the priorities of proactive and reactive tasks to meet irregular levels of demand Enhance officer safety and provide more responsive support by tracking officer deployment in “real-time” Increase visible patrolling and the percentage of time spent by police officers on operational duty in the areas identified as priorities by local communities and National Intelligence Model (NIM) analysis to support local policing and improve public confidence 1.3 NYPs Requirements Supplier Response a) How does your solution identify how resources and assets (officers staff and vehicles) have been deployed relative to a given location target? b) Detail how your solution provides a range of telematics information from a vehicle to include but not exclusively, speed, braking, mileage, lights on/off, accelerating, blues&twos on/off, direction of travel, time of last update c) Does your solution have the ability to change the polling rate of NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 7 of 29 NOT PROTECTIVELY MARKED d) e) f) g) h) i) j) devices on demand. Detail how this is achieved. Demonstrate how deployments could be linked to STORM incidents so it is identifiable which resources went to which incident Details how your solution allows Supervisors / Controllers to see the location of all deployable resources and assets across the force in real time Through geo-fencing or other similar technology detail how you are able to identify the number of assets that have visited that locality and incident location and the duration of their visit Detail how your solution can Identify the location of any number of assets in real-time or at a given historic time (or period) Provide details of how your solution can identify a vehicle driver and occupants quickly and easily, so for example system checks can be made to ensure the driver is qualified for the vehicle type they are driving, if this is not the case their supervisor can be notified Provide details of how your solution has the ability to replay, snail trail, screen capture of archive plays One requirement that would be very useful for the service to achieve, would be to have visibility of neighbouring Police Service resources. Provide details of any projects that you have delivered that have included this type of capability. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 8 of 29 NOT PROTECTIVELY MARKED 2. Tasking and Briefing - This section represents 8% of the total score 2.1 Current Processes NYP have a number of different methods of delivering briefings and tasking across the organisation including: Sgt delivers briefing to team either on site or over the phone. Officers self brief by reviewing incidents and intelligence that have occurred recently Force briefing manager application captures items to be briefed out Taskings can come through briefings, from the FCR, from the tasking team, or from supervision during the shift NYP operates its tasking processes in line with NIM, including holding a Daily Management Meeting (DMM), and TTCG. The service has also recently introduced the THRIVE (Threat, Harm, Risk, Investigate , Vulnerability, Engagement) initiative using this risk assess, prioritise and determine most appropriate response to calls On attendance at a tasking, Officers are expected to complete a number of tasking return forms and this may involve completing 3or4 forms for the same tasking based on current local initiatives 2.2 Expected Benefits Tasking and Briefing is a key area of functionality for NYP, we are therefore particularly interested in how you have delivered MAUDS functionality, that assists in this process, into other organisations. Please provide details of up to 3 examples of how you have delivered benefits through your contribution to a tasking and briefing process in other organisations. The following are what NYP expect to achieve from improved tasking and briefing processes: A more consistent and informative briefing process leading to better informed and therefore more effective officers Be able to review effectiveness and attendance at tasked location targets with a view to being able to modify patrol strategy as required Increases in the amount of visible patrolling taking place Improved quality of deployments through enhanced intelligence packages Integration with tasking processes – introduction of an element of dynamic tasking based on previous history (such as an officer is notified they are entering an ASB hot spot, and they may want to patrol there for longer, or on a specific street location) Improved and more targeted briefing processes giving officers the information when and where they need it, this to be coupled with NYP’s mobile data solution once this is established (expected summer 2015) Reduced time for officers completing tasking returns – expectation that this could be automated or simplified based on the officers NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 9 of 29 NOT PROTECTIVELY MARKED attendance at a location 2.3 NYPs Requirements Supplier Response a) Provide details of how the system has the ability to notify officers via their mobile device or an in-car system that they are entering a target location (e,g, ASB hot spot), or a tasking exists for that vicinity b) Provide details of how your solution would support the utilisation of a tasking list which contains items such as curfew checks, reassurance visits etc. c) If the functionality is available detail how officers can accept/reject a tasking and this is recorded on the tracking system. If accepted a method of tracking is then initiated, if rejected the task is assigned to another suitable resource d) If functionality is available detail how your MAUDS solution supports an officer who has accepted a task and is then given supporting information appropriate to that location / task through their mobile device e) Provide details of how your solution allows the creation of geofences that identify target locations. Demonstrate how these can be created simply, easily and independently by such as supervisors f) Explain how your solution can contribute to a service briefing system by identifying such as what activity had already taken place for a given tasking/location NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 10 of 29 NOT PROTECTIVELY MARKED 3. Integration with Existing NYP Systems - This section represents 5% of the total score 3.1 Current Processes NYP uses STORM for their Command and Control processes, this is integrated with Northgate XC for mapping functionality (XD is also used for more specialist mapping GIS functionality and XI for wider force mapping requirements) Niche is used for incident / crime recording APD is used for the location pings via the Airwave TETRA radios and APD INCA for the vehicle location. Tetra Gateways integrate the location information onto the XC Mapping and Storm Command and Control, and clear tone for in-car video. Tranman is used for fleet management activities The service is currently implementing a new HR system called Origin The Tetra Gateway provides: 1) the vehicle call sign identification for the cortex radio software for dispatchers 2) the table which reference the existing radio issi number and call sign which then cross reference the call sign table within storm to populate the storm resource list 3) there are a number of vehicles that report e.g. pool vehicles that are not on our storm resource list. This is reliant on the driver switching the radio on – process should be automated. 3.2 Expected Benefits NYP expects any MAUDS solution will integrate with other systems as required, with minimal disruption and integration costs Minimal re-training requirements The MAUDS data set is able to be viewed alongside other NYP data sets to inform the ‘big data’ picture for the service and provide enhanced organisational intelligence 3.3 NYPs Requirements Supplier Response a) NYP uses IBM’s ibase system for Intelligence analysis, and brings together data from a number of NYP systems to provide a rich picture of linked activity, it is anticipated that the data generated from a MAUDS system can add significantly to this NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 11 of 29 NOT PROTECTIVELY MARKED b) c) d) e) picture – the ability to make this data available for use by ibase is a requirement of the system. If applicable provide details of how your solution has been used in other organisations to inform a bigger picture and how this has been used to support and enhance analysis processes. The solution must incorporate a GIS/ mapping system which covers the complete geographic area of the service area at a range of scales from 1:250,000 to ‘house level’ (1:1250 for urban and 1:2500 for rural areas) and includes aerial photography. Suppliers must provide details of the GIS mapping system that they propose to use with their MAUDS solution specifying the layers/scales that it renders, associated level of detail e.g street names etc. and the method of ‘zooming’ between scales. The solution must not rely on using publicly available mapping on the World Wide Web. Provide details of how your solution meets this requirement. All relevant supplied equipment must be compatible within the One Box standard. Provide details of the equipment that you propose to provide and how it meets this standard. NYP already have a virtualised Microsoft and Linux server environment running under VMWare vSphere and are moving to Virtualised windows desktop environment running under VMWare, Mirage and View. All deployed technology should be compatible with this and be able to operate in a virtualised environment. Detail how your solution will operate in this environment and provide examples of how this has been done in other similar environments. NYP see considerable benefit in being able to have future NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 12 of 29 NOT PROTECTIVELY MARKED duties information (next 0 -8 hours) sat alongside current resource locations. This has the potential to improve planning of the use of resources during live operations, and ensuring a smoother handover between shift changeovers Provide details of how this can be achieved f) Provide a detailed technical specification of the infrastructure required to support your proposed solution based on your experience of other organisations and the size of the service NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 13 of 29 NOT PROTECTIVELY MARKED 4. Efficient Fleet Management - This section represents 3% of the total score 4.1 Current Processes NYP already have a very effective fleet management function. However, they are restrained from improving this further by the limited information that is available to them. The fleet is currently managed under the Tranman application, therefore integration with the Tranman application is required 4.2 Expected Benefits Evidence based analysis of resource usage and attendance at location targets Be able to demonstrate officer attendance at given patrol targets internally and to the public Enable controllers and commanders to deploy operational resources more effectively by balancing the priorities of proactive and reactive tasks to meet irregular levels of demand Enhance officer safety and provide more responsive support by tracking officer deployment in “real-time” Increase visible patrolling and the percentage of time spent by police officers on operational duty in the areas identified as priorities by local communities and National Intelligence Model (NIM) analysis to support local policing and improve public confidence 4.3 NYPs Requirements Supplier Response a) Provide details of how your black box / hardware / software technology solution can provide information and reports that allow identification of inefficient vehicle usage b) Provide details of how your solution will automatically collect information from vehicles relating to mileage that will allow more accurate scheduling of servicing c) Your solution should provide a set of tools/reports that give the service the ability to monitor driving standards and therefore proactively identify deteriorating driving standards and take appropriate early intervention action. Detail how your solution can support this process. d) Provide details of how your solution can be used to stipulate NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 14 of 29 NOT PROTECTIVELY MARKED tolerances around locations (such as speed restrictions in certain areas), and report to such as Driver training when these are breached e) Details how your solution integrates with a mobile data terminal and sat nav capability that can also push out the location of an allocated incident f) Detail how you have integrated the MAUDS solution with ANPR technology in other services NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 15 of 29 NOT PROTECTIVELY MARKED 5. Safety Improvements - This section represents 4% of the total score 5.1 Current Processes Driver training currently use some cameras in car and on the trainees face to watch eye movement. Operational RPG and FSU cars are fitted with front and rear facing cameras to record activity. NYP currently use clear tone to manage the incar video. 5.2 Expected Benefits NYP can monitor driver training and link camera images to location/situations whilst driving is taking place A view of front and back of cars provides evidence of 5.3 NYPs Requirements Supplier Response a) Provide details of any projects you have undertaken that have involved linking cameras to MAUDS solution that video record officers whilst under driver training and can then be analysed afterwards b) Detail any solution you have implemented where cars are fitted with video that records all activity to the front and behind whilst the vehicle is in use. This is linked to the MAUDS application so can be viewed alongside other data such as the speed of the car, location, whether braking or not etc. c) Does your solution allow integration with in-car video systems, if so detail how this is achieved d) Detail how your solution provides instantaneous feedback to notify vehicle drivers if they are exceeding driving tolerances NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 16 of 29 NOT PROTECTIVELY MARKED 6. Management Information - This section represents 8% of the total score 6.1 Current Processes Currently only have the capability to view resources and vehicles real-time locations, and interrogate historical movements on an individual unit basis 6.2 Expected Benefits Efficient and effective utilisation of vehicles Demonstrably less time spent in the station by officers Reduced fleet mileage More effective taskings that are closely managed and therefore issues are dealt with more quickly Be able to demonstrate internally and to the public, where appropriate, patrol strategies and effectiveness An improving safety record in relation to vehicle incidents 6.3 NYPs Requirements Supplier Response A comprehensive suite of management information is available to include but not limited to:a) The ability to report on such as how many cars were double crewed and for how long over a given period of time b) Movement of officer and vehicle resources both live and historically c) The use of the reporting needs to be automated as far as is possible d) Reporting on last known location update date / time to identify such as lost radios e) Ability to report from different types of resource groups e.g. handheld, vehicle types defined by role f) The ability to report from historic MAUDS data g) Be able to provide a range of information that will support crash investigations where police vehicles have been involved (such as NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 17 of 29 NOT PROTECTIVELY MARKED h) i) j) k) l) m) n) o) p) speed, braking, mileage, lights on/off, accelerating, blues & two’s on/off etc.) There are tools/interfaces that allow the service to create their own reports 3rd party reporting tools can be used to interrogate the MAUDS data set Reports are available from the MAUDS system that are linked to a tasking, and can demonstrate what activities have been undertaken in relation to a given task Access to historical data spanning a range of different requirements and functions but to assist with such as eg Professional Standards Department (PSD), performance, area supervision, FCR supervision Ability to replay the data (recent and historic) onto existing mapping systems Ability to ‘record / screen shot’ archive replays for evidential purposes A breakdown of the types of journeys undertaken e.g station to station, response, incident type Be able to easily identify categories of activity by days of the week, and times of day Identify how your solution can set and monitor KPIs and other performance data NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 18 of 29 NOT PROTECTIVELY MARKED 7. Future Proofing - This section represents 5% of the total score 7.1 Current Processes N/A 7.2 Expected Benefits NYP engage with a supplier who can provide a MAUDS solution that meets current and future capability NYP engage with a supplier who are flexible and will work with the service over a period of time to enhance the MAUDS system to achieve maximum operational benefit 7.3 NYPs Requirements Supplier Response Suppliers should provide relevant details of their system and how it will be developed during its planned lifetime and provide details of associated costs within the pricing schedule including:a) The functionality of any additional system modules that are available or are planned, and the time scales within which these are expected b) The number of planned software releases per year c) How and when software and hardware upgrades or additional modules are made available to clients, with associated costs d) Do you operate national/regional user groups e) Do you have any other mechanisms for sharing best practice among the user community of your product set f) NYP have a number of initiatives underway working with neighbouring forces in order to achieve improved operational effectiveness, and value for money. This is an on-going and developing picture and in order for the force to continue to develop these services there is a requirement that any system needs to be scalable both in terms of expansion and contraction over the period of any contract. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 19 of 29 NOT PROTECTIVELY MARKED g) Detail how you are remaining cognisant and informed about working towards integration with the new Emergency Services Mobile Communications Project (ESMCP) h) Detail how you engage with customers re statutory and regulatory changes that impact on your system functionality e.g. How do you notify customers? How long does it take you to respond to these changes? Do you charge for updates of this nature? Please note your response to this question does not carry any marks and is for information. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 20 of 29 NOT PROTECTIVELY MARKED 8. Technical Considerations - This section represents 4% of the total score 8.1 Current Processes N/A 8.2 Expected Benefits The chosen supplier must be flexible and will work with the service and other system providers to achieve a fully functioning and integrated MAUDS solution and implementation The system is designed and configured to be resilient with maximum up-time in line with the requirements of an emergency service 8.3 NYPs Requirements Supplier Response a) Detail how your solution technology optimises communications connectivity and therefore improve the reliability and timeliness of the information available. Solutions that can address this problem will be looked on favourably, this should include functionality such as ‘store and forward’ that allows data to be stored until a connection is established b) NYP, alongside all other police services are making their infrastructure compliant with the standards set out under the Government Public Sector Network initiative PSN. NYP expects to have achieved compliance by Summer 2015, any new functionality introduced to the service must be compliant with PSNP standards. Suppliers are required to detail how their proposed solution will be compliant with any PSN standards c) What levels of security are available in your system, does the system support an organisational hierarchical structure, and if so how is this created and maintained - can this be pulled from NYP’s current HR system Origin. Demonstrate how your system is secure with different levels of security applicable to a users role. This may NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 21 of 29 NOT PROTECTIVELY MARKED d) e) f) g) h) i) j) k) include things such as an officer is restricted to seeing their own movements or those of their colleagues who work in the same team. Detail how your MAUDS solution could take in GPS data from external sources. An example of this might be prisoner tagging systems. Demonstrate how your solution could utilise the existing layered data sets that NYP already have in place and built up over many years. The solution must be able to accept all existing layered data sets, developed for current mapping application such as CCTV etc. Suppliers must identify how much data is transmitted from each device and how frequently, so that we can assess current infrastructure capacity for such as broadband traffic and data storage requirements. Include a topological network/connectivity diagram of how your proposed solution will work, including the use of any APN, and integration with firewall systems Is the solution you are proposing carrier agnostic, i.e. NYP will have the opportunity to combine any data transmissions from a MAUDS solution with other contracts/negotiations underway via multitelcos and the Airwaves network thus maximising coverage across North Yorkshire. From the technology implemented in cars to record location and usage data, is there an option for this to be transmitted via wifi so that data transmission over 3g/4g can be optimised Provide details of how your solution will be compatible with future changes to airwave and any move to LTE (4g technologies) Provide details of how the different elements of your system will NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 22 of 29 NOT PROTECTIVELY MARKED l) m) n) o) p) q) r) s) t) be patchable/updateable. The preference would be that this can be done remotely for all modules. Provide details of your preferred database technology and the details of any others that your system supports. NYP currently support SQL Sever or Oracle platforms. Provide details of your preferred server platform and the details of any others that your system supports. The service currently uses Windows Server 2008 R2, Windows Server 2012 and SUSE SLES 11SP3 Enterprise Linux where Linux is a requirement. Provide details of any mobile version of the app to allow access for such as remote configuration of technology elements Detail how your MAUDS solution has the ability to take in GPS data from the internal NYP TGW servers Detail how your MAUDS solution interacts with the APD Cortex System Apps and other system requirements must be capable of working on a range of mobile data platforms that may include Windows, Android and Apple IOS. Detail the range of platforms that your solution can operate on. Through your work with other organisations please detail how you would assist us with transitioning to your system and how we could retain access to historical tracking data Provide examples (maximum of 3) of where you have upgraded from an existing MAUDS system with integration to Command and Control to your MAUDS system. From your experience with the installations provide details of how time Synchronisation to other NYP systems will be managed NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 23 of 29 NOT PROTECTIVELY MARKED u) What resilience measures would you recommend for your MAUDS solution, what have you implemented in other installations v) To dovetail with current processes we need to be able to : ‘Unlink an officer’ on the storm resource list when they are away from the vehicle (so when leave vehicle for foot pursuit) so they can be tracked on the mapping, without the dispatcher having to remove them from the call sign – detail how this can be achieved in your system. w) Detail how your system interacts and uses call sign information x) Provide details of how much data your solution will cache if out of bearer and how and when this data will be sent back in y) Provide details of how black box technology can be managed remotely and data extracted, including log dumps being requested remotely z) Provide details of how you currently provide support for customers of your MAUDS solution. Please note that any remote access by third parties for support and upgrades must be in accordance with our remote access policies and procedures, and in line with any PSNP requirements. Details of these can be provided at a later stage if required. aa) Detail how telematics data is transmitted, over which networks and any priority associated with these. What networks are used (e.g. 2g, 3g/4g, Tetra Airwave……..) bb) In line with best practice there is a requirement for an annual inspection/check of vehicle data recording devices. Confirm how this would be factored into any maintenance plans you would propose. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 24 of 29 NOT PROTECTIVELY MARKED cc) If you offer a fully hosted and managed solution please provide details of this here, including any compliances achieved. A separate table to provide costs for this are available Appendix A – pricing schedule. Please note your response to this question does not carry any marks and is for information only. NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 25 of 29 NOT PROTECTIVELY MARKED 9. Command and Control / FCRXN (NYP Force Control Room) Requirements - This section represents 3% of the total score 9.1 Current Processes NYP currently receive live resource location information from both the force deployable vehicles and police officers and staff which are mapped directly onto our XC mapping system. The current system receives information from the HR system to indicate if a resource is from a deployable department or not. Supervisors manually provide FCR with details of who is on duty, after ringing round teams to see who has turned in. 9.2 Expected Benefits Minimise training requirements Effective integration with existing technologies Reduce administration and support required to the system to a minimum FCR are notified automatically who is on duty via an automated link between the duties and Command and Control system reducing the administrative burden on Sgts and FCR staff 9.3 NYPs Requirements Supplier Response a) Detail how your solution supports the ability to filter the types of resources that are displayed on the mapping application e.g. Dogs, Firearms, Deployable, Non-deployable etc. b) Detail how your solution can identify who is on duty and how this information is integrated with existing systems, including the duties/HR system (Origin) and STORM c) Provide details of how resources are linked to vehicles and how this information is integrated with the Storm C&C system NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 26 of 29 NOT PROTECTIVELY MARKED 10. Implementation and Rollout - This section represents 2% of the total score 10.1 Current Processes N/A 10.2 Expected Benefits Successful delivery of a MAUDS solution into NYP Based on the information provided suppliers are required to provide a benefits profile and approach of how and what NYP could potentially achieve through cashable and operational efficiencies were you to be the successful system provider. This may take the form of examples of savings and benefits achieved in other police/ similar organisations but based on NYP’s resource and vehicle numbers. 10.3 NYPs Requirements Supplier Response a) Detail how you would manage an implementation with NYP and what resources would you allocate to the project , what resources would you expect NYP to provide. For information NYP manage projects following the Prince 2 methodology. b) Do you have, or would you develop a detailed plan of activities based on your experience of other implementations. Provision of a detailed implementation and transition plan will be a requirement to work with NYP c) Provide details of how you would assist NYP in delivering the benefits the project aims to achieve. d) Detail your expected time scales for an implementation in NYP, and provide a plan is MS Project or other preferred format based on the requirements detailed in this document e) Detail how you would achieve a skills transfer to NYP staff, in being able to support your system – what level of formal training would be required? NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 27 of 29 NOT PROTECTIVELY MARKED Section 3 – Further Considerations 3.1 NYP welcome submissions from a range of innovative and forward thinking suppliers who can demonstrate a track record in the delivery of MAUDS technologies, in blue light and/or other services. 3.2 NYP would expect any potential suppliers to engage in a trial or proof of concept, to allow us to fully evaluate your solution and to ensure it is compatible with current systems, and that your proposed ‘black box’ technology can be fitted/is compatible with our vehicle fleet. 3.3 The current NYP fleet vehicle mix is as shown in Table 1. Type Total Car M/Bike Van Grand Total Table 1 292 18 192 502 NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 28 of 29 NOT PROTECTIVELY MARKED Appendix A NOT PROTECTIVELY MARKED Version: Final 15.01.15 Page 29 of 29