Capture data for business questions (Simplified)

Data can be most easily collected in the Simplified Data Capture view which allows you to capture data for specific business questions without the need to configure data capture templates. An XLSX file can be generated for each object class that is relevant for a business question. The generated XLSX file only includes columns for the attributes, referenced objects, indicators, and roles that are necessary for the business question. Once you have captured your data in the XLSX file, you can upload it and then check the completeness and quality of your data in the context of a business question. Here you can see immediately the quality of your data and correct any data quality issues.

Go to Data Import > Simplified Data Capture.
Click the filter symbol and select a business question in the Business Question field and click Update. Alternatively you can select a class in the Class field.
The data should be defined in numerical order, starting with the classes that have the smallest numbers displayed in the lower right corner of the boxes. Select an object class and click Generate Data Capture Template File.
Capture the data as described in the section General information about data collection with XLSX files.
Click Data Capture > Upload Data Capture File.
Click Data Capture > Open Data Capture Status Report to check the success of your data import.
Change to the Portfolio Manager user profile and go to the business question that you are capturing the data for to check the data quality of the business question.

Data requirements for "Who is responsible for our assets?"

This business question enables your company to understand the users and organizations that have a functional role defined for the assets in the IT portfolio.

To have meaningful data for the business question Who is responsible for our assets?, you must import and capture the following information about the assets in the repository as well as the persons or organizations that have a role defined for the asset in your company:

Class	Explanation
Assets	An asset can be based on any of the following classes: Application, Application Group, Business Capability, Business Data, Business Process, Component, Data Category, Information Flow, IT Capability, Location, Organization, Physical Server, Vendor, Virtual Server
Role	A role references the asset, the responsible person or organization, and the role type that the role is based on.
Role Type	Role types are preconfigured by Software GmbH. Your company can also configure role types. Role types are only available for objects of the object class that the role type is assigned to. The following preconfigured role types are available: Application Manager: A person who is the subject matter expert for the application from a functional and technical point of view. Architect: A person who is responsible for the governance of the asset. Asset Owner: A person or organization that legally owns the asset. These users and organizations are responsible for making asset allocation decisions based on strategic and operational objectives. Business Owner: A person or organization that owns the asset and is responsible for managing the functional requirements. Capability Owner: A person who is responsible for the asset. IT Owner: A person or IT organization that owns the asset and is thus typically responsible for approval decisions. Operations: An IT organization responsible for the operation of the asset. Project Manager: A person who is responsible for planning, organizing, managing, and executing projects from beginning to end including the project's budget, resources, and scheduling. Staffing Manager: A person who is responsible to allocate and balance the human resources required for a project. Stakeholder: A person or organization that has an interest in the asset and therefore requires read-only access permissions.
Person	The user that is responsible for the asset.
Organization	The organization that is responsible for the asset.

Data requirements for "What should we be focusing on?"

This business question identifies the applications, the business capabilities and their business relevance, and the number of applications associated with the business capabilities in the as-is and to-be landscapes.

To have meaningful data for the business question What should we be focusing on?, you must capture the following information about the applications and business capabilities in your company. This business question requires the availability of at-least 2 levels of business capabilities in your portfolio.

Class	Attribute	Mandatory	Explanation
Application	Start Date	x	The start date is the date when the application is actively used.
	End Date	x	The end date is the date when the application is no longer used.
	Recommendation	x	The strategic recommendation regarding future investment for the application.
	Strategic Application	x	Indicates whether the application is strategic for the business.
Business Capability	Level ID		The hierarchical number of the business capability in the business capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc. Necessary for the visualization.
	Name		Necessary for the visualization.
	Business Relevance	x	Indicates how relevant the business capability is for the business: Business capabilities that are relevant for the business have the value Mission Critical or Business Evolving. Business capabilities that are not relevant for the business have the value Business Enabling or Business Operating.
	Parent Business Capability	x	Every business capability on the second level of the hierarchy and lower should have a parent business capability defined. This enables the aggregation of applications that provide a lower-level business capability up to the second-level business capability.
	Application		One or more applications that provide the business capability.

Data requirements for "What are our technology standards?"

This business question helps to assess whether components are aligned with the standards catalog to support the company's IT capabilities.

