Using the Standard FusionGraph Layers

What are the standard FusionGraph Layers, Classifications and Relationships?

Mapping your organisation and what you do within FusionGraph can feel like a daunting task. To help with this, we have developed a standard set of layers that you can use to do this quickly and in a structured way.

The layers are broken down into OrgGraph, FactGraph and PlanGraph sections.

  • OrgGraph: Contextual information about your Organization. For example, Applications, Processes, Locations, Interfaces, Data, Partners, etc.
  • FactGraph: Knowledge (tacit knowledge or explicit knowledge) in the form of ‘facts’ about your current situation. Facts are ‘static’ things like workarounds, ways of working or inefficiencies, etc. and are often in spreadsheets or peoples heads
  • PlanGraph: Activities based on a timeline that represent what you are doing (or may do in the future). Plans represent projects and roadmaps and have a possibility, timeframe and status.

The available data layers provided in the FusionGraph template are as follows:


Layer Name




Used to describe business applications and systems used within the enterprise.

Business Units

Used to describe aspects of the business which perform different functions, or serve particular markets.

Data Entities

Used to describe data objects used within the business.


Describe the hierarchy of regions, countries and locations that the business operates across. Use Global for the top level.


Describe the people and teams that work within the enterprise, and the hierarchical structure.


Used to describe individual interfaces between Applications and Partners.


Describe which partners support the business and who support projects and applications.

Business Processes

Used to describe the hierarchical business process framework that defines business scope.


Used to create a catalogue of reports to measure business performance.


KPIs and measures used to manage performance of the enterprise.


Forms, documents, labels, PDFs and electronic interchange outputs used to communicate with external partners.

Strategic Thrusts

Describe the components of the business strategy.



Capture business problems that need to be solved.


Capture solutions to existing business problems.

Process Controls

Capture controls that are in place to mitigate risks to the business or processes.

Process Risks

Capture risks that could impact the business or processes.


Describe inefficiencies of business processes, classify using the 7 Toyota Wastes (Muda)

Ways of Working

Capture policies and nuances in the way that certain countries perform business processes.


Capture situations where business people are working in non-standard ways.


List of Risks managed and recorded in a RAAIDD log.


List of Issues managed and recorded in a RAAIDD log.


List of Dependencies managed and recorded in a RAAIDD log.


List of Actions managed and recorded in a RAAIDD log.


List of Assumptions managed and recorded in a RAAIDD log.


List of Decisions managed and recorded in a RAAIDD log.


Capture business requirements that need to be delivered as part of the roadmap.

Initiatives Capture business initiatives for campaigns through which goals or visions are to be achieved
Opportunities Capture business opportunities that could deliver value or competitive advantage
Pain Points Describe pain points and issues that need to be addressed

SAP Usage

Current SAP usage normally captured from ST03N data.

SAP Custom Transactions

Catalogue of SAP Custom Transactions.

SAP Custom Programs

Catalogue of SAP Custom Programs.


Catalogue of SAP Remote Function Calls (RFCs).

SAP Query

Catalogue of SAP Queries.



Planned programmes and projects to deliver business and technical improvements.


Application roadmap items that are planned to deliver benefits and improvements.


Expected benefits and improvements to be realized by business programmes.


WRICEFs are Workflows, Reports, Interfaces, Conversions, Enhancements, and Forms. The term is commonly used during SAP projects.

Solution Components

Used in roadmapping to define individual components of a to be solution.

Functionality Assessment Used to record the assessment status of SAP Functionality

Each Standard Layer is delivered with a set of classifications and relationships. You are free to add to these or delete them to make them fit your business.

Layer Classifications Relationships      

Status (Complete, Escalated, In Progress, New)

Mitigate Risks

Resolve Issues


Portfolio (Invest, Maintain, Retire)

Type (Cloud, On-Premise)

Deliver Benefits

Enable Business Processes

Export to Interfaces

Support Roadmap

Support Solution Components

Used by Business Unit


Status (Closed, New, Rejected, Under Review, Validated)

Present Risks


Benefit Type (Hard, Soft)

Gained by Resolving Inefficiencies

Reduce Cost of Business Processes

Relate to Geography

Business Processes

Business Criticality (High, Medium, Low)

Change Impact (High, Medium, Low)

Competitive Advantage (Bottom Line - H, Bottom Line - L, Bottom Line - M, Commodity 0, Top Line - H, Top Line - L, Top Line - M)

Complexity (High, Medium, Low)

Number of Users (Individuals, Multiple Business Units, Organization
Single, Business Unit)

Operational Frequency (High, Medium, Low)

Opportunity for Automation (High, Medium, Low)

Opportunity for Improved Analytics (High, Medium, Low)

Process Efficiency (High, Medium, Low)

