Basic Enterprise Architecture Methodology (BEAM)

1

One WorldInformation

System


System

Basic Enterprise Architecture Methodology

(BEAM)Http://one-world-is.com/beam

Roy Roebuck(703) 598-2351

[email protected] World Information System (OWIS)

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California

94305, USA. Noncommercial use and extension of BEAM is allowed as described in this Creative Commons license.

Commercial use of BEAM requires purchase of one or more types of low-cost BEAM Licenses for Service Provider, and Value-Added Reseller (VAR) BEAM use. BEAM licenses are available from One World Information System as indicated on a subsequent page of this

presentation.

2/19/2004 5:17 PM

The Basic Enterprise Architecture Methodology (BEAM) is a public-licensable subset of the General Enterprise Management (GEM) methodology of One World Information System.

What is the General Enterprise Management (GEM) methodology? GEM provides an integrated and continuously evolving “Table of Contents” and “Index” to your enterprise, as it is, was, and is intended to be. BEAM builds this enterprise Table of Contents and Index, and helps establish the GEM mechanisms which integrate them, use them for security management, expertise management, and situational awareness, and keep them up to date.

Why use GEM? How many organizational Executives, Senior Managers, Managers, Workers, Staff, etc., wouldn’t like the right information they need to do their jobs well and make good decisions, to be provided to them in the way it is need, when it is needed. GEM can help your enterprise, whether Government, Commercial, Non-Profit, Community, or Individual, to attain just that capability.

BEAM is a detailed procedure for defining an enterprise architecture that is intended to be conformant with the evolving U.S. Federal Enterprise Architecture (FEA) being defined by the FEA Program Management Office (PMO) of the U.S. Office of Management and Budget (OMB). BEAM predates and is a superset of the popular Zachman Framework for EA, the Spewak EA Planning methodology, and the DoD Architecture Framework. BEAM is intended to provide the foundation for full enterprise management, leveraging the BEAM extension of typical EA structure and content as the start point of an enterprise knowledge base.

BEAM supports ISO 9000 Quality efforts in the enterprise, along with other “maturity” efforts such as the five maturity levels of Software Engineering Institute’s Software, System, Acquisition and other Capability Maturity Model (CMM) and CMM-Integrated (CMMI) efforts. BEAM specifically supports the ISO 9000 – Eight Quality Management Principles:

1. Customer Focus2. Leadership3. Involvement of People4. Process Approach5. System Approach to Management6. Continual Improvement7. Factual Approach to Decision Making8. Mutually Beneficial Supplier Relationships

Training and support on BEAM is available from One World Information System (OWIS) and licensed GEM Service Providers.

2

2/19/2004 This Work Is Provided Under The Creative Commons Attribution-NonCommercial-ShareAlike License of Roy Roebuck, 1982-2003. http://one-world-is.com/beam

2


System


SystemPresentation Outline1. BEAM Concepts2. Executive Overview

What are BEAM, GEM, and EMM and why are they valuable? GEM Facts/History and Claimed BenefitsWhat are the costs of BEAM?

3. Technical OverviewWhat is the BEAM process?

4. BEAM Procedures5. Standards/Technology Supporting BEAM6. Products Supporting BEAM7. BEAM Implementation Project Plan Samples8. BEAM Solution Scenarios9. Summary

3


System


System

1. BEAM Concepts

4


4


System


SystemBEAM Glossary• Enterprise: A purposeful (i.e., goal seeking) endeavor.

• Architecture: The orderly arrangement of parts within an endeavor. The structure of endeavor components and their interfaces, and the description and diagramming of this structure and its properties.

• Capability: A talent or ability that has potential for development, deployment, and use/reuse.

• Management: The purposeful resolution of complexity, inconsistency, and chaos in science, society, and perception into a system of controlled order.

Here are some of the “common terms” underlying BEAM.

5


5


System


SystemWhat and Why - Enterprise Architecture?• What is EA:

– Enterprise Architecture is: • An inventory of the identified “components” of an organization within its environment of customers, suppliers, authorities, and partners• A blueprint mapping the component relationships• Detailed descriptions of the components and relationships• A governance process to control the accuracy, timeliness, and fitness-to-enterprise-purpose of the component inventory and blueprint• Reference-to and/or use-of external component standards and categories in the blueprint when appropriate• Application of the EA as a top-level map for more detailed organization resource maps of IT, Facilities, Supplies, Services, Skill Sets,

Funds, etc.• A mental map that everyone works from in their various enterprises – it’s usually not communicated fully or consistently with

associates to improve coordination and collaboration• Why perform EA?

– A formal (i.e., documented, shared, and controlled) EA is a sign of good, mature, and responsible management• EA is used for engineering of management• Management without EA is management as a craft – perhaps creating beautiful results, but not repeatable or easily maintainable• Would you build, rebuild, or renovate a house (i.e., your organization’s capabilities) without a blueprint?• Would you rather build/rebuild/renovate/maintain your house from common or unique components?• Would you rather have your blueprints maintained over time or redrawn from scratch any time a change was needed?

– EA is mandated by OMB to support:• Clinger-Cohen Act (CCA) for IT resources• Federal Investment Budgeting (Exhibits 300 and 53) for any resource initiative• President’s Management Agenda (PMA) Enhanced eGovernment Initiative• Government Paperwork Elimination act (GPEA)• Government Performance and Result Act (GPRA)

6


6


System


SystemHow Enterprise Architecture?• How to perform EA

– Follow OMB Federal EA Guidance where available (only 60% complete as of Sep 03)– Follow broad concepts provided by CIO Council extension to Zachman Framework (describing what EA is, but not

how to perform it) – Fit EA activities within existing operations where possible to reduce duplicative and fragmented efforts to collect

and organize EA data– Find, buy, or develop a procedure to walk the organization, its managers, and its workforce through the EA

process that will consistently produce and maintain a FEA compliant enterprise architecture

7


7


System


System

Basic Enterprise Architecture Methodology –What and Why

• What is BEAM?– BEAM is a detailed workflow procedure to step the organization through a comprehensive

EA development, operation, and maintenance process, as part of a larger workflow procedure for whole-organization life cycle management

– BEAM is released under a public license for noncommercial use (e.g., free for non-outsourced use by government, academic and other organization)

• Why use BEAM?– BEAM is the only full EA methodology (i.e., workflow procedure) available, commercially or

otherwise– BEAM provides the means for simultaneous FEA, CCA, GPRA, GPEA, CMM/CMMI, and

ISO-9000 compliance– BEAM supports all five government-wide initiatives of the PMA– BEAM is based on over two decades of operational research and experience in government

and industry– Every typical medium to large organization is already performing the activities within the

BEAM workflow – BEAM primarily organizes and integrates these activities’ operations, controls, and data

– BEAM can be performed by internal resources and/or by commercial/contracted/outsourced resources

8


8


System


System

Basic Enterprise Architecture Methodology –How?

• How to use BEAM?– Register for free BEAM non-commercial use– Specify BEAM as your required EA methodology in your EA Contracts and Task Orders– Receive authorized training on BEAM or find a licensed commercial BEAM service provider– Assign or acquire technology to support BEAM– Implement a BEAM project for the first EA cycle (Example Project)

• Site Survey Task – 1 month• Initial Business Architecture and EA Business Case Task – 2 more months• Full Business Architecture (BRM + PRM) Task – 2 more months• Full EA (BRM, PRM, SRM, DRM, TRM) Task – 4 more months

– Implement recurring BEAM operations workflow for subsequent EA maintenance– Extend BEAM for other business function activities and applications

• A76 sourcing studies• Feasibility Studies• Impact Analyses• Security Management (role-based asset distribution and access control, e.g., to support Sarbanes-Oxley Act, Information

Assurance, Privacy Act)• Contingency Management• Continuity Management• Vulnerability/Risk Management• Knowledge management• Human Capital Improvement (Expertise Management, Expertise On-Call Collaboration, Skills Inventory, Skills

Requirements, Training Management)• Budget/Performance Integration• Improved Financial Management and Reporting (Roll-up and Drill-Down to/from any level, for any subject/expense-

element)• Enterprise Application Integration (Workflow, Web Services)• Enterprise Information Integration (Virtual databases, user-customized views of enterprise data)

– GEM extensions of BEAM (Commercial Service and Support from licensed GEM Service Providers)• Integrated above BEAM extensions with enterprise Operations workflow based in dynamic enterprise intelligence

– 8 more months after BEAM• Integrated enterprise Value-Chain (e.g., supplier/customer chain) workflow and real-time situational awareness - 8

final months for first GEM iteration• Continuing GEM operations workflow with dynamic intelligence

9


9


System


System

EA as Color By The Numbers – Consistency and Simplicity is Needed!

1.1. Inventory, ID, and Arrange

Business Functions,

Organizations, and Locations

2.1. Inventory, ID, and Organize

Functional References, Data, Tools/Technology,

and Standards

1.2. Identify and ID the Assignment of

Functional Responsibility

2.2. Inventory, ID, and Organize

Goals, Objectives, Performance

Measures, and Strategies

2.3. Inventory, ID, and Organize Funded and

Unfunded Plans for Recurring

Operations and New Initiatives

2.4. Collect identified EA information

3.1. Perform Function, Program,

and Project Activities

3.2. Monitor, Assess, Report,

and Adjust Performance

3.3. Monitor, Assess, Report,

and Adjust Enterprise

1. Map the organization and its environment2. Map the organization operations and resources3. Perform and improve resource management and operations

1

2

3

High Level BEAM Process Steps1. Map the organization and its environment1.1. Inventory, ID, and Arrange Business Functions, Organizations, and Locations1.2. Identify and ID the Assignment of Functional Responsibility2. Map the organization operations and resources2.1. Inventory, ID, and Organize Functional References, Data, Tools/Technology, and

Standards2.2. Inventory, ID, and Organize Goals, Objectives, Performance Measures, and Strategies2.3. Inventory, ID, and Organize Funded and Unfunded Plans for Recurring Operations and

New Initiatives2.4. Collect identified EA information3. Perform and improve resource management and operations3.1. Perform Function, Program, and Project Activities3.2. Monitor, Assess, Report, and Adjust Performance3.3. Monitor, Assess, Report, and Adjust Enterprise

10


10


System


System

What Basic Enterprise Architecture Methodology Integrates and Why

Extend and Customize BEAM for:

Y

Y

Y

Y

Y

Y

Y

Y

Human Capital

Improvement

IT SecurityBusiness Process Analysis

IT Architecture

Budget and Performance

Strategic Plan

FEABEAM Activity

YYYY9. Monitor, Assess, Report, and Adjust Enterprise

YYYY8. Monitor, Assess, Report, and Adjust Performance

YYYYTRM7. Perform Function, Program, and Project Activities

YYYYYFEA6. Collect identified EA information

YYYYPRM, TRM5. Inventory, ID, and Organize Funded and Unfunded Plans for Recurring Operations and New Initiatives

YYYYPRM4. Inventory, ID, and Organize Goals, Objectives, Performance Measures, and Strategies

YYYBRM, TRM3. Inventory, ID, and Organize Functional References, Data, Tools/Technology, and Standards

YYYYBRM, SRM, DRM, TRM

2. Identify and ID the Assignment of Functional Responsibility

YYYYBRM1. Inventory, ID, and Arrange Business Functions, Organizations, and Locations

Why: BEAM Helps Identify and Reduce Duplicative Efforts, Reduce Inconsistency, Share Awareness/Knowledge/Information/Data, and Perform Parallel Improvements.

11


11


System


SystemBEAM BasicsAssertion: Something declared or stated positively, often with no support or attempt at proof.

Simple Assertion

Concept

Concept

Relation

C1 C2R1

C3 C4R2 R3

Compound Assertion

R6

R4R5

An Assertion is two or more concepts (i.e., nouns/names for things you know) connected by their relations (verbs or verb phrases).

A Semantic (Meaning) is a pathway of connections within an assertion. The more complex the assertion, the more complex its semantics/meaning.•Path R1, from C1 to C2 provides one meaning of the Assertion.•Path R4, R3, and R6 from C1 to C2 provides a different meaning of the assertion.•The first path above might be false, while the second path might be true, or vice-versa.•A single marked path, or a collection of them, through a compound assertion is a semantic network.

Everything, from the largest to the smallest, is part of many compound assertions with many meanings.

Joe has money.Mary is a consultant.Deer eat grain.

Deer/C1 eat/R1 grain/C2Deer/C1 Are Supported by/R4 money/C3 from/R3 Mary/C4 for/r6 grain/C2

Deer/C1grain/C2money/C3Mary/C4

eat/R1 costs/R2from/R3are supported by/R4 are fed by/R5for/r6

Paraphrased from http://www.knowledgemanager.us/KM-SemanticPaths-eng.htm:

The fundamental elements of models, or any type of map representing perceived or factual reality, are concepts, their instances, and their relations (i.e., interfaces). Concepts (conceptual generalizations, events, named things, etc.) connected by their relations, form Assertions. The reticular (net-like resemblance) connectiveness of real, possibly-real, and non-real assertions forms the knowledge of a person or group. Thus, a model not only illustrates that two concepts are related, but identifies how these concepts are related.

