Business Impact Analysis Use Case Design

This topic explains the Business Impact Analysis use case design.

Architecture Diagram

The following diagram shows the relationships between the applications that make up the Business Impact Analysis use case.

Download the source file of the diagram here: Business Impact Analysis Architecture Diagram

Business Impact Analysis use case architecture

Applications

The following table describes the use case applications.

Application

Description

Business Processes

The Business Processes application captures the base data for a given process. A process may be assigned to a particular business unit or shared across multiple business units. A business process may also be referenced to one or multiple products or services. The application enables you to track the business processes personnel, criticality, recovery time objective (RTO) and ITIL category, and associate it with other aspects of the enterprise infrastructure.

Note: The Business Processes application is included in the Enterprise Catalog package.

BIA Campaign

The BIA Campaign application creates new Business Impact Analysis records based on the selected scoping methodology as well as links existing BIA records discovered during the campaign.

Business Impact Analysis

The Business Impact Analysis (BIA) application enables organizations to inventory their business processes or products and services, as well as their dependencies (people, processes, technologies, and third parties). A BIA should be completed for each product and service, or for each business process, depending on the methodology used by the organization.

Use the BIA application to do the following:

  • Apply decision criteria to help organizations determine the criticality for each product or service.

  • Determine criticality at the business process level using a traditional business continuity approach.

BIA Archive

The BIA Archive application stores a copy of each completed and approved BIA and associates that archived copy to the BIA records.

Impact Tolerances

The Impact Tolerances application enables organizations to define the maximum tolerable period of disruption to important products and services or business processes. It identifies the type of impact, such as harm to consumers, market integrity, market participants, threat to financial stability, policyholder protection, and safety and soundness. Impact tolerances must always be expressed as a unit of time - hours, days, or weeks, but can also include other metrics such as financial loss, impact to reputation, regulatory impact, and consumer impact. Impact tolerances can also be defined over time to identify the resilience during each time period.

Company

The Company application stores general, financial, and compliance information at the company level. Combined with the Division and Business Unit applications, this application supports roll-up reporting of governance, risk, and compliance initiatives across the enterprise.

Note: The Company application is included in the Enterprise Catalog package.

Business Unit

The Business Unit application provides a detailed view of all activities related to the specific business unit.

Note: The Business Unit application is included in the Enterprise Catalog package.

Division

The Division application represents the intermediate unit within the business hierarchy which is a layer below the high-level company and a layer above the individual business unit. You can use this application to further document the relationships within your business and measure the effectiveness and compliance of individual divisions within the enterprise.

Note: The Division application is included in the Enterprise Catalog package.

Products and Services

The Products and Services application maintains all products and services provided within an organization. For example, a financial services firm provides a variety of products and services, such as banking, brokerage, and lending services.

Note: The Products and Services application is included in the Enterprise Catalog package.

Contacts

The Contacts application serves as a central repository for contact information, is utilized across multiple areas of Archer, and contains information that is often leveraged by other use cases. Updates to a profile record within this application automatically propagate in any records with displayed contact information.

Note: The Contacts application is included in the Enterprise Catalog package.

Use Case Dashboard

The following table describes the use case dashboards.

Dashboard

Description

BR Task Driver

The BR Task Driver dashboard contains quick links for frequent tasks and features metrics specific to the current user, such as BIAs pending my action, past due BCDR Plans, and active Incidents.

BR Process Manager

The BR Process Manager dashboard displays items relevant to Business Process Owners and Program leads. Charts are designed to help leads monitor how processes are functioning and identify gaps. The dashboard features metrics, such as expired BIAs and BCDR plans, BIA RTOs and RPOs, and the dependency mapping status by business unit.

BR Management

The BR Management dashboard provides critical information to help the management understand the resilience of business units. The dashboard uses interactive charts to display data, such as incidents by business unit, products and services by category, and BIAs by criticality rating.

Access Roles

The following table describes the available access roles within the Business Impact Analysis use case and any related permissions that the role requires.

Role

Description

BIA: BCM Program Lead

  • Creates BIAs campaigns for all business processes in organization, runs BIA campaigns, and initiates advanced workflows.
  • Approves or rejects BIAs.

BIA: Participant

  • Owns business processes that must undergo a BIA.
  • Reports to Business Unit Leader.
  • Can complete their assigned questions on the BIA.
  • Can approve or reject the completed BIA after the Controller and Compliance Manger responds to and submits their part of the of BIA.
  • Can view the status of all BIAs for their respective business processes.
  • Responds to questions in the Strategic, Operational, Reputation, Information Confidentiality, and Information Integrity sections of the BIA.

Personas

The following table describes the use case personas.

Access Role