To have meaningful data for the business question What are our technology standards?, you must capture the following information about the components and IT capabilities in your company.

Class	Attribute	Mandatory	Explanation
Component	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Standardization	x	Indicates whether the component is a standard component. A component will be colored based on the Standardization setting.
	IT Capability	x	Components are assigned to the IT capabilities they support.
IT Capability	Level ID		The hierarchical number of the IT capability in the IT capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc. Necessary for the visualization.
	Name		Necessary for the visualization.
	Parent IT Capability		The parent IT capability relationship is used to aggregate components assigned to a lower-level IT capability to the second-level IT capability in the IT capability hierarchy.
Local Component	Application		The local component is used by the application it belongs to.
	Component		The local component is derived from a component.

Data requirements for "Who owns which applications?"

This business question focuses on the roles Business Owner and IT Owner in the company and examines which organizations have responsibility for applications. The best-practice recommendation is that a business owner and IT owner are documented for every application.

To have meaningful data for the business question Who owns which applications?, you must import and capture the following information about the applications and organizations in your company:

Class	Attribute	Mandatory	Explanation
Application	business owner (Organization)	x	The business owner is an organizational role for applications.
	IT owner (Organization)	x	The IT owner is an organizational role for applications.
Organization	Name		The Name defines the segments in the doughnut charts
	parent (Organization)		The parent relationship is used to roll-up all applications owned by a lower-level organization up to the second level organization shown in the report.

Data requirements for "What are our most important projects?"

This business question examines all projects including their lifecycle information, current year budget, architecture impact, business value, and project risk.

To have meaningful data for the business question What are our most important projects?, you must capture the following information about the projects in your company.

Class	Attribute	Mandatory	Explanation
Project	ID
	Name
	Start Date		The date that the project starts.
	End Date	x	The date that the project ends.
	Status	x	The approval status of the project.
	Project Risk	x	An evaluation based on project duration, team size, and technology adoption indicators.
	Business Value	x	An evaluation based on cost saving, market opportunity, and strategic value indicators.
	Architectural Impact	x	An evaluation based on complexity reduction, innovation, and standards conformity indicators.
	Monitoring Budget	x	Project monitoring KPI to ensure that the project is within budget.
	Monitoring Resource	x	Project monitoring KPI to ensure that the project is within the resource allocation.
	Monitoring Time	x	Project monitoring KPI to ensure that the project is on time.
Project Group	Name

Data requirements for "What is the status of our project portfolio?"

This business question provides and overview of the project time schedule including milestones and project dependencies.

To have meaningful data for the business question What is the status of our project portfolio?, you must capture the following information about the projects in your company.

Class	Attribute	Mandatory	Explanation
Project	ID
	Name
	Start Date		The date that the project starts.
	End Date	x	The date that the project ends.
	Status	x	The approval status of the project.
Project Group	Name

Data requirements for "What is our application portfolio?"

This business question examines the application portfolio. The visualization is a master list of all applications and their attributes and relationships to other aspects of the IT architecture.

To have meaningful data for the business question What is our application portfolio?, you must capture the following information about the applications in your company.