A proposition is a statement that affirms or denies something, and is an Assertion that is considered a truth. Other forms of Assertions are opinions, conjecture, speculation, contingencies, possibilities, etc., which may or may not represent factual knowledge.

12


12


System


SystemBEAM Basics 2• Assertion: Something declared or stated positively, often with no support or attempt at proof.

A data model or schema is the collection of properties within a semantic network.

An ontology is a collection of semantic networks and data models about a subject which identifies the structure of the knowledge, meaning, and properties of the subject.

An ontology is the structure or schema of a knowledge base, in the same way that a data model is the schema of a database.

SubjectObject

Relation Types (Concept Context)•Category (e.g., Taxonomy)•Containment•Sequence•Change (Past/Future)•Reference•Alias

Relation Properties

Concept Types (GEM Categories Subset) (Concept Content)

•Location•Organization•Organization Unit•Function•Process•Resource

Concept Properties

Concept Types

Predicate

Additional information about the concepts and relations, their Properties, help to describe and identify the concepts and relations, and their behaviors.

In Library and Information Science domains, the BEAM approach uses what is known as “faceted classification”, to enable dynamic and very rich description and linking between concepts.

13


13


System


SystemObject Basics 3 – Four Comparable Assertion Structures

Value 2.3Value 2.2Value 2.1Instance 2


Attribute 3Attribute 2Attribute 1

Class 1 (Table 1)

C2 Attributes

R1 Attributes

C2 Attributes

R1 Attributes

C1 Instance

2Value 1/2/2C1

AttributesValue 1/2/1

C1 Attributes

C2 Attributes

R1 Attributes

C2 Attributes

R1 Attributes

C1 Instance

1CLASS

1

Value 1/1/2C1 Attributes

Value 1/1/1

C1 Attributes

C1 Attributes

R1 Attributes

C2 Instance 1

Class 2

Value 1/3/1

C2 Attributes

C1 Instance

3

C2 Instance 2

Value 1/3/2C1 Attributes

C2 Attributes

R1 Attributes

Relation 1