Persona

Description

BIA: BCM Program Lead

BCM Program reviewer

  • Can create BIA Campaign and initiate advanced workflow.
  • Can approve or reject completed BIAs that have been approved by the BUM.

BIA: Participant access role

Business Process Manager

Can create BIAs for business processes that they own and initiate workflow on their BIAs.

BIA: Participant

Controller

  • Can complete the Finance section of the BIA.
  • Can select cross-references in the Financial Impact Category.
  • Can submit BIAs.

BIA: Participant

Compliance Manger

  • Can complete Compliance-related questions on the BIA and submit the BIA.
  • Can select cross-references in the Compliance Impact Category.

BIA: Participant

Business Unit Manager (BUM)

  • Reviews completed BIA.
  • Can approve or reject a completed BIA or multiple BIAs that have been approved by the BPM.
  • Can see the status of all the BIAs for the business processes in their Business Unit.

Data Feeds

The following table describes the data feeds. For instructions on setting up the feeds, see Setting Up BIA Data Feeds.

Data Feed

Description

BIA Campaign JS Data Feed

The BIA Campaign JS data feed is a Java script transporter data feed that automates the creation of Business Impact Analysis records based on the selected scoping methodology and target records. The scoping method can be a Business Process, Business Unit or Products and Services. Depending on the selected scoping methodology, the data feed generates Business Impact Analysis (BIA) records for the following:

  • On business process scoping, 1 BIA record is created for each selected business process record.

  • On products and services scoping, 1 BIA record is created for each selected products and services record.

  • On business unit scoping, BIA's are created either for business processes or products and services related to the selected business unit.

For more information on the JavaScript data feed, see Configuring the JavaScript Transporter Settings.

Business Impact Analysis – Business Process Copy Feed

The Business Impact Analysis – Business Process Copy Feed is a Web Services Transporter feed that copies the supporting infrastructure from the evaluated business processes into the Business Impact Analysis application. The supporting infrastructure includes child processes, products and services, business unit, information assets, risks, contacts, facilities, devices, applications, third party profiles, engagements, and subcontractors. It copies Third Parties, Engagements, Subcontractors, Stakeholders (Contacts), Facilities, Devices, Information Assets, Qualitative Risks, Quantitative Risks and Applications from the Business Process into the related BIA.

Once a BIA record is enrolled into the advanced workflow, the value of the DFM: BP/PS copy field is set to Yes, which initiates the data feed. The data feed leverages the DFM_Copy Content From BP To BIA report contained in the Business Impact Analysis application.

Business Impact Analysis – Product and Services Copy Feed

The Business Impact Analysis – Products and Services Copy Feed is a Web Services Transporter feed that copies the supporting infrastructure from the evaluated product and service into the Business Impact Analysis application. The supporting infrastructure includes child products and services, business processes, third parties, facilities, contacts, devices, applications, information assets, risks, engagements, and subcontractors.

Once a BIA record is enrolled into an advanced workflow, the value of the DFM: BP/PS copy field is set to Yes, which initiates the data feed. The data feed leverages the DFM_Copy Content From P&S To BIA report contained in the Business Impact Analysis application.

Copy BIA Supporting Infrastructure to Business Process Feed

Business Process Copy Feed is a Web Services Transporter feed that copies the supporting infrastructure from the evaluated business processes into the Business Impact Analysis application. The supporting infrastructure includes child processes, products and services, business unit, information assets, G/L accounts, and loss events.

Once a BIA record is enrolled into the advanced workflow, the value of the DFM: BP/PS copy field is set to Yes, which initiates the data feed. The data feed leverages the DFM_Copy Content From BP To BIA report contained in the Business Impact Analysis application.

Copy BIA Supporting Infrastructure to Products/Services Feed

The Copy BIA Supporting Infrastructure to Products or Services Feed is a Web Services Transporter feed that copies the supporting infrastructure from the product and service being evaluated as part of a Business Impact Analysis into the corresponding Product and Service record. The supporting infrastructure includes child products and services, business processes, third parties, facilities, contacts, devices, applications, information assets, risks, engagements, and subcontractors.

Once the BIA is approved by the Product and Service Owner, the data feed runs to copy the supporting infrastructure.

Business Impact Analysis – Archive Feed

The Business Impact Analysis – Archive Feed is a Web Services Transporter feed that copies approved Business Impact Analysis records into the BIA Archive application. This preserves historical information such as criticality, RTO/RPO, participants, and responses that may be altered over time in the original record.

Once a BIA record is approved, the value of the DFM: Archive Flag field is set to Yes, which initiates the data feed. The data feed leverages the DFM Archive report contained in the Business Impact Analysis application.