Enterprise Architecture supported by BPMS case tool

Today we are overwhelmed with information.

The challenge is to capture, to manage, to steer upon this information from many points of view.

Information arises by triggers, business stakeholders, IT delivery teams, external / internal representatives, etc.

This information continuously is in motion.

What are the triggers ?

In order to manage the impact we need an agile instrument to steer upon.

What is a bpms ?

•Is a software tool (on prem / saas)

•Helps your organization improve your business processes with the help of analysis and automation

•Supports you in the BUILD phase to let you model solutions (design-transition)

•Supports you in the RUN phase to manage solutions (collect data and analytics)

•Uses visual modeling techniques

•Is more than diagramming

•Is more than a process diagram

•Is more than (static) documenting

•Supports various stakeholders : business, IT, other value stream responsibles

What are the components of a BPMS?

•A repository (*) fully structured

•An engine (*) respecting ruling, standards

•A set of frameworks (*)

oITSM/ITIL

oAPQC / SCOR / APIC

oPRINCE2 / PMBOK / Scrum / Agile

oTOGAF

•A reporting engine (*) • •

(*) standard and customisable

What are the benefits / cost drivers of a BPMS?

•Risk reduction

•Better organisational control

•Optimised processes (M2M)

•Increased agility (impact analysis)

•Improved collaboration (integrated knowledge sharing)

•Workflow automation (RPA)

•Ensured compliance (standard rules)

•Overview of organisational goals

•Employee happiness

•Single Point Of Truth centric

A journey of modeling

Step1: we gather information to drive / improve our business

Step2: we classify, we design solutions

Step3: we deliver products & services to our stakeholders & customers

Every step in this lifecycle is supported by BPMS.

Detail explanation

Step 1: gathering information

goal: structure the information gathered

Step 2: build the enterprise architecture

Step 3: challenge the stakeholders (internal / external)

Active Structure : to represent subjects that display actual behavior (who, actors, users).

Behavior Structure : to represent behaviors of active structures (how, processes, procedures, actions)

Passive Structure : to represent the objects behavior is performed on (what, tooling, deliverables)

To model this vast flow of information we need at least a digital repository able to be “aware” of impacts if we change the major horizontal layers (strategy, business processes, application functionalities, technology stack, physical organisation, …)

A BPMS case tool provides the tools to manage this kind of knowledge end 2 end.

Quick overview of the objectives.

•The objective is to facilitate the discovery of information needs within the enterprise.

•Along the journey of a project implementation (IT or Business) we need to understand the lifecycle of a project, of a product.

•Then to re-use artefacts documented during each phase of a project.

Example: suppose we use the following lifecycle:

Every phase of a project makes available new information (not exhaustive):

•Ideations : write the epics, the story boards, the uses cases, plan the roadmap, clarify the workload, business case, benefits

•Design : setup the Business logics (process / organisation), describe the Information exchange (how & when sequencing), design the Architecture & infrastructure artefacts, integrate the Data model

•Implementation : orchestrate the Deployment artefacts, manage Release artefacts, Sprints artefacts, •Quality & assurance

•Go Live : Perform Transitions

Along this path we use for instance the agile / scrum framework