| Go Back | Show | Hide | Reset | Information is for official use only - Last update | |||||||||||
|
|
|||||||||||
| DOI Glossary - Linked |
|
| Glossary Domain |
|---|
| BFA |
| BRM |
| DRM |
| Deployment Architecture |
| Investment Architecture |
| MetaModel Management |
| Methodology |
| Organization and Person |
| PRM |
| SRM |
| Security |
| System Architecture |
| TBD |
| TRM |
| Glossary Sub Domain |
|---|
| BFA |
| Role |
| PRM |
| DRM |
| BRM |
| Investment |
| Methodology |
| SRM |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BFA-INTEGRATION | T | F | F | name "touch point" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | TBD | F | "BFA-INTEGRATION" | |||||||||||
| touch point | Touchpoint (with Picklist) Potential Analyzed | Unknown | TBD | T | Potential Analyzed NA Unknown | "BFA-INTEGRATION" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-DRIVER/PERSON | Updated by complex Matrix Business Driver to Person. | F | F | F | columndefinition comment "comment date" name rowdefinition |
| BUSINESS-FOCUS/ORGANIZATION-ROLE | This associative entity BUSINESS-FOCUS/ORGANIZATION will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | "architectural status" "business focus area" name organizations |
| BUSINESS-FOCUS/PERSON-ROLE | This associative entity BUSINESS-FOCUS/PERSON will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | "architectural status" "business focus area" name persons |
| BUSINESS-FOCUS/SYSTEM-INV-ROLE | Look up table for roles System Invemtories can play with in a BFA. Possible values: Pending, Retire, Target, Target-Integrate, Target-Consolidate. | F | F | F | "business focus area" name "system inventories" |
| BUSINESS-FOCUS-AREA (TEAM INFORMATION) | Sub-Attributes for the Business Focus Area; Persons and Organizations involved with the blueprints | T | F | F | background charter "communications plan" "meeting minutes" "meeting presentations" mission "next meeting" organization "organization roles" "person roles" scope "web site" |
| COMPONENT_/ORGANIZATION-ROLE | This associative entity will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete Name organization "role remarks" "system component" version |
| COMPONENT_/PERSON-ROLE | This associative entity SYSTEM-COMPONENT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete Name Person "Role Remarks" "System Component" Version |
| INVESTMENT-PROJECT/ORG-ROLE | This associative entity INVESTMENT-PROJECT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete "investment project" name organizations |
| INVESTMENT-PROJECT/PERSON-ROLE | This associative entity INVESTMENT-PROJECT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete "investment project" name person |
| ORGANIZATION/PERSON-ROLE | This associative entity ORGANIZATION/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete name organization person "role remarks" |
| PROGRAM/PERSON-ROLE | Associative between these two objects | F | F | F | Delete name person program |
| SUB-SYSTEM/ORGANIZATION-ROLE | This associative entity SUB-SYSTEM/ORGANIZATION-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete organization "role remarks" "sub system" "sub system version" system "system version" |
| SYSTEM/ORGANIZATION-ROLE | This associative entity will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete Name organization "role remarks" system version |
| SYSTEM/PERSON-ROLE | This associative entity SYSTEM/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | Delete Name Person "Role Remarks" System Version |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| columndefinition | PERSON | TBD | F | "BUSINESS-DRIVER/PERSON" | ||||||||||
| comment | Persons comment about business driver. | TBD | F | "BUSINESS-DRIVER/PERSON" | ||||||||||
| comment date | Date comment captured | TBD | F | "BUSINESS-DRIVER/PERSON" | ||||||||||
| name | TBD | F | "BUSINESS-DRIVER/PERSON" | |||||||||||
| rowdefinition | BUSINESS-DRIVER | TBD | F | "BUSINESS-DRIVER/PERSON" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/ORGANIZATION-ROLE" | ||||||||
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/ORGANIZATION | TBD | F | "BUSINESS-FOCUS/ORGANIZATION-ROLE" | ||||||||||
| name | Name of the BUSINESS-FOCUS/ORGANIZATION Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/ORGANIZATION-ROLE" | ||||||||||
| organizations | The organization related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/ORGANIZATION-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/PERSON-ROLE" | ||||||||
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/PERSON | TBD | F | "BUSINESS-FOCUS/PERSON-ROLE" | ||||||||||
| name | Name of the BUSINESS-FOCUS/PERSON Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/PERSON-ROLE" | ||||||||||
| persons | The person related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/PERSON-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/SYSTEM-INV | TBD | F | "BUSINESS-FOCUS/SYSTEM-INV-ROLE" | ||||||||||
| name | Name of the BUSINESS-FOCUS/SYSTEM-INV Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/SYSTEM-INV-ROLE" | ||||||||||
| system inventories | The doi tracked system related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/SYSTEM-INV-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| background | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| charter | The team will be charged with the development of a charter with roles and responsibilities. | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | ||||||||||
| communications plan | Link to the BFA communication plan. | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | ||||||||||
| meeting minutes | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| meeting presentations | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| mission | Mission of the Team. | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | ||||||||||
| next meeting | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| organization | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| organization roles | ORGANIZATION in the context of role they play. | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | ||||||||||
| person roles | PERSON_ in the context of the role they play. | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | ||||||||||
| scope | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" | |||||||||||
| web site | The CMBT is responsible for generating a communication strategy that will address stakeholders from executive management through system users and should include updating the progress of the activity on the IEA Architecture web site | TBD | F | "BUSINESS-FOCUS-AREA (TEAM INFORMATION)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" | |||||||||||
| Name | Name of the SYSTEM-COMP/ORGANIZATION-ROLE Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" | ||||||||||
| organization | The organization related to the SYSTEM-COMP/ORGANIZATION-ROLE | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" | ||||||||||
| role remarks | Any further description of the Role (Org or Person) as noted | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" | ||||||||||
| system component | The system component related to the SYSTEM-COMP/ORGANIZATION-ROLE | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" | ||||||||||
| version | The System Component Version | TBD | F | "COMPONENT_/ORGANIZATION-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "COMPONENT_/PERSON-ROLE" | |||||||||||
| Name | Role the individual plays in either managing or supporting the the subsystem | TBD | F | "COMPONENT_/PERSON-ROLE" | ||||||||||
| Person | The individual's name who is performing the role | TBD | F | "COMPONENT_/PERSON-ROLE" | ||||||||||
| Role Remarks | Field to further explain the nature of the role | TBD | F | "COMPONENT_/PERSON-ROLE" | ||||||||||
| System Component | That part of a system that provides business functionality | TBD | F | "COMPONENT_/PERSON-ROLE" | ||||||||||
| Version | Text that identifies the configuration management version of the System Component. | TBD | F | "COMPONENT_/PERSON-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "INVESTMENT-PROJECT/ORG-ROLE" | |||||||||||
| investment project | Name of the investment project | TBD | F | "INVESTMENT-PROJECT/ORG-ROLE" | ||||||||||
| name | TBD | F | "INVESTMENT-PROJECT/ORG-ROLE" | |||||||||||
| organizations | Individual performing the role associated to the investment | TBD | F | "INVESTMENT-PROJECT/ORG-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "INVESTMENT-PROJECT/PERSON-ROLE" | |||||||||||
| investment project | Name of the investment project | TBD | F | "INVESTMENT-PROJECT/PERSON-ROLE" | ||||||||||
| name | TBD | F | "INVESTMENT-PROJECT/PERSON-ROLE" | |||||||||||
| person | Individual performing the role associated to the investment | TBD | F | "INVESTMENT-PROJECT/PERSON-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "ORGANIZATION/PERSON-ROLE" | |||||||||||
| name | Intersection attribute that describes the association of organization to individuals name | TBD | F | "ORGANIZATION/PERSON-ROLE" | ||||||||||
| organization | The name of organization associated to the individual who is performing the role | TBD | F | "ORGANIZATION/PERSON-ROLE" | ||||||||||
| person | Individual playing the role | TBD | F | "ORGANIZATION/PERSON-ROLE" | ||||||||||
| role remarks | Free text field to describe the nature of the role. | TBD | F | "ORGANIZATION/PERSON-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "PROGRAM/PERSON-ROLE" | |||||||||||
| name | TBD | F | "PROGRAM/PERSON-ROLE" | |||||||||||
| person | TBD | F | "PROGRAM/PERSON-ROLE" | |||||||||||
| program | TBD | F | "PROGRAM/PERSON-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | |||||||||||
| organization | The organization related to the SUB-SYSTEM/ORGANIZATION-ROLE | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| role remarks | Any further description of the Role (Org or Person) as noted | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| sub system | The sub system related to the SUB-SYSTEM/ORGANIZATION-ROLE | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| sub system version | The sub system version related to the SUB-SYSTEM/ORGANIZATION-ROLE | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| system | The system related to the SUB-SYSTEM/ORGANIZATION-ROLE | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| system version | The system version related to the SUB-SYSTEM/ORGANIZATION-ROLE | TBD | F | "SUB-SYSTEM/ORGANIZATION-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "SYSTEM/ORGANIZATION-ROLE" | |||||||||||
| Name | The association of the organization to a system to support the establishment of how the individual and organization support the system | TBD | F | "SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| organization | The organization identified to support the system | TBD | F | "SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| role remarks | Free text field further describing the nature of relationship of the individual and organization to the system | TBD | F | "SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| system | the system that is to be supported by the organization and individual | TBD | F | "SYSTEM/ORGANIZATION-ROLE" | ||||||||||
| version | The Version of the System that this is linked to | TBD | F | "SYSTEM/ORGANIZATION-ROLE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Delete | TBD | F | "SYSTEM/PERSON-ROLE" | |||||||||||
| Name | An association describing the role of the individual to the system | TBD | F | "SYSTEM/PERSON-ROLE" | ||||||||||
| Person | The person performing the role in support of the IT system | TBD | F | "SYSTEM/PERSON-ROLE" | ||||||||||
| Role Remarks | Free text field further describing the nature of relationship of the individual to the system | TBD | F | "SYSTEM/PERSON-ROLE" | ||||||||||
| System | This describes the association of the system and the individual and the role they play in support of the system. | TBD | F | "SYSTEM/PERSON-ROLE" | ||||||||||
| Version | The Version of the System that this is linked to | TBD | F | "SYSTEM/PERSON-ROLE" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-DRIVER/ORGANIZATION | Updated by complex Matrix Business Driver to Organization. | T | F | F | "architectural status" columndefinition comment "comment date" name rowdefinition |
| BUSINESS-FOCUS/BUSINESS-DRIVER | Updated through Complex Matrix Business Focus Area to Business Driver. | F | F | F | "architectural status" "business driver category" columndefinition "description swot assessment" "mbt findings" name "rollout phase" rowdefinition stakeholders |
| BUSINESS-FOCUS/INTEGRATION | Should only be created through the business focus area which is to be the primary business focus area. | F | F | F | columndefinition name rowdefinition "touch point" |
| BUSINESS-FOCUS/OUTCOME | This associative entity BUSINESS-FOCUS/END-OUTCOME will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | "architectural status" "business focus area" "end outcome" "end outcome name" name "rollout phase" |
| BUSINESS-FOCUS/PRODUCT | Updated via Business Focus Area to Product Matrix. | F | F | F | "architectural status" columndefinition "level business objectives" "level description" "level target" name "rollout phase" rowdefinition |
| GENERIC-INDICATOR/MEASURE | Operationalized Measurement Indicators agencies use in the PRM will be informed and determined by the GPRA and budget planning process, PART assessments, and other drivers. This is the intersection between the OMB PRM and the DOI PRM. It is implemented as a complex matrix. | T | F | F | "generic measurement indicator" "intermediate outcome measure" "measurement area" "measurement category" name |
| GENERIC-MEASUREMENT-INDICATOR | Generic Measurement Indicators – The generic indicators, for example delivery time, that agencies then "operationalize" for their specific environment. Importantly, the Generic Measurement Indicators included in the PRM are merely starting points for agencies. In their FY 2005 Exhibit 300s, agencies "operationalize" the four Generic Measurement Indicators they propose to use for each major IT initiative classified as DME. Agencies are free to tailor these operationalized Measurement Indicators so that they fit the agency’s specific environment and the IT initiative’s specific goals. As agencies use the PRM over time, these Operationalized Measurement Indicators will evolve and comprise the actual and most useful contents of the PRM. The development of these will be more difficult in some cases than in others and the links between inputs and outcomes will not always be easy to define. For IT initiatives that support programs that have been subject to the PART, a useful starting point would be to use the PART key performance measures. | T | F | F | "end outcome measures" "intermediate outcome measures" "measurement area" "measurement category" name |
| MEASURE | A measurable indicator of the Intermediate Outcome that can be systematically tracked to assess progress made in achieving predetermined End Outcome goals and using such indicators to assess progress in achieving these goals. A measurement must be an Operationalized Measurement Indicator in the Mission and Business Results Measurement Area. The Operationalized Measurement Indicators agencies create should be determined by referencing the End outcome indicators identified in the DOI Strategic Plan. A Measure must fit within the three Measurement Categories of the Mission and Business Results Measurement Area of the PRM. These categories are Ser-vices for Citizens, Support Delivery of Services, and Management of Government Resources. This Measurement Area aligns with Measurement Areas described in the Business Reference Model Version 2.0. | T | F | F | comments "contributing organizations" "data point of contact" "data reported" "date last changed" description "goal leads" "key terms/definitions" "measure goal value" "measure goal value notes" "measure indicator" "measure type" "measurement process" name "prm measure area" "prm measure category" "prm measure sub area" "reporting frequency" "scope of the measure" |
| MEASUREMENT-AREA | Measurement Areas – The high-level organizing framework of the PRM that captures aspects of performance at the input, output, and outcome levels. The PRM includes six measurement areas: Mission and Business Results, Customer Results, Processes and Activities, Human Capital, Technology, and Other Fixed Assets. Human Capital and Other Fixed Assets will not be used in FY 2005 budget formulation. | T | F | F | "child measurement area categories" "measurement area type" name |
| MEASUREMENT-CATEGORY | Measurement Categories – Groupings within each Measurement Area that describe the attribute or characteristic to be measured. For example, the Mission and Business Results Measurement Area includes three Measurement Categories: Services for Citizens, Support Delivery of Services, and Management of Government Resources. | T | F | F | "child generic measurement indicator" "measurement area" name |
| MISSION-AREA | GPRA Program Activity (Mission Goal) This is the goal level used in bureau and office plans, sometimes referred to as the mission goal level in bureau plans. This level is not directly measurable. Interior crosswalks budget activities to the GPRA program activity level. In DEAR, MISSION-AREA lists the DOI Goal Names. Definition needs work. | T | F | F | description "end outcomes" name |
| OUTCOME | Project Performance Goals describe and support the Strategic Goal. Also known in the DOI Strategic Plan as the Long-Term Goal. There are two or more long-term Goals suppoing a DOI Strategic Goal. Long-Term Goal: The long-term goal expresses a desired result and is measured by one or more performance indicators. This is the 5-year goal level that is used in the strategic plan. Annual performance measures indicate the success in achieving the long-term goal. Definition needs work. | T | F | F | "abc work activities" department description "end outcome measures" "intermediate outcomes" name "outcome name" "outcome type" |
| PERFORMANCE-REFERENCE-MODEL | The PRM is a standardized framework to measure the performance of major IT initiatives and their contribution to program performance. This standardized framework has three main purposes: 1. Help produce enhanced IT performance information to improve strategic and daily decisionmaking; 2. Improve the alignment—and better articulate the contribution of—IT to business outputs and outcomes, thereby creating a clear "line of sight" to desired results; and 3. Identify performance improvement opportunities that span traditional organizational structures and boundaries. The PRM is driven by a legislative framework for IT performance consisting of the E-Government Act of 2002, the Clinger-Cohen Act of 1996, and the Government Performance and Results Act of 1993. The PRM also leverages 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 draft PRM was informed by what agencies are currently measuring through GPRA, Enterprise Architecture, IT Capital Planning and Investment Control, and PART assessment findings. Section 4 of this document provides more detail on how the PRM was developed. The PRM is structured around Measurement Areas, Measurement Categories, and Measurement Indicators. | T | F | F | name |
| STRATEGIC-PLAN | A document used by an organization to align its organization and budget structure with organizational priorities, missions, and objectives. In DEAR, STRATEGIC-PLAN lists the DOI Mission Area Names. | T | F | F | "as of date" "date of plan" description "end outcomes" "intermediate outcomes" "mission areas" "mission statement" name organization version "vision statement" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | As Is | TBD | T | LIST As Is To Be List As Is To Be Both NA Unkown | "BUSINESS-DRIVER/ORGANIZATION" | |||||||||
| columndefinition | ORGANIZATION | TBD | F | "BUSINESS-DRIVER/ORGANIZATION" | ||||||||||
| comment | Organizations comment about business driver. | TBD | F | "BUSINESS-DRIVER/ORGANIZATION" | ||||||||||
| comment date | Date comment captured | TBD | F | "BUSINESS-DRIVER/ORGANIZATION" | ||||||||||
| name | TBD | F | "BUSINESS-DRIVER/ORGANIZATION" | |||||||||||
| rowdefinition | BUSINESS-DRIVER | TBD | F | "BUSINESS-DRIVER/ORGANIZATION" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | As Is | TBD | T | As Is To Be Both NA Unknown | "BUSINESS-FOCUS/BUSINESS-DRIVER" | |||||||||
| business driver category | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | |||||||||||
| columndefinition | BUSINESS-DRIVER | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | ||||||||||
| description swot assessment | Property Description Labeled SWOT Assessment Will appear in the matrix cell. | Unknown | TBD | T | Strength Weakness Opportunity Threat Unknown NA | "BUSINESS-FOCUS/BUSINESS-DRIVER" | ||||||||
| mbt findings | MBT-FINDINGS associated to a BFA and BD | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | ||||||||||
| name | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | |||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | |||||||||||
| rowdefinition | BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" | ||||||||||
| stakeholders | TBD | F | "BUSINESS-FOCUS/BUSINESS-DRIVER" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| columndefinition | integrating business focus area BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/INTEGRATION" | ||||||||||
| name | TBD | F | "BUSINESS-FOCUS/INTEGRATION" | |||||||||||
| rowdefinition | primary business focus area BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/INTEGRATION" | ||||||||||
| touch point | Touchpoint (with Picklist) Potential Analyzed | Unknown | TBD | T | Potential Analyzed NA Unknown | "BUSINESS-FOCUS/INTEGRATION" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/OUTCOME" | ||||||||
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/END-OUTCOME | TBD | F | "BUSINESS-FOCUS/OUTCOME" | ||||||||||
| end outcome | The end outcome related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/OUTCOME" | ||||||||||
| end outcome name | Name of the BUSINESS-FOCUS/END-OUTCOME Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/OUTCOME" | ||||||||||
| name | Name of the BUSINESS-FOCUS/END-OUTCOME Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/OUTCOME" | ||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/OUTCOME" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | Architectural Status List | As Is | TBD | T | As Is To Be Both NA Unknown | "BUSINESS-FOCUS/PRODUCT" | ||||||||
| columndefinition | PRODUCT | TBD | F | "BUSINESS-FOCUS/PRODUCT" | ||||||||||
| level business objectives | 3 seperate properties for levels 1, 2, and 3. List Of Business Objective | TBD | F | "BUSINESS-FOCUS/PRODUCT" | ||||||||||
| level description | 3 seperate properties for levels 1, 2, and 3. | TBD | F | "BUSINESS-FOCUS/PRODUCT" | ||||||||||
| level target | 3 seperate properties for levels 1, 2, and 3. Target Implementation List | Unkonwn | TBD | T | Near Term Mid Term Long Term NA Unkonwn | "BUSINESS-FOCUS/PRODUCT" | ||||||||
| name | TBD | F | "BUSINESS-FOCUS/PRODUCT" | |||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/PRODUCT" | |||||||||||
| rowdefinition | BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/PRODUCT" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| generic measurement indicator | The generic measurement indicator related to the GENERIC-INDICATOR/INTR-MEASURE | TBD | F | "GENERIC-INDICATOR/MEASURE" | ||||||||||
| intermediate outcome measure | The intermediate outcome measure related to the GENERIC-INDICATOR/INTR-MEASURE | TBD | F | "GENERIC-INDICATOR/MEASURE" | ||||||||||
| measurement area | The measurement area related to the GENERIC-INDICATOR/INTR-MEASURE | TBD | F | "GENERIC-INDICATOR/MEASURE" | ||||||||||
| measurement category | The measurement category related to the GENERIC-INDICATOR/INTR-MEASURE | TBD | F | "GENERIC-INDICATOR/MEASURE" | ||||||||||
| name | Name of the GENERIC-INDICATOR/INTR-MEASURE | TBD | F | "GENERIC-INDICATOR/MEASURE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| end outcome measures | The end outcome measures related to the GENERIC-MEASUREMENT-INDICATOR | TBD | F | "GENERIC-MEASUREMENT-INDICATOR" | ||||||||||
| intermediate outcome measures | TBD | F | "GENERIC-MEASUREMENT-INDICATOR" | |||||||||||
| measurement area | The measurement area related to the GENERIC-MEASUREMENT-INDICATOR | TBD | F | "GENERIC-MEASUREMENT-INDICATOR" | ||||||||||
| measurement category | The measurement category related to the GENERIC-MEASUREMENT-INDICATOR | TBD | F | "GENERIC-MEASUREMENT-INDICATOR" | ||||||||||
| name | Name of the GENERIC-MEASUREMENT-INDICATOR | TBD | F | "GENERIC-MEASUREMENT-INDICATOR" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| comments | TBD | F | MEASURE | |||||||||||
| contributing organizations | Organizations that contributed to establishing and using this measure (primarily bureaus and offices within the department) | TBD | F | MEASURE | ||||||||||
| data point of contact | TBD | F | MEASURE | |||||||||||
| data reported | TBD | F | MEASURE | |||||||||||
| date last changed | TBD | F | MEASURE | |||||||||||
| description | The text description for the intermediate outcome goal. | TBD | F | MEASURE | ||||||||||
| goal leads | TBD | F | MEASURE | |||||||||||
| key terms/definitions | TBD | F | MEASURE | |||||||||||
| measure goal value | The quantifiable measure associated to the intermediate goal | TBD | F | MEASURE | ||||||||||
| measure goal value notes | Free text field containing notes that is associated to the intermediate outcome measure. | TBD | F | MEASURE | ||||||||||
| measure indicator | A measurable indicator of the Intermediate Outcome that can be systematically tracked to assess progress made in achieving predetermined End Outcome goals and using such indicators to assess progress in achieving these goals. A measurement must be an Operationalized Measurement Indicator in the Mission and Business Results Measurement Area. The Operationalized Measurement Indicators agencies create should be determined by referencing the End outcome indicators identified in the DOI Strategic Plan. A Measure must fit within the three Measurement Categories of the Mission and Business Results Measurement Area of the PRM. These categories are Ser-vices for Citizens, Support Delivery of Services, and Management of Government Resources. This Measurement Area aligns with Measurement Areas described in the Business Reference Model Version 2.0. Measurement Components: Costs, Benefits, Schedules, Risks, Alignment, Portfolio, Statistical Projections Legislative Mandates, Organizational constraints, Budgetary Constraints IT Efficiency and Effectiveness Metrics Best Practice Benchmarks | TBD | F | MEASURE | ||||||||||
| measure type | Required property denoting end or intermediate measure. | TBD | T | END INTERMEDIATE | MEASURE | |||||||||
| measurement process | TBD | F | MEASURE | |||||||||||
| name | The OMB PRM Parent Measurement Generic Indicator that this Operationalized Measure relates to | TBD | F | Alpha-numeric | MEASURE | |||||||||
| prm measure area | The OMB PRM Parent Measurement Area that this Operationalized Measure relates to | TBD | F | MEASURE | ||||||||||
| prm measure category | The OMB PRM Parent Measurement Category that this Operationalized Measure relates to | TBD | F | MEASURE | ||||||||||
| prm measure sub area | The DOI PRM sub-Measurement Area that this Operationalized Measure relates to | TBD | F | MEASURE | ||||||||||
| reporting frequency | TBD | F | MEASURE | |||||||||||
| scope of the measure | TBD | F | MEASURE |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child measurement area categories | The child measurement area categories related to the MEASUREMENT-AREA | TBD | F | "MEASUREMENT-AREA" | ||||||||||
| measurement area type | The measurement area type related to the MEASUREMENT-AREA | TBD | T | VALUE Mission and Business Results VALUE Customer Results VALUE Processes and Activities VALUE Technology | "MEASUREMENT-AREA" | |||||||||
| name | Name of the MEASUREMENT-AREA | TBD | F | "MEASUREMENT-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child generic measurement indicator | The child generic measurement indicator related to the MEASUREMENT-CATEGORY | TBD | F | "MEASUREMENT-CATEGORY" | ||||||||||
| measurement area | The measurement area related to the MEASUREMENT-CATEGORY | TBD | F | "MEASUREMENT-CATEGORY" | ||||||||||
| name | Name of the MEASUREMENT-CATEGORY | TBD | F | "MEASUREMENT-CATEGORY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| description | Strategic Goal: Describes the Mission Area Goal, in the strategic Plan this is the Strategic Goal. | TBD | F | Alpha-numeric | "MISSION-AREA" | |||||||||
| end outcomes | The OUTCOME type END related to the MISSION-AREA | TBD | F | "MISSION-AREA" | ||||||||||
| name | This is the goal level used in bureau and office plans, sometimes referred to as the mission goal level in bureau plans. This level is not directly measurable. Interior crosswalks budget activities to the GPRA program activity level. [GPRA Program Activity (Mission Goal)] In DEAR, MISSION-AREA lists the DOI Goal Names. | TBD | F | Alpha-numeric | "MISSION-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| abc work activities | Activity Based Costing a means to identify and track the work and its associated costs performed by an organization | TBD | F | OUTCOME | ||||||||||
| department | True if is a department level outcome. Should only be mapped to strat plan if is department level. | TBD | F | OUTCOME | ||||||||||
| description | Free text field to describe the end outcome more fully | TBD | F | OUTCOME | ||||||||||
| end outcome measures | The MEASURE type END related to the OUTCOME | TBD | F | OUTCOME | ||||||||||
| intermediate outcomes | The MEASURE type INTERMEDIATE related to the OUTCOME | TBD | F | OUTCOME | ||||||||||
| name | Name of the END-OUTCOME | TBD | F | OUTCOME | ||||||||||
| outcome name | Project Performance Goals describe and support the Strategic Goal. Also known in the DOI Strategic Plan as the Long-Term Goal. There are two or more long-term Goals supporting a DOI Strategic Goal. Long-Term Goal The long-term goal expresses a desired result and is measured by one or more performance indicators. This is the 5-year goal level that is used in the strategic plan. Annual performance measures indicate the success in achieving the long-term goal. Outputs/Outcomes Calculation Vectors (6 dimensions): People, Process, Technology, Fixed Assets, Service Levels, Time Performance Scorecards Dashboards | TBD | F | Alpha-numeric | OUTCOME | |||||||||
| outcome type | Required field denoting end or intermediate outcome. | TBD | T | END INTERMEDIATE | OUTCOME |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | Name of the PERFORMANCE-REFERENCE-MODEL | TBD | F | "PERFORMANCE-REFERENCE-MODEL" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| as of date | The date that this version of the Strategic Plan was released | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| date of plan | The date range that this Strategic Plan represents | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| description | Small Description of the Mission Area from the DOI Strategic Plan. | TBD | F | Alpha-numeric | "STRATEGIC-PLAN" | |||||||||
| end outcomes | TBD | F | "STRATEGIC-PLAN" | |||||||||||
| intermediate outcomes | TBD | F | "STRATEGIC-PLAN" | |||||||||||
| mission areas | The mission areas related to the STRATEGIC-PLAN | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| mission statement | A mission is the enduring, chartered, long-term goal(s) of an organization. At the DOI, it is the mission statement that guides the DOI Strategic Goals from the Strategic Plan. From ITIM GAO 05/00 Vol 1 Doc. Example: The mission of the DOI is to protect and provide access to our Nation's natural and cultural heritage and honor our trust responsibilities to Indian Tribes and our commitments to island communities | TBD | F | Alpha-numeric | "STRATEGIC-PLAN" | |||||||||
| name | Name of the strategic plan | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| organization | Organization that produced this Strategic Plan | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| version | The Version of the Strategic plan | TBD | F | "STRATEGIC-PLAN" | ||||||||||
| vision statement | The Vision Statement that is within this Strategic Plan | TBD | F | "STRATEGIC-PLAN" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| AD-HOC-ASSOCIATION | An association line able to be drawn between various elements. | T | F | F | |
| BUSINESS-FOCUS/DATA-SUB-AREA | Associative between these two objects | F | F | F | "architectural status" "data subject area" name |
| BUSINESS-FOCUS/INFO-CLASS | Associative between these two objects | F | F | F | "architectural status" columndefinition columndefinitionkey1 name "rollout phase" rowdefinition |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/DATA-SUB-AREA" | ||||||||
| data subject area | The data subject area related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/DATA-SUB-AREA" | ||||||||||
| name | Name of the BUSINESS-FOCUS/DATA-SUB-AREA Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/DATA-SUB-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | Architectural Status List | As Is | TBD | T | As Is To Be Both NA Unknown | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||
| columndefinition | INFORMATION-CLASS | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||||
| columndefinitionkey1 | INFORMATION-CLASS Data Subject Area | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||||
| name | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | |||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | |||||||||||
| rowdefinition | BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-FOCUS/FUNCT-ACTIVITY | This associative entity BUSINESS-FOCUS/FUNCT-ACTIVITY will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | "architectural status" "business focus area" "function activity" "modes of delivery" name "rollout phase" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/FUNCT-ACTIVITY" | ||||||||
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/FUNCT-ACTIVITY | TBD | F | "BUSINESS-FOCUS/FUNCT-ACTIVITY" | ||||||||||
| function activity | The function activity related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/FUNCT-ACTIVITY" | ||||||||||
| modes of delivery | This is used to relate modes of delivery sub functions when an association is made from the business focuse area to a service for citizen function activity or sub function. | TBD | F | "BUSINESS-FOCUS/FUNCT-ACTIVITY" | ||||||||||
| name | Name of the BUSINESS-FOCUS/FUNCT-ACTIVITY Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/FUNCT-ACTIVITY" | ||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/FUNCT-ACTIVITY" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-FOCUS/INVESTMENT | This associative entity BUSINESS-FOCUS/INVESTMENT will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | "architectural status" "business focus area" "investment project" name "rollout phase" |
| EXHIBIT-53 | A data container for miscellaneous information required by the Exhibit 53. At this time, it only contains the exhibit53-name. If this is the same as the Exhibit 53 Investment Title, that information is already captured in INVESTMENT(PROJECT) investment-title. I believe this is a hold over from some earlier modeling when we were representing reports as objects. | T | F | F | exhibit53-name |
| INVESTMENT/MBT-RECOMMENDATION | Updated via Matrix Investment Project to MBT Recommendation Cell property is Investment Status. | F | F | F | "architectural status" columndefinition "investment status" name "roll out phase" rowdefinition |
| INVESTMENT-PHASE | Will either be Exhibit 300 or 300-1. | T | F | F | actual-exit-date name target-exit-date |
| INVESTMENT-PROJECT | An acquisition activity associated with the procuring and management of an asset or service throughout the asset's or service's life-cycle. Capital projects represent investments associated with the acquisition of capital assets and the management of that asset through its life-cycle after the initial acquisition. An IT Investment represents a special type of capital project (or investment). An Investment for an IT project has a corresponding Exhibit 300 and is represented by a summary line on an Exhibit 53. A Program may sponsor many Investments, but an Investment may only have one sponsoring Program. Many Programs, however, may support an Investment by contributing funds, and a Program may support many Investments. | F | F | F | "budget year" "curernt upi code" egov gpea "home land security" "investment load comment" "investment phase" "investment title" "investment type" name "omb investment type" "percent financial" "percent security" "planned completion date" "previous investment title" "previous upi code" |
| INVESTMENT-PROJECT (OTHER RELATIONS) | Sub-Attributes of INVESTMENT-PROJECT; Relationships to Organizations, People, or Programs | F | F | F | "business focus areas" "contributing organizations" "contributing programs" "mbt recommendations" "organization roles" "project investment roles" "sponsoring program" |
| INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) | Sub-Attributes of INVESTMENT-PROJECT; Relationships to FEA Reference Models | F | F | F | "associated brm sub-functions" "associated prm - end outcomes" "associated prm - intermediate outcomes" "associated srm - components" "associated trm - standards" "primary brm sub-function" |
| INVESTMENT-PROJECT (SOA) | Sub-Attributes of INVESTMENT-PROJECT; Relationships to SOA Artifacts produced | F | F | F | "enterprise level solutions presentation" "final solution requirements document" "findings and recommendations presentation" "implemented solution" "ooa application security group requirements" "ooa architectural decisions" "ooa glossary" "ooa non functional requirements" "ooa requirements matrix" "ooa test strategy" "ooa user requirements" "ooc backup and recovery plan" "ooc build procedures" "ooc deployable components" "ooc help manual" "ooc operations guide" "ooc source code" "ooc test results" "ooc test specification" "ood acceptance test plan" "ood application resource descriptions" "ood deployment plan" "ood detailed test plan" "ood enterprise information and data stores definition" "ood persistence design specifications" "ood service descriptions" "ood ui specification and navigation detail" "policy memo(s)" "proposal evaluation criteria" "soa team" "systems development compliance document" "training strategy/curriculum" |
| PROGRAM | A Program, from a budget perspective, accounts for overhead, administration, operational, IT, and other costs that are needed achieve the stated program goals. It is very generalized concept that typically aligns with mission areas, although multiple mission areas can be addressed by a Program. A Program typically has goals, but may not have a well defined end state. In other words, it can represent a set of on-going activites. A Program sponsors and directs funding for IT Projects associated with the Program. A Program does not have to have an associated IT Project, but it can sponsor or provide funding support to many IT Projects. An IT Project may have many supporting Programs that contribute fundings, but only one sponsoring Program. Not all DOI Bureaus use the concept of Program. (This definition is derived from a conversation on 7/30/2003 with DOI OCIO budget representatives and internal discussions.) | T | F | F | name "program roles" "sponsoring organization" "supporting organizations" url |
| STATUS | Generic Status Container. Consider categorization of Status. Examples: System Status, CPIC Status, C& A Review Status. Why do we need a generic STATUS container? We have investment-life-cycle-stage in BUSINESS-CASE-EXHIBIT-300 (moved from CPIC-STATUS), C-&-A-PHASE-ACTIVITY activity-status, & SYSTEM Operational Status & system-life-cycle-phase. What other system, CPIC, and C&A review statuses do we need or have requirements for? | T | F | F | status-type status-value |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/INVESTMENT" | ||||||||
| business focus area | The Business Focus Area specific to this relationship of BUSINESS-FOCUS/INVESTMENT | TBD | F | "BUSINESS-FOCUS/INVESTMENT" | ||||||||||
| investment project | The investment project related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/INVESTMENT" | ||||||||||
| name | Name of the BUSINESS-FOCUS/INVESTMENT Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/INVESTMENT" | ||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/INVESTMENT" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| exhibit53-name | The name of the Exhibit 53 if one exists. If this is the Investment Title in an Exhibit 53, then the data already exists in the INVESTMENT PROJECT) entity. | TBD | F | Alpha-numeric | "EXHIBIT-53" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | As Is | TBD | T | As Is To Be Both NA Unknown | "INVESTMENT/MBT-RECOMMENDATION" | |||||||||
| columndefinition | MBT-RECOMMENDATION | TBD | F | "INVESTMENT/MBT-RECOMMENDATION" | ||||||||||
| investment status | Unknown | TBD | T | VALUE New VALUE Recommended VALUE Rejected VALUE Approved VALUE In Progress VALUE Implemented VALUE NA VALUE Unknown | "INVESTMENT/MBT-RECOMMENDATION" | |||||||||
| name | TBD | F | "INVESTMENT/MBT-RECOMMENDATION" | |||||||||||
| roll out phase | TBD | F | "INVESTMENT/MBT-RECOMMENDATION" | |||||||||||
| rowdefinition | INVESTMENT-PROJECT | TBD | F | "INVESTMENT/MBT-RECOMMENDATION" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| actual-exit-date | Captures the actual decision date (CPIC) when an investment is permitted to go to the next phase. | TBD | F | "INVESTMENT-PHASE" | ||||||||||
| name | Name of the INVESTMENT-PHASE | TBD | F | "INVESTMENT-PHASE" | ||||||||||
| target-exit-date | Date the investment is to move to the subsequent phase of the investment cycle | TBD | F | "INVESTMENT-PHASE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| budget year | The fiscal year corresponding to the budget represented by this record of investment data. Updated on Import from eCPIC | TBD | F | Alpha-numeric | "INVESTMENT-PROJECT" | |||||||||
| curernt upi code | The UPI currently associated to the project | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| egov | Is this an eGov investment - Yes, No, or Probably (Target) | TBD | F | Yes No Probable | "INVESTMENT-PROJECT" | |||||||||
| gpea | Yes/No - whethere this system is covered by GPEA | TBD | F | Type Code Name GPEA Y Yes, system covered by GPEA GPEA N No, system not covered by GPEA | "INVESTMENT-PROJECT" | |||||||||
| home land security | As noted in Ex. 300 | TBD | F | Type Code Name HomelandDef N No, system does not support Homeland Security goals HomelandDef Y Yes, system supports Homeland Security goals JFMIPConfStatus X Not applicable | "INVESTMENT-PROJECT" | |||||||||
| investment load comment | Noted on Import from eCPIC | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| investment phase | The current CPIC investment phase for this investment. The phases are: Pre-Select, Select, Control, Evaluate, and Steady State. Pre-Select – Initial Concept Phase in the Ex. 300. Select – Screen, Rank, and Progress. Planning Phase in the Ex. 300. Control – Monitor Progress and Take Corrective Action. Full Acquisition Phase in the Ex. 300. Evaluate – Conduct Reviews, Make Adjustments, Apply Lessons Learned Steady-State Phase in the Ex. 300. Steady-State – See Evaluate. Steady-state Phase in the Ex. 300. | TBD | T | Pre-Select Select Control Evaluate Steady-State Mixed-Lifecycle NA Unknown | "INVESTMENT-PROJECT" | |||||||||
| investment title | The name of the investment as documented on the Exhibit 300 business case. Corresponds to the Exhibit 300 Name of Investment field. | TBD | F | Alpha-numeric | "INVESTMENT-PROJECT" | |||||||||
| investment type | Saved from Prior year loads or if the same, original name | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| name | Name of the investment project | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| omb investment type | Updated on Import from eCPIC | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| percent financial | he estimated percentage of the total IT investment budget authority associated with the financial components of an Investment listed on Exhibit 53. Only reported for the Investment summary line on the Exhibit 53. See the financial system definition in OMB Circular A-11, Section 53, for a description of financial functions. DME refers to the program cost for new investments, changes or modifications to existing systems that improve capability or performance, changes mandated by Congress or agency leadership, personnel costs for project (investment) management, and direct support. This amount equals the sum of amounts reported for planning and full acquisition of that system in exhibit 300. Updated on Import from eCPIC | TBD | F | Percentage | "INVESTMENT-PROJECT" | |||||||||
| percent security | The estimated percentage of the total investment for budget year associated with IT security for a specific investment listed on Exhibit 53. Only reported for the Investment summary line on the Exhibit 53. Federal agencies must consider the criteria specified in OMB Circular A-11, Section 53, to determine security costs for a specific IT investment. Updated on Import from eCPIC | TBD | F | Percentage | "INVESTMENT-PROJECT" | |||||||||
| planned completion date | Updated on Import from eCPIC | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| previous investment title | Saved from Prior year loads or if the same, original name | TBD | F | "INVESTMENT-PROJECT" | ||||||||||
| previous upi code | Saved from Prior year loads or if the same, original name | TBD | F | "INVESTMENT-PROJECT" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business focus areas | complex matrix to BUSINESS-FOCUS-AREA | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| contributing organizations | ORGANIZATION | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| contributing programs | PROGRAM | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| mbt recommendations | MBT-RECOMMENDATION | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| organization roles | INVESTMENT-PROJECT/ORGANIZATION-ROLE | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| project investment roles | INVESTMENT-PROJECT/PERSON-ROLE | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" | ||||||||||
| sponsoring program | PROGRAM | TBD | F | "INVESTMENT-PROJECT (OTHER RELATIONS)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| associated brm sub-functions | The OMB BRM business reference model sub-functions that are associated to the investment | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" | ||||||||||
| associated prm - end outcomes | The associated OUTCOME type END from the PRM related to the investment | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" | ||||||||||
| associated prm - intermediate outcomes | The associated OUTCOME type INTERMEDIATE from the PRM related to the investment | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" | ||||||||||
| associated srm - components | SRM-SERVICE-COMPONENT | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" | ||||||||||
| associated trm - standards | TRM-SERVICE-STANDARD | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" | ||||||||||
| primary brm sub-function | The associated primary sub-function from the BRM | TBD | F | "INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| enterprise level solutions presentation | TBD | F | "INVESTMENT-PROJECT (SOA)" | |||||||||||
| final solution requirements document | TBD | F | "INVESTMENT-PROJECT (SOA)" | |||||||||||
| findings and recommendations presentation | Task 5 Outputs • Recommendations and Findings Presentation | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| implemented solution | TBD | F | "INVESTMENT-PROJECT (SOA)" | |||||||||||
| ooa application security group requirements | Link To Document (probably use a req. mgmt tool) WP Desc.: A description of the required security structure and data regarding users, groups, rights, etc. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa architectural decisions | Link to Document WP Desc.: A record of important decisions about any aspect of the architecture including the structure of the system, the provision and allocation of function, and adherence to standards. Although this work product is initially created during Analysis and maintained during Design, all Architectural Decisions must be resolved by the end of Design. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa glossary | Link to Document WP Desc.: A definition of acronyms and terms encountered during the project. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Optional | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa non functional requirements | Link To Document WP Desc.: A specification of the qualitative and other nonfunctional requirements or conditions that the system must satisfy. Tool: MS-Word or MS-Excel Responsible: Solution Architecture Team Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa requirements matrix | Link To Document (probably use a req. mgmt tool) WP Desc.: A tracking matrix which details all the requirements of the system, including their type, priority, status, etc. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa test strategy | Link To Document (probably use a req. mgmt tool) WP Desc.: A high-level description of major testing Tasks and approach to be used to ensure that the critical attributes of the system are tested adequately. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooa user requirements | Link To Document WP Desc.: A description of the business requirements for an application, including the capabilities and features it must support. These requirements must be from a business perspective. Tool: MS-Word Responsible: Solution Architecture Team Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc backup and recovery plan | Link to Document WP Desc.: A description for backing up the application data Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc build procedures | Link to Document WP Desc.: A description of how to generate an executable copy of the system. This may include such items as which files are required, which links must be in place, which libraries are accessed, and the sequence of steps required to generate the system, etc. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc deployable components | Link to Document WP Desc.: The primary software deliverables for a system Tool: Project-Dependent Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc help manual | Link to Document WP Desc.: A description of the system’s functions Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc operations guide | Link to Document WP Desc.: A depiction of the processes required in order to support the system in the production environment. Includes details regarding normal operation Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc source code | Link to Document WP Desc.: The actual implementation of the system design in the chosen programming language(s). Tool: Project-Dependent Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc test results | Link to Document WP Desc.: A description of the outcomes of a specific test execution, and comparison of the actual test results to the expected results from the test case. It identifies and documents any variances that indicate further analysis is required.. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ooc test specification | Link to Document WP Desc.: A set of documents that define and describe the actual test architecture Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood acceptance test plan | Link to Document WP Desc.: A description of the steps the customer will use to verify that the constructed system satisfies the stated requirements. The plan describes clearly and fully how to set up the test and the acceptable system behaviors in response to the test. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood application resource descriptions | Link to Document WP Desc.: A description of resources (property files, etc.) used by an application, including their purpose, contents, and physical (file) names. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood deployment plan | Link to Document WP Desc.: A description of the organization, strategy, resources, and methods used to deploy the new application at customer sites. It provides a detailed schedule of events, expected project duration, persons responsible, and event dependencies required to ensure successful cut-over to the new system. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood detailed test plan | Link to Document WP Desc.: A description created for each level of testing identified as necessary in the Test Strategy. Each plan identifies the scope of testing for that level, functions/features to be tested, the testing Steps to be performed, and the personnel responsible for each Step. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood enterprise information and data stores definition | Link to Document WP Desc.: A graphical and text representation of the major data sources used by the system. For each source, it includes a description plus detail on the characteristics of the source, such as transactional requirements, performance/availability, sharing/locking, security, etc. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood persistence design specifications | Link to Document WP Desc.: A description of how all of the persistence services will be fulfilled for the system. For each service, it contains detail on the Persistence Contract (input), associated Persistence Object, return/result (Persistence Object Façade), data source specifics such as table/columns or file/field locations, and custom query info. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood service descriptions | Link to Document WP Desc.: A collection of information that defines the purpose of a service, along with detail on how to interact with it. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| ood ui specification and navigation detail | Link to Document WP Desc.: A description of all Application Interface components (this is applicable to all types of Application Clients [including, but not limited to, those created with JSPs, HTML, Java Swing, etc.] and Application Agents [servlets]) including a depiction of screen appearance, input fields, session data usage, exception handling, and navigational destinations. Tool: MS-Word Responsible: Developer Usage: Reqd | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| policy memo(s) | TBD | F | "INVESTMENT-PROJECT (SOA)" | |||||||||||
| proposal evaluation criteria | TBD | F | "INVESTMENT-PROJECT (SOA)" | |||||||||||
| soa team | ORGANIZATION | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| systems development compliance document | Task 3 Outputs • Systems Development Compliance Document / Matrix (doc link) | TBD | F | "INVESTMENT-PROJECT (SOA)" | ||||||||||
| training strategy/curriculum | TBD | F | "INVESTMENT-PROJECT (SOA)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | The unique name for a DOI Program. | TBD | F | Alpha-numeric | PROGRAM | |||||||||
| program roles | Program to person role. | TBD | F | PROGRAM | ||||||||||
| sponsoring organization | An organization that provides the role of sponsor for an investment | TBD | F | PROGRAM | ||||||||||
| supporting organizations | Organizations who are not directly responsible for but play an important role with respect to the investment or system. | TBD | F | PROGRAM | ||||||||||
| url | A reference URL where additional information may be found about the Program. | TBD | F | Alpha-numeric | PROGRAM |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| status-type | TBD | TBD | F | STATUS | ||||||||||
| status-value | TBD | TBD | F | STATUS |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| ARCHITECTURAL-PATTERN | Symbol used on the System Interface decomposition to represent a pattern overlay for networks. | T | F | F | "anti pattern" "child patterns" name |
| BUSINESS-FOCUS/MBT-STATUS | Look up table for MBT Status where Business Focus area is NULL. Should be set list of status choices when added to BFA become unique to that BFA. | F | F | F | business-focus-area name "status begin date" "status comment" "status end date" |
| BUSINESS-FOCUS-AREA | A BFA is a logical grouping of business areas and/or sets of interrelated business functions that are currently serving the business. For example, within the DOI OCIO office, the CPIC Planning, Policy Development and Enterprise Architecture (EA) are three of its major functions. The establishment of a BFA for the OCIO, might only include EA and CPIC given their strong demand for common information and possibilities to improve business processes. | F | F | F | "blueprint scope" "business focus area type" "Data Quality Attributes" "Default Authorization Group" "main point of contact" "managing partner" name |
| BUSINESS-FOCUS-AREA (ANALYSIS) | Sub-Attributes for the Business Focus Area; Captures the Analysis Summary and Supporting artifacts links delivered as part of this blueprint | T | F | F | "business results score" "citizen and market score" "executive summary" "funding strategy" "highlevel findings summary" "human resource score" "impact statement" "implementation plan" "knowledge management score" "leadership score" "mbt criterion scoring" "mbt findings" "process management score" "risk management plan" "sequencing plan" "strategic planning score" "total score" |
| BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) | Sub-Attributes for the Business Focus Area; Captures metadata related to the transformation and modernization status of this blueprint | T | F | F | accomplishments "blueprint status" "irb priority" "issues/challlenges" "mbt status" "milestones / budgeted or required funds" overview "quantitative data sources" "quantitative data sources text" "record of decision" |
| BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) | Sub-Attributes for the Business Focus Area; Captures links to the BPR efforts related to this blueprints | T | F | F | "bprt background" "bprt charter" "bprt meeting minutes" "bprt meeting presentations" "bprt mission" "bprt next meeting" "bprt organization" "bprt scope" |
| BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION) | Sub-Attributes for the Business Focus Area; Captures vision and mission blurbs and links | T | F | F | "business focus area description" "business mission" "business vision" "candidate ideas" challenges "due dilligence" "top priority ideas" "values and benefits" |
| BUSINESS-FOCUS-AREA (LINE OF SIGHT) | Sub-Attributes for the Business Focus Area; Identifies the objectives, products, services, functions, data, and technologies involved in this blueprint | T | F | F | business-drivers "end outcomes" "function activities" "information classes" "lines of business" products "service components" "technical service categories" |
| BUSINESS-FOCUS-AREA (PROTFOLIO) | Sub-Attributes for the Business Focus Area; Systems and Investments that are part of this blueprint | T | F | F | enterprise "enterprise components" "investment projects" organizations persons "system inventories" "system inventory roles" |
| ISSUE | None | T | F | F | "issue status" name |
| MBT-CATEGORY | See MBT Blueprint Step 5 for Categorization of Findings and Recommendations | T | F | F | "child mbt categories" name "parent mbt category" |
| MBT-CRITERIA | See MBT Blueprint Step 5 for Criteria guidance of Findings and Recommendations | T | F | F | name type |
| MBT-CRITERIA/BUSINESS-FOCUS | Associative between these two objects | F | F | F | "business focus area" "mbt criteria" "mbt issues" name rationale score |
| MBT-CRITERIA/SYSTEM | Associative between these two objects | F | F | F | "mbt criteria" "mbt issues" name rationale score system "system version" |
| MBT-FINDING | See MBT Blueprint Step 5 for Criteria on Blueprint Findings | F | F | F | "business drivers" "mbt categories" "mbt recomendations" name "stakeholder categories" |
| MBT-RECOMENDATION-CATEGORY | See MBT Blueprint Step 5 for Categorization of Recommendations | T | F | F | "child mbt recomendation categories" name "parent mbt recomendation category" |
| MBT-RECOMMENDATION | See MBT Blueprint Step 5 for Criteria on Blueprint Recommendations | F | F | F | "best practice classification" "business case" "child recommendations" "dependant recommendations" "end outcomes" "fy(04) o&m funding" "intermediate outcomes" "mbt recomendation category" "mbt tactical areas" name "planning period" priority "protfolio manager prioritization" "recomendation type" "tactical solution - cost estimate" "tactical solution - level of effort" |
| MBT-RECOMMENDATION/MBT-STATUS | Look up table for MBT Status where MBT Recommendation is NULL. Should be set list of status choices when added to BFA become unique to that Recommendation. | F | F | F | name recommendation "status begin date" "status comment" "status end date" |
| MBT-STATUS | Captures the Status of what MBT Step this blueprint or business focus area is in | T | F | F | name |
| MBT-TACTICAL-AREA | T | F | F | name | |
| RECOMENDATION-CATEGORY | None | T | F | F | name |
| ROLLOUT-PHASE | Look up table to determine phase for imiplementation or phase out. | T | F | F | Description Name |
| STAKEHOLDER-CATEGORY | Existing SA Definition Type | T | F | F | name "stakeholder type" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| anti pattern | TBD | F | "ARCHITECTURAL-PATTERN" | |||||||||||
| child patterns | List of ARCHITECTURAL-PATTERN is child in. | TBD | F | "ARCHITECTURAL-PATTERN" | ||||||||||
| name | TBD | F | "ARCHITECTURAL-PATTERN" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business-focus-area | TBD | F | "BUSINESS-FOCUS/MBT-STATUS" | |||||||||||
| name | TBD | F | "BUSINESS-FOCUS/MBT-STATUS" | |||||||||||
| status begin date | TBD | F | "BUSINESS-FOCUS/MBT-STATUS" | |||||||||||
| status comment | TBD | F | "BUSINESS-FOCUS/MBT-STATUS" | |||||||||||
| status end date | TBD | F | "BUSINESS-FOCUS/MBT-STATUS" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| blueprint scope | Blueprint Scope List | Bureau/Office | TBD | T | Cross-Agency Department Bureau/Office NA Unknown | "BUSINESS-FOCUS-AREA" | ||||||||
| business focus area type | Business Focus Area Type List | Core Functional Area | TBD | T | Core Functional Area Management Functional Area Support Functional Area Service Area NA Unknown | "BUSINESS-FOCUS-AREA" | ||||||||
| Data Quality Attributes | TBD | F | "BUSINESS-FOCUS-AREA" | |||||||||||
| Default Authorization Group | Used to determine what Authorization is granted on default when looking up the managing organization. The group will be kept in LDAP and the repositories group manager (i.e. in System Architect v10.3, will be kept in the Catalog Manager and synchronized with names in Active Directory on a MS platform) | TBD | F | <Managing Organization>_Users, _Report, _Security_Managers, etc. | "BUSINESS-FOCUS-AREA" | |||||||||
| main point of contact | One of PERSON_ | TBD | F | "BUSINESS-FOCUS-AREA" | ||||||||||
| managing partner | One of ORGANIZATION | TBD | F | "BUSINESS-FOCUS-AREA" | ||||||||||
| name | TBD | F | "BUSINESS-FOCUS-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business results score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| citizen and market score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| executive summary | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| funding strategy | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| highlevel findings summary | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| human resource score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| impact statement | For example, if a recommendation requires coordinating several organizations to support the project, obtaining committed resources from these areas may be a risk. The team will need to develop a mitigation strategy and alternatives for all the risks they identify. Additionally, the implementation may have impacts on the current business procedures, policy, human resources, organizational structure, organizational relationships or program funding sources. These items will need to be developed into a change management plan with associated strategies to facilitate the project implementation transition. | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | ||||||||||
| implementation plan | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| knowledge management score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| leadership score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| mbt criterion scoring | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| mbt findings | MBT-FINDINGS | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | ||||||||||
| process management score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| risk management plan | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| sequencing plan | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| strategic planning score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" | |||||||||||
| total score | TBD | F | "BUSINESS-FOCUS-AREA (ANALYSIS)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| accomplishments | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | |||||||||||
| blueprint status | Blueprint status list | Not Started | TBD | T | Not Started 1 - Vision 2 - Inventory 3 - Analysis 4 - Draft 5 - Final/Maintenance | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | ||||||||
| irb priority | Priority that IRB places on the blueprint for this BFA. | Unknown | TBD | T | High Medium Low NA Unknown | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | ||||||||
| issues/challlenges | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | |||||||||||
| mbt status | Complete list of BUSINESS-FOCUS/MBT-STATUS for capturing status and comments. | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | ||||||||||
| milestones / budgeted or required funds | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | |||||||||||
| overview | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | |||||||||||
| quantitative data sources | If there are quantitative data sources like work volumes, actual costs, number of human resources involved, process metrics, or capital investments, the team should try to use them to support the prioritization. Additionally, if there are strategic drivers like Government Performance Results Act (GPRA), Government Paperwork Elimination Act (GPEA), E-Government or auditing and oversight factors that are exerting pressure on the business, they should be discussed in the context of prioritization. | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | ||||||||||
| quantitative data sources text | If there are quantitative data sources like work volumes, actual costs, number of human resources involved, process metrics, or capital investments, the team should try to use them to support the prioritization. Additionally, if there are strategic drivers like Government Performance Results Act (GPRA), Government Paperwork Elimination Act (GPEA), E-Government or auditing and oversight factors that are exerting pressure on the business, they should be discussed in the context of prioritization. | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" | ||||||||||
| record of decision | If the IRB approves the proposal, the official Record of Decision (ROD) needs to be communicated to the extended business and architecture communities through an official memorandum. | TBD | F | "BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bprt background | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt charter | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt meeting minutes | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt meeting presentations | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt mission | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt next meeting | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt organization | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" | |||||||||||
| bprt scope | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business focus area description | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | |||||||||||
| business mission | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | |||||||||||
| business vision | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | |||||||||||
| candidate ideas | The presentation should expound on the top priority idea but also discuss the other candidate ideas. | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | ||||||||||
| challenges | The BFA should be generated by interacting with the vested business community’s participants to identify their most significant obstacles or challenges to serving their customers or achieving their program’s performance goals and objectives. Simple questionnaires, brainstorming or visioning exercises often produce a valuable set of ideas to support this discovery. | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | ||||||||||
| due dilligence | The architect should research the PART, e-CPIC, DEAR, E-government initiatives and other DOI IEA projects to develop insight into related efforts. The effort should also strongly consider GAO and OMB influences. | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | ||||||||||
| top priority ideas | The presentation should expound on the top priority idea but also discuss the other candidate ideas. Identify and define the key business problems and functional areas that need to be addressed within their sphere of influence | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" | ||||||||||
| values and benefits | The presentation’s message should focus on explaining the potential value and benefits of the recommendation to the organization’s future | TBD | F | "BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business-drivers | Complex matrix to BUSINESS-DRIVER | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| end outcomes | Complex Matrix to END-OUTCOMES | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| function activities | Complex Matrix to FUNCTION-ACTIVITY | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| information classes | Complex Matrix to INFORMATION-CLASS | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| lines of business | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | |||||||||||
| products | Complex matrix to PRODUCT | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| service components | Complex Matrix to SERVICE-COMPONENT | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" | ||||||||||
| technical service categories | TBD | F | "BUSINESS-FOCUS-AREA (LINE OF SIGHT)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| enterprise | Defaults to Enterprise to allow Enterprise Reporting | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| enterprise components | Complex Matrix to SYSTEM-COMP0NENT where type is enterprise. | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| investment projects | Complex Matrix to INVESTMENT-PROJECT | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| organizations | Complex Matrix to ORGANIZATION | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| persons | Complex Matrix to PERSON_ | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| system inventories | Complex Matrix to SYSTEM-INVENTORY | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" | ||||||||||
| system inventory roles | BUSINESS-FOCUS/SYSTEM-INV-ROLE captures the role the system plays with in the business focus area. | TBD | F | "BUSINESS-FOCUS-AREA (PROTFOLIO)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| issue status | what is the status of this issue? | TBD | F | ISSUE | ||||||||||
| name | Name of the ISSUE | TBD | F | ISSUE |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child mbt categories | MBT-CATEGORY | TBD | F | "MBT-CATEGORY" | ||||||||||
| name | TBD | F | "MBT-CATEGORY" | |||||||||||
| parent mbt category | MBT-CATEGORY | TBD | F | "MBT-CATEGORY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | The name will be a concatonation of the type, level, and name. Example P1 Business Processes Supported - Low | TBD | F | "MBT-CRITERIA" | ||||||||||
| type | This is the type of TAA criteria. It will either be Process, Data, Application or Technology | TBD | T | P D A T | "MBT-CRITERIA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business focus area | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" | |||||||||||
| mbt criteria | MBT_CRITERIA | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" | ||||||||||
| mbt issues | List of MBT-ISSUE | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" | ||||||||||
| name | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" | |||||||||||
| rationale | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" | |||||||||||
| score | TBD | F | "MBT-CRITERIA/BUSINESS-FOCUS" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| mbt criteria | MBT_CRITERIA | TBD | F | "MBT-CRITERIA/SYSTEM" | ||||||||||
| mbt issues | List of MBT-ISSUE | TBD | F | "MBT-CRITERIA/SYSTEM" | ||||||||||
| name | TBD | F | "MBT-CRITERIA/SYSTEM" | |||||||||||
| rationale | TBD | F | "MBT-CRITERIA/SYSTEM" | |||||||||||
| score | TBD | F | "MBT-CRITERIA/SYSTEM" | |||||||||||
| system | TBD | F | "MBT-CRITERIA/SYSTEM" | |||||||||||
| system version | TBD | F | "MBT-CRITERIA/SYSTEM" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business drivers | TBD | F | "MBT-FINDING" | |||||||||||
| mbt categories | List of MBT-CATEGORY | TBD | F | "MBT-FINDING" | ||||||||||
| mbt recomendations | List Of MBT-RECOMENDATION | TBD | F | "MBT-FINDING" | ||||||||||
| name | TBD | F | "MBT-FINDING" | |||||||||||
| stakeholder categories | TBD | F | "MBT-FINDING" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child mbt recomendation categories | TBD | F | "MBT-RECOMENDATION-CATEGORY" | |||||||||||
| name | TBD | F | "MBT-RECOMENDATION-CATEGORY" | |||||||||||
| parent mbt recomendation category | TBD | F | "MBT-RECOMENDATION-CATEGORY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| best practice classification | Unknown | TBD | T | Department BP Bureau BP General BP NA Unknown | "MBT-RECOMMENDATION" | |||||||||
| business case | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| child recommendations | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| dependant recommendations | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| end outcomes | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| fy(04) o&m funding | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| intermediate outcomes | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| mbt recomendation category | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| mbt tactical areas | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| name | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| planning period | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| priority | Priority of recommendation. | Unknown | TBD | T | Tactical Strategic TBD NA Unknown | "MBT-RECOMMENDATION" | ||||||||
| protfolio manager prioritization | TBD | F | "MBT-RECOMMENDATION" | |||||||||||
| recomendation type | TBD | T | Strategic Tactical NA Unknown | "MBT-RECOMMENDATION" | ||||||||||
| tactical solution - cost estimate | BEA Team Recommended Tactical Solution Cost Estimate - (Man-Weeks) $$$ = 40-100 Man-weeks, $$ = 12-40 Man-weeks, $ = 2-12 Man-weeks | TBD | F | "MBT-RECOMMENDATION" | ||||||||||
| tactical solution - level of effort | BEA Team Recommended Tactical Solution Level of Effort - (Man-Weeks) | TBD | F | "MBT-RECOMMENDATION" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | TBD | F | "MBT-RECOMMENDATION/MBT-STATUS" | |||||||||||
| recommendation | TBD | F | "MBT-RECOMMENDATION/MBT-STATUS" | |||||||||||
| status begin date | TBD | F | "MBT-RECOMMENDATION/MBT-STATUS" | |||||||||||
| status comment | TBD | F | "MBT-RECOMMENDATION/MBT-STATUS" | |||||||||||
| status end date | TBD | F | "MBT-RECOMMENDATION/MBT-STATUS" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | TBD | F | "MBT-STATUS" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | TBD | F | "MBT-TACTICAL-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | Name of the RECOMENDATION-CATEGORY | TBD | F | "RECOMENDATION-CATEGORY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | TBD | F | "ROLLOUT-PHASE" | |||||||||||
| Name | TBD | F | "ROLLOUT-PHASE" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| name | TBD | F | "STAKEHOLDER-CATEGORY" | |||||||||||
| stakeholder type | Stakeholder Type List Per value of list selected will change the depiction of the symbo. | Person | TBD | T | Organization Person NA Unknown | "STAKEHOLDER-CATEGORY" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-FOCUS/SERVICE-COMP | Associative between these two objects | F | F | F | "architectural status" columndefinition "level business objectives" "level description" "level target" name "rollout phase" rowdefinition |
| SERVICE-COMP/FUNCTION-ACTIVITY | This associative entity SERVICE-COMP/FUNCTION-ACTIVITY will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | T | F | F | "analysis explanation" columndefinition description "geospatial analysis candidate" "geospatial modify candidate" "geospatial read candidate" Intersection? "modify explanation" name "read explanation" rowdefinition |
| SERVICE-COMPONENT | The final layer of the SRM is the Component level. These 168 Components represent the lower-level, logical building blocks of a business or application service component. REF:FEA_SRM_Release1.0] | T | F | F | "best practices" "brm tiers" "businesss focus areas" "child service components" comments "domain architecture principles" "enterprise investments" "fea code" name "parent service type" "service type" "system components" "technical service standards" "technology domain team" |
| SERVICE-DOMAIN | The Customer Services Domain defines the set of capabilities that are directly related to an internal or external customer, the business interaction with the customer, and the customer driven activities or functions. The taxonomy provides for a breakdown into Service Types and then into Service Components. [REF: FEA_SRM_Release1.0] | T | F | F | "best practices" comments "fea code" name "skills composition" |
| SERVICE-REFERENCE-MODEL | The Federal Enterprise Architecture Service Component Reference Model Version 1.0 is organized as a functional hierarchy, with Service Domains at the highest level followed by Service Types and Components. There are 7 Service Domains that provide a top-level categorization of the service capabilities and categories from a business perspective. These seven Service Domains are comprised of 29 Service Types that further categorize and define the capabilities of a Service Domain. The Service Types define the second level of detail that describes a business-oriented service. The next and final layer of the SRM is the Component level. Service | T | F | F | "child service domains" name |
| SERVICE-TYPE | These seven Service Domains are comprised of 29 Service Types that further categorize and define the capabilities of a Service Domain. | T | F | F | "best practices" comments "fea code" name "skills compositions" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | Architectural Status List | As Is | TBD | T | As Is To Be Both NA Unknown | "BUSINESS-FOCUS/SERVICE-COMP" | ||||||||
| columndefinition | SERVICE-COMPONENT | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" | ||||||||||
| level business objectives | 3 seperate properties for levels 1, 2, and 3. List Of Business Objective | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" | ||||||||||
| level description | 3 seperate properties for levels 1, 2, and 3. | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" | ||||||||||
| level target | 3 seperate properties for levels 1, 2, and 3. Target Implementation List | Unkonwn | TBD | T | Near Term Mid Term Long Term NA Unkonwn | "BUSINESS-FOCUS/SERVICE-COMP" | ||||||||
| name | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" | |||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" | |||||||||||
| rowdefinition | BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/SERVICE-COMP" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| analysis explanation | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| columndefinition | SERVICE-COMPONENT | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | ||||||||||
| description | The association from the SRM Service Component to the BRM work activity | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | ||||||||||
| geospatial analysis candidate | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| geospatial modify candidate | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| geospatial read candidate | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| Intersection? | The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | ||||||||||
| modify explanation | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| name | The name within the association of the SRM service component to the work activity of the BRM. | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | ||||||||||
| read explanation | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" | |||||||||||
| rowdefinition | FUNCTION-ACTIVITY | TBD | F | "SERVICE-COMP/FUNCTION-ACTIVITY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| best practices | The best practices identified as a part of the SRM | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| brm tiers | The association capability between the SRM and BRM | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| businesss focus areas | BUSINESSS-FOCUS-AREA Update via matrix or import. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| child service components | SERVICE-COMPONENT is child in. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| comments | Free text comment field describing the principle. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| domain architecture principles | The principles or rules that provide guidance for the respective SRM areas. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| enterprise investments | INVESTMENT-PROJECT | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| fea code | Code as specified in the FEA Reference Model for Service Reference Manual | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| name | The name of the principle. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| parent service type | Foreign key associating the various levels of the service reference model. | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| service type | The second tier of the SRM hierarchical model that classifies the service component tier | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| system components | The lowest tier of the SRM that articulates and describes the capability . | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| technical service standards | Foreign Key to TRM | TBD | F | "SERVICE-COMPONENT" | ||||||||||
| technology domain team | A domain team is responsible for developing architecture principles, with associated rationale and implication, identifying applicable standards and preferred products, and conducting other work assigned by the Architecture Team, for a given collection of related technologies. There is a domain team associated with each of the Technical Architecture Domains | TBD | F | "SERVICE-COMPONENT" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| best practices | The best practices associated to the top level of the SRM or the service domain | TBD | F | "SERVICE-DOMAIN" | ||||||||||
| comments | Free text field that further describes the service domain of the SRM | TBD | F | "SERVICE-DOMAIN" | ||||||||||
| fea code | Code as specified in the FEA Reference Model. | TBD | F | "SERVICE-DOMAIN" | ||||||||||
| name | The name of a classification within the SRM. | TBD | F | "SERVICE-DOMAIN" | ||||||||||
| skills composition | The identified skills associated with or required by the SRM | TBD | F | "SERVICE-DOMAIN" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child service domains | Foreign key associating the various levels of the service reference model. | TBD | F | "SERVICE-REFERENCE-MODEL" | ||||||||||
| name | The name of the SRM | TBD | F | "SERVICE-REFERENCE-MODEL" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| best practices | The best practices associated to the second tier of the SRM | TBD | F | "SERVICE-TYPE" | ||||||||||
| comments | Free text field used to describe the second tier of the SRM | TBD | F | "SERVICE-TYPE" | ||||||||||
| fea code | Code as specified in the FEA Reference Model. | TBD | F | "SERVICE-TYPE" | ||||||||||
| name | The name of the classification of the service type within the SRM | TBD | F | "SERVICE-TYPE" | ||||||||||
| skills compositions | The type of skills required to support or evolve the technologies | TBD | F | "SERVICE-TYPE" |
| Glossary Sub Domain |
|---|
| ABC |
| FEA BRM |
| Enterprise BRM |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| ABC-WORK-ACTIVITY | The Activity-Based Costing Item that describes an activity that can have work tied to it to measure effort against. Short name to describe the activity usually containing 3-10 words Needs to be renamed to ABC Work Activity per change by the DOI ABC Team. | T | F | F | "cost drivers" description "doi program area contact(s)" "doi program area contacts" "doi sub process code" "doi sub process name" "example notes" "full name" "function activities" inputs name organization outcomes output "program area" "system interfaces" "unit of measure" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cost drivers | The is a descriptive list of all the variables that can contribute to the total program cost for the activity | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| description | Long Description of: - What costs are associated with or covered by this activity - What set of actions make up this activity - Types of Groups that do this activity - Planning and other activities that are covered by this activity | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| doi program area contact(s) | List of PERSON_ updated for contacts from programs areas. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| doi program area contacts | Describes the nature of the role for an individual associated to the ABC program. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| doi sub process code | A unique code that identifies the DOI subprocess which is subordinate to the DOI Work Activity | management | F | management | "ABC-WORK-ACTIVITY" | |||||||||
| doi sub process name | Descriptive name for the supporting sub process | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| example notes | An area to capture notes about this ABC Work Activity or examples used to describe ABC Work Activity. Free text to explain the conditions and guidance around how to apply this definition of the work activity. | TBD | F | Alpha-numeric | "ABC-WORK-ACTIVITY" | |||||||||
| full name | The complete name of the ABC work activity. The name may have gotten truncated due to an 80 Character limitation | TBD | F | Alpha-numeric | "ABC-WORK-ACTIVITY" | |||||||||
| function activities | The level of the BRM (business reference model ) hierarchical model from FUNCTION-ACTIVITY | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| inputs | This is a list of the resources, policy , approvals, decisions etc that influence the work activity | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| name | Activity Based Costing Work Activity Name: The name of the Activity-Based Costing Item that describes an activity that can have work tied to it to measure effort against. Short name to describe the activity usually containing 3-10 words. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| organization | The DOI agencies that are associated with this goal and work activity. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| outcomes | The expected OUTCOME's of the effort described and codified . This is associated to the DOI work activity | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| output | Provides a list of systems from which the metric information will be collected. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| program area | TBD | F | "ABC-WORK-ACTIVITY" | |||||||||||
| system interfaces | Provides a list of systems from which the metric information will be collected. | TBD | F | "ABC-WORK-ACTIVITY" | ||||||||||
| unit of measure | One quantitative or qualitative way of measuring the success of this activity. Objective Free-Form statement - Quantitative or Qualitative Example: - Litigation matters concluded - Number of populations evaluated. Effectiveness will be based on the goals of the treatment. - Number of scientific assessments delivered | TBD | F | Alpha-numeric | "ABC-WORK-ACTIVITY" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| BUSINESS-AREA | An FEA BRM Business Area as defined by OMB. | T | F | F | "child lines of business" "fea code" name "parent business reference model" |
| BUSINESS-REFERENCE-MODEL | A way to relate a certain Line of Business to the other EA Domains The term Business Focus Area (BFA) was chosen as the BRM uses the term Line of Business slightly differently than the DOI does. BFA serves multiple purposes across domains Without this, a | T | F | F | "child business areas" |
| FUNCTION-ACTIVITY (SECURITY) | NIST attributes from the NIST 800-60 used in FIPS-199 Security Categorization based on Information types used by a system. NIST adopted the FEA BRM as the standard. NIST Information Types is equal to FEA BRM Sub-functions | T | F | F | "availability impact description" "availability impact recommended level" "availability impact special factors" "avaliability impact rationale" "confidentiality impact description" "confidentiality impact rationale" "confidentiality impact recommended level" "confidentiality impact special factors" "integrity impact description" "integrity impact rationale" "integrity impact recommended level" "integrity impact special factors" |
| LINE-OF-BUSINESS | An FEA BRM Line of business. The LINE-OF-BUSINESS inherits attributes from BRM-TIER. The complete As-Is DOI Business Architecture for the following business areas: Fire Management - DOI will extend the FEA BRM Line of Business to include Fire Management. Law Enforcement Indian Trust - DOI will extend the FEA BRM Line of Business to include Indian Trust (To Be Decided by Trust TEA team). Financial Management Recreation | T | F | F | "child sub functions" "fea code" "parent business area" |
| SUB-FUNCTION | An FEA BRM Business SubFunction. SUB-FUNCTION inherits attributes from BRM-TIER. | T | F | F | "fea code" "homeland security flag" "parent line of business" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child lines of business | The line of business that is a part of this business area | TBD | F | "BUSINESS-AREA" | ||||||||||
| fea code | The unique id is typically, a number, but is represented by a string. For FEA derived (BUSINESS-AREA, LINE-OF-BUSINESS, SUB FUNCTION), this is the FEA code, for additional levels this code is assigned by the DOI. The first digit represents the business area, the next 2 represent the line of business (in cross-agency form as well), and the final 3 digits represent the sub function (in cross-agency form as well) | TBD | F | "BUSINESS-AREA" | ||||||||||
| name | TBD | F | "BUSINESS-AREA" | |||||||||||
| parent business reference model | The highest level of the DOI functional decomposition within the BRM. | TBD | F | "BUSINESS-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child business areas | Foreign key used to associate the various levels of the BRM | TBD | F | "BUSINESS-REFERENCE-MODEL" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| availability impact description | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| availability impact recommended level | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "FUNCTION-ACTIVITY (SECURITY)" | ||||||||||
| availability impact special factors | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| avaliability impact rationale | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| confidentiality impact description | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| confidentiality impact rationale | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| confidentiality impact recommended level | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "FUNCTION-ACTIVITY (SECURITY)" | ||||||||||
| confidentiality impact special factors | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| integrity impact description | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| integrity impact rationale | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" | |||||||||||
| integrity impact recommended level | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "FUNCTION-ACTIVITY (SECURITY)" | ||||||||||
| integrity impact special factors | TBD | F | "FUNCTION-ACTIVITY (SECURITY)" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| child sub functions | The sub functions that belong to this line of business | TBD | F | "LINE-OF-BUSINESS" | ||||||||||
| fea code | The unique id is typically, a number, but is represented by a string. For FEA derived (BUSINESS-AREA, LINE-OF-BUSINESS, SUB FUNCTION), this is the FEA code, for additional levels this code is assigned by the DOI. The first digit represents the business area, the next 2 represent the line of business (in cross-agency form as well), and the final 3 digits represent the sub function (in cross-agency form as well) | TBD | F | "LINE-OF-BUSINESS" | ||||||||||
| parent business area | Primary name (parent) defining a DOI business area. | TBD | F | "LINE-OF-BUSINESS" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| fea code | The unique id is typically, a number, but is represented by a string. For FEA derived (BUSINESS-AREA, LINE-OF-BUSINESS, SUB FUNCTION), this is the FEA code, for additional levels this code is assigned by the DOI. The first digit represents the business area, the next 2 represent the line of business (in cross-agency form as well), and the final 3 digits represent the sub function (in cross-agency form as well) | TBD | F | "SUB-FUNCTION" | ||||||||||
| homeland security flag | Identifies the sub-function as being associated with homeland security. This is used specifically in the Exhibit 300 instruction noting that if an investment supports homeland security, indicate by corresponding number which homeland security mission area(s) this investment supports? 1. Intelligence and Warning; 2. Border and Transportation Security; 3. Defending Against Catastrophic Threats; 4. Protecting Critical Infrastructure and Key Assets; 5. Emergency Preparedness and Response; or 6. Other. | TBD | F | Yes No | "SUB-FUNCTION" | |||||||||
| parent line of business | The line of business that this FEA Sub function belongs to | TBD | F | "SUB-FUNCTION" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| Class | T | F | F | ||
| FUNCTION-ACTIVITY | BRM-TIER represents an entity in the FEA BRM. A BRM-TIER can be a Business area, Line of Businbess, or Business Sub Funciton or a further Agency specific decomposition. It is the super entity for BUSINESS-AREA, LINE-OF-BUSINESS, SUB-FUNCTION, LEVEL-2-SUB-FUNCTION, WORK-ACTIVITY, and PROCESS-STEP. The OMB has incorporated Mode of Delivery into the categorization of a Business Area. It is also considered to be its own entity at its level of Business Area with its own two lines of businesses. This later part is not modeled with the expectation that OMB will provide further guidance. | T | F | F | "abc work activities" "child function activities" "full name" "functin activity type" "leaf node flag" level "modes of delivery" name organizations "parent function activity" "secondary parent function activities" "service components" "sub function flag" "sub systems" |
| ICOM-ARROW | None | T | F | F | "business drivers" "data entities" delete name |
| PROCESS-STEP | A subtype of BRM-TIER. A PROCESS-STEP performs a WORK-ACTIVITY. PROCESS-STEP inherits attributes from BRM-TIER. | T | F | F |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| abc work activities | The ABC work activities comprise the foundation for the functional definition of the BRM | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| child function activities | Child function activities are those functions that are subordinate to the parent function activities and describe lower level functional activities | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| full name | TBD | F | "FUNCTION-ACTIVITY" | |||||||||||
| functin activity type | Function Activity Type List Depending on the value selection will update the depiction of the symbol on the diagram. | Unknown | TBD | T | Sub Function Function Process Activity Task NA Unknown | "FUNCTION-ACTIVITY" | ||||||||
| leaf node flag | TBD | F | "FUNCTION-ACTIVITY" | |||||||||||
| level | 1 through 10 list Subfunction 3, Function 4, Process 5, Activity 6, Task 7-10 | TBD | T | 1 2 3 4 5 6 7 8 9 10 | "FUNCTION-ACTIVITY" | |||||||||
| modes of delivery | FUNCTION-ACTIVITY Where mode of delivery flag = true. Should only be filled out if it is a Service to Citizen. This is a matrix property and should only be filled out on import or through matrix. | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| name | Activity Based Costing Work Activity Name: The name of the Activity-Based Costing Item that describes an activity that can have work tied to it to measure effort against. Short name to describe the activity usually containing 3-10 words. | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| organizations | Foreign key supporting relationship of the BRM to the org. | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| parent function activity | The highest level of the DOI functional decomposition within the BRM. | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| secondary parent function activities | if alternate parents exist. | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| service components | The service components are those generic capabilities that are used to support the implementation of the business function | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| sub function flag | Differentiator attribute that distinguishes FEA from DOI introduced functions | TBD | F | "FUNCTION-ACTIVITY" | ||||||||||
| sub systems | Defines the association to the IT sub systems that support the business function. | TBD | F | "FUNCTION-ACTIVITY" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business drivers | list of BUSINESS-DRIVER definitions should only be updated for Controls or Mechanisms. | TBD | F | "ICOM-ARROW" | ||||||||||
| data entities | List of ENTITY | TBD | F | "ICOM-ARROW" | ||||||||||
| delete | TBD | F | "ICOM-ARROW" | |||||||||||
| name | TBD | F | "ICOM-ARROW" |
| Glossary Sub Domain |
|---|
| DRM |
| Enterprise DRM |
| Enterprise DRM Relationships |
| Deletion Candidate |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| AD-HOC-ASSOCIATION | An association line able to be drawn between various elements. | T | F | F | |
| BUSINESS-FOCUS/DATA-SUB-AREA | Associative between these two objects | F | F | F | "architectural status" "data subject area" name |
| BUSINESS-FOCUS/INFO-CLASS | Associative between these two objects | F | F | F | "architectural status" columndefinition columndefinitionkey1 name "rollout phase" rowdefinition |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | The state of the relationship in the architecture. | As Is | TBD | T | As Is To Be NA Unknown | "BUSINESS-FOCUS/DATA-SUB-AREA" | ||||||||
| data subject area | The data subject area related to this Business Focus Area | TBD | F | "BUSINESS-FOCUS/DATA-SUB-AREA" | ||||||||||
| name | Name of the BUSINESS-FOCUS/DATA-SUB-AREA Relationship - typically not unique or specific since the relationship is what defines this definition | TBD | F | "BUSINESS-FOCUS/DATA-SUB-AREA" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| architectural status | Architectural Status List | As Is | TBD | T | As Is To Be Both NA Unknown | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||
| columndefinition | INFORMATION-CLASS | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||||
| columndefinitionkey1 | INFORMATION-CLASS Data Subject Area | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | ||||||||||
| name | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | |||||||||||
| rollout phase | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" | |||||||||||
| rowdefinition | BUSINESS-FOCUS-AREA | TBD | F | "BUSINESS-FOCUS/INFO-CLASS" |
| Glossary Entity | Description | IsCoreData | IsSecurityData | IsSensitive | Glossary Model Object Properties |
|---|---|---|---|---|---|
| AGREEMENT | AN ARRANGEMENT BETWEEN PARTIES. | T | F | F | "AGREEMENT ABBREVIATED NAME" "AGREEMENT CATEGORY CODE" "AGREEMENT DESCRIPTION TEXT" "AGREEMENT DURATION TYPE CODE" "AGREEMENT EFFECTIVE CALENDAR DATE" "AGREEMENT EXPIRATION CALENDAR DATE" "AGREEMENT IDENTIFIER" "AGREEMENT NAME" "AGREEMENT TEXT" "AGREEMENT TYPE CODE" "AGREEMENT USE CATEGORY CODE" "AGREEMENT VERSION IDENTIFIER" |
| AGREEMENT-ASSOCIATION | AN ASSOCIATION BETWEEN AN AGREEMENT AND ANOTHER AGREEMENT. | T | F | F | "AGREEMENT-ASSOCIATION IDENTIFIER" "AGREEMENT-ASSOCIATION REASON CODE" |
| ALTERNATE-KEY-GROUP-MEMBER | To be defined by ITA Team | T | F | F | |
| ARCHITECTURE-PROJECT-ANALYSIS-RESULT | THE ASSOCIATION BETWEEN A SPECIFIC ARCHITECTURE-PROJECT AND A SPECIFIC ARCHITECTURE-ANALYSIS-PROCESS-RESULT. | T | F | F | "ACTION-DOCUMENT IDENTIFIER" "Analysis Process ACTION IDENTIFIER" "ARCHITECTURE IDENTIFIER" "ARCHITECTURE-ANALYSIS-PROCESS-RESULT IDENTIFIER" "ARCHITECTURE-PROJECT IDENTIFIER" "Project ACTION IDENTIFIER" "Project DOCUMENT IDENTIFIER" |
| CATEGORY-RELATIONSHIP | A SPECIFIC TYPE OF DATA MODEL RELATIONSHIP USED TO SPECIFY A CATEGORY TYPE ARRANGEMENT BETWEEN PARENT AND CHILD ENTITIES. | T | F | F | "CATEGORY-RELATIONSHIP COMPLETENESS CODE" |
| CONCEPTUAL-DATA-MODEL | A STRUCTURED GRAPHICAL AND TEXTUAL REPRESENTATION OF CONCEPTS AND KNOWLEDGE WITHIN AN ACTIVITY. | T | F | F | "CONCEPTUAL-DATA-MODEL CREATOR IDENTIFIER" "CONCEPTUAL-DATA-MODEL DEVELOPMENT METHODOLOGY NAME" "CONCEPTUAL-DATA-MODEL DEVELOPMENT STATUS IDENTIFIER" "CONCEPTUAL-DATA-MODEL DEVELOPMENT TOOL NAME" "CONCEPTUAL-DATA-MODEL NOTATION STYLE NAME" "CONCEPTUAL-DATA-MODEL PURPOSE TEXT" "CONCEPTUAL-DATA-MODEL REFINEMENT LEVEL CODE" "CONCEPTUAL-DATA-MODEL REVISION EFFECTIVE CALENDAR DATE" "CONCEPTUAL-DATA-MODEL SCOPE TEXT" "CONCEPTUAL-DATA-MODEL STATUS EFFECTIVE CALENDAR DATE" "CONCEPTUAL-DATA-MODEL TENSE CODE" "CONCEPTUAL-DATA-MODEL TENSE EFFECTIVE CALENDAR DATE" |
| CONCEPTUAL-DATA-MODEL-VIEW | A COLLECTION OF ENTITIES, ATTRIBUTES, AND RELATIONSHIPS THAT REPRESENT A SPECIFIC PART OF A DATA MODEL. | T | F | F | "CONCEPTUAL-DATA-MODEL-VIEW CREATOR IDENTIFIER" "CONCEPTUAL-DATA-MODEL-VIEW DATA STANDARDIZATION IDENTIFIER" "CONCEPTUAL-DATA-MODEL-VIEW SCOPE TEXT" |
| CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION | THE ASSOCIATION BETWEEN ONE CONCEPTUAL-DATA-MODEL-VIEW AND ANOTHER. | T | F | F | "CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION CREATION CALENDAR DATE" "CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION DEPENDENCY DESCRIPTION TEXT" |
| CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY | To be defined by IDA Team | T | F | F | |
| CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP | AN ASSOCIATIVE ENTITY THAT IDENTIFIES A DATA-ENTITY-RELATIONSHIP WITH A CON CEPTUAL-DATA-MODEL-VIEW. | T | F | F | "CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP COMMENT TEXT" |
| DATA-ATTRIBUTE | A PROPERTY OR CHARACTERISTIC OF A DATA-ENTITY THAT IS COMMON TO INSTANCES OF AN ENTITY AND REPRESENTS THE ASSOCIATION OF A DATA-DOMAIN WITH A DATA-ENTITY. | T | F | F | "attribute composition type name" "authoritative source" "derivation procedure" derived "domain description" "domain values" "entity name" "full name" "indian trus data" model name notes precision "reference source" "security classification code" "units of measure" "xml tag name" |
| DATA-ATTRIBUTE-ALIAS | AN ASSOCIATIVE ENTITY THAT IDENTIFIES AN ALTERNATE LABEL USED TO REFER TO A DATA-ATTRIBUTE. | T | F | F | "ALIAS IDENTIFIER" "DATA-ATTRIBUTE-ALIAS CREATION CALENDAR DATE" |
| DATA-ATTRIBUTE-ASSOCIATION | THE ASSOCIATION AMONG DATA ATTRIBUTES WHICH INDICATES HOW A NON-ATOMIC DATA ATTRIBUTE IS CONSTRUCTED. | T | F | F | "DATA-ATTRIBUTE-ASSOCIATION TYPE CODE" |
| DATA-ATTRIBUTE-CHAIN | (4227/1) (A) A SUBTYPE OF DATA ATTRIBUTE ASSOCIATION WHICH INDICATES A DATA ATTRIBUTE DE RIVED THROUGH PARTICIPATION IN A CHAIN. | T | F | F | "DATA-ATTRIBUTE-CHAIN PARTICIPANT TYPE CODE" |
| DATA-ATTRIBUTE-CHAIN-BASE-ATTRIBUTE | To be defined by IDA Team | T | F | F | |
| DATA-ATTRIBUTE-CHAIN-MEMBER-ATTRIBUTE | To be defined by IDA Team | T | F | F | "DATA-ATTRIBUTE-CHAIN DATA ATTRIBUTE POSITION IDENTIFIER" |
| DATA-ATTRIBUTE-DATA-TYPE | THE SPECIFICATION OF A DATA CLASS OF A DATABASE QUERY LANGUAGE FOR A SPECIFIC DATA-ATTRIBUTE. | T | F | F | "DATA-ATTRIBUTE-DATA-TYPE NAME" "DATA-ATTRIBUTE-DATA-TYPE TARGET ENVIRONMENT NAME" |
| DATA-ATTRIBUTE-DERIVED | A SUBTYPE OF A DATA ATTRIBUTE ASSOCIATION WHICH INDICATES A DERIVED DATA AT TRIBUTE. | T | F | F | "DATA-ATTRIBUTE-DERIVED ALGORITHM TEXT" |
| DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD | AN ASSOCIATIVE ENTITY THAT IDENTIFIES A DATA-ATTRIBUTE WITH A USER-PRESENTATION-VIEW-FIELD. | T | F | F | "User Presentation View INFORMATION-ASSET IDENTIFIER" "USER-PRESENTATION-VIEW-FIELD IDENTIFIER" |
| DATA-CLASS | THE CLASSIFICATION OF DATA TO WHICH A DATA ATTRIBUTE BELONGS. | T | F | F | "Data Class INFORMATION-ASSET IDENTIFIER" "DATA-CLASS CATEGORY NAME" "DATA-CLASS TYPE CODE" |
| DATA-DICTIONARY | A LISTING OF DATA-ELEMENTS AND THEIR CHARACTERISTICS. | T | F | F | "DATA-DICTIONARY TYPE CODE" |
| DATA-DICTIONARY-ELEMENT | AN INFORMATION CONCEPT DEFINED IN A SPECIFIC DATA-DICTIONARY. | T | F | F | "DATA-DICTIONARY-ELEMENT APPROVAL STATUS CALENDAR DATE" "DATA-DICTIONARY-ELEMENT APPROVAL STATUS CODE" "DATA-DICTIONARY-ELEMENT DEFINITION TEXT" "DATA-DICTIONARY-ELEMENT FORMAT DESCRIPTION TEXT" "DATA-DICTIONARY-ELEMENT IDENTIFIER" "DATA-DICTIONARY-ELEMENT NAME" "DATA-DICTIONARY-ELEMENT SOURCE NAME" "DATA-DICTIONARY-ELEMENT USAGE DESCRIPTION TEXT" "INFORMATION-ELEMENT IDENTIFIER" |
| DATA-DICTIONARY-ELEMENT-ASSOCIATION | THE RELATIONSHIP OF ONE DATA-DICTIONARY-ELEMENT TO ANOTHER DATA-DICTIONARY-ELEMENT. | T | F | F | "DATA-DICTIONARY-ELEMENT-ASSOCIATION IDENTIFIER" "DATA-DICTIONARY-ELEMENT-ASSOCIATION TYPE CODE" |
| DATA-DICTIONARY-SPECIFICATION | A DOCUMENT THAT CONTAINS METADATA FOR INFORMATION CONCEPTS. | T | F | F | "DOCUMENT IDENTIFIER" |
| DATA-DOMAIN | A SET OF PERMISSIBLE DATA VALUES FROM WHICH ACTUAL VALUES ARE TAKEN. | T | F | F | "DATA-DOMAIN CONSTRUCTION TYPE CODE" "DATA-DOMAIN FORMAT CODE" "DATA-DOMAIN MAXIMUM CHARACTER QUANTITY" "DATA-DOMAIN TYPE CODE" "DATA-DOMAIN VALUE TYPE CODE" |
| DATA-DOMAIN-BASE | A DATA DOMAIN, ASSIGNED A CERTAIN DATA TYPE, UPON WHICH OTHER DOMAINS MAY BE BASED. | T | F | F | "DATA-DOMAIN-BASE DATA TYPE NAME" |
| DATA-DOMAIN-LIST | AN ENUMERATED SET OF VALUES ALLOWED IN DATA REPRESENTATION OF A DATA-ATTRIBUTE. | T | F | F | "DATA-DOMAIN-LIST SOURCE LIST TEXT" |
| DATA-DOMAIN-LIST-VALUE | A SPECIFIC ACCEPTABLE INSTANCE VALUE THAT IS PART OF A DATA-DOMAIN-LIST. | T | F | F | "DATA-DOMAIN-LIST-VALUE DEFINITION TEXT" "DATA-DOMAIN-LIST-VALUE IDENTIFIER" "DATA-DOMAIN-LIST-VALUE SOURCE NAME" |
| DATA-DOMAIN-LIST-VALUE-ASSOCIATION | THE RELATIONSHIP OF ONE SPECIFIC DATA-DOMAIN-LIST-VALUE WITH ANOTHER DATA-DOMAIN-LIST-VALUE. | T | F | F | "DATA-DOMAIN-LIST-VALUE-ASSOCIATION ALGORITHM TEXT" |
| DATA-DOMAIN-RANGE | THE SET OF ALL ACCEPTABLE INSTANCE VALUES OF A DATA DOMAIN WHERE THE INSTANCE VALUES ARE CONSTRAINED BY LOWER AND/OR UPPER BOUNDARIES. | T | F | F | "DATA-DOMAIN-RANGE HIGH VALUE TEXT" "DATA-DOMAIN-RANGE INCREMENT MEASUREMENT QUANTITY" "DATA-DOMAIN-RANGE LOW VALUE TEXT" |
| DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION | THE COMBINATION OF RULES BY WHICH A DATA DOMAIN IS CONSTRUCTED. | T | F | F | "DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION ALGORITHM TEXT" "DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION NAME" |
| DATA-DOMAIN-TYPED | A DATA DOMAIN WHOSE ALLOWABLE VALUES ARE CONSTRAINED BY A DATA DOMAIN STRUC TURE RULE. | T | F | F | "DATA-DOMAIN-TYPED NAME" |
| DATA-ENTITY | THE REPRESENTATION OF A SET OF PEOPLE, OBJECTS, PLACES, EVENTS OR IDEAS, THAT SHARE THE SAME CHARACTERISTICS. | T | F | F | "entity mappable indicator" "full name" "function activities" "information classes" name "sub systems" version "xml tag name" |
| DATA-ENTITY-ALTERNATE-KEY-GROUP | To be defined by IDA Team | T | F | F | "DATA-ENTITY-ALTERNATE-KEY-GROUP IDENTIFIER" "DATA-ENTITY-DATA-ATTRIBUTE ALTERNATE KEY IDENTIFIER" |
| DATA-ENTITY-DATA-ATTRIBUTE | To be defined by IDA Team | T | F | F | |
| DATA-ENTITY-FOREIGN-KEY-GROUP | To be defined by IDA Team | T | F | F | |
| DATA-ENTITY-KEY-GROUP | To be defined by IDA Team | T | F | F | "DATA-ENTITY-KEY-GROUP Identifier" |
| DATA-ENTITY-OPTIONAL-ATTRIBUTE | To be defined by IDA Team | T | F | F | |
| DATA-ENTITY-PRIMARY-KEY-GROUP | To be defined by IDA Team | T | F | F | |
| DATA-ENTITY-RELATIONSHIP | THE ASSOCIATION OF ONE SPECIFIC DATA-ENTITY WITH ANOTHER DATA-ENTITY. | T | F | F | "DATA-ENTITY-RELATIONSHIP CARDINALITY TYPE CODE" "DATA-ENTITY-RELATIONSHIP CATEGORY CODE" "DATA-ENTITY-RELATIONSHIP CHILD DELETE RULE TEXT" "DATA-ENTITY-RELATIONSHIP CHILD INSERT RULE TEXT" "DATA-ENTITY-RELATIONSHIP CHILD UPDATE RULE TEXT" "DATA-ENTITY-RELATIONSHIP DEPENDENCY CODE" "DATA-ENTITY-RELATIONSHIP DESCRIPTION TEXT" "DATA-ENTITY-RELATIONSHIP GLOBALLY-UNIQUE PHYSICAL NAME" "DATA-ENTITY-RELATIONSHIP IDENTIFIER" "DATA-ENTITY-RELATIONSHIP NAME" "DATA-ENTITY-RELATIONSHIP NULL RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT DELETE RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT INSERT RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT UPDATE RULE TEXT" "DATA-ENTITY-RELATIONSHIP TYPE CODE" "DATA-ENTITY-RELATIONSHIP VERSION IDENTIFIER" |
| DATA-ENTITY-RELATIONSHIP-ROLE-NAME | To be defined by IDA Team | T | F | F | "DATA-ENTITY-RELATIONSHIP ROLE NAME IDENTIFIER" |
| DATA-ENTITY-REQUIRED-ATTRIBUTE | To be defined by IDA Team | T | F | F | |
| DATA-FLOW | To be defined by IDA Team | T | F | F | Delete "information classes" name |
| DATA-FORMAT | Look up table for system interface capability data formats. | T | F | F | Name |
| DATA-SET | In an EA sense, a geospatial data set can be viewed in a similarfashion as a system and may be viewed as a type of simplified system in the EA:they have a defined structure, a set of data elements, a theme or subject area,and are created and maintained by owners. They also have a set of standardized ?system?metadata, such as creator, creation date, description, status, currentness , purpose etc. The FGDC metadata standard for spatialdata sets is a good way to consistently describe them across the department. In fact, if a data set is fully described using this metadata, they should already contain much of the information to populate DEAR | T | F | F | "creation date" creator currentness Entities name "owning organization" purpose status "subject area diagram" |
| DATA-STORE | A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. | T | F | F | "information classes" name "processing nodes" "system component instances" "technical service specifications" |
| DATA-SUBJECT-AREA | A BROAD CLASSIFICATION OF INFORMATION or a grouping of related entities (those in which data are closely related and describe a general business idea or object) are called Data Subject Areas (DSA). A DSA is a grouping of entities based on a commonality of the data, and NOT how it is used by any given business process or application. This will be a definition object as well as a diagram object. The DATA-SUBJECT-AREA entity should be able to support both the DOI data management program and BEA. Source:IT Pioneers, Jim Cox, & BLM EA Team of Bob Perkins & Barb Kett | T | F | F | "information classes" name status |
| DATA-SUBJECT-AREA-ENTITY | To be defined by IDA Team | T | F | F | |
| DOCUMENT | RECORDED INFORMATION REGARDLESS OF PHYSICAL FORM. | T | F | F | "CAVEATED-SECURITY-CLASSIFICATION IDENTIFIER" "DOCUMENT ABBREVIATED NAME" "DOCUMENT APPROVAL CALENDAR DATE" "DOCUMENT ARCHITECTURE PRODUCT TYPE CODE" "DOCUMENT CATEGORY CODE" "DOCUMENT CREATION CALENDAR DATE" "DOCUMENT DESCRIPTION TEXT" "DOCUMENT IDENTIFIER" "DOCUMENT NAME" "DOCUMENT NOTATION TEXT" "DOCUMENT ORIGINATOR NAME" "DOCUMENT PUBLICATION CALENDAR DATE" "DOCUMENT REMARK TEXT" "DOCUMENT ROUTING CODE" "DOCUMENT TEMPORAL SCOPE CODE" "DOCUMENT TYPE CODE" "DOCUMENT UNIVERSAL RESOURCE LOCATOR TEXT" "DOCUMENT VERSION IDENTIFIER" "SECURITY-CLASSIFICATION CODE" "Time Frame PERIOD IDENTIFIER" |
| DOCUMENT-ASSOCIATION | AN ASSOCIATION BETWEEN A DOCUMENT AND ANOTHER DOCUMENT. | T | F | F | "DOCUMENT-ASSOCIATION BEGIN CALENDAR DATE-TIME" "DOCUMENT-ASSOCIATION END CALENDAR DATE-TIME" "DOCUMENT-ASSOCIATION IDENTIFIER" "DOCUMENT-ASSOCIATION REASON CODE" |
| DOMAIN-VALUE | Meant to represent the list of valid values for a given attribute. | T | F | F | name |
| ENTITY/ORGANIZATION-ROLE | Associative between these two objects | T | F | F | description entity model name organizations |
| GUIDANCE | (336/3) (A) A STATEMENT OF DIRECTION RECEIVED FROM A HIGHER ECHELON. | T | F | F | "GUIDANCE AUTHORITY TEXT" "GUIDANCE BEGIN CALENDAR DATE-TIME" "GUIDANCE CATEGORY CODE" "GUIDANCE END CALENDAR DATE-TIME" "GUIDANCE FUNCTIONAL TYPE CODE" "GUIDANCE IDENTIFIER" "GUIDANCE NAME" "GUIDANCE SUBJECT TEXT" "GUIDANCE SYNOPSIS TEXT" "GUIDANCE TEXT" "POINT-OF-CONTACT IDENTIFIER" |
| GUIDANCE-ASSOCIATION | AN ASSOCIATION OF A SPECIFIC GUIDANCE WITH ANOTHER SPECIFIC GUIDANCE. | T | F | F | "GUIDANCE-ASSOCIATION BEGIN CALENDAR DATE-TIME" "GUIDANCE-ASSOCIATION END CALENDAR DATE-TIME" "GUIDANCE-ASSOCIATION IDENTIFIER" "GUIDANCE-ASSOCIATION ROLE CODE" |
| INFORMATION-ASSET | AN INFORMATION RESOURCE. | T | F | F | "INFORMATION-ASSET ACRONYM TEXT" "INFORMATION-ASSET COMMENT TEXT" "INFORMATION-ASSET DEFINITION TEXT" "INFORMATION-ASSET IDENTIFIER" "INFORMATION-ASSET NAME" "INFORMATION-ASSET REUSABLE CODE" "INFORMATION-ASSET SHORT NAME" "INFORMATION-ASSET STANDARDIZATION AUTHORITY CODE" "INFORMATION-ASSET STANDARDIZATION STATUS CALENDAR DATE" "INFORMATION-ASSET STANDARDIZATION STATUS CODE" "INFORMATION-ASSET TYPE CODE" "INFORMATION-ASSET VERSION IDENTIFIER" |
| INFORMATION-ASSET-AGREEMENT | THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET TO A SPECIFIC AGREEMENT. | T | F | F | "INFORMATION-ASSET-AGREEMENT IDENTIFIER" "INFORMATION-ASSET-AGREEMENT ROLE CODE" |
| INFORMATION-ASSET-DOCUMENT | THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET TO A SPECIFIC DOCUMENT. | T | F | F | "INFORMATION-ASSET-DOCUMENT IDENTIFIER" "INFORMATION-ASSET-DOCUMENT ROLE CODE" |
| INFORMATION-ASSET-GUIDANCE | THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET WITH A SPECIFIC INSTANCE OF GUIDANCE. | T | F | F | "INFORMATION-ASSET-GUIDANCE DESCRIPTION TEXT" |
| INFORMATION-ASSET-RELATION | THE ASSOCIATION BETWEEN INFORMATION-ASSETS. | T | F | F | "INFORMATION-ASSET-RELATION REASON TEXT" "INFORMATION-ASSET-RELATION ROLE CODE" "INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE" "INFORMATION-ASSET-RELATION TYPE CODE" |
| INFORMATION-ASSET-SECONDARY-STEWARD | None | T | F | F | |
| INFORMATION-CLASS | To be defined by IDA Team Was named super type. | T | F | F | "business focus areas" "data entities" "data subject area" name status "sub systems" |
| INFORMATION-CLASS/SUB-SYSTEM | This associative entity SUPER-TYPE/SUB-SYSTEM will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. | F | F | F | columndefinition columndefinitionkey1 columndefinitionkey2 columndefinitionkey3 "curd info" "data store form of sharing" "data subject area" name rowdefinition rowdefinitionkey1 |
| INFORMATION-SYSTEM | A COLLECTION OF INFORMATION-ASSETS COMBINED TO ACHIEVE A DIRECTED PURPOSE. | T | F | F | "FUNCTIONAL-AREA IDENTIFIER" "INFORMATION-SYSTEM ENVIRONMENT TEXT" "INFORMATION-SYSTEM INTERFACE TRANSACTION PREDOMINANT METHOD CODE" "INFORMATION-SYSTEM SITE QUANTITY" "INFORMATION-SYSTEM TYPE CODE" "INFORMATION-SYSTEM USER QUANTITY" |
| INFORMATION-TECHNOLOGY-REQUIREMENT | GUIDANCE THAT SPECIFIES A NEED OR DEMAND FOR THE ACQUISITION, STORAGE, MANIPULATION, MANAGEMENT, MOVEMENT, CONTROL, SWITCHING, INTERCHANGE, TRANSMISSION, OR RECEPTION OF DATA. | T | F | F | "FUNCTIONAL-AREA IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT ALTERNATE IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT ALTERNATE IDENTIFIER SOURCE NAME" "INFORMATION-TECHNOLOGY-REQUIREMENT CATEGORY CODE" "INFORMATION-TECHNOLOGY-REQUIREMENT DESCRIPTION TEXT" "INFORMATION-TECHNOLOGY-REQUIREMENT USE CLASS CODE" |
| INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET | THE ASSOCIATION OF A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT WITH A SPECIFIC INFORMATION-ASSET. | T | F | F | "INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET ROLE CODE" |
| LOGICAL-DATA-MODEL | A FORMAL SPECIFICATION OF THE STRUCTURE AND MEANING OF A SET OF INFORMATION BY USE OF GRAPHICS FOR ENTITIES, ATTRIBUTES, AND RELATIONSHIPS. | T | F | F | |
| MIGRATED-DATA-ATTRIBUTE | None | T | F | F | |
| OWNED-DATA-ATTRIBUTE | None | T | F | F | |
| PRIMARY-KEY-DATA-ATTRIBUTE | None | T | F | F | |
| PROJECT | None | T | F | F | INFORMATION-PROJECT-NAME |
| QUALITATIVE-DATA-DOMAIN | A SET OF PERMISSIBLE DATA TO WHICH MATHEMATICAL OPERATIONS DO NOT APPLY. | T | F | F | "QUALITATIVE-DATA-DOMAIN ACCURACY-PERCENT QUANTITY" "QUALITATIVE-DATA-DOMAIN CHARACTER SET NAME" "QUALITATIVE-DATA-DOMAIN DATA TYPE CODE" |
| QUANTITATIVE-DATA-DOMAIN | A SET OF DATA FROM UPON WHICH MATHEMATICAL OPERATIONS CAN BE PERFORMED. | T | F | F | "QUANTITATIVE-DATA-DOMAIN ACCURACY CODE" "QUANTITATIVE-DATA-DOMAIN BASE QUANTITY" "QUANTITATIVE-DATA-DOMAIN DATA TYPE CODE" "QUANTITATIVE-DATA-DOMAIN SCALE QUANTITY" |
| QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT | THE DESIGNATION WHICH INDICATES THE DIMENSION, QUANTITY OR CAPACITY OF AN OBJECT. | T | F | F | "Data Class INFORMATION-ASSET IDENTIFIER" "QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT IDENTIFIER" "QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT NAME" |
| QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT-CONVERSION-ASSOCIATION | THE MATHEMATICAL RELATION BETWEEN ONE QUANTITATIVE-DATA-DOMAIN-MEASUREMENT- UNIT WITH ANOTHER. | T | F | F | "QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT-CONVERSION-ASSOCIATION ALGORITHM TEXT" |
| RELATION-TYPE | AN ASSOCIATION BETWEEN OBJECTS THAT DEFINES AN INFORMATION ASSET. | T | F | F | "RELATION-TYPE GENERATE TRACE ADDITION INDICATOR CODE" "RELATION-TYPE IDENTIFIER" "RELATION-TYPE INVERSE RELATION NAME" "RELATION-TYPE NAME" |
| SECURITY-CLASSIFICATION | THE LEVEL ASSIGNED TO NATIONAL SECURITY INFORMATION AND MATERIAL THAT DENOTES THE DEGREE OF DAMAGE THAT ITS UNAUTHORIZED DISCLOSURE WOULD CAUSE TO NATIONAL DEFENSE OR FOREIGN RELATIONS OF THE UNITED STATES AND THE DEGREE OF PROTECTION REQUIRED. | T | F | F | "SECURITY-CLASSIFICATION CODE" "SECURITY-CLASSIFICATION DESCRIPTION TEXT" "SECURITY-CLASSIFICATION DOWNGRADE INSTRUCTION TEXT" "SECURITY-CLASSIFICATION STATUS CODE" |
| SOFTWARE-APPLICATION | A COLLECTION OF AUTOMATED PROGRAMS THAT PROVIDES A SPECIFIC SET OF INFORMATION ON PROCESSING SERVICES. | T | F | F | "SOFTWARE-APPLICATION CREATOR IDENTIFIER" "SOFTWARE-APPLICATION FUNCTIONAL DESCRIPTION TEXT" "SOFTWARE-APPLICATION PRODUCTION STATUS CODE" "SOFTWARE-APPLICATION VERSION RELEASE CALENDAR DATE" |
| SYSTEM-PLATFORM | THE COLLECTION OF HARDWARE AND SOFTWARE USED BY A SYSTEM. | F | F | F | "SYSTEM-PLATFORM DESCRIPTION TEXT" |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AGREEMENT ABBREVIATED NAME | THE SHORTENED FORM OF THE NAME FOR A SPECIFIC AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT CATEGORY CODE | THE CODE THAT REPRESENTS A CLASSIFICATION OF AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT DESCRIPTION TEXT | THE TEXT OF THE CHARACTERISTICS OF AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT DURATION TYPE CODE | THE CODE THAT REPRESENTS A SPECIFIC KIND OF TIME FRAME ASSOCIATED WITH AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT EFFECTIVE CALENDAR DATE | THE CALENDAR DATE WHEN AN AGREEMENT BECOMES EFFECTIVE. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT EXPIRATION CALENDAR DATE | THE CALENDAR DATE ON WHICH AN AGREEMENT IS NO LONGER IN FORCE. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT IDENTIFIER | THE IDENTIFIER THAT REPRESENTS AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT NAME | HE NAME OF AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT TEXT | THE TEXT OF AN AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT TYPE CODE | THE CODE THAT REPRESENTS A SPECIFIC KIND OF AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT USE CATEGORY CODE | THE CODE THAT REPRESENTS A CLASS OF EMPLOYMENT OF A SPECIFIC AGREEMENT. | TBD | F | AGREEMENT | ||||||||||
| AGREEMENT VERSION IDENTIFIER | THE IDENTIFIER OF A SPECIFIC RENDITION OF A SPECIFIC AGREEMENT. | TBD | F | AGREEMENT |
| Glossary Entity | Description | Data Collection Comment | Data Collection Reason | DEAR Data Requirement | DEAR Default Value | DEAR Team Assignment | DOI Data Owner | Domain if Not Same as Entity | Check if this is a Controlled List | 'List Of' Values | Read-Only? | Type of Change | UsrProp Name | Model Object |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AGREEMENT-ASSOCIATION IDENTIFIER | THE IDENTIFIER OF AN AGREEMENT-ASSOCIATION FOR A SPECIFIC ORDINATE AGREEMENT AND A SPECIFIC SUBORDINATE AGREEMENT. | TBD | F | "AGREEMENT-ASSOCIATION" | ||||||||||
| AGREEMENT-ASSOCIATION REASON CODE | HE CODE THAT REPRESENTS THE UNDERLYING BASIS OF AN AGREEMENT-ASSOCIATION. | TBD |