Currently viewing the tag: "data reference model"

9402689084?profile=RESIZE_400xBusiness and technology resources are lined up by employing Enterprise Architecture (EA) so as to realize strategic results, augment organizational performance, and direct departments to meet their key missions more effectually and achieve Operational Excellence.

Federal Enterprise Architecture Framework (FEAF) achieves these objectives for any U.S. federal agency and aids systems exceed interagency boundaries.

The FEAF comprises of 6 interconnected Reference Models, each relating to a sub-architectural domain of the framework.

Here, we deliberate on 1 of the 6 reference models of the Federal Enterprise Architecture Framework—the Application Reference Model (ARM).  ARM sets the foundation for categorizing software applications and their components.

Through the implementation of ARM, we can achieve a number of positive outcomes throughout the enterprise.  Mapping of existing and future information systems to ARM categorizations assists in detecting gaps and redundancies.  Gap detection helps identify occasions for sharing, reuse, and merging or renegotiation of licenses.  Gap information is used in conjunction with other models to identify opportunities. 

ARM has been based on guiding principles that emanate from Common Approach to Federal EA with further refinement based on the purpose and desired outcomes of the Application Reference Model.  The principles are:

  • ARM should be based on the Separation of Concerns principle i.e., founded on an adaptive structure that permits addition of new methods of providing IT capabilities.
  • Definition of ARM should be with reference to applications supplied within the Service Oriented Architecture enabling facilitation of shared services and interoperability.
  • Definition of ARM should be in terms of a hierarchy of broadly paired IT application components.
  • ARM ought to be standards based along several levels of abstraction to circumvent vendor lock-in, under permitting circumstances.
  • Ascertained touch points should enable ARM to back the Business Reference Model (BRM) and the Data Reference Model (DRM). 

ARM contains 3 levels in its structure: Systems, Application Components, and Interfaces.  ARM is also strongly connected with the rest of the 5 reference models of the Consolidated Reference Model Framework.  More on that in the FEAF: Application Reference Model presentation. 

ARM uses 3 potential methodologies in combination with one another to assist in taking advantage of information and strategizing of applications and investments:

  1. Capability Modeling and Analysis
  2. Service Oriented Architecture (SOA)
  3. Portfolio Management

These 3 methods help take advantage of the information in the ARM structure as well as the agency mapping of applications and investments to it, in addition to the other Reference Models.

Let us dive a little deeper into these methods.

Capability Modeling and Analysis

Capability Modeling and Analysis is a requirements analysis technique that converts business or mission as well as technical requirements into distinct competencies that assist in sharing and reuse analysis.

Instead of employing standard requirement or business process analysis techniques, breaking down requirements into detailed capabilities, and modeling the capability dependencies, leads to a clearer picture regarding commonality of requirements.

Service Oriented Architecture (SOA)

For assembly of IT solutions, a collection of interacting services enables an architectural style—SOA—a layered diagram that depicts the services and their dependencies.  SOA offers extra application flexibility due to ease of modification and replacement of services. 

Portfolio Management

Portfolio management techniques are employed to gauge assets for feasibility of use in future and to mature a service lifecycle plan for each asset thus promoting reuse and sharing of services.

Interested in learning more about the Application Reference Model (ARM)?  You can download an editable PowerPoint on FEAF: Application Reference Model (ARM) here on the Flevy documents marketplace.

Do You Find Value in This Framework?

You can download in-depth presentations on this and hundreds of similar business frameworks from the FlevyPro Library.  FlevyPro is trusted and utilized by 1000s of management consultants and corporate executives. Here’s what some have to say:

“My FlevyPro subscription provides me with the most popular frameworks and decks in demand in today’s market.  They not only augment my existing consulting and coaching offerings and delivery, but also keep me abreast of the latest trends, inspire new products and service offerings for my practice, and educate me in a fraction of the time and money of other solutions.  I strongly recommend FlevyPro to any consultant serious about success.”

– Bill Branson, Founder at Strategic Business Architects