An ontology is the structure or schema of a knowledge base, in the same way that a data model is the schema of a database. The elemental structure of an ontology is the triple (i.e., subject/predicate/object, noun/verb/noun, component/relation/component. The standard for triples is called Resource Description Framework (RDF)

Class1 Class2Relation 1

C1Attributes

C2Attributes

R1Attributes



Attribute 3Attribute 2Attribute 1

Class 2 (Table 2)

Relation 1 AssertionClass 1

Attribute 1Value 1

Class 2Attribute 1

Value 1Relation

Attribute 1Value 1

A. DLG

B. SQL

C. Matrix

D. XML

An Assertion can be represented as a directed labeled graph, (DLG) a matrix, and a parent/child table structure, among other means.

14


14


System


SystemArchitecture Basics• Architecture: The structure of an endeavor’s components and their interfaces, and the description

and diagramming of this structure and its properties.

Component 1

Component 2

Interface 1

Common Component and Interface Properties•Name•Unique ID•Description•Absolute Position•Create Date•Creator Unique ID•Modify Date•Modifier Unique ID•Deactivate Date•Deactivator ID

Structure Properties(Structure Metadata)

Structure

Architecture

Component 1 Specific PropertiesHeightWidthLengthWeight

Component 2 Specific PropertiesStreet AddressCityStateZip Code

Interface 1 Specific PropertiesShip Component 1 to Component 2Delivery DateDelivery CostRelation Forms: (Space, Matter, Energy, Time, Assertion)

The structure is diagrammed using a “directed labeled graph” - DLG, shown here with the requisite minimum of two labeled-components connected with a single labeled unidirectional arrowed line.

The properties of the structure are documented in a format now known as the “resource description framework” – RDF, established as a standard by the W3C. RDF is the foundation for object role modeling and data modeling used in semantics and data management, and for the ontology modeling used in knowledge management. The properties of the structure, including the diagram’s properties, are stored in RDF format, preferably in an RDF, or metadata, repository. This metadata repository can use XML, tabular, LDAP, or SQL technology. The recommended metadata repository storage technology is an XML database with the RDF storage schema implemented as the RDF-variant Managed Object Facility (MOF) schema, with MOF established as a standard by the Object Management Group. The MOF repository has the necessary flexibility to store, process, present, and maintain the continuously evolving schema and content of architectures and implementations.

15


15


System


SystemArchitecture Basics 2• Architecture: The structure of an endeavor’s components and their interfaces, and the description

and diagramming of this structure and its properties.

Component 1

Component 2

Link 1 Node 2

Node 1

Interface 1 (I1) = N1+L1+N2

•Interface 1 provides Extraction of an asset of Value 1 through Node 1 of Component 1, Asset Transformation (to Value 2)/Transport/Transfer over Link 1, and Loading of that asset with its added transaction Value 2 through Node 2 of Component 2 (ETL), under change transaction rules.•ETL provides Exchange Transactions for Physical Assets and Interchange Transactions for Digital Assets

Architecture Observations:•Architecture maps our perception of the world. •Engineering seeks to control the portion of the world’s mapped structure that we depend on. •Science seeks to identify and establish consistent controls on the portion of the world’s structure that we need to be reliable.•Everyone is an architect because they perceive and organize their own world view. Some architects have engineering discipline and skills. Some architects have scientific rigor and skills.•Architecture is observation, Engineering is applied theory, Science is reproducible proof of theory.•Engineering looks deeper into an architecture’s structure to identify and control the details of the sub-architectures’ structure. •All architecture, engineering, and science must be consistently communicated to have value. If it is not structured it cannot be engineered for reliability nor made consistent using science.

Architecture Example:A ship and a dock are components of a port’s architecture. The ship (component 1) interfaces with the dock (component 2) via a tie-line (interface 1). The ship has a tie-down point (node 1) linking the ship to the tie-line. The dock has a tie-down point (node 2) linking the dock to the tie-line. The tie-line (node 1 + line 1 + node 2) performs some combinations of interface extraction, transformation, transport, transfer, and loading of some physical (e.g., force) and/or digital (e.g., signal) asset between the ship and the dock, and conversely over another or the same interface.

Structure

Architecture is represented here in more detail, in relation to engineering and science. Architecture is presented here as a human trait for perceiving the world. Architecture’s value comes in communicating the perceived structures in a way that can be used as the start point for engineering and science.

16


16


System


SystemEnterprise Architecture Basics• A purposeful endeavor - an enterprise - can have an inventory of its known

and approved components, but an inventory is not an architecture• Those inventoried components that have defined interfaces/relationships

are the enterprise’s architecture, “As It Is” at the time of the component inventory and any interface identification

• An intended or desired structure and its properties is an architecture “To Be” formed at some future time

• A time-phased plan to introduce, modify, or eliminate components from the current enterprise As-Is inventory, with the corresponding introduction, modification, and/or elimination of relevant interfaces, to form the objective To-Be architecture, is an “Architectural Plan” to migrate the enterprise from its “As Is” to its “To Be” architecture

• Architectural plans can be for a single component, a single interface, a single property, or multiple components, interfaces, and properties

• Architectural plans are implemented as individual or collected projects and thus require project management controls (i.e., controls on production schedule, production budget, and product/service quality) with aggregation into programs, then into portfolios, and then into strategies

17


17


System


System

Open-Standard EA and IT Management Repository Elements

Standard Object Repository

EnterpriseArchitecture Design Rules

IT Common Information

Model(Device, Network,

Software, and Configuration

Integration Rules)

Standard Object Model

EA Tools IT Mgmt Tools

Data Mgmt via Common Database

and Data Warehouse Design Rules

Application Mgmt via System and

Software Design Rules

MOF Repository, showing enterprise architecture and IT operation management components.

18


18


System


System

BEAM Improvement Management Environment

Strategic and Business Plan (Future)•Function•Functional Mission•Functional Vision•Functional Goals•Functional Performance Measures•Functional Performance Strategies•Current Operations Analysis•New Initiatives•Alternate Improvement Paths•Improvement Path Economic Analysis•Improvement Project Funding

BEAM Integrated Web-enabled Management Repository•Object Repository (e.g., OMG XMI, CWM, CIM Schema)•SQL DBMS•Web Server•PKI Registration/Certificate/Security Service•PKI Authentication and Namespace Directory Service•Directory Service (Namespace Categorization and Attributes)•Architecture Modeling Service (Components, Relations, Descriptions, and Change Tracking)•Messaging Service (e.g., Email, Application Integration, Web Service)•Schedule/Calendar Service•Discussion/Conferencing/Collaboration Service•Document/Content Management Service•Change Management Service (Contingency, Plan, Current, History Change/Version Tracking)

Program/Project (Current and History)Detailed Planning, Tracking, and Reporting to Supply Data on Daily Management of Tasks:•Events

•Vulnerability/Risk•Deliverables•Activities•Action Items•Milestones•Meetings•Incident Reports•Status

•Labor Performance•Value Expectation and Requirement Management•Deliverable/Product Status•Performance Metrics•Task Processes•Event Dates (Contractual and Estimated Due, Start, End)

Program/Project Planning (Future)•Project Work Breakdown Structure•Resource Breakdown Structure•Organization Breakdown Structure•Task/Organization Matrix•Project Plan (Task, Milestone, Product Dependency, Critical Path)•Earned Value Management (Cost Variance, Schedule Variance)•Requirement and Constraint Specification

Management ScopeEnterprise

FunctionMission

VisionGoal

ObjectiveStrategy

PlanProject

TaskEvent

This diagram illustrates the types of information required to manage such an improvement effort. The GEM methodology provides a solid foundation for managing this type of information and the corresponding activities.

Projects directly linked to the organization mission and goals work with the information products in the boxes shown in the diagram, to manage the bolded elements in the strategic management scope outline.

After the project is planned, the execution of the project requires detailed tracking, analysis, and reporting of events over time. This is necessary to identify and resolve variance from project budget (resource plan) or schedule (time plan).

For project planning and tracking to be performed effectively and efficiently, especially in a distributed effort, technology that links the two management processes together must be made available and used.

19


19


System


System

Common information that business and IT workers would supply for BEAM.

Form 1: Enterprise

Form 2: Location

Form 3: Organization

Is At<>

Contains

Contains<>

Occupies

Form 4: Workforce

Form 6: Process

Implements<>

Performed By

Uses/Creates<>

Enables

Form 5: Function

Employs<>

Supports

Form 7: Resource

Form 8: Requirement

Applies<>

Activates

Satisfies<>

Constrains

Form 9: Time/Event

At<>

Schedule, Duration,

Frequency, Change

The “facets” of information collected and organized by BEAM are illustrated here. Each of these facets represents the root of a hierarchical “catalog” of these types of things.

20


20


System


SystemBEAM Form Templates, Part 1

Form 2: LocationGeographic:

Postal Address:Residence:Business:Public:Other:

Facility:Region Name:Spatial Coordinates:

Solar:Geospatial:

Latitude:Longitude:Altitude:

Virtual:Telephone:Email:URI/Web:UNC/File:Database:Radio Frequency:

Form 3: Related OrganizationName:

Chief Executive:Purpose:

Private:Personal:Commercial:

Public:Commercial:Non-Profit:Government:

Contains<>

Occupies

Form 3: EnterpriseName:

Chief Executive:Purpose:

Private:Personal:Commercial:

Public:Commercial:Non-Profit:Government:

At<>

Contains

OptionalFor GIS, Mapping,and CADUse

Example Enterprise, Location, and Organization class attributes and their primary relationships.

21


21


System


SystemBEAM Form Templates, Part 2Form 4: Workforce

Office:Position/Billet:

Team:Role:

Occupation:Grade:

Form 6: ProcessName:Standard:Role

Input:Control:Output:Mechanism:

Implements<>

Performed By

Form 5.1: FunctionName:

Mission:Vision:

Goal:Measure:

Strategy:Plan:

Operations/Projects:Requirements

BudgetsScheduleQuality

Operation:Maintenance:Functional Assessment:

Sustain:Dispose:

Review:Value Chain Assessment:SWOT Assessment:

Strength:Weakness:Opportunity:Threat:

Applies<>

ActivatesForm 5.2: Assignment

Responsible Person:Authority Limits:

LocationOrganizationOrganization UnitFunctionProcessResource

BudgetBudget Items:

Form 5.3: ReferencePolicy:

Process:Procedure:

Template:Constraint:Metadata:Data Required:Date ProducedTools:Materiel RequiredMateriel Produced:

Example Workforce (i.e., organization unit), Function, and Process class attributes and their primary relationships. Note that more detailed information collected and organized about function assignments, references, and plans.

22


22


System


SystemBEAM Form Templates, Part 4Form 7: Resources

Life formFaunaFlora

InformationUnstructuredSemi-structuredStructured

FundsOperationMaintenanceInvestment

SkillSocialBusinessTechnical

MaterielSuppliesEquipment

FacilitiesServicesSpace

DistanceAreaVolumeVelocityAcceleration

Energy

Form 8: RequirementResource

TimeframeScheduleDurationFrequencyChange HistoryChange Projection

QuantityQualityResource Life Cycle

StageProcess

Process StageFunctionOrganization UnitOrganizationLocation

Satisfies<>

Constrains

Form 9: TimePast Event:

Period:From:To:

Chronology:Predecessor:Successor:

Present Event:Period

Began:End:


Future Event:Period

Begin:End:


Ongoing Event:

At<>

During

Example Resource, Requirement, and Time/Event class attributes and their primary relationships. Note that considerable detail will be added the resource class as BEAM proceeds, to include specific types of resources approved for enterprise use, thus providing the content for an EA Technical Reference Model. The current and planned system specifications would be captured as requirements, while the schedule of the requirements would be captured in the Time/Event class.

23


23


System


SystemBEAM Management Relation Matrices

By asking the BEAM procedure’s questions in the order given, the tables shown at the top of this diagram are generated, representing relation matrices for the subjects of the questions. These populated relation matrices, when organized as a whole, related chain of subjects, provides a rich knowledge base of the enterprise as a whole. These same matrices provide the data necessary to generate the various information, products, and views specified by the various enterprise architecture frameworks (e.g., Zachman, FEA, DoDAF/C4ISR, TOGAF). Detailed attributes for each subject contain the majority of the subject detail, and both the subjects and their attributes are tailorable to each organization. GEM provides the mechanism to aggregate these subjects and their attributes, and privacy/security-appropriate data (e.g., knowledge instances) to enable the core GEM content distributed by OWIS to be increasingly refined over time, for all GEM users.

24


24


System


SystemBEAM Management Simplified Entity Relation Diagram

This diagram represents the entity-relationship structure generated by organizing the BEAM Subject Relation Matrices into a relational database, or XML or Java class.

25


System


System

2. Executive Overview

26


26


System


SystemWhat are BEAM, GEM, and EMM and why are they valuable?

• GEM = General Enterprise Management methodology• BEAM = Basic Enterprise Architecture Methodology. A subset of GEM• EMM = Enterprise Management Maturity. A five level scale for identifying

an enterprise’s level of management maturity, corresponding to the stages of fully implementing the GEM methodology

• GEM is valuable because it enables an enterprise to perform its operations with dynamically updated internal and environmental intelligence

• BEAM is valuable because it provides a step by step procedure, free for non-commercial use, to collect the information needed for satisfying the U.S. Federal and basic business requirements for an enterprise architecture, while providing recommended open-standard technologies for storing this information, while simultaneously forming the early stages of an enterprise knowledge base usable by the GEM methodology and its derived applications.

• EMM is valuable because it enables an organization to rate theirenterprise’s management maturity against the full Real-Time Enterprise management capability offered by fully following the GEM methodology, as well as providing the procedures, in stages, for implementing the GEM methodology, building/populating/integrating the GEM repository beyond the BEAM capability, and building/integrating GEM-based functional applications

GEM is a proven "management solution" framework that is the basis for consistent solution design and implementation. GEM is a generalization and integration of several processes present in all enterprise functions, and in all enterprise management, and is an improvement of processes that have been used for centuries. Through this integration, GEM provides a consistent method for analysis and integration of enterprise business, management, systems, value, and other subjects. The documentation of these analyses and integrations can be loaded into a multi-purpose knowledge-base which is part of the GEM design. The implementation of this integration results in knowledge-based value-chain workflow applications that reach across functional and enterprise boundaries.

The concepts and designs behind GEM date back over 35 years to an early “connection model” extension to the popular “systems model”. The connection model was subsequently renamed a “generalized object model”. This early object model is comparable to today’s industry standard Object Metaschema defined jointly by the OpenGroup and Object Management Group (OMG) as the foundation for the structure and management of many modern information technologies. The GEM methodology, repository, and application design has been developed over the past 21 years as information technology has evolved over that period.

GEM is designed as a method for simultaneously attaining enterprise management process and operation maturity, customer focus and value, continuous quality improvement, situational awareness, enterprise architecture, portfolio management, vulnerability management, etc., without all of the overhead required by each of these individual efforts. It is comparable to CMM for Software Engineering, and CMMI for System/Software Engineering and Acquisition Management, but for all organization functions, programs, projects, and processes.

27


27


System


SystemAdvantages of the BEAM UmbrellaBEAM can be used to support, integrate, merge, or eliminate• IT Architecture Management• IT Program, Project, Task, Event Management• System and Software Engineering Life Cycle Management• System/Software Requirement Specification Management• Requirement Management• Independent Verification and Validation (IV&V) of Requirements, Design, and

Development• A76 Outsourcing Studies• Organization And Function Management (Staffing and Structure, Realignment,

Reorganization, Relocation, Mergers, Acquisitions, Task Forces, BPR, etc.)• Quality Management (Six Sigma, TQM, etc.)• Maturity Management (e.g., ISO-9002, CMM, CMMI)• Human Capital Knowledge Management (i.e., Building individual and collective

knowledge base, identifying skills available, identifying skills required, identifying skills gap, driving training management and recruiting)

• Functional strategies, plans, and budgets tracked through to completion• Expenditures traced back to driving missions, goals, objectives, and strategies.• Reference Management (i.e., Policies, Processes, Procedures, Templates,

Standards, Tools)

28


28


System


System

BEAM Business Intelligence Capability Uses EA for Drill Down and Roll Up of Budgets, Priorities,

Performance, Production Levels

Functions and Uses of the Drill Down and Roll-Up Features of BEAM:• Asset Distribution Requirements• Asset Access Control and Information Requirements• Summaries, aggregations, and details concerning Business Functions, Priorities,

Budget• Gives the ability, as a business intelligence technique, to explain to anyone (e.g.,

Congress, OMB) the impact of funding changes (e.g., if you budget this agency XXX dollars you will get these outputs from our mission area in these quantities, in these time frames, with these qualities, etc., as in GPRA support.)

29


29


System


System

GEM Facts/History and Claimed BenefitsFacts/History

GEM, and to a large degree its BEAM subset, has been proven by over two decades of day to day practical use, including:

1. Re-justifying and reorganizing a 16,000 person U.S. Army command assigned to NATO

2. Mapping together job functions, positions, skill sets, IT requirements, organization units, facilities, training, and budgets for organizational productivity improvements and IT acquisitions based on enterprise-wide business patterns

3. Modeling and building an application to provide wartime and contingency operational scenario generation, event release for execution, and performance tracking

4. Modeling and managing the garrison IT architecture for a 300,000 person Theater Army

5. Managing IT requirements in conformance with that enterprise architecture

6. IT planning, programming, and budgeting for that Theater Army

7. Adoption of that methodology, and the application that applied it, as a candidate standard Army management system for managing IT architecture, plans, and execution

8. Inclusion of the management methodology’s knowledge schema in a standard DoD application combining SQL, GIS, and CAD functions for IT architecture, infrastructure, and systems planning and topological display

9. Serving as the management methodology in supporting engineering management for the DoD Common Operating Environment (COE) and Global Command and Control System (GCCS)

10. Providing the operational model and analytical schema to identify the traffic and usage patterns of the DoD Joint Operations Planning and Execution System (JOPES) for use in its redesign.

Claimed Benefits• GEM provides a methodology, i.e., a detailed set of

procedures supported by a variety of open-standard technologies, for developing and implementing management solutions, regardless of the subject being managed

• BEAM provides a single procedure to simultaneously support:– Enterprise architecture (As-Is and To-Be Architectures

and Migration Plans)– A76 competitive sourcing studies– Staffing, structure, and equipping studies– Reorganization/realignment/relocation projects– Functional and enterprise knowledge modeling (for

leveraging and enriching Human Capital)– Strategic management and performance management

of strategic plans/portfolios and budgets/programs/projects

– Business process reengineering (BPR)– Business process maturation (e.g., supporting ISO

9000, and CMMI and CMM at all maturity levels)• GEM provides the procedural steps beyond BEAM to provide:

– Enterprise modeling and management– Enterprise Knowledge Management– Enterprise Workflow– Enterprise Application and Information Integration

(EAI/EII)– Security Architecture and Management– Enterprise Resource and Requirements Management– Enterprise Situational Awareness and Managed

Intelligence– Integrated Enterprise Operations based on Dynamic

Enterprise Intelligence

30


30


System


System

What are the rough costs of BEAM?

• For non-commercial (e.g., government, FFRDC, Academic, individual, community) and internal organization use there is no charge to use the BEAM. (Register for BEAM use, including any of your extensions to BEAM, under the same Creative Commons license, by sending an email to [email protected]). If Contractors without BEAM commercial licenses are used to deploy BEAM internally or in other organization units of a largerorganization, then the initially registering organization must purchase appropriate commercial BEAM licenses from [email protected].

• The BEAM methodology does not introduce significant new work to the typical medium to large organization, but does change the way existing information about the organization and its environs is collected, shared, organized, applied, and maintained. BEAM provides an engineered approach to enterprise architecture as a substitute for the more typical non-repeatable "craft" approach to EA. These changes may involve added costs, which would predictably be offset by increases in productivity, responsiveness, and accuracy of the resultant BEAM-supported work.

• BEAM costs for commercial and non-profit licenses are shown in the table below. This would include providing contracted BEAM support to other organizations, and other non-commercial uses.

• To make payment, click on the hyperlinks in the table below, or contact [email protected] or +1 (703) 598-2351, to make other payment arrangements.

• To download BEAM documentation, project plan, and view lists of Licensed BEAM Supporters and VAR, visit http://one-world-is.com/BEAM.

BEAM Practitioners are available on hourly or retainer basis. Contact [email protected].

$ 20,000.00 1$50 Formal Organization10,000 3.4 Global

$ 10,000.00 1$50 Formal Organization1,000 3.3 National

$ 5,000.00 1$50 Formal Organization100 3.2 State

$ 2,500.00 1$50 Formal Organization50 3.1 City, Metro-Area, or County

CostQntyx License Type MultiplierBEAM Operations Scope and Multiplier

BEAM Commercial Service Provider Annual License Cost:

$ 5,000.00 2.4 Other Methodology or Corporate Software using BEAM

$ 1,000.00 2.3 Community Software using BEAM

$ 400.00 2.2 Small Team Software using BEAM

$ 200.00 2.1 Single User Software using BEAM

BEAM annual VAR license cost varies with inclusion of BEAM in Individual, Small team, Community, and Corporate commercial products or commercial methodology use.

BEAM Annual Licenses for Commercial and Non-Profit Organizations

31


31


System


SystemBEAM for EA Governance

Strength, Weakness, Opportunity, and Threat

(SWOT)Assessment,

Risk Assessment, and VulnerabilityManagement

---------Map Organization, Environment, Operations, and Resources (i.e., Document and Maintain Enterprise Architecture)

• Mission/Vision• Goals

• Performance Objectives• Performance Targets/Indicators

Develop StrategiesRecurring Operations

---------

Initiatives (Projects)---------

Implement StrategiesPerform Projects---------

Measure Project PerformanceReview Strategy PerformanceAdjust Performance---

Enterprise OperationsSpiral

Value Chain Assessment

BEAM enables the enterprise to resolve many of its toughest EA problems through the implementation of its integrated repository. This diagram illustrates the major enterprise and functional management activities supporting a BEAM environment, as a closed loop system.

The dashed elements of the diagram represent GEM components, outside of the BEAM scope.

32


32


System


System

GEM Intelligence Categories (i.e., Facet Classification) Give Context To The Subject

IT Focus

Operation and Performance

Focus

Management Focus

Increasing Context(=Decreasing Disorder)

Next State (Order)

Decision

Awareness

Knowledge

Information

Data

Signal

Event

Current State (Order)

IncreasingIntelligence

Response

Impact

Learning

Process

Metadata

Pattern

Indicator

Change

GEM Function – Enterprise Intelligence

GEM Subject Assertions (Fact, Opinion, History, Conjecture, Projection, Plan, Theory, etc.)

GEM Subjects

In GEM, Enterprise Intelligence is a collection of those sensed, perceived, and recorded things, treated as resources, that guide enterprise decisions for in responding to changes in monitored situations. These intelligence resources are best managed as a whole, thus providing integrated assertions (e.g., facts, opinions, contingencies, requirements) for decisions and response.

GEM categorizes and structures its intelligence in terms of the basic human questions and answers of: where, who, what, why, how, when, how many, how often, for how long, of what quality, at what stage, etc. The intelligence categories of GEM are named: Location, Organization, Organization Unit, Function, Process, Resource, and Requirement. GEM is used to collect, identify, describe, relate, control, and disseminate information about subjects in these categories.

33


33


System


System

1Where we are today…

(As-Is)

2Where we want to go…

(To-Be)

Value-Lattice(Integrated Value Chains)

Operating Environment Mission

Vision

Tightening “Acceptable Performance” Indicators

from Lessons Learned During Operations(Intelligence Refinement)

Risk Assessment, Performance Measurement,

And Adjustments

Objective Criteria

GoalStrength,

Weakness, Opportunity, and Threat Awareness

Evolving Strategy(Adaptation Decisions)

BEAM provides a procedure to move from problems to solutions.BEAM enables accomplishment of architecture goals and objectives.

BEAM Function – Migrating from As-Is to ToBe

3How we’ll get there

(Migration)

Management: The purposeful resolution of complexity, inconsistency, and chaos in science, society, and perception into a dynamicsystem of relative controlled order. The movement from Current Problem to Solved Problem, or from As-Is situation to To-Be situation.

An enterprise is a “purposeful endeavor”, and thus can include the purposeful (e.g., goal-oriented) endeavors of nations, collections of nations, organizations, chains of formally and informally linked organizations, markets, communities, groups, and/or individuals. Each of these endeavors has an As-Is “architecture” at some degree of completeness.

Part of enterprise architecture is defining how to move an enterprise’s As-Is architecture, and the infrastructure and systems described by that architecture, “from here to there” in a purposeful way. This entails knowing: 1) where you are, 2) where you want to go, 3) what path and pace you want to follow, 4) how you’re progressing on the path and pace, and 5) what adjustments are neededto these.