Attribute	Mandatory	Explanation
Name	x
Short Name		The short name can be used in diagrams where space is limited.
Version	x
Description	x
Object State		Indicates whether the application is planned, currently active, or retired.
State Date		The start date is the date when the application is actively used.
End Date		The end date is the date when the application is no longer used.
Object State	x	Describes the operational status of the application and indicates whether it is actively used, planned to be used, or has been used in the past. The application's start and end dates indicate the planned period of activity for the object. Therefore, object state should be changed from Plan to Active once the start date is reached.
Status	x	Specifies the approval status of an application and determines whether or not the application can be edited or deleted.
Architecture Type	x	The architecture type of the application: Possible values are: Client-Server: Applications that divide tasks or workloads between the providers and consumers of a resource or service. Cloud-Based: An application that runs on SaaS cloud environments. The cloud infrastructure could be local or remote to the organization. Distributed: Applications that run on multiple computers within a network. The network boundary can extend from private intranets to public clouds. External Webpage: An external resource represented through a web link. Mainframe: Applications used by large organization to carry out critical processing tasks such as bulk processing of data, transactions, planning or statistical activities. Stand-Alone: A self-contained application, that does not rely on external entities to complete a task. Unknown: The architectural type has not yet been assessed.
Development Type	x	The application development type. Bespoke: An application created specifically to address a unique use case. COTS - Configured: A commercial off-the-shelf application that has been configured or supports configuration to fulfill the requirements of the enterprise and is fully supported and upgrade-stable. COTS - Customized: A commercial off-the-shelf application that is customized or contains organization-specific code/programming to suit the requirements of the enterprise. Unknown: The application development type has not yet been assessed.
Authentication	x	The authentication used in the application. Autonomous: The application supports autonomous methods such as Direct Autonomous Authentication (DAA) for authentication. This can be carried out through mobile or remote authentication systems. Basic Access: The applications support basic authentication based on a username and password. Protocols and layers such as HTTPS, SSL. or TLS could be used to enhance security but these are not mandatory. Multi-Factor: The application requires more than one method of authentication from independent verification sources to verify the transactional identity. Multi-Factor & SSO: The application supports both multi-factor authentication (MFA) and single sign-on (SSO) authentication methods. No Authorization: The application does not support authentication. Single Sign-On: The application supports the use of a single ID and password to gain access to several related or unrelated systems. Unknown: The authentication mode has not yet been assessed.
Alias		A unique suffix used to identify this application.
Recommendation	x	The strategic recommendation regarding future investment for the application. Possible values are: Tolerate: Invest in the application Invest: Consider the application as a migration candidate Migrate: Sundown the application Eliminate: Discontinue the application
Strategic	x	Indicates whether the application is strategic for the business.
Confidentiality	x	KPI
Integrity	x	KPI
Availability	x	KPI
Current Lifecycle Phase		Generated value based on application's lifecycle phases and the current date.
Lifecycle	x	An application lifecycle describes the different phases of the planned schedule of the application. The lifecycle phases are Plan, Pilot, Production, Sunset, and Retired. The active period of the application is the time between the application's start and end date. Each lifecycle phase is aligned with the proceeding and succeeding lifecycle phase that has been defined. Typically, the object state is set to Active during the lifecycle phase Production.
1 SW License Cost 1 SW License Cost 2 SW Maintenance Cost 3 Infrastructure Cost 4 Service Cost 5 OpEx Other	x	Current year operational expenditure
Predecessor Application		The previous application version.
Successor Application		The next application version.
Application Manager, Architect, Business Owner, IT Owner and Stakeholder	x	A user can have one of these roles or a custom role added by your company. A business owner or IT owner must be specified for either a person or organization for an application.
Business Owner, IT Owner, Operations, and Stakeholder	x	An organization can have one of these roles or a custom role added by your company. A business owner or IT owner must be specified for either a person or organization for an application.
Business Process		The business processes that the application supports.
Business Capability (Supported)	x	The business capabilities that the application provides.
Business Capability (Using)		The business capabilities that use the application.
Organization (Using)	x	The organizations that use the application.
Application Group		The application groups that the application is assigned to.
Components	x	The components that help provide the application.
Vendor		The vendors that indirectly provide the application via the components that the vendor provides.
Virtual Server, Physical Server	x	The virtual and physical servers that the application runs on. This is an indirect reference via the deployment
Location		The location of the application based on the location of the physical/virtual server that it runs on.
upstream (Application)	x	Indirect Reference via Incoming Information Flow
downstream (Application)	x	Indirect Reference via outgoing Information Flow
Business Data	x	The business data that is used by the application and transferred via its information flows.

Data requirements for "What is our technical debt?"

This business question allows you to understand the dependence of the applications on components based on component and application lifecycles so that you can act on your technical debt before the application or component goes out of service.

To have meaningful data for the business question What is our technical debt?, you must capture the following information about the applications and components in your company.

Class	Attribute	Mandatory	Explanation
Application	Name
	Version
	Start Date		The start date is the date when the application is actively used.
	End Date	x	The end date is the date when the application is no longer used.
	Strategic Application		Indicates whether the application is strategic for the business.
	Lifecycle		The active period of the application is the time between the application's start and end date. The lifecycle conflict occurs if the component end date is before the application end date.
Local Component	Application	x	The local component is used by the application it belongs to.
	Component		The local component is derived from a component.