“As a niche strategic consulting firm, Flevy and FlevyPro frameworks and documents are an on-going reference to help us structure our findings and recommendations to our clients as well as improve their clarity, strength, and visual power.  For us, it is an invaluable resource to increase our impact and value.”

– David Coloma, Consulting Area Manager at Cynertia Consulting

“FlevyPro has been a brilliant resource for me, as an independent growth consultant, to access a vast knowledge bank of presentations to support my work with clients.  In terms of RoI, the value I received from the very first presentation I downloaded paid for my subscription many times over!  The quality of the decks available allows me to punch way above my weight – it’s like having the resources of a Big 4 consultancy at your fingertips at a microscopic fraction of the overhead.”

– Roderick Cameron, Founding Partner at SGFE Ltd

9316883094?profile=RESIZE_400xEnterprise Architecture (EA) conveys management best practices for positioning business and technology resources to fulfil strategic goals, enhance Organizational Performance, and guide departments to achieve their core missions more successfully via Operational Excellence.

The Federal Enterprise Architecture Framework (FEAF) realizes this goal for U.S. Federal agencies and assists systems surpass interagency boundaries.  FEAF facilitates through documentation and information, and conveys a summarized outlook of an enterprise at various tiers of scope and detail.

The FEAF comprises of 6 interconnected Reference Models, linked through Consolidated Reference Model (CRM), each relating to a sub-architectural domain of the FEA framework.

Data Reference Model (DRM) is a FEA tool for ascertaining the data that the Federal government has and the process through which that data will be shared when business/mission requirements occur.

DRM is propounded as a theoretical framework from which actual implementations may be derived.

DRM offers a uniform way to describe, categorize, manage, share, and reuse data/information within and across the Federal government.  DRM also enables detection and communication of core information across organizational boundaries.

What DRM is not is static and invariable nor is it a data management manual for how to build and maintain data architectures.  It is neither a pan-government conceptual data model nor an all-embracing / fully attributed logical data model.  DRM is not supposed to be a comprehensive collection of XML schemas or a substitute of prevailing data structures within the agencies.

DRM works in consonance with other reference models in various ways.  For example, it identifies opportunities for strategic coordination through relationships among data sources by linking with Performance Reference Model (PRM) while improving business processes and decision-making performance through data sharing with Business Reference Model (BRM).

Data Reference Model arrangement is demarcated by a 3 layered hierarchy.  The 3-layer arrangement of the Data Reference Model delineates domains, subjects, and topics.

  • Domains – Uppermost level of the hierarchy comprises of 4 Domains.
  • Subjects – Central level of the hierarchy covers 22 Subject elements.
  • Topics – Lowermost level of the hierarchy consists of 144 Topic elements.

DRM refers to data and information required to execute Federal business and mission functions.  In order to assist agencies in consistently categorizing, describing, and exchanging their data, there are 3 fundamental method areas associated with the DRM:

  1. Data Description
  2. Data Context
  3. Data Sharing

 

Let us delve a little deeper into the DRM methods.

Data Description

Data Description offers an approach to consistently arrange, portray, and share data.  Customarily, Data Description was exclusively concentrated on arranging and describing structured data.  To tackle the challenge of unstructured data, DRM Data Description section was revised to focus on Metadata.

Metadata is broadly classified into 2 types, business or technical.

Data Context

Data Context is any information that gives added sense to data and a perception of the reason for which it was created.  Data Context permits Data Governance and forms the basis for exhaustive Data Description.  Data categorization methods such as Data Asset Catalog and Information Discovery and Search portray common data architecture artifacts.

Data Sharing

Data Sharing concentrates on architectural patterns for sharing and exchanging data.  Data Sharing assists in retrieving and swapping of data, where access involves supplementary requests and exchange involves permanent, repeating transactions between interest groups.

Interested in learning more about the Data Reference Model?  You can download an editable PowerPoint on FEAF: Data Reference Model (DRM) here on the Flevy documents marketplace.

Do You Find Value in This Framework?

