Enterprise Content and Business Process ManagementDeveloping an ECM and BPM IT architecture

Feb 2008

What Drives CM and BPM?Business drives ITBusiness requirements dictate the

architecturesWe must understand the business

requirements before proposing solutionsThe business must have a strategic visionWe in IT must work with the business to

develop the architectures needed to implement the strategic vision of the business

The ArchitecturesData or information architectureApplication architectureInfrastructure and StandardsBusiness process architecture (tasks)

Data ArchitectureThe data flow architecture is comprised of 4

major piecesInputsContent and metadata storageBusiness processesOutputs

The business requirements drive the dataflow architecture

Data Architecture

Inputs

ScanFax

Desktop appsEmailforms

Stored in repositori

es

Content , data and

metadata

storage

Content triggers business

processes

Business

Processes

Meet SLAs,

compliance,

customer service

Business Processproduce output

Outputs

Documents,

historical data, web services, business

informatio

n

Data ArchitectureEveryone has multiple repositories

data, metadata and contentWe need to federate content repositoriesWe need real-time access to data and metadata

repositoriesThe strategic plan must consider performance (e.g.

document retrieval using cache services)Physical architecture is driven by

GeographyVolumePerformance requirementsBusiness requirements

Physical ArchitectureBringing together all the physical hardwareCapture, Image Services, Content Engine,

Process Engine, Application Engine, Cache Server, Web Server, Database Server, Directory Server, Messaging Server, Reporting Engine, Rules Engine

Application ArchitectureJ2EE assumedFrameworks (e.g. BPF)Multi-tier model (client, web, business, EIS)Components (e.g. JSPs, servlets, portlets,

EJBs)Data interfaces (JDBC, JMS, APIs)Web servicesLegacy interfacesUser authentication and authorization

(security)

Application ArchitectureAll applications have some level of

requirement for:AuthenticationAuthorizationAuditingLoggingStatisticsError handling

These can be built into the architecture

Business Process ArchitectureAll applications are not the sameCategorize the applications in the strategic

planInternal documents (e.g. quarterly reports)“One and done” applications (e.g. service

documents)Case management applications (e.g.

underwriting)

Creating the ArchitectureConnect architecture to the businessAnalyze the business current stateConstruct the business target stateAnalyze the business target state and identify

gaps and opportunitiesCreate an architecture model (a graphical

representation of the business view of the data)

Translating Architecture to ProjectsCommon mistakes

Attempt to implement too much, too quicklyInability to tie implementation to business

successUnderestimation of resistance to changeNo commitment or buy-in from the entire

organizationLack of supporting enterprise-wide processesInsufficient focus on the people issues

Translating Architecture to ProjectsIdentify candidate projects (translate the

architecture into business-focus projects)Select/prioritize key projectsNarrow the scope of selected projects

Implementing the ArchitectureEstablish Metrics

Measure architecture effectivenessSet business objectivesSet project objectivesSet architecture objectives

Gaining supportGaining executive support

Summarize the business needs/opportunities/gaps

Construct a presentation level modelDevelop a brief proposal for the project(s)Develop a one-page bottom line

Gaining IT supportDiscuss early versionsSolicit inputRequest volunteers to review the architecture

SummaryDeveloping the CM/BPM architecture

requires viewing the enterprise from many angles

The architecture must meet the business requirements

The architecture integrates content with business process

The architecture must provide benefits to the business