Context
SharePoint, Aconex, Asite: these are commonly called CDEs and certainly play CDE-adjacent roles. But they are document management systems with workflow added on top. A true CDE in the ISO 19650 sense is a different category of tool, with different structural commitments.
All CDEs are document-aware; not all document management systems are CDEs.
Explanation
Three structural differences matter most:
Containers vs. files
A DMS treats everything as a file. A CDE treats information as containers that may correspond to a file, a 3D model, a requirements list, a clash report, or a database extract. The container is the unit of information; the storage format is incidental.
Status, not folders
A DMS uses folders and access permissions to communicate status. A CDE uses an explicit lifecycle (WIP, Shared, Published, Archived) baked into the data model. Status is queryable across the entire dataset; folders are not.
Semantic relationships
A DMS knows files have authors and revision numbers. A CDE knows a requirement is satisfied by a model element which lives in a system which is part of an asset. Relationships are first-class objects, not metadata.
A CDE is closer to a database with a domain ontology than to a filing cabinet. Weaver makes that explicit, the underlying store is an RDF knowledge graph, not a folder hierarchy. Documents still exist (they're a kind of information container), but they live alongside structured data and model elements as equal citizens.