Digital Supply Chains: Part Seven – The Role of Workflow


Fully digital supply chains require a combination of system-to-system integration and workflows that incorporate human decision making and collaboration. Here we discuss the role of workflow in creating a digital supply chain.


( This article is excerpted from the complimentary report:
Getting Real with Workflow-Enabled Digital Supply Chains
, available for download here. )

Previous installments of this series described numerous examples of digitization across different types of supply chain processes. Here we talk about the role that workflow plays.

The Pivotal Role of Workflow in Creating Digital Supply Chains

The end-to-end processes we’ve been discussing invariably involve data and subprocesses from many different enterprise applications and systems, as well as countless interactions that happen outside the enterprise systems in the form of phone calls, paper documents, fax, email, and so forth. Those interactions, outside of the enterprise systems, are where the digital thread breaks, in the gaps between the systems (see sidebar, Workflow Spans the Gaps in the Digital Chain).
Workflow provides the glue that can stitch together these disparate sub-processes into one cohesive end-to-end process. Furthermore, workflow can automate the myriad interactions that happen in-between the enterprise systems — the hand-off points and manual processes where things get bogged down, where delays and errors accumulate. Finally, workflow provides unambiguous, hi-fidelity documentation of the full end-to-end process and encoded corporate policies. Anyone with a need and authority can see exactly how things are done and, if needed, easily make changes that are reliably enforced and executed — provided the underlying workflow platform provides visualization of processes and no-coding, intuitive, visual workflow authoring and editing tools.
Not all workflow platforms are the same. The ease with which business people can understand and modify workflows makes a big difference in business agility. When programmers have to get involved, it creates risks of ‘lost in translation’ errors, as well as forcing business people to wait in the queue for IT assistance. The ability for line of business and process owners to quickly adjust workflows is a critical competence to stay agile in today’s fast paced world where everything is in constant flux due to competitors’ actions, emerging threats, regulatory changes, market forces, changing political winds, shifting trade policies, fluctuating demand patterns, and so forth.

The Right Tools for an Agile, Incremental Approach

An agile incremental approach requires tools that don’t require heavy IT involvement and allow business users direct control and the ability to evolve workflows themselves, one step at a time. The following capabilities enable a workflow platform to support an agile, incremental transition to a digital supply chain:

  • Graphical, no-coding workflow logic editing — Being agile requires the ability to create workflows graphically, and do all but the most sophisticated workflows without requiring coding or scripting.
  • Painless integration for workflow authors — When business users are authoring or modifying workflows, the system must make it intuitive and easy to integrate all required enterprise systems and data from other sources as well. An example is drag and drop connections to/from the relevant systems and databases.
  • Easy set up of integrations by technical staff — It also needs to be relatively easy for the technical team (whether it’s the company’s own IT staff or a system integrator) to set up the integrations with the enterprise systems and other systems and services behind the scenes. This is enabled by a workflow platform coming with a rich set of prebuilt connections, the ability to easily customize those connectors as needed (such as adjusting the semantical mappings), and the ability to straightforwardly integrate other data, APIs, and microservices from systems for which prebuilt connectors have not yet been created.
  • IoT support — With the rapid growth of IoT (Internet of Things), the ‘things’ — i.e. machines, vehicles, buildings, products, and other objects — can become directly-connected, digital participants in these digital workflows. Workflow platforms should be ‘future-proofed’ to incorporate IoT devices and data streams.
  • WYSWIG1 Templated Document Builder — The workflow needs to be able to generate documents (e.g. emails, PDFs, Word docs, etc.) on the fly, using templates and the same integration tools used for authoring the workflows.
  • Forms — Easy to author forms are needed, available in email, web, and mobile formats.
  • Universal, mobile communications — The ability to reach users wherever they are, the way they work, on whatever devices and communications systems they use. This includes email, text messages, IVR2; with strong support for various mobile devices and a responsive UI. It also includes the ability to easily connect to trading partners (very important for supply chain), without them having to load any application or have a license. As well, ‘lazy approval3 support, where the user can reply to an email or text sent by the workflow engine with a simple one word response, like “Yes” or “No”.
  • Offline support — Mobile workflow apps need to be able to run in ‘disconnected mode’ when there is no network, with all the necessary rules and logic running locally, as well as the ability to accumulate data and actions (e.g. form submission) locally, queued up for submission as soon as a connection is established.
  • Process data capture and analytics — Workflow captures an incredibly valuable stream of data that is not available in any other system. The workflow platform should have dashboards and analytic tools for both data about the execution of processes and data extracted from content of the processes. Process execution data analytics help companies understand how often processes are run, how long each step in a process is taking (both elapsed time and working time), differences in performance between different locations or individuals, what content is used, and so forth. Process content data allows the analyst or manager to peer into the actual transactions, data entry fields, and so forth to get more specific information — such as what is the average temperature recorded at this point in this process, or what is the mix of services being requested at location X, or how many and what kind of RFQs are we sending out, and how many respondents are there by commodity type. The value potential of these kinds of analytics is enormous and is currently largely untapped.
  • Audit trail — The system should have the ability to keep an immutable record of past actions and provide the ability to audit those actions to help ensure regulatory and other compliance, as well as provide countermeasures against fraud

With these characteristics, the workflow platform can still conform to IT standards and fit within IT controls, yet not be constrained by IT backlogs, because it doesn’t require a programmer writing code or scripts. A typical business analyst, or even power business user can understand the tools and start to build automated flows. Not all workflow platforms have these traits — many, if not most, require some sort of script writing and coding. Once a programmer is required, things can get lost in translation as requests are passed from the business user to the business analyst to the coder, like a game of telephone. The attributes of a workflow platform listed above are crucial if that platform is to enable a business to be truly agile in today’s fast-paced hyper-competitive world.

The eighth and final article in this series discusses how to get started on the journey to a fully digital supply chain without getting overwhelmed.


1 WYSWIG = What you see is what you get. — Return to article text above
2 IVR = Interactive Voice Response, where people interact with a computer via audio phone call, using voice and the dial pad. — Return to article text above
3 The need for text-based ‘lazy approval’ is driven in part by companies that only allow text-based email for security reasons, or because of bandwidth constraints. — Return to article text above

To view other articles from this issue of the brief, click here.

Scroll to Top