Access Official Technical PDF

Share Summary:LinkedInEmail

Enterprise technology adoption is not simply a matter of selecting a new tool. In complex organizations, technology must address defined business needs, work alongside established systems and processes, and be implemented with operational discipline. A 2018 account of technology initiatives at a large financial services group illustrates several of these challenges, including systems efficiency, automation and early experimentation with blockchain. For industrial automation leaders, the examples offer a useful framework for evaluating innovation without assuming that a promising proof of concept is already a production-ready solution.

Enterprise technology adoption starts with business priorities

The initiatives described span several different functions: research and consulting, information systems, securities operations and banking. That breadth matters. Technology adoption is more likely to be relevant when it is connected to the work of the business, rather than treated as a stand-alone innovation program.

In its IT systems business, the group reported responding to large institutional projects, including work related to global financial regulation. At the same time, it pursued cost efficiency through ongoing automation and improvements to development and management operations. These priorities show two complementary aims: meeting demanding system requirements while improving the way systems are built and maintained.

Industrial organizations face their own combinations of operational requirements and efficiency objectives. The specific systems and regulations differ, but the underlying planning question is similar: what business or operational need should a technology initiative serve, and how will it fit into the systems and workflows already in place?

Automation can improve the work around systems

The source describes automation as part of a sustained effort to make development and systems management more efficient. It does not identify particular tools, quantify results or claim that all work can be automated. The more useful takeaway is the focus on ongoing process improvement rather than treating automation as a one-time project.

For automation engineers and system integrators, that distinction is important. A technology investment may affect not only the equipment or application at its center, but also the work required to develop, operate and support it. Reviewing these surrounding activities can help teams identify where repeatable tasks or inefficient handoffs deserve attention. Any proposed change still needs to be assessed against the organization’s actual operating requirements and technical environment.

Use proofs of concept to test a defined use case

One example in the account is a proof of concept involving blockchain technology for securities post-trade processing. The work was carried out within a Tokyo Stock Exchange consortium framework. The description positions the initiative as a test of technology for a specific business process—not as evidence that blockchain had been deployed broadly or had replaced existing transaction systems.

That distinction is valuable across industries. A proof of concept can help an organization examine whether a technology is relevant to a particular process and whether it merits further consideration. It should not be confused with an operational deployment. Before moving beyond a test, decision-makers need to understand how the proposed approach relates to current systems, process responsibilities and business objectives. The available account does not provide results from the blockchain test, so it cannot establish whether the approach met those criteria.

Keep experimentation connected to implementation

The group also described efforts to apply advanced technology in actual business situations and to expand its customer base. Read together, these aims suggest that experimentation was part of a broader technology and business agenda. For industrial organizations, a similar discipline means defining what a pilot is intended to establish and considering early how a successful test could fit into real operations. A technically interesting demonstration alone does not answer questions about deployment, support or integration.

Systems integration and organizational coordination matter

Technology initiatives rarely sit within a single team. The account describes systems work across major institutional projects, continued improvements to development and management processes, and collaboration through an external consortium for the blockchain proof of concept. These examples underline the importance of coordination between technical teams, business stakeholders and external participants.

In industrial automation, systems integrators and plant teams can use the same principle when evaluating new technologies: involve the people who understand the process, the existing technical environment and the operational consequences of change. This is not a claim that financial services and industrial systems have identical requirements. Rather, it recognizes that technology decisions in both settings depend on how a solution connects with the wider organization.

Build a practical path from innovation to operations

The initiatives provide a framework for technical decision-makers considering enterprise technology adoption:

  • Start with a specific need. Link the initiative to an identifiable business or operational requirement.
  • Consider the existing environment. Assess how the technology relates to current systems, development practices and management processes.
  • Use a proof of concept to investigate, not to overclaim. Define what the test is meant to evaluate and distinguish a trial from a proven deployment.
  • Include relevant stakeholders. Coordinate technical and business perspectives, particularly when an initiative spans organizations or functions.
  • Plan for sustained operations. Consider how a solution would be developed, managed and supported if it progresses beyond experimentation.

The 2018 examples are specific to a financial services group, and they do not establish the performance or suitability of these approaches for industrial applications. Their practical value lies in the decision-making principles they illustrate: connect technology to business priorities, improve supporting processes, test emerging ideas against defined use cases, and treat integration as part of implementation. For industrial automation teams, those principles can help turn interest in new technology into a disciplined evaluation of operational value.

Access Official Technical PDF

About The Author