You can download in-depth presentations on this and hundreds of similar business frameworks from the FlevyPro Library.  FlevyPro is trusted and utilized by 1000s of management consultants and corporate executives.  Here’s what some have to say:

“My FlevyPro subscription provides me with the most popular frameworks and decks in demand in today’s market.  They not only augment my existing consulting and coaching offerings and delivery, but also keep me abreast of the latest trends, inspire new products and service offerings for my practice, and educate me in a fraction of the time and money of other solutions.  I strongly recommend FlevyPro to any consultant serious about success.”

– Bill Branson, Founder at Strategic Business Architects

“As a niche strategic consulting firm, Flevy and FlevyPro frameworks and documents are an on-going reference to help us structure our findings and recommendations to our clients as well as improve their clarity, strength, and visual power.  For us, it is an invaluable resource to increase our impact and value.”

– David Coloma, Consulting Area Manager at Cynertia Consulting

“FlevyPro has been a brilliant resource for me, as an independent growth consultant, to access a vast knowledge bank of presentations to support my work with clients.  In terms of RoI, the value I received from the very first presentation I downloaded paid for my subscription many times over!  The quality of the decks available allows me to punch way above my weight – it’s like having the resources of a Big 4 consultancy at your fingertips at a microscopic fraction of the overhead.”

– Roderick Cameron, Founding Partner at SGFE Ltd

9223435882?profile=RESIZE_400xBusiness and technology resources are aligned using Enterprise Architecture (EA) in order to achieve strategic results, make organizational performance better, achieve Cost Optimization, and guide departments to fulfill their central missions more efficaciously through Operational Excellence.

Federal Enterprise Architecture Framework (FEAF) does that for any U.S. federal agency and helps systems transcend interagency boundaries.  FEAF offers a shared approach for the consolidation of strategic, business, and technology management as a component of Organization Design and Performance Management.  The Enterprise Architecture methodology introduced under FEAF transcended several interagency boundaries.

The FEAF comprises of 6 interconnected Reference Models, linked through Consolidated Reference Model (CRM), each relating to a sub-architectural domain of the framework.

These Reference Models convey word-based abstractions of original architectural data and deliver a structure for relating significant elements of the FEA in a collective and uniform manner:

  1. Strategy Domain -> Performance Reference Model (PRM)
  2. Business Domain -> Business Reference Model (BRM)
  3. Data Domain -> Data Reference Model (DRM)
  4. Applications Domain -> Application Reference Model (ARM)
  5. Infrastructure Domain -> Infrastructure Reference Model (IRM)
  6. Security Domain -> Security Reference Model (SRM)

Discussed here is 1 of the 6 reference models of the Federal Enterprise Architecture Framework—the Business Reference Model (BRM), its structure, framework, touchpoints with other reference models, and BRM Taxonomy.

Slide-Deck-image-FEAF-BRM.png?profile=RESIZE_710x

BRM is employed to explain the type of business functions at the system, segment, agency, sector, Federal, national, or international levels rather than giving an organizational vantage point.

Cross-government cooperation between the Executive departments and subsidiary agencies—as well as external partners—is promoted by describing the Federal government in this manner enabling:

  • Uncovering of possibilities for cost reduction.
  • Collaboration.
  • Shared services.
  • Solution reuse in agency IT portfolios and collaboration between and within agency.

BRM elucidates the “what we do” of the organization via the delineation of outcome-oriented and measurable functions and services.

BRM’s real usefulness and worth is gained when it is put to use effectively in business analysis, design, and decision support that aids in improving the working of an agency, bureau, or program.

BRM classification is organized as a 3-layer order, embodying Executive Branch Mission Sectors, Business Functions, and Services.

  • Mission Sector – Pinpoints 10 business functions of the Federal government in the Common Approach to Enterprise Architecture.
  • Business Function – Defines the Federal government functioning at high level, by means of budget function classification codes.
  • Service – Elaborates further what the Federal government does at a subsidiary or section level.

Mission Sector is exclusive to the executive branch of the Federal government.  This layer should be used appropriately for other organizations.

