CompareEnterprise architecture

Dotwork vs Cameo Enterprise Architecture

Dassault Systèmes’ standards-compliant tool for authoring UAF, DoDAF, MODAF and NAF architecture models.

Cameo Enterprise Architecture authors the framework-compliant architecture models that engineering programs require, and Dotwork does not do that work. Dotwork shows the cost and funding of the capabilities and applications those models describe, on one Enterprise Operating Model.

At a glance

Enterprise architecture

Cameo Enterprise Architecture

vs

Operating model

Dotwork

Overlaps with

Dotwork runs these and 16 more on one model.

Usually runs alongside Dotwork

Dotwork connects to it and puts its data in the context of the whole enterprise.

The short version

What each is built for.

Cameo Enterprise Architecture

Cameo Enterprise Architecture, from Dassault Systèmes (formerly No Magic) and also sold as Magic Systems of Systems Architect, is a modeling tool for standards-compliant architecture frameworks including UAF, DoDAF, MODAF and NAF. Built on MagicDraw and part of the CATIA and 3DEXPERIENCE family, it keeps architecture views in the same model as SysML system models and connects to simulation, requirements and engineering tools.

  • Authoring UAF and DoDAF views that defense and government programs are required to deliver
  • Keeping architecture views and SysML system models in one engineering model
  • Running simulation and parametric analysis on architecture models
  • Exchanging models with requirements and engineering tools in defense and aerospace programs

Dotwork

Dotwork is an AI-native enterprise operating platform built on the Enterprise Operating Model: one live, graph-based model that connects strategy, capital, work, technology and AI across the enterprise. Dotwork does a different job from Cameo: it does not author framework views, but it can show the cost and funding of the capabilities and applications a program architecture names.

  • Showing what capabilities and applications cost, based on cost allocated from finance systems
  • Linking capabilities to the investments and initiatives that fund them
  • Connecting architecture to strategy, labor and AI on one operating model
  • Giving CIO, finance and portfolio leaders a shared view of the technology estate

The core difference

How Dotwork and Cameo Enterprise Architecture approach the problem.

Cameo and Dotwork mostly do different jobs, and the overlap between them is narrow. Cameo authors the formal architecture descriptions that engineering programs must produce; Dotwork holds the operating model where the cost, funding and labor of capabilities and applications are connected.

Context

Cameo organizes context around framework-defined views and model elements tied to systems engineering. Dotwork organizes context around operating records such as investments, capabilities, applications, teams and cost.

Decisions

Cameo supports engineering and program decisions, such as whether an architecture meets its requirements and framework rules. Dotwork supports investment and operating decisions, such as what a capability costs and which work is funded to change it.

Time

Cameo models architecture across program phases and capability increments as part of an engineering lifecycle. Dotwork holds plans, investments and cost history across budget and planning periods.

Change

Cameo manages change through a shared engineering model, versioned for teams. Dotwork shows how a change to a capability or application connects to funded work and the cost base.

Architecture and data model

Side by side.

The two products meet only where a program architecture names capabilities and applications that also carry cost. Cameo remains the place to author the architecture description, and Dotwork can show what those capabilities and applications cost and which investments fund them.

Architecture and data model comparison between Dotwork and Cameo Enterprise Architecture
DimensionCameo Enterprise ArchitectureDotwork
Primary purposeStandards-compliant architecture and systems modeling for engineering programsAn enterprise operating model connecting strategy, cost, work, technology and AI
FrameworksUAF, DoDAF, MODAF and NAF, alongside SysML, UML and BPMNReference model mapped to BIZBOK, TOGAF and ArchiMate concepts; no UAF or DoDAF support
CostModel metrics and parametric values for analysis, rather than a finance cost modelCost allocated from finance systems onto capabilities and applications, designed to reconcile to the source
Engineering linkArchitecture and SysML system models in one model, with simulationNo link to systems engineering models
Primary usersProgram architects and systems engineersCIO, finance, portfolio and architecture leaders

The role of AI

Where the AI gets its context.

Cameo automates checking and analysis of engineering models. Dotwork applies AI to questions and record changes across an operating model of strategy, cost, work and technology.

Cameo Enterprise Architecture

Cameo’s automation centers on engineering rigor: validating models against framework rules, simulation and parametric analysis, and interchange with requirements and engineering tools.

Dotwork

Dotwork includes an assistant that answers questions across the whole model and agents that can create and update Dotwork records, with optional human review. An MCP server, enabled per site, makes the same model available to outside AI tools. Because the model spans strategy, cost, architecture, labor and AI, a single question can cross those domains.

A fair comparison

Where Cameo Enterprise Architecture is strong — and where Dotwork is different.

Where Cameo Enterprise Architecture is strong

  • Authoring UAF, DoDAF, MODAF and NAF views that defense and government programs must deliver; Dotwork does not support these frameworks
  • Architecture views and SysML system models in the same model, a requirement in many defense programs
  • Simulation, parametric analysis and interchange with requirements and engineering tools
  • Part of the Dassault CATIA and 3DEXPERIENCE family, with Teamwork Cloud for shared models

Where Dotwork is different

  • Shows what capabilities and applications cost, from cost allocated out of finance systems
  • Connects capabilities to the investments and initiatives that fund them, with strategy above
  • Shows labor, cloud and vendor spend on the same capability and application records
  • Serves CIO, finance and portfolio leaders rather than program engineering teams

Choosing

Which fits your situation.

Choose Cameo Enterprise Architecture when

  • Your program must deliver UAF or DoDAF views
  • Architecture needs to live in the same model as SysML system models
  • You need simulation and engineering tool interchange for architecture models

Defense, aerospace, government and automotive programs that must produce framework-compliant architecture and keep it tied to systems engineering models.

Choose Dotwork when

  • You need to know what capabilities and applications cost and what funds them
  • Your buyers are CIO, finance and portfolio leaders rather than program architects
  • You want architecture connected to strategy, labor and AI on one model

Organizations that want to see what their technology estate costs and which investments change it, across strategy, portfolio, architecture and AI.

The bottom line

Choose Dotwork when you want to connect the enterprise across systems and silos — with a lower total cost of ownership.

One operating model across strategy, capital, work, technology and AI, instead of another tool to integrate, reconcile and maintain alongside Cameo Enterprise Architecture.

See it on your data

FAQ

Questions buyers ask.

Can Cameo and Dotwork be used together?+

Yes, where both are needed. Cameo remains the tool for authoring the program architecture. Dotwork can hold the capabilities and applications it names as operating records and show what they cost and which investments fund them.

Does Dotwork support UAF or DoDAF?+

No. Dotwork does not author UAF, DoDAF or other framework views. Its reference model is mapped to BIZBOK, TOGAF and ArchiMate concepts.

Is Dotwork an alternative to Cameo?+

Generally not. The two do different jobs and overlap only on the capabilities and applications they both describe. Organizations that need framework-compliant modeling should keep Cameo for that work.

Be Decisive.Build Fast.Connect Everything.

Start Connecting