This post walks through the core entities that underpin an enterprise project scheduling environment. By clarifying how structures, resources, activities, codes, and calendars relate to each other, it becomes easier to understand how schedules are built, controlled, and analyzed across complex portfolios.
Modeling based on the Author's Perspective
| Entity | Description |
|---|---|
| Enterprise | The overall organization within which projects, resources, and standards are managed. |
| Enterprise Structure | The high-level hierarchy that organizes organizational units and resource groupings. |
| Resource Breakdown Structure | A hierarchical classification of resources, grouping them by function, discipline, or organization. |
| Organization Breakdown Structure | A hierarchy of organizational units used to represent responsibility, control, and reporting lines. |
| Enterprise Codeable Entities | Enterprise-level objects that can be tagged with standardized codes for reporting and analysis. |
| Resources | People, equipment, or materials that are assigned to activities to perform project work. |
| Resource Breakdown Structure Assignment to Resource | The link that places each resource into the appropriate node of the resource breakdown structure. |
| Role | A generic skill or job function used to plan and staff activities before specific resources are chosen. |
| Activity Assignment | The relationship that connects activities with the roles and resources responsible for executing them. |
| Activity Assignment to Role | The assignment of a role to an activity to represent required skills or responsibilities. |
| Activity Assignment to Resource | The assignment of a specific resource to an activity to perform the planned work. |
| Work Break-down Structure | A hierarchical decomposition of project scope into manageable deliverables and control accounts. |
| Activities | Discrete units of work that represent the tasks needed to deliver project scope. |
| Task Activities | Activities with duration that consume resources and drive the project schedule. |
| Milestone Activities | Zero-duration activities used to mark key events, decisions, or delivery points. |
| Logic | The network of relationships between activities that defines sequence, dependencies, and critical path. |
| Project Schedule Versions | Different saved states of a project schedule used for comparison, baselining, and scenario analysis. |
| Projects | Formal initiatives with defined scope, schedule, and resources managed within the enterprise. |
| Enterprise Codes | Standardized code sets applied across the enterprise to categorize and group objects consistently. |
| Project Codes | Code sets used to classify and group projects according to business, region, phase, or other criteria. |
| Calendar | The definition of working and non-working time used for scheduling and resource availability. |
| Enterprise Calendar | A calendar that defines global working patterns and holidays used across multiple projects. |
| Resource Calendar | A calendar that defines the specific availability and working time of an individual resource. |
| Project Calendar | A calendar that defines working time and constraints specific to a particular project. |
Seeing these entities side by side highlights how scheduling, responsibility, and classification all intersect in a single ecosystem. Once you can name each part and its role, it becomes much easier to reason about schedule quality, governance, and the kinds of insights you can reliably draw from your project data.
Comments
Post a Comment