Investigative Case Management Prototype xCelerator


Welcome to the Investigative Case Management (ICM) Prototype xCelerator.  This xCelerator demonstrates how xCP can be used to build a solution that will handle the complex requirements around Investigative Case Management, handling the investigation of a case through its entire lifecycle.  Although only a prototype system many basic design principles and solution patterns have been used that can be implemented in any xCP solution.


The solution has been built on xCP 1.5 and utilises the following components:

    • xCP 1.5 including Business Activity Monitor
    • Document Science xPression
    • Corticon (optional)
    • Captiva
    • Federated Search Services
    • Advanced Search xCelerator


The scenario supported directly is that of a burglary, going from the recording of the incident in the ICM system, through to the arrest of a suspect and the request for advice from the court before charging the suspect with the crime.  It is worth noting that other scenarios could be demonstrated with minimal additional configuration.


Highlights of the xCelerator

    • Configurable case templates
    • Flexible tasking: single user, single user from group, work queue - push and pull and ad-hoc tasks
    • Google Maps integration
    • Dynamic Hi-Fidelity form generation
    • Correspondence generation using Document Science xPression
    • Calendar event management: automatic creation of events such as task due dates, milestones and peoples availability
    • Business logs: human readable audit trail (readonly) and editable log files for notes and contact with people
    • Integration with business rules engine
    • Integration with external systems: dispatch record system and HR absence notification
    • Automatic ingestion into cases via FTP import
    • Video support in TaskSpace
    • Collaboration via CenterStage
    • Collaboration via eMail




Download Link
ICM Prototype Installation PackageICM Deployment
ICM Prototype Deployment GuideDeploying ICM Prototype 1.0.pdf
ICM Prototype Technical Design DocumentICM Prototype Technical Design 1.0.pdf
ICM Prototype Overview PresentationxCelerator Presentation.pdf
ICM Prototype Video Download

ICM Prototype Screencams

ICM Prototype Screencams

ICM Prototype Annotated Screencams


ICM Prototype Annotated Screencams


Demonstration Video

The video is broken up into meaningful sections based on which user conducts each task for easy navigation.  Each section is available online as a full-screen video, and as an annotated video.  The entire set of video files can also be downloaded for use offline, and the annotated version is encoded for use on mobile devices such as the iPhone, for use as an aid memoire alongside a live system while working with it.


The key actors/roles, and the name of the corresponding test users are as follows.


    • Police officer – Brown, Addah
    • Police officer supervisor - Smith
    • Screening officer - George
    • Investigating officer – Street, Ford, Austin
    • Investigating officers supervisor - Patel
    • Victim support unit – Tims
    • Evidentiary review officer – Judge


As well as system users, the court actor/role is represented by a user with an email address of  The user for CenterStage is dmadmin.


The main stages of the scenario are as follows.



    • Recording an incident
    • Review of the incident by the recording officers supervisor
    • Screening (decision to investigate further or not)
    • Assignment of crime investigation to an investigating officer
    • Investigation of the crime
    • Request for pre-charge advice from the court


In addition to these, the following use cases are also supported


    • Creation and handling of an ad-hoc task (also called a Memo)
    • Notification to the Victim Support team than a new victim requires follow-up
    • Generation of dynamic correspondence using xPression
    • Notification of officers long-term absence from an external system and subsequent reassignment of tasks


1 Record Incident - Brown

Officer Brown records a new incident and adds all of the required case artifacts before sending it to his supervisor for review.  The case is created from a template and contains default artifacts such as a business log, case summary (showing Google Maps) and milestone calendar event.  A photo of the victim is uploaded and a pre-populated Hi-Fidelity form generated for the witness statement.




2 Review Incident - Smith

Officer  Smith reviews the incident, checking that the victim information is present and whether the forensic report and witness statement have been  generated and completed.  Officer Smith decides that further work is needed before the process can continue and so tasks Officer Addah with following up the work.



3 Revise Incident - Addah

Officer Addah receives two tasks.  The first is to get the witness statement completed.  The High Fidelity form can be edited online, printed off for  signature by the witness, and then scanned back into the system.  Because the form has a barcode with the case reference it could be automatically reconciled to the case.  The second task is to check that the forensic officer will get their report completed.



4 Approve Incident - Smith

Officer Smith reviews the incident after it has been revised.  The Action Log shows that the forensic officer will be completing their report on time and so Officer Smith sends the incident for screening (a decision as to whether the incident will be investigated as a crime or not).  Finally Officer Smith checks the Management dashboard.



5 Complete Forensic Report - Sherlock

Officer Sherlock receives an ad-hoc task (also called a Memo) to complete the forensic report for the incident.  The report is edited and the task completed, but before completion Office Sherlock remembers that he saw a similar case recently and adds a note to that effect.  This allows an officer to locate the similar case and relate it later on.



6 Screening - George

The task is assigned to a team.  Officer George accepts the task and screens the case with a wizard style interface.  Screening is the process of deciding if an incident becomes a crime that is investigated further, and there are many factors which affect the decision.  A rules engine (Corticon) provides a suggested screening decision, and a link to external help allows Officer George to confirm it.



7 Assign Investigator - Patel

Officer Patel manages a team of investigating officers and so that task enters his queue, ready for assignment.  Skill set filtering warns that the selected officer does not have the required experience, but Officer Patel continues with the assignment.



8 Accept Case - Street

Officer Street accepts the task of investigating the crime and creates an investigation plan.  The investigation notes are updated, the related crime is linked to the case and some CCTV footage is uploaded to the  case and viewed through TaskSpace.



9 Monitor Case - Patel

As the supervising officer, Patel needs to review the case every 7 days and so the system sends him an iCal object by email that he can add to his normal calendar tool.  The system also emails him if the review is overdue.  Finally, Officer Ford notifies him via an external HR system that he will be unavailable for duty and so Patel reassigns Officer Ford's cases.



10 Victim Support - Tims

Officer Tims is a Victim Support officer.  This team have a simpler view of the system and can only get the next task from a shared queue.  Officer Tims adds a discussion comment to the case and generates a personalised letter to the victim using xPression.



11 Submit to Court - Street

Once a suspect is arrested, a court file is created from case artifacts, and a new court summary document is created.  The court is asked for advice before proceeding with the charging of the suspect with the crime, demonstrating collaboration with external parties by ftp, email and collaboration tools such as CenterStage.