A Functional Framework for Project Information Architecture

Integrating ISO 15489 and ISO 19650 for Project Managers

In the absence of a global standard for project classification, practitioners often rely on ad hoc systems that lead to information silos and version control failures. To build a robust Document Management System (DMS), PMs must distinguish between Classification (rigorous, hierarchical filing) and Categorization (flexible grouping based on similarity). While categorization supports creative phases, formal classification is required for long-term project control.

Top-Level: Functional Classification (ISO 15489)

Standardizing folders by "Subject" is inherently unstable. Following ISO 15489, documentation should be structured by Function—what the document does for the project.

• 100 Governance: Charters, contracts, and legal compliance.
• 200 Requirements: User stories, business logic, and data models.
• 300 Design: Architecture diagrams and UI/UX wireframes.
• 400 Implementation: Technical documentation and API schemas.
• 500 Quality Assurance: Test plans, bug reports, and validation logs.
• 600 Operations: Release notes and configuration data.

Sub-Level: Information Status (ISO 19650)

To eliminate versioning ambiguity, each functional folder utilizes the Common Data Environment (CDE) status levels defined in ISO 19650.

• S1 (Work In Progress): Unvetted team drafts and informal notes.
• S2 (Shared): Information approved for cross-disciplinary coordination.
• S3 (Published): Validated, contractual deliverables.
• S4 (Archived): Superseded or obsolete records kept for audit trails.

The Metadata Layer: Faceted Naming

Research into Faceted Classification proves that "where" a file is located is often less important than "how" it is named. A faceted convention ensures every file is self-describing and searchable.

Conclusion

A DMS should be engineered, not forced. By combining Functional Classification for structure and CDE Status for maturity, a Project Manager ensures information serves the project lifecycle rather than complicating it.