Component	Name		The Name and Version are shown in the Name column.
	Version
	Object State		Indicates whether the component is planned, currently active, or retired. Retired components are not displayed in the report.
	Start Date		The start date is the date when the component is actively used.
	End Date	x	The end date is the date when the component is no longer supported.
	Strategic Component		Indicates whether the component is strategic for the business.
	Lifecycle

Data requirements for "Who are our vendors?"

This business question offers insight about your vendors and how they impact the components, supported business capabilities, and applications relevant to your IT portfolio.

To have meaningful data for the business question Who are our vendors?, you must capture the following information about the applications, business capabilities, components, and vendors in your company. It is recommended that application data is complete and that the application's information flows and the business data they transfer as well as the components that the applications use are captured.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Object State		Describes the operational status of the application. Applications with a retired object state are ignored.
Business Capability	Level ID		Indicates the hierarchical number of the business capability in the business capability hierarchy.
	Name
	Business Relevance	x	Indicates how relevant the business capability is for the business.
	Application	x	Application providing the business capability
Local Component	Application		The local component is used by the application it belongs to.
	Component		The component that the local component is derived from.
Component	Name
	Version
	Object State		Describes the operational status of the component.
	Lifecycle	x	The component lifecycle begins with the start date and concludes with the end date.
	Vendor	x	The vendor providing the component.
Vendor	Name		This is necessary for the visualization.

Data requirements for "What are our architectural dependencies?"

This business question examines the dependencies that applications have to other applications based on their information flows.

To have meaningful data for the business question What are our architectural dependencies?, you must capture the following information about the applications and information flows in your company.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Object State		Indicates whether the application is planned, currently active, or retired.
Information Flow	Name		The name is displayed as a tooltip for the information flows.
	Connection Method		A connection method describes the mode of transfer used by a specific information flow to transfer business data between the two associated applications or their respective components. Preconfigured connection methods include: Middleware, P2P, Other
	Connection Frequency		A connection frequency describes how often a specific information flow is used to transfer business data between the two associated applications or their respective components. Preconfigured connection frequencies include: Hourly, Daily, Weekly, Monthly, Quarterly, Yearly, Real Time, On Demand, Other
	Source Application	x	An information flow requires an application that is the source of the connection.
	Target Application	x	An information flow requires an application that is the target of the data exchange.

Data requirements for "What is our project budget?"

This business question provides an overview of your projects and their costs.

To have meaningful data for the business question What is our project budget?, you must capture the following information about the projects in your company.

Class	Attribute	Mandatory	Explanation
Project	ID
	Name
	Software License Cost		The costs for software license for the project.
	Software Maintenance Cost	x	The costs to maintain software license for the project.
	Infrastructure Cost	x	The costs to deploy IT assets for the project.
	Service Cost	x	Other service costs in addition to the maintenance costs.
	OpEx Cost	x	The operating expenditures for the project.
	Year		The project cost per year.
Project Group	Name

Data requirements for "What are our investment and retirement candidates?"

This business question focuses on applications on multiple dimensions in the context of a TIME ( Tolerate, Invest, Migrate, Eliminate ) quadrant.