This goal-seeking approach resembles, and is a superset of, the operations-planning approach used by many organizations. It supports and can enable automation of large enterprise management controls such as compliance with the U.S. Government Performance and Results Act (GPRA) and Information Technology Management Reform Act (ITMRA, also known as Clinger-Cohen Act – CCA), and automation of management endeavors such as the 2001 U.S. President’s Management Agenda with its five key government-wide initiatives (Strategic Management of Human Capital, Competitive Sourcing, Improved Financial Performance, Expanded Electronic Government, Budget and Performance Integration).

BEAM can provide an integrated mechanism to support these controls and can thus directly support the Federal Enterprise Architecture (FEA).

34


34


System


SystemBEAM Supports the FEA and the PMA

EA

TA

AA

DA

BA

XXX

XXX

XXX

XXX

XXX

XXX

XXX

President’s Management Agenda Hierarchy

XGovernment Performance and Results Act (GPRA) (1993)

XPresident’s Goals (2001)

X• OMB PART Scorecard

X5. Budget/Performance

X• Federal Information Security Mgt Act

X• FEA in support of Clinger Cohen Act

X• 24 eGov Initiatives

X4. Enhanced eGovernment

X3. Financial Performance / BMMP

X2. Competitive Sourcing / A76

X1. Human Capital / CHCO

XFive Government-Wide Initiatives (Scorecard Items)

XPresident’s Mgt Agenda

BEAM Methodology Structure

FEA = Federal Enterprise ArchitectureBA = Business Architecture (FEA BRM/PRM and DoDAF OV Conformant)DA = Data Architecture (FEA DRM and DoDAF OV Conformant)AA = Application Architecture (FEA SRM and DoDAF OV Conformant)TA = Technology Architecture (FEA TRM and DoDAF TV Conformant)

GEM Methodology Structure

BusinessArchitecture

DataArchitecture

ApplicationArchitecture

TechnologyArchitecture

Enterprise Architecture

PMA = President’s Management AgendaCHCO = Chief Human Capital OfficerBMMP = Business Management Modernization PlanPART = Performance Assessment and Rating Tool

BEAM directly supports the U.S. President’s Management Agenda (PMA) initiative of “Enhanced eGovernment” and its FEA efforts. The commercially available GEM methodology supports the more comprehensive requirements of the full PMA.

Through internal capabilities and teaming and/or GEM licensing arrangements with best of breed management and technology service providers, OWIS provides a full spectrum of Services for managing an organization and its enterprise architecture. We are willing and able to team with your existing contractors in all categories of service, such as planning and implementing BEAM in your organization, or to license GEM to you or them.

BEAM can be directly applied to help achieve the expected results of the President’s Management Agenda, as shown in this diagram. At the heart of the BEAM support for the PMA initiatives is a FEA conformant enterprise architecture, satisfying the EA portion of the “Expanding eGovernment” PMA initiative, with extensions into infrastructure and system development and operations that encompasses the DoD Architecture Framework (DoDAF).

To build the EA, BEAM efforts collect and organize the Business, Data, Application, Technology, and Security Architectures, withmapping to existing and planned infrastructure and systems. BEAM provides the structured basis for effectively, efficiently, and securely building and using enterprise applications.

With the EA in place, the management solution for the other PMA initiatives, and other management initiatives, is greatly simplified. The BEAM Business Architecture, often in conjunction with the Security Architecture, is the most commonly used area of the BEAM-derived Enterprise Architecture. They provide the detailed system and requirement analyses used in defining the data, application, and technology architectures and in implementing subsequent information system capabilities.

35


35


System


System

GEM For Enterprise Management Services• Extending BEAM into Full Enterprise Engineering and Real-Time Enterprise• Operations and Intelligence Management Workflow• Performance/Quality/Cost Improvement• Cycle Time Reduction• Vulnerability/Security/Continuity/Risk Management• Knowledge Management• Multimedia Knowledge and Content Integration• Expertise Location, Collaboration, Notification, Certification, and Development• GEM Intelligence for:

Supporting The President’s Mgt Agenda (PMA)

Basic Enterprise Architecture Methodology (BEAM)Consulting-On, Implementing, and Extending:

IT Services

Network Infrastructure Services•IP, Telephony, VOIP, Satellite, Wireless, Radio•Provisioning, Prioritization/Precedence, and Quality Management

• FEA / NASCIO• DoDAF/C4ISR

• TOGAF• Spewak

• Zachman• Portfolio Management

• LAN/WAN/Wireless Network Management• Application and Database Integration• Complex Databases, Data Warehousing• Web-based Applications

• CFO• CIO• CTO

• CIO• CTO• System/Software

Development Mgrs

Target ServiceAudience

• CEO• COO• CFO• Functional Managers

• CHCO• CKO• CIO

PMA Initiatives(Simultaneous Support)

1. Human Capital• CHCO

2. Competitive Sourcing • A76

3. Financial Performance• BMMP

4. Enhanced eGovernment

• 24 eGov Initiatives• FEA• FISMA

5. Budget/Performance Integration

• Scorecard

GEM-Based Management Support and IT Services

• Organization Studies (Outsourcing/A76, Realignment, Reorganization, Relocation, Cultural and Political Change)

From top to bottom of the above service stratum:1. OWIS provides commercial Enterprise Management Services and Support using our GEM methodology, implemented in value-producing phases using our Enterprise Management Maturity model. 2. GEM includes BEAM, the Public-Licensed EA methodology from OWIS, within its larger methodology for managing the intelligence and intelligence-based operations of any enterprise. BEAM is a methodology, supported by appropriate technology, for developing, maintaining, and leveraging enterprise architectures. BEAM is provided as a public license to enable those working with the FEA and/or TOGAF to have a common starting point for defining EA terms, procedures, and products, thus helping the government clients and their EA providers to begin to reduce the uncontrolled variation in EA approaches into a common approach.

Following the BEAM provides the map or "blueprint" of the enterprise components and their interfaces. BEAM also provides the resultant "inventory" of enterprise resources/assets at their various life cycle stages, and links those resources to the "architecture" of processes, functions, organization units, organization, and locations relevant to the enterprise. In doing this, BEAM extends Enterprise Architecture capabilities far beyond those provided by FEA/FEAF, DoDAF/C4ISR, TOGAF, Zachman, Spewak, etc.

Through use of the more comprehensive and structured BEAM methodology, we provide Enterprise Architecture services and support, having the ability and readiness to work with:Other EA frameworks (e.g., Zachman, DoDAF/C4ISR, FEA, TOGAF, etc.) and EA methodologies (e.g., Spewak), data, application, and architecture modeling tools (e.g., Computas Metis, Agilense Web Modeler, Popkin System Architect, Rational Rose, Ptech, Poseidon UML, Oracle Designer, Microsoft Visio for Enterprise Architects), metadata (model) repositories

Open Standard (MOF, Agilense EA Repository, Netbeans MDR, DSTC),Proprietary (Metis, CA/Platinum ModelMart, ASG Rochade, Cyrano, Softlab Enabler, Oracle, Microsoft, Rational ClearCase, ISC E-GEN/MAP, Sybase Metaworks)

middleware products (workflow, metadata management, metadata integration, ETL, etc.)3. We provide full life cycle support for EA-governed system and software capabilities through our award-winning IT service capabilities, and by teaming with other high quality companies.4. We provide network infrastructure services, such as data and voice telecommunication services and support, through our teaming with high quality network service providers.

36


36


System


System

EMM Level 5: Real-Time Enterprise Management

EMM Level 4: Enterprise Operational Management

GEM™ and Enterprise Management Maturity Levels

GEM provides escalating levels for building and integratinga mature enterprise management capability.

EMM Level 3: Enterprise Architecture (BEAM)

EMM 2EMM 1

EMM 3

EMM 4 EMM 5

Growing the Capability Tree

GEM can begin at any levelof the enterprise and grow outward,

but starting with the whole enterprise is recommended.

EMM Level 1System

Architecture A

EMM Level 2:Functional

Architecture X

EMM Level 1System

Architecture B

EMM Level 1System

Architecture C

EMM Level 2:Functional

Architecture Y

EMM Level 1System

Architecture D

The EMM process has five levels for deploying the capabilities enabled by the General Enterprise Management (GEM) methodology. As illustrated here, the GEM methodology can be applied at multiple levels of the enterprise, but the enterprise only gains a “whole-enterprise” view starting at EMM Level 3, through the application of EA, preferably using BEAM.

GEM is applicable at all levels of the enterprise capability (e.g., from isolated system to “living” enterprise), but the enterprise gains the most value, in the shortest overall time, at the lowest overall cost and complexity, by pursuing EMM 3 through 5 in sequence.

An analogy to help understand the EMM levels of GEM comes from medicine. EMM Level 1 is equivalent to the anatomy and function of a human’s finger. EMM Level 2 is equivalent to the anatomy and function of a human’s arm. EMM Level 3 is equivalent to the anatomy and function of a human body. EMM Level 4 is equivalent to the physiology and mechanical operations of a human body, which both apply the anatomy. EMM Level 5 is equivalent to the psychology and awareness, the intelligence, of the human, which applies the body’s anatomy, physiology, and mechanics.

Stretching that same analogy a bit further, an organization with an enterprise architecture, such as one provided at EMM Level 3, is basically an anatomically modeled organization, much like a cadaver serves as a model of a human. EMM Level 4 is much like a human in a coma – operating but not aware, proactive, or reactive. EMM Level 5 is much like an aware and active human operating in their dynamic environment.

37


37


System


SystemImplementing GEM™ Using EMM™Advanced Services

• BEAM Business Analysis (Partial EMM 3)

• BEAM Enterprise Architecture(Full EMM 3)

• Integrated Operational Management Capability(EMM 4)

• Real-time Enterprise Management Capability(EMM 5)

Outcome/Results• Business Case for Full EA (EMM 3) and GEM (EMM 4 and 5)• Partial EA (Extending FEA BRM into initial Functional Knowledge Base) • Initial Security Architecture (Role basis for asset access and distribution) (GEM only)

• BRM, PRM, DRM, SRM, and TRM for FEA-Conformant EA• Full Security Architecture (Full Role-Based Access Controls) (GEM only)• Initial Vulnerability (Operation Value, Continuity, Risk) Modeling (GEM only)• Enterprise Portfolio Analysis• Initial Physical and Digital Asset Management (GEM only)• Enterprise Model and Value Chain Maturity (GEM only)• Functional Knowledge Base (GEM only)• Guidance Inventory• Guidance Integration (GEM only)

• Mature Operations and Integrated Workflow• Metadata Management for Enterprise Application Integration and Virtual Enterprise Database• Enterprise Portfolio Management• Detailed Physical and Digital Asset Management• Vulnerability Management• Leverages EA for Performance Mgt, Configuration Mgt, Security Mgt, etc.• Continuously Updated Management Dashboards• Reference Architecture (Functional Maturity) Support• Semantic Models

• Situational Awareness for Leaders and Workers• Fastest Decision and Response Cycles• Command and Control• Dynamic Enterprise Intelligence, Operations, Value-Chain Workflow, and Value-Lattice Visualization• Enables Complex Change Management• Mature Culture• Enterprise Ontologies and Dynamic Knowledge Management

OWIS is prepared to support your organization and your contractors in applying the GEM methodology to your enterprise management operation and reporting requirements. This diagram represents our primary GEM-related services.

•What are EMM/GEM durations (for most Federal Departments/Agencies, State and Local Government Departments, and medium to large commercial organizations)? GEM operates in spiral management life cycles, with each subsequent cycle operating from the refined results of the previous cycle. These GEM/EMM stage estimates are cumulative durations, not additive (i.e., Level 4.2 takes approximately three months added on to the 12 months of a Level 4.1 task, yielding an approximate 15 months total).