The 3 layers allow arrangement and analysis of IT investments and applications for an assortment of purposes.

All reference models are envisioned to work jointly.  BRM’s further mappings to other reference models contribute added context for the investment or activity.  Input for BRM is through Performance Reference Model (PRM) enabling BRM to feed other reference models.

BRM is intended to deliver agencies with a uniform means to classify their capital investments, detect areas for collaboration and reuse, centered on delivery of business capability.

BRM also aids in refining the general IT architecture to further improve mission outcomes. It extends decision-support abilities to stakeholders and various levels of staff, within and outside an agency, and across the Federal government.  From a Federal viewpoint, BRM permits discovery of prospects for joint effort and reuse of shared services, government-wide.  This collaboration takes 2 forms:

  1. Inter-agency
  2. Intra-agency

BRM is usable in combination with several architecture, development, or analysis methods to deliver all-inclusive standardized design, development, and governance abilities.  There are 3 primary types of BRM methods:

  • Business Architecture for Decision Support
  • Business Process Modeling
  • Business Process Modeling Notation (BPMN) 

Interested in learning more about the FEAF Business Reference Model?  You can download an editable PowerPoint on FEAF: Business Reference Model here and FEAF associated series PowerPoint presentations on the Flevy documents marketplace.

Do You Find Value in This Framework?

You can download in-depth presentations on this and hundreds of similar business frameworks from the FlevyPro Library.  FlevyPro is trusted and utilized by 1000s of management consultants and corporate executives. Here’s what some have to say:

“My FlevyPro subscription provides me with the most popular frameworks and decks in demand in today’s market.  They not only augment my existing consulting and coaching offerings and delivery, but also keep me abreast of the latest trends, inspire new products and service offerings for my practice, and educate me in a fraction of the time and money of other solutions.  I strongly recommend FlevyPro to any consultant serious about success.”

– Bill Branson, Founder at Strategic Business Architects

“As a niche strategic consulting firm, Flevy and FlevyPro frameworks and documents are an on-going reference to help us structure our findings and recommendations to our clients as well as improve their clarity, strength, and visual power.  For us, it is an invaluable resource to increase our impact and value.”

– David Coloma, Consulting Area Manager at Cynertia Consulting

“FlevyPro has been a brilliant resource for me, as an independent growth consultant, to access a vast knowledge bank of presentations to support my work with clients.  In terms of RoI, the value I received from the very first presentation I downloaded paid for my subscription many times over!  The quality of the decks available allows me to punch way above my weight – it’s like having the resources of a Big 4 consultancy at your fingertips at a microscopic fraction of the overhead.”

– Roderick Cameron, Founding Partner at SGFE Ltd

9209039874?profile=RESIZE_400xEnterprise Architecture (EA) denotes management best practices for lining up business and technology resources to realize strategic results, expand upon Organizational Performance, achieve Cost Optimization, and steer departments to achieve their core missions through Operational Excellence.

Federal Enterprise Architecture Framework (FEAF) was first introduced in September 1999 by the Federal CIO Council for evolving an EA within any U.S. federal agency.  FEAF assists through documentation and information that conveys a summarized outlook of an enterprise at various tiers of scope and detail.

FEAF offers a shared approach for the consolidation of strategic, business, and technology management as a component of Organization Design and Performance Management.  FEAF introduced a methodology for an Enterprise Architecture that transcended several interagency boundaries.

The Collaborative Planning Methodology suggested along with FEAF is envisioned as a complete planning and implementation lifecycle, for employment down all tiers of scope defined in the Common Approach to Federal Enterprise Architecture—i.e., International, National, Federal, Sector, Agency, Segment, System, and Application.

May 2012 saw a full new guide, called the “Common Approach to Federal Enterprise Architecture.”  The guide offers an overall approach to establishing and employing Enterprise Architecture in the Federal Government for expanding joint approaches to IT service delivery.  The Common Approach homogenizes the expansion and employment of architectures within and between Federal Agencies.

