Entity Name |
Entity Description |
IsCoreData |
IsSecurityData |
IsSensitive |
Glossary Model Object Properties |
Attribute Name |
Attribute Description |
Data Collection Comment |
Data Collection Reason |
DEAR Data Requirement |
DEAR Default Value |
DEAR Team Assignment |
DOI Data Owner |
Domain if Not Same as Entity |
Check if this is a Controlled List |
'List Of' Values |
Read-Only? |
Type of Change |
UsrProp Name |
Model Object |
ABC-WORK-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
|
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 |
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
|
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 |
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
|
doi program area contact(s) |
List of PERSON_ updated for contacts from programs areas. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
doi program area contacts |
Describes the nature of the role for an individual associated to the ABC program. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
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 |
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
|
doi sub process name |
Descriptive name for the supporting sub process |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
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 |
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
|
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 |
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
|
function activities |
The level of the BRM (business reference model ) hierarchical model from FUNCTION-ACTIVITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
inputs |
This is a list of the resources, policy , approvals, decisions etc that influence the work activity |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
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 |
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
|
organization |
The DOI agencies that are associated with this goal and work activity. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
outcomes |
The expected OUTCOME's of the effort described and codified . This is associated to the DOI work activity |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
output |
Provides a list of systems from which the metric information will be collected. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
program area |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
system interfaces |
Provides a list of systems from which the metric information will be collected. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ABC-WORK-ACTIVITY |
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
|
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 |
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 ABBREVIATED NAME |
THE SHORTENED FORM OF THE NAME FOR A SPECIFIC AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 CATEGORY CODE |
THE CODE THAT REPRESENTS A CLASSIFICATION OF AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 DESCRIPTION TEXT |
THE TEXT OF THE CHARACTERISTICS OF AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 DURATION TYPE CODE |
THE CODE THAT REPRESENTS A SPECIFIC KIND OF TIME FRAME ASSOCIATED WITH AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 EFFECTIVE CALENDAR DATE |
THE CALENDAR DATE WHEN AN AGREEMENT BECOMES EFFECTIVE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 EXPIRATION CALENDAR DATE |
THE CALENDAR DATE ON WHICH AN AGREEMENT IS NO LONGER IN FORCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 NAME |
HE NAME OF AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 TEXT |
THE TEXT OF AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 TYPE CODE |
THE CODE THAT REPRESENTS A SPECIFIC KIND OF AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 USE CATEGORY CODE |
THE CODE THAT REPRESENTS A CLASS OF EMPLOYMENT OF A SPECIFIC AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
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 VERSION IDENTIFIER |
THE IDENTIFIER OF A SPECIFIC RENDITION OF A SPECIFIC AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT |
AGREEMENT-ASSOCIATION |
AN ASSOCIATION BETWEEN AN AGREEMENT AND ANOTHER AGREEMENT. |
T |
F |
F |
AGREEMENT-ASSOCIATION IDENTIFIER
AGREEMENT-ASSOCIATION REASON CODE
|
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 |
AN ASSOCIATION BETWEEN AN AGREEMENT AND ANOTHER AGREEMENT. |
T |
F |
F |
AGREEMENT-ASSOCIATION IDENTIFIER
AGREEMENT-ASSOCIATION REASON CODE
|
AGREEMENT-ASSOCIATION REASON CODE |
HE CODE THAT REPRESENTS THE UNDERLYING BASIS OF AN AGREEMENT-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
AGREEMENT-ASSOCIATION |
ARCHITECTURAL-PATTERN |
Symbol used on the System Interface decomposition to represent a pattern overlay for networks. |
T |
F |
F |
anti pattern
child patterns
name
|
anti pattern |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURAL-PATTERN |
ARCHITECTURAL-PATTERN |
Symbol used on the System Interface decomposition to represent a pattern overlay for networks. |
T |
F |
F |
anti pattern
child patterns
name
|
child patterns |
List of ARCHITECTURAL-PATTERN is child in. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURAL-PATTERN |
ARCHITECTURAL-PATTERN |
Symbol used on the System Interface decomposition to represent a pattern overlay for networks. |
T |
F |
F |
anti pattern
child patterns
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURAL-PATTERN |
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
|
ACTION-DOCUMENT IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN ACTION-DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
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
|
Analysis Process ACTION IDENTIFIER |
THE UNIQUE IDENTIFIER THAT REPRESENTS A SPECIFIC ACTION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
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
|
ARCHITECTURE IDENTIFIER |
THE IDENTIFIER OF A SPECIFIC ARCHITECTURE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
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
|
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-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
|
ARCHITECTURE-PROJECT IDENTIFIER |
THE IDENTIFIER OF AN ARCHITECTURE-PROJECT FOR A SPECIFIC ARCHITECTURE AND A SPECIFIC PROJECT. |
|
|
|
|
|
|
TBD |
F |
|
|
New |
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
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
|
Project ACTION IDENTIFIER |
THE UNIQUE IDENTIFIER THAT REPRESENTS A SPECIFIC ACTION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
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
|
Project DOCUMENT IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ARCHITECTURE-PROJECT-ANALYSIS-RESULT |
BEST-PRACTICE |
To be defined by ITA Team |
T |
F |
F |
description
name
|
description |
Members of the Domain Advisory Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BEST-PRACTICE |
BEST-PRACTICE |
To be defined by ITA Team |
T |
F |
F |
description
name
|
name |
Best practice name... |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BEST-PRACTICE |
BFA-INTEGRATION |
|
T |
F |
F |
name
touch point
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BFA-INTEGRATION |
BFA-INTEGRATION |
|
T |
F |
F |
name
touch point
|
touch point |
Touchpoint (with Picklist) Potential Analyzed |
|
|
|
Unknown |
|
|
TBD |
T |
Potential Analyzed NA Unknown |
|
|
|
BFA-INTEGRATION |
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
|
child lines of business |
The line of business that is a part of this business area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-AREA |
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
|
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 |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-AREA |
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
|
parent business reference model |
The highest level of the DOI functional decomposition within the BRM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-AREA |
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 type |
Look up table of BD types. TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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 focus areas |
Complex matrix Business Focus Area to Business Driver from associative is BUSINESS-FOCUS/BUSINESS-DRIVER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
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 |
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
|
citation initial date |
When the law passed, ruling was delivered, etc. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
citation last changed |
When the citation was last changed (law amended, ruling overturned, etc.) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
end outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
in effect |
T/F flag for whether the mandate is still in effect |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
intermediate outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
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 |
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
|
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 |
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
|
name |
Identifier for the business drivers derived from the DOI TRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
organizations |
Complex matrix Business Driver to Organization from associative is BUSINESS-DRIVER/ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
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
|
persons |
Complex matrix Business Driver to Person from associative is BUSINESS-DRIVER/PERSON |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
architectural status |
|
|
|
|
As Is |
|
|
TBD |
T |
LIST As Is To Be List As Is To Be Both NA Unkown |
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
columndefinition |
ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
comment |
Organizations comment about business driver. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
comment date |
Date comment captured |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/ORGANIZATION |
Updated by complex Matrix Business Driver to Organization. |
T |
F |
F |
architectural status
columndefinition
comment
comment date
name
rowdefinition
|
rowdefinition |
BUSINESS-DRIVER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/ORGANIZATION |
BUSINESS-DRIVER/PERSON |
Updated by complex Matrix Business Driver to Person. |
F |
F |
F |
columndefinition
comment
comment date
name
rowdefinition
|
columndefinition |
PERSON |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/PERSON |
BUSINESS-DRIVER/PERSON |
Updated by complex Matrix Business Driver to Person. |
F |
F |
F |
columndefinition
comment
comment date
name
rowdefinition
|
comment |
Persons comment about business driver. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/PERSON |
BUSINESS-DRIVER/PERSON |
Updated by complex Matrix Business Driver to Person. |
F |
F |
F |
columndefinition
comment
comment date
name
rowdefinition
|
comment date |
Date comment captured |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/PERSON |
BUSINESS-DRIVER/PERSON |
Updated by complex Matrix Business Driver to Person. |
F |
F |
F |
columndefinition
comment
comment date
name
rowdefinition
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/PERSON |
BUSINESS-DRIVER/PERSON |
Updated by complex Matrix Business Driver to Person. |
F |
F |
F |
columndefinition
comment
comment date
name
rowdefinition
|
rowdefinition |
BUSINESS-DRIVER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-DRIVER/PERSON |
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
|
architectural status |
|
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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 driver category |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
columndefinition |
BUSINESS-DRIVER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
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 |
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
|
mbt findings |
MBT-FINDINGS associated to a BFA and BD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
rowdefinition |
BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
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
|
stakeholders |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/BUSINESS-DRIVER |
BUSINESS-FOCUS/DATA-SUB-AREA |
Associative between these two objects |
F |
F |
F |
architectural status
data subject area
name
|
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 |
BUSINESS-FOCUS/DATA-SUB-AREA |
Associative between these two objects |
F |
F |
F |
architectural status
data subject area
name
|
data subject area |
The data subject area related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/DATA-SUB-AREA |
BUSINESS-FOCUS/DATA-SUB-AREA |
Associative between these two objects |
F |
F |
F |
architectural status
data subject area
name
|
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 |
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
|
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/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 area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/FUNCT-ACTIVITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/FUNCT-ACTIVITY |
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
|
function activity |
The function activity related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/FUNCT-ACTIVITY |
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
|
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 |
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
|
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 |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/FUNCT-ACTIVITY |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
architectural status |
Architectural Status List |
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
columndefinition |
INFORMATION-CLASS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
columndefinitionkey1 |
INFORMATION-CLASS Data Subject Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
BUSINESS-FOCUS/INFO-CLASS |
Associative between these two objects |
F |
F |
F |
architectural status
columndefinition
columndefinitionkey1
name
rollout phase
rowdefinition
|
rowdefinition |
BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INFO-CLASS |
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
|
columndefinition |
integrating business focus area BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INTEGRATION |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INTEGRATION |
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
|
rowdefinition |
primary business focus area BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INTEGRATION |
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
|
touch point |
Touchpoint (with Picklist) Potential Analyzed |
|
|
|
Unknown |
|
|
TBD |
T |
Potential Analyzed NA Unknown |
|
|
|
BUSINESS-FOCUS/INTEGRATION |
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
|
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/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 area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/INVESTMENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INVESTMENT |
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
|
investment project |
The investment project related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INVESTMENT |
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
|
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 |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/INVESTMENT |
BUSINESS-FOCUS/MBT-STATUS |
Look up table for MBT Status where Business Focus area is NULL. Should be set list of status choices when added to BFA become unique to that BFA. |
F |
F |
F |
business-focus-area
name
status begin date
status comment
status end date
|
business-focus-area |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/MBT-STATUS |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/MBT-STATUS |
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
|
status begin date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/MBT-STATUS |
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
|
status comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/MBT-STATUS |
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
|
status end date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/MBT-STATUS |
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
|
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/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 area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/ORGANIZATION-ROLE |
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
|
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 |
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
|
organizations |
The organization related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/ORGANIZATION-ROLE |
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
|
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/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 area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/END-OUTCOME |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/OUTCOME |
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
|
end outcome |
The end outcome related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/OUTCOME |
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
|
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 |
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
|
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 |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/OUTCOME |
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
|
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/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 area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/PERSON |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PERSON-ROLE |
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
|
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 |
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
|
persons |
The person related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PERSON-ROLE |
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
|
architectural status |
Architectural Status List |
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
columndefinition |
PRODUCT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
level business objectives |
3 seperate properties for levels 1, 2, and 3. List Of Business Objective |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
level description |
3 seperate properties for levels 1, 2, and 3. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
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 |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
rowdefinition |
BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/PRODUCT |
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
|
architectural status |
Architectural Status List |
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
columndefinition |
SERVICE-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
level business objectives |
3 seperate properties for levels 1, 2, and 3. List Of Business Objective |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
level description |
3 seperate properties for levels 1, 2, and 3. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
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 |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
rollout phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
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
|
rowdefinition |
BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SERVICE-COMP |
BUSINESS-FOCUS/SYSTEM-INV-ROLE |
Look up table for roles System Invemtories can play with in a BFA. Possible values: Pending, Retire, Target, Target-Integrate, Target-Consolidate. |
F |
F |
F |
business focus area
name
system inventories
|
business focus area |
The Business Focus Area specific to this relationship of BUSINESS-FOCUS/SYSTEM-INV |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SYSTEM-INV-ROLE |
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
|
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 |
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
|
system inventories |
The doi tracked system related to this Business Focus Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS/SYSTEM-INV-ROLE |
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
|
blueprint scope |
Blueprint Scope List |
|
|
|
Bureau/Office |
|
|
TBD |
T |
Cross-Agency Department Bureau/Office NA Unknown |
|
|
|
BUSINESS-FOCUS-AREA |
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 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 |
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
|
Data Quality Attributes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA |
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
|
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 |
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
|
main point of contact |
One of PERSON_ |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA |
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
|
managing partner |
One of ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA |
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 results score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
citizen and market score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
executive summary |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
funding strategy |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
highlevel findings summary |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
human resource score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
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) |
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
|
implementation plan |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
knowledge management score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
leadership score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
mbt criterion scoring |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
mbt findings |
MBT-FINDINGS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
process management score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
risk management plan |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
sequencing plan |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
strategic planning score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
total score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (ANALYSIS) |
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
|
accomplishments |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) |
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
|
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) |
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
|
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) |
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
|
issues/challlenges |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) |
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
|
mbt status |
Complete list of BUSINESS-FOCUS/MBT-STATUS for capturing status and comments. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) |
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
|
milestones / budgeted or required funds |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) |
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
|
overview |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BLUEPRINT STATUS) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
bprt background |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt charter |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt meeting minutes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt meeting presentations |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt mission |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt next meeting |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt organization |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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
|
bprt scope |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING) |
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 description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION) |
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 mission |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION) |
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 vision |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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-drivers |
Complex matrix to BUSINESS-DRIVER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
end outcomes |
Complex Matrix to END-OUTCOMES |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
function activities |
Complex Matrix to FUNCTION-ACTIVITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
information classes |
Complex Matrix to INFORMATION-CLASS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
lines of business |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
products |
Complex matrix to PRODUCT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
service components |
Complex Matrix to SERVICE-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
technical service categories |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (LINE OF SIGHT) |
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
|
enterprise |
Defaults to Enterprise to allow Enterprise Reporting |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
enterprise components |
Complex Matrix to SYSTEM-COMP0NENT where type is enterprise. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
investment projects |
Complex Matrix to INVESTMENT-PROJECT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
organizations |
Complex Matrix to ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
persons |
Complex Matrix to PERSON_ |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
system inventories |
Complex Matrix to SYSTEM-INVENTORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (PROTFOLIO) |
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
|
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) |
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
|
background |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
charter |
The team will be charged with the development of a charter with roles and responsibilities. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
communications plan |
Link to the BFA communication plan. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
meeting minutes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
meeting presentations |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
mission |
Mission of the Team. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
next meeting |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
organization |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
organization roles |
ORGANIZATION in the context of role they play. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
person roles |
PERSON_ in the context of the role they play. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
scope |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-FOCUS-AREA (TEAM INFORMATION) |
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
|
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) |
BUSINESS-INFORMATION-REQUIREMENT |
To be defined by ITA Team |
T |
F |
F |
BIR_description
BIR_ID
|
BIR_description |
Business Information Requirements description derived from the DOI TRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-INFORMATION-REQUIREMENT |
BUSINESS-INFORMATION-REQUIREMENT |
To be defined by ITA Team |
T |
F |
F |
BIR_description
BIR_ID
|
BIR_ID |
Unique Identifier of the Business Information Requirement (BIR) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-INFORMATION-REQUIREMENT |
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
|
child business areas |
Foreign key used to associate the various levels of the BRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
BUSINESS-REFERENCE-MODEL |
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
|
Accreditation Status |
|
|
|
|
Unknown |
|
|
TBD |
T |
ATO IATO No Authorization to Operate Unknown |
|
|
|
C-&-A-BOUNDARY |
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
|
acronym |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY |
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
|
additional names |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY |
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
|
bureau |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY |
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
|
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 |
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
|
id |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY |
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
|
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 |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY |
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
|
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 |
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
|
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 |
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
|
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 |
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
|
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 |
C-&-A-BOUNDARY (CATEGORIZATION) |
Sub-Attributes of the C-&-A-BOUNDARY object; FIPS-199 Categorization status |
T |
F |
T |
availability
confidentiality
integrity
securitycategorization
|
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) |
C-&-A-BOUNDARY (CATEGORIZATION) |
Sub-Attributes of the C-&-A-BOUNDARY object; FIPS-199 Categorization status |
T |
F |
T |
availability
confidentiality
integrity
securitycategorization
|
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) |
C-&-A-BOUNDARY (CATEGORIZATION) |
Sub-Attributes of the C-&-A-BOUNDARY object; FIPS-199 Categorization status |
T |
F |
T |
availability
confidentiality
integrity
securitycategorization
|
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) |
C-&-A-BOUNDARY (CATEGORIZATION) |
Sub-Attributes of the C-&-A-BOUNDARY object; FIPS-199 Categorization status |
T |
F |
T |
availability
confidentiality
integrity
securitycategorization
|
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) |
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
|
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) |
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
|
daa_email |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
daa_phone |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
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) |
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
|
owner_email |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
owner_phone |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
sso_email |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
sso_phone |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (CONTACTS) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
fips-199 |
C&A Attributes are defined and maintained by the Department CyberOffice and updated in DEAR Quarterly |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (DATES) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
c and a comments |
additional comments about C&A. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (other FISMA) |
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
|
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) |
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
|
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) |
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
|
provider of services |
|
|
|
|
|
|
|
TBD |
T |
VALUE External Cross-Servicing VALUE Government Wide VALUE Contractor Owned VALUE NA VALUE Unknown |
|
|
|
C-&-A-BOUNDARY (other FISMA) |
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
|
system criticality |
Defines level of system criticality. |
|
|
|
|
|
|
TBD |
T |
VALUE Protects Life VALUE Protects Property VALUE NA VALUE Unknown |
|
|
|
C-&-A-BOUNDARY (other FISMA) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
pia comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (PRIVACY) |
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
|
pia completed |
If PIA Required, when was PIA Completed? |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (PRIVACY) |
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
|
pia required |
Is this PIA required. |
|
|
|
No |
|
|
TBD |
T |
Yes No Undetermined |
|
|
|
C-&-A-BOUNDARY (PRIVACY) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
pia_online_form_omb_number_name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (PRIVACY) |
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
|
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) |
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
|
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) |
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
|
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) |
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
|
prelim_pia |
MM/DD/YYYY - All Systems required a Preliminary PIA and date completed |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
C-&-A-BOUNDARY (PRIVACY) |
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
|
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) |
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
|
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) |
CAP-IMPLICATION |
To be defined by ITA Team |
T |
F |
F |
cap_implication_description
cap_implication_id
|
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 |
To be defined by ITA Team |
T |
F |
F |
cap_implication_description
cap_implication_id
|
cap_implication_id |
Unique Identifier of the Conceptual Architecture Principles (CAP) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CAP-IMPLICATION |
CAP-RATIONALE |
To be defined by ITA Team |
T |
F |
F |
cap_rationale_description
cap_rationale_id
|
cap_rationale_description |
This field describes the series of rationales for the CAP (Conceptual Architecture Principle) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CAP-RATIONALE |
CAP-RATIONALE |
To be defined by ITA Team |
T |
F |
F |
cap_rationale_description
cap_rationale_id
|
cap_rationale_id |
Unique identified for CAP (Conceptual Architecture Principle) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CAP-RATIONALE |
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
|
CATEGORY-RELATIONSHIP COMPLETENESS CODE |
THE CODE THAT REPRESENTS THE ENTIRETY OF A CATEGORY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CATEGORY-RELATIONSHIP |
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
|
crv_author |
Common Requirements Vision Author |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
crv_background |
The background section text of the CRV document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
crv_ID |
Identifier for the common requirements vision (CRV) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
crv_introduction |
The introductory text of the CRV document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
crv_version |
Version of the common requirements vision document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
External File 1 |
Pointer to document of Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
External File 2 |
Pointer to document of Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
External File 3 |
Pointer to document of Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMMON-REQUIREMENTS-VISION |
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
|
bi-directional |
Describes if the interface communicates/shares data in both directions |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
description |
Brief Description of the interface, though usually the name is sufficient - exceptions only |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
from sub system |
The related sub-system to SYSTEM-COMP-INST-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
from sub system version |
The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
from system |
The Parent system of the sub-system/SCI interfacing from |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
from system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
from system-component-instance |
The from system-component-instance related to SYSTEM-COMP-INST-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
initiator |
Initiator List |
|
|
|
|
|
|
TBD |
T |
Source Target Neither NA Unknown |
|
|
|
COMP-INST-INTERFACE |
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
|
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 |
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
|
joint it security requirements |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
moa or mou complete |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
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 |
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
|
operational mode |
Describes the mode/how the interface operates (see values) |
|
|
|
Unknown |
|
|
TBD |
T |
Batch Interactive Manual NA Unknown |
|
|
|
COMP-INST-INTERFACE |
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
|
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 |
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
|
to sub system |
The related sub-system to SYSTEM-COMP-INST-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
to sub system version |
The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
to system |
The Parent System of the sub-system/SCI interfacing to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
to system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
to system-component-instance |
The to system-component-instance related to SYSTEM-COMP-INST-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
type |
Interface Type List |
|
|
|
Interface |
|
|
TBD |
T |
Interface Interconnected Interdependant Information Sharing NA Unknown |
|
|
|
COMP-INST-INTERFACE |
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
|
written approval for esbablishing connection |
For AVG Use Only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMP-INST-INTERFACE |
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
|
acronym |
Abbreviations for the system component. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
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_ |
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 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_ |
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 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_ |
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
|
configuration management flag |
Indicator of the Interior Configuration Management baseline status of this item. |
|
|
|
Y |
|
|
TBD |
T |
Y N Unknown |
|
|
|
COMPONENT_ |
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
|
construction comment |
Comments on the construction of the system component that are not captured elsewhere. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
data storage comment |
Comments on the data storage environment of the system component that are not captured elsewhere. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
data transformation design model |
The rule-based data transformation technologies used for the interface. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
enterprise |
Allows enterprise reporting...default to Enterprise. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
enterprise architecture component state rationale |
The rationale or reasoning behind the assigned Enterprise Architecture state of this component. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
managing partner |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
message format design model |
The nature of the internal structure of the message being transmitted between platforms. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
name |
Descriptive text that identifies the system component. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
organization roles |
The organization roles related to the SYSTEM-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
person roles |
The person roles related to the SYSTEM-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
replaces system components |
System Component(s) planned to replace this component |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
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_ |
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
|
security authentication model |
The method(s) employed by the system component to identify configured users. look up table for security authentication. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
security comment |
A text description of relevant additional security design information. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
service interface design model |
Defines the technology used to describe the programming interface to the component. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
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_ |
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
|
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_ |
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
|
transport protocol design model |
The structured message exchange communication processes (protocols) used for the interface at the network transport layer. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_ |
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
|
version |
Text that identifies the configuration management version of the System Component. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
COMPONENT_ |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/ORGANIZATION-ROLE |
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
|
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 |
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
|
organization |
The organization related to the SYSTEM-COMP/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/ORGANIZATION-ROLE |
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
|
role remarks |
Any further description of the Role (Org or Person) as noted |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/ORGANIZATION-ROLE |
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
|
system component |
The system component related to the SYSTEM-COMP/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/ORGANIZATION-ROLE |
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
|
version |
The System Component Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/ORGANIZATION-ROLE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
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
|
Name |
Role the individual plays in either managing or supporting the the subsystem |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
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
|
Person |
The individual's name who is performing the role |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
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
|
Role Remarks |
Field to further explain the nature of the role |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
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
|
System Component |
That part of a system that provides business functionality |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
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
|
Version |
Text that identifies the configuration management version of the System Component. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT_/PERSON-ROLE |
COMPONENT-ARCHITECTURE |
Look table for valules. |
T |
F |
F |
name
|
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 |
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
|
Acronym |
Abbreviations for the system component instance - typically same as the system component |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
data storage comment |
Comments on the data storage environment of the system component that are not captured elsewhere. |
|
|
|
|
|
|
TBD |
F |
Alphanumeric |
|
|
|
COMPONENT-INSTANCE |
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
|
deployment mode |
The mode of deployment for this instance (see values) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
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 |
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
|
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 |
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
|
deployment tiers |
The Tier that this SCI represents when deployed (see values) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
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 |
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
|
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 |
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
|
interface comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
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 |
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
|
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 |
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
|
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 |
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
|
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 |
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
|
processing nodes |
The processing nodes related to the SYSTEM-COMPONENT-INSTANCE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
quantity |
# of times this instance deployed |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
replaces system component instsances |
The SCIs that are Replaced by this SCI |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
sub system |
The sub system related to the SYSTEM-COMPONENT-INSTANCE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
sub system version |
The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
system |
The system related to the SYSTEM-COMPONENT-INSTANCE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
system component |
The system component related to the SYSTEM-COMPONENT-INSTANCE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
system component version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
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
|
system version |
Version of Parent System |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
COMPONENT-INSTANCE |
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
cap_author
cap_background
cap_ID
cap_introduction
cap_version
|
cap_author |
Author of the CAP Document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
cap_author
cap_background
cap_ID
cap_introduction
cap_version
|
cap_background |
The background section text of the CAP document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
cap_author
cap_background
cap_ID
cap_introduction
cap_version
|
cap_ID |
Identifier for the Conceptual Architecture Principles |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
cap_author
cap_background
cap_ID
cap_introduction
cap_version
|
cap_introduction |
The introductory text of the CAP document |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
cap_author
cap_background
cap_ID
cap_introduction
cap_version
|
cap_version |
The version of this Principle |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-ARCHITECTURE-PRINCIPLE |
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 CREATOR IDENTIFIER |
THE IDENTIFIER OF THE AGENT RESPONSIBLE FOR CREATING A SPECIFIC CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 DEVELOPMENT METHODOLOGY NAME |
THE NAME OF THE PROCEDURE USED TO DEVELOP A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 DEVELOPMENT STATUS IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS THE STATE OF DEVELOPMENT OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 DEVELOPMENT TOOL NAME |
THE NAME OF THE MECHANISM USED TO DEVELOP A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 NOTATION STYLE NAME |
THE NAME OF THE MEMORANDUM MANNER USED IN A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 PURPOSE TEXT |
THE TEXT OF THE INTENTION OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 REFINEMENT LEVEL CODE |
THE CODE THAT REPRESENTS THE LEVEL OF REFINEMENT OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 REVISION EFFECTIVE CALENDAR DATE |
THE EFFECTIVE DATE OF AN AMENDMENT TO A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 SCOPE TEXT |
THE TEXT OF THE BOUNDARIES OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 STATUS EFFECTIVE CALENDAR DATE |
THE EFFECTIVE DATE OF THE STATE OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 TENSE CODE |
THE CODE THAT REPRESENTS THE TIME DISTINCTION OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 TENSE EFFECTIVE CALENDAR DATE |
THE EFFECTIVE DATE OF THE TIME DISTINCTION OF A CONCEPTUAL-DATA-MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL |
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 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 |
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 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 |
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 SCOPE TEXT |
THE TEXT OF THE BOUNDARIES OF A CONCEPTUAL-DATA-MODEL-VIEW. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL-VIEW |
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-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 |
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-ASSOCIATION DEPENDENCY DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES THE DEPENDENCY OF A CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION |
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
|
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 |
CRV-STRATEGY |
To be defined by ITA Team |
T |
F |
F |
strategy_description
strategy_ID
|
strategy_description |
The text description for the strategies within the PRM and strategic plan |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CRV-STRATEGY |
CRV-STRATEGY |
To be defined by ITA Team |
T |
F |
F |
strategy_description
strategy_ID
|
strategy_ID |
Unique identifier for the strategic plan strategy concept |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
CRV-STRATEGY |
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
|
attribute composition type name |
Describes the structural makeup of a data attribute. Composition Type List |
|
|
|
Unknown |
|
|
TBD |
T |
Atomic Composite NA Unknown |
|
|
|
DATA-ATTRIBUTE |
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
|
authoritative source |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
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 |
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
|
derived |
Is the attribute derived if so mark as T. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
domain description |
Text field for temporary storage of Domain Values from ERWin |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
domain values |
List of DOMAIN-VALUE for future use in storing domain information. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
entity name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
full name |
Full Name fro ERWin if exceeded 80 chars. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
indian trus data |
yes/No/NA List |
|
|
|
Unknown |
|
|
TBD |
T |
Yes No NA Unknown |
|
|
|
DATA-ATTRIBUTE |
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
|
model |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
notes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
precision |
Represents Decimal Point Precision. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
reference source |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
security classification code |
Will be pick list when values are determined. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
units of measure |
will be pick list when values are determined. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
xml tag name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE |
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
|
ALIAS IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN ALIAS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-ALIAS |
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-ALIAS CREATION CALENDAR DATE |
THE ORIGINATION DATE OF A DATA-ATTRIBUTE-ALIAS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-ALIAS |
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-ASSOCIATION TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-ATTRIBUTE-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-ASSOCIATION |
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 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 |
DATA-ATTRIBUTE-CHAIN-MEMBER-ATTRIBUTE |
To be defined by IDA Team |
T |
F |
F |
DATA-ATTRIBUTE-CHAIN DATA ATTRIBUTE POSITION IDENTIFIER
|
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 |
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-DATA-TYPE NAME |
THE NAME OF THE DATA-ATTRIBUTE-DATA-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-DATA-TYPE |
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-DATA-TYPE TARGET ENVIRONMENT NAME |
THE NAME OF THE SETTING FOR A SPECIFIC DATA-ATTRIBUTE-DATA-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-DATA-TYPE |
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-DERIVED ALGORITHM TEXT |
THE TEXT OF THE DERIVATION FORMULA OF A DATA-ATTRIBUTE-DERIVED. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-DERIVED |
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
|
User Presentation View INFORMATION-ASSET IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD |
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
|
USER-PRESENTATION-VIEW-FIELD IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A USER-PRESENTATION-VIEW-FIELD. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD |
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 Class INFORMATION-ASSET IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-CLASS |
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-CLASS CATEGORY NAME |
THE NAME OF THE CLASSIFICATION OF A DATA-CLASS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-CLASS |
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-CLASS TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-CLASS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-CLASS |
DATA-DICTIONARY |
A LISTING OF DATA-ELEMENTS AND THEIR CHARACTERISTICS. |
T |
F |
F |
DATA-DICTIONARY TYPE CODE
|
DATA-DICTIONARY TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-DICTIONARY. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY |
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 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 |
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 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 |
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 DEFINITION TEXT |
THE TEXT THAT STATES THE PRECISE MEANING OF A SPECIFIC DATA-DICTIONARY-ELEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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 FORMAT DESCRIPTION TEXT |
THE TEXT THAT CHARACTERIZES THE PHYSICAL FORM OF A SPECIFIC DATA-DICTIONARY-ELEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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 IDENTIFIER |
THE IDENTIFIER OF A DATA-DICTIONARY-ELEMENT FOR A SPECIFIC DATA-DICTIONARY. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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 NAME |
THE NAME OF A SPECIFIC DATA-DICTIONARY-ELEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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 SOURCE NAME |
THE NAME OF THE ORIGIN OF A SPECIFIC DATA-DICTIONARY-ELEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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 USAGE DESCRIPTION TEXT |
THE TEXT THAT SUMMARIZES THE WAY A SPECIFIC DATA-DICTIONARY-ELEMENT IS INTENDED TO BE IMPLEMENTED. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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
|
INFORMATION-ELEMENT IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A SPECIFIC INFORMATION-ELEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT |
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-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 |
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-ELEMENT-ASSOCIATION TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-DICTIONARY-ELEMENT-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-ELEMENT-ASSOCIATION |
DATA-DICTIONARY-SPECIFICATION |
A DOCUMENT THAT CONTAINS METADATA FOR INFORMATION CONCEPTS. |
T |
F |
F |
DOCUMENT IDENTIFIER
|
DOCUMENT IDENTIFIER |
This is supporting data structures for Reporting |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DICTIONARY-SPECIFICATION |
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 CONSTRUCTION TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF CONSTRUCT OF A DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN |
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 FORMAT CODE |
THE CODE THAT REPRESENTS THE JUSTIFICATION FORM OF A DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN |
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 MAXIMUM CHARACTER QUANTITY |
THE MAXIMUM QUANTITY OF CHARACTERS OF A DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN |
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 TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN |
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 VALUE TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF VALUATION OF A DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN |
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-BASE DATA TYPE NAME |
THE NAME OF A KIND OF DATA IN A DATA-DOMAIN-BASE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-BASE |
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 SOURCE LIST TEXT |
THE TEXT OF THE ORIGIN OF A LISTING IN A DATA-DOMAIN-LIST. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-LIST |
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 DEFINITION TEXT |
THE TEXT THAT REPRESENTS THE MEANING OF A SPECIFIC DATA-DOMAIN-LIST-VALUE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-LIST-VALUE |
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 IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A DATA-DOMAIN-LIST-VALUE FOR A SPECIFIC DATA-DOMAIN-LIST. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-LIST-VALUE |
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 SOURCE NAME |
THE NAME OF THE ORIGIN OF A SPECIFIC DATA-DOMAIN-LIST-VALUE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-LIST-VALUE |
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-LIST-VALUE-ASSOCIATION ALGORITHM TEXT |
THE TEXT CHARACTERIZES THE MATHEMATICAL RELATIONSHIP THAT THE ORDINATE DATA-DOMAIN-LIST-VALUE HAS IN RELATION TO THE SUBORDINATE DATA-DOMAIN-LIST-VALUE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-LIST-VALUE-ASSOCIATION |
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-RANGE HIGH VALUE TEXT |
THE TEXT OF THE UPPER LIMIT OF A DATA-DOMAIN-RANGE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-RANGE |
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-RANGE INCREMENT MEASUREMENT QUANTITY |
THE QUANTITY OF THE MEASUREMENT STEP FROM ONE VALUE TO ANOTHER IN A DATA-DOMAIN-RANGE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-RANGE |
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-RANGE LOW VALUE TEXT |
THE TEXT OF THE LOWER LIMIT OF A DATA-DOMAIN-RANGE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-RANGE |
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-STRUCTURE-RULE-ASSOCIATION ALGORITHM TEXT |
THE TEXT OF THE DERIVATION FORMULA OF A DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION |
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-STRUCTURE-RULE-ASSOCIATION NAME |
THE NAME OF A DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION |
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-DOMAIN-TYPED NAME |
THE NAME OF A DATA-DOMAIN-TYPED. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-DOMAIN-TYPED |
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
|
entity mappable indicator |
Yes/No/NA List. Yes or no if an entity is recommended for mapping to other enterprise architecture compoennts. |
|
|
|
|
|
|
TBD |
T |
Yes No NA Unknown |
|
|
|
DATA-ENTITY |
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
|
full name |
Full name from ERWin if exceeds 80 chrs. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
function activities |
FUNCTION-ACTIVITY Only update via matrix or on import. DRM to BRM mapping. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
information classes |
INFORMATION-CLASS Only updated on import. DRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
sub systems |
SUB-SYSTEM DRM to System mapping |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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
|
xml tag name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY |
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-ALTERNATE-KEY-GROUP IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN ALTERNATIVE IDENTIFYING FUNCTION OF A DATA-ENTITY-DATA-ATTRIBUTE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-ALTERNATE-KEY-GROUP |
DATA-ENTITY-ALTERNATE-KEY-GROUP |
To be defined by IDA Team |
T |
F |
F |
DATA-ENTITY-ALTERNATE-KEY-GROUP IDENTIFIER
DATA-ENTITY-DATA-ATTRIBUTE ALTERNATE KEY IDENTIFIER
|
DATA-ENTITY-DATA-ATTRIBUTE ALTERNATE KEY IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN ALTERNATIVE IDENTIFYING FUNCTION OF A DATA-ENTITY-DATA-ATTRIBUTE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-ALTERNATE-KEY-GROUP |
DATA-ENTITY-KEY-GROUP |
To be defined by IDA Team |
T |
F |
F |
DATA-ENTITY-KEY-GROUP Identifier
|
DATA-ENTITY-KEY-GROUP Identifier |
Unique identifier for the Data Entity Group |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-KEY-GROUP |
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 CARDINALITY TYPE CODE |
THE CODE THAT REPRESENTS THE KIND OF CARDINALITY OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 CATEGORY CODE |
THE CODE THAT REPRESENTS A CLASSIFICATION OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 CHILD DELETE RULE TEXT |
THE TEXT OF THE RULE FOR DELETION OF DEPENDENT ENTITIES OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 CHILD INSERT RULE TEXT |
THE TEXT OF THE RULE FOR INSERTION OF DATA TO DEPENDENT ENTITIES OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 CHILD UPDATE RULE TEXT |
THE TEXT OF THE RULE FOR UPDATING DEPENDENT ENTITY DATA OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 DEPENDENCY CODE |
THE CODE THAT REPRESENTS THE DEPENDENCY NATURE OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 GLOBALLY-UNIQUE PHYSICAL NAME |
THE NAME OF A SPECIFIC DATA-ENTITY-RELATIONSHIP THAT IS UNIQUE AMONG ALL RELATIONSHIPS FOR AN IMPLEMENTATION OF A SPECIFIC DATA MODEL. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 IDENTIFIER |
THE IDENTIFIER OF A DATA-ENTITY-RELATIONSHIP FOR A SPECIFIC ORDINATE ENTITY AND A SPECIFIC SUBORDINATE ENTITY. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 NAME |
THE NAME DEPICTING THE WAY IN WHICH THE ORDINATE DATA-ENTITY IS ASSOCIATED WITH THE SUBORDINATE DATA-ENTITY. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 NULL RULE TEXT |
THE TEXT OF THE RULE FOR NULL VALUES IN A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 PARENT DELETE RULE TEXT |
THE TEXT OF THE RULE FOR DELETION OF DATA FROM INDEPENDENT ENTITIES OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 PARENT INSERT RULE TEXT |
THE TEXT OF THE RULE FOR INSERTION OF DATA TO INDEPENDENT ENTITIES OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 PARENT UPDATE RULE TEXT |
THE TEXT OF THE RULE FOR UPDATING THE DATA OF AN INDEPENDENT ENTITY IN A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
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 VERSION IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A SPECIFIC RENDITION OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP |
DATA-ENTITY-RELATIONSHIP-ROLE-NAME |
To be defined by IDA Team |
T |
F |
F |
DATA-ENTITY-RELATIONSHIP ROLE NAME IDENTIFIER
|
DATA-ENTITY-RELATIONSHIP ROLE NAME IDENTIFIER |
THE NAME OF THE FUNCTION OF A DATA-ENTITY-RELATIONSHIP. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-ENTITY-RELATIONSHIP-ROLE-NAME |
DATA-FLOW |
To be defined by IDA Team |
T |
F |
F |
Delete
information classes
name
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-FLOW |
DATA-FLOW |
To be defined by IDA Team |
T |
F |
F |
Delete
information classes
name
|
information classes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-FLOW |
DATA-FLOW |
To be defined by IDA Team |
T |
F |
F |
Delete
information classes
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-FLOW |
DATA-FORMAT |
Look up table for system interface capability data formats. |
T |
F |
F |
Name
|
Name |
What is the nature of the internal structure of the message being transmitted between platforms? Choose all message formats that apply to this interface.. Data Format is the structure of a file. There are hundreds of formats, and every application has many different variations (database, word processing, graphics, executable program, etc.). Each format defines its own layout of the data. The file format for text is the simplest XML – (eXtensible Markup Language) XML has emerged as the standard format for web data, and is beginning to be used as a common data format at all levels of the architecture. Many specialized vocabularies of XML are being developed to support specific Government and Industry functions. http://www.w3.org/XML/ |
|
|
|
|
|
|
TBD |
F |
Component Proprietary COTS or GOTS Proprietary HTML XML GIF TIFF JPEG MPEG PDF RTF MIME EDI Messages Other Unknown |
|
|
|
DATA-FORMAT |
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 quality comments |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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 quality description |
Property Repeate for 25 Sections: Inventory Privacy Sys Arch Hierarchy TRM Link DOI TRM Spec Additions SRM Link Processing Nodes Processing Nodes Linkage Location Node Location Linkage System Interface Diagrams Load Bureau Systems PRM Linkage BRM Linkage BRM Link Attrib Enclave/Member Systems DRM Linkage DRM Link Attrib Attribute Bureau Systems Organization Breakdown Person Roles DOI BRM Extension* Security (C&A Load) Invest Linkage |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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 quality status |
Property Repeate for 25 Sections: Inventory Privacy Sys Arch Hierarchy TRM Link DOI TRM Spec Additions SRM Link Processing Nodes Processing Nodes Linkage Location Node Location Linkage System Interface Diagrams Load Bureau Systems PRM Linkage BRM Linkage BRM Link Attrib Enclave/Member Systems DRM Linkage DRM Link Attrib Attribute Bureau Systems Organization Breakdown Person Roles DOI BRM Extension* Security (C&A Load) Invest Linkage |
|
|
|
Unkonwn |
|
|
TBD |
T |
Not Prioroty Not Collected Not Populated Populated Validated NA Unknown |
|
|
|
DATA-QUALITY |
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
|
integrating rating score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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
|
inventory rating score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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
|
modeling rating score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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
|
next steps |
Property Repeate for 25 Sections: Inventory Privacy Sys Arch Hierarchy TRM Link DOI TRM Spec Additions SRM Link Processing Nodes Processing Nodes Linkage Location Node Location Linkage System Interface Diagrams Load Bureau Systems PRM Linkage BRM Linkage BRM Link Attrib Enclave/Member Systems DRM Linkage DRM Link Attrib Attribute Bureau Systems Organization Breakdown Person Roles DOI BRM Extension* Security (C&A Load) Invest Linkage |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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
|
priority |
Property Repeate for 25 Sections: Inventory Privacy Sys Arch Hierarchy TRM Link DOI TRM Spec Additions SRM Link Processing Nodes Processing Nodes Linkage Location Node Location Linkage System Interface Diagrams Load Bureau Systems PRM Linkage BRM Linkage BRM Link Attrib Enclave/Member Systems DRM Linkage DRM Link Attrib Attribute Bureau Systems Organization Breakdown Person Roles DOI BRM Extension* Security (C&A Load) Invest Linkage |
|
|
|
High |
|
|
TBD |
T |
High Medium Low NA Unknown |
|
|
|
DATA-QUALITY |
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
|
ref model mapping rating score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-QUALITY |
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
|
creation date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
creator |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
currentness |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
Entities |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
owning organization |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
purpose |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
status |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
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
|
subject area diagram |
Link to their subject area diagram. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SET |
DATA-STORE |
A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. |
T |
F |
F |
information classes
name
processing nodes
system component instances
technical service specifications
|
information classes |
List of INFORMATION-CLASS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE |
DATA-STORE |
A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. |
T |
F |
F |
information classes
name
processing nodes
system component instances
technical service specifications
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE |
DATA-STORE |
A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. |
T |
F |
F |
information classes
name
processing nodes
system component instances
technical service specifications
|
processing nodes |
PROCESSING-NODE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE |
DATA-STORE |
A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. |
T |
F |
F |
information classes
name
processing nodes
system component instances
technical service specifications
|
system component instances |
SYSTEM-COMPONENT-INSTANCE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE |
DATA-STORE |
A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION. |
T |
F |
F |
information classes
name
processing nodes
system component instances
technical service specifications
|
technical service specifications |
TECHNICAL-SERVICE-SPEC |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE |
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 store |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
name |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
sub system |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
sub system version |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
system |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
system component instance |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
system component instance version |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
system version |
To be defined by IDA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-STORE/SYSTEM-COMP-INST |
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
|
information classes |
List of INFORMATION-CLASS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SUBJECT-AREA |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DATA-SUBJECT-AREA |
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
|
status |
Data Status List |
|
|
|
Pending |
|
|
TBD |
T |
Pending Draft Final NA Unknown |
|
|
|
DATA-SUBJECT-AREA |
DEPLOYMENT-TIER |
None |
T |
F |
F |
Name
|
Name |
List of deployment tiers. What system component processing tiers does this deployment instance support for the related system component? |
|
|
|
|
|
|
TBD |
T |
Business Logic Custom Data Access None Other Presentation - Server-based Presentation - Distributed Presentation - Monolithic Unknown |
|
|
|
DEPLOYMENT-TIER |
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
|
CAVEATED-SECURITY-CLASSIFICATION IDENTIFIER |
THE IDENTIFIER OF A CAVEATED-SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 ABBREVIATED NAME |
THE SHORTENED FORM OF THE NAME OF A SPECIFIC DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 APPROVAL CALENDAR DATE |
THE CALENDAR DATE THAT A DOCUMENT IS APPROVED. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 ARCHITECTURE PRODUCT TYPE CODE |
THE CODE THAT REPRESENTS THE KIND OF ARCHITECTURAL STRUCTURED SPECIFICATION DESCRIBED BY THE DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 CATEGORY CODE |
THE CODE THAT REPRESENTS A CLASSIFICATION OF A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 CREATION CALENDAR DATE |
THE CALENDAR DATE ON WHICH A DOCUMENT IS CREATED. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 NAME |
THE NAME OF A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 NOTATION TEXT |
THE TEXT THAT SPECIFIES THE SYNTACTICAL LANGUAGE USED IN THE DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 ORIGINATOR NAME |
THE NAME FOR THE ORIGINATING ENTITY FOR A SPECIFIC DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 PUBLICATION CALENDAR DATE |
THE CALENDAR DATE ON WHICH A SPECIFIC DOCUMENT WAS MADE PUBLICLY AVAILABLE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 REMARK TEXT |
THE TEXT OF COMMENTS ASSOCIATED WITH A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 ROUTING CODE |
THE CODE THAT DENOTES THE DISTRIBUTION CATEGORY SPECIFIED FOR A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 TEMPORAL SCOPE CODE |
THE CODE THAT REPRESENTS THE ACTUAL OR PLANNED TIME FRAME ADDRESSED BY A SPECIFIC DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 UNIVERSAL RESOURCE LOCATOR TEXT |
THE TEXT THAT PROVIDES A WORLD-WIDE WEB UNIVERSAL RESOURCE LOCATOR (URL) ACCESS TO A SPECIFIC DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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 VERSION IDENTIFIER |
THE IDENTIFIER FOR A SPECIFIC RELEASE OF A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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
|
SECURITY-CLASSIFICATION CODE |
THE CODE THAT REPRESENTS A SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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
|
Time Frame PERIOD IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A PERIOD. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT |
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-ASSOCIATION BEGIN CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME A DOCUMENT-ASSOCIATION STARTS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-ASSOCIATION |
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-ASSOCIATION END CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME A DOCUMENT-ASSOCIATION CONCLUDES. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-ASSOCIATION |
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-ASSOCIATION IDENTIFIER |
THE IDENTIFIER OF AN INSTANCE OF DOCUMENT-ASSOCIATION FOR A SPECIFIC ORDINATE DOCUMENT AND A SPECIFIC SUBORDINATE DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-ASSOCIATION |
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-ASSOCIATION REASON CODE |
THE CODE THAT REPRESENTS THE UNDERLYING BASIS OF A DOCUMENT-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-ASSOCIATION |
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
|
Creating Office |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Custodian |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Cutoff Date |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Disposition |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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-instance-name |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
New |
|
DOCUMENT-INSTANCE |
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
|
Electronic Location |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
File Scheme |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
GRS |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
HTML Link |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
New |
|
DOCUMENT-INSTANCE |
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
|
Media Type |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Paper Location |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Record Indicator |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Status |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Vital |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-INSTANCE |
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
|
Author |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Category |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Document Status |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
document-type-name |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
New |
|
DOCUMENT-TYPE |
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
|
File Name |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
ID |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Keywords |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Links |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Report or Binder |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Revision Date |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Synopsis |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Type |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
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
|
Version nbr |
This attribute is utilized internal by System Architect to aid Report generation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOCUMENT-TYPE |
DOMAIN-ARCH-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
dap implications
dap rationales
name
service components
technology domain team
|
dap implications |
The domain architecture implications associated to the SRM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-ARCH-PRINCIPLE |
DOMAIN-ARCH-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
dap implications
dap rationales
name
service components
technology domain team
|
dap rationales |
Domain Architecture rationales or describe the business value to support the principles identified within the DOI TRM Domain chapters |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-ARCH-PRINCIPLE |
DOMAIN-ARCH-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
dap implications
dap rationales
name
service components
technology domain team
|
name |
Name of the domain architecture principle associated between the DAP and SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-ARCH-PRINCIPLE |
DOMAIN-ARCH-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
dap implications
dap rationales
name
service components
technology domain team
|
service components |
Name of the service component associated between the DAP and SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-ARCH-PRINCIPLE |
DOMAIN-ARCH-PRINCIPLE |
To be defined by ITA Team |
T |
F |
F |
dap implications
dap rationales
name
service components
technology domain team
|
technology domain team |
The name of the team that generates the principles for the domain |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-ARCH-PRINCIPLE |
DOMAIN-VALUE |
Meant to represent the list of valid values for a given attribute. |
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
DOMAIN-VALUE |
ENTITY/ORGANIZATION-ROLE |
Associative between these two objects |
T |
F |
F |
description
entity
model
name
organizations
|
description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/ORGANIZATION-ROLE |
ENTITY/ORGANIZATION-ROLE |
Associative between these two objects |
T |
F |
F |
description
entity
model
name
organizations
|
entity |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/ORGANIZATION-ROLE |
ENTITY/ORGANIZATION-ROLE |
Associative between these two objects |
T |
F |
F |
description
entity
model
name
organizations
|
model |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/ORGANIZATION-ROLE |
ENTITY/ORGANIZATION-ROLE |
Associative between these two objects |
T |
F |
F |
description
entity
model
name
organizations
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/ORGANIZATION-ROLE |
ENTITY/ORGANIZATION-ROLE |
Associative between these two objects |
T |
F |
F |
description
entity
model
name
organizations
|
organizations |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/ORGANIZATION-ROLE |
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
|
columndefinition |
The following entity ENTITY/SUB-SYSTEM represents the row and column respectively of the matrix in support the reporting functions. In the User Interface the user will see a label ENTITY/SUB-SYSTEM and not the attributes listed in the schema. SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
columndefinitionkey1 |
SUB-SYSTEM Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
columndefinitionkey2 |
SUB-SYSTEM System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
columndefinitionkey3 |
SUB-SYSTEM System |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
crud info |
Create Retrieve Update and Delete moniker that describes the nature of the transactions performed by the function on data or information |
|
|
|
Read-Only |
|
|
TBD |
T |
Create Modify Read-Only All TBD |
|
|
|
ENTITY/SUB-SYSTEM |
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
|
data store form of sharing |
Form of Sharing - indicates the form of data sharing the application utilizes; Private, Duplicated, Shared, Enterprise. Value Descriptions Private means that the application exclusively controls that particular data and it is neither read nor updated by other analyzed applications. Duplicated means that the data is copied, either dynamically or periodically, between multiple applications for the purposes of rudimentary data sharing; this category does not include data replication for distributed databases, failure, or disaster recovery purposes. Shared data means that multiple applications have shared access to the data in a single data store, however there may still be multiple private, duplicated, and shared instances of the data. Enterprise data means a single source of the data accessed by all applications using that data; the data is not duplicated, nor are there other private or shared instances of the same data. |
|
|
|
Private |
|
|
TBD |
T |
Duplicate Enterprise Private Shared TBD |
|
|
|
ENTITY/SUB-SYSTEM |
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
|
description |
Free text field to describe the relationship between the ENTITY/SYSTEM-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
intersection? |
The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
name |
Identifying name for the relationship of the ENTITY/SYSTEM-COMPONENT work activity to the intermediate outcomes. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
rowdefinition |
The following entity ENTITY/SUB-SYSTEM represents the row and column respectively of the matrix in support the reporting functions. In the User Interface the user will see a label ENTITY/SUB-SYSTEM and not the attributes listed in the schema. ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
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
|
rowdefinitionkey1 |
ENTITY Model |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENTITY/SUB-SYSTEM |
ENVIRONMENTAL-TREND |
None |
T |
F |
F |
env_trend_description
env_trend_ID
|
env_trend_description |
This field describes the environmental trends identified as a part of the Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENVIRONMENTAL-TREND |
ENVIRONMENTAL-TREND |
None |
T |
F |
F |
env_trend_description
env_trend_ID
|
env_trend_ID |
This is the unique identifier for the environmental trend identified as a part of the Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ENVIRONMENTAL-TREND |
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
|
exhibit53-name |
The name of the Exhibit 53 if one exists. If this is the Investment Title in an Exhibit 53, then the data already exists in the INVESTMENT PROJECT) entity. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
EXHIBIT-53 |
FOCUS |
None |
T |
F |
F |
focus_idenifier
|
focus_idenifier |
Is the unique identifier for the focus that is associated to the environmental trends and strategies with the Common Requirements Vision |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FOCUS |
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
|
abc work activities |
The ABC work activities comprise the foundation for the functional definition of the BRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
child function activities |
Child function activities are those functions that are subordinate to the parent function activities and describe lower level functional activities |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
full name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
functin activity type |
Function Activity Type List Depending on the value selection will update the depiction of the symbol on the diagram. |
|
|
|
Unknown |
|
|
TBD |
T |
Sub Function Function Process Activity Task NA Unknown |
|
|
|
FUNCTION-ACTIVITY |
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
|
leaf node flag |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
level |
1 through 10 list Subfunction 3, Function 4, Process 5, Activity 6, Task 7-10 |
|
|
|
|
|
|
TBD |
T |
1 2 3 4 5 6 7 8 9 10 |
|
|
|
FUNCTION-ACTIVITY |
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
|
modes of delivery |
FUNCTION-ACTIVITY Where mode of delivery flag = true. Should only be filled out if it is a Service to Citizen. This is a matrix property and should only be filled out on import or through matrix. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
name |
Activity Based Costing Work Activity Name: The name of the Activity-Based Costing Item that describes an activity that can have work tied to it to measure effort against. Short name to describe the activity usually containing 3-10 words. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
organizations |
Foreign key supporting relationship of the BRM to the org. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
parent function activity |
The highest level of the DOI functional decomposition within the BRM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
secondary parent function activities |
if alternate parents exist. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
service components |
The service components are those generic capabilities that are used to support the implementation of the business function |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
sub function flag |
Differentiator attribute that distinguishes FEA from DOI introduced functions |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
sub systems |
Defines the association to the IT sub systems that support the business function. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY |
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
|
availability impact description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
availability impact recommended level |
|
|
|
|
|
|
|
TBD |
T |
VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown |
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
availability impact special factors |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
avaliability impact rationale |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
confidentiality impact description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
confidentiality impact rationale |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
confidentiality impact recommended level |
|
|
|
|
|
|
|
TBD |
T |
VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown |
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
confidentiality impact special factors |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
integrity impact description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
integrity impact rationale |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
integrity impact recommended level |
|
|
|
|
|
|
|
TBD |
T |
VALUE Low VALUE Medium VALUE Moderate VALUE High VALUE NatlSecurity VALUE NA VALUE Unknown |
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
integrity impact special factors |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY (SECURITY) |
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
|
columndefinition |
ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
columndefinitionkey1 |
ENTITY Model |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
crud info |
CRUD property that is for capturing the Target CRUD for function to entity interaction. |
|
|
|
|
|
|
TBD |
T |
VALUE All VALUE Create VALUE Read VALUE Update VALUE TBD VALUE Unknown |
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
rollout/phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
rowdefinition |
FUNCTION-ACTIVITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/ENTITY |
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
|
columndefinitionkey |
Primary key for creation of the intersection matrix that bridges the FUNCTION-ACTIVITY/SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
columndefinitionkey1 |
Primary key for creation of the intersection matrix that bridges the FUNCTION-ACTIVITY/SUB-SYSTEM . |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
data qualification |
Qualifying attribute describing how the FUNCTION-ACTIVITY/SUB-SYSTEM interacts with the information |
|
|
|
|
|
|
TBD |
T |
Read Only Source Data Modification NA Unknown |
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
description |
Free text field to describe the relationship between the FUNCTION-ACTIVITY/SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
intersection? |
The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
name |
Identifying name for the relationship of the FUNCTION-ACTIVITY/SUB-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
process automation qualification |
Attribute describing how well or complete the automated implementation of the subsystem is in supporting the business function Process Automation is either: Minimal - Some automation, but primarily not integrated function or activity Partial - Mostly Automated, but requires intervention to complete Full - Fully automated, though will/may require review/administration |
|
|
|
|
|
|
Intersection |
T |
Minimal Partial Full NA Unknown |
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
rollout/phase |
|
|
|
|
|
|
|
TBD |
T |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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
|
rowdefinition |
The following entity FUNCTION-ACTIVITY/SUB-SYSTEM represents the row and column respectively of the matrix in support the reporting functions. In the User Interface the user will see a label FUNCTION-ACTIVITY/SUB-SYSTEM and not the attributes listed in the schema. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
FUNCTION-ACTIVITY/SUB-SYSTEM |
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 |
The generic measurement indicator related to the GENERIC-INDICATOR/INTR-MEASURE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-INDICATOR/MEASURE |
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
|
intermediate outcome measure |
The intermediate outcome measure related to the GENERIC-INDICATOR/INTR-MEASURE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-INDICATOR/MEASURE |
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
|
measurement area |
The measurement area related to the GENERIC-INDICATOR/INTR-MEASURE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-INDICATOR/MEASURE |
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
|
measurement category |
The measurement category related to the GENERIC-INDICATOR/INTR-MEASURE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-INDICATOR/MEASURE |
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
|
name |
Name of the GENERIC-INDICATOR/INTR-MEASURE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-INDICATOR/MEASURE |
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
|
end outcome measures |
The end outcome measures related to the GENERIC-MEASUREMENT-INDICATOR |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-MEASUREMENT-INDICATOR |
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
|
intermediate outcome measures |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-MEASUREMENT-INDICATOR |
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
|
measurement area |
The measurement area related to the GENERIC-MEASUREMENT-INDICATOR |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-MEASUREMENT-INDICATOR |
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
|
measurement category |
The measurement category related to the GENERIC-MEASUREMENT-INDICATOR |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-MEASUREMENT-INDICATOR |
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
|
name |
Name of the GENERIC-MEASUREMENT-INDICATOR |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GENERIC-MEASUREMENT-INDICATOR |
GOAL |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GOAL |
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 AUTHORITY TEXT |
THE TEXT OF THE AUTHORITY FOR PROMULGATING GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 BEGIN CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME ON WHICH GUIDANCE STARTS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 CATEGORY CODE |
THE CODE THAT DENOTES A SPECIFIC CLASS OF GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 END CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME ON WHICH GUIDANCE CONCLUDES. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 FUNCTIONAL TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF GUIDANCE BY FUNCTIONAL AREA. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN OCCURRENCE OF GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 NAME |
THE NAME OF A GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 SUBJECT TEXT |
THE TEXT THAT DESCRIBES THE TOPIC OF A GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 SYNOPSIS TEXT |
THE TEXT THAT PROVIDES A CONDENSED DESCRIPTION OF AN OCCURRENCE OF GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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 TEXT |
THE TEXT OF AN OCCURRENCE OF GUIDANCE IN ITS ENTIRETY. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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
|
POINT-OF-CONTACT IDENTIFIER |
(63573/1) (C) THE IDENTIFIER OF A SPECIFIC POINT-OF-CONTACT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE |
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
|
GUIDANCE-ASSOCIATION BEGIN CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME A GUIDANCE-ASSOCIATION STARTS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE-ASSOCIATION |
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
|
GUIDANCE-ASSOCIATION END CALENDAR DATE-TIME |
THE CALENDAR DATE-TIME A GUIDANCE-ASSOCIATION CONCLUDES. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE-ASSOCIATION |
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
|
GUIDANCE-ASSOCIATION IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A SPECIFIC GUIDANCE-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE-ASSOCIATION |
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
|
GUIDANCE-ASSOCIATION ROLE CODE |
THE CODE THAT REPRESENTS THE RATIONALE THAT ASSOCIATES ONE OCCURRENCE OF GUIDANCE TO ANOTHER OCCURRENCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
GUIDANCE-ASSOCIATION |
ICOM-ARROW |
None |
T |
F |
F |
business drivers
data entities
delete
name
|
business drivers |
list of BUSINESS-DRIVER definitions should only be updated for Controls or Mechanisms. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ICOM-ARROW |
ICOM-ARROW |
None |
T |
F |
F |
business drivers
data entities
delete
name
|
data entities |
List of ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ICOM-ARROW |
ICOM-ARROW |
None |
T |
F |
F |
business drivers
data entities
delete
name
|
delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ICOM-ARROW |
ICOM-ARROW |
None |
T |
F |
F |
business drivers
data entities
delete
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ICOM-ARROW |
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 ACRONYM TEXT |
THE TEXT THAT DESCRIBES THE INITIAL CHARACTERS OF THE NAME OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 COMMENT TEXT |
THE TEXT OF COMMENTARY ON AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 DEFINITION TEXT |
THE TEXT THAT DEFINES AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 NAME |
THE NAME OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 REUSABLE CODE |
THE CODE THAT REPRESENTS THE REUSABILITY OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 SHORT NAME |
THE SHORTENED NAME OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 STANDARDIZATION AUTHORITY CODE |
THE CODE THAT REPRESENTS THE APPROVAL AUTHORITY FOR THE CONFORMITY TO ESTABLISHED CRITERIA OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 STANDARDIZATION STATUS CALENDAR DATE |
THE CALENDAR DATE OF THE CONFORMITY TO ESTABLISHED CRITERIA OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 STANDARDIZATION STATUS CODE |
THE CODE THAT REPRESENTS THE CONFORMITY TO ESTABLISHED CRITERIA OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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 VERSION IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A SPECIFIC RENDITION OF AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET |
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-AGREEMENT IDENTIFIER |
THE IDENTIFIER OF AN INFORMATION-ASSET-AGREEMENT FOR A SPECIFIC INFORMATION-ASSET AND A SPECIFIC AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-AGREEMENT |
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-AGREEMENT ROLE CODE |
THE CODE THAT REPRESENTS THE SPECIFIC WAY IN WHICH AN INFORMATION-ASSET IS RELATED TO AN AGREEMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-AGREEMENT |
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-DOCUMENT IDENTIFIER |
THE IDENTIFIER OF A INFORMATION-ASSET-DOCUMENT FOR A SPECIFIC INFORMATION-ASSET AND SPECIFIC DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-DOCUMENT |
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-DOCUMENT ROLE CODE |
THE CODE THAT REPRESENTS THE SPECIFIC WAY IN WHICH AN INFORMATION-ASSET USES A DOCUMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-DOCUMENT |
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-GUIDANCE DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES AN INFORMATION-ASSET-GUIDANCE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-GUIDANCE |
INFORMATION-ASSET-RELATION |
THE ASSOCIATION BETWEEN INFORMATION-ASSETS. |
T |
F |
F |
INFORMATION-ASSET-RELATION REASON TEXT
INFORMATION-ASSET-RELATION ROLE CODE
INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE
INFORMATION-ASSET-RELATION TYPE CODE
|
INFORMATION-ASSET-RELATION REASON TEXT |
THE TEXT OF THE REASON FOR AN INFORMATION-ASSET-RELATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-RELATION |
INFORMATION-ASSET-RELATION |
THE ASSOCIATION BETWEEN INFORMATION-ASSETS. |
T |
F |
F |
INFORMATION-ASSET-RELATION REASON TEXT
INFORMATION-ASSET-RELATION ROLE CODE
INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE
INFORMATION-ASSET-RELATION TYPE CODE
|
INFORMATION-ASSET-RELATION ROLE CODE |
THE CODE THAT REPRESENTS THE SPECIFIC WAY IN WHICH ONE INFORMATION-ASSET IS RELATED TO ANOTHER INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-RELATION |
INFORMATION-ASSET-RELATION |
THE ASSOCIATION BETWEEN INFORMATION-ASSETS. |
T |
F |
F |
INFORMATION-ASSET-RELATION REASON TEXT
INFORMATION-ASSET-RELATION ROLE CODE
INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE
INFORMATION-ASSET-RELATION TYPE CODE
|
INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE |
THE CODE THAT REPRESENTS THE INDICATION OF TRACKING AN INFORMATION-ASSET-RELATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-RELATION |
INFORMATION-ASSET-RELATION |
THE ASSOCIATION BETWEEN INFORMATION-ASSETS. |
T |
F |
F |
INFORMATION-ASSET-RELATION REASON TEXT
INFORMATION-ASSET-RELATION ROLE CODE
INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE
INFORMATION-ASSET-RELATION TYPE CODE
|
INFORMATION-ASSET-RELATION TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF INFORMATION-ASSET-RELATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-ASSET-RELATION |
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
|
business focus areas |
Complex Matrix to BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS |
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
|
data entities |
List of ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS |
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
|
data subject area |
The data subject area related to the SUPER-TYPE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS |
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
|
name |
Name of the SUPER-TYPE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS |
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
|
status |
Data Status List |
|
|
|
Pending |
|
|
TBD |
T |
Pending Draft Final NA Unknown |
|
|
|
INFORMATION-CLASS |
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
|
sub systems |
Complex Matrix to SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS |
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
|
columndefinition |
SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
columndefinitionkey1 |
SUB-SYSTEM The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
columndefinitionkey2 |
SUB-SYSTEM The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
columndefinitionkey3 |
SUB-SYSTEM System |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
curd info |
Create Retrieve Update and Delete moniker that describes the nature of the transactions performed by the function on data or information |
|
|
|
Read-Only |
|
|
TBD |
T |
Create Modify Read-Only All TBD |
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
data store form of sharing |
Form of Sharing - indicates the form of data sharing the application utilizes; Private, Duplicated, Shared, Enterprise. Value Descriptions Private means that the application exclusively controls that particular data and it is neither read nor updated by other analyzed applications. Duplicated means that the data is copied, either dynamically or periodically, between multiple applications for the purposes of rudimentary data sharing; this category does not include data replication for distributed databases, failure, or disaster recovery purposes. Shared data means that multiple applications have shared access to the data in a single data store, however there may still be multiple private, duplicated, and shared instances of the data. Enterprise data means a single source of the data accessed by all applications using that data; the data is not duplicated, nor are there other private or shared instances of the same data. |
|
|
|
Private |
|
|
TBD |
T |
Duplicate Enterprise Private Shared TBD |
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
data subject area |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
name |
Name of the SUPER-TYPE/SUB-SYSTEM Relationship - typically not unique or specific since the relationship is what defines this definition |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
rowdefinition |
INFORMATION-CLASS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
rowdefinitionkey1 |
INFORMATION-CLASS Data Subject Area |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-CLASS/SUB-SYSTEM |
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
|
FUNCTIONAL-AREA IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A FUNCTIONAL-AREA. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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-SYSTEM ENVIRONMENT TEXT |
THE TEXT OF THE SYSTEM ENVIRONMENT OF AN INFORMATION-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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-SYSTEM INTERFACE TRANSACTION PREDOMINANT METHOD CODE |
THE CODE THAT REPRESENTS THE PREVALENT METHODOLOGY OF INTERACTION WITH AN INFORMATION-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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-SYSTEM SITE QUANTITY |
THE QUANTITY OF SITES OF AN INFORMATION-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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-SYSTEM TYPE CODE |
THE CODE THAT REPRESENTS A KIND OF INFORMATION-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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-SYSTEM USER QUANTITY |
THE QUANTITY OF UTILIZES OF AN INFORMATION-SYSTEM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-SYSTEM |
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
|
FUNCTIONAL-AREA IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A FUNCTIONAL-AREA. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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 ALTERNATE IDENTIFIER |
THE IDENTIFIER THAT ALTERNATIVELY DESIGNATES A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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 ALTERNATE IDENTIFIER SOURCE NAME |
THE NAME OF THE ORIGINATOR OF THE ALTERNATE IDENTIFIER FOR A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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 CATEGORY CODE |
THE CODE THAT REPRESENTS A CLASS OF INFORMATION-TECHNOLOGY-REQUIREMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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 DESCRIPTION TEXT |
THE TEXT THAT CHARACTERIZES A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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 USE CLASS CODE |
THE CODE THAT REPRESENTS THE CATEGORY OF EMPLOYMENT OF A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT |
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
|
INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET IDENTIFIER |
THE IDENTIFIER OF AN INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET FOR A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT AND A SPECIFIC INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET |
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
|
INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET ROLE CODE |
THE CODE THAT REPRESENTS THE SPECIFIC WAY IN WHICH AN INFORMATION-TECHNOLOGY-REQUIREMENT IS RELATED TO AN INFORMATION-ASSET IN A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET |
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
|
bi-directional |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
data entities |
List of ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
description |
Any further description of the Role (Org or Person) as noted |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
initiator |
Initiator List |
|
|
|
|
|
|
TBD |
F |
Source Target Neither NA Unknown |
|
|
|
INTERFACE_ |
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
|
joint it security requirements |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
moa or mou complete |
For AVG use only defalut F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
name |
Name of the SYSTEM-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
operational frequency |
Operational Frequency List |
|
|
|
|
|
|
TBD |
T |
Daily Daily+ Weekly Bi-Weekly Monthly Monthly+ Real-time Other NA Unknown |
|
|
|
INTERFACE_ |
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
|
operational mode |
Operational Mode List |
|
|
|
Unknown |
|
|
TBD |
T |
Batch Interactive Manual NA Unknown |
|
|
|
INTERFACE_ |
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
|
type |
Interface Type List from AVG |
|
|
|
Interface |
|
|
TBD |
T |
Interface Interconnected Interdependant Information Sharing NA Unknown |
|
|
|
INTERFACE_ |
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
|
written approval for esbablishing connection |
For AVG use only default is F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INTERFACE_ |
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
|
architectural status |
|
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
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
|
columndefinition |
MBT-RECOMMENDATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
INVESTMENT/MBT-RECOMMENDATION |
Updated via Matrix Investment Project to MBT Recommendation Cell property is Investment Status. |
F |
F |
F |
architectural status
columndefinition
investment status
name
roll out phase
rowdefinition
|
investment status |
|
|
|
|
Unknown |
|
|
TBD |
T |
VALUE New VALUE Recommended VALUE Rejected VALUE Approved VALUE In Progress VALUE Implemented VALUE NA VALUE Unknown |
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
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
|
roll out phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
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
|
rowdefinition |
INVESTMENT-PROJECT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT/MBT-RECOMMENDATION |
INVESTMENT-PHASE |
Will either be Exhibit 300 or 300-1. |
T |
F |
F |
actual-exit-date
name
target-exit-date
|
actual-exit-date |
Captures the actual decision date (CPIC) when an investment is permitted to go to the next phase. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PHASE |
INVESTMENT-PHASE |
Will either be Exhibit 300 or 300-1. |
T |
F |
F |
actual-exit-date
name
target-exit-date
|
name |
Name of the INVESTMENT-PHASE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PHASE |
INVESTMENT-PHASE |
Will either be Exhibit 300 or 300-1. |
T |
F |
F |
actual-exit-date
name
target-exit-date
|
target-exit-date |
Date the investment is to move to the subsequent phase of the investment cycle |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PHASE |
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
|
budget year |
The fiscal year corresponding to the budget represented by this record of investment data. Updated on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
INVESTMENT-PROJECT |
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
|
curernt upi code |
The UPI currently associated to the project |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
egov |
Is this an eGov investment - Yes, No, or Probably (Target) |
|
|
|
|
|
|
TBD |
F |
Yes No Probable |
|
|
|
INVESTMENT-PROJECT |
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
|
gpea |
Yes/No - whethere this system is covered by GPEA |
|
|
|
|
|
|
TBD |
F |
Type Code Name GPEA Y Yes, system covered by GPEA GPEA N No, system not covered by GPEA |
|
|
|
INVESTMENT-PROJECT |
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
|
home land security |
As noted in Ex. 300 |
|
|
|
|
|
|
TBD |
F |
Type Code Name HomelandDef N No, system does not support Homeland Security goals HomelandDef Y Yes, system supports Homeland Security goals JFMIPConfStatus X Not applicable |
|
|
|
INVESTMENT-PROJECT |
INVESTMENT-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 load comment |
Noted on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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 phase |
The current CPIC investment phase for this investment. The phases are: Pre-Select, Select, Control, Evaluate, and Steady State. Pre-Select – Initial Concept Phase in the Ex. 300. Select – Screen, Rank, and Progress. Planning Phase in the Ex. 300. Control – Monitor Progress and Take Corrective Action. Full Acquisition Phase in the Ex. 300. Evaluate – Conduct Reviews, Make Adjustments, Apply Lessons Learned Steady-State Phase in the Ex. 300. Steady-State – See Evaluate. Steady-state Phase in the Ex. 300. |
|
|
|
|
|
|
TBD |
T |
Pre-Select Select Control Evaluate Steady-State Mixed-Lifecycle NA Unknown |
|
|
|
INVESTMENT-PROJECT |
INVESTMENT-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 title |
The name of the investment as documented on the Exhibit 300 business case. Corresponds to the Exhibit 300 Name of Investment field. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
INVESTMENT-PROJECT |
INVESTMENT-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 type |
Saved from Prior year loads or if the same, original name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
name |
Name of the investment project |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
omb investment type |
Updated on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
percent financial |
he estimated percentage of the total IT investment budget authority associated with the financial components of an Investment listed on Exhibit 53. Only reported for the Investment summary line on the Exhibit 53. See the financial system definition in OMB Circular A-11, Section 53, for a description of financial functions. DME refers to the program cost for new investments, changes or modifications to existing systems that improve capability or performance, changes mandated by Congress or agency leadership, personnel costs for project (investment) management, and direct support. This amount equals the sum of amounts reported for planning and full acquisition of that system in exhibit 300. Updated on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
Percentage |
|
|
|
INVESTMENT-PROJECT |
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
|
percent security |
The estimated percentage of the total investment for budget year associated with IT security for a specific investment listed on Exhibit 53. Only reported for the Investment summary line on the Exhibit 53. Federal agencies must consider the criteria specified in OMB Circular A-11, Section 53, to determine security costs for a specific IT investment. Updated on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
Percentage |
|
|
|
INVESTMENT-PROJECT |
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
|
planned completion date |
Updated on Import from eCPIC |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
previous investment title |
Saved from Prior year loads or if the same, original name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
previous upi code |
Saved from Prior year loads or if the same, original name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT |
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
|
business focus areas |
complex matrix to BUSINESS-FOCUS-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
contributing organizations |
ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
contributing programs |
PROGRAM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
mbt recommendations |
MBT-RECOMMENDATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
organization roles |
INVESTMENT-PROJECT/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
project investment roles |
INVESTMENT-PROJECT/PERSON-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
sponsoring program |
PROGRAM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (OTHER RELATIONS) |
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
|
associated brm sub-functions |
The OMB BRM business reference model sub-functions that are associated to the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
associated prm - end outcomes |
The associated OUTCOME type END from the PRM related to the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
associated prm - intermediate outcomes |
The associated OUTCOME type INTERMEDIATE from the PRM related to the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
associated srm - components |
SRM-SERVICE-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
associated trm - standards |
TRM-SERVICE-STANDARD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
primary brm sub-function |
The associated primary sub-function from the BRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION) |
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
|
enterprise level solutions presentation |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
final solution requirements document |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
findings and recommendations presentation |
Task 5 Outputs • Recommendations and Findings Presentation |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
implemented solution |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa application security group requirements |
Link To Document (probably use a req. mgmt tool) WP Desc.: A description of the required security structure and data regarding users, groups, rights, etc. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa architectural decisions |
Link to Document WP Desc.: A record of important decisions about any aspect of the architecture including the structure of the system, the provision and allocation of function, and adherence to standards. Although this work product is initially created during Analysis and maintained during Design, all Architectural Decisions must be resolved by the end of Design. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa glossary |
Link to Document WP Desc.: A definition of acronyms and terms encountered during the project. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Optional |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa non functional requirements |
Link To Document WP Desc.: A specification of the qualitative and other nonfunctional requirements or conditions that the system must satisfy. Tool: MS-Word or MS-Excel Responsible: Solution Architecture Team Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa requirements matrix |
Link To Document (probably use a req. mgmt tool) WP Desc.: A tracking matrix which details all the requirements of the system, including their type, priority, status, etc. Tool: MS-Word or MS-Excel Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa test strategy |
Link To Document (probably use a req. mgmt tool) WP Desc.: A high-level description of major testing Tasks and approach to be used to ensure that the critical attributes of the system are tested adequately. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooa user requirements |
Link To Document WP Desc.: A description of the business requirements for an application, including the capabilities and features it must support. These requirements must be from a business perspective. Tool: MS-Word Responsible: Solution Architecture Team Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc backup and recovery plan |
Link to Document WP Desc.: A description for backing up the application data Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc build procedures |
Link to Document WP Desc.: A description of how to generate an executable copy of the system. This may include such items as which files are required, which links must be in place, which libraries are accessed, and the sequence of steps required to generate the system, etc. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc deployable components |
Link to Document WP Desc.: The primary software deliverables for a system Tool: Project-Dependent Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc help manual |
Link to Document WP Desc.: A description of the system’s functions Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc operations guide |
Link to Document WP Desc.: A depiction of the processes required in order to support the system in the production environment. Includes details regarding normal operation Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc source code |
Link to Document WP Desc.: The actual implementation of the system design in the chosen programming language(s). Tool: Project-Dependent Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc test results |
Link to Document WP Desc.: A description of the outcomes of a specific test execution, and comparison of the actual test results to the expected results from the test case. It identifies and documents any variances that indicate further analysis is required.. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ooc test specification |
Link to Document WP Desc.: A set of documents that define and describe the actual test architecture Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood acceptance test plan |
Link to Document WP Desc.: A description of the steps the customer will use to verify that the constructed system satisfies the stated requirements. The plan describes clearly and fully how to set up the test and the acceptable system behaviors in response to the test. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood application resource descriptions |
Link to Document WP Desc.: A description of resources (property files, etc.) used by an application, including their purpose, contents, and physical (file) names. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood deployment plan |
Link to Document WP Desc.: A description of the organization, strategy, resources, and methods used to deploy the new application at customer sites. It provides a detailed schedule of events, expected project duration, persons responsible, and event dependencies required to ensure successful cut-over to the new system. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood detailed test plan |
Link to Document WP Desc.: A description created for each level of testing identified as necessary in the Test Strategy. Each plan identifies the scope of testing for that level, functions/features to be tested, the testing Steps to be performed, and the personnel responsible for each Step. Tool: MS-Word & MS-Project Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood enterprise information and data stores definition |
Link to Document WP Desc.: A graphical and text representation of the major data sources used by the system. For each source, it includes a description plus detail on the characteristics of the source, such as transactional requirements, performance/availability, sharing/locking, security, etc. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood persistence design specifications |
Link to Document WP Desc.: A description of how all of the persistence services will be fulfilled for the system. For each service, it contains detail on the Persistence Contract (input), associated Persistence Object, return/result (Persistence Object Façade), data source specifics such as table/columns or file/field locations, and custom query info. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood service descriptions |
Link to Document WP Desc.: A collection of information that defines the purpose of a service, along with detail on how to interact with it. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
ood ui specification and navigation detail |
Link to Document WP Desc.: A description of all Application Interface components (this is applicable to all types of Application Clients [including, but not limited to, those created with JSPs, HTML, Java Swing, etc.] and Application Agents [servlets]) including a depiction of screen appearance, input fields, session data usage, exception handling, and navigational destinations. Tool: MS-Word Responsible: Developer Usage: Reqd |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
policy memo(s) |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
proposal evaluation criteria |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
soa team |
ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
systems development compliance document |
Task 3 Outputs • Systems Development Compliance Document / Matrix (doc link) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
training strategy/curriculum |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT (SOA) |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/ORG-ROLE |
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 |
Name of the investment project |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/ORG-ROLE |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/ORG-ROLE |
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
|
organizations |
Individual performing the role associated to the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/ORG-ROLE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/PERSON-ROLE |
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 project |
Name of the investment project |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/PERSON-ROLE |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/PERSON-ROLE |
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
|
person |
Individual performing the role associated to the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
INVESTMENT-PROJECT/PERSON-ROLE |
ISSUE |
None |
T |
F |
F |
issue status
name
|
issue status |
what is the status of this issue? |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ISSUE |
ISSUE |
None |
T |
F |
F |
issue status
name
|
name |
Name of the ISSUE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ISSUE |
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
|
child sub functions |
The sub functions that belong to this line of business |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LINE-OF-BUSINESS |
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
|
fea code |
The unique id is typically, a number, but is represented by a string. For FEA derived (BUSINESS-AREA, LINE-OF-BUSINESS, SUB FUNCTION), this is the FEA code, for additional levels this code is assigned by the DOI. The first digit represents the business area, the next 2 represent the line of business (in cross-agency form as well), and the final 3 digits represent the sub function (in cross-agency form as well) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LINE-OF-BUSINESS |
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
|
parent business area |
Primary name (parent) defining a DOI business area. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LINE-OF-BUSINESS |
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
|
address 1 |
First Line of address for a node. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
LOCATION-NODE |
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
|
address 2 |
Second line of address for a node. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
LOCATION-NODE |
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
|
city |
City part of address for a node. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
LOCATION-NODE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LOCATION-NODE |
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
|
Name |
Name of Building in which a node is deployed. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
LOCATION-NODE |
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
|
node type |
Type of Location - See Values |
|
|
|
|
|
|
TBD |
F |
Region (ex. New Orleans District) State City Center-Campus (ex. Denver Federal Center) Building (ex. DFC Bldg 53) Building Area (ex. DFC Bldg 53-3rd Floor) |
|
|
|
LOCATION-NODE |
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
|
participating organizations |
This is a ListOf relationship to ORGANIZATION. Organizations that are at this Location Node. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LOCATION-NODE |
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
|
state |
State part of address |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
LOCATION-NODE |
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
|
sub location noes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
LOCATION-NODE |
MBT-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Findings and Recommendations |
T |
F |
F |
child mbt categories
name
parent mbt category
|
child mbt categories |
MBT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CATEGORY |
MBT-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Findings and Recommendations |
T |
F |
F |
child mbt categories
name
parent mbt category
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CATEGORY |
MBT-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Findings and Recommendations |
T |
F |
F |
child mbt categories
name
parent mbt category
|
parent mbt category |
MBT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CATEGORY |
MBT-CRITERIA |
See MBT Blueprint Step 5 for Criteria guidance of Findings and Recommendations |
T |
F |
F |
name
type
|
name |
The name will be a concatonation of the type, level, and name. Example P1 Business Processes Supported - Low |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA |
MBT-CRITERIA |
See MBT Blueprint Step 5 for Criteria guidance of Findings and Recommendations |
T |
F |
F |
name
type
|
type |
This is the type of TAA criteria. It will either be Process, Data, Application or Technology |
|
|
|
|
|
|
TBD |
T |
P D A T |
|
|
|
MBT-CRITERIA |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
business focus area |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
mbt criteria |
MBT_CRITERIA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
mbt issues |
List of MBT-ISSUE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
rationale |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/BUSINESS-FOCUS |
Associative between these two objects |
F |
F |
F |
business focus area
mbt criteria
mbt issues
name
rationale
score
|
score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/BUSINESS-FOCUS |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
mbt criteria |
MBT_CRITERIA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
mbt issues |
List of MBT-ISSUE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
rationale |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
score |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
system |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-CRITERIA/SYSTEM |
Associative between these two objects |
F |
F |
F |
mbt criteria
mbt issues
name
rationale
score
system
system version
|
system version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-CRITERIA/SYSTEM |
MBT-FINDING |
See MBT Blueprint Step 5 for Criteria on Blueprint Findings |
F |
F |
F |
business drivers
mbt categories
mbt recomendations
name
stakeholder categories
|
business drivers |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-FINDING |
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 categories |
List of MBT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-FINDING |
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 recomendations |
List Of MBT-RECOMENDATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-FINDING |
MBT-FINDING |
See MBT Blueprint Step 5 for Criteria on Blueprint Findings |
F |
F |
F |
business drivers
mbt categories
mbt recomendations
name
stakeholder categories
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-FINDING |
MBT-FINDING |
See MBT Blueprint Step 5 for Criteria on Blueprint Findings |
F |
F |
F |
business drivers
mbt categories
mbt recomendations
name
stakeholder categories
|
stakeholder categories |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-FINDING |
MBT-RECOMENDATION-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Recommendations |
T |
F |
F |
child mbt recomendation categories
name
parent mbt recomendation category
|
child mbt recomendation categories |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMENDATION-CATEGORY |
MBT-RECOMENDATION-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Recommendations |
T |
F |
F |
child mbt recomendation categories
name
parent mbt recomendation category
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMENDATION-CATEGORY |
MBT-RECOMENDATION-CATEGORY |
See MBT Blueprint Step 5 for Categorization of Recommendations |
T |
F |
F |
child mbt recomendation categories
name
parent mbt recomendation category
|
parent mbt recomendation category |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
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
|
best practice classification |
|
|
|
|
Unknown |
|
|
TBD |
T |
Department BP Bureau BP General BP NA Unknown |
|
|
|
MBT-RECOMMENDATION |
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
|
business case |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
child recommendations |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
dependant recommendations |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
end outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
fy(04) o&m funding |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
intermediate outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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 recomendation category |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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 tactical areas |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
planning period |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
priority |
Priority of recommendation. |
|
|
|
Unknown |
|
|
TBD |
T |
Tactical Strategic TBD NA Unknown |
|
|
|
MBT-RECOMMENDATION |
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
|
protfolio manager prioritization |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
recomendation type |
|
|
|
|
|
|
|
TBD |
T |
Strategic Tactical NA Unknown |
|
|
|
MBT-RECOMMENDATION |
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
|
tactical solution - cost estimate |
BEA Team Recommended Tactical Solution Cost Estimate - (Man-Weeks) $$$ = 40-100 Man-weeks, $$ = 12-40 Man-weeks, $ = 2-12 Man-weeks |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
tactical solution - level of effort |
BEA Team Recommended Tactical Solution Level of Effort - (Man-Weeks) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION/MBT-STATUS |
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
|
recommendation |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION/MBT-STATUS |
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
|
status begin date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION/MBT-STATUS |
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
|
status comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION/MBT-STATUS |
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
|
status end date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-RECOMMENDATION/MBT-STATUS |
MBT-STATUS |
Captures the Status of what MBT Step this blueprint or business focus area is in |
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-STATUS |
MBT-TACTICAL-AREA |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MBT-TACTICAL-AREA |
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
|
comments |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
contributing organizations |
Organizations that contributed to establishing and using this measure (primarily bureaus and offices within the department) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
data point of contact |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
data reported |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
date last changed |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
description |
The text description for the intermediate outcome goal. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
goal leads |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
key terms/definitions |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
measure goal value |
The quantifiable measure associated to the intermediate goal |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
measure goal value notes |
Free text field containing notes that is associated to the intermediate outcome measure. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
measure indicator |
A measurable indicator of the Intermediate Outcome that can be systematically tracked to assess progress made in achieving predetermined End Outcome goals and using such indicators to assess progress in achieving these goals. A measurement must be an Operationalized Measurement Indicator in the Mission and Business Results Measurement Area. The Operationalized Measurement Indicators agencies create should be determined by referencing the End outcome indicators identified in the DOI Strategic Plan. A Measure must fit within the three Measurement Categories of the Mission and Business Results Measurement Area of the PRM. These categories are Ser-vices for Citizens, Support Delivery of Services, and Management of Government Resources. This Measurement Area aligns with Measurement Areas described in the Business Reference Model Version 2.0. Measurement Components: Costs, Benefits, Schedules, Risks, Alignment, Portfolio, Statistical Projections Legislative Mandates, Organizational constraints, Budgetary Constraints IT Efficiency and Effectiveness Metrics Best Practice Benchmarks |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
MEASURE |
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
|
measure type |
Required property denoting end or intermediate measure. |
|
|
|
|
|
|
TBD |
T |
END INTERMEDIATE |
|
|
|
MEASURE |
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 process |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
name |
The OMB PRM Parent Measurement Generic Indicator that this Operationalized Measure relates to |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
MEASURE |
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
|
prm measure area |
The OMB PRM Parent Measurement Area that this Operationalized Measure relates to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
prm measure category |
The OMB PRM Parent Measurement Category that this Operationalized Measure relates to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
prm measure sub area |
The DOI PRM sub-Measurement Area that this Operationalized Measure relates to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
reporting frequency |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASURE |
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
|
scope of the measure |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
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
|
child measurement area categories |
The child measurement area categories related to the MEASUREMENT-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASUREMENT-AREA |
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 area type |
The measurement area type related to the MEASUREMENT-AREA |
|
|
|
|
|
|
TBD |
T |
VALUE Mission and Business Results VALUE Customer Results VALUE Processes and Activities VALUE Technology |
|
|
|
MEASUREMENT-AREA |
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
|
name |
Name of the MEASUREMENT-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASUREMENT-AREA |
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
|
child generic measurement indicator |
The child generic measurement indicator related to the MEASUREMENT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASUREMENT-CATEGORY |
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
|
measurement area |
The measurement area related to the MEASUREMENT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASUREMENT-CATEGORY |
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
|
name |
Name of the MEASUREMENT-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MEASUREMENT-CATEGORY |
MISSION |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MISSION |
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
|
description |
Strategic Goal: Describes the Mission Area Goal, in the strategic Plan this is the Strategic Goal. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
MISSION-AREA |
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
|
end outcomes |
The OUTCOME type END related to the MISSION-AREA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
MISSION-AREA |
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
|
name |
This is the goal level used in bureau and office plans, sometimes referred to as the mission goal level in bureau plans. This level is not directly measurable. Interior crosswalks budget activities to the GPRA program activity level. [GPRA Program Activity (Mission Goal)] In DEAR, MISSION-AREA lists the DOI Goal Names. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
MISSION-AREA |
OBJECTIVE |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OBJECTIVE |
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
|
administrative loss rate |
THE ACTUAL RATE OF PERSONNEL ATTRITION APPLICABLE TO AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
business drivers |
Complex matrix Business Driver to Organization from associative is BUSINESS-DRIVER/ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
category code |
THE CODE THAT REPRESENTS A CLASSIFICATION OF AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
charter |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
child organizations |
this describes the recursive relationship or hierarchical construct associated to the org. structure. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
classification code |
THE CODE THAT REPRESENTS A CATEGORIZATION OF AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
Data Quality Attributes |
Chapter Data Quality LAYOUT {COLS 2 TAB ALIGN OVER} GROUP Overall Summary {LAYOUT {COLS 2 TAB ALIGN OVER} PROPERTY Inventory Rating Score {EDIT TEXT LENGTH 10 HELP None } PROPERTY Integration Rating Score {EDIT TEXT LENGTH 10 HELP None } PROPERTY Ref Model Mapping Rating Score {EDIT TEXT LENGTH 10 HELP None } PROPERTY Modeling Rating Score {EDIT TEXT LENGTH 10 HELP None } PROPERTY Overall Comments {EDIT TEXT LENGTH 3000 LINES 2 ZOOMABLE HELP Sample Priority, Next Steps, and other Descriptive information READONLY} } GROUP System Inventory {LAYOUT {COLS 2 TAB ALIGN OVER} PROPERTY Inventory Completeness {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Inventory Attribution {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY System Hierarchy Modeled {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Inventory Comments {EDIT TEXT LENGTH 3000 LINES 2 ZOOMABLE HELP Sample Priority, Next Steps, and other Descriptive information READONLY} } GROUP Integrate with OCIO {LAYOUT {COLS 2 TAB ALIGN OVER} PROPERTY C&A Boundary Completeness {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY C&A Boundary Mapping {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY CPIC Mapping {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Privacy Mapping {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY IITD Mapping {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Contact Information {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Integration Comments {EDIT TEXT LENGTH 3000 LINES 2 ZOOMABLE HELP Sample Priority, Next Steps, and other Descriptive information READONLY} } GROUP Describe with Reference Models {LAYOUT {COLS 2 TAB ALIGN OVER} PROPERTY Mapped to Performance Reference Model {EDIT TEXT LISTONLY LIST Data Quality Status List DEFAULT Unknown LENGTH 30 HELP None } PROPERTY Map |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
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. |
|
|
|
ORGANIZATION |
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
|
duration type code |
THE CODE THAT REPRESENTS A SPECIFIC KIND OF TIME FRAME ASSOCIATED WITH AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
enterprise type code |
THE CODE THAT DENOTES THE KIND OF ENTERPRISE UNDERTAKEN BY AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
formal |
denotes whether an organizaiton is formal or not. Informal organizations are like teams. Default is true. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
interacting organizations |
List of ORGANIZATION related by INTERACTING for reporting purposes. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
managing organization |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
name |
Name of the organization |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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 identifier |
THE IDENTIFIER THAT REPRESENTS AN ADMINISTRATIVE STRUCTURE WITH A MISSION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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 roles |
The role that the specific organization performs |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
parent organization |
That member of the organizational hierarchy that has children elements beneath. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
primary activity code |
THE CODE THAT REPRESENTS THE PRINCIPAL FUNCTION OF AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
primary industry category code |
THE CODE THAT REPRESENTS A CLASSIFICATION OF THE PRINCIPAL BUSINESS AREA OF AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
purpose |
Purpose of the informal organization. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
symbol identifier |
THE IDENTIFIER THAT REPRESENTS AN ALTERNATIVE IDENTIFICATION OF AN ORGANIZATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
team members |
list of relationship to STAKEHOLDER-CATEGORY. More of what type of team members would be involved. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
technical-service-specifications |
That part of the Technical Reference Model (TRM) that details the specific products used to satisfy a technology requirement |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
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
|
type code |
THE CODE THAT REPRESENTS A KIND OF ORGANIZATION. |
|
|
|
|
|
|
TBD |
T |
Department Office Bureau Program Area Division Interagency Team to be used as CMBT or CMIT for BFA NA Unknown |
|
|
|
ORGANIZATION |
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
|
url |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION |
ORGANIZATION ADDRESS |
None |
T |
F |
F |
ORGANIZATION ADDRESS Identifier
|
ORGANIZATION ADDRESS Identifier |
Unique identifier for the address detailing the facilities location. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION ADDRESS |
ORGANIZATION NAME |
None |
T |
F |
F |
ORGANIZATION NAME Identifier
ORGANIZATION-NAME Category Code
|
ORGANIZATION NAME Identifier |
Unique identifier for the Name of the organization |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION NAME |
ORGANIZATION NAME |
None |
T |
F |
F |
ORGANIZATION NAME Identifier
ORGANIZATION-NAME Category Code
|
ORGANIZATION-NAME Category Code |
Code to identify the organization |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION NAME |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION/PERSON-ROLE |
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
|
name |
Intersection attribute that describes the association of organization to individuals name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION/PERSON-ROLE |
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
|
organization |
The name of organization associated to the individual who is performing the role |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION/PERSON-ROLE |
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
|
person |
Individual playing the role |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION/PERSON-ROLE |
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
|
role remarks |
Free text field to describe the nature of the role. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ORGANIZATION/PERSON-ROLE |
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
|
abc work activities |
Activity Based Costing a means to identify and track the work and its associated costs performed by an organization |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
department |
True if is a department level outcome. Should only be mapped to strat plan if is department level. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
description |
Free text field to describe the end outcome more fully |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
end outcome measures |
The MEASURE type END related to the OUTCOME |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
intermediate outcomes |
The MEASURE type INTERMEDIATE related to the OUTCOME |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
name |
Name of the END-OUTCOME |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
OUTCOME |
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
|
outcome name |
Project Performance Goals describe and support the Strategic Goal. Also known in the DOI Strategic Plan as the Long-Term Goal. There are two or more long-term Goals supporting a DOI Strategic Goal. Long-Term Goal The long-term goal expresses a desired result and is measured by one or more performance indicators. This is the 5-year goal level that is used in the strategic plan. Annual performance measures indicate the success in achieving the long-term goal. Outputs/Outcomes Calculation Vectors (6 dimensions): People, Process, Technology, Fixed Assets, Service Levels, Time Performance Scorecards Dashboards |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
OUTCOME |
OUTCOME |
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
|
outcome type |
Required field denoting end or intermediate outcome. |
|
|
|
|
|
|
TBD |
T |
END INTERMEDIATE |
|
|
|
OUTCOME |
OUTER-DEPLOYMENT-SCOPE |
Look table for valules. |
T |
F |
F |
name
|
name |
Name of the OUTER-DEPLOYMENT-SCOPE |
|
|
|
|
|
|
TBD |
T |
Commercial-E-Government Inter-DOI Inter-Federal Government Inter-Other Government Inter-State Government NA Public-E-Government Unknown |
|
|
|
OUTER-DEPLOYMENT-SCOPE |
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
|
name |
Name of the PERFORMANCE-REFERENCE-MODEL |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PERFORMANCE-REFERENCE-MODEL |
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
|
address-line1 |
First line of an individual's business address. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
address-line2 |
Second line of individual's business address. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
business drivers |
Complex matrix Business Driver to Organization from associative is BUSINESS-DRIVER/ORGANIZATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PERSON |
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
|
city |
City part of individual's business address. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
person-email |
Email address(es) comma separated |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
person-id |
A unique identifier for an individual. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
person-name |
An individual's name. First (Middle) Last Name |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
phone1 |
An individual's phone number. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
phone2 |
An individual's secondary (or cellular) phone number. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
state |
The state part of An individual's address. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
zip |
The zip code of an individual's address. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PERSON |
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
|
role |
The role a person assumes relative to a specific system. A system will have a number of individuals associated with it in a variety of roles. A person may occupy multiple roles relative to a specific system. For DOI A-130 Managers, the following roles are important: *IT System Owner, * IS Program Manager, *System Security Manager, *System Project Manager. |
|
|
|
|
|
|
Intersection |
F |
Project Manager Agency Head Stakeholder Project Team Member IS Program Manager IT System Owner System Security Manager System Project Manager C&A Point of Contact Program Manager |
|
|
|
POC/PERSON |
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
|
role-remarks |
General comments or remarks that serve to further clarify a specific role between a person and a system. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
POC/PERSON |
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
|
additional information comments |
Additional information outside of a description. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
alias |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
asset id |
The Unique Asset ID used to identify this piece of hardware |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
database/storage |
The database/storageTRM relationship. Used to define what Technologies the Processing Node Uses/Has/Provides. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
deep packet inspection |
Should only be populated if Fire Wall. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
delivery servers |
The delivery serversTRM relationship. Used to define what Technologies the Processing Node Uses/Has/Provides. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
hardware/infrastructure |
The hardware/infrastructureTRM relationship. Used to define what Technologies the Processing Node Uses/Has/Provides. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
ip address |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
known issues |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
location node |
The physical facility location that describes where an IT assets has been deployed. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
managing organization |
This is a OneOf relationship to ORGANIZATION. Organization managing the Processing Node. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
name |
Name of the processing assets. If not a formal name, describe the node as best as possible. Such as Intel-Bureau-Client/Server-Use for a name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
node deployment month |
Month the hardware was put into deployment, not necessarily the date the/a system went into deployment on the piece of hardware |
|
|
|
Unknown |
|
|
TBD |
T |
1 2 3 4 5 6 7 8 9 10 11 12 Unknown |
|
|
|
PROCESSING-NODE |
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
|
node deployment year |
Year the hardware was put into deployment, not necessarily the date the/a system went into deployment on the piece of hardware |
|
|
|
Unknown |
|
|
TBD |
T |
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 |
|
|
|
PROCESSING-NODE |
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
|
parent processing nodes |
The processing node is a logical partition of the parent processing node. This allows you to make a tree of processing nodes if you have the situation where you have a node split by domains and further by other logical partitioning, etc. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
physical processing node |
The processing node is a logical partition of the parent processing node. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
point of contact information |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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 functions |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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 Type |
Processing node can be physical or a logical partition. If it is logical then it can have a physical processing node as the parent. |
|
|
|
|
|
|
TBD |
F |
Physical *default Logical |
|
|
|
PROCESSING-NODE |
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
|
protocol capabilities |
|
|
|
|
Unknown |
|
|
TBD |
T |
IPv4 IPv6 dual stack tunneling NAT |
|
|
|
PROCESSING-NODE |
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
|
serial number |
If physical, and desired, put serial # of hardware |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
support platforms |
The support platformsTRM relationship. Used to define what Technologies the Processing Node Uses/Has/Provides. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
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
|
technology refresh date |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE |
PROCESSING-NODE-FUNCTION |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROCESSING-NODE-FUNCTION |
PRODUCT |
|
T |
F |
F |
business focus areas
enterprise investments
name
|
business focus areas |
Complex matrix to BUSINESS-FOCUS-AREA. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PRODUCT |
PRODUCT |
|
T |
F |
F |
business focus areas
enterprise investments
name
|
enterprise investments |
INVESTMENT-PROJECT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PRODUCT |
PRODUCT |
|
T |
F |
F |
business focus areas
enterprise investments
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PRODUCT |
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
|
name |
The unique name for a DOI Program. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PROGRAM |
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 roles |
Program to person role. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM |
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
|
sponsoring organization |
An organization that provides the role of sponsor for an investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM |
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
|
supporting organizations |
Organizations who are not directly responsible for but play an important role with respect to the investment or system. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM |
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
|
url |
A reference URL where additional information may be found about the Program. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
PROGRAM |
PROGRAM/PERSON-ROLE |
Associative between these two objects |
F |
F |
F |
Delete
name
person
program
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM/PERSON-ROLE |
PROGRAM/PERSON-ROLE |
Associative between these two objects |
F |
F |
F |
Delete
name
person
program
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM/PERSON-ROLE |
PROGRAM/PERSON-ROLE |
Associative between these two objects |
F |
F |
F |
Delete
name
person
program
|
person |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM/PERSON-ROLE |
PROGRAM/PERSON-ROLE |
Associative between these two objects |
F |
F |
F |
Delete
name
person
program
|
program |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROGRAM/PERSON-ROLE |
PROJECT |
None |
T |
F |
F |
INFORMATION-PROJECT-NAME
|
INFORMATION-PROJECT-NAME |
Name of the project |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
PROJECT |
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
|
QUALITATIVE-DATA-DOMAIN ACCURACY-PERCENT QUANTITY |
THE QUANTITY THAT REPRESENTS HOW ACCURATE A QUALITATIVE-DATA-DOMAIN MUST BE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUALITATIVE-DATA-DOMAIN |
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
|
QUALITATIVE-DATA-DOMAIN CHARACTER SET NAME |
THE NAME OF THE COLLECTION OF SYMBOLS OF A QUALITATIVE-DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUALITATIVE-DATA-DOMAIN |
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
|
QUALITATIVE-DATA-DOMAIN DATA TYPE CODE |
THE CODE THAT REPRESENTS THE KIND OF WAY IN WHICH DOMAIN VALUES ARE STORED IN A DATABASE FOR A SPECIFIC QUALITATIVE-DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUALITATIVE-DATA-DOMAIN |
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 ACCURACY CODE |
THE CODE THAT REPRESENTS THE REQUIRED ACCURACY OF A QUANTITATIVE-DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN |
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 BASE QUANTITY |
THE BENCHMARK QUANTITY OF A QUANTITATIVE-DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN |
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 DATA TYPE CODE |
THE CODE THAT REPRESENTS THE KIND OF WAY IN WHICH DOMAIN VALUES FROM A SPECIFIC QUANTITATIVE-DATA-DOMAIN ARE STORED IN A DATABASE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN |
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 SCALE QUANTITY |
THE QUANTITY OF POSITIONS TO THE RIGHT OF THE DECIMAL OF A QUANTITATIVE-DATA-DOMAIN. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN |
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
|
Data Class INFORMATION-ASSET IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS AN INFORMATION-ASSET. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT |
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 IDENTIFIER |
HE IDENTIFIER THAT REPRESENTS A QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT |
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 NAME |
THE NAME OF QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT |
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
|
QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT-CONVERSION-ASSOCIATION ALGORITHM TEXT |
THE TEXT OF THE FORMULA OF A QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT-CONVERSION-ASSOCIATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
QUANTITATIVE-DATA-DOMAIN-MEASUREMENT-UNIT-CONVERSION-ASSOCIATION |
RECOMENDATION-CATEGORY |
None |
T |
F |
F |
name
|
name |
Name of the RECOMENDATION-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
RECOMENDATION-CATEGORY |
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
|
RELATION-TYPE GENERATE TRACE ADDITION INDICATOR CODE |
THE CODE THAT REPRESENTS THE INDICATION OF ADDITION OF A RELATION-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
RELATION-TYPE |
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
|
RELATION-TYPE IDENTIFIER |
THE IDENTIFIER THAT REPRESENTS A RELATION-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
RELATION-TYPE |
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
|
RELATION-TYPE INVERSE RELATION NAME |
THE NAME OF A REVERSE RELATION OF A RELATION-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
RELATION-TYPE |
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
|
RELATION-TYPE NAME |
THE NAME OF A RELATION-TYPE. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
RELATION-TYPE |
REQUIREMENT-FOR-TECH-ARCH |
None |
T |
F |
F |
TAR_description
TAR_ID
|
TAR_description |
Technical Architecture requirement description is a free text field that describes |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
REQUIREMENT-FOR-TECH-ARCH |
REQUIREMENT-FOR-TECH-ARCH |
None |
T |
F |
F |
TAR_description
TAR_ID
|
TAR_ID |
Technical Architecture requirement description unique identifier. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
REQUIREMENT-FOR-TECH-ARCH |
ROLLOUT-PHASE |
Look up table to determine phase for imiplementation or phase out. |
T |
F |
F |
Description
Name
|
Description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ROLLOUT-PHASE |
ROLLOUT-PHASE |
Look up table to determine phase for imiplementation or phase out. |
T |
F |
F |
Description
Name
|
Name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
ROLLOUT-PHASE |
SECURITY-AUTHENTICATION-MODEL |
None |
T |
F |
F |
Name
|
Name |
Look up table for security authentication. What is the authentication model (identification of who the user is) used for this system component? Choose the combination of list items that describe the models that have been implemented. |
|
|
|
|
|
|
TBD |
F |
User ID Password Digital Certificate Smart Card Other Custom None Unknown |
|
|
|
SECURITY-AUTHENTICATION-MODEL |
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
|
SECURITY-CLASSIFICATION CODE |
THE CODE THAT REPRESENTS A SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SECURITY-CLASSIFICATION |
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
|
SECURITY-CLASSIFICATION DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES A SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SECURITY-CLASSIFICATION |
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
|
SECURITY-CLASSIFICATION DOWNGRADE INSTRUCTION TEXT |
THE TEXT THAT EXPLAINS PROCEDURES FOR LOWERING A CURRENT SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SECURITY-CLASSIFICATION |
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
|
SECURITY-CLASSIFICATION STATUS CODE |
THE CODE THAT DENOTES THE STATE OF A SECURITY-CLASSIFICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SECURITY-CLASSIFICATION |
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
|
analysis explanation |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
columndefinition |
SERVICE-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
description |
The association from the SRM Service Component to the BRM work activity |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
geospatial analysis candidate |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
geospatial modify candidate |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
geospatial read candidate |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
Intersection? |
The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
modify explanation |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
name |
The name within the association of the SRM service component to the work activity of the BRM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
read explanation |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
rowdefinition |
FUNCTION-ACTIVITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMP/FUNCTION-ACTIVITY |
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
|
best practices |
The best practices identified as a part of the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
brm tiers |
The association capability between the SRM and BRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
businesss focus areas |
BUSINESSS-FOCUS-AREA Update via matrix or import. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
child service components |
SERVICE-COMPONENT is child in. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
comments |
Free text comment field describing the principle. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
domain architecture principles |
The principles or rules that provide guidance for the respective SRM areas. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
enterprise investments |
INVESTMENT-PROJECT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
fea code |
Code as specified in the FEA Reference Model for Service Reference Manual |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
name |
The name of the principle. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
parent service type |
Foreign key associating the various levels of the service reference model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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 type |
The second tier of the SRM hierarchical model that classifies the service component tier |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
system components |
The lowest tier of the SRM that articulates and describes the capability . |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
technical service standards |
Foreign Key to TRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
technology domain team |
A domain team is responsible for developing architecture principles, with associated rationale and implication, identifying applicable standards and preferred products, and conducting other work assigned by the Architecture Team, for a given collection of related technologies. There is a domain team associated with each of the Technical Architecture Domains |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT |
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
|
columndefinition |
The following entity ENTITY/SYSTEM-COMPONENT represents the row and column respectively of the matrix in support the reporting functions. In the User Interface the user will see a label ENTITY/SYSTEM-COMPONENT and not the attributes listed in the schema. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
columndefinitionkey1 |
Primary key for creation of the intersection matrix that bridges the Entity/SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
1 Null |
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
description |
The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
intersection? |
The intersection of the row and column to support a matrix report where a positive match between row and column gets populated with an x and a negative match has a null value. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
name |
The name describing the association of the service component of the SRM to the system component |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
relationship type |
How does this Service Component support the system component Core Capability - This is the primary service provided by this system component Cross Capability - This is a service that this component provides that is a cross-cutting service Secondary Capability - This system component can provide this service, but is not the primary focus - before assuming re-use for this service, consider other options NA Unknown |
|
|
|
Unknown |
|
|
TBD |
T |
Core Capability Cross Capability Secondary Capability NA Unknown |
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
re-use design |
ARCHITECTURAL-PATTERN |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
rollout/phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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 system interaction |
What this Service Component does to support the system component Provides - The system component offers this service to be used Utilizes - The system component uses this service (for example, via a system interface) |
|
|
|
Unknown |
|
|
TBD |
T |
Provides Utilizes TBD NA Unknown |
|
|
|
SERVICE-COMPONENT/COMPONENT_ |
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
|
best practices |
The best practices associated to the top level of the SRM or the service domain |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-DOMAIN |
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
|
comments |
Free text field that further describes the service domain of the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-DOMAIN |
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
|
fea code |
Code as specified in the FEA Reference Model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-DOMAIN |
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
|
name |
The name of a classification within the SRM. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-DOMAIN |
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
|
skills composition |
The identified skills associated with or required by the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-DOMAIN |
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
|
child service domains |
Foreign key associating the various levels of the service reference model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-REFERENCE-MODEL |
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
|
name |
The name of the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-REFERENCE-MODEL |
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
|
best practices |
The best practices associated to the second tier of the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-TYPE |
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
|
comments |
Free text field used to describe the second tier of the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-TYPE |
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
|
fea code |
Code as specified in the FEA Reference Model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-TYPE |
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
|
name |
The name of the classification of the service type within the SRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-TYPE |
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
|
skills compositions |
The type of skills required to support or evolve the technologies |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SERVICE-TYPE |
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
|
SOFTWARE-APPLICATION CREATOR IDENTIFIER |
THE IDENTIFIER OF THE AGENT RESPONSIBLE FOR CREATING A SPECIFIC SOFTWARE-APPLICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SOFTWARE-APPLICATION |
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
|
SOFTWARE-APPLICATION FUNCTIONAL DESCRIPTION TEXT |
THE TEXT THAT DESCRIBES THE OPERATIONS OF A SOFTWARE-APPLICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SOFTWARE-APPLICATION |
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
|
SOFTWARE-APPLICATION PRODUCTION STATUS CODE |
THE CODE THAT REPRESENTS THE OPERATIONAL STATUS OF A SOFTWARE-APPLICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SOFTWARE-APPLICATION |
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
|
SOFTWARE-APPLICATION VERSION RELEASE CALENDAR DATE |
THE ISSUE DATE OF A RENDITION OF A SOFTWARE-APPLICATION. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SOFTWARE-APPLICATION |
STAKEHOLDER-CATEGORY |
Existing SA Definition Type |
T |
F |
F |
name
stakeholder type
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STAKEHOLDER-CATEGORY |
STAKEHOLDER-CATEGORY |
Existing SA Definition Type |
T |
F |
F |
name
stakeholder type
|
stakeholder type |
Stakeholder Type List Per value of list selected will change the depiction of the symbo. |
|
|
|
Person |
|
|
TBD |
T |
Organization Person NA Unknown |
|
|
|
STAKEHOLDER-CATEGORY |
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
|
status-type |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STATUS |
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
|
status-value |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STATUS |
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
|
as of date |
The date that this version of the Strategic Plan was released |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
date of plan |
The date range that this Strategic Plan represents |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
description |
Small Description of the Mission Area from the DOI Strategic Plan. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
STRATEGIC-PLAN |
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
|
end outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
intermediate outcomes |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
mission areas |
The mission areas related to the STRATEGIC-PLAN |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
mission statement |
A mission is the enduring, chartered, long-term goal(s) of an organization. At the DOI, it is the mission statement that guides the DOI Strategic Goals from the Strategic Plan. From ITIM GAO 05/00 Vol 1 Doc. Example: The mission of the DOI is to protect and provide access to our Nation's natural and cultural heritage and honor our trust responsibilities to Indian Tribes and our commitments to island communities |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
STRATEGIC-PLAN |
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
|
name |
Name of the strategic plan |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
organization |
Organization that produced this Strategic Plan |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
version |
The Version of the Strategic plan |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
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
|
vision statement |
The Vision Statement that is within this Strategic Plan |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGIC-PLAN |
STRATEGY |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
STRATEGY |
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
|
fea code |
The unique id is typically, a number, but is represented by a string. For FEA derived (BUSINESS-AREA, LINE-OF-BUSINESS, SUB FUNCTION), this is the FEA code, for additional levels this code is assigned by the DOI. The first digit represents the business area, the next 2 represent the line of business (in cross-agency form as well), and the final 3 digits represent the sub function (in cross-agency form as well) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-FUNCTION |
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
|
homeland security flag |
Identifies the sub-function as being associated with homeland security. This is used specifically in the Exhibit 300 instruction noting that if an investment supports homeland security, indicate by corresponding number which homeland security mission area(s) this investment supports? 1. Intelligence and Warning; 2. Border and Transportation Security; 3. Defending Against Catastrophic Threats; 4. Protecting Critical Infrastructure and Key Assets; 5. Emergency Preparedness and Response; or 6. Other. |
|
|
|
|
|
|
TBD |
F |
Yes No |
|
|
|
SUB-FUNCTION |
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
|
parent line of business |
The line of business that this FEA Sub function belongs to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-FUNCTION |
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
|
acronym |
Abbreviations for the sub-system. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SUB-SYSTEM |
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
|
current user total |
Defines the current user total that this sub-system currently has, regardless of design |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
description |
Textual description of the subsystem, including the business operation it supports and general functions the subsystem performs. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
full name |
Descriptive text that identifies the subsystem. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
geographic user description |
Choose the description that most closely states the extent that the users will be geographically distributed taking into account all types of users expected. This is the user distribution the system component should be able to handle through the use of distributed architecture design principles |
|
|
|
|
|
|
TBD |
T |
Center Office Users Field Office Users International Users Mobile Users National Users State Office Users Unknown Washington Office Users |
|
|
|
SUB-SYSTEM |
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
|
interface comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
managing partner |
ORGANIZATION designated as the managing partner. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
maximum user design |
The sum of all actual or planned users for this subsystem. This number should include the maximum number of users for which this subsystem has been designed. It should include all anticipated users at the maximum planned deployment. Include all users from all sites that will be able to access the subsystem when operational regardless of concurrency. |
|
|
|
|
|
|
TBD |
F |
Numeric |
|
|
|
SUB-SYSTEM |
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
|
name |
Descriptive text that identifies the subsystem. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SUB-SYSTEM |
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
|
number of eauthentications per year |
Enter from 0 to 100000 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
number of users in g2b segment |
Enter from 0 to 100000 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
number of users in g2c segment |
Enter from 0 to 100000 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
number of users in g2g segment |
Enter from 0 to 100000 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
number of users in iee segment |
Enter from 0 to 100000 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
organizational roles |
ORGANIZATION and the roles they play within the sub system. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
peak concurrent user design |
Defines the peak concurrent user design that this sub-system was designed for |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
peak concurrent user total |
The peak number of concurrent users currently using the subsystem - should include the total number of defined users currently using a subsystem at the same time during peak subsystem processing times. |
|
|
|
|
|
|
TBD |
F |
Integer from 0 to 100000 Unknown |
|
|
|
SUB-SYSTEM |
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
|
replaces sub systems |
Relationship that describes which sub systems replace sub systems |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
system |
The System that this Subsystem belongs to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
system component instances |
The instance of a component which is the lowest level of implemented IT functionality when done can correctly can be reused by other IT systems. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
system version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM |
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
|
user communities |
a general description of the types of users for the system |
|
|
|
|
|
|
TBD |
T |
External Commercial Management External Commercial Staff External Government Management General International Public General U.S. Public Internal Management Internal Staff Unknown |
|
|
|
SUB-SYSTEM |
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
|
user design comment |
Further describe the nature and distribution of users. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SUB-SYSTEM |
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
|
version |
Text that identifies the configuration management version of the subsystem. Whole integers separated by underscores, no periods should be used. Example 1_2_4 |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SUB-SYSTEM |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
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
|
organization |
The organization related to the SUB-SYSTEM/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
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
|
role remarks |
Any further description of the Role (Org or Person) as noted |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
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
|
sub system |
The sub system related to the SUB-SYSTEM/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
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
|
sub system version |
The sub system version related to the SUB-SYSTEM/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
SUB-SYSTEM/ORGANIZATION-ROLE |
This associative entity SUB-SYSTEM/ORGANIZATION-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. |
F |
F |
F |
Delete
organization
role remarks
sub system
sub system version
system
system version
|
system |
The system related to the SUB-SYSTEM/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
SUB-SYSTEM/ORGANIZATION-ROLE |
This associative entity SUB-SYSTEM/ORGANIZATION-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. |
F |
F |
F |
Delete
organization
role remarks
sub system
sub system version
system
system version
|
system version |
The system version related to the SUB-SYSTEM/ORGANIZATION-ROLE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM/ORGANIZATION-ROLE |
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
|
bi-directional |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
description |
Any further description of the Role (Org or Person) as noted |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
from sub-system |
The related sub-system to SUB-SYSTEM-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
from system |
The Parent System of the sub-system interfacing from |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
from system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
from version |
The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
initiator |
Initiator List |
|
|
|
|
|
|
TBD |
T |
Source Target Neither NA Unknown |
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
joint it security requirements |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
moa or mou complete |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
name |
Name of the SUB-SYSTEM-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
operational frequency |
Operational Frequency List |
|
|
|
|
|
|
TBD |
T |
Daily Daily+ Weekly Bi-Weekly Monthly Monthly+ Real-time Other NA |
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
operational mode |
Operational Mode List |
|
|
|
Unknown |
|
|
TBD |
T |
Batch Interactive Manual NA Unknown |
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
to sub-system |
The related sub-system to SUB-SYSTEM-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
to system |
The Parent System of the sub-system interfacing to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
to system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
to version |
The Sub-system Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
type |
Interface Type List |
|
|
|
Interface |
|
|
TBD |
T |
Interface Interconnected Interdependant Information Sharing NA Unknown |
|
|
|
SUB-SYSTEM-INTERFACE |
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
|
written approval for esbablishing connection |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUB-SYSTEM-INTERFACE |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
curd info |
Create Retrieve Update and Delete moniker that describes the nature of the transactions performed by the function on data or information |
|
|
|
|
|
|
TBD |
F |
modify readonly |
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
sub system |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
sub system version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
system |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPER-TYPE/SUB-SYSTEM |
Associative between these two objects |
F |
F |
F |
curd info
name
sub system
sub system version
system
system version
|
system version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPER-TYPE/SUB-SYSTEM |
SUPPLIER |
|
T |
F |
F |
address
contact
name
url
|
address |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPPLIER |
SUPPLIER |
|
T |
F |
F |
address
contact
name
url
|
contact |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPPLIER |
SUPPLIER |
|
T |
F |
F |
address
contact
name
url
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPPLIER |
SUPPLIER |
|
T |
F |
F |
address
contact
name
url
|
url |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SUPPLIER |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
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
|
Name |
The association of the organization to a system to support the establishment of how the individual and organization support the system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
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
|
organization |
The organization identified to support the system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
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
|
role remarks |
Free text field further describing the nature of relationship of the individual and organization to the system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
SYSTEM/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 |
the system that is to be supported by the organization and individual |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
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
|
version |
The Version of the System that this is linked to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/ORGANIZATION-ROLE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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
|
Name |
An association describing the role of the individual to the system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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
|
Person |
The person performing the role in support of the IT system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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
|
Role Remarks |
Free text field further describing the nature of relationship of the individual to the system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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 |
This describes the association of the system and the individual and the role they play in support of the system. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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
|
Version |
The Version of the System that this is linked to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM/PERSON-ROLE |
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
|
acronym |
The acronym specified in the system's supporting contract or identified within the OMB Form 53. |
|
|
|
|
|
|
Project ArchitecJim Cox |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
application score |
Calculated from underlying MBT scoring criteria where type is application. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
construction comment |
Comments on the construction of the system component that are not captured elsewhere. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
data score |
Calculated from underlying MBT scoring criteria where type is data. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
data storage comment |
Comments on the data storage environment of the system component that are not captured elsewhere. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
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 |
|
|
|
SYSTEM_ |
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
|
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 |
T |
Field Office State National NA Unknown |
|
|
|
SYSTEM_ |
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
|
deployment scope outer enterprise |
Breadth of deployment and intended usage of this system beyond the owning organization. |
|
|
|
|
|
|
TBD |
T |
Commercial-E-Government Inter-DOI Inter-Federal Government Inter-Other Government Inter-State Government NA Public-E-Government Unknown |
|
|
|
SYSTEM_ |
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
|
estimated end of system life |
Estimation of retirement of a system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
execution environment comment |
Description of the execution environment of the system component that are not captured elsewhere including software technology migration plans. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
full name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
future plans comment |
Description of the future plans for the system 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 |
|
|
|
SYSTEM_ |
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
|
interface comment |
Description of the interfaces and their design both hardware and software. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
investment project |
A project that has been established to manage the investment |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
mbt criterion and scoring |
Associative definition to hold the score, criteria, and rational for the various areas of MBT system scoring. Application Data Process Technology Total |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
mbt findings |
MBT-FINDINGS |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
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 |
|
|
|
SYSTEM_ |
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
|
name |
Descriptive text that identifies the system. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
operational environment comment |
Description of the operational environment of the system component that are not captured elsewhere including software technology migration plans. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
operational month |
The month of the actual or planned deployment of the system. |
|
|
|
Unknown |
|
|
TBD |
T |
1 2 3 4 5 6 7 8 9 10 11 12 Unknown |
|
|
|
SYSTEM_ |
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
|
operational status |
The status of the actual or planned deployment of the system. 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 |
T |
Operational Under Development Under Procurement Undergoing A Major Modification NA Unknown |
|
|
|
SYSTEM_ |
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
|
operational year |
The year of the actual or planned deployment of the system. |
|
|
|
Unknown |
|
|
TBD |
T |
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 |
|
|
|
SYSTEM_ |
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
|
organization roles |
Role that the orgranziation plays in supporting the system |
|
|
|
|
|
|
TBD |
T |
Develops Funds Hosts Managing Partner Owns Unknown Uses |
|
|
|
SYSTEM_ |
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
|
person roles |
Roles required to support the development and operations of a system' |
|
|
|
|
|
|
TBD |
T |
C&A Point of Contact Information Technology Investment Management Representative IS Program Manager Portfolio Manager Project Proponent Project Sponsor System Owner System Project Manager System Security Manager System User Representative Unknown |
|
|
|
SYSTEM_ |
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
|
platform comment |
Comments on the platform (hardware) environment of the system that are not captured elsewhere, including hardware technology migration plans. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
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
|
process score |
Calculated from underlying MBT scoring criteria where type is process |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
replaces systems |
Attribut that defines the relationship between the system and other systems that it will replace. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
security architecture design model |
The internal structuring or architecture of the software security model for this system. Choose any combination of list items that describe the method by which the system component security function has been implemented. |
|
|
|
|
|
|
TBD |
T |
Custom Developed Security Component None Other Reuse of Bureau Security Component Reuse of Certificate Security Component Reuse of COTS Security Component Reuse of Database Security Component Reuse of GOTS Security Component Reuse of Middleware Security Component Reuse of Operating System Security Component Reuse of Other Security Component Reuse of Web Application Server Security Component Reuse of Web Services Security Component Unknown |
|
|
|
SYSTEM_ |
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
|
software development lifecycle stage |
|
|
|
|
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 |
|
|
|
SYSTEM_ |
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
|
sub systems |
SUB-SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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 architecture design model |
The structure of the system. The internal system architecture is defined by the ability to distribute logically isolated processing tiers on different physical platforms. Examples are: • 1-tier Standalone – Microsoft Word, single platform Access database applications, UNIX character-based applications with console user interface • 1-tier Distributed Presentation – Microsoft Word, single platform Access database applications distributed with Citrix, UNIX character-based applications with telnet user interface, single platform UNIX application with X-windows user interface • 1-tier Other – Single platform but not standalone or Distributed Presentation (i.e. a Web UI requiring a plug-in for integration at the desktop) • 2-tier Synchronous Client Server – Synchronous, distributed client Access database applications, Informix or Oracle forms application (majority of business logic performed at the client) • 2-tier Replicated Client Server – Replicated Lotus notes or other replication architecture applications (majority of business logic performed at the client) • 2-tier Other– Single platform but not 2-tier Synchronous Client Server or 2-tier Replicated Client Server (i.e. a Web UI requiring a plug-in for integration at the desktop, or thin client with business logic embedded in database layer trigger or stored procedures) • 3-tier Synchronous Data/Business Logic/Presentation – Synchronous applications with logically isolated data, application logic and user interface tiers capable of distribution across multiple physical platforms. E.g. A system component with an Informix database tier, a Java beans application server tier and an HTML user interface tier. • 3-tier Replicated Data/Business Logic/Presentation – Replicated applications with logically isolated data, application logic and user interface tiers capable of distribution across multiple physical platforms. E.g. A system component with an Informix database tier, a Lotus Notes application server tier, and a Lotus Notes client user interface tier using replicated documents or databases. • 3-tier Other – Multiple platform but not 3-tier Synchronous Data/Business Logic/Presentation or 3-tier Replicated Data/Business Logic/Presentation (i.e. a Web UI requiring a plug-in for integration at the desktop, or thin client with business logic embedded in database layer trigger or stored procedures) • 3+tier – Synchronous or replicated applications with logically isolated data, application logic and user interface tiers capable of distribution across multiple physical platforms. E.g. An Informix database tier, a Java beans application server tier, a Java server page presentation logic tier and an HTML user interface tier. |
|
|
|
|
|
|
TBD |
T |
1-tier Distributed Presentation 1-tier Other 1-tier Standalone 2-tier Other 2-tier Replicated Client Server 2-tier Synchronous Client Server 3+tier 3-tier Other 3-tier Replicated Data/Business/Presentation 3-tier Synchronous Data/Business/Presentation Custom Other Unknown NA |
|
|
|
SYSTEM_ |
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 inventory |
SYSTEM-INVENTORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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 types |
SYSTEM-TYPE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
technology score |
Calculated from underlying MBT scoring criteria where type is technology |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
total score |
Calculated from underlying MBT scoring criteria where type is cumulative score from PDAT. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_ |
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
|
Version |
Text that identifies the configuration management version of the System. |
|
|
|
|
|
|
TBD |
F |
Alpha-numeric |
|
|
|
SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
columndefinition |
SYSTEM_ |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
columndefinitionkey1 |
System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
recommendations |
MBT-RECOMMENDATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
rollout/phase |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
rowdefinition |
SYSTEM_ |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
rowdefinitionkey1 |
System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM_/SYSTEM_ |
Upudated via System to System Recommendations matrix. |
F |
F |
F |
columndefinition
columndefinitionkey1
name
recommendations
rollout/phase
rowdefinition
rowdefinitionkey1
status of systems
|
status of systems |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM_/SYSTEM_ |
SYSTEM-ARCHITECTURE |
None |
T |
F |
F |
name
|
name |
Name of the SYSTEM-ARCHITECTURE |
|
|
|
|
|
|
TBD |
F |
Name Description 1-tier Distributed Presentation 1-tier Distributed Presentation – Microsoft Word, single platform Access database applications distributed with Citrix, UNIX character-based applications with telnet user interface, single platform UNIX application with X-windows user interface 1-tier Other 1-tier Other – Single platform but not standalone or Distributed Presentation (i.e. a Web UI requiring a plug-in for integration at the desktop) 1-tier Standalone 1-tier Standalone – Microsoft Word, single platform Access database applications, UNIX character-based applications with console user interface 2-tier Other 2-tier Other– Single platform but not 2-tier Synchronous Client Server or 2-tier Replicated Client Server (i.e. a Web UI requiring a plug-in for integration at the desktop, or thin client with business logic embedded in database layer trigger or stored procedures) 2-tier Replicated Client Server 2-tier Replicated Client Server – Replicated Lotus notes or other replication architecture applications (majority of business logic performed at the client) 2-tier Synchronous Client Server 2-tier Synchronous Client Server – Synchronous, distributed client Access database applications, Informix or Oracle forms application (majority of business logic performed at the client) 3+tier 3+tier – Synchronous or replicated applications with logically isolated data, application logic and user interface tiers capable of distribution across multiple physical platforms. E.g. An Informix database tier, a Java beans application server tier, a Java server page presentation logic tier and an HTML user interface tier. 3-tier Other 3-tier Other – Multiple platform but not 3-tier Synchronous Data/Business Logic/Presentation or 3-tier Replicated Data/Business Logic/Presentation (i.e. a Web UI requiring a plug-in for integration at the desktop, or thin client with business logic embedded in database layer trigger or stored procedures) 3-tier Replicated Data/Business/Presentation 3-tier Replicated Data/Business Logic/Presentation – Replicated applications with logically isolated data, application logic and user interface tiers capable of distribution across multiple physical platforms. E.g. A system component with an Informix database tier, a Lotus Notes application server tier, and a Lotus Notes client user interface tier using replicated documents or databases. 3-tier Synchronous Data/Business/Presentation 3-tier Synchronous Data/Business Logic/Presentation – |
|
|
|
SYSTEM-ARCHITECTURE |
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
|
bi-directional |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
data entities |
List of ENTITY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
description |
Any further description of the Role (Org or Person) as noted |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
from system_ |
The system interfacing from |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
from version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
initiator |
Initiator List |
|
|
|
|
|
|
TBD |
T |
Source Target Neither NA Unknown |
|
|
|
SYSTEM-INTERFACE |
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
|
joint it security requirements |
For AVG use only default F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
moa or mou complete |
For AVG use only defalut F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
name |
Name of the SYSTEM-INTERFACE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
operational frequency |
Operational Frequency List |
|
|
|
|
|
|
TBD |
T |
Daily Daily+ Weekly Bi-Weekly Monthly Monthly+ Real-time Other NA Unknown |
|
|
|
SYSTEM-INTERFACE |
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
|
operational mode |
Operational Mode List |
|
|
|
Unknown |
|
|
TBD |
T |
Batch Interactive Manual NA Unknown |
|
|
|
SYSTEM-INTERFACE |
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
|
to system_ |
The system interfacing from |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
to version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
type |
Interface Type List from AVG |
|
|
|
Interface |
|
|
TBD |
T |
Interface Interconnected Interdependant Information Sharing NA Unknown |
|
|
|
SYSTEM-INTERFACE |
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
|
written approval for esbablishing connection |
For AVG use only default is F. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INTERFACE |
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
|
508 compliance |
|
|
|
|
F |
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
additional names |
The full name of the system that is being monitored or tracked for architectural or investment purposes by the DOI |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
architectural status |
Architectural Status LIst. |
|
|
|
As Is |
|
|
TBD |
T |
As Is To Be Both NA Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
business focus areas |
A name representing the a grouping or categorized functionality performed by the DOI. This concept can be found within the BRM where the focus area can be seen in the context of the entire DOI and more specific detail for the focus area. Also know as a Line of Business (LOB). This will be used to assist in filtering out systems by LOB when creating Target Architectures or other reports along these lines Group 1 - C&A and 300 - Was found in the C&A and 300 list and is not a Business Focus Area System Group 2 - C&A only - Was found only in the C&A list and is not a Business Focus Area System Group 3 - 300 Only - Was found only in the 300 list and is not a Business Focus Area System Group 4 - Fire Management - Classified as a Fire System or found in Master List Group 6 - Financial Management - Classified as a MA Financial System or found in Master List Group 7 - Law Enforcement - Classified as a MA Law System or found in Master List Group 8 - Recreation - Classified as a MA Recreation System or found in Master List Group 90 - Infrastructure Network Enclave Defined as a C&A Network Enclave or an Infrastructure Component Group 91 - GSS Enclave Defined as a C&A GSS Enclave or is a GSS type of System Group 95 - Indian Trust Classified as a Trust System found in Master List Group 98 - Original C&A List Only Only found in original C&A list |
|
|
|
|
|
|
TBD |
F |
VALUE Financial Management VALUE Indian Trust VALUE Law Enforcement VALUE Fire Management VALUE Recreation VALUE Priority - C&A Only VALUE Priority - 300 Only VALUE Priority - C&A and 300 VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
data collection as of date |
Last Date of an update of Data for this System and its detail below |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
data collection status |
Not Populated = Only the System has been identifies as being tracked by DOI Populated = Initial Data collection has been performed, but has not been validated by the customer. Validated = Customer has reviewed and accepted data collection as complete for this system. |
|
|
|
|
|
|
TBD |
F |
VALUE Phase 1 - Not Populated VALUE Phase 1 - Populated VALUE Phase 1 - Validated VALUE Phase 2 - Not Populated VALUE Phase 2 - Populated VALUE Phase 2 - Validated VALUE Phase 3 - Not Populated VALUE Phase 3 - Populated VALUE Phase 3 - Validated |
|
|
|
SYSTEM-INVENTORY |
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
|
department standards |
|
|
|
|
NA |
|
|
TBD |
F |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
financial system type |
|
|
|
|
NA |
|
|
TBD |
F |
VALUE Acquisition (Procurement, Purchasing) VALUE Budget Formulation VALUE Core Financial VALUE Labor Distribution VALUE Executive Information System VALUE Seized/Firfeited Assets VALUE Government-Wide Processing/Information System VALUE Grants VALUE Inventory/Property VALUE Insurance Claim VALUE Guaranteed Loans VALUE Direct Loans VALUE Property Management VALUE Personnel/Payroll - Civilian VALUE Revenue VALUE Inventory (Held or Sale) VALUE Travel VALUE Cost Accounting VALUE Personnel/Payroll - Other VALUE (Benefit Payment VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
financial/mixed |
|
|
|
|
NA |
|
|
TBD |
F |
VALUE Financial VALUE Mixed VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
gao category |
|
|
|
|
Unknown |
|
|
TBD |
F |
VALUE Infrastructure VALUE Software Application VALUE Hardware Trade-out VALUE Other VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
internal description |
Description of Inventory updates including reasons added, removed, updated status, type, etc. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
inventory comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
inventory reasons |
Look up object for reasoning of inventory. Objects: Indian Trust System Major Application Financial Management System General Support System Other System - Associated with Major IT Investment - Exhibit 300 Other System - Associated with Non-Major IT Investment - Exhibit 300-1 Not DOI-Tracked System |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
inventory status |
Current - Live as Inventory Item Pending - Newly added to Inventory Remove - Marked as being removed (Usually associated with Comment for removal, history) Sensitive - Marked as such for systems that will not be further detailed due to the level of sensit |
|
|
|
Current |
|
|
TBD |
F |
Current Pending Remove Sensitive |
|
|
|
SYSTEM-INVENTORY |
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
|
inventory type |
Defines which inventory this system belongs to. |
|
|
|
Department |
|
|
TBD |
F |
Department Bureau External NA Unknown |
|
|
|
SYSTEM-INVENTORY |
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
|
managing partner |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
primary business focus area |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
sensitive system |
If T then the system will not be further attributed. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
sifms |
|
|
|
|
NA |
|
|
TBD |
F |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY |
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 criticality |
|
|
|
|
Unknown |
|
|
TBD |
F |
VALUE Protects Life VALUE Protects Property VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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 internet need |
|
|
|
|
Unknown |
|
|
TBD |
F |
VALUE Requires Internet VALUE Aware of Internet VALUE Not Aware of Internet VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY |
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 id |
The unique identifier that represents the individual system. XXX-YYY-### XXX is the department YYY is the Bureau ### is the Uniquely generated # by Bureau. *Please note that the length of each set of XXX, YYY, and ### is dynamic and not hard-coded. The way to delimit and parse out this ID is by the dashes. Though Acronym in future may be at the beginning of this number, currently acronyms are not consistently used across all DOI Tracked systems to make a standard ID. Other groups or tracking IDs used in others systems can link to this ID as this will become the standard ID at the DOI. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
url |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY |
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
|
owner |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
owner_email |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
owner_phone |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
pia_completed_by |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
pia_completed_by_email |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
pia_completed_by_phone |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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_mgr |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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_mgr_email |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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_mgr_phone |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (CONTACTS) |
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
|
accounting standards |
Type Code Name AccountStanCompl N System does not meet generally accepted accounting standards AccountStanCompl X Not applicable AccountStanCompl Y System meets generally accepted accounting standards |
|
|
|
NA |
|
|
TBD |
T |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
agency information standard |
To be defined by TEA Team |
|
|
|
NA |
|
|
TBD |
T |
VALUE Target VALUE Current VALUE Obsolete VALUE Does Not Meet VALUE Not Available VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
annual transaction volume |
Yearly volumes of transactions as tracked for that system |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
custom development |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
department standards |
|
|
|
|
NA |
|
|
TBD |
T |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
end of life year |
Expected Year the System will end |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
estimated authorized users |
Designed user base (not concurrent, or current, but what was designed for) |
|
|
|
NA |
|
|
TBD |
T |
VALUE Less Than 100 VALUE 100 to 1000 VALUE Greater Than 1000 VALUE Undertermined VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
estimated federal support fte |
To be defined by TEA Team |
|
|
|
NA |
|
|
TBD |
T |
VALUE Less Than 20 VALUE 20 to 100 VALUE Greater Than 100 VALUE Undertermined VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
external reporting |
Supports Reporting outside of Organization (i.e. to Department, to OMB) |
|
|
|
NA |
|
|
TBD |
T |
VALUE Yes VALUE Partial VALUE No VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
financial system id |
Original Identifie as Tracked in Financial Encyclopedia from 5/2003 |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
financial system type |
See values |
|
|
|
NA |
|
|
TBD |
T |
Acquisition (Procurement, Purchasing) Budget Formulation Core Financial Labor Distribution Executive Information System Seized/Firfeited Assets Government-Wide Processing/Information System Grants Inventory/Property Insurance Claim Guaranteed Loans Direct Loans Property Management Personnel/Payroll - Civilian Revenue Inventory (Held or Sale) Travel Cost Accounting Personnel/Payroll - Other (Benefit Payment NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
financial/mixed |
|
|
|
|
NA |
|
|
TBD |
T |
Financial Mixed NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
fmfia |
Type Code Name FMFIAConfStatus X Not applicable FMFIAConfStatus Y Yes, the application is in conformance with FMFIA and has no reported material weaknesses FMFIAConfStatus N No, the application is not in conformance and has reported material weaknesses |
|
|
|
NA |
|
|
TBD |
T |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
gisra |
Type Code Name MeetsGISRA Y Yes, system meets GISRA requirements MeetsGISRA N No, system doesn not meet GISRA requirements |
|
|
|
NA |
|
|
TBD |
T |
Y N NA |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
implementation date |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
information standard date |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
internal reporting |
Supports Reporting within Organization |
|
|
|
NA |
|
|
TBD |
T |
VALUE Yes VALUE Partial VALUE No VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
jfmip required |
Type Code Name JFMIPConfStatus N No, the application is not in conformance JFMIPConfStatus Y Yes, the application is in conformance with JFMIP standards |
|
|
|
NA |
|
|
TBD |
T |
Y N NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
last upgade date |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
number served |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
off the shelf |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
processing |
See Values. |
|
|
|
NA |
|
|
TBD |
T |
VALUE Yes VALUE Partial VALUE No VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
replaced by fbms |
To be defined by TEA Team. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
sgl |
See values. |
|
|
|
NA |
|
|
TBD |
T |
VALUE Fully VALUE Partialy VALUE No Implementation VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
sifms |
|
|
|
|
NA |
|
|
TBD |
T |
Yes No Undetermined NA Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
source |
To be defined by TEA team. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
standard data |
See values |
|
|
|
NA |
|
|
TBD |
T |
VALUE Total Information Architecture VALUE Core Financial Information VALUE Not Expected To VALUE Does Not Meet VALUE Standards Not Available VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
users of service |
see values |
|
|
|
NA |
|
|
TBD |
T |
VALUE External Cross-Servicing VALUE Government Wide VALUE Contractor Owned VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
version number |
The Financial System attribution of Version (where applicable) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (FINANCIAL) |
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
|
egovernment initiative? |
Is the eGovernment initiative (i.e. QuickSilver) or not. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (GOVERNANCE) |
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
|
enterprise |
One of relationship to Enterprise definition. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (GOVERNANCE) |
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
|
gao category |
General categories specified by GAO to identify the following: |
|
|
|
Unklnown |
|
|
TBD |
T |
VALUE Infrastructure VALUE Software Application VALUE Hardware Trade-out VALUE Other VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (GOVERNANCE) |
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
|
section 508 |
Is the System 508 compliant or not. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (GOVERNANCE) |
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
|
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 |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
pia comment |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
pia completed |
If PIA Required, when was PIA Completed? |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
pia required |
Is this PIA required. |
|
|
|
No |
|
|
TBD |
T |
Yes No Undetermined |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
pia_online_form |
If PIA Required, Was an online form used to collect the Privacy Information? |
|
|
|
No |
|
|
TBD |
T |
Yes No Undetermined |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
pia_online_form_omb_number_name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
prelim_pia |
MM/DD/YYYY - All Systems required a Preliminary PIA and date completed |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
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 |
|
|
|
|
SYSTEM-INVENTORY (PRIVACY) |
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
|
artifact not included |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
core trust process |
To be defined by TEA team. |
|
|
|
|
|
|
TBD |
T |
VALUE Accounting VALUE Accounting/ Lease Management VALUE Appraisal VALUE Audit VALUE Beneficiary Services VALUE Cadrastral VALUE Docketing - not valid VALUE Docketing / Probate VALUE Fin AR/AP/GL/Billing/Debt Coll VALUE Lease Management VALUE not provided VALUE Probate VALUE Subsurface resource management VALUE Surface resource management VALUE Title VALUE Trust Record System VALUE Trust support VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
iitd comment |
comment for IITD data selection. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
iitd data |
See values |
|
|
|
NA |
|
|
TBD |
T |
VALUE Houses VALUE Provides Access to VALUE NA VALUe Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
numberr of system users |
To be defined by TEA team. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
questionair returned |
To be defined by TEA team. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
secondary trust system sub category |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
T |
VALUE 1) Land Title Management (determines the status of title) VALUE 2)Conveyance Processing (including Probate Orders) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE 1) Land Title Management (determines the status of title) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
third trust system sub category |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
T |
VALUE 1) Land Title Management (determines the status of title) VALUE 2)Conveyance Processing (including Probate Orders) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE 1) Land Title Management (determines the status of title) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
transaction category |
To be defined by TEA team. |
|
|
|
NA |
|
|
TBD |
T |
VALUE Decommissioned VALUE Legacy VALUE Migration VALUE Steady State VALUE Target VALUE NA VALUe Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
trust system id |
Master Trust System Identified tracked as noted in the Trust Information Resource Catalog managed by the Interior Trust Architecture Team |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
trust system sub category |
To be defined by TEA Team |
|
|
|
|
|
|
TBD |
T |
VALUE 1) Land Title Management (determines the status of title) VALUE 2)Conveyance Processing (including Probate Orders) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE 1) Land Title Management (determines the status of title) VALUE 3)Â Lease (Contract) Management (Encumbrances) VALUE 4) Resource Management Planning VALUE 5) Resource Management VALUE 5a) Resource Management Surface VALUE 5b)Â Resource Management Sub-surface VALUE 6)Â Account Receivable 11) Financial Audits VALUE 7)Â Accounting Disbursement VALUE 8)Â Appraisal VALUE 9) VALUE 10d)Â GIS/Resource inventory and management VALUE 10f)Â GIS/ Land Information Systems VALUE 11) Financial Audits VALUE 12) Program Compliance Monitoring VALUE 13)Â Reconciliation VALUE 14) Beneficiary Services VALUE 15) VALUE 16) VALUE 17) Investigation Analysis/Investigation Management VALUE 18)Â Royalty Data Management VALUE 19) VALUE 20)Â Case Analysis/Management (ClS, Appraisal, and other Tracking systems VALUE 21)Â Mandate Management (access to rules, orders, regulations, statutes and other legal mandates) VALUE 22) Service Request VALUE 23)Â Trust Records Archiving VALUE NA VALUE Unknown |
|
|
|
SYSTEM-INVENTORY (TRUST) |
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
|
architectural status |
The architectural status of the BUSINESS-FOCUS/ISSUE - i.e. As-Is, To-be, etc. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-NODE |
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
|
Delete |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-NODE |
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
|
name |
Name of the SYSTEM-NODE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-NODE |
SYSTEM-PLATFORM |
THE COLLECTION OF HARDWARE AND SOFTWARE USED BY A SYSTEM. |
F |
F |
F |
SYSTEM-PLATFORM DESCRIPTION TEXT
|
SYSTEM-PLATFORM DESCRIPTION TEXT |
THE DESCRIPTION OF A SYSTEM-PLATFORM, INCLUDING OPERATING CHARACTERISTICS, HARDWARE, SOFTWARE, STORAGE, AND ANY ADDITIONAL UNIQUE SERVICES OR CONSTRAINTS. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-PLATFORM |
SYSTEM-TYPE |
Look up table for system type. |
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
SYSTEM-TYPE |
TAA-CATEGORY |
TBD |
T |
F |
F |
name
|
name |
Name of the TAA-CATEGORY |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CATEGORY |
TAA-CRITERIA |
TBD |
T |
F |
F |
name
type
|
name |
The name will be a concatonation of the type, level, and name. Example P1 Business Processes Supported - Low |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA |
TAA-CRITERIA |
TBD |
T |
F |
F |
name
type
|
type |
This is the type of TAA criteria. It will either be Process, Data, Application or Technology |
|
|
|
|
|
|
TBD |
T |
P D A T |
|
|
|
TAA-CRITERIA |
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
|
name |
Name of the TAA-CRITERIA/SYSTEM Relationship - typically not unique or specific since the relationship is what defines this definition |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA/SYSTEM |
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
|
rationale |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA/SYSTEM |
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
|
score |
The score related to the TAA-CRITERIA/SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA/SYSTEM |
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
|
system |
The system related to the TAA-CRITERIA/SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA/SYSTEM |
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
|
system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-CRITERIA/SYSTEM |
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
|
bea tactical solution - cost estimate |
BEA Team Recommended Tactical Solution Cost Estimate - (Man-Weeks) $$$ = 40-100 Man-weeks, $$ = 12-40 Man-weeks, $ = 2-12 Man-weeks |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
bea tactical solution - level of effort |
BEA Team Recommended Tactical Solution Level of Effort - (Man-Weeks) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
business case |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
fy(04) o&m funding |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
name |
Name of the TAA-RECOMENDATION |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
planning period |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
protfolio manager prioritization |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION |
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
|
recomendation type |
TBD |
|
|
|
|
|
|
TBD |
T |
Strategic Tactical NA Unknown |
|
|
|
TAA-RECOMENDATION |
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
|
name |
Name of the TAA-RECOMENDATION/SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION/SYSTEM |
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
|
system |
The system related to the TAA-RECOMENDATION/SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION/SYSTEM |
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
|
system version |
The System Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION/SYSTEM |
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
|
taa recomendation |
The taa recomendation related to the TAA-RECOMENDATION/SYSTEM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION/SYSTEM |
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
|
taa tactical areas |
TBD |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TAA-RECOMENDATION/SYSTEM |
TACTIC |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TACTIC |
TECHNICAL-REFERENCE-MODEL |
The top node of the Technical Reference Model |
T |
F |
F |
child technical service areas
name
|
child technical service areas |
The technical service |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-REFERENCE-MODEL |
TECHNICAL-REFERENCE-MODEL |
The top node of the Technical Reference Model |
T |
F |
F |
child technical service areas
name
|
name |
Name of the TRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-REFERENCE-MODEL |
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
|
best practices |
The best practices required to sustain the TSA |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-AREA |
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
|
comments |
Comment field to support a more complete understanding |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-AREA |
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
|
description |
A text description of relevant Technical Service Area information |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-AREA |
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
|
fea code |
Unique Identifier Code as specified in the FEA Reference Model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-AREA |
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
|
name |
Name of the Technical Service Area |
|
|
|
|
|
|
TBD |
F |
|
|
New |
|
TECHNICAL-SERVICE-AREA |
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
|
skills compositions |
A descriptin of the types of skills required to support the TSA. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-AREA |
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
|
best practice |
The best practices required to sustain the Technical Service Category |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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
|
comments |
Comment field to support a more complete understanding |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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
|
description |
A text description of relevant Technical Category information |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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
|
fea code |
Unique Identifier Code as specified in the FEA Reference Model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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
|
name |
Name of the Technical Service Category |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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
|
skills compositions |
A description of the types of skills required to support the technical service category. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-CATEGORY |
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 area |
Technical tier of the FEA TRM that supports the secure construction, exchange and delivery of business or service components. |
|
|
|
|
|
|
TBD |
F |
Component Framwork Service Access and Deliver Area Service Interface and Integration Service Platform and Infrastructure TRM |
|
New |
|
TECHNICAL-SERVICE-CATEGORY |
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
|
best practices |
The best practices required to sustain the Technical Service Category |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
comments |
Comment field to support a more complete understanding |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
contact information |
The lead point contact to inquire about the technology or product |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
description |
A text description of relevant Technical Category information |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
IPv6 Compliant |
Date of IPv6 Compliance. If blank, not [scheduled to be] compliant |
|
|
|
|
|
|
TBD |
T |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
license explanation |
Text field describing the nature of the agreed upon license for the product or technology |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
license status |
The status of the license that would be required for the product or technology |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
manufacturer |
The manufacturer or supporting of the specification. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
manufacturer upgrade plan |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
name |
The product or technology name |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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 category |
Foreign key that provides filter to TRM to make available only those technology services that are relevant |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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 specification roles |
An identified role associated with the required skills that are used to support this technology standard. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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 |
FEA Technical Service Standards |
|
|
|
|
|
|
TBD |
F |
Application Servers Audio Conferencing Authentication / Single Sign-on Backbone Services Certificates / Digital Signatures Change Management Client component Collaboration Communications Components of (FCAPS) Compression Concentrator Content Rendering Data Exchange Data Format / Classification Data Transformation Data Types / Validation Database Database Connectivity Deployment Management Desktop Desktop Devices Desktop Publishing Desktop Remote Control Desktop Remote Control DHCP Directory Services Distance Learning DNS Drawing Dynamic / Server-Side Display Electronic Mail Embedded Technology Devices Enterprise Application Integration Extranet FAX Firewalls Full General Purpose Routers Hosting Instant Messaging Integrated Development Environment (IDE) Internet Intranet LAN (Local area Network) /Intranet Legislative / Compliance Managed Switches Media Players Media Servers Middleware Modeling Modeling and Analytical Multimedia Network Devices Network Devices / Standards Network Devices/ Standards Network Management Network-to-Network Component Non-Backbone Services NTP Office Automation Online Online meeting services Other Applications Other Electronic Channels Peer to Peer (P2P) Peripherals Platform Dependent (MS) Platform Dependent BL (MS) Platform Independent (J2EE) Platform Independent BL (J2EE) Portal Servers Project Mgmt Radio Radio Readers Reporting and Analysis Routed LAN protocols Routed WAN protocols Routing protocols Servers / Computers Service Description / Interface Service Discovery Service Transport Shared Calendaring Software Configuration Management Special Purpose Routers Specialized room Static Display Storage Supporting Network Services Supporting Security Services Synchronization Telecom based Test Management Threaded Discussions Utilities Video Conferencing Virtual Private Network (VPN) WAN WAN (Wide Area Network) Web Browser Web Filtering Web Servers Web Services Wireless / Mobile / Voice Wireless / PDA Wireless/ Mobile Wiring-Coaxial Wiring-Fiber Optic Wiring-Unshielded Twisted Pair (UTP) zxzzzz |
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
TSS-TYPE |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
Usages |
As defined by CTOC, the classification by the one to many usages for this specification |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-SPEC |
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
|
version |
Text that identifies the configuration management version of the Technice Service Specification, Product, or Standard |
|
|
|
|
|
|
TBD |
F |
1 Null |
|
New |
|
TECHNICAL-SERVICE-SPEC |
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
|
best practices |
The description of the best practices idnetified in the DOI TRM |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
comments |
Free text field describing the Technical Service Standard |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
description |
Description of the Service component |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
fea code |
Unique Identifier Code as specified in the FEA Reference Model. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
name |
Part of the hierarchical (3rd level) description of the FEA model (TRM) that describes hardwar, software or specificaitons that widely used and accepted or sanctioned by standards organizations. Eg. Programming language, Operating System etc… |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
service componets |
Self contained business process or functionality that can be exposed through multiple technologies. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
skills compositions |
A description of the type of skills required to support this type of product or technology standard… |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
technical service category |
Sub tier of the FEA TRM model that classifies lower levels of technologies , standards and specifications with respect to the technology function they serve. |
|
|
|
|
|
|
TBD |
F |
Access-Channels Business-Logic Data Management Database-Storage Data-Interchange Data-Management Delivery-Channels Delivery-Servers Hardware-Infrastructure Integration Interface Interoperability Presentation-Interface Security Service-Requirements Service-Transport Software-Engineering Software-Infrastructure Support-Platforms |
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
technical service specifications |
The Child technical service specifications of this Standard |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECHNICAL-SERVICE-STANDARD |
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
|
description |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-CLASSIFICATION |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-CLASSIFICATION |
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
|
characteristics |
Business or use context (i.e. Enterprise-wide vs. local use, or use with financials only) |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
classification |
required field to denote the classifacation. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
organizations |
If usage is by a specific organization(s), identify which organization this usage applies to |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
platform |
|
|
|
|
NA |
|
|
TBD |
T |
J2EE dotNET Both NA |
|
|
|
TECH-SPEC-USAGE |
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
|
requirements met |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
service components |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
technical service specification |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
technical service specification version |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SPEC-USAGE |
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
|
Person |
The individual's name who is performing the role |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/PERSON-ROLE |
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
|
Role |
Role the individual plays in either managing or supporting the the specification. |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/PERSON-ROLE |
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
|
Role Remarks |
Comment field to support the nature of the role and its responsibility |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/PERSON-ROLE |
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
|
Technical Service Specification |
A formal layout, bluprint or design of an application development model for a distributed component based architecture |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/PERSON-ROLE |
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
|
Version |
Text that identifies the configuration management version of the Technice Service Specification |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/PERSON-ROLE |
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
|
columndefinition |
SYSTEM-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
columndefinitionkey1 |
SYSTEM-COMPONENT Version |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
deployed? |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
rollout/phase |
ROLLOUT-PHASE |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
rowdefinition |
TECHNICAL-SERVICE-SPEC |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
service components |
SERVICE-COMPONENT |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
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
|
suppliers |
SUPPLIER |
|
|
|
|
|
|
TBD |
F |
|
|
|
|
TECH-SVC-SPEC/SCOMPONENT_ |
USER-COMMUNITY |
A category of individuals who interact with a sub-system in a like way and for similar purposes. |
T |
F |
F |
name
|
name |
Name of the USER-COMMUNITY |
|
|
|
|
|
|
TBD |
T |
External Commercial Management External Commercial Staff External Government Management General International Public General U.S. Public Internal Management Internal Staff Unknown |
|
|
|
USER-COMMUNITY |
VISION |
|
T |
F |
F |
name
|
name |
|
|
|
|
|
|
|
TBD |
F |
|
|
|
|
VISION |