Business process automation is often associated with factory equipment, control systems and production workflows. But a 2018 NOAH conference program also documented digital companies using automation to manage identity checks, assess financing applications, support trading and coordinate marketplace transactions. These examples come from financial services and online platforms rather than industrial plants, yet they illustrate a useful principle for automation leaders: technology can reorganize a process by changing how information is captured, assessed and acted upon.
For industrial automation engineers, system integrators and operations leaders, the value is not in treating a consumer platform as a factory template. It is in examining the underlying design choices: which steps are automated, what data those steps depend on, where risk is assessed, and how people remain involved. The following cases, described in the conference material as they stood in 2018, offer concrete points for comparison.
Business process automation starts with the workflow
Automation is most meaningful when it is understood in the context of an end-to-end workflow. The profiles describe companies addressing distinct, often manual or fragmented tasks: checking identification documents, evaluating a small business’s financing request, connecting market participants, or arranging the sale of a used vehicle. In each case, software is presented as part of a broader operating model, not simply as a standalone technical feature.
That distinction matters in industrial settings. Digitizing a form or adding a software tool does not, by itself, establish that a process is automated effectively. A useful assessment traces the steps from input through decision to outcome. It also asks whether information moves reliably between systems and whether exceptions can be handled appropriately.
Automating data capture, validation and decisions
Identity checks and customer onboarding
AU10TIX was described as developing systems to capture, authenticate and validate identity documents, then generate digital records. Its stated application areas included regulated services such as financial services, telecommunications, vehicle sales and rental, as well as environments such as airports and secured facilities. The profile presented automation as a way to replace slow, error-prone manual document processing and support customer enrollment and compliance checks.
The transferable lesson is to define the decision boundaries clearly. Document capture, validation and record creation are related steps, but they are not interchangeable. In any operational workflow that relies on automated checks, teams need to understand what information is being assessed, what the system produces, and what happens when a case cannot be resolved automatically. That same discipline applies when evaluating data validation or automated inspection workflows in industrial operations.
Automated assessment and risk
Billie, a digital invoice-financing platform, was presented as using automated scoring engines and KYC/AML modules for customer onboarding and risk assessment. The profile said these processes could take place within minutes and described the business as operating under a factoring license from Germany’s BaFin regulator. The example shows how automation can combine information gathering with assessment in a regulated process.
For technical decision-makers, it highlights the importance of separating workflow speed from decision quality. An automated assessment depends on defined inputs, rules and controls. Before applying similar approaches to an operational process, teams should establish which decisions can be handled by software, which require escalation, and how outcomes can be reviewed. The conference profile does not describe the platform’s detailed scoring methods, so it should not be taken as evidence of a particular algorithm or performance level.
Platforms coordinate activity across multiple participants
Some of the conference examples focused less on automating a single task and more on coordinating a network. 360T was described as providing web-based trading technology and integration solutions for over-the-counter instruments, alongside a multi-bank portal and related services. Its profile emphasized a secure transaction network and a combination of over-the-counter and exchange-based foreign exchange trading and clearing.
In a different market, AUTO1 Group was described as buying used cars from sources including manufacturers and dealerships, then selling them through a global dealer network. The profile said its pricing was determined by a proprietary algorithm and included inspection and valuation in its service. CARS24, meanwhile, described a transaction-led marketplace in which sellers could offer vehicles and businesses could buy through mobile auctions.
These are not industrial control networks, and their operating requirements differ from plant-floor systems. Still, they demonstrate how a platform can bring together information, participants and transactions within a defined process. For industrial teams, the comparison can prompt practical questions: Which participants need access to shared information? Where do handoffs create delays or rework? Which process steps depend on consistent data from multiple sources?
Keep the human and system boundaries visible
Automation does not remove the need to define responsibility. The NOAH profiles describe applications involving financial decisions, identity records, trading and vehicle transactions, but they do not provide detailed accounts of exception handling, system integration architecture or human review practices. Those limits matter: a company profile can identify the intended role of a technology without explaining every safeguard or implementation detail.
When evaluating an automation initiative, industrial organizations can use these examples to structure a review:
- Map the workflow: Identify each step, handoff, input and outcome before selecting technology.
- Clarify decision ownership: Define what software determines and when a person needs to assess an exception.
- Check information quality: Establish how data is captured, validated and made available to the next process step.
- Review interfaces: Consider how the automated process connects with existing systems and participants.
- Match evidence to claims: Distinguish a stated capability from verified performance or a detailed implementation specification.
Conclusion: Apply the principles, not the templates
The digital businesses featured in the 2018 NOAH material provide examples of automation applied to document processing, customer onboarding, risk assessment, trading infrastructure and marketplace coordination. Their technologies are not substitutes for industrial automation systems, and the profiles do not offer enough detail to assess their designs comprehensively. Their broader value is as process examples: successful automation begins with understanding the workflow, the information it depends on and the decisions it must support.
For plant managers, engineers and system integrators, that perspective can make automation planning more disciplined. Start with the process and its constraints, make data and decision boundaries explicit, and evaluate technology against the actual operating need. The result is a clearer basis for deciding where automation can contribute—and where human judgment or additional system design remains necessary.