Scope Status (In scope S/4HANA, In scope SAP Product Suite, In scope Other, To be confirmed, Out of scope)

Shared Service (High, Medium, Low)

Shared Functionality (High, Medium, Low)

Sustainability Consideration (No, Yes)

Usability for end users (Good, Medium, Poor)

Volume (High, Medium, Low)

Affected by Problems

Enable Strategic Thrusts

Performed by Business Unit

Rely on Data Entities

Suffer from Inefficiencies

Business Unit


In it's Projects
Operates from Geography
Use Business Processes
Data Entities

Data Protection Impact (High Risk, Medium Risk, Low Risk)

Data Type (Master Data, MI Data, Transactional Data)

used in Applications
Decisions Status (Decision Made, Superseded)
Dependencies Status (Agreed, To be Confirmed)
Present Risks
Geographies None
Use Applications
Use Business Processes           
Functionality Assessment None

Assesses Alerts

Assesses Fiori

Assesses Fiori - SAP GUI

Assesses Functionality - New

Assesses Functionality - Changed

Assesses SI - Changed

Assesses SI - Deleted

Inefficiencies Muda (Defects, Inventory, Motion, Over Processing, Over Production, Transportation, Waiting)
Occur in Geographies


Support Business Processes
Alleviate Inefficiencies
Deliver Opportunities
Alleviate Pain Points
Solve Problems

Frequency (Daily, Event-Driven, Hourly, Monthly, On-Demand, Weekly)

Middleware (None, SAP PO/PI, Other)

Criticality (High, Medium, Low)

Impact Business Processes
Send to Partners
Transform Data Entities
Update Applications
Issues Status (Accepted, New, Rejected, Resolved) None      
Metrics None
Measure Business Processes
Outputs Output Type (Digital, Print)
output from Applications
reference Data Entities
support Business Processes
Opportunities None
Benefit Applications
Benefit Business Processes
Pain Points Priority (High, Medium, Low)
Are caused by Applications
Occur in Business Processes
Occur in Business Units
Occur in Geographies
Lead to Inefficiencies
Are caused by  Interfaces
Partners  None
Receive from Interfaces
Support Applications
Support Business Processes
Support Projects
Support Ways of Working
People Staff Type (Contract, Permanent, Partner)

Use Applications

Work in Business Processes

Work in Geographies

Problems None Affect Business Processes      
Process Controls Control Type (Automatic, Manual)
Mitigate Process Risks
Projects Project Type (Finance, HR Project, IT Project, Marketing, Supply Chain)
Improve Applications
Improve Business Processes
Improve Interfaces
Managed by People
Resolve Inefficiencies
Reports Report Focus (Operational, Strategic, Tactical)

comprise KPI

Measure Business Processes


Requirement Class (Functional, Non-Functional)

Requirement Type (Business Requirements, Solution Requirements, Stakeholders Requirements, Transition Requirements)

Signature Requirement (Yes, No)

Priority (High, Medium,, Low)

Relate to Applications

Relate to Interfaces

Relate to Reports

Support Business Processes

Solve Problems


Impact (Critical, High, Low, Medium, Very High)

Probability (Certain, Likely, Unlikely, Very Likely, Very Unlikely)

Stage (Accepted, Escalated to Issue, In progress, Mitigated, New, Rejected)

Become Issues

Mitigated by Assumptions

Roadmap Roadmap Category (Approved, Possible, Probable, Released)

Enables Business Processes

Resolve Workarounds

Supports Strategic Thrusts

SAP Custom Transactions Portfolio Strategy (Rebuild (low code), Refactor (code), Retain, Revert (to standard))

Supports Business Processes

Assessed in Roadmap

SAP Custom Programs

Portfolio Strategy (Rebuild (low code), Refactor (code), Retain, Revert (to standard))

Customisation Type (Transaction, Report, Interface, Output, Workflow, Batch Process, Upload/Extract, Utility, Miscellaneous)

Supports Business Processes

Relate to Interfaces

Assessed in Roadmap

Solution None Resolve Problems      
Strategic Thrust None None      
Ways of Working


Are Specific to Business Processes

Are specific to Geographies

Relate to Applications



Impact Business Processes

Occur in Geographies

Relate to Applications


Complexity (High, Medium, Low)

Priority (Could Have, Must Have, Should Have, Will Not Have)

WRICEF Status (Approved, Built, In Build, Proposed, Rejected, Released, Tested)

WRICEF Type (Conversion, Enhancement, Form, Interface, Report, Workflow)

are part of Projects

enable Business Processes

Owned by People

relate to Data Entities

relate to Interfaces

relate to Outputs

relate to Reports

relate to Requirements

relate to SAP Custom Programs

relate to SAP Custom Transactions