Access Official Technical PDF

Share Summary:LinkedInEmail

Digital engineering is more than the use of software tools to create engineering models. It is an approach to using models—comprising data, algorithms and processes—as a technical means of communication across engineering work. For industrial automation teams, the underlying idea is relevant wherever complex systems require coordinated design, analysis, testing, operation and support: engineering information should remain useful as decisions and activities move across the lifecycle.

Discussions at the 2020 Systems & Mission Engineering Conference connected digital engineering with model-based systems engineering (MBSE), modeling and simulation, data strategy, the digital thread and systems-of-systems engineering. Taken together, these topics point to a practical challenge: building a coherent engineering environment in which models and their results can inform decisions, rather than treating each model or analysis as an isolated deliverable.

What digital engineering means in practice

Models can make technical information available in a form that supports communication across engineering activities. When models are used consistently, they can help connect system representations, engineering analyses and acquisition or program decisions. The conference track description emphasized this cohesion and the possibility of using simulation results in decision-making at different levels.

This does not mean that a model automatically provides a complete or reliable picture of a system. Its value depends on how it is developed, maintained and used, and on whether its information fits the decision at hand. Digital engineering therefore involves both technical artifacts and the processes, skills and supporting infrastructure needed to use them.

Connecting MBSE, simulation and the digital thread

MBSE is one part of this broader picture. The conference program addressed model-based systems engineering alongside digital engineering, modeling and simulation, and digital-thread topics. These areas overlap, but they are not interchangeable: MBSE focuses on applying models within systems engineering, while modeling and simulation can support analysis across different process phases. Digital engineering provides a broader context for connecting models and engineering activities.

A digital thread can be understood here as a means of maintaining useful connections among engineering information and lifecycle activities. Sessions on integrating MBSE with product lifecycle management, model management across multiple repositories and extending a digital engineering framework into operations illustrate the questions organizations face when trying to carry models beyond an individual design task.

For engineering leaders, the practical question is not simply whether teams have modeling tools. It is whether teams can use the resulting information in a connected way. A model that cannot be related to relevant analysis or downstream work may offer limited support for cross-functional decisions. Conversely, connected models and workflows can provide a basis for reviewing assumptions, comparing alternatives and carrying engineering knowledge into later activities.

Digital engineering for complex systems

The conference also treated digital engineering in the context of large systems and systems of systems. In these settings, engineering decisions can involve multiple systems, disciplines and mission needs. The program included topics such as architecture frameworks, model-based approaches to systems-of-systems development and digital environments for mission engineering.

These subjects highlight why system boundaries and relationships matter. Engineers may need to examine how a change in one part of a system relates to other parts, or how a design supports an intended mission. Modeling and simulation can contribute to that analysis, while architecture and systems-engineering methods help organize the representations being used.

The same principle is relevant to industrial automation projects involving interconnected equipment, control functions and supporting processes. The source material does not prescribe a particular implementation for industrial plants, but its emphasis on connected models and system-level analysis offers a useful consideration: define what the model must help the organization understand, and establish how that information will support engineering decisions.

Building the conditions for adoption

Adopting digital engineering is an organizational change as well as a technical one. Conference topics on model-based enterprise capabilities, deployment mechanisms, cloud infrastructure, data architecture and leadership adoption reflect the range of conditions that may need attention. A sustainable approach requires more than selecting tools; organizations also need supportive processes, infrastructure, skills and expertise.

It is also important to consider how teams will manage model information over time. Sessions addressed multi-repository model management, format independence for SysML models and information exchange. These topics point to practical concerns around accessing, sharing and using models across tools and work groups. Organizations should make those needs visible when defining their engineering environment, rather than assuming that models will connect automatically.

Measurement is another part of implementation. The program included work on digital-engineering measures, lessons learned and the value of systems engineering. For decision-makers, measures are most useful when they clarify whether an approach is supporting the intended engineering and program needs. The goal is not measurement for its own sake, but a clearer understanding of how engineering activities contribute value and where improvement is needed.

From models to better-informed decisions

Digital engineering is most useful when models serve an identifiable purpose: communicating technical information, supporting analysis, connecting engineering activities or informing a decision. That requires attention to model quality and relevance, as well as the workflows and organizational capabilities surrounding the models.

For automation engineers, system integrators and plant leaders, the practical takeaway is to treat digital engineering as a coordinated way of working, not simply a modeling initiative. Start with the decisions and lifecycle activities that need better-connected information. Then consider the models, simulation capabilities, data practices and team processes required to support them. With that foundation, digital engineering can help make engineering knowledge more cohesive and useful across complex systems.

Access Official Technical PDF

About The Author