DOI Glossary - Objects/Attributes

Go Back | Show | Hide | Reset

Information is for official use only - Last update

Export :

DOI Glossary - Objects/Attributes

Count: 1456

Entity Name	Entity Description	IsCoreData	IsSecurityData	IsSensitive	Glossary Model Object Properties	Attribute Name	Attribute Description	DEAR Default Value	Domain if Not Same as Entity	Check if this is a Controlled List	'List Of' Values	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.