Unified Data Model
ScopeOps uses a unified canonical data model that aligns portfolio, delivery, governance, and analytics. All modules share the same data foundation, ensuring accuracy and consistency across the platform.
Core Principles
The ScopeOps data model is designed from the ground up to support enterprise portfolio management, delivery tracking, and governance workflows with a single source of truth.
Hierarchical Structure
Portfolio → Program → Project hierarchy with automatic roll-ups and aggregations.
Cross-Module Consistency
Shared entities across Demand, Scoping, Delivery, and Analytics ensure data integrity.
API-First Design
All data accessible via REST API v2 with JSON:API compliance for integrations.
Analytics Optimized
Star schema design for Power BI and analytics with incremental refresh support.
Key Entities
- •Portfolio: Top-level container for strategic alignment and investment tracking
- •Program: Collection of related projects with shared objectives
- •Project: Individual delivery initiative with scope, timeline, and budget
- •Demand: Intake requests that convert to projects
- •Work Item: Unified representation of ScopeOps tasks, ADO epics, and Jira issues
- •Baseline: Version-controlled scope, schedule, and budget snapshots
- •Change Request: Governance-tracked modifications with approval workflows
Traceability
Full bidirectional traceability from Demand → Project → Work Item → ADO/Jira ensures that every deliverable can be traced back to its business justification.
Want to learn more?
Explore the full platform overview or contact us for detailed architecture documentation.