| Go Back | Show | Hide | Reset | Information is for official use only - Last update | |||||||||||
|
|
|||||||||||
| DOI Glossary - Objects/Attributes - Linked |
|
| 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" |
| 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" |
| ARCHITECTURAL-PATTERN | Symbol used on the System Interface decomposition to represent a pattern overlay for networks. | T | F | F | "anti pattern" "child patterns" name |
| 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" |
| BEST-PRACTICE | To be defined by ITA Team | T | F | F | description name |
| BFA-INTEGRATION | T | F | F | name "touch point" | |
| 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-DRIVER | To be defined by ITA Team | F | F | F | "business driver type" "business focus areas" citation "citation initial date" "citation last changed" "end outcomes" "in effect" "intermediate outcomes" level "mandate final date" name organizations persons |
| BUSINESS-DRIVER/ORGANIZATION | Updated by complex Matrix Business Driver to Organization. | T | F | F | "architectural status" columndefinition comment "comment date" name rowdefinition |
| BUSINESS-DRIVER/PERSON | Updated by complex Matrix Business Driver to Person. | F | F | F | columndefinition comment "comment date" name rowdefinition |
| 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" |
| 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" |
| 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/DATA-SUB-AREA | Associative between these two objects | F | F | F | "architectural status" "data subject area" name |
| 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" |
| BUSINESS-FOCUS/INFO-CLASS | Associative between these two objects | F | F | F | "architectural status" columndefinition columndefinitionkey1 name "rollout phase" rowdefinition |
| 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/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" |
| 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/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/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/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/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 |
| 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 |
| 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-INFORMATION-REQUIREMENT | To be defined by ITA Team | T | F | F | BIR_description BIR_ID |
| 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" |
| C-&-A-BOUNDARY | All components of an information system to be accredited by an authorizing official and excludes separately accredited systems, to which the information system is connected. Synonymous with the term security perimeter defined in Committee on National Security Systems (CNSS) Instruction 4009 and Director of Central Intelligence Directive 6/3. (Source: NIST Special Publication 800-37) | F | T | F | "Accreditation Status" acronym "additional names" bureau ca300andl id "member system inventories" name outsourced production stype system_category |
| C-&-A-BOUNDARY (CATEGORIZATION) | Sub-Attributes of the C-&-A-BOUNDARY object; FIPS-199 Categorization status | T | F | T | availability confidentiality integrity securitycategorization |
| C-&-A-BOUNDARY (CONTACTS) | Sub-Attributes of the C-&-A-BOUNDARY object; Contact information related to this boundary | T | F | T | daa daa_email daa_phone owner owner_email owner_phone pia_completed_by pia_completed_by_email pia_completed_by_phone sso sso_email sso_phone system_mgr system_mgr_email system_mgr_phone |
| C-&-A-BOUNDARY (DATES) | Sub-Attributes of the C-&-A-BOUNDARY object; dates related to each document within the C&A Package for this boundary | T | F | T | acc asc_test avg ca800_26 cert cp cp_test fips-199 ra ssp st_e |
| C-&-A-BOUNDARY (PRIVACY) | Sub-Attributes of the C-&-A-BOUNDARY object; Privacy fields abstracted from a Privacy Impact Assessmen Document used in FISMA and Enterprise Reporting on Privacy Status | T | F | T | "completed privacy impact assessment" fed_owned_info fed_owned_info_a fed_owned_info_b fed_owned_info_c fed_owned_info_d "individuals doing business" "personnel privacy concerns" "pia comment" "pia completed" "pia required" pia_fed_owned_info_id pia_online_form pia_online_form_omb_number pia_online_form_omb_number_name pia_online_form_privacy_notice pia_records_name pia_records_notice prelim_pia "privacy act system of record" "public information individuals" |
| C-&-A-BOUNDARY (other FISMA) | Sub-Attributes of the C-&-A-BOUNDARY object; Additional FISMA fields as requested for reporting purposes | T | F | T | "c and a comments" "e-authentication eligible" "level of assurance required" "provider of services" "system criticality" "system internet need" |
| CAP-IMPLICATION | To be defined by ITA Team | T | F | F | cap_implication_description cap_implication_id |
| CAP-RATIONALE | To be defined by ITA Team | T | F | F | cap_rationale_description cap_rationale_id |
| 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" |
| COMMON-REQUIREMENTS-VISION | To be defined by ITA Team | T | F | F | crv_author crv_background crv_ID crv_introduction crv_version "External File 1" "External File 2" "External File 3" |
| COMP-INST-INTERFACE | 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 | bi-directional Delete description "from sub system" "from sub system version" "from system" "from system version" "from system-component-instance" initiator Initiator "joint it security requirements" "moa or mou complete" "operational frequency" "operational mode" "system interface capability" "to sub system" "to sub system version" "to system" "to system version" "to system-component-instance" type "written approval for esbablishing connection" |
| COMPONENT-ARCHITECTURE | Look table for valules. | T | F | F | name |
| COMPONENT-INSTANCE | A system component instance actually does (at least part of) what the system is made to do. A system component instance is physical--you actually deploy it on a processing node. In a car, the system component instance for the passenger-holding subsystem w | F | F | T | Acronym "data storage comment" "deployment mode" "deployment scope inter enterprise" "deployment scope outer enterprise" "deployment tiers" "execution environment comment" "future plans comment" "interface comment" name "operational month" "operational status" "operational year" "platform comment" "processing nodes" quantity "replaces system component instsances" "sub system" "sub system version" system "system component" "system component version" "system version" |
| COMPONENT_ | Independently deployable unit of software that exposes its functionality through a set of services accessed via well-defined interfaces. A component is based on a component standard, is described by a specification, and has an implementation. Components can be assembled to create applications or larger-grained components. | F | F | F | acronym "availability requirement" "component architecture design model" "component framework design model" "configuration management flag" "construction comment" "construction modification level" "cpic phase" "data exchange technique" "data interchange design model" "data storage comment" "data transformation design model" "database architecture design model" "delivery channel types" enterprise "enterprise architecture component state" "enterprise architecture component state rationale" "execution environment comment" "external system component" functionality "future plans comment" "government approved encryption algorithm usage" "managing partner" "message exchange protocol design model" "message format design model" "middleware architecture design model" "modification eligibility" name "organization roles" "ownership model" "performance requirement" "person roles" "platform comment" "replaces system components" "re-use design" "scalability requirement" scope "security authentication model" "security authorization model" "security comment" "service delivery model" "service discovery" "service interface design model" "software development lifecycle stage" "throughput requirement" "transport protocol design model" version |
| 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 |
| CONCEPTUAL-ARCHITECTURE-PRINCIPLE | To be defined by ITA Team | T | F | F | cap_author cap_background cap_ID cap_introduction cap_version |
| 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-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" |
| CRV-STRATEGY | To be defined by ITA Team | T | F | F | strategy_description strategy_ID |
| 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-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-KEY-GROUP | To be defined by IDA Team | T | F | F | "DATA-ENTITY-KEY-GROUP Identifier" |
| 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-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-QUALITY | T | F | F | "data quality comments" "data quality description" "data quality status" "integrating rating score" "inventory rating score" "modeling rating score" "next steps" priority "ref model mapping rating score" | |
| 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-STORE/SYSTEM-COMP-INST | This associative entity DATA-STORE/SYSTEM-COMP-INST 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 | "data store" name "sub system" "sub system version" system "system component instance" "system component instance version" "system version" |
| 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 |
| DEPLOYMENT-TIER | None | T | F | F | Name |
| 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" |
| DOCUMENT-INSTANCE | This Entity is utilized internall by System Architect to aid Report generation. It is not part of the DOI Enterprise Architecture Definition. | T | F | F | "Creating Office" Custodian "Cutoff Date" Disposition document-instance-name "Electronic Location" "File Scheme" GRS "HTML Link" "Media Type" "Paper Location" "Record Indicator" Status Vital |
| DOCUMENT-TYPE | This Entity is utilized internall by System Architect to aid Report generation. It is not part of the DOI Enterprise Architecture Definition. | T | F | F | Author Category "Document Status" document-type-name "File Name" ID Keywords Links "Report or Binder" "Revision Date" Synopsis Type "Version nbr" |
| DOMAIN-ARCH-PRINCIPLE | To be defined by ITA Team | T | F | F | "dap implications" "dap rationales" name "service components" "technology domain team" |
| 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 |
| ENTITY/SUB-SYSTEM | 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. This relatioinship has been taken to the lowest level (rather than sub-system) since if it is not known at the system component, then it is likely not known at the sub-system level. | F | F | F | columndefinition columndefinitionkey1 columndefinitionkey2 columndefinitionkey3 "crud info" "data store form of sharing" description intersection? name rowdefinition rowdefinitionkey1 |
| ENVIRONMENTAL-TREND | None | T | F | F | env_trend_description env_trend_ID |
| 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 |
| FOCUS | None | T | F | F | focus_idenifier |
| 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" |
| 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" |
| FUNCTION-ACTIVITY/ENTITY | This associative entity FUNCTION-ACTIVITY/DATA-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. | T | F | F | columndefinition columndefinitionkey1 "crud info" name "rollout/phase" rowdefinition |
| FUNCTION-ACTIVITY/SUB-SYSTEM | How the system component is utilized by business processes. Taken to the lowest level (rather than sub-system) since if it is not known at the system component, then it is likely not known at the sub-system level. | F | F | F | columndefinitionkey columndefinitionkey1 "data qualification" description intersection? name "process automation qualification" "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 |
| GOAL | T | F | F | name | |
| 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" |
| ICOM-ARROW | None | T | F | F | "business drivers" "data entities" delete name |
| 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-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" |
| INTERFACE_ | Generic Interface used in the SYSTEM-INTERFACE-DECOMPOSITION Diagram. Not keyed by to and from objects. | F | F | F | bi-directional "data entities" description initiator "joint it security requirements" "moa or mou complete" name "operational frequency" "operational mode" type "written approval for esbablishing connection" |
| 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" |
| 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 |
| 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 |
| ISSUE | None | T | F | F | "issue status" name |
| 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" |
| LOCATION-NODE | A Location Node could be a building, city, center, room, or other designation of a physical place. | F | F | T | "address 1" "address 2" city Delete Name "node type" "participating organizations" state "sub location noes" |
| 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 | |
| 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 | T | F | F | 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 |
| OBJECTIVE | T | F | F | name | |
| ORGANIZATION | AN ADMINISTRATIVE STRUCTURE WITH A MISSION. Agency, Bureau, Office, etc.... | T | F | F | "administrative loss rate" "business drivers" "category code" charter "child organizations" "classification code" "Data Quality Attributes" "Default Authorization Group" "duration type code" "enterprise type code" formal "interacting organizations" "managing organization" name "organization identifier" "organization roles" "parent organization" "primary activity code" "primary industry category code" purpose "symbol identifier" "team members" technical-service-specifications "type code" url |
| ORGANIZATION ADDRESS | None | T | F | F | "ORGANIZATION ADDRESS Identifier" |
| ORGANIZATION NAME | None | T | F | F | "ORGANIZATION NAME Identifier" "ORGANIZATION-NAME Category Code" |
| 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" |
| 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" |
| OUTER-DEPLOYMENT-SCOPE | Look table for valules. | T | F | F | name |
| 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 |
| PERSON | An actual person (rather than a position title) who fulfills a role (i.e. project manager) in relation to another entity such as a investment, system, etc. | F | F | F | address-line1 address-line2 "business drivers" city person-email person-id person-name phone1 phone2 state zip |
| POC/PERSON | 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 | role role-remarks |
| PROCESSING-NODE | Need definition. | F | F | T | "additional information comments" alias "asset id" "database/storage" "deep packet inspection" Delete "delivery servers" "hardware/infrastructure" "ip address" "known issues" "location node" "managing organization" name "node deployment month" "node deployment year" "parent processing nodes" "physical processing node" "point of contact information" "processing node functions" "Processing Node Type" "protocol capabilities" "serial number" "support platforms" "technology refresh date" |
| PROCESSING-NODE-FUNCTION | T | F | F | name | |
| PRODUCT | T | F | F | "business focus areas" "enterprise investments" name | |
| 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 |
| PROGRAM/PERSON-ROLE | Associative between these two objects | F | F | F | Delete name person program |
| 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" |
| RECOMENDATION-CATEGORY | None | T | F | F | name |
| 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" |
| REQUIREMENT-FOR-TECH-ARCH | None | T | F | F | TAR_description TAR_ID |
| ROLLOUT-PHASE | Look up table to determine phase for imiplementation or phase out. | T | F | F | Description Name |
| SECURITY-AUTHENTICATION-MODEL | None | T | F | F | 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" |
| 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-COMPONENT/COMPONENT_ | 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 | columndefinition columndefinitionkey1 description intersection? name "relationship type" "re-use design" "rollout/phase" "service system interaction" |
| 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" |
| 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" |
| STAKEHOLDER-CATEGORY | Existing SA Definition Type | T | F | F | name "stakeholder type" |
| 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 |
| 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" |
| STRATEGY | T | F | F | name | |
| 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" |
| SUB-SYSTEM | Subsystems are used to refer to groups of applications or components that form part of the system. A subsystem is a logical organization for a solution and is not directly deployed on the technology infrastructure. | F | F | F | acronym "current user total" description "full name" "geographic user description" "interface comment" "managing partner" "maximum user design" name "number of eauthentications per year" "number of users in g2b segment" "number of users in g2c segment" "number of users in g2g segment" "number of users in iee segment" "organizational roles" "peak concurrent user design" "peak concurrent user total" "replaces sub systems" system "system component instances" "system version" "user communities" "user design comment" version |
| SUB-SYSTEM-INTERFACE | Implemented as a info/data exchange line between two subsystems. | F | F | F | bi-directional Delete description "from sub-system" "from system" "from system version" "from version" initiator "joint it security requirements" "moa or mou complete" name "operational frequency" "operational mode" "to sub-system" "to system" "to system version" "to version" type "written approval for esbablishing connection" |
| 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" |
| SUPER-TYPE/SUB-SYSTEM | Associative between these two objects | F | F | F | "curd info" name "sub system" "sub system version" system "system version" |
| SUPPLIER | T | F | F | address contact name url | |
| SYSTEM-ARCHITECTURE | None | T | F | F | name |
| SYSTEM-INTERFACE | Used in diagrams such as SYSTEM-INTERFACE-DECOMPOSITION to show the sharing of information between two systems | F | F | F | bi-directional "data entities" Delete description "from system_" "from version" initiator "joint it security requirements" "moa or mou complete" name "operational frequency" "operational mode" "to system_" "to version" type "written approval for esbablishing connection" |
| SYSTEM-INVENTORY | Contains the Inventory Attributes of a System whereas SYSTEM_ contains the Architectural Details (Ref. Model Relationships, and other Arch. Info) Attribute Groups include: Primary BFA Associated BFA Data Collection (By Phase) Inventory Type (Dept., Bur, | F | F | F | "508 compliance" "additional names" "architectural status" "business focus areas" "data collection as of date" "data collection status" "department standards" "financial system type" "financial/mixed" "gao category" "internal description" "inventory comment" "inventory reasons" "inventory status" "inventory type" "managing partner" name "primary business focus area" "sensitive system" sifms "system criticality" "system internet need" "system inventory id" url |
| SYSTEM-INVENTORY (CONTACTS) | Sub-Attributes for SYSTEM-INVENTORY; Contact Information related to this System | F | F | F | owner owner_email owner_phone pia_completed_by pia_completed_by_email pia_completed_by_phone system_mgr system_mgr_email system_mgr_phone |
| SYSTEM-INVENTORY (FINANCIAL) | Sub-Attributes for SYSTEM-INVENTORY; Financial Reporting Status Information related to this System | F | F | F | "accounting standards" "agency information standard" "annual transaction volume" "custom development" "department standards" "end of life year" "estimated authorized users" "estimated federal support fte" "external reporting" "financial system id" "financial system type" "financial/mixed" fmfia gisra "implementation date" "information standard date" "internal reporting" "jfmip required" "last upgade date" "number served" "off the shelf" processing "replaced by fbms" sgl sifms source "standard data" "users of service" "version number" |
| SYSTEM-INVENTORY (GOVERNANCE) | Sub-Attributes for SYSTEM-INVENTORY; Governance related and requested metadata about a system typically used for external reporting needs | F | F | F | "egovernment initiative?" enterprise "gao category" "section 508" |
| SYSTEM-INVENTORY (PRIVACY) | Sub-Attributes for SYSTEM-INVENTORY; Privacy metadata abstracted from Privacy Impact Assessment documents to support enterprise Reporting Status Information related to this System | F | F | F | "completed privacy impact assessment" fed_owned_info fed_owned_info_a fed_owned_info_b fed_owned_info_c fed_owned_info_d "individuals doing business" "personnel privacy concerns" "pia comment" "pia completed" "pia required" pia_fed_owned_info_id pia_online_form pia_online_form_omb_number pia_online_form_omb_number_name pia_online_form_privacy_notice pia_records_name pia_records_notice prelim_pia "privacy act system of record" "public information individuals" |
| SYSTEM-INVENTORY (TRUST) | Sub-Attributes for SYSTEM-INVENTORY; Indian Trust Reporting Status Information related to this System (NOTE: This is not IITD) | F | F | F | "artifact not included" "core trust process" "iitd comment" "iitd data" "numberr of system users" "questionair returned" "secondary trust system sub category" "third trust system sub category" "transaction category" "trust system id" "trust system sub category" |
| SYSTEM-NODE | To be used as a container for grouping systems together on the SYSTEM-INTERFACE-DECOMPOSITION, SYSTEM-AREA-MAP, and ARCHITECTURE-MIGRATION diagrams. Will create a relationship that is reportable from the diagram. | F | F | F | "architectural status" Delete name |
| SYSTEM-PLATFORM | THE COLLECTION OF HARDWARE AND SOFTWARE USED BY A SYSTEM. | F | F | F | "SYSTEM-PLATFORM DESCRIPTION TEXT" |
| SYSTEM-TYPE | Look up table for system type. | T | F | F | name |
| 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 |
| SYSTEM_ | A discrete set of information resources organized for the collection, processing, maintenance, transmission, and dissemination of information, in accordance with defined procedures, whether automated or manual. (Source: OMB Circular A-130, Revised (OMB Circular A-130, Revised, Transmittal Memorandum No. r, Paragraph 6.q.) | F | F | F | acronym "application score" "construction comment" "data score" "data storage comment" "database architecture design model" "deployment scope inter enterprise" "deployment scope outer enterprise" "estimated end of system life" "execution environment comment" "full name" "future plans comment" "interface comment" "investment project" "mbt criterion and scoring" "mbt findings" "middleware architecture design model" name "operational environment comment" "operational month" "operational status" "operational year" "organization roles" "person roles" "platform comment" "process score" "replaces systems" "security architecture design model" "software development lifecycle stage" "sub systems" "system architecture design model" "system inventory" "system types" "technology score" "total score" Version |
| SYSTEM_/SYSTEM_ | Upudated via System to System Recommendations matrix. | F | F | F | columndefinition columndefinitionkey1 name recommendations "rollout/phase" rowdefinition rowdefinitionkey1 "status of systems" |
| TAA-CATEGORY | TBD | T | F | F | name |
| TAA-CRITERIA | TBD | T | F | F | name type |
| TAA-CRITERIA/SYSTEM | This associative entity TAA-CRITERIA/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. | T | F | F | name rationale score system "system version" |
| TAA-RECOMENDATION | TBD | T | F | F | "bea tactical solution - cost estimate" "bea tactical solution - level of effort" "business case" "fy(04) o&m funding" name "planning period" "protfolio manager prioritization" "recomendation type" |
| TAA-RECOMENDATION/SYSTEM | This associative entity TAA-RECOMENDATION/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. | T | F | F | name system "system version" "taa recomendation" "taa tactical areas" |
| TACTIC | T | F | F | name | |
| TECH-SPEC-CLASSIFICATION | Entries in the TRM reflect technology at all stages of life. In order to distinguish the new from the old, and to identify the capable and the unacceptable, a classification methodology has been developed and applied to the items in the TRM. DOI has developed a classification system that indicates where in the spectrum of useful and unusable these technology items lie, and what restrictions govern their application. Discussion is still underway concerning a finalized list of classifications, but Exhibit 4 2 shows the current set of classifications used and their significance for technology acquisition and use. Life Cycle Classifications Definition Comments Preferred The product/technology maps to and is consistent with the target Interior Solution Architecture and is representative of the DOI's strategic direction for IT solutions. If licensed by DOI, this technology must be used within its intended functional/technical domain (i.e., context) where it satisfies mission needs. Limited The product/technology is preferred only for a particular bureau or service, or for a particular sub-function within a line of business and its use will be limited to that bureau, service or sub-function Contained The product/technology does not map to and/or is not consistent with the target Interior Solution Architecture and is not representative of the DOI's strategic direction for IT solutions. The product/technology is targeted for retirement at the soonest practicable date. Obsolete The product/technology is not currently used at DOI and is not representative of the DOI's strategic direction for IT solutions. Pending The product/technology has not yet been classified as any of the above values. Rejected Product/Standard has been evaluated and found not to meet technical architecture needs or to have serious security flaws. IEA Waiver typically not allowed. This classification is not currently used in the TRM | T | F | F | description name |
| TECH-SPEC-USAGE | TRM v3.0 Object - Requires Definition | T | F | F | characteristics classification name organizations platform "requirements met" "service components" "technical service specification" "technical service specification version" |
| TECH-SVC-SPEC/PERSON-ROLE | This associative entity TECH-SVC-SPEC/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 | Person Role "Role Remarks" "Technical Service Specification" Version |
| TECH-SVC-SPEC/SCOMPONENT_ | Associative to relate tech specs to system compoents. Future use will contain service components employed, suppliers, rollout phase, and whether is deployed or not. TRM future. | T | F | F | columndefinition columndefinitionkey1 deployed? name "rollout/phase" rowdefinition "service components" suppliers |
| TECHNICAL-REFERENCE-MODEL | The top node of the Technical Reference Model | T | F | F | "child technical service areas" name |
| TECHNICAL-SERVICE-AREA | The TRM is comprised of four (4) core Service Areas. Service Areas represent a technical tier supporting the secure construction, exchange, and delivery of Service Components. | T | F | F | "best practices" comments description "fea code" name "skills compositions" |
| TECHNICAL-SERVICE-CATEGORY | Service Category – is a sub-tier of the Service Area to classify lower levels of technologies, standards, and specifications in respect to the business or technology function they serve. | T | F | F | "best practice" comments description "fea code" name "skills compositions" "technical service area" |
| TECHNICAL-SERVICE-SPEC | A technical service specification is a product. | T | F | F | "best practices" comments "contact information" description "IPv6 Compliant" "license explanation" "license status" manufacturer "manufacturer upgrade plan" name "technical service category" "technical service specification roles" "technical service standard" TSS-TYPE Usages version |
| TECHNICAL-SERVICE-STANDARD | Standard – hardware, software, or specifications that are widely used and accepted (de facto), or are sanctioned by a standards organization (de jure). Standards are typically categorized as follows: Programming Language Standards Character Code Standards | T | F | F | "best practices" comments description "fea code" name "service componets" "skills compositions" "technical service category" "technical service specifications" |
| USER-COMMUNITY | A category of individuals who interact with a sub-system in a like way and for similar purposes. | T | F | F | name |
| VISION | T | F | F | name |
| 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 | 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 | F | "AGREEMENT-ASSOCIATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ACTION-DOCUMENT IDENTIFIER | THE IDENTIFIER THAT REPRESENTS AN ACTION-DOCUMENT. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | ||||||||||
| Analysis Process ACTION IDENTIFIER | THE UNIQUE IDENTIFIER THAT REPRESENTS A SPECIFIC ACTION. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | ||||||||||
| ARCHITECTURE IDENTIFIER | THE IDENTIFIER OF A SPECIFIC ARCHITECTURE. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | ||||||||||
| ARCHITECTURE-ANALYSIS-PROCESS-RESULT IDENTIFIER | THE IDENTIFIER OF AN ARCHITECTURE-ANALYSIS-PROCESS-RESULT FOR A SPECIFIC ARCHITECTURE AND A SPECIFIC ANALYSIS-PROCESS. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | ||||||||||
| ARCHITECTURE-PROJECT IDENTIFIER | THE IDENTIFIER OF AN ARCHITECTURE-PROJECT FOR A SPECIFIC ARCHITECTURE AND A SPECIFIC PROJECT. | TBD | F | New | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | |||||||||
| Project ACTION IDENTIFIER | THE UNIQUE IDENTIFIER THAT REPRESENTS A SPECIFIC ACTION. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" | ||||||||||
| Project DOCUMENT IDENTIFIER | THE IDENTIFIER THAT REPRESENTS A DOCUMENT. | TBD | F | "ARCHITECTURE-PROJECT-ANALYSIS-RESULT" |
| 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 | Members of the Domain Advisory Team | TBD | F | "BEST-PRACTICE" | ||||||||||
| name | Best practice name... | TBD | F | "BEST-PRACTICE" |
| 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 | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| business driver type | Look up table of BD types. TBD | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| business focus areas | Complex matrix Business Focus Area to Business Driver from associative is BUSINESS-FOCUS/BUSINESS-DRIVER | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| citation | What ever document it came from, e.g. USC Title 25, Public Law 108-74, DM 34, Cobell v. Norton, Policy Memo, etc. NOT a doc link, this is text | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| citation initial date | When the law passed, ruling was delivered, etc. | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| citation last changed | When the citation was last changed (law amended, ruling overturned, etc.) | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| end outcomes | TBD | F | "BUSINESS-DRIVER" | |||||||||||
| in effect | T/F flag for whether the mandate is still in effect | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| intermediate outcomes | TBD | F | "BUSINESS-DRIVER" | |||||||||||
| level | Corporate - Corporate level (Federal, Departmental and Agencies) Business Unit - Business unit level (Deputy Chief &Regional level within Agencies) Functional - Functional level (Responsibility for functions) | Unknown | TBD | F | Values: Corporate Business Unit Functional NA Unknown | "BUSINESS-DRIVER" | ||||||||
| mandate final date | When the policy expires, law is repealed, etc (e.g. when the In Effect flag changed from T to F) | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| name | Identifier for the business drivers derived from the DOI TRM | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| organizations | Complex matrix Business Driver to Organization from associative is BUSINESS-DRIVER/ORGANIZATION | TBD | F | "BUSINESS-DRIVER" | ||||||||||
| persons | Complex matrix Business Driver to Person from associative is BUSINESS-DRIVER/PERSON | TBD | F | "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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 | 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 | 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 | 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/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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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/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 | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| BIR_description | Business Information Requirements description derived from the DOI TRM | TBD | F | "BUSINESS-INFORMATION-REQUIREMENT" | ||||||||||
| BIR_ID | Unique Identifier of the Business Information Requirement (BIR) | TBD | F | "BUSINESS-INFORMATION-REQUIREMENT" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Accreditation Status | Unknown | TBD | T | ATO IATO No Authorization to Operate Unknown | "C-&-A-BOUNDARY" | |||||||||
| acronym | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY" | ||||||||||
| additional names | TBD | F | "C-&-A-BOUNDARY" | |||||||||||
| bureau | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY" | ||||||||||
| ca300andl | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | No | TBD | T | Yes No Undetermined NA Unknown | "C-&-A-BOUNDARY" | ||||||||
| id | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY" | ||||||||||
| member system inventories | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly Only updated if the security application type is General Support System | TBD | F | "C-&-A-BOUNDARY" | ||||||||||
| name | TBD | F | "C-&-A-BOUNDARY" | |||||||||||
| outsourced | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | No | TBD | T | Yes No Undetermined NA Unknown | "C-&-A-BOUNDARY" | ||||||||
| production | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | No | TBD | T | Yes No Undetermined NA Unknown | "C-&-A-BOUNDARY" | ||||||||
| stype | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly. Assigned by NIST 800-60. | TBD | T | VALUE MA VALUE GSS | "C-&-A-BOUNDARY" | |||||||||
| system_category | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | VALUE AOSS VALUE BES VALUE Financial DEPICTIONS VALUE MCS VALUE NCIIS VALUE NSIS VALUE Trust VALUE NA VALUE Unknown | "C-&-A-BOUNDARY" |
| 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 | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (CATEGORIZATION)" | |||||||||
| confidentiality | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (CATEGORIZATION)" | |||||||||
| integrity | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (CATEGORIZATION)" | |||||||||
| securitycategorization | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | T | VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (CATEGORIZATION)" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| daa | PERSON_ designated as DAA. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| daa_email | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| daa_phone | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| owner | PERSON_ designated as owner. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| owner_email | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| owner_phone | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| pia_completed_by | PERSON_ whom completed the privacy information act. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| pia_completed_by_email | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| pia_completed_by_phone | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| sso | PERSON_ designated as SSO. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| sso_email | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| sso_phone | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| system_mgr | PERSON_ designated as system manager. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| system_mgr_email | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" | ||||||||||
| system_mgr_phone | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (CONTACTS)" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| acc | Date Accredited C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| asc_test | Annual Security Controls Test Date. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| avg | Asset Valuation Guide C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly Retired Field | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| ca800_26 | Annual Self Evaluation. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| cert | Date Certified. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| cp | Contingency Plan Date. C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| cp_test | Contingency Plan Test Date C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| fips-199 | C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| ra | Risk Assessment Date C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| ssp | System Security Plan C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" | ||||||||||
| st_e | Security Testing and Evaluation C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly | TBD | F | "C-&-A-BOUNDARY (DATES)" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| completed privacy impact assessment | A Yes or No indicator that signifies whether or not the system owner or system manager has developed a Privacy Impact ssessment. This is needed for systems with information about individuals. | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| fed_owned_info | Does the system have Federally-owned information in an identifiable form? Does the system have Federally-owned information in an identifiable form [(i.e. Information on Individuals, linked back to the individual). | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| fed_owned_info_a | Is this information identifiable to the individual? If there is NO information collected, maintained, or used that is identifiable to the individual in the system, the remainder of the Privacy Impact Assessment does not have to be completed. | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| fed_owned_info_b | Is the information about individual members of the public? If YES, a PIA must be submitted with the OMB Exhibit 300, and with the IT Security C&A documentation. | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| fed_owned_info_c | Is the information about employees? If yes and there is no information about members of the public, the PIA is required for the DOI IT Security C&A process, but is not required to be submitted with the OMB Exhibit 300 documentation | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| fed_owned_info_d | Does the system contain information on Individuals Doing Business for the public? If yes, a PIA is required | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| individuals doing business | A Yes or No indicator that signifies whether or not the system maintains information on individuals who interact with the Department as small business owners. | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| personnel privacy concerns | A Yes or No indicator that signifies whether or not the system maintains information on individuals and may therefore have privacy concerns. | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| pia comment | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | |||||||||||
| pia completed | If PIA Required, when was PIA Completed? | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| pia required | Is this PIA required. | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_fed_owned_info_id | If PIA Required LABEL Federally-owned information is retrieved by name or unique identifier? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_online_form | If PIA Required, Was an online form used to collect the Privacy Information? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_online_form_omb_number | Does the form contain the OMB Approval #? If yes to Was an online form used to collect the Privacy Information? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_online_form_omb_number_name | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | |||||||||||
| pia_online_form_privacy_notice | Does the page housing the form have the appropriate web privacy notices? If yes to Was an online form used to collect the Privacy Information? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_records_name | Records Notice Name If yes to does this system operate under a Privacy Act Systems of Records Notice? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| pia_records_notice | If PIA Required LABEL Does this system operate under a Privacy Act Systems of Records Notice? | No | TBD | T | Yes No Undetermined | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||
| prelim_pia | MM/DD/YYYY - All Systems required a Preliminary PIA and date completed | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| privacy act system of record | A Yes or No indicator that signifies whether or not the system has information which can be retrieved by a name or other personal identifier (employee ID, SSN etc). | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" | ||||||||||
| public information individuals | A Yes or No indicator that signifies whether or not the system maintains information on individuals who are not DOI employees. | TBD | F | "C-&-A-BOUNDARY (PRIVACY)" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| c and a comments | additional comments about C&A. | TBD | F | "C-&-A-BOUNDARY (other FISMA)" | ||||||||||
| e-authentication eligible | Yes if the system is browser-based AND public facing AND requires end-user authentication. Update 800-63 RA Date if Yes | TBD | F | "C-&-A-BOUNDARY (other FISMA)" | ||||||||||
| level of assurance required | Legal values are 1-4. Results of the 800-63 Risk Assessment (if required) | TBD | F | 1 - 4 are only valid values. | "C-&-A-BOUNDARY (other FISMA)" | |||||||||
| provider of services | TBD | T | VALUE External Cross-Servicing VALUE Government Wide VALUE Contractor Owned VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (other FISMA)" | ||||||||||
| system criticality | Defines level of system criticality. | TBD | T | VALUE Protects Life VALUE Protects Property VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (other FISMA)" | |||||||||
| system internet need | Defines reliance or awareness of the internet. | TBD | T | VALUE Requires Internet VALUE Aware of Internet VALUE Not Aware of Internet VALUE NA VALUE Unknown | "C-&-A-BOUNDARY (other FISMA)" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cap_implication_description | The Interior Enterprise Architecture (IEA) Conceptual Architecture Principles (CAP) represents core business and technical guidelines upon which all Interior-wide technical domain architectures will be based. These principles guide the implementation of technology to meet Interior-wide requirements as well as guide decision-making to maximize business benefit and the adaptability of the IT environment. | TBD | F | "CAP-IMPLICATION" | ||||||||||
| cap_implication_id | Unique Identifier of the Conceptual Architecture Principles (CAP) | TBD | F | "CAP-IMPLICATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cap_rationale_description | This field describes the series of rationales for the CAP (Conceptual Architecture Principle) | TBD | F | "CAP-RATIONALE" | ||||||||||
| cap_rationale_id | Unique identified for CAP (Conceptual Architecture Principle) | TBD | F | "CAP-RATIONALE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CATEGORY-RELATIONSHIP COMPLETENESS CODE | THE CODE THAT REPRESENTS THE ENTIRETY OF A CATEGORY-RELATIONSHIP. | TBD | F | "CATEGORY-RELATIONSHIP" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| crv_author | Common Requirements Vision Author | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| crv_background | The background section text of the CRV document | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| crv_ID | Identifier for the common requirements vision (CRV) | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| crv_introduction | The introductory text of the CRV document | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| crv_version | Version of the common requirements vision document | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| External File 1 | Pointer to document of Common Requirements Vision | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| External File 2 | Pointer to document of Common Requirements Vision | TBD | F | "COMMON-REQUIREMENTS-VISION" | ||||||||||
| External File 3 | Pointer to document of Common Requirements Vision | TBD | F | "COMMON-REQUIREMENTS-VISION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bi-directional | Describes if the interface communicates/shares data in both directions | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| Delete | TBD | F | "COMP-INST-INTERFACE" | |||||||||||
| description | Brief Description of the interface, though usually the name is sufficient - exceptions only | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| from sub system | The related sub-system to SYSTEM-COMP-INST-INTERFACE | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| from sub system version | The Sub-system Version | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| from system | The Parent system of the sub-system/SCI interfacing from | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| from system version | The System Version | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| from system-component-instance | The from system-component-instance related to SYSTEM-COMP-INST-INTERFACE | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| initiator | Initiator List | TBD | T | Source Target Neither NA Unknown | "COMP-INST-INTERFACE" | |||||||||
| Initiator | Flags the system component instance in the relationship as the SCI that initiates the interface | TBD | T | Source Target Neither NA Unknown | "COMP-INST-INTERFACE" | |||||||||
| joint it security requirements | For AVG use only default F. | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| moa or mou complete | For AVG use only default F. | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| operational frequency | Describes the frequency/how often the interface operates (see values) | TBD | T | Daily Daily+ Weekly Bi-Weekly Monthly Monthly+ Real-time Other NA Unknown VALUE Other VALUE NA VALUE Unknown } | "COMP-INST-INTERFACE" | |||||||||
| operational mode | Describes the mode/how the interface operates (see values) | Unknown | TBD | T | Batch Interactive Manual NA Unknown | "COMP-INST-INTERFACE" | ||||||||
| system interface capability | Describes the Technological capabilities of the Interface as it relates to the TRM and other Technical Capabilities that can be described | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| to sub system | The related sub-system to SYSTEM-COMP-INST-INTERFACE | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| to sub system version | The Sub-system Version | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| to system | The Parent System of the sub-system/SCI interfacing to | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| to system version | The System Version | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| to system-component-instance | The to system-component-instance related to SYSTEM-COMP-INST-INTERFACE | TBD | F | "COMP-INST-INTERFACE" | ||||||||||
| type | Interface Type List | Interface | TBD | T | Interface Interconnected Interdependant Information Sharing NA Unknown | "COMP-INST-INTERFACE" | ||||||||
| written approval for esbablishing connection | For AVG Use Only default F. | TBD | F | "COMP-INST-INTERFACE" |
| 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 structure of the system component. The internal architecture is defined by the ability to distribute logically isolated processing tiers on different physical platforms. Examples of the different component architectures are: - Data Access component - a modular, logically isolated, deployable data access processing tier - Business Logic component - a modular, logically isolated, deployable business logic processing tier - Monolithic Presentation component - a single-platform, self-contained user interface presentation processing tier - Client-side Presentation component - a modular, logically isolated, deployable user interface presentation processing tier operating on the client - Server-side Presentation component - a modular, logically isolated, deployable user interface presentation processing tier operating on the server | TBD | T | Business Logic Component Client-side Presentation Component Custom Data Access Component Monolithic Presentation Component None Other Server-side Presentation Component Unknown | "COMPONENT-ARCHITECTURE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Acronym | Abbreviations for the system component instance - typically same as the system component | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| data storage comment | Comments on the data storage environment of the system component that are not captured elsewhere. | TBD | F | Alphanumeric | "COMPONENT-INSTANCE" | |||||||||
| deployment mode | The mode of deployment for this instance (see values) | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| deployment scope inter enterprise | Breadth of deployment and intended usage of this system component within the owning organization. Designation of National means: All IT investments that support multiple program areas, affect multiple States, or cost more than $500,000 over the total life cycle are defined as National investments. Designation of National means: All IT investments that support multiple program areas, affect multiple States, or cost more than $500,000 over the total life cycle are defined as National investments. | Unknown | TBD | F | Field Office State National Regional NA Unknown | "COMPONENT-INSTANCE" | ||||||||
| deployment scope outer enterprise | Breadth of deployment and intended usage of this system component beyond the owning organization. This is the organizational scope of this system component beyond the enterprise. | Unknown | TBD | F | Commercial-E-Government Inter-DOI Inter-Federal Government Inter-Other Government Inter-State Government NA Public-E-Government Unknown | "COMPONENT-INSTANCE" | ||||||||
| deployment tiers | The Tier that this SCI represents when deployed (see values) | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| execution environment comment | Comments on the execution environment of the system component that are not captured elsewhere including software technology migration plans | TBD | F | Alphanumeric | "COMPONENT-INSTANCE" | |||||||||
| future plans comment | Comments on the future plans for the system component for development, consolidation with other applications, COTS replacement strategy or future enhancement planned (i.e. geospatial enablement) that are not captured elsewhere. | TBD | F | Alphanumeric | "COMPONENT-INSTANCE" | |||||||||
| interface comment | TBD | F | "COMPONENT-INSTANCE" | |||||||||||
| name | TBD | F | "COMPONENT-INSTANCE" | |||||||||||
| operational month | The month of the actual or planned deployment of the system component. | Unknown | TBD | F | 1 2 3 4 5 6 7 8 9 10 11 12 Unknown | "COMPONENT-INSTANCE" | ||||||||
| operational status | The status of the actual or planned deployment of the system component. Operational – Currently in operation. Under Development – Being designed, developed or implemented. Under Procurement – Being evaluated for procurement. Undergoing A Major Modification – Undergoing a major conversion or transition. Unknown – The operational status is not known at this time. | Unknown | TBD | F | Operational Under Development Under Procurement Undergoing A Major Modification NA Unknown | "COMPONENT-INSTANCE" | ||||||||
| operational year | The year of the actual or planned deployment of the system component. | Unknown | TBD | F | 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 Unknown | "COMPONENT-INSTANCE" | ||||||||
| platform comment | Comments on the platform (hardware) environment of the system component that are not captured elsewhere, including hardware technology migration plans. | TBD | F | Alphanumeric | "COMPONENT-INSTANCE" | |||||||||
| processing nodes | The processing nodes related to the SYSTEM-COMPONENT-INSTANCE | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| quantity | # of times this instance deployed | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| replaces system component instsances | The SCIs that are Replaced by this SCI | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| sub system | The sub system related to the SYSTEM-COMPONENT-INSTANCE | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| sub system version | The Sub-system Version | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| system | The system related to the SYSTEM-COMPONENT-INSTANCE | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| system component | The system component related to the SYSTEM-COMPONENT-INSTANCE | TBD | F | "COMPONENT-INSTANCE" | ||||||||||
| system component version | TBD | F | "COMPONENT-INSTANCE" | |||||||||||
| system version | Version of Parent System | TBD | F | "COMPONENT-INSTANCE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| acronym | Abbreviations for the system component. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| availability requirement | What are the business requirements for the daily period that this system component needs to be available to users (expressed as a percentage of the period)? | Unknown | TBD | T | Less than 70% 70 - 80% 80 - 90% 90 - 95% 95 - 100% Unknown | COMPONENT_ | ||||||||
| component architecture design model | The type of the system component in relation to the logical component architecture processing tier. Need to check the attribute name. Tim indicates that this should be component architecture type. Examples of the different component architectures are: - Data Access component - a modular, logically isolated, deployable data access processing tier - Business Logic component - a modular, logically isolated, deployable business logic processing tier - Monolithic Presentation component - a single-platform, self-contained user interface presentation processing tier - Client-side Presentation component - a modular, logically isolated, deployable user interface presentation processing tier operating on the client - Server-side Presentation component - a modular, logically isolated, deployable user interface presentation processing tier operating on the server | TBD | T | Business Logic Component Client-side Presentation Component Custom Data Access Component Monolithic Presentation Component None Other Server-side Presentation Component Unknown | New | COMPONENT_ | ||||||||
| component framework design model | Comment on the Component Framework Design of this System Component. Did it follow any industry Framework patterns, any futher comments on how services are exposed. | TBD | F | COMPONENT_ | ||||||||||
| configuration management flag | Indicator of the Interior Configuration Management baseline status of this item. | Y | TBD | T | Y N Unknown | COMPONENT_ | ||||||||
| construction comment | Comments on the construction of the system component that are not captured elsewhere. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| construction modification level | Indicator of the extent of the alteration of a system component from its initial state. Maintenance & Enhancement - An administrative decision has been made to control the scope and/or growth of an internal-maintenance-responsibility system component by limiting modifications to maintaining and enhancing existing functionality. Maintenance Only - An administrative decision has been made to limit the money and effort spent on an internal-maintenance-responsibility system component by restricting modification to maintenance work only (severity 1 and 2 bug fixes where 1 = mission critical fix, no work around, 2 = mission critical fix, work around exists, 3 = major bug, 4 = minor bug, 5 = cosmetic bug). Restricted - An administrative decision has been made to halt modifications to an internal-maintenance-responsibility system component except in extraordinary circumstance. External Maintenance & Enhancement –Agreements are in place to decide to control the scope and/or growth of an external-maintenance-responsibility system component by limiting modifications to maintaining and enhancing existing functionality. External Maintenance Only - Agreements are in place to decide to limit the money and effort spent on an external-maintenance-responsibility system component by restricting modification to maintenance work only (severity 1 and 2 bug fixes). External Restricted - Agreements are in place to decide to halt modifications to an external-maintenance-responsibility system component except in extraordinary circumstance. Unrestricted - No administrative restrictions imposed on modifications to this system component. Unknown - The administrative restrictions imposed on modifications to this system component are not known. | Unknown | TBD | T | Maintenance & Enhancement Maintenance Only Restricted External Maintenance and Enhancement External Maintenance Only External Restricted Unrestricted NA Unknown | COMPONENT_ | ||||||||
| cpic phase | If tracked by IT Investment (CPIC, SCO, etc.), what is the phase assigned to this system component by SCO? Examples are: 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. Mixed-LifeCycle – Phases in CPIC do not map to lifecycle of project. Phase used in Ex. 300 Rejected – Not Selected Withdrawn – No longer an Application Candidate | Unknown | TBD | T | Select Control Evaluate Rejected Withdrawn Potential Terminated Not Tracked Unknown | COMPONENT_ | ||||||||
| data exchange technique | Method used for the data exchange during the execution of the interface. | Unknown | TBD | T | File Transfer Message Broker Procedure Call Method Invocation EDI Store/Forward Publish/Subscribe NA Unknown | COMPONENT_ | ||||||||
| data interchange design model | The data interchange technologies used for the interface. Data Interchange is concerned with the sending of data over a communications network. Need to correct typo in attribute name. | TBD | F | COMPONENT_ | ||||||||||
| data storage comment | Comments on the data storage environment of the system component that are not captured elsewhere. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| data transformation design model | The rule-based data transformation technologies used for the interface. | TBD | F | COMPONENT_ | ||||||||||
| database architecture design model | The internal structuring or architecture of the database model for this system as a whole. | TBD | T | Custom Data Mart Data Warehouse DBMS Replication Enterprise Data Store Hierarchical DBMS Multi-Dimensionsl DBMS None Object DBMS Object-Relational DBMS OnLine Analytical Processing OnLine Transaction Processing Other Relational DBMS Unknown | COMPONENT_ | |||||||||
| delivery channel types | The delivery channel types supported by this interface capability. | TBD | T | Client-Server Extranet Internet Intranet Other Peep to Peer Standalone Unknown Virtual Private Network | COMPONENT_ | |||||||||
| enterprise | Allows enterprise reporting...default to Enterprise. | TBD | F | COMPONENT_ | ||||||||||
| enterprise architecture component state | EA state indicates the overall alignment of this component with the Enterprise Architecture and the commitment to continue to maintain the component in light of that alignment. | Unknown | TBD | T | Current Contain Retire NA Unknown | COMPONENT_ | ||||||||
| enterprise architecture component state rationale | The rationale or reasoning behind the assigned Enterprise Architecture state of this component. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| execution environment comment | Comments on the execution environment of the system component that are not captured elsewhere including software technology migration plans | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| external system component | A Yes or No indicator that defines a system component which is owned and managed by an external organization to this enterprise. | TBD | F | COMPONENT_ | ||||||||||
| functionality | The essential function that this interface capability performs. | Unknown | TBD | T | Data Replication Data Syncronization File Transfer Data Access Business Logic Processing Presentation Server Presentation Client NA Unknown | COMPONENT_ | ||||||||
| future plans comment | Comments on the future plans for the system component for development, consolidation with other applications, COTS replacement strategy or future enhancement planned (i.e. geospatial enablement) that are not captured elsewhere. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| government approved encryption algorithm usage | Security algorithms that have been implemented in this system component that have been approved for use by the US Federal Government. Choose any combination of list items that describe algorithms that have been implemented. | TBD | F | 128-bit SSL 256-bit SSL Custom None Other Triple DES Unknown | COMPONENT_ | |||||||||
| managing partner | TBD | F | COMPONENT_ | |||||||||||
| message exchange protocol design model | These protocols are those used by component frameworks in conjunction with supporting network services and service transport protocols to affect a message exchange. | TBD | F | COMPONENT_ | ||||||||||
| message format design model | The nature of the internal structure of the message being transmitted between platforms. | TBD | F | COMPONENT_ | ||||||||||
| middleware architecture design model | The internal structuring or architecture of the middleware model for this system as a whole. Middleware provides COTS application services that facilitate and simplify communication within and between heterogeneous, distributed application systems. Data Standards Definitions: Remote Data Access – Program-to-database capability to read or write to a database that is physically on a different platform using procedural techniques. Object Remote Data Access – Program-to-database capability to read or write to a database that is physically on a different platform using object-oriented techniques. Remote Procedure Calls – Program-to-program capability to call a programmed procedure on a physically different platform as though it were a local procedure. Remote Objects – Program-to-program capability to invoke a programmed method on an object that is on a physically different platform as though it were a local method. Transaction Processing – Program-to-program capability for processing units of work that update a single database on a single platform in either a completely committed manner or a completely undone (or rolled back) manner. Distributed Transaction Processing – Program-to-program capability for processing units of work that update databases on multiple, physically different platforms in either a completely committed manner or a completely undone (or rolled back) manner. Transactional Objects – Program-to-program capability for processing units of work via object-oriented method calls that update databases on multiple, physically different platforms in either a completely committed manner or a completely undone (or rolled back) manner. Message Queuing – Peer-to-peer middleware for program-to-queue communication that provides the capability to put a message (for deferred but guaranteed delivery to its destination) on a message queue. Object Request Broker -- the programming that acts as a broker between a client request for a service from a distributed object or component and the completion of that request. Having ORB support in a network means that a client program can request a service without having to understand where the server is in a distributed network or exactly what the interface to the server program looks like. Components can find out about each other and exchange interface information as they are running. Message Broker -- A software system based on asynchronous, store-and-forward messaging. It manages interactions between application and other information resources, using abstraction techniques such as publish and subscribe to mediate the interaction between applications, allowing the publishers and subscribers of information to truly remain anonymous. Message brokers transform and convert data, reformat and reconstitute messages, and route information to any number of targets (determined by centrally defined business rules applied to the message content). Message brokers have three primary components: the message transformation layer, the rules engine, and the intelligent routing mechanism. [Linthicum, David S. 2000] Web Services - a software system identified by a URI (Uniform Resource Identifiers a.k.a. URLs) are short strings that identify resources in the web: documents, images, downloadable files, services, electronic mailboxes, and other resources.), whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems may then interact with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols. [W3 2003.] Extract, Transform, and Load -- Software that facilitates the extraction, transformation, and loading of data from one database system to another. | TBD | T | Custom Distributed Transaction Processing Extract, Transform, and Load Message Brokers Message Queuing None Object Remote Data Access Object Request Brokers Other Remote Access Data Remote Objects Remote Procedure Calls Transaction Processing Transactional Objects Unknown | COMPONENT_ | |||||||||
| modification eligibility | Indicates extent of administrative restrictions on the modification of a system component. | TBD | F | Maintenance & Enhancement Maintenance Only Restricted External Maintenance and Enhancement External Maintenance Only External Restricted Unrestricted NA Unknown | COMPONENT_ | |||||||||
| name | Descriptive text that identifies the system component. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| organization roles | The organization roles related to the SYSTEM-COMPONENT | TBD | F | COMPONENT_ | ||||||||||
| ownership model | Indicator of the model under which the system component was procured and therefore affecting ownership and maintenance responsibilities. Data Standards Definitions: Commercial Custom - a system component provider has supplied a commercial system component internally altered to be made proprietary to the INTERIOR. Commercial Off The Shelf – a commercially-available system component acquired with generally-available behavior and documentation from an external application provider. Government Custom – a non-INTERIOR Government system component provider has provided a non-INTERIOR Government system component internally altered to be made proprietary to the INTERIOR. Government Off The Shelf – a Government-available system component acquired with generally-available behavior and documentation from a non-INTERIOR Government system component provider. Custom – a system component that was developed and documented to INTERIOR proprietary specifications. Leased Service – system component processing is performed under an externally-acquired service model versus a purchase model. Not Applicable (External) – system component processing is performed under an externally-acquired service model versus a purchase model. | TBD | T | Commercial Custom Commercial Off The Shelf Government Custom Government Off The Shelf Custom Application Leased Service Not Applicable (External) NA Unknown | COMPONENT_ | |||||||||
| performance requirement | Tthe business requirements for the maximum response time in seconds of a typical transaction during the peak processing period of this system component? | Unknown | TBD | T | .1 - .9 1 - 3 3 - 5 5 - 10 0 - 60 More than 60 Unknown | COMPONENT_ | ||||||||
| person roles | The person roles related to the SYSTEM-COMPONENT | TBD | F | COMPONENT_ | ||||||||||
| platform comment | Comments on the platform (hardware) environment of the system component that are not captured elsewhere, including hardware technology migration plans. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| replaces system components | System Component(s) planned to replace this component | TBD | F | COMPONENT_ | ||||||||||
| re-use design | Indicator if the System Component is considered to be reusable. | Unknown | TBD | T | Not-Reuseable Limited Re-Use Enterprise Re-Use NA Unknown | COMPONENT_ | ||||||||
| scalability requirement | The business requirements for the percentage of the peak processing load that this system component needs to be able to sustain with adequate performance on a short term basis without major architectural modification? | Unknown | TBD | T | 100% 100 - 150% 150 - 200% Over 200% Unknown | COMPONENT_ | ||||||||
| scope | An interface capability is internal to the container subsystem (used only by other system component elements of this system) or external to the container subsystem (a published and maintained interface available to components outside of this system component). Should only external interfaces to the system component be modeled? An interface can be both internal and external. | Unknown | TBD | T | Internal Between System Components External Between System Components NA Unknown | COMPONENT_ | ||||||||
| security authentication model | The method(s) employed by the system component to identify configured users. look up table for security authentication. | TBD | F | COMPONENT_ | ||||||||||
| security authorization model | The method(s) employed by the system component to identify the configured permissions to system component resources for identified users. Choose any combination of list items that describe the models that have been implemented. | TBD | T | Administrative User Anonymous User Authenticated User Custom None Other Power User Unknown | COMPONENT_ | |||||||||
| security comment | A text description of relevant additional security design information. | TBD | F | Alpha-numeric | COMPONENT_ | |||||||||
| service delivery model | The delivery channel model implemented by this interface capability. | Unknown | TBD | T | Portal Integration Systems Integration Marketplace Data Access Exchange Commerce Custom Other NA Unknown | COMPONENT_ | ||||||||
| service discovery | The technology used to discover the interface capability. Many systems assume a direct connection to an interface instead of using a discovery process. Service Discovery Defines the method in which applications, systems or web services are registered and discovered. UDDI – (Universal Description Discovery and Integration) UDDI provides a searchable registry of XML Web Services and their associated URLs and WSDL pages. http://www.uddi.org/about.html | Unknown | TBD | T | Universal Description Discovery and Integration Other NA Unknown | COMPONENT_ | ||||||||
| service interface design model | Defines the technology used to describe the programming interface to the component. | TBD | F | COMPONENT_ | ||||||||||
| software development lifecycle stage | See values | Unknown | TBD | T | VALUE Project Definition VALUE System/Services Acquisition VALUE System Design VALUE System Development/Construction VALUE User/System Acceptance Testing VALUE Transition/Deployment VALUE NA VALUE Unknown | COMPONENT_ | ||||||||
| throughput requirement | The business requirements for the number of transactions per day required of this system component | Unknown | TBD | T | 0 - 100 100 - 200 200 - 500 500 - 1000 1000 - 5000 5000 - 10000 More than 10000 Unknown | COMPONENT_ | ||||||||
| transport protocol design model | The structured message exchange communication processes (protocols) used for the interface at the network transport layer. | TBD | F | COMPONENT_ | ||||||||||
| version | Text that identifies the configuration management version of the System Component. | TBD | F | Alpha-numeric | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cap_author | Author of the CAP Document | TBD | F | "CONCEPTUAL-ARCHITECTURE-PRINCIPLE" | ||||||||||
| cap_background | The background section text of the CAP document | TBD | F | "CONCEPTUAL-ARCHITECTURE-PRINCIPLE" | ||||||||||
| cap_ID | Identifier for the Conceptual Architecture Principles | TBD | F | "CONCEPTUAL-ARCHITECTURE-PRINCIPLE" | ||||||||||
| cap_introduction | The introductory text of the CAP document | TBD | F | "CONCEPTUAL-ARCHITECTURE-PRINCIPLE" | ||||||||||
| cap_version | The version of this Principle | TBD | F | "CONCEPTUAL-ARCHITECTURE-PRINCIPLE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPTUAL-DATA-MODEL CREATOR IDENTIFIER | THE IDENTIFIER OF THE AGENT RESPONSIBLE FOR CREATING A SPECIFIC CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL DEVELOPMENT METHODOLOGY NAME | THE NAME OF THE PROCEDURE USED TO DEVELOP A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL DEVELOPMENT STATUS IDENTIFIER | THE IDENTIFIER THAT REPRESENTS THE STATE OF DEVELOPMENT OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL DEVELOPMENT TOOL NAME | THE NAME OF THE MECHANISM USED TO DEVELOP A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL NOTATION STYLE NAME | THE NAME OF THE MEMORANDUM MANNER USED IN A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL PURPOSE TEXT | THE TEXT OF THE INTENTION OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL REFINEMENT LEVEL CODE | THE CODE THAT REPRESENTS THE LEVEL OF REFINEMENT OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL REVISION EFFECTIVE CALENDAR DATE | THE EFFECTIVE DATE OF AN AMENDMENT TO A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL SCOPE TEXT | THE TEXT OF THE BOUNDARIES OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL STATUS EFFECTIVE CALENDAR DATE | THE EFFECTIVE DATE OF THE STATE OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL TENSE CODE | THE CODE THAT REPRESENTS THE TIME DISTINCTION OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-MODEL" | ||||||||||
| CONCEPTUAL-DATA-MODEL TENSE EFFECTIVE CALENDAR DATE | THE EFFECTIVE DATE OF THE TIME DISTINCTION OF A CONCEPTUAL-DATA-MODEL. | TBD | F | "CONCEPTUAL-DATA-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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPTUAL-DATA-MODEL-VIEW CREATOR IDENTIFIER | THE IDENTIFIER OF THE AGENT RESPONSIBLE FOR CREATING A SPECIFIC CONCEPTUAL-DATA-MODEL-VIEW. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW" | ||||||||||
| CONCEPTUAL-DATA-MODEL-VIEW DATA STANDARDIZATION IDENTIFIER | THE IDENTIFIER OF A SPECIFIC CONCEPTUAL-DATA-MODEL-VIEW THAT PROVIDES TRACKING OF DATA STANDARDS. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW" | ||||||||||
| CONCEPTUAL-DATA-MODEL-VIEW SCOPE TEXT | THE TEXT OF THE BOUNDARIES OF A CONCEPTUAL-DATA-MODEL-VIEW. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION CREATION CALENDAR DATE | THE CREATION DATE OF A CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION" | ||||||||||
| CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION DEPENDENCY DESCRIPTION TEXT | THE TEXT THAT DESCRIBES THE DEPENDENCY OF A CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP COMMENT TEXT | THE TEXT OF OBSERVATIONS OF A CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP. | TBD | F | "CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| strategy_description | The text description for the strategies within the PRM and strategic plan | TBD | F | "CRV-STRATEGY" | ||||||||||
| strategy_ID | Unique identifier for the strategic plan strategy concept | TBD | F | "CRV-STRATEGY" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| attribute composition type name | Describes the structural makeup of a data attribute. Composition Type List | Unknown | TBD | T | Atomic Composite NA Unknown | "DATA-ATTRIBUTE" | ||||||||
| authoritative source | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| derivation procedure | Text that describes the algorithms, equation, logical expressiojn, or matrix used in deriving the data values for a data element. Will not show unless Derived is T. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| derived | Is the attribute derived if so mark as T. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| domain description | Text field for temporary storage of Domain Values from ERWin | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| domain values | List of DOMAIN-VALUE for future use in storing domain information. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| entity name | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| full name | Full Name fro ERWin if exceeded 80 chars. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| indian trus data | yes/No/NA List | Unknown | TBD | T | Yes No NA Unknown | "DATA-ATTRIBUTE" | ||||||||
| model | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| name | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| notes | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| precision | Represents Decimal Point Precision. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| reference source | TBD | F | "DATA-ATTRIBUTE" | |||||||||||
| security classification code | Will be pick list when values are determined. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| units of measure | will be pick list when values are determined. | TBD | F | "DATA-ATTRIBUTE" | ||||||||||
| xml tag name | TBD | F | "DATA-ATTRIBUTE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ALIAS IDENTIFIER | THE IDENTIFIER THAT REPRESENTS AN ALIAS. | TBD | F | "DATA-ATTRIBUTE-ALIAS" | ||||||||||
| DATA-ATTRIBUTE-ALIAS CREATION CALENDAR DATE | THE ORIGINATION DATE OF A DATA-ATTRIBUTE-ALIAS. | TBD | F | "DATA-ATTRIBUTE-ALIAS" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-ATTRIBUTE-ASSOCIATION TYPE CODE | THE CODE THAT REPRESENTS A KIND OF DATA-ATTRIBUTE-ASSOCIATION. | TBD | F | "DATA-ATTRIBUTE-ASSOCIATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-ATTRIBUTE-CHAIN PARTICIPANT TYPE CODE | The code that denotes a the kind of participation that a DATA-ATTRIBUTE plays in a DATA-ATTRIBUTE-CHAIN. | TBD | F | "DATA-ATTRIBUTE-CHAIN" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-ATTRIBUTE-CHAIN DATA ATTRIBUTE POSITION IDENTIFIER | THE IDENTIFIER THAT REPRESENTS THE PLACEMENT OF A DATA ATTRIBUTE WITHIN A DATA-ATTRIBUTE-CHAIN. | TBD | F | "DATA-ATTRIBUTE-CHAIN-MEMBER-ATTRIBUTE" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-ATTRIBUTE-DATA-TYPE NAME | THE NAME OF THE DATA-ATTRIBUTE-DATA-TYPE. | TBD | F | "DATA-ATTRIBUTE-DATA-TYPE" | ||||||||||
| DATA-ATTRIBUTE-DATA-TYPE TARGET ENVIRONMENT NAME | THE NAME OF THE SETTING FOR A SPECIFIC DATA-ATTRIBUTE-DATA-TYPE. | TBD | F | "DATA-ATTRIBUTE-DATA-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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-ATTRIBUTE-DERIVED ALGORITHM TEXT | THE TEXT OF THE DERIVATION FORMULA OF A DATA-ATTRIBUTE-DERIVED. | TBD | F | "DATA-ATTRIBUTE-DERIVED" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| User Presentation View INFORMATION-ASSET IDENTIFIER | THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. | TBD | F | "DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD" | ||||||||||
| USER-PRESENTATION-VIEW-FIELD IDENTIFIER | THE IDENTIFIER THAT REPRESENTS A USER-PRESENTATION-VIEW-FIELD. | TBD | F | "DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Data Class INFORMATION-ASSET IDENTIFIER | THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. | TBD | F | "DATA-CLASS" | ||||||||||
| DATA-CLASS CATEGORY NAME | THE NAME OF THE CLASSIFICATION OF A DATA-CLASS. | TBD | F | "DATA-CLASS" | ||||||||||
| DATA-CLASS TYPE CODE | THE CODE THAT REPRESENTS A KIND OF DATA-CLASS. | TBD | F | "DATA-CLASS" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-DICTIONARY TYPE CODE | THE CODE THAT REPRESENTS A KIND OF DATA-DICTIONARY. | TBD | F | "DATA-DICTIONARY" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-DICTIONARY-ELEMENT APPROVAL STATUS CALENDAR DATE | THE CALENDAR DATE ON WHICH THE CURRENT LEVEL OF VALIDITY WAS REACHED FOR A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT APPROVAL STATUS CODE | THE CODE THAT REPRESENTS THE LEVEL OF VALIDITY OF A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT DEFINITION TEXT | THE TEXT THAT STATES THE PRECISE MEANING OF A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT FORMAT DESCRIPTION TEXT | THE TEXT THAT CHARACTERIZES THE PHYSICAL FORM OF A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT IDENTIFIER | THE IDENTIFIER OF A DATA-DICTIONARY-ELEMENT FOR A SPECIFIC DATA-DICTIONARY. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT NAME | THE NAME OF A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT SOURCE NAME | THE NAME OF THE ORIGIN OF A SPECIFIC DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| DATA-DICTIONARY-ELEMENT USAGE DESCRIPTION TEXT | THE TEXT THAT SUMMARIZES THE WAY A SPECIFIC DATA-DICTIONARY-ELEMENT IS INTENDED TO BE IMPLEMENTED. | TBD | F | "DATA-DICTIONARY-ELEMENT" | ||||||||||
| INFORMATION-ELEMENT IDENTIFIER | THE IDENTIFIER THAT REPRESENTS A SPECIFIC INFORMATION-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-DICTIONARY-ELEMENT-ASSOCIATION IDENTIFIER | THE IDENTIFIER OF A DATA-DICTIONARY-ELEMENT-ASSOCIATION FOR A SPECIFIC ORDINATE DATA-DICTIONARY-ELEMENT AND A SPECIFIC SUBORDINATE DATA-DICTIONARY-ELEMENT. | TBD | F | "DATA-DICTIONARY-ELEMENT-ASSOCIATION" | ||||||||||
| DATA-DICTIONARY-ELEMENT-ASSOCIATION TYPE CODE | THE CODE THAT REPRESENTS A KIND OF DATA-DICTIONARY-ELEMENT-ASSOCIATION. | TBD | F | "DATA-DICTIONARY-ELEMENT-ASSOCIATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DOCUMENT IDENTIFIER | This is supporting data structures for Reporting | TBD | F | "DATA-DICTIONARY-SPECIFICATION" |
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-DOMAIN CONSTRUCTION TYPE CODE | THE CODE THAT REPRESENTS A KIND OF CONSTRUCT OF A DATA-DOMAIN. | TBD | F | "DATA-DOMAIN" | ||||||||||
| DATA-DOMAIN FORMAT CODE | THE CODE THAT REPRESENTS THE JUSTIFICATION FORM OF A DATA-DOMAIN. | TBD | F | "DATA-DOMAIN" | ||||||||||
| DATA-DOMAIN MAXIMUM CHARACTER QUANTITY | THE MAXIMUM QUANTITY OF CHARACTERS OF A DATA-DOMAIN. | TBD | F | "DATA-DOMAIN" | ||||||||||
| DATA-DOMAIN TYPE CODE | THE CODE THAT REPRESENTS A KIND OF DATA-DOMAIN. | TBD | F | "DATA-DOMAIN" | ||||||||||
| DATA-DOMAIN VALUE TYPE CODE | THE CODE THAT REPRESENTS A KIND OF VALUATION OF A DATA-DOMAIN. | TBD | F | "DATA-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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DATA-DOMAIN-BASE DATA TYPE NAME | THE NAME OF A KIND OF DATA IN A DATA-DOMAIN-BASE. |