Options for training, simulating, testing and experimenting in Crisisworks
One of the benefits of Crisisworks is that you don’t have to be in the middle of a big emergency to use it.
You’re able to use it at any time to train, test or experiment. You can even use it to run a scenario, or organised test event involving multiple people, agencies and roles. Crisisworks has built in tools for “sandboxing”, that is, creating an isolated test environment that won’t impact your day to day or emergency use.
The most important step is deciding what you’re going to use the test environment for. This can determine how you configure it and what assistance you may need, if any.
Here are two of the main options along with some of their pros and cons:
Test Event
Test Events let you create an event just like any other in Crisisworks, with the key difference any activity is clearly marked ** TEST ** in communications and auditing.
Because you’re limiting the users and roles involved in the test, only those people who are on duty can participate and receive notifications.
Some of the main uses for Test Events are:
Training events
Practice and drills
Simulations and scenario exercises
Testing of new functionality or features
Experimentation (for example for new uses or processes)
Creating a Training or Test Event has the added benefit of keeping a full audit log of your practice, and testing that your users have the correct settings and positions to sign in and perform their duties. It is also good testament to your preparedness if you are ever under scrutiny in your emergency or risk management role.
The first step is event creation. In the New Event template you’ll find a Category called “Test Only”. This marks all system notifications as test messages. It is a good idea when creating a new test event that you put something in the title of the event that identifies it as a test or training event. It is also recommended that you put the start date in the title so that other users know that it is a current test. If you’re doing ongoing testing you probably won’t need an end date. Adding a description of the nature of the test event helps with auditing and review later — i.e. is it a simulation/scenario, is it for training purposes, or just experimentation and testing.
The next step is to join that event and go on duty using the positions that you want for that event. You can use the mobile application for performing tests in the field.
Sandbox Instance
Alternatively, Datalink can create a temporary “sandbox” for your Crisisworks site which is completely independent from your main site. Sandboxes last only for 90 days, but are great for testing ideas that may otherwise mess up your data or impact your users.
Sandboxes are ideal for testing imports or integration, and if you want to redesign your site’s core records such as creating new positions, organisations and the like.
Sandboxes aren’t recommended unless you’re experimenting with Crisisworks in a non-standard way or you’re working with data that is not important and happy for it to be permanently deleted.
With Sandboxes, we can either create a clone of your system or a start with a completely blank system. Having your system clones means you can use your existing configuration and having a blank system means you’ll need to recreate any that you need. Either way, a sandbox is going to require significant time and effort to configure user accounts and positions and mobile devices to ensure that they meet the desired purpose.
With a cloned sandbox you may have the opportunity to remove communication options such as email addresses and phone numbers before testing.
Unlike test events, sandbox environments are time limited and data is deleted after a period of time and is not archived. This helps ensure that security standards are met.
Make sure when requesting a sandbox instance that you let the support team know what you intend to use it for.
Conclusion
Testing in Crisisworks doesn’t have to be daunting, it is designed to be easy for anyone to create and manage testing. For general training purposes, it is recommended to use Test Events. However if you do decide you would like to sandbox, let us know and we can assist you to set one up.