•A GEM/EMM Site Survey takes approximately 2 weeks. It provides the necessary information to establish the scale of the GEM/EMM effort, the technologies, methods, models, and notations currently in place, and the organizational context of the GEM/EMM effort to help establish the parameters for the Change Management (i.e., communication plan, etc.) process that runs in parallel with the GEM/EMM implementation activities. The Site Survey helps to determine the costs of the EMM efforts within the estimated timeframes below.•EMM Level 1 services take approximately 2 months per system. Note that multiple Level 1 services within a single function would never yield the same benefit as a Level 2 service for that function and all of its systems.•EMM Level 2 services take approximately 4 months. Note that multiple Level 2 services within a single enterprise would never yield the same benefit as a Level 3.3 service for that enterprise and all of its functions.•EMM Level 3.1 – BEAM Initial Business Architecture services take approximately 3 months, yielding a portion of BEAM functionality.•EMM Level 3.2 – BEAM Full Business Architecture services take approximately 5 months, yielding a portion of BEAM functionality.•EMM Level 3.3 –BEAM Enterprise Architecture services take approximately 9 months, yielding a portion of GEM functionality with FEA and C4ISR/DoDAF conformance.•EMM Level 4.1 – Operational Enterprise Architecture services take approximately 12 months, yielding a portion of GEM functionality. (EAI)•EMM Level 4.2 – Dynamic Enterprise Management services take approximately 15 months, yielding a portion of GEM functionality. (Workflow)•EMM Level 5 – Real-time Enterprise Management services take approximately 24 months, yielding the full GEM functionality. (Value-Chain Workflow, Situational Awareness)

•Who can benefit from BEAM and EMM/GEM? Any organizational executive, manager, workforce members, singly or in groups, and their customers, suppliers, authorities, partners, and the relevant public constituency.•What are the benefits of BEAM and EMM/GEM? Shared and maintained knowledge based on common terminology, meaning, and understanding, as appropriate by the attained EMM Level. Increased operational capability, effectiveness, efficiency, adaptability, and responsiveness.•What is the cost of BEAM and EMM/GEM? Cost of infrastructure to support BEAM/GEM (network, repository platform, repository software, client platform, client software, training on these, maintenance of these). Cost of initial and ongoing organizational and functional analysis. Cost of interfacing organizational and functional knowledge with legacy information systems, Web, Semantic Web, Web Services, etc.•Where are BEAM and EMM/GEM performed? BEAM/GEM would operate using a technical platform distributed over the organization’s intranet, private networks, and Internet.•When are BEAM and EMM/GEM performed? GEM is performed continuously once begun, operating as a core process within its adopted organizations.•What are the BEAM and EMM/GEM frequency? An EMM Level, once reached, would require consistent use and maintenance to sustain its value and capability. BEAM/GEM use would be by your organization’s personnel and/or its OWIS support team. The BEAM and EMM/GEM maintenance could be performed by OWIS and/or by your personnel trained in the EMM/GEM techniques and tools.

38


38


System


System

BEAM Spiral Life Cycle Support for Standards, Regulations, and Legislation

4. Infrastructure

4. Enterprise Architecture

5. Business Case, Technology,

Standards, R&D

2. Business Function Plans

4. Function Systems

5. Function Operation Performance5. Business Requirements

4. Capability Provisioning

5. Function Satisfaction

3. Process Maturity

1. Enterprise View

2. Enterprise References and Reference Maintenance

5.. P

erso

nnel

Fun

ctio

n

5. L

ogis

tics

Func

tion

5. F

inan

ce F

unct

ion

5. F

acilit

ies

Func

tion

5. M

arke

ting

Func

tion

5. O

ther

Bus

ines

s Fu

nctio

n

4. Functional Foundation

1. Enterprise Context Inventory

3. Requirements Management

2. Strategic Management

5. Customer Satisfaction

5. Function Information Products

3. Process Management (Workflow)

5. Strength, WeaknessOpportunity, Threat

Zach

man

, FEA

, TO

GAF

EA

GPR

A

GPR

A

ITM

RA/

Clin

ger-C

ohen

Act

DoD

AF/C

4ISR

EA

This figure illustrates the life cycle of enterprise management information resources. An enterprise model, showing the inventory of managed objects within the enterprise, provides a mapping for subsequent management activity. By building a management capability from an enterprise model, you gain the ability to manage the context of the enterprise as a whole. This provides the mechanism for situational awareness, knowledge-based activities, and process (supply chain, value chain) optimization.

39


System


System

3. Technical Overview

40


40


System


System

What is the BEAM process? (BEAM – EA Capability Management Stages Preceding GEM)

IT Capability Management Stages

System/Software Engineering (i.e., Detail Design) and Operation Enterprise Architecture and System/Software High Level Architecture

Certification and Accreditation (GEM)(e.g., DITSCAP Definition, Verification, Validation, Post-Accreditation Activities)

SA(GEM)

Customers, Business, and Investment

(GEM)

Content and Performance

(GEM)

Software(GEM)

Application Platform(GEM)

Infrastructure(GEM)

TA(TRM)

AA(SRM)

DA(DRM)

BA(BRM/P

RM)

Business Service (Component) Definition (Reusable solution set)

Security Architecture(GEM)

Security Domains mapped to security policy, procedures, and guidelines, and then to Enterprise Security Architecture (ESA) guidance

Technology ArchitectureFunction Technology•TRM Services Category

–Mapped to Runtime Patterns•TRM Approved Service Category Products

–Mapped to Runtime Products•Request TRM Waiver

Applications ArchitectureFunction Logic•Application and Business Component Catalog

–Feature•Behavior

–Benefit»Cost

•Request new Application or Component

Data ArchitectureFunction Data•Domain

–Subject Area•Subject

–Attributes–Constraints

–Structured Content•SQL, LDAP

–Semi-structured Content•XML, Messages

–Unstructured Content•Office Files•HTML, Text

•Request New Data

Business ArchitectureFunction•References

–Policy•Process

–Procedure»Templates»Rules»Standards

–Vocabulary -> Knowledge•Mission Operations•Assignment

–Org Units•Organization

–Locations

•Request New FunctionRole-based Access Definition(GEM)

Role-based Data Classification(GEM)

Access Rules and Methods(GEM)

Access Mechanisms

BEAM EA products as foundation for System/Software Engineering and Operations.

41


41


System


SystemBEAM™, Your Tools, and MDEM™

MDEM Repository

BEAM

Software Design Repository

Application Development and Data Modeling Tools

IT Repository

IT Management Tools

Metadata Repository

Metadata and Data Management Tools

Why Model Driven Enterprise Management (MDEM)? Using modern open-standard technology, MDEM can provide enterprise users with the effectively and efficiently-managed intelligence needed to conduct and improve operational activities, reduce costs, and reduce the latency of decisions.

RequirementRepository

Resource Management

Tools

The BEAM, in conjunction with a robust open-standard mechanism to collect and relate data from a variety of tools, provides MDEM. GEM is vendor neutral, although specific technical capabilities applied in the GEM implementation and subsequent operations are provided by a limited number of technology vendors.

42


42


System


System

Model Driven Enterprise Management - MDEM Tools (GEM Support)GEM Schema And Enterprise Model (GEM)

BEAM and GEM MDEM Repository Elements

OMG Managed Object Format (MOF) Repository (BEAM)

EnterpriseArchitecture Schema via Model

Driven Architecture – MDA (BEAM)

IT Common Information

Model – CIMSchema

(Networks, Platforms, Devices, Software, and Configurations)

(GEM)

IT OperationsManagement Focus:•CIO•CTO

IT Governance and Development Focus:•CFO•CIO•CTO

EnterpriseManagement Focus:•CEO•COO•CFO•CHCO•CKO•CIO•Functional Managers

OpenGroup and OMG Object Metaschema

GEM-based Operation, Asset, Vulnerability, and Security Management

WBEM Tools

Data Model (e.g., Metadata, ORM,

IDEF1X) Integration w/ Common Warehouse Metamodel – CWM

(GEM)

Application Model (e.g., UML)

Integration via XML Model Interchange –

XMI (GEM)

Software Development Focus:•Development Managers•CIO•CTO

Open StandardSoftware Process

Engineering Workflow (GEM)

Open Standard Web Services,

Business Process Integration, and Workflow (GEM)

BEAM and GEM Repository elements, showing enterprise management, enterprise architecture and IT operation management components. Standard are underlined.

43


43


System


SystemEMM 3 – Extended Enterprise Architecture (EA) +

Functional Operations with Technology

Portfolio s for PRM, Technology Development

Enterprise Operation, Asset, Vulnerability, and Configuration Management(DoDAF AV)

Controls

Infrastructure and Systems Linkage to EA(DoDAF SV)

Certification & Accreditation(FISMA)

• Information Management Technology (TV)

• Services Management Technology–e.g., personnel services, cleaning services, IT services, food services

• Facilities Management Technology

• Materiel Management Technology–Equipment (e.g., vehicles, factories, IT hardware/software, furniture–Supplies (e.g., food, fuel, office supplies, IT supplies

• Skills Management Technology

• Funds Management Technology

• Personnel Management Technology

Functional Technology Types

• Mechanisms for Asset Distribution and Access Control of Physical and Digital Assets (GEM, Final RBAC)

• Capability Package (Business Component)• Basis for Physical and Digital Asset Access Rules and Methods (GEM)

• Metadata and Data Management• Basis for Data Classification (Privacy, Confidentiality, Secrecy, Need to Know, etc.)

• FEA compliant BRM• Information for Physical and Digital Asset Management (GEM)• Information for Process Modeling and Management (Workflow and Asset Distribution) (GEM)• Information for Role-based Push/Pull of information for Situational Awareness and C2 (GEM)• Information for Knowledge Base

• Information for EA, System, and Functional Business Cases• Basis for Role-Based Access Control – RBAC to physical and digital assets (GEM)• Information for Organization and Functions Management (e.g., Task Organization, Realignment,

Reorganization, Merger/Acquisition)

Results

Full Business Architecture (FBA)

(2 months)

InitialBusiness

Architecture (IBA)(2 months)

Enterprise Architecture Elements

Enterprise Capability Documentation*** Enterprise Architecture is NOT about information technology.*** IT management benefits from EA, as does everyone in the enterprise, their customers, their partners,their authorities, their suppliers, and the public.

(Italic Underlines show IT-Specific EA Elements, with drivers from OMB FEA, Clinger-Cohen Act, OMB A-130 and A11, Investment Budget, etc.)

Technology Architecture (TA) (FEA TRM) (DoDAF TV)

Application Architecture (AA) (FEA SRM)(OV)

Data Architecture (DA) (FEA DRM) (OV)

Business Architecture (BA)

(FEA BRM and PRM) (DoDAF OV)

Security Architecture (SA) (FISMA)

FEA and DoDAF/C4ISR

Conformant EA(8 months)

BEAM supports the development and maintenance of the enterprise architecture.

This slide illustrates that, of all of the elements of a full-scale enterprise architecture, only a few relate to information technology. The CIO typically has the lead in EA because IT has measurable economies and efficiencies to gain in satisfying business, legal, andregulatory requirements. But the lead can also come from a functional, program or project manager, or another executive such as the CTO, CKO, CHCO, CSO, CFO, COO, CEO, or President.

However, the enterprise executive with the authority to implement the full enterprise architecture, operational enterprise architecture, and intelligent-enterprise management is usually the organization CEO, President, Director, or Commanding General, as an Executive Management Agenda initiative.

BEAM extends the early “business systems planning/information strategy planning” (BSP/ISP) of IBM’s Dewey Walker, the later 1987Enterprise Architecture Framework of IBM’s John Zachman, and the later 1992 Enterprise Architecture Planning methodology of Steven Spewak.

While BSP/ISP, Zachman Framework, and Spewak methodology are highly useful and parallel, and can substitute for, much of the initial phases of the BEAM approach, they provide only a subset of the capabilities provided by BEAM. Part of this is because of the basic model applied by these earlier EA efforts. The early efforts are patterned on a “relational” or “matrix” model, while BEAM is patterned on an “object” model, which has the inherent capability of working with more “dimensions” of information than the relational model. The organizations which have used BSP/ISP, Zachman Framework (or its derivatives of FEA/FEAF/TEAF, DoDAF/C4ISR, CADM, DIAD, TOGAF, NASCIO, etc.), or the Spewak Methodology (for pursuing the initial elements of the Zachman Framework) can apply the results of those efforts directly to the BEAM implementation to shorten BEAM implementation time.

44


44


System


SystemBEAM Delivers Capabilities

Enterprise Model RelatingEnterprise andFunctional Missions

OrganizationMission Organization EA

•PRM Extension•BRM Extension•DRM Extension•SRM Extension•TRM Extension•FISMA SA (GEM)

Capability (Component, System)

Architecture

CapabilityDevelopment

Functional ReferenceArchitectureand Methodology

FunctionalRequirementsAndPriorities

Approved Designs

Multiple InputAnd Output Formats

Specifications supporting Federal Enterprise Architecture (FEA)• PRM = Performance Reference Model• BRM = Business Reference Model• DRM = Data Reference Model• SRM = Service Component (e.g., Application) Reference Model• TRM = Technical Reference Model• FISMA = Federal Information Security Management Act• SA = Security Architecture• MDEM = Model Driven Enterprise Management

CapabilityOperation and Maintenance

Deployed Components (Reality)

BEAM Results• Single repository for integrating and sharing

Intelligence for Operations• Traceability of Capability Architecture,

Development, and Operation costs to Executive Management Agenda and Enterprise and Functional Missions

BEAM enables a smooth flow, with accountability, from mission to implementation.

BEAM Repository (MDEM Technology)

• Missions• Visions• Goals• Performance Results• Reusable Component Management• Business Drivers• Technology Drivers• Relationship Drivers• Enterprise Architecture• AIS Design, Test Plans, Test Data• Metadata and Data Management• Physical and Digital Assets• Portfolio Management• Configuration Management

• Objectives• Strategies• Plans

This diagram illustrates the GEM repository, from a US Government perspective, as the mechanism for connecting business drivers, enterprise management, IT management, and IT components/assets. It can do the same for management of any category of assets.

45


45


System


SystemCapability (Requirement) Management Life Cycle

Life Cycle Development by Functional Area (Requirements Management Process)

BasicScenario

Performance(Load/Stress)

Test. Network,System,

Application, andService Tests

Function Test,Against Validated

Requirements

RequirementVerification.

Solution SatisfiesValidated

Requirements

RequirementValidation

RequirementDocuments

InternalFunctions

ExternalFunctions

OtherFunctions

Conduct ofFunctional

Activity

OrganizationalAnd Functional

Strategic Planning

Organization andFunction Plans

and Policy

Emails, TaskingLetters, ConceptPapers, Enquiries

RequirementStatements, With

Authorizing OfficialIdenity. Table ofemphatic "shall"

statements with aperson held

accountable ($) forits validity

Decision to Build orBuy Required

Capability

Buy Capabilityfrom Product/

Service Vendors

Build Capability,using System/

SoftwareDevelopers

Product/Service

EvaluationCriteria

VendorContact

System/SoftwareSpecifications (e.g., ISO 830-

1998 System RequirementSpecification (SRS))

Design Phase

Build Phase

Test Phase

Deploy Phase

Initial OperationalCapability

Deployment

Final OperationalCapability

Deployment

Product Evaluation.Anectdotal

(Documents,References),

Demonstration, andTest EvaluationsAgainst Criteria

Security Test

Security Review

Preliminary DesignReview

Critical DesignReview

EvaluationRecommendation

OperationalAcceptance Test

(OAT)

Operate, Maintain,and Dispose

System Engineering (ANSI/EIA 632) and/or Software Engineering (IEEE/EIA 12207) Life Cycle Process

Software IntegrationSystem Integration

Infrastructure IntegrationEnterprise Integration

Requirements Traceback

Functional IT Infrastructure/Systems/Software



Build

Buy

Develop

IntegrateIntegrate Product/Service Into

Enterprise, Infrastructrure,System, or Software

Prototype or FOCDevelopment

Using Product/Service

ISO 14258EnterpriseModeling

ISO 15704 Enterprise Reference Architecture and Methodology

Requirements Analysis Build/Buy Acquisition Activity Implement Capability

This diagram illustrates the life cycle of requirements management derived from day to day operations, with system and software development being traceable back to the underlying operational need. This life cycle is mapped to the corresponding standards which can be used to guide the management of development efforts and the corresponding methodology, notation, and tool selection of the enterprise.

46


46


System


System

Typical Manually Controlled Role-Based Security(What are you securing, from whom or what, in what situation?)

•Q: What are you securing? A: Resources (i.e., Assets) and Processes.•Q: Whom or what are you securing from? A: Users = persons, processes, devices, etc.)•Q: How are you securing? A: Assigning (i.e., giving responsibility and authority) resource access rights to users.•Q: How do you measure security? A: Regularly count vulnerabilities to any and all resources on enterprise and value-chain scale, and watch and measure vulnerabilities and breaches over time.

User Resource(AssignmentsBased on Human Knowledge and Actions)

•Networks•Databases

•Applications•File Systems

•Message Systems•Facilities

•EquipmentRelationshipManagement

Value-ChainProcess / Workflow

Operation

UserIdentity

UserInventory

ResourceInventory

And Classification

IdentityManagement

ResourceManagement

This diagram illustrates the elements of enterprise security enabled through the typical manual process. The weakness in this approach becomes apparent when the number of assigned requirements increase, and the need for changing assignments becomes more fluid.

47


47


System


SystemBEAM-Based Security for Internal Control

(What are you securing, from whom or what, in what situation?)•Q: What are you securing? A: Resources (i.e., Assets) and Processes.•Q: Whom or what are you securing from? A: Users = persons, processes, devices, etc.)•Q: How are you securing? A: Assigning (i.e., giving responsibility and authority) resource access rights to users.•Q: How do you measure security? A: Regularly count vulnerabilities to any and all resources on enterprise and value-chain scale, and watch and measure vulnerabilities and breaches over time.

