Gargi
AtlasWalkthroughChainApp
Atlas›Stage 2 · Planning›M25 · Employee Mgmt
M25build

Employee Mgmt

employee data, role taxonomy, project assignments, and RBAC — the people backbone every other module reads from.

What it is

EMS is the system of record for in-house staff across BD, Design, MEP, DCO, CPT, CM, QAA, EHS, and HPM. It owns identity, role, project assignment, performance, training, and leave. Distinct from vendor management (external parties) and labour management (on-site workers). Every other module reads from EMS to know who can do what and on which project.

Inputs
Triggers
  • ·New employee onboarding initiated
  • ·Role change approved by department head
  • ·Project assignment requested by PMO
  • ·Annual performance review cycle
  • ·Training completion submitted
  • ·Leave or exit request raised
Data reads
  • ·IT identity provider for authentication
  • ·Department head approvals for role and project decisions
  • ·Project records (chain.ts) for project IDs and current phases
  • ·Training curriculum from Standards team
Artefacts consumed
  • ·Joining letter and offer documents
  • ·Role change approval memos
  • ·Training certificates from internal and external providers
  • ·Leave application forms
Tools & Techniques
Methods
  • ·Role taxonomy with L0-L4 hierarchy mapped to function (BD, Design, MEP, etc.)
  • ·RBAC policy generation from role + project + sensitivity level
  • ·Performance review aggregation from project outcomes, not self-reports
  • ·Skill-to-role matching for project staffing recommendations
Policies
  • ·HR policy for role definitions and approval thresholds
  • ·IT security policy for RBAC scope and access revocation
  • ·Performance review cadence and weightage policy
  • ·Leave policy by employee category
Decision rules
  • ·Role change above L2 requires department head plus HR approval
  • ·Project assignment for L0/L1 approved by MD
  • ·RBAC scope auto-derived from role; exceptions logged
  • ·Performance reviews triggered by project completion, not calendar
Outputs
Artefacts produced
  • ·Employee master record (read by every module)
  • ·Active project assignment register
  • ·RBAC permissions for downstream system enforcement
  • ·Performance review record with project-outcome linkage
  • ·Training and certification register
Data writes
  • ·Employee record updated on lifecycle events
  • ·Project assignments propagated to PMC and project workspaces
  • ·RBAC tokens issued to identity provider
Downstream triggers
  • ·New assignment notifies PMO and the project workspace
  • ·Role change triggers RBAC re-evaluation across all modules
  • ·Exit triggers access revocation across every system
Stakeholders
  • HROwns employee master record and lifecycle
  • Department HeadsApprove role changes, project assignments, performance
  • PMOConsumes assignment data for project staffing
  • ITRBAC enforcement through identity integration
  • Every employeeConsumer — sees their record, raises updates
The flow
  1. 01Employee onboarding — joining formalities, identity creation
  2. 02Role taxonomy mapping — BD / Design / MEP / DCO / CPT / CM / QAA / EHS / HPM, with L0-L4 hierarchy
  3. 03Project assignment — primary project, secondary projects, roles per project
  4. 04RBAC scope set — what this person can read, write, approve, in which module
  5. 05Performance reviews captured against project outcomes
  6. 06Training records maintained, mapped to role requirements
  7. 07Leave and availability tracked
  8. 08Exit formalities and access revocation
State change
Before

Employee data lives across HR records, IT identity, project trackers, and email distribution lists with no single source of truth.

After

EMS is the canonical employee record; every module joins to it for identity, role, and project context.

Real-world example

Manasi Sawant — DGM, Platform Team, primary project Atelier, secondary projects opswalk + Pool feedback tracker. RBAC: read all MEP modules, write own project records, approve L4 deliverables. Last performance review captured March 2026 with cycle-time and quality scores.

Artefacts
  • ·Employee master record
  • ·Role taxonomy and hierarchy definitions
  • ·Project assignment register
  • ·RBAC policy per role
  • ·Performance review records
  • ·Training and certification log
Pain today

Role definitions vary across departments. Project assignments live in PMO spreadsheets. RBAC is implemented per-tool inconsistently — same person has different access in Atelier, Bandhoo, and SAP. New joiner takes two weeks to get full system access.

Integrations
IT identity provider (Active Directory or equivalent)Every other system (provides identity and RBAC scope)