To have meaningful data for the business question What are our investment and retirement candidates?, you must capture the following information about the applications, business capabilities, organizations, application groups, information flows, and components in your company.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Start Date	x	The start state contributes to the technical score of the application.
	Recommendation	x	The strategic recommendation regarding future investment for the application. The recommendation is compared with the calculation of the business and technical scores. Possible values are: Tolerate: Invest in the application Invest: Consider the application as a migration candidate Migrate: Sundown the application Eliminate: Discontinue the application
	Architecture Type	x	Specifies the architecture of the application. The Architecture Type contributes to the application's technical score. Possible values are: Client-Server: Applications that divide tasks or workloads between the providers and consumers of a resource or service. Cloud-Based: An application that runs on SaaS cloud environments. The cloud infrastructure could be local or remote to the organization. Distributed: Applications that run on multiple computers within a network. The network boundary can extend from private intranets to public clouds. External Webpage: An external resource represented through a web link. Mainframe: Applications used by large organization to carry out critical processing tasks such as bulk processing of data, transactions, planning or statistical activities. Stand-Alone: A self-contained application, that does not rely on external entities to complete a task. Unknown: The architectural type has not yet been assessed.
	Development Type	x	Specifies whether the application is a bespoke or commercial off-the-shelf application. The Development Type contributes to the application's technical score. Possible values are: Bespoke: An application created specifically to address a unique use case. COTS - Configured: A commercial off-the-shelf application that has been configured or supports configuration to fulfill the requirements of the enterprise and is fully supported and upgrade-stable. COTS - Customized: A commercial off-the-shelf application that is customized or contains organization-specific code/programming to suit the requirements of the enterprise. Unknown: The application development type has not yet been assessed.
	Number of Users	x	Indicator specifying the number users of the application. Contributes to the application's business score. 0: 0 1: 1-10 2: 11-100 3: 101-1.000 4: 1.001-10.000 5: >10.000
	1 SW License Cost 2 SW Maintenance Cost 3 Infrastructure Cost 4 Service Cost 5 OpEx Other	x (all)	The application's current year total operational expenditure (OpEx) is defined as the sum of the application costs for the current year.
	Business Owner and IT Owner	x	The roles business owner and IT owner must be specified for either a person or organization for an application.
	Organization (Using)	x	The number of organizations using the application. Contributes to the business score.
Business Capability	Level ID		The hierarchical number of the business capability in the business capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc.
	Name		Necessary for the visualization
	Business Relevance	x	Indicates how relevant the business capability is for the business. Contributes to the business score. Business capabilities that are relevant for the business have the value Mission Critical or Business Evolving. Business capabilities that are not relevant for the business have the value Business Enabling or Business Operating.
	Application	x	Application providing the business capability
Information Flow	Object State		Describes the operational status of the information flow. Information flows with a retired object state are ignored.
	Source Application, Target Application	x	An information flow requires an application that is the source and target of the connection. The number of information flows for which the application is the source or target contributes to the technical score.
Local Component	Application	x	The local component associates the component it is derived from with the application it belongs to.
	Component		The component that the local component is derived from.
Component	Object State		Describes the operational status of the component. Components with a retired object state are ignored.
	Lifecycle	x	The earliest end date of the lifecycle phase Manufacturer Extended Support of all components assigned to applications via local component is used to calculate the Vendor Support Lifespan indicator. The Vendor Support Lifespan indicator contributes to the technical score.

Data requirements for "What are our cost drivers?"

This business question focuses on the costs of the business capabilities based on the operational expenses of the applications that support them.

To have meaningful data for the business question What are our cost drivers?, you must capture the following information about the applications and business capabilities in your company.

Class	Attribute	Mandatory	Explanation
Application	1 SW License Cost 2 SW Maintenance Cost 3 Infrastructure Cost 4 Service Cost 5 OpEx Other	x (all)	The application's current year total operational expenditure (OpEx) per business capability is defined as the sum of the application costs for the current year divided by the number of provided business capabilities (equal cost distribution). This contributes to the size of the level 2 business capabilities.
Business Capability	Level ID		The hierarchical number of the business capability in the business capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc. Necessary for the visualization.
	Name		Necessary for the visualization.
	Business Relevance	x	Indicates how relevant the business capability is for the business: Business capabilities that are relevant for the business have the value Mission Critical or Business Evolving. Business capabilities that are not relevant for the business have the value Business Enabling or Business Operating.
	Parent Business Capability		Every business capability on the second level of the hierarchy and lower should have a parent business capability defined. This enables the aggregation of applications that provide a lower-level business capability up to the second-level business capability.
	Application	x	The application providing the business capability.

Data requirements for "What is our roadmap?"

This business question provides an overview of the application roadmap and allows you to understand lifecycles of the applications including when they will be implemented or reach end-of-life.

To have meaningful data for the business question What is our roadmap?, you must capture the following information about the applications in your company.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Start Date		The start date is the date when the application is actively used.
	End Date	x	The end date is the date when the application is no longer used.
	Lifecycle	x	An application lifecycle describes the different phases of the planned schedule of the application. The lifecycle phases are Plan, Pilot, Production, Sunset, and Retired. The active period of the application is the time between the application's start and end date. Each lifecycle phase is aligned with the proceeding and succeeding lifecycle phase that has been defined. Typically, the object state is set to Active during the lifecycle phase Production.
	Strategic Application		Indicates whether the application is strategic for the business.
	Predecessor Application		All predecessor applications of a selected application are shown.
	Successor Application		All successor applications of a selected application are shown. The successor relations are visualized as black vertical arrows starting with the predecessor's end date and pointing to the successor application.

