Step 4 of 10

Map Applications to Activities

Created by Jean Baptiste SARRODIE · Dec 17, 2024 · 4 min read
← Step 3: Detailed Process Modeling Step 5: Analyze WC →

Overview

Mapping applications to activities involves identifying the specific applications used in each activity. This mapping helps to understand the application landscape and its relationship to the vital services.

Detailed Application Mapping

The identification of applications supporting activities involves a collaborative effort between process owners, and SMEs such as Enterprise/Functional Architects, Business Analysts, Product Owners and Application Managers.

Each activity is analyzed to determine the applications involved in its execution. This analysis considers:

A diagram, based on the one created previously to document the process, is created to visually depict this mapping.

Golden Source and AUID

The golden source for applications is ServiceNow. Applications are modeled as Application Components with a property named AUID containing the Group unique identifier assigned to the application. The short name declared in ServiceNow is used as the name of the Application Component. Other properties will be later created or updated using a ServiceNow Synchronization Script (when using the modeling tool Archi).

⚠ Modeling rules
  • The golden source for applications is ServiceNow. They are modeled as Application Component with a property named AUID containing the Group unique identifier assigned to the application. The short name declared in ServiceNow is used as the name of the Application Component. Other properties will be later created or updated using a ServiceNow Synchronization Script (when using the modeling tool Archi).
  • Applications are mapped to activities (i.e., Business Functions or Business Processes) by nesting Application Components within the corresponding activities. This nesting represents the serving relationship from the Application Component to the Business Function/Process.
  • Serving relationship from Application Component to the Business Function/Process should have a property named Critical, set as Yes if the application is critical to the execution of the activity, or No otherwise.
  • Applications which are critical to an activity are shown using a different color (e.g. dark blue) than non-critical ones (e.g. light blue). Note that an application can be critical for one activity but not critical for another.

Example: Application Mapping Diagram

The following diagram illustrates how applications are mapped to activities for the Cash Payments - Outgoing process. Dark blue boxes indicate critical applications; light blue boxes indicate non-critical ones.

4. Cash Payments - Outgoing (Nominal Application Mapping)
Example of an application-to-activity mapping diagram
Payment
Instruction Sent
→
?
(manual) (electronic)
Receive Instruction
Assignment / Manual input of payment information
MTM Cerise Hobart
(if SSI issue) ↓
Check Electronic Payment Order
MTM
→
Coherence Checks
GEODE ARPE BP2S AceTP MTM
FXCLEARER SHINE Continuity Actimize (AML) SVR
→
Change
→
Repair of Instruction
/ Release of alert
FCX MTM Actimize Cash Claim Mgmt
←
Payment Release
SIBIS ARPE BP2S PLASMA MTM
→
(compliance alert)
Compliance Alerts
Handling
Actimize (AML)
(reconciliation issue)
Regulatory Reporting
Emission
Financial / Accounting
Positions Update
Accounting
Treasury
→
Billing
→
Archiving
→
Client Reporting
Nominal process activity
Critical Application
Non-critical Application

Footnotes

  1. ServiceNow is the golden source for application data. The AUID is the Group's unique application identifier.
  2. Criticality is activity-specific — an application can be critical for one activity but supporting for another.