User Resource(AssignmentsManagement)

•Networks•Databases

•Applications•File Systems

•Message Systems•Facilities

•EquipmentRelationshipManagement

Value-Chain

Process / WorkflowOperation

BEAM Knowledge Base (i.e., EA Management Repository)SUBJECT CONTEXTSUBJECT

AuthenticatePerson orProcess?

AuthorizeOr Prohibit

Access?

UserIdentity

RightsControl

UserInventory

ResourceInventory

And Classification

BEAM Content

Third Party Tools

IdentityManagement

ResourceManagement

BEAM KB to Specify User Resource Requirements and Distribution

BEAM KB to Specify Resource Access Constraints

BEAM KB to Assign (i.e., as Internal Controls) User Access Permissions to Resources

This diagram illustrates the elements of enterprise security enabled through the GEM methodology and supporting tools.

48


48


System


SystemBEAM Cycle “Tree” Analogy in relation to FEA and DoDAF/C4ISR Elements

Sec

urity

Man

agem

ent (

FIS

MA

)

Sec

urity

Arc

hite

ctur

e(F

ISM

A S

A)

Ope

ratio

ns

BEAM Approach To EA (e.g., Zachman, FEAF, FEA, TOGAF, Spewak, etc.)

BEAM Approach To DoDAF/C4ISR

EMM3-Functional Guidance and Intelligence

EMM3-Full Functional Reference Architecture

EMM3-Infrastructure

EMM2-Functional Operations (Rules)

EMM2-Functional Systems

EMM1-Functional Products (Templates and Instances)

Business Architecture(FEA BRM and PRM)

Data Architecture(FEA DRM)

Application Architecture(FEA SRM)

Technical Architecture(FEA TRM)

Functional Systems

System Products (Templates and Instances)

Infrastructure

DoDAF OperationalView

DoDAF Technical View

DoDAF SystemView

BEAM Approach To EA

BEAM operates from the principle of a “spiral life cycle”, also known as a “closed loop system”. The results of one cycle are fed into the next cycle, providing part of the basis for adjusting that subsequent cycle. In BEAM, EA information products, such as reports, documents, data, etc., are “recycled” by the enterprise to refine its knowledge about its EA. Because BEAM is based on the GEM “generalized” approach, BEAM can be applied to perform enterprise architecture in all its varieties.

49


49


System


SystemBEAM - System (EMM Level 1) Capability Architecture Elements

Configuration Management

Across all Aspects of the

Enterprise

Security Management

Enterprise Architecture References

Capability Documentation

Detail Design, Implementation Plan, Tracking, Performance Measurement, Reporting, and Adjustments

High Level Capability (e.g., System) Architecture

Life Cycle Stages

Quality Assurance and Performance Measurement

Content Development, Operation and Maintenance Performance (GEM)

AIS Certification and Accreditation (C&A) (GEM)

Customer Relationship Management (CRM), Business Utility (e.g., Balanced Scorecard), and Investment Goals (e.g., CPIC)

Customer, Business, and Investment Satisfaction (GEM)

Approved Runtime and Security Products and Software Design Patterns

Software, Development, Operation, and Maintenance (GEM)

Platform Development, Operation, and Maintenance (GEM)

Approved Runtime Products and Security Products

Infrastructure Development, Operations, and Maintenance (GEM)

Business Function Requirement and Process (BEAM Step 30 & 31)

Business Component Testing and Deployment(GEM)

Application, Runtime and Security Patterns, Runtime TRM Service Categories, Security Service Categories

Technology Architecture Reference Selection (Mechanisms for Access Control) (FEA TRM)

Application Architecture Reference Selection (Basis for Access Rules and Methods) (FEA SRM) (BEAM Step 30 & 31)

Application and Security PatternsData Architecture Reference Selection (Basis for Data Classification) (FEA DRM) (BEAM Step 30 & 31)

Business Component (i.e., Solution Set) Definition(BEAM)

Business, Integration, Composite, and Security Patterns

Business Architecture Reference Selection (Basis for Role-Based Access Control – RBAC) (FEA BRM and PRM) (BEAM Step 30 & 31)

Security Architecture Reference Selection(GEM)

System Business Component

Development

System Pattern Matching (Ref. IBM Patterns for eBusiness and

System/Software Design Patterns)

System Capability Architecture Elements

Bottom-Up EA. EA built up from the System Capability level by linking to or creating enterprise-wide EA references.

50


System


System

4. BEAM Procedures

51


51


System


SystemBEAM Project Gantt Chart (Blue Bars)

(BEAM Precedes GEM, BPR, and Capability Design, Development, and Operations)

ID Task Name2004

3 BEAM Site Survey

4 BEAM Initial BusinessArchitecture

5 BEAM Full BusinessArchitecture

7 BEAM Data Architecture

8 BEAM ApplicationArchitecture

9 BEAM TechnicalArchitecture

10 GEM EA-based SecurityArchitecture. EMM4

21 EA-Based Business ProcessImprovement. EMM2, After BEAM

22 Initial BPI List

23 Refined BPI List

24 Baseline BPI List

25 BPI Project Template

26 BPI Projects (Multiple)

29

EA-based Technology SolutionLogical Design (UML, Metadata/DataModel, Data Migration). EMM1, AfterBPI

30 Technology Logical Design ProjectTemplate

31 Technology Logical Design Projects(Multiple)

34EA-Based Technology PhysicalDevelopment. EMM1, After LogicalDesign

37 Technology Physical DevelopmentProject Template

38 Technology Physical DevelopmentProjects

2Basic Enterprise ArchitectureMethodology (BEAM) life cycle.EMM3

6 BEAM Enterprise ITArchitecture

2003

FebJanNov

BPI Projects (Multiple)27

BPI Projects (Multiple)28

Technology Logical Design Projects(Multiple)32

Technology Logical Design Projects(Multiple)33

Apr

35 Technology Insertion Assessment

36 Technology Build/Buy/ReuseAcquisition Assessment

May

GEM EA-based OngoingKnowledge Inventory. EMM412

GEM EA-based OngoingKnowledge Integration. EMM4/513

GEM EA-based OngoingKnowledge Structure Definition.EMM4/5

18

GEM EA-based SituationalAwareness. EMM520

Dec Mar Jun

1 GEM Methodology Life Cycle Phases

11GEM-Based Ongoing Security,Vulnerability, and Risk ManagementEstablished. EMM4

19

17

16

15

14 Expertise Location andCategorization

Expertise Development andCertification

Expertise Notification andRecall

Expertise Communication,Coordination, and Collaboration

GEM Ongoing Integration ofEnterprise Workflow, Applications,and Information. EMM4/5)

41

42

39EA-Based Functional TechnologyOperations and Maintenance. EMM1,After Development

Technology Operations40

Technology Maintenance

Technology Maintenance

BEAM Activities(Enterprise Architecture)

GEM Activities, includingDevelopment of SecurityArchitecture as predecessor toBPR and Solution Design, Development, and Operation; Sarbanes-Oxley Act support First/Rapid Response support, etc.

BPR Activities based on detailed enterprise and functional analysisresulting from BEAM.

Solution Logical Design, under EA governance, using standard system and software modeling techniques and approved products and Services from Technical Architecture

Solution Development andOperation under EA Governance

This diagram is available fordownload from http://www.one-world-is.com/beam/BEAM+GEM+IT%20Gantt.jpg

This resource-loaded project plan, in MS Project format, is available at http://www.one-world-is.com/beam/BEAM-EMM3%20Organization%20EA-IT%20Rollout.mpp

A calculator to identify the rough order of magnitude (ROM) cost and duration of a BEAM project for your organization may be downloaded fromhttp://www.one-world-is.com/beam/BEAM%20Organization%20Project%20Scaling%20Formula.xls

The BEAM approach is easily implemented and controlled through standard project management techniques, and can serve as the comprehensive and consistent systems analysis needed for enterprise and/or functional BPR and subsequent functional capability implementation and operation.

52


52


System


System

BEAM Information Structure

GEM Security Architecture

GEM ExpertiseManagement

GEM LearningManagement

GEM KnowledgeManagement

GEM EnterpriseProcess and Value-Chain

Workflow(Function as Service)

GEM Real-TimeSituationalAwareness

(Service Agents)

Updated through continuous functional refinement (dynamic data, metadata, ontologies, and knowledge) (technology insertion/refresh) (Adjust Mission down through Plan) (ContinuouslyImprove Internal Controls)

Management Integrated Strategic, Operations, and Project/Tactical Life Cycle

EnterpriseLocations

OrganizationsOrganization Units

Functions (e.g., WfMC)Policy

Process (e.g., BPMS)

Procedure

Template (e.g., Web Forms and WSDL)

Metadata

Transaction / Event

ResourceRole

Rules

TechnologyComponents

Interface

Behavior

Interaction

Responsibility

Authority

BudgetInput

Control(Internal and External)

Output

Mechanism