Data requirements for "What is our landscape?"

This business question provides insights to the business capabilities, their dependencies, and the applications providing functional support to the business capabilities.

To have meaningful data for the business question What is our landscape?, you must capture the following information about the applications and business capabilities in your company. This business question requires the availability of at-least 2 levels of business capabilities in your portfolio.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	Start Date	x	The start date is the date when the application is actively used.
	End Date	x	The end date is the date when the application is no longer used.
	KPI		The KPI to be displayed can be any indicator type as configured in the application class configuration. The KPI to be used for coloring is any criteria as configured in color rules.
Business Capability	Level ID		The hierarchical number of the business capability in the business capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc. Necessary for the visualization.
	Name		Necessary for the visualization.
	Business Capability		Every business capability on the second level of the hierarchy and lower should have a parent business capability defined. This enables the aggregation of applications that provide a lower-level business capability up to the second-level business capability.
	Application	x	One or more applications that provide the business capability.

Data requirements for "What is our target architecture?"

This business question looks at the business support provided by applications to business capabilities and the organizations that use the applications.

To have meaningful data for the business question What is our target architecture?, you must import and capture the following information about the applications, business capabilities, organizations and business supports in your company:

Class	Attribute	Mandatory	Explanation
Application	Name		The Name and Version of the application that is related to the business support is shown in the cells of the matrix.
	Version
	KPI		The KPI to be used for coloring is any criteria as configured in color rules.
	Start Date		The application can be filtered by Start - and End Date using the Active Date filter to generate a snapshot at a point in time.
	End Date
Business Capability	Level ID		The Level ID and Name is shown on the X-Axis.
	Name
	parent (Business Capability)		The parent relationship is used to roll-up the X-Axis as defined in the filter.
Organization	Name		The Name is shown on the Y-Axis.
	parent (Organization)		The parent relationship is used to roll-up the Y-Axis as defined in the filter.
Business Support	Start Date		The business supports shown in the matrix can be filtered by Start - and End Date, Status and by Relevance Group.
	End Date
	Status
	Relevance Group
	used by (Business Capability)	x	The business support relates the using organization with the used application to the used business capabilities.
	used by (Organization)	x
	used by (Application)	x

Data requirements for "How will IT failure impact our business?"

The business question How will IT failure impact our business? provides a high-level end-to-end view of your IT technology landscape. This offers insight to which business capabilities will fail if servers and applications go offline.

To have meaningful data for the business question How will IT failure impact our business?, you must capture the following information about the business capabilities, applications, physical servers, virtual servers, and locations relevant for this business question in your company.

Class	Attribute	Mandatory	Explanation
Business Capability	Level ID		The hierarchical number of the business capability in the business capability hierarchy. For example: 1, 1.1, 1.1.1, 1.2, 1.2.1, etc.
	Name		Necessary for the visualization.
	Application	x	The application supporting the business capability.
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
Virtual Server	Name		Necessary for the visualization.
	Physical Server	x	A virtual server runs on a physical server.
Physical Server	Name		Necessary for the visualization.
	Location	x	The location where the physical server is deployed.
Location	Name		Necessary for the visualization.
	Location		The parent location indicates where a location can be found and serves as the full location name.

Data requirements for "Where do we use sensitive data?"

This business question examines the application portfolio and the business data that is created, read, updated, or deleted by your applications.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
Business Data Usage	Create	x	CRUD value that describes that an application creates a referenced business data.
	Read	x	CRUD value that describes that an application reads a referenced business data.
	Update	x	CRUD value that describes that an application updates a referenced business data.
	Delete	x	CRUD value that describes that an application deletes a referenced business data.
	Application	x	The application that uses the business data.
	Business Data		The business data that is used by the business data.
Business Data	Name		Necessary for the visualization.
	Data Classification	x	The classification of the business data based on confidentiality issues.

