|
|
Archived DOI Reference Models |
PRM v1.0 (5/2004) |
Top |
[Archive] |
FEA Introduction: The PRM is a “reference model” or standardized framework to measure the performance of major IT investments and their contribution to program performance. The PRM has three main purposes:
- Help produce enhanced performance information to improve strategic and daily decision-making;
- Improve the alignment — and better articulate the contribution of — inputs to outputs and outcomes, thereby creating a clear “line of sight” to desired results; and
- Identify performance improvement opportunities that span traditional organizational structures and boundaries
The PRM attempts to leverage the best of existing approaches to performance measurement in the public and private sectors, including the Balanced Scorecard, Baldrige Criteria, Value Measurement Methodology, program logic models, the value chain, and the theory of constraints. In addition, the PRM was informed by what agencies are currently measuring through PART assessments, GPRA, Enterprise Architecture, and Capital Planning and Investment Control. Agencies’ use of the PRM will populate the model over time. The PRM is currently comprised of four measurement areas:
DOI Extension Introduction: The Interior's PRM (Performance Reference Model) relates the business goals to the mission as defined within the DOI Strategic Plan, and defines measurements aligned to the FEA PRM to check whether the business is lined up with the mission.
DOI Strategic Plan (Fiscal Year - 2003 - 2008)
DEAR PRM reports:
DOI PRM -> DOI PRM
DOI PRM with Outcome Measures -> DOI PRM - End and Intermediate Outcome Measures
DOI PRM to ABCs via Outcomes -> DOI PRM to ABCs Through the Outcomes
DOI PRM to BRM via Outcomes -> DOI PRM via Outcomes thru ABCs to BRM
FEA PRM -> FEA PRM
FEA PRM to DOI PRM Outcome Measures -> FEA PRM to DOI PRM Outcome Measures
BRM v2.1 (08/2005) |
Top |
[Archive] |
FEA Introduction: “The Business Reference Model is a function-driven framework for describing the business operations of the Federal Government independent of the agencies that perform them.”
The Business Reference Model provides an organized, hierarchical construct for describing the day-to-day business operations of the Federal government. While many models exist for describing organizations - org charts, location maps, etc. - this model presents the business using a functionally driven approach. The Lines of Business and Sub-functions that comprise the BRM represent a departure from previous models of the Federal government that use antiquated, stovepiped, agency-oriented frameworks. The BRM is the first layer of the Federal Enterprise Architecture and it is the main viewpoint for the analysis of data, service components and technology.
DOI Extension Introduction: The Interior's BRM (Business Reference Model) is the business, the actual job the organization does extending into much greated detail below the Federal levels . The BRM looks at the functions, processes, activities, and tasks BELOW the FEA sub-function level. As well, those lower level details are put into business value chain and flow context via business process modeling efforts as described in MBT Step 3 and 8 respectively. By relating the inventory to the BRM, one can perform common business overlap, gap, and integration analysis performed across organizations.
DEAR BRM reports:
FEA BRM -> FEA BRM
DOI BRM (No Descriptions) -> DOI BRM without Descriptions/Organizations
DOI BRM-Linked View -> DOI BRM-Linked View
DOI BRM-FAs-Alpha-Listing -> DOI BRM-FAs-Alphabetical List of All ABCs
DOI BRM Functions by Organization -> DOI BRM Functions by Organization
FEA BRM Line of Business by Organization -> FEA BRM Line of Business by Organization
DOI BRM Level 5 Process Details -> DOI BRM is built from the FY05 ABCs - see details on those ABCs
DOI BRM - including only ABCs -> Only including Processes created from ABCs
DOI PRM to BRM via Outcomes -> DOI PRM via Outcomes thru ABCs to BRM
DOI BRM to DOI DRM -> DOI DRM Entity to DOI BRM Level 5 F/As
DRM v4.1 (5/2007) |
Top |
[Archive] |
FEA Introduction: The Data Reference Model (DRM) describes, at an aggregate level, the data and information supporting government program and business line operations. This model enables agencies to describe the types of interaction and exchanges occurring between the Federal government and citizens.
The DRM categorizes government information into greater levels of detail. It also establishes a classification for Federal data and identifies duplicative data resources. A common data model will streamline information exchange processes within the Federal government and between government and external stakeholders.
The DRM provides a standard means by which data may be described, categorized, and shared. These are reflected within each of the DRM’s three standardization areas:
- Data Description: Provides a means to uniformly describe data, thereby supporting its discovery and sharing
- Data Context: Facilitates discovery of data through an approach to the categorization of data according to taxonomies; additionally, enables the definition of authoritative data assets within a community of interest (COI)
- Data Sharing: Supports the access and exchange of data where access consists of ad-hoc requests (such as a query of a data asset), and exchange consists of fixed, re-occurring transactions between parties
The FEA PMO is collaborating with members of the interagency DRM Working Group, chartered by the Architecture and Infrastructure Committee (AIC) of the Chief Information Officer (CIO) Council, to implement and maintain this reference model.
DOI Extension Introduction: The Interior's DRM (Data Reference Model) extends the FEA DRM with the department's Conceptual and Logical Entity Relationship Model Diagrams that are categorized within the DOI Subject Areas and Information Classes. Using the DRM artifacts available in DEAR, one can:
- Idenityfing Blueprint Functions and Processes within focus area that use specific common data
- Identifying Common Entity or Information Class by system inventory or organizational use
- Subject Areas and Information Classes as modeled in Conceptual Entity Relationship Diagrams
- Identifying Common Entity or Information Class by system inventory or organizational use
- Entities as modeled in Logical Entity Relationship Diagrams
- Entities as classified within DRM Subject Areas and Information Classes
- Establish DOI BRM Process to DRM Entity relationship
- Creating Common data sharing format standard for describing data packages (i.e. XML)
- MBT Steps 3 (Business/Data Analysis) , 4 (System to Data), and 9 (Data Standardization)
- See: Biz Lab Services Data and Information Design
FEA DRM Documents:
Data Reference Model 2.0
(PDF, 1.47mb)
Data Resource Management Policy and Guidance:
- 378 DM 1 Data Resource Management Policy
- OCIO Directive 2006-11 Data Standardization Procedures
- Data Standardization Procedures Manual
Metadata Repository:
Interim Metadata Repository (Access)
DRM reports: (Version 4.1)
ELEMENT REPORT AGREEMENT VIEW (EXCEL)
ELEMENT REPORT FACILITY VIEW (EXCEL)
ELEMENT REPORT FINANCIAL MGT VIEW (EXCEL)
ELEMENT REPORT GEOSPATIAL VIEW (EXCEL)
ELEMENT REPORT HIGHLY SHARED VIEW (EXCEL)
ELEMENT REPORT HSPD 12 VIEW (EXCEL)
ELEMENT REPORT HUMAN RESOURCES VIEW (EXCEL)
ELEMENT REPORT LAND MGT VIEW (EXCEL)
ELEMENT REPORT LAW ENFORCEMENT VIEW (EXCEL)
ELEMENT REPORT OCIO VIEW (EXCEL)
ELEMENT REPORT ORGANIZATION VIEW (EXCEL)
ELEMENT REPORT PERMIT VIEW (EXCEL)
ELEMENT REPORT PERSON VIEW (EXCEL)
ELEMENT REPORT RECORDS MGT VIEW (EXCEL)
ELEMENT REPORT RECREATION VIEW (EXCEL)
ELEMENT REPORT SECURITY VIEW (EXCEL)
ELEMENT REPORT STRATEGIC PLAN VIEW (EXCEL)
ELEMENT REPORT SURFACE MINING VIEW (EXCEL)
ELEMENT REPORT TRUST VIEW (EXCEL)
ELEMENT REPORT WILDLAND FIRE VIEW (EXCEL)
ENTITY REPORT AGREEMENT VIEW (EXCEL)
ENTITY REPORT FACILITY VIEW (EXCEL)
ENTITY REPORT FINANCIAL MGT VIEW (EXCEL)
ENTITY REPORT GEOSPATIAL VIEW (EXCEL)
ENTITY REPORT HIGHLY SHARED VIEW (EXCEL)
ENTITY REPORT HSPD 12 VIEW (EXCEL)
ENTITY REPORT HUMAN RESOURCES VIEW (EXCEL)
ENTITY REPORT LAND MGT VIEW (EXCEL)
ENTITY REPORT LAW ENFORCEMENT VIEW (EXCEL)
ENTITY REPORT OCIO VIEW (EXCEL)
ENTITY REPORT ORGANIZATION VIEW (EXCEL)
ENTITY REPORT PERMIT VIEW (EXCEL)
ENTITY REPORT PERSON VIEW (EXCEL)
ENTITY REPORT RECORDS MGT VIEW (EXCEL)
ENTITY REPORT RECREATION VIEW (EXCEL)
ENTITY REPORT SECURITY VIEW (EXCEL)
ENTITY REPORT STRATEGIC PLAN VIEW (EXCEL)
ENTITY REPORT SURFACE MINING VIEW (EXCEL)
ENTITY REPORT TRUST VIEW (EXCEL)
ENTITY REPORT WILDLAND FIRE VIEW (EXCEL)
SRM v1.1, FEA (8/2004) |
[Archive] |
FEA Introduction: “The Service Component Reference Model (SRM) is a business and performance-driven, functional framework that classifies Service Components with respect to how they support business and/or performance objectives.”
The SRM is intended for use to support the discovery of government-wide business and application Service Components in IT investments and assets. The SRM is structured across horizontal and vertical service domains that, independent of the business functions, can provide a leverage-able foundation to support the reuse of applications, application capabilities, components, and business services.
DOI Extension Introduction: The Interior's SRM (Service Component Reference Model) describes the services, or tasks; the components or pieces of the business that use the data and technology to get things done. Few extensions have been made to the FEA SRM, but as blueprints discover enterprise services unique or described in more detailed capabilities at the DOI, extensions will be made. Though, the DOI has performed two cross-relationships pertaining to FEA SRM to other DOI reference models:
- within MBT Step 3, the business value chain is examined by overlapping services needed throughout
- within Technology Domain Analysis, Services are examined as to the classification/Technology standards that should/should not be providing those services.
DEAR SRM reports:
FEA SRM -> FEA SRM
TRM v3.1 (06/2006) |
Top |
[Archive] |
FEA Introduction:The TRM is a component-driven, technical framework used to categorize the standards, specifications, and technologies that support and enable the delivery of service components and capabilities.
The Technical Reference Model (TRM) provides a foundation to categorize the standards, specifications, and technologies to support the construction, delivery, and exchange of business and application components (Service Components) that may be used and leveraged in a Component-Based or Service-Oriented Architecture. The TRM unifies existing Agency TRMs and E-Gov guidance by providing a foundation to advance the re-use of technology and component services from a government-wide perspective.
DOI Extension Introduction: The Interior's TRM (Technical Reference Model) extends the FEA TRM by populating the specification level with products, specifications, or product standards and classifying each by technology implementation usage. As well, as mentioned in the SRM, the TRM is related to the SRM through the usage as classified. An example may be that a certain document management product provides multiple services - such as document management and records management, but at the Department, the product is preferred for usage as a document management service, but contained for usage of its a records management service capabilities as there is another product that is preferred for that capability.
TRM v3.1 Supporting Documents (06/2006) - (DOI Network Only)
DEAR TRM v3.1 reports (06/2006):
DOI TRM (Standards) -> DOI TRM (Standards)
DOI TRM (Specifications) with Usage Detail -> DOI TRM (Specifications) with Usage Classification Details
DOI TRM (Specifications)-Linked View -> DOI TRM (Specifications)-Linked View
DOI TRM (by Manufacturer) -> DOI TRM (by Manufacturer)
FEA TRM -> FEA TRM
DEAR Glossary v3.0 (05/2006) |
Top |
[Archive] |
Summarizes the Objects and Attributes grouped by domains within the DEAR (DOI Enterprise Architecture Repository) metamodel
DOI Metamodel Diagrams (Visual Interactive)
DOI Glossary -> DOI Glossary
DOI Glossary - Linked -> DOI Glossary - Linked
DOI Glossary - Objects/Attributes -> DOI Glossary - Objects/Attributes
DOI Glossary - Objects/Attributes - Linked -> DOI Glossary - Objects/Attributes - Linked