ProductionGoal

Mission

Vision

Goal

ObjectiveStrategy

(Program, Portfolio)

Plan(Recurring, Initiative)

Project

Task

Activity

Resource

Schedule

Dependency

Product(Deliverable

Implementation of Plan

TrackingPerformance

Reporting Performance

Adjusting Performance

Assessing Performance Against Plan

Assessment of Strategy, Objective, Goal, Mission, Function, and Enterprise

Reporting

Adjusting

TechnologyCategory

TechnologyVendor

Technology Product or Service

TechnologyInventory and

Tracking

Service(SRM, OV)


(e.g., BRM and CPV, PRM, OV)

DataArchitecture(DRM, OV)

Service ComponentArchitecture(SRM, OV)

TechnologyArchitecture(TRM, TV)


ServiceLevels

(BRM, SRM, OV)

Managed Interoperability Bus (Network and Service Infrastructure)

(Enterprise Service Bus (ESB), Service Oriented Architecture (SOA),

Enterprise Application Integration (EAI), Enterprise Information Integration (EII), Electronic Data Interchange, (EDI) etc.)

External / Internet Bus

Internal / Intranet Bus

ServiceBus(SV)

Priority and Ranking of Plan

(Operations, Investments)

Plan ManagementApproach

System Engineering Management Plan (SEMP)

Software Engineering Management Plan

Plan Technical Approach

Vocabulary

TaxonomySemantics

OntologyKnowledge

BEAM Enterprise Architecture (Core Enterprise Knowledge Base) (e.g., FEA, DoDAF, TOGAF8 Support) (AV). GPRA, GPEA, CCA, and FISMA Support. Sarbanes-Oxley Internal Control Verification Support.

Service Information Sets(Functional References)(Supports Workflow –WfMC, BPM, WSDL)

Enterprise Context (Supports Universal Application Network - UAN)

IT Management

The large frame in this diagram represents the hierarchy of subjects encompassed and integrated by BEAM to create a core enterprise knowledge base. The gray boxes to the left represent the GEM products built from the BEAM Knowledge Base content.

53


53


System


System

BEAM – Procedural Flow(Concurrently For All Enterprise Organizations, Functions, Programs, and Projects)

4. Function 6. Policy

15. Process

16. Procedure

17. Templates

19. Metadata

21. Data

18. Constraints, Rules, and Principles

8. Authority 26. Budgets 27. Budget Lines

22. Equipment, Supplies, and Service (IT and Others)

13. StrategiesDefinitions& Portfolios

14. Plans29. Functional

Programs& Projects

32. Performance

28. Expense Elements

5. Mission

9. Vision

10. Goals

11. Objectives

12. PerformanceIndicators

30. Technology Infrastructure, Systems, and Devices Testing, Development, and Deployment

31. Technology Prototyping, Operation, and Maintenance

7. Responsibility

23. Technology Catalog

24. Technology-Specification and Insertion

20. Data Dictionary

TechnologyArchitecture(IncludingTechnicalReference Model - TRM)

Data Architecture(Including FEA Data Reference Model - DRM)

ApplicationArchitecture(Including FEA Service Component Reference Model - SRM)

Business Architecture (Including FEA Performance Reference Model –PRM, and Business Reference Model - BRM)

25. Requirements

BA-BRMElements

BA-PRMElements

Function Capability

Components

Technology Components

ResourceManagement

Services

ITServices

3. Organization Unit 2. Organization 1. Location

This diagram illustrates the operational flow of an organization using the BEAM life cycle. It also represents the multiple-level linkage of EA entity/relationship or class schema. The BEAM procedure is equivalent to a resource management procedure. In this case, the resource managed by BEAM is architectural information and optionally, information about actual or intended instances of enterprise infrastructure and systems built, operated, and maintained in conformance with the architecture. BEAM enables refinement of enterprise architecture throughout each subsequent cycle. The information created, used, and modified in this procedure needs to be stored in a single repository to avoid fragmentation of the enterprise architecture.

This diagram also illustrates the operational flow elements of the BEAM Spiral Life Cycle overlaid on the top-level OMB FEA Model with its PRM, BRM, SRM, DRM, and TRM elements, shown as yellow frames. The light blue boxes represent operational activities common to most organizations, whether accomplished formally or informally.

Note that while an “enterprise architecture”, shown here as BEAM components in relation to the FEA model, has elements in common across all organizations, GEM extends the organization’s enterprise architecture to support the larger enterprise management process of secure organizational operations management from managed organizational intelligence. GEM extends the BEAM, FEA, Zachman Framework, C4ISR/DoDAF, TOGAF, TEAF, and other EA frameworks, and glues these EA efforts together with the operational efforts, melding them into a full enterprise management (EM) solution framework. GEM, as a methodology, repository, and repository-based and repository-integrated applications, provides a dynamic federated interoperability model for communities of interest (COI) within the enterprise, and a comprehensive EA and EM management approach.

The concepts underlying EA are not new. EA is largely the repackaging of what most who have taken an "enterprise view", or a "system view of the organization" have done all along.

Note that The EA and FEA, through BEAM or otherwise, are not ends in themselves, but are a means to gain control over technology expenditures, primarily IT expenditures. IT spending has shown the trend of suboptimization - spending on localized views of need for assigned or assumed functions, not prioritized enterprise requirements. This control over technology spending and the reduction of suboptimization directly supports the alignment of the Executive Branch and its operations with the President's Management Agenda, in pursuit of Performance Management and compliance with the Government Performance and Results Act (GPRA).

If the common operational artifacts above are reviewed by those outside of the EA and IT communities, then most will acknowledge that their organization performs the activities yielding enterprise-wide common operational artifacts roughly matching the PRM and BMR. Fewer will have enterprise-wide common operational artifacts matching the SRM, while even fewer will have enterprise-wide common operational artifacts matching the DRM and TRM.

The need for a closed loop EA process thus drives the need for a shared, distributed, common, enterprise-wide repository for EA. Without such a shared repository - an "enterprise brain“ - every activity in this flow that is not shared through the repository breaks that activity and its subsequent activities out of the "enterprise-wide" view and makes it a locally suboptimized activity. If an EA activity and its artifacts are not stored and processedin the shared repository, they are hidden from the enterprise view and enterprise accountability. This takes local operational autonomy too far in the direction of wildness and away from the controlled order needed by any organization to survive and thrive. It's like a wild mutation, or worse, like cancer. Most wild mutations are not beneficial to the organization/organism, and cancer is never beneficial. A closed-loop, self-referencing, environmentally adaptive, self-healing management process is needed.

54


54


System


System

BEAM – Procedure Steps0. Identify your enterprise, most typically your organization. For your enterprise, identify the following to the degree you consider economical and relevant. Store and maintain

all of this information in a single data store to reduce enterprise fragmentation.1. What locations are relevant to you? Where do you operate?2. What is your organization's name? What are the organization names of your value-chain stakeholders (i.e., customers, suppliers, authorities, and partners), and what are

their locations which are relevant to you?3. What are your organization's internal units, as typically portrayed as blocks on an organization chart, or more formally identified by a budget, plan, or program within your

organization's aggregate financial management plan? What are the relevant organization units of your customers, suppliers, authorities, and partners for each internal organization unit?

4. What are the functions (i.e., assigned work) performed by your organization units? What are the relevant functions performed by their relevant organization units of your customers, suppliers, authorities, and partners?

5. What is the mission of each organizational unit's function?6. What policy governs the function?7. Which person, identified by name, unique identifier, and assigned position, is responsible for achieving the function's mission?8. What is the boundary of the functional mission's authority in terms of function, functional interfaces, organization units, organizations, and locations?9. What is the responsible person's vision of perfect mission performance?10. What measurable goals has the responsible person defined to achieve the vision of perfect mission performance?11. What performance objectives, specified in terms of schedule, cost, and quality, has the responsible person defined to attain these goals?12. What quantitative performance indicators give proof of reaching the objective on time, within budget, to the required quality specified?13. What strategies, including executing portfolios of investments, will enable the responsible person to quantitatively prove, through meeting the specified performance

indicators, that they have attained their objectives, and thus goals, and thus mission?14. What plans, either for recurring operations or new initiative projects, will be used to implement each strategy?15. What process will be followed in performing the planned recurring operation or initiative project?16. What specific procedure will be followed at each defined step of the process?17. What template will be used to collect or present information used in the procedure, and is this template automated (e.g., online form, web service) or manual (paper)?18. What constraints, rules, or principles must be complied with in using the template?19. What metadata does the template and constraint contain?20. What is the unique ID for each metadata item in each template and each constraint?21. What is the procedural transaction data for each metadata item in the template or constraint?22. What equipment, supplies, and/or service is required to complete the procedure, in what quantity, with what qualities, on what schedule?23. What category describes each equipment, supply, and service resource, and is this category approved by the enterprise's architecture (i.e., component and interface)

control authority to avoid wild variance in enterprise resources?24. What are the item/product/vendor specifics of the equipment, supply or service required for the procedure, and is this technology ubiquitous, in early adoption, or in the

research stage? 25. What are the collected requirements, defined in terms of procedural performance resources, in specific quantities, with specific qualities, at specific times, at specific cost,

for fully implementing the plans?26. What is the budget in the current and future years for filling the requirements of the plans, for the strategies, in accomplishing the function's objectives, goals, and mission?27. What budget line items, in the aggregate, fully describe the requirement?28. What elements of expense (i.e., pre-established categories of resources) categorize each budget line?29. As sub-functions, what programs, as collections of inter-related projects, and which program and project managers, are given responsibility for satisfying the requirements?30. What capability technology insertion, development, and deployment projects are governed by the Program and Project Managers, and what are their detailed performance

schedule, budget, and quality constraints? (Use ANSI 632 System Engineering Process, and ISO 12207 Software Life Cycle Management as guidelines here)31. What initial and recurring capability prototyping, operations, and maintenance are governed by the Program or Functional Managers, and what are their detailed

performance schedule, budget, and quality constraints? (Use ANSI 632 System Engineering Process, and ISO 12207 Software Life Cycle Management as guidelines here)

Feed all collected responses to these questions into the EA repository, noting that items 30 and 31 related to actual infrastructure and system development, deployment, operation, and maintenance, not enterprise architecture. However, these items form the basis for measuring compliance with the architecture and the success/fit of the architecture to the enterprise/function mission.

BA

BA

DAAA

TA

Business architecture is developed in steps 0 through 19 and 25 through 31. Data architecture is developed in steps 17 through 21. Application architecture is developed in steps 18 through 21. Technical Architecture is developed in steps 22 through 25. Note that Information Technology is considered only as one category within the TA and is not given consideration in the BA, DA, or AA.

55


55


System


System

C. EvolvingTime-PhasedArchitecture (TRM)

B. Proven PatternsAnd SharedComponents

A. TechnologyInsertionCenter

11. Future IT Architecture (TRM)

+ Exploratory Change

8. Next Generation. IT Architecture (TRM) +

Proactive/ Planned Change

5. Current IT Architecture (TRM) + Rapid Adaptive Change

10. Future IT Infrastructure

Prototypes / Testbed / Shared Components

7. Next Generation IT Infrastructure

Prototypes / Testbed / Shared Components

4. Current IT Infrastructure /

Shared Components

Architecture Driver Roles•User Awareness

•Functional User•Functional Technologist

•IT Management Awareness•IT Researcher•IT Architect•IT Infrastructure Engineer•IT System Engineer

CommonUse

I. R&D III. Standards V. DeployedII. Early

PrototypesIV. EarlyAdoption

VI. EarlyDeployment

VII. UbiquitousDeploymentIT Technology/

Product Status

12. Advanced Technology Demonstration Systems

9. Prototype Systems

6. Pilot Systems

3. Current Systems

Deprecated Use

1. Business Architecture

(BRM)

2. Existent Data (DRM)

and Application

(SRM) Architectures

Technology Insertion/Refreshment Process Flow(Within Steps 24, 30, and 31 of BEAM Procedure)

This diagram illustrates the phases of activity involved in developing and implementing an IT Architecture and the related infrastructure and systems. If reading the bottom bar from right to left, an organization cannot gain ubiquitous deployment (i.e., VII) of some IT capability until the capability has progressed through most, if not all, of the preceding phases (i.e., I – VI).

56


56


System


SystemTechnology Insertion/Refreshment ProcedureThe process for reviewing technology for insertion into the organization can use the following steps.1. Determine the business architecture2. Determine the data and application architectures.3. Examine the current (As-Is) technology infrastructure and systems supporting the applications’ processing of data

for business operations. Identify the requirements for inserting other technology (either new or common-use) into the ToBe infrastructure or systems. Plan the insertion project. Initially test the insertion as a pilot system (i.e., #6) in a lab. Initially implement and operate the insertion pilot. Operationally test the insertion. Gain acceptance of the insertion operational results. Fully implement the insertion as a production system. Operate and maintain the inserted technology.

4. Identify the technology components in the pilots, systems, and infrastructure that have use across multiple applications, data models, and business processes.

5. Register the successful pilot and operational technologies in the TRM as suitable for production systems, and have future system/infrastructure developers specify the technology’s TRM category in their initial plans and design.

6. Develop and test pilot systems using early-adoption and deployed-standard technologies in the lab.7. Identify technologies in the pilot that need to be prototyped in a lab yet which appear to satisfy unique and

common requirements.8. Include the successfully prototyped deployed technologies in the TRM as suitable for “Next Generation” and pilot

systems.9. Develop and prototype systems using R&D, pre-standard, and new-standard technologies in the lab.10. Identify technologies in the prototype that need further R&D and standardization.11. Include successfully prototyped pre-standard technologies in the TRM as suitable for future prototypes and pilots.12. Work with researchers to conduct Advanced Technology Demonstrations prior to the technology’s standardization

and register successfully demonstrated technology in the TRM as appropriate for prototyping and piloting of future systems.

57


System


System

5. Standards/Technology Supporting BEAM

58


58


System


System

Information Assurance Common Criteria (ISO 15408)

BEAM - Enterprise IT Reference Architecture (i.e., Technical Process Standards)

Enterprise Modeling (ISO 14258)

Enterprise Reference Architecture and Methodology (ISO 15704, FEA, ISO 9000)

SEI Capability Maturity Model Integrated (CMMI) (IT)

Standards Container / Component Relations

BEAM leverages these standards and others

ANSI/EIA 748-1998, Earned Value Management Systems

Acquisition Management (e.g., DoD 5000 Series, CMM, CMMI)

ISO/IEC 11179 Series – Specification and Standardization of Data Elements (IT)

Configuration Mgmt (ANSI/EIA-649)

System and Software Requirement Specification (IEEE 1233-1996 and 830-1998) (IT)

Process for Engineering a System (ANSI/EIA 632) (IT)

Software Life Cycle Management (IEEE / EIA 12207.x) (IT) Resource Management,

RequirementsManagement, and Access Provisioning

Information Assurance(Defining and Defending the Enterprise External and Internal Boundaries)

EnterpriseMissionManagement(GPRA, CC/ITMRA, Performance Management, IT Investment Planning and Management)

Enterprise References (Policy, Process, Procedure, Templates, Standards), Methodology, Role Management, and Architectures

This diagram illustrates the enterprise and IT standards leveraged by BEAM, and the applications and resultant functionality that results from implementing them as parts of the GEM whole-enterprise management approach.

59


59


System


SystemBEAM Information Product CategoriesContext

(Individual or CollectiveWorld View,

Philosophical Ontology)

Information(Structured

and Unstructured)

Words(Concepts, Tagged

Information)

Keywords(Major Concepts,

Tagged Information)

Taxonomies(Categorized Word

Inventory, With Word Variants)

Concept Maps(Keyword Relations:

Category, Containment, Sequence, Change, Reference)

Data Models(Keyword (i.e., Entity)

Relations, with Attributes)

Semantic Models(Detailed Data Models,

with Detailed Relationships)

Data Meaning(Significance, or value,

of Entity to Users, Meaningful Information)

Applications(Automated Rule-BasedProcessing of Data for

Transactions and Analysis)

Dictionaries(Words and Phrases,

With Definitions, Variants, and Usage)

Lexicon/Vocabularies(Function-Specific

Word and Phrase Variants)

Databases(Entity Values)

Process Models(Information/Work Flow

Across Users and Value Chain)

PrehistoryTill Now

1951 TillNow

Timeframe for Intelligence Technology

Item, List, Outline, Table,

Reference Table

Network, Hierarchical, and Relational

Database, Hierarchical Directory,

Multidimensional Database

60


60


System


System

BEAM, with Your EA and Other Tools, with MDEM™

MDEM MOF Repository(Open Source and Multiple Vendors)

BEAM

Tool Repository or Format

Legacy EA Tools (UML, XMI, IDEF, or Proprietary Formats)(Metis, PTech, Popkin, Agilense/Adaptive, Rational, Poseidon, etc.)

XMIEAMS Tools

(OMB Exhibit 300 Support)

XMI

CIM

IT Management Tools(Network, Platform, Help Desk,

Applications, Storage)(WBEM)

Metadata Repository Metadata and Data Management Tools

(Application Data Models, Warehouse Data Models,

i.e., IDEF1X, ORM))(Operational and Analytical Data)

CWM

The BEAM methodology, in conjunction with a robust mechanism to collect and relate data from a variety of tools, provides the start point for MDEM.

61


61


System


System

OMG 4 Layer Metamodel for MDEM(MDA, SPEM, XMI, GEM/BEAM, CIM, CWM)

M3 MOF

M2

M1

M0

MetaObject Facility(metadata repository)

MOF Extension/Profile

MOF-based Application Design

MOF-basedApplication Instance

UML (SPEM)

RUP

ImplementedProject

SW Process Metamodel

SW Process Model

SW Process Performance Or AggregatedPerformance

Object Metaschema (Generalized Object Model, Generalized Object Repository)

UML (XMI)

RUP

ImplementedProject

SW Design Metamodel

SW Design Model

SW DesignFor System orAggregated Design

BEAM Metaschema

BEAM Schema

ImplementedProject

BEAM Design Metamodel

BEAM Design Model

BEAM InstanceIn Enterprise Or AggregatedGEM Capability

CIM Metaschema

CIM Schema

IT ManagementRepository

CIM Design Metamodel

CIM Design Model

CIM InstanceOn Device, orAggregatedIT Management

CWM Metaschema

CWM Schema

Data ManagementRepository

Data Design Metamodel

Data Design Model

Data Model Or AggregatedData Models

This diagram provides a means of comparing the underlying structure of BEAM to “object” management standards.

62


62


System


System

Model Driven Enterprise Management - MDEM - Technology (GEM Support)

GEM Schema Tools(IntegratedEnterprise,Function,Process,Data,System,Software,Security,&KnowledgeModelingAnd Management)

6. Products Supporting BEAM

OMG Managed Object Format (MOF) Repository

Enterprise Architecture Schema(FEA, DoDAF, TOGAF, etc.) Business, Data, Application, & Technical)•Agilense WebModeler•Popkin SA•PTech•Computas Metis•Other EA/CASE Tools

