Field | Description |
---|---|
Primary Name | Name of the business area. Enter a name that users can recognize easily. |
Description | Description of the business area. |
Parent | Parent name of the business area that you want to create. |
Field | Description |
---|---|
Axon Status | Status of the business area in Axon. You can select one of the following statuses:
|
Lifecycle | Stage of the business area in the production lifecycle. The stages are Operating and Obsolete. |
Axon Viewing | Whether the business area is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Segment | The segment to which you want to assign the business area to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Primary Name | Name of the capability. |
Ref. | ID for the capability. If you leave this field empty, Axon assigns a new reference automatically. |
Description | Description of the capability. |
Parent | Parent of the capability if the capability belongs to a hierarchy. |
Field | Description |
---|---|
Axon Status | Status of the capability in Axon. |
Axon Viewing | Whether the capability is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Lifecycle | Stage of the capability in the approval lifecycle. |
Classification | Classification of the capability that best describes its purpose, for example, Regulatory Capability. The options you see here are predefined in your Axon installation. |
Capability Type | Type of capability that best describes the object. |
Segment | The segment to which you want to assign the capability to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Short name of the client. Enter a name that users can recognize easily. |
Description | Description of the client. |
Long Name | Full name of the client. |
Parent | Parent name of the client that you want to create. |
Field | Description |
---|---|
Axon Status | Status of the client in Axon. You can select one of the following statuses:
|
Lifecycle | Stage of the client in the production lifecycle. The stages are In Production and Obsolete. |
Axon Viewing | Whether the client is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Segment | The segment to which you want to assign the client to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Primary Name | Name of the committee. Enter a name that users can recognize easily. |
Ref | ID for the committee. If you leave this field empty, Axon automatically assigns a new reference identifier. |
Description | Description of the committee. |
Parent | Parent name of the committee that you want to create. |
Field | Description |
---|---|
Axon Status | Status of the committee in Axon. You can select one of the following statuses:
|
Axon Viewing | Whether the committee is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Lifecycle | Stage of the committee in the production lifecycle. The stages are In Effect and Obsolete. |
Classification | Classification of the committee. You can classify a committee as a Core Governance Entity. |
Committee Type | Type of the committee. Select one of the following types:
|
Segment | The segment to which you want to assign the committee to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Name of the data set. You can create several data sets with the same name, if they belong to different systems. |
System | System that the data set belongs to. |
Ref. | Unique identifier for the data set. If you leave this field empty, Axon automatically assigns a reference identifer. |
Definition | Description of the data set. |
Glossary Name | Glossary that the data set is associated with. |
Usage | Additional information about the data set. |
Field | Description |
---|---|
Axon Status | Status of the data set asset in Axon. |
Type | Type of the data set. You can select the following data set types:
The options you see here are predefined in your Axon installation. |
Axon Viewing | Whether the data set should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Lifecycle | Stage of the data set in the governance lifecycle. You can select the following default stages:
|
Segment | The segment to which you want to assign the data set to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Value Update Frequency | The frequency at which you plan to update the list of values. Select one of the following frequencies:
|
Update Frequency Comments | Notes or comments about the frequency at which you plan to update the list of values |
Availability | The method by which you plan to make the list of values available to other applications. Select one of the following methods:
|
Availability Comments | Notes or comments about the availability of the list of values. |
Values in Axon | Select whether the value is part of a complete list of values or a sample representation of values. |
Field | Description |
---|---|
Name | Name of the geographical region or country in which you want to enforce a regulation. |
Parent | Name of the parent geographical region. |
Description | Description of the geographical region. |
Segment | The segment to which you want to assign the geography to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Name of the glossary. |
Definition | Definition of the glossary. |
Ref. | A unique reference identifier for the glossary. If you leave this field empty, Axon automatically assigns a reference identifier. |
Format Type | Format in which the glossary is expressed. You can select the following data types:
|
Alias Names | Alternate names for the glossary. Enter synonyms of the glossary that are commonly used in your organization. |
Format Description | Description of the glossary format. |
LDM Reference | Place of the glossary in a Logical Data Model. |
Business Logic | Business context in which the glossary is used. |
Examples | Contextual examples of the business logic. |
Parent Name | Parent name of the glossary in the glossary hierarchy. |
Field | Description |
---|---|
Axon Status | Status of the glossary in Axon. |
Lifecycle | Stage of the glossary in the approval lifecycle. You can select the following default stages:
|
Axon Viewing | Whether the glossary is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Type | The type of a glossary. You can specify the following types for a glossary:
You can view the type of a glossary in the following areas:
|
Security Classification | Security classification of the glossary. You can select the following security classification options:
The options you see here are predefined in your Axon installation. |
CIA Rating | Confidentiality, Integrity, and Availability (CIA) rating of a glossary. Confidentiality, Integrity, and Availability are crucial elements of security for a glossary.
The CIA rating indicates the security assessment of a glossary. Each of the CIA elements is rated from 1 to 3. You can add a maximum of nine ratings for each element from the Admin panel. The value you select here is a composite rating of all three elements. The CIA Rating list values defined in the Admin panel apply to Glossary and System objects. If the CIA rating ranges from 1 to 3, each digit in the rating has the following indicators:
For example, a rating of 213 has the following indicators:
|
KDE | Indicates whether or not the glossary is a key data element. You can add new key data element values from the Admin panel in addition to the default values, True and False, as necessary. Configure the Glossary KDE settings from Meta-Model Administration > Dropdown Configuration. |
Segment | The segment to which you want to assign the glossary to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Long Name | Full name of the legal entity. |
Short Name | Short name of the legal entity. Enter a name that users can recognize easily. |
Description | Description of the legal entity. |
Parent | Parent name of the legal entity that you want to create. |
Field | Description |
---|---|
Axon Status | Status of the legal entity in Axon. |
Axon Viewing | Whether the legal entity is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Segment | The segment to which you want to assign the legal entity to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Primary Name | Name of the local department, team, or unit. |
Ref. | Reference identifier for the org unit. The reference ID must be a string data type. If you enter a number, you must format the column to Text type. Otherwise, when you bulk upload org unit assets using a template, Microsoft Excel alters the reference ID by deleting trailing zeros. |
Description | Relevant description about the org unit. |
Parent | Parent of the org unit. The parent record must exist in Axon before you create an org unit asset. |
Axon Status | Status of the org unit object in Axon. |
Field | Description |
---|---|
Name | Name of the policy. Enter a name that users can recognize easily. |
Ref. | ID for the policy. If you leave this field empty, Axon assigns a new reference automatically. |
Description | Description of the policy. |
Type | Category that best describes the policy. The options you see here are predefined in your Axon installation. If the Axon SuperAdmin has enabled Data Marketplace in the Axon Admin Panel, Policy objects that are related to Data Set objects appear in the Marketplace data collections. For more information, see the Axon Data Governance 7.1 Data Marketplace User Guide. Note: To specify a Policy object as a data collection usage guide, create a policy with the EULA_Information or EULA_Confirmation type. If the Type field does not display the EULA_Information or EULA_Confirmation value, contact the Axon SuperAdmin to create new dropdown values. For more information, see the Axon Data Governance 7.1 Administrator Guide. |
Internal | Whether the policy is internal or external. |
URL | Link to another page where the policy is mentioned in detail. Include the network protocol in the link. For example, enter https://www.website.com. |
Parent | Parent of the policy if the policy belongs to a hierarchy. |
Security or Classification Policy Reference | The name of the Data Privacy Management policy that you want to link to the Axon policy. You can select a security or classification policy. |
Field | Description |
---|---|
Effective Date | Date from which the policy is effective. When you bulk upload policy assets from a Microsoft Excel file, sometimes, Microsoft Excel converts the date into number of days. To prevent this, enter a single quote before the date. For example, enter March 20, 2017 as '20-03-2017 in Microsoft Excel. |
End Date | Date after which the policy ceases to be effective. When you bulk upload policy assets from a Microsoft Excel file, sometimes, Microsoft Excel converts the date into number of days. To prevent this, enter a single quote before the date. For example, enter March 20, 2017 as '20-03-2017 in Microsoft Excel. |
Axon Status | Status of the policy asset in Axon. |
Lifecycle | Stage of the policy in the approval lifecycle. |
Axon Viewing | Whether the policy should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Segment | The segment to which you want to assign the policy to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Primary Name | Name of the process. |
Ref. | ID for the process. If you leave this field empty, Axon assigns a new reference automatically. |
Description | Description of the process. |
Parent | Parent process of the process that you create. After you create a process, you can view the parent name of the process when you hover over the process name regardless of the tab that you are in. |
Input Description | Description of relevant inputs to the process. |
Output Description | Description of relevant outputs from the process. |
Class | Classification of the process. You can select the Execution Process. The options you see here are predefined in your Axon installation. |
Automation | Level of automation.
|
Permissions | Default permission granted to the user for working with the process. |
Duration | The time duration for the process that you create. Choose hours or days as the unit of time. If you want to enter the unit of time in weeks or week days, you can configure the Process Duration Type property from Meta-Model Administration | Dropdown Configurations in the Admin Panel. You can view the specified process duration in a process or context map. |
Field | Description |
---|---|
Axon Status | Status of the process asset in Axon. |
Lifecycle | Stage of the process in the approval lifecycle. |
Type | Indicates whether you create a complete process, a step within a process, or a control within a process. In the Edit mode of a Process object, you can enter a condition text in the Condition column for the Control type processes. The annotation text appears on the output of the Control type process in process maps. |
Step Type | Whether you are creating the starting step of a process, the ending step of a process, or a common step across the process. |
Axon Viewing | Whether the process should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Segment | The segment to which you want to assign the process to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Type | Step Type | Notation in Map | Example |
---|---|---|---|
Step | Starting Step | A block with a green circle () indicates the starting step for a process. | |
Step | Common Step | A plain grey block indicates a common step within a process. | |
Step | Ending Step | A block with a blue circle () indicates the ending step for a process. | |
Process | Starting Step, Common Step, or Ending Step | A block with a plus symbol () indicates that it is a complete process in itself. When the Type value is "Process," the Step Type value is not considered while creating the block. | |
Control | Starting Step, Common Step, or Ending Step | An orange decision box () indicates a decision control step for a process. When the Type value is "Control," the Step Type value is not considered while creating the block. |
Field | Description |
---|---|
Name | Short name of the product. Enter a name that users can recognize easily. |
Description | Description of the product. |
Ref. | A unique reference identifier for the product that you want to create. |
Long Name | Full name of the product. |
Parent | Parent name of the product that you want to create. |
Field | Description |
---|---|
Axon Status | Status of the product asset in Axon. |
Axon Viewing | Whether the product is available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Lifecycle | Stage of the product in the production lifecycle. The stages are In Production and Obsolete. |
Segment | The segment to which you want to assign the product to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Name of the project. Enter a name that users can recognize easily. |
Ref. | ID for the project. If you leave this field empty, Axon assigns a new reference automatically. |
Description | Description of the project. |
Type | Whether you are creating a program or project within a program. The options you see here are predefined in your Axon installation. |
Parent | Parent of the project if the project belongs to a hierarchy. |
Classification | Purpose of the project. You can select from the following classification options:
|
Field | Description |
---|---|
Axon Status | Status of the project asset in Axon. |
Lifecycle | Stage of the project in the project management lifecycle. You can select from the following classification options:
|
Axon Viewing | Whether the project should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
RAG | Status of the project in the project management lifecycle. Select Red, Amber or Green. |
Start Date | Start date of the project. When you bulk upload a project assets from a Microsoft Excel file, sometimes, Microsoft Excel converts the date into number of days. To prevent this, enter a single quote before the date. For example, enter March 20, 2017 as '20-03-2017 in Microsoft Excel. |
End Date | End date of the project. When you bulk upload a project assets from a Microsoft Excel file, sometimes, Microsoft Excel converts the date into number of days. To prevent this, enter a single quote before the date. For example, enter March 20, 2017 as '20-03-2017 in Microsoft Excel. |
Segment | The segment to which you want to assign the project to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Long Name | Full name of the regulation, for example, General Data Protection Regulation. |
Ref | ID for the regulation. |
Description | Description of the regulation. |
Short Name | Short name of the regulation. The most commonly used name or an acronym for the regulation, such as GDPR. Enter a name that users can recognize easily. |
Legal Advice | A description of the legal advice. |
Legal Advice Type | The type of legal advice. Select one of the following legal advice types:
|
Additional Info | Any additional information that provides a context to the regulation. |
Parent | Parent object of the regulation. |
Field | Description |
---|---|
Compliance Level | The current state of the response of the organization to the regulation. Select one of the following compliance levels:
|
Maturity | The level of maturity in understanding and interpreting the regulation. Select one of the following maturity stages:
|
Probability | The extent to which a regulation is probable. Select Confirmed. |
Impact Rating | The level of impact of the regulation on the organization. Select one of the following impact ratings:
|
Status | Status of the regulation in Axon. Select one of the following statuses:
|
Stage | The stage of the organization when a regulation is created or updated. Select one of the following stages:
|
Access Control | Whether or not the regulation needs to be available to public. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before you configure the field to "Non-Public." |
Publication Date | The date of the original publication of the regulation. If a regulation object is manually created and the object is a child of another regulation object, the publication date automatically inherits the value from the parent. |
Compliance Date | The date by when you want to enforce the regulation, for example, 25th May 2018. If a regulation object is manually created and is the child of another regulation object, the compliance date automatically inherits the value from the parent. |
Comments Date | The date by when you want the stakeholders of an organization to provide comments or opinions on the draft regulation. |
Finalisation Date | The date by when you want the stakeholders to submit comments and finalize the regulation. |
Segment | The segment to which you want to assign the regulation to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Full name of the regulator. |
Short Name | Short name of the regulator. The most commonly used name or an acronym for the regulator. Enter a name that users can recognize easily. |
Description | Description of the regulator. |
Segment | The segment to which you want to assign the regulator to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Full name of the regulatory theme. |
Description | Description of the regulatory theme. |
Ref | ID for the regulatory theme. |
Short Name | Short name of the regulatory theme. The most commonly used name or an acronym for the regulatory theme. Enter a name that users can recognize easily. |
Parent | Parent object of the regulatory theme. |
Field | Description |
---|---|
Axon Status | Status of the regulatory theme in Axon. Select one of the following statuses:
|
Segment | The segment to which you want to assign the regulatory theme to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |
Field | Description |
---|---|
Name | Name of the system interface. You can create several interfaces between the same systems. Duplicate names are allowed, but Informatica recommends that you enter a name that is descriptive and unique. |
Ref. | ID for the system interface. If you leave this field empty, Axon assigns a new reference automatically. |
Source System | System or data set from which the information flows out. |
Target System | System or data set to which the information flows in. |
Description | Description of the system interface. |
Synchronization Control | Description of the rules that control the synchronization of information between the two connected interfaces. |
Field | Description |
---|---|
Axon Status | Status of the system interface asset in Axon. |
Axon Viewing | Whether the system interface should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
Lifecycle | Stage of the system interface in the production lifecycle. You can select the following default stages:
|
Automation | Level of automation. You can select the following the automation levels:
|
Frequency | Frequency at which data flows between the source and target system. You can select the following frequencies:
|
Asset ID | ID of the asset. |
Transfer Method | Protocol or medium used to move information between the source and target system. You can select the following methods:
|
Transfer Format | Format or file type used to flow information between the source and target system. You can select the following formats:
|
Interface Classification | Classification of the system interface that best describes its purpose, for example, BAU. The options you see here are predefined in your Axon installation. |
Field | Description |
---|---|
Short Name | Short name of the system. Enter a name that users can recognize easily. |
Description | Description of the system. |
Type | Whether the system is a software application or one of several file types. You also need to specify whether the system is hosted internally inside your organization or externally outside your organization. |
Long Name | Full name or proper name of the system. |
URL | Link to another page where related information is mentioned. Include the network protocol in the link. For example, enter https://www.website.com. |
Parent | Parent process of the system that you create. |
Field | Description |
---|---|
Axon Status | Status of a system in Axon. |
Lifecycle | Stage of the system in the production lifecycle. You can select the following default stages:
|
Axon Viewing | Whether the system should be available for public viewing or not. Axon is meant for public use within your organization. Contact Informatica Global Customer Support before setting this field as Non-Public. |
CIA Rating | Confidentiality, Integrity, and Availability (CIA) rating of a system. Confidentiality, Integrity, and Availability are crucial elements of security for a system.
The CIA rating indicates the security assessment of a system. Each of the CIA elements is rated from 1 to 3. You can add a maximum of nine values to the CIA Rating list using the dropdown configuration in the Admin Panel. The value you select here is a composite rating of all three elements. The CIA Rating list values defined in the Admin panel apply to Glossary and System objects. If the CIA rating ranges from 1 to 3, each digit in the rating has the following indicators:
|
Asset ID | ID for the system. |
Classification | Classification of the system that best describes its function. You can select the Data Warehouse classification. |
Segment | The segment to which you want to assign the system to. This field appears if a SuperAdmin user has created segments in the Admin Panel. |