EPMS — Enterprise Management System — brings eight modules into one requirements conversation. Define which you need, how their records relate and who acts on them.
What is in scope
Modules
Pick the ones your requirement touches. How their records relate is defined with you during Map.
Documents, tied to the workProject documents and their relationship to the work being managed. Lifecycle, access, review, versions and handover are defined with you during Map.
Engineering information in contextEngineering information and the activities or decisions it supports. The engineering scope, deliverables and workflow are defined with you.
Linked to the delivery requirementProcurement records and their connection to the delivery requirement. Stages covered, approval behaviour and interfaces are agreed in the scope.
What the plan needs to knowThe scheduling information needed to coordinate the work. Planning, update and dependency functions are defined with you.
Related initiatives, togetherHow related initiatives are organised and viewed together. The portfolio and program hierarchy, and the reporting scope, are agreed for your organisation.
Named as suppliedKept under the name supplied. What DPR covers in your scope, and who produces and receives it, is defined with you during Map.
Named as suppliedKept under the name supplied. The record it manages, its intended users, workflow and retention context are identified with you.
Selected tasks, on siteMobile access to selected EPMS tasks or information. Platforms, functions and connectivity conditions are confirmed against your requirement.