Why We Didn’t Build Another COMOS

When we set out to build PlantFCE, the obvious question from many in the EPC industry was: “So you’re building a COMOS alternative?”

The short answer: No.

The long answer is more interesting, and it’s at the heart of our design philosophy.

The COMOS Problem: Too Heavy, Too Early

COMOS and similar tools like SmartPlant P&ID were designed to support the full project lifecycle - from concept through handover and beyond. They are powerful, comprehensive, and standardized.

But that power comes at a cost:

• Heavy upfront investment in licenses, training, and implementation
• High data input demands that often don’t reflect actual project constraints
• Complexity that can only be justified in large, well-resourced projects

What we saw on the ground was different: most teams didn’t want another COMOS. They wanted something lighter, faster, and cheaper that still let them get the job done.

A New Reality: Speed and Scarcity

In cost estimation and detailed engineering, speed is king.

• During cost estimation, there is little time or incentive to implement a full COMOS workflow.
• In post-handover plant operations, few have the licenses or manpower to maintain or update the COMOS model.

The result? Most engineering work still happens on PDFs and Excel sheets, not smart databases.

We didn’t see this as a failure of digitization. We saw it as an opportunity to meet teams where they are.

What We Built Instead

We built tools that operate on PDFs, images, and exported data — not only CAD models or proprietary formats.

We focused on three core principles:

1. Local-first: All tools run offline, so no sensitive data ever leaves your network.
2. Hybrid AI: We combine automation with human-in-the-loop validation for better accuracy and traceability.
3. Just Enough Structure: Rather than build a rigid, end-to-end ecosystem, we provide smart entry points into your existing workflow.

This lets you:

• Extract equipment and instrument lists from P&IDs
• Annotate and validate them visually
• Convert them into MTOs, micro data sheets, and cost inquiries
• Maintain audit trails without heavyweight software

COMOS Has Its Place

We aren’t anti-COMOS. For greenfield mega-projects, or tightly integrated enterprise workflows, COMOS is still an excellent tool.

But in the messy, fragmented, PDF-dominated reality of most projects?

PlantFCE is what works.

Final Thought

Digital transformation doesn’t have to be all-or-nothing. PlantFCE sits in the messy middle, where cost estimators, project engineers, and operations teams actually work.

That’s why we didn’t build another COMOS. We built something different. And in many cases, something better.