A 2nd version of FEAF was published in January 2013, meeting the criteria set forth by the Common Approach.  It underscores the importance of Strategic Planning and Strategic Goals as the source for driving business services, which consequentially provides the requirements for enabling technologies.  At the heart of it is the Consolidated Reference Model (CRM), which links 6 reference models and equips all departments with a shared language and framework to explain and evaluate investments.

The FEAF comprises of 6 interconnected Reference Models, linked through Consolidated Reference Model (CRM), each relating to a sub-architectural domain of the framework.

These Reference Models convey word-based abstractions of original architectural data and deliver a structure for relating significant elements of the FEA in a collective and uniform manner:

  1. Strategy Domain -> Performance Reference Model (PRM)
  2. Business Domain -> Business Reference Model (BRM)
  3. Data Domain -> Data Reference Model (DRM)
  4. Applications Domain -> Application Reference Model (ARM)
  5. Infrastructure Domain -> Infrastructure Reference Model (IRM)
  6. Security Domain -> Security Reference Model (SRM)

CRM is intended to permit inter-agency evaluation and detection of overlapping investments, disparities and prospects for cooperation within and across agencies.

By means of the collection of reference models a common nomenclature and system is cultivated for describing IT resources.  Making use of this standard framework and terminology, IT portfolios can be managed more suitably and taken advantage of throughout the Federal Government.

A brief description of the reference models is as follows:

Performance Reference Model (PRM)

PRM relates agency strategy, internal business factors, and investments, presenting a way to measure the influence of those investments on strategic outcomes.

Business Reference Model (BRM)

BRM depicts an organization through arrangement of common mission and support service segments rather than through vertical lines of control, thus encouraging cooperation within and across agencies.

Data Reference Model (DRM)

DRM assists in detection of existing data assets located in solitary storages and aids in comprehending the meaning of that data, ways of accessing it, and means for leveraging it for supporting performance outcomes.

Application Reference Model (ARM)

ARM classifies the standards and technologies involving systems and applications that support the delivery of service capabilities, allowing agencies to share and reuse common solutions and benefit from economies of scale.

The Infrastructure Reference Model (IRM)

IRM sorts the standards and technologies relating to network/cloud to aid and facilitate the provision of voice, data, video, and mobile service components and facilities.

The Security Reference Model (SRM)

SRM offers a mutual language and approach for deliberating on security and privacy in connection with Federal agencies’ business and performance goals.

Interested in learning more about Federal Enterprise Architecture Framework (FEAF) and its reference models?”  “You can download an editable PowerPoint on Federal Enterprise Architecture Framework (FEAF) Primer here and FEAF associated PowerPoint series presentations on the Flevy documents marketplace.

Do You Find Value in This Framework?

You can download in-depth presentations on this and hundreds of similar business frameworks from the FlevyPro Library.  FlevyPro is trusted and utilized by 1000s of management consultants and corporate executives. Here’s what some have to say:

“My FlevyPro subscription provides me with the most popular frameworks and decks in demand in today’s market.  They not only augment my existing consulting and coaching offerings and delivery, but also keep me abreast of the latest trends, inspire new products and service offerings for my practice, and educate me in a fraction of the time and money of other solutions.  I strongly recommend FlevyPro to any consultant serious about success.”

– Bill Branson, Founder at Strategic Business Architects

“As a niche strategic consulting firm, Flevy and FlevyPro frameworks and documents are an on-going reference to help us structure our findings and recommendations to our clients as well as improve their clarity, strength, and visual power.  For us, it is an invaluable resource to increase our impact and value.”

– David Coloma, Consulting Area Manager at Cynertia Consulting

“FlevyPro has been a brilliant resource for me, as an independent growth consultant, to access a vast knowledge bank of presentations to support my work with clients.  In terms of RoI, the value I received from the very first presentation I downloaded paid for my subscription many times over!  The quality of the decks available allows me to punch way above my weight – it’s like having the resources of a Big 4 consultancy at your fingertips at a microscopic fraction of the overhead.”

– Roderick Cameron, Founding Partner at SGFE Ltd