Eight modules, named as supplied
EPMS — Enterprise Management System — brings project records, engineering, procurement and scheduling into one requirements conversation. Each module is scoped per engagement; nothing here is described as deployed.
- Modules
- 08
- Scoped
- By module
- Starts with
- Map
- Terms
- In scope
Document Management System
Project documents and their relationship to the work being managed. Lifecycle, access, review, versions and handover are defined with you during Map.
Engineering Management System
Engineering information and the activities or decisions it supports. The engineering scope, deliverables and workflow are defined with you.
Procurement
Procurement records and their connection to the delivery requirement. Stages covered, approval behaviour and interfaces are agreed in the scope.
Scheduler
The scheduling information needed to coordinate the work. Planning, update and dependency functions are defined with you.
Portfolio/Program Management
How related initiatives are organised and viewed together. The portfolio and program hierarchy, and the reporting scope, are agreed for your organisation.
DPR
Kept under the name supplied. What DPR covers in your scope, and who produces and receives it, is defined with you during Map.
Electronic Management Record
Kept under the name supplied. The record it manages, its intended users, workflow and retention context are identified with you.
Mobile Apps
Mobile access to selected EPMS tasks or information. Platforms, functions and connectivity conditions are confirmed against your requirement.
- First conversation
- EPMS desk takes first conversations for EPMS.
- New requirements
- operations@hyperspace.works