ASB Case Studies
The Anti-Social Behaviour System, has quite literally been shaped by our response to our customer's needs. The following Case Studies are some examples of customers who have extended the system by expressing their needs - usually at go-live time.
Victim Support
North Ayrshire Council, in Scotland, have a Victim Support or Home Security team, providing security facilities to the victims of ASB, DV etc. The benefit of integration with Caseworks was obvious, but the data requirements and functions were completely different. Furthermore, whilst many of the Clients where Victims of ASB, many had been referred from other sources and were not being managed by the ASB Unit. This requirement, led to the development of the Caseworks Modular structure, in which a separate module, with a separate User List, could have different functionality and yet share Persons and Properties, where these were common to the two systems.
Case Audit
Solihull AMB, in the midlands, had a Quality Assurance office, who audited cases before they were completed, to review progress and make recommendations. The requirement was, that the page could only be created and updated by a senior officer, but would be viewable by the Caseworkers and would list in the Case Load, to show a case most recently updated by another officer.
Incident Diary
Sefton Council in Liverpool, expressed a need, since taken up and extended by others, to have the facility to enter many incidents in one go, in the format in which they were often notified - as a victim's incident diary. This led to the development of the screen with the most fields of any Caseworks Page - 50 rows and 6 columns of incident details. It takes a short time to load and save data, but in a minute can save nearly an hour of data entry if every incident had been entered separately. Subsequent upgrades, have permitted start and end times, and automatically "copied down" common details from rows above.
Panel Meetings
Surrey Police operate on a multi-agency basis through a structure of Panel Meetings. These collect Persons and Incidents for consideration on a monthly cycle. We added Panel Submission records and Panel Meeting records to the system to meet this need. Actions decided in the Panel Meetings, are logged to the submissions, and automatically create actions in the relevant case. These actions are asigned to the relevant officer for action.
EMail Alerts
Riverside RSL is an extremely diverse organisation, with a Call Centre at its hub, collecting the bulk of complaints of ASB from its customers. The Case Transfer system in Caseworks, was not going to be full proof for the Call Centre to notify the Local Offices, as it depended on the right user being available locally, and conscientiously logging in twice per day. We developed an email Alert System, which not only alerts the user to a Transfer Alert, but (optionally) copies the email to another email account - which for Riverside is a shared account.
The Anti-Social Behaviour System, has quite literally been shaped by our response to our customer's needs. The following Case Studies are some examples of customers who have extended the system by expressing their needs - usually at go-live time.
Victim Support
North Ayrshire Council, in Scotland, have a Victim Support or Home Security team, providing security facilities to the victims of ASB, DV etc. The benefit of integration with Caseworks was obvious, but the data requirements and functions were completely different. Furthermore, whilst many of the Clients where Victims of ASB, many had been referred from other sources and were not being managed by the ASB Unit. This requirement, led to the development of the Caseworks Modular structure, in which a separate module, with a separate User List, could have different functionality and yet share Persons and Properties, where these were common to the two systems.
Case Audit
Solihull AMB, in the midlands, had a Quality Assurance office, who audited cases before they were completed, to review progress and make recommendations. The requirement was, that the page could only be created and updated by a senior officer, but would be viewable by the Caseworkers and would list in the Case Load, to show a case most recently updated by another officer.
Incident Diary
Sefton Council in Liverpool, expressed a need, since taken up and extended by others, to have the facility to enter many incidents in one go, in the format in which they were often notified - as a victim's incident diary. This led to the development of the screen with the most fields of any Caseworks Page - 50 rows and 6 columns of incident details. It takes a short time to load and save data, but in a minute can save nearly an hour of data entry if every incident had been entered separately. Subsequent upgrades, have permitted start and end times, and automatically "copied down" common details from rows above.
Panel Meetings
Surrey Police operate on a multi-agency basis through a structure of Panel Meetings. These collect Persons and Incidents for consideration on a monthly cycle. We added Panel Submission records and Panel Meeting records to the system to meet this need. Actions decided in the Panel Meetings, are logged to the submissions, and automatically create actions in the relevant case. These actions are asigned to the relevant officer for action.
EMail Alerts
Riverside RSL is an extremely diverse organisation, with a Call Centre at its hub, collecting the bulk of complaints of ASB from its customers. The Case Transfer system in Caseworks, was not going to be full proof for the Call Centre to notify the Local Offices, as it depended on the right user being available locally, and conscientiously logging in twice per day. We developed an email Alert System, which not only alerts the user to a Transfer Alert, but (optionally) copies the email to another email account - which for Riverside is a shared account.