Data requirements for "What are our cloud focus areas?"

This business question provides a top-down portfolio analysis for cloud migration in order to understand the applications that are best suited for migration based on cloud relevance and cloud readiness indicators.

To have meaningful data for the business question What are our cloud focus areas?, you must capture the following information about the applications, information flows, business capabilities, and servers in your company.

Class	Attribute	Mandatory	Explanation
Application	Name		Necessary for the visualization.
	Version		Necessary for the visualization.
	End Date	x	The end date of the application is used to calculate the Application End of Life indicators for the cloud readiness score and the cloud relevance score.
	Cloud Migration Strategy	x	The strategy to migrate the application to the cloud. Values include: Retain, Rehost, Rearchitect, Rebuild, Migrated, Unknown
	Architecture Type	x	The architecture type is used to calculate the cloud readiness score. Values include: Unknown, Mainframe, Distributed, Client Server, Stand Alone, Cloud-Based, External Webpage
	Authentication	x	The authentication type is used to calculate the cloud readiness score. Values include: Unknown, Multi-Factor & SSO, Multi-Factor, Client Server, SSO, Bsic Access, Autonomous, No Authorization
	Subject to Compliance Regulation	x	Indicates whether the application is subject to compliance regulations. Used to calculate the cloud relevance score.
	Peaks in the workload	x	Indicator used to contribute to the cloud relevance score.
	License Portability	x	Indicator used to contribute to the cloud relevance score.
	Current Year OpEx	x	The application's current year total operational expenditure (OpEx) is defined as the sum of the application costs for the current year.
Business Capability	Business Relevance	x	Indicates how relevant the business capability is for the business. Contributes cloud relevance score.
	Application	x	Application providing the business capability
Information Flow	Object State		Describes the operational status of the information flow. Information flows with a retired object state are ignored.
	Source Application, Target Application	x	An information flow requires an application that is the source and target of the connection. The number of information flows for which the application is the source or target contributes to the cloud readiness score.
Virtual Server	Physical Server		The virtual server runs on a physical server. Whether the application is running on a virtual server impacts the cloud readiness score.
	Object State		Describes the operational status of the virtual server. Virtual servers with a retired object state are ignored.
Physical Server	Object State		Describes the operational status of the physical server. Physical servers with a retired object state are ignored. Whether the application is running on a physical server impacts the cloud readiness score.

Data requirements for "What is our cloud migration strategy?"

This business question supports the planning of a migration strategy for each application in your cloud portfolio based on an understanding of the impact of migration to business capabilities and the IT ecosystem.

To have meaningful data for the business question What is our cloud migration strategy?, you must capture the following information about the applications in your company. It is recommended that application data is complete and that the application's information flows and the business data they transfer as well as the components that the applications use are captured.

Class Attribute Mandatory Explanation

Application

Name

Version

Cloud Migration Strategy
x
The strategy to migrate the application to the cloud. Possible values include:

Retain: The application supports a business capability for which the Business Relevant indicator is set to Business Enabling or Business Operating and the application cannot be migrated to the cloud immediately. Or the application is at the end of its lifecycle and is about to be retired.

Rehost: The application is SaaS-enabled but is either outdated or would require rehosting to the cloud platform.

Refactor: The application requires some changes in code to be eligible for migration to the cloud. The application can be modular or a self-contained application with services that can easily be refactored.

Rearchitect: The application requires additional effort to make it cloud enabled. For example, this might be due to application health monitoring, application security, data backup and policies, scalability and replication zones, disaster recovery, network utilization, multi-channel communication, or identity management.

Rebuild: The application could be made cloud ready but would require a change in the build process to ensure seamless delivery. The concepts of CI/CD (continuous integration/continuous delivery) could be leveraged for these applications.

Migrated: The application has been migrated to the cloud successfully.

Unknown: The cloud migration strategy is unknown for the application. This may be the case for applications for which the Architecture Type attribute is not set to Cloud-Based.

user

organization

role

asset

application

business capability

component

IT capability

role

organization

application

application

application

component

vendor

component

business capability

application

application

information flow

application

business capability

organization

application group

information flow

component

business capability

application

application

business capability

application

business support

application

business capability

organization

business capability

physical server

application

application

business data

application

application