IT Management Tools

OpenGroup and OMG Object Metaschema

GEM-based Operation, Asset, Vulnerability, and Security Management Tools

CWM Schema (Data and Metadata Models)•Data Modeling•Metadata Management•BI Tools•OLAP Tools•Data Warehouse Tools•3HT eSnap•Schema Logic•MetaMatrixORM Tools (for Semantic and Data Modeling)

•MS Visio for EA

•MS VisioModeler

XMI Schema (Application Models)•UML Tool Examples

•Rational•Poseidon

ORM Tools (Semantic Models)

•MS Visio for EA•MS VisioModeler

Open StandardSoftware Process

Engineering Metaschema

(SPEM) Standards and Tools (GEM)

Open Standard Business Process

Integration (WSDL, BPM) and Workflow (WfMC, UAN)

Standards and Tools

(GEM)

CIM Schema (IT Models) (MOF)•Troux (HW/SW/Net/EA)•Isogon (SW)•Tivoli TM1•MS SMS•BMC Patrol•HP OpenView•Other WBEM ToolsStandards Subsumed byCIM/MOF•SNMP IP Tools (MIB)•Desktop Mgmt Tools (MIF)•HelpDesk Tools (SES/SIS)•Others

BEAM and GEM Repository elements, showing enterprise management, enterprise architecture and IT operation management components. Standard are underlined.

63


System


System

7. Sample BEAM Implementation Project Plans

64


64


System


System

7.1 Sample BEAM Organizational EA (EMM 3) Project Plan

ID BEAMStep

Task Name BEAM Deliverable Durat ion

1 Develop Enterprise Architecture 174 days2 Preparation Phase Determine Scale, Complexity, and Readiness for EA 10 days3 Site Survey and Readiness Assessment 10 days4 Repository installation and configuration 5 days5 Operation Management Conduct BEAM Operations Management 169 days6 Repository Operation, Maintenance, and

Customization169 days

7 Change Management Planning, Dissemination,Implementation, and Tracking. BEAM Tailoring

164 days

8 Initial Business Architecture Business Case for Full EA (EMM 3) and GEM (EMM 4and 5), Partial EA (Extending FEA BRM into initial GEMFunctional Knowledge Base). Initiate Role-BasedAccess Control – RBAC definition for physical anddigital asset security.

42 days

21 Full Business Architecture FEA compliant BRM. Additional Information forPhysical and Digital Asset Management Security.Initial Process Modeling for Workflow and AssetDistribution. Additional Information for Enterprise

40 days

27 Enterprise Architecture BRM, PRM, DRM, SRM, and TRM for FEAConformance. Enterprise Guidance Inventory.

35 days

36 Budget and Portfolio Development Enterprise Portfolio Analysis. 30 days42 Infrastructure, System, and IT Management

Linkage to EAMapping of Resources to Mission. 5 days

BCBE,BC

BE

BC

T W T F S S M T W T F S S M T W T F SDec 7, '03 Jan 11, '04 Feb 15, '04 Mar 21, '04 Apr 25, '04 May 30, '04 Jul 4, '04 Aug 8, '04

Labor Category Initials Rate Work CostBEAM Consultant BC $280.00/hr 1,382 hrs $386,960.00BEAM Repository Engineer BE $120.00/hr 1,392 hrs $167,040.00Business Architect BA $170.00/hr 1,216 hrs $206,720.00Data Architect DA $150.00/hr 222 hrs $33,300.00Application Architect AA $150.00/hr 142 hrs $21,300.00Technology Architect TA $150.00/hr 360 hrs $54,000.00

Estimate $869,320.00

65


65


System


System

7.2 Sample BEAM Functional Architecture (EMM2) Project Plan(e.g., for A76 Studies and As-Is Function Modeling Independent of Organization EA)

ID BEAMStep

Task Name BEAM Deliverable Duration

1 Develop Functional Architecture prior to Full OrganizationEA

Rich functional As-Is model for Planning improvement,competetive sourcing, and start of knowledge managementand skillset alignment.

22 days

2 Preparation Phase Determine Scale, Complexity, and Readiness for ArchitectureEffort

2 days

3 Site Survey and Readiness Assessment 2 days

4 Repository installation and configuration 1 day

5 Operation Management Conduct BEAM Operations Management 20 days6 Repository Operation, Maintenance, and

Customization20 days

7 Change Management Planning, Dissemination,Implementation, and Tracking. BEAM Tailoring

19 days

8 Initial Function Business Architecture Business Case for Full EA (EMM 3) and GEM (EMM 4 and 5),Partial EA (Extending FEA BRM into initial GEM FunctionalKnowledge Base). Initiate Role-Based Access Control –RBAC definition for physical and digital asset security.

6 days

21 Full Function Business Architecture FEA compliant BRM. Additional Information for Physical andDigital Asset Management Security. Initial Process Modelingfor Workflow and Asset Distribution. Additional Informationfor Enterprise Knowledge Base.

7 days

27 Function Enterprise Architecture BRM, PRM, DRM, SRM, and TRM for FEA Conformance.Enterprise Guidance Inventory. Metadata and Data Inventory.

4.5 days

36 Budget and Portfolio Development Enterprise Portfolio Analysis. 3.5 days42 Functional Infrastructure, System, and IT Management

Linkage to Functional ArchitectureMapping of Resources to Mission. 0.5 days

BC

BE,BC

BE

BC

M W F S T T S M W F S T T S M W Fec 28, '03 Jan 4, '04 Jan 11, '04 Jan 18, '04 Jan 25, '04

Labor Category Initials Rate Work CostBEAM Consultant BC $280.00/hr 207.5 hrs $58,100.00BEAM Repository Engineer BE $120.00/hr 168 hrs $20,160.00Business Architect BA $170.00/hr 170 hrs $28,900.00Data Architect DA $150.00/hr 36 hrs $5,400.00Application Architect AA $150.00/hr 28 hrs $4,200.00Technology Architect TA $150.00/hr 40 hrs $6,000.00

Estimate $122,760.00

66


66


System


System8. BEAM Scenarios for Initial EA Governance Cycle

• Enterprise-wide (Top Down) Implementation = BEAM Procedure Steps 0-31

• System-level (Bottom Up) Implementation = BEAM Procedure Steps 22-31, 0-21 multiplied by number of systems to be architected and linked to Functional Architecture.

• Functional (Middle Out) Implementation = BEAM Procedure Steps 13-31, 0-12 multiplied by number of functions to be architected and linked to Enterprise Architecture.

67


67


System


System9. BEAM Summary• BEAM provides a comprehensive step by step procedure to walk an

organization, group, or person through the inventory, identification, categorization, and subsequent management of things that are important to them.

• BEAM provides the process and information products needed for enterprise architecture management

• BEAM can be used for many purposes beyond developing an enterprise architecture and IT portfolios, to include providing the Enterprise Knowledge Base foundation for:– Security Management– Knowledge/Expertise Management– Real-Time Situational Awareness– Business Process Reengineering– IT Design/Development/Operations– Outsourcing/Reorganization/Realignment/Relocation Studies– Performance Management of Enterprise and Functional Missions

Basic Enterprise Architecture Methodology (BEAM)

Documents

Transcript of Basic Enterprise Architecture Methodology (BEAM)