Skip to end of metadata
Go to start of metadata

The Investigative Case Management ES bundle allows the integration of SAP and third-party applications to facilitate the investigation process of police departments, fire departments, secret service agencies, or other similar customers who have to deal with intelligence-led processes in the course of their duties as law-enforcement or public-security entities. Examples are the usage of geographical maps and spider diagrams for the analysis of relationships, the verification of persons' identities with plausibility checks, efficient document and form handling, and data exchange with applications like shift planning and logistics.

The business partners referred to in the Investigative Claims Management bundle are not what are typically thought of as business partners in other ES bundles. In this bundle, business partner refers to one of the following types of people:

  • A victim
  • A witness
  • A suspect
  • A lawyer

Please note that Investigative Case Management is available as a complete solution within SAP Business Suite 7. The enterprise services in this ES bundle provide some of the integration within that solution and can also be reused in order to integrate that solution with additional third-party software relevant for your environment and use cases.

Audience

The target audience for the Investigative Case Management ES bundle includes law enforcement personnel such as detectives, public security officials, secret service agents, investigators in fire departments, and personnel who have to investigate cases in other public safety organizations that deal with law enforcement, emergency, or disaster relief management.

For details on Service Operations, Business Objects and Process Components, please check the ES Workplace.


How To Use This ES Bundle

In the past, when law enforcement personnel dealing with various cases had to work with the different types of information involved in those cases, such as locations of possible suspects or witnesses in a crime, a manual transfer of the data from one application to another had to take place. This manual transfer of data would most likely have been done in the form of transferring information such as an address to a map viewer or descriptive information to a verification map.

With the services in this ES bundle, these kinds of transfers can be triggered automatically, as described in the use cases below. This streamlining of data transfer not only provides cost savings, in that it will allow for faster and easier integration to third-party applications, but it also improves efficiency by accelerating the processes involved in investigations.

This section explores a series of use cases for the Investigative Claims Management ES bundle. Each use case shows how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate a few of the ways that this ES bundle could be used, the intention is to show the flexibility and reusability of these business objects and enterprise service operations so that you will have a clearer understanding of how to best deploy them in your own environment. This wiki is also a space for you to share knowledge and collaborate with others who are implementing the Investigative Claims Management ES bundle.

Note that the following use cases may refer to users directly invoking enterprise services. Services are triggered by a user interface element, a composite application, or through application-to-application communication. The use cases are meant to illustrate possible flows of services to achieve a particular end and are not meant to be taken literally in terms of user interaction. To see the services in action, please visit this video presentation on SAP TV.

Use Case 1: Business Partner Selection on Map

In this first use case, let's consider a scenario in which a murder has taken place in a major city. After police detectives have finished interviewing people from the neighborhood in order to gather intelligence in hopes of finding a suspect, a name is gleaned from several potential witnesses.

After filing the initial reports back at the precinct, the lead detective on the case, searches for the suspect using either SAP Investigative Case Management or a composite application, which invokes Find Business Partner by Basic Data enterprise service.

The detective then selects names that match the search criteria, which repeatedly invokes the Read Business Partner Basic Data enterprise service. The system then transfers the potential addresses for the suspect to a Geographic Information System (GIS). No enterprise service is invoked at this point.

The GIS then displays the "hits" or possible matches as markers on a map by using the main addresses for each business partner with this name. As in the previous step, no enterprise service is invoked. The detective then selects one of the markers, which invokes the Read Business Partner Basic Data enterprise service that in turn retrieves the detailed data for the selected business partner. Finally, if needed, the detective can modify and save the data, updating the address if it is known to be incorrect for example. The service called to perform the change is Change Business Partner Basic Data.

Step

Enterprise Service Invoked

Step 1: Search for a suspect by name

Find Business Partner by Basic Data

Step 2: Read information for all suspects by that name

Read Business Partner Basic Data

Step 3: Transfer addresses to a GIS (geographical information system), which maps the addresses of the selected potential suspects

(No enterprise service is invoked during this step)

Step 4: Select one of the business partners on map

Read Business Partner Basic Data

Step 5: If appropriate, change data of business partner

Change Business Partner Basic Data

Use Case 2: Intelligence Check of Business Partner Data

One major problem in the field is duplication of data. Police enter a new business partner into the system in a variety of context, but have no time to check for duplicates or ensure greater quality in their entries because of the circumstances under which the data is entered.

This use case illustrates how to serve both needs of the organization---speed for those in operational roles and quality in information captured.

The police officer stops a person on a routine traffic stop and searches based on the information provided by the driver, which invokes the Find Business Partner by Basic Data service. The search provides no results, so the police officer creates a new business partner, which invokes the Create Business Partner Basic Data enterprise service operation.

Meanwhile, in the backend system, another search is run, referred to as a doublet check. This search uses fuzzier criteria, looking for suspect names with a similar spelling, for example. When this doublet check is run, the Find Business Partner by Basic Data is invoked. If a possible duplication is found, the Create Activity enterprise service is invoked, creating an activity directed at the data quality manager in charge of resolving possible duplicate business partners.

When the data quality manager logs on, she sees the new activity. She investigates further to see if these are duplicate entries. And in this case they are duplicates. The data quality manager indicates this in her notes and saves them, which invokes the Change Activity enterprise service operation as well as the Change Business Partner Basic Data enterprise service operation to merge the two entries.

Step

Enterprise Service Invoked

Step 1: Police officer quickly searches for a person

Find Business Partner by Basic Data

Step 2: If no exact match, the police officer enters a new business partner in the system

Create Business Partner Basic Data

Step 3: The application runs a doublet check in the background and if a doublet is found, creates an activity for the data quality manager to resolve the duplication

Find Business Partner by Basic Data
Create Activity

Step 4: The data quality manager reviews the duplication and resolves it

Change Activity

Step 5: The data quality manager merges the doublets if needed

Change Business Partner Basic Data

Future Directions

Future directions for this ES bundle will be market-driven.

System Requirements

  • SAP CRM 7.0, with SAP Investigative Case Management enabled

Related ES Bundles