Information management

24
Information Management We are all trying to do this

description

Example of combining methodologies to architect a complex IT solution.

Transcript of Information management

Page 1: Information management

Information ManagementWe are all trying to do this

Page 2: Information management

Information ManagementAIIM has a nice layman’s definition

CaptureStoreManagePreserveDeliver

This happens when we are talking and listening or when we are trying to manage Petabytes

There is a lot more behind the next slide

Page 4: Information management

Cloud Platform (thank you Gartner)Turnkey Service (sounds like SOA)Elastic (scalable)Shared Environment (multi-tenant)Pay for what you use (have to track usage

stats)Use standard protocols (HTTP/HTTPS)Like an electric utility, just use it and pay the

bill

Page 5: Information management

3 Levels of Cloud ServiceIAAS

Bare-bones VM capacityPAAS

Software development tools to create and run applications

SAASOut-of-the-box software solutions accessed

through a front-end portal

Page 6: Information management

Cloud TypesPublic cloud

Resource dynamically provisioned on a self-serve basis via the web from an off-site 3rd party provider who shares resources and bills clients

Private cloudInstallations that emulate many aspects of

public cloud computing but do so on a completely secure private network

Hybrid cloudSome resource in-house and others managed

externally

Page 7: Information management

IBM View Example

Page 8: Information management

IBM Smart Analytics Cloud

Page 9: Information management

Enterprise Services “Enterprise services architecture emphasizes abstraction and

componentization, which provides a mechanism for employing both the required internal and external business standards. The main goal of enterprise services architecture is to create an IT environment in which standardized components can aggregate and work together to reduce complexity. To create reusable and useful components, it is equally important to build an infrastructure allowing components to conform to the changing needs of the environment.” - Techopedia

In other words, “loosely coupled” services that perform specific tasks, can be easily inserted, updated or replaced

The services may be “course-grained” or “fine-grained”. Course-grained is what the business sees, fine-grained can be reused by the course-grained.

Page 10: Information management

Enterprise ArchitectureMaturity Model4 stages

Application siloStandardized

TechnologyRationalized DataModular

From MIT Sloan School of Management Center for Information Systems Research

Page 11: Information management

From MIT Sloan School of Management Center for Information Systems Research

Page 12: Information management

Business Operating Models

From MIT Sloan School of Management Center for Information Systems Research

Page 13: Information management

SOA Governance Example

Page 14: Information management

Implementing Enterprise ServicesImplementing enterprise services starts not

with technology but with the business requirements.

What enterprise services does the business need?ReportingAnalyticsProcess managementPredictive analyticsMessaging and routing Data translation

Page 15: Information management

Example Hadoop + Analytics

Page 16: Information management

Defining ArchitecturesNetworkServerApplicationDataTransformationSecurityEvent and event handlingESB and adapters

Page 17: Information management

Business and Ops SupportPlan for support of multi-tenant environment

Tools to capture usage statisticsPlan for proactive operational support

Tools for monitoring all aspects of the solution

Page 18: Information management
Page 19: Information management

MethodologyTwo Paths in Parallel

Business Gather high-level requirements

Functional Non functional

Technical Identify technology platforms and components Design architectures Design end-to-end proof-of-concept

Crawl, walk, run

Page 20: Information management

MethodologyArchitectural blueprinting

Work in progress through project phasesDefine a multi-phase project management

strategyLook for small wins first

Page 21: Information management

Architecture BlueprintsGraphical representation of the business view

of data, functions, technology, people and the relationship and/or interactions between them

Set the contextSet ground rules for modelingDetermine modeling levels of detail

Page 22: Information management

Architecture Blueprints – Set the contextWho is the audience?What level of detail do they need to see?What will the content include?

Data, functions, technology, people?Communications layers?Sequence, flow?

What planning horizon will be used?What part of IT does the architecture need to

describe?

Page 23: Information management

Architecture Blueprints – Ground RulesAgree on a set of standard componentsUse a standard representation schemeSet a scopeDetermine the level of detail

Level 0 – conceptual, one pageLevel 1 – More detailed, specificLevel N – Most detailed, form the bridge from

architecture to developmentDefine the state to be modeled (current, target)Define the environment (prod, dev, ops)

Page 24: Information management

Project SummaryCapture data from many sources in many

formatsRoute data to data warehouse using ESBUtilize Analytics and/or BI platform on data