What is a business?

What is a business?
A process view

Four truths, fourteen domains in three layers, and fifteen end-to-end flows that run across them. Built from APQC’s Process Classification Framework 8.0 and the Microsoft Business Process Catalog.

Source to pay, order to cash and forecast to plan, drawn across the domains they touch. Select a domain to explore it.

Four truths about how a business works

Each one builds on the one before: from processes, to the people and applications that run them, to the data they leave behind.

  1. 1

    Every business can be described as a network of connected processes.

    Processes describe how the business works. The business itself consists of people, assets, information, legal entities and culture.

    It lives through its relationships with customers, suppliers and partners.

  2. 2

    Processes fall into three layers.

    Management processes steer the business, core processes create and deliver value to customers, and support processes enable both. Some domains, like asset management, serve more than one layer.

  3. 3

    Processes are carried out by people and applications, including connected machines and AI.

    Every step reads, creates or changes data. Almost everything a business owns or does, from a screw in the warehouse to an hour worked, is represented as data somewhere.

  4. 4

    Data should be the truth about the company’s situation.

    In practice, it’s only as accurate as the processes, people and applications that create it.

The fifth rule: when no person is needed

The four truths lead to a conclusion. When a data change needs no judgment, and the information for it already exists digitally, the work can complete on its own.

5

If processes change data, and the data should reflect reality, then a data change that needs no judgment and no information beyond what’s already digital doesn’t need a person.

  • The information must be accessible and reliable.Integrations or sensors make it reachable, and it has to be trustworthy.
  • Some humans are mandated.Law, policy or accountability may still require a person, for example to approve a payment.
  • People handle the exceptions.Agents bring unclear cases to people, who either fix the data source or make the decision. Fixing root causes keeps shrinking the exceptions.

Example: Source to pay

Most of the daily work meets the rule. Eight of the ten most frequent tasks need no person. The work that does need people is mostly decisions and supplier relationships, and much of it happens outside the system.

No person needed

Recording supplier invoices

No judgment is needed, and e-invoices bring the information in digitally. People handle the mismatches.

A person is mandated

Changing a supplier’s bank account

No judgment is needed, but bank detail changes are a common fraud route, so policy keeps a person in the loop.

Digitize the input first

Returning faulty goods

Automatable once the defect is registered at receiving, for example by scanning.

Based on Microsoft’s process catalog and checked against APQC’s framework. Task frequencies are estimates for a typical mid-size company.

Two ways to describe the same business

APQC describes what any organization does, function by function, with no software in mind. Microsoft describes how work flows end to end, and how to run it in Dynamics 365. This site uses APQC as the backbone and Microsoft as the view from implementation.

APQC Process Classification Framework 8.0

Function view
    • 3,284 performance metrics with formulas and units
    • Stable PCF IDs that survive renumbering between versions
    • Neutral: no product, module or configuration detail

    Microsoft Business Process Catalog

    Flow view
      • Mapped to Dynamics 365 products, modules, menus and data entities
      • Includes workshops, tasks and deliverables for implementation projects
      • Deprecated items are left out of this site

      Three layers, fourteen domains

      Management processes steer the business, core processes create and deliver value to customers, and support processes keep both running. Asset management spans two layers: production equipment serves the core, while offices and facilities support everyone. Select a domain to explore its processes and flows.

      Flows run across the business

      Many professionals think in end-to-end flows rather than functions. Pick a flow to see which domains it passes through, then open it for its process areas, processes and scenarios.

      Making products, delivering services

      The model keeps both production and service delivery, so it works for any company. Many manufacturers also sell services on top of their products, and maintenance is where the two meet.

      Where the detail sits

      Processes per domain in each source. The two use different granularity, so compare the shape rather than the numbers. Microsoft goes deeper where software runs the daily work, such as procurement, production and logistics. APQC carries more of the management layer.

      APQC processes (level 3)Microsoft processes (active)

        Using the two sources together

        The sources answer different questions, so they stack rather than compete.

        Business domains

        The fourteen domains on this site: a shared, simple map everyone in the business recognizes.

        APQC reference model

        What each domain does, down to activities, and how to measure it. Use the PCF ID as the stable key.

        Microsoft solution model

        How each process runs in Dynamics 365: process areas, scenarios, and the configuration behind them.

        Things to keep in mind

        • Microsoft doesn’t map its catalog to APQC. The placement of Microsoft process areas into domains here is a judgment call.
        • Microsoft’s export has no stable unique ID, so use its process sequence numbers with care.
        • Order to cash in Microsoft covers selling and getting paid. Shipping the goods sits in Inventory to deliver.
        • APQC 8.0 renamed and added elements compared with 7.4. Hierarchy numbers can change between versions while PCF IDs stay the same.