An engineer's method: structured, traceable, verifiable.
Clear governance, document quality, risk and change management: what makes a project keep its commitments.
Five phases, from input data to lessons learned.
Every technical package follows this approach, led by a senior expert and coordinated by a single project manager.
Scoping & needs analysis
- Specification and scope review
- Technical, regulatory, environmental constraints
- Deliverables and milestones
Organisation & planning
- Project team by discipline
- Communication plan and schedule
- Approval workflows
Design, engineering & review
- Technical deliverable production
- Standards applied (IEC, ISO, ASME, API)
- Cross-discipline review
Quality control & approval
- Document consistency and compliance
- Internal sign-off before submission
- Secure document archiving
Handover & lessons learned
- Structured delivery
- Knowledge transfer
- Continuous feedback loop
Every document has a code, a revision and a status.
Versions are managed in a document system with access rights. Any major change goes through a change request (DCN) with impact analysis and formal approval.
TA-[CLIENT]-[PROJET]-LOT03-CAL-0042-REV1
Coding example: discipline, package, type, index, revision.
| Step | Action |
|---|---|
| DB | Input data and Design Basis validation |
| V0 | Initial issue and cross-reading |
| QA/QC | Internal review: standards checklist and specification compliance |
| V1 | Issued for client comments, tracking register |
| V2 | Comments closed, final approval and archiving |
Who does what, in black and white.
Kick-off meeting, weekly steering committee, shared dashboard (progress, risks, quality KPIs) and a shared comment register.
| Activity | Client | Project director | Package lead | Engineer | QA/QC |
|---|---|---|---|---|---|
| Input data validation | A | R | C | C | I |
| Deliverable production | I | A | R | R | C |
| Internal QA/QC review | I | C | C | C | R |
| Joint review & comment close-out | A | R | R | C | C |
| Final approval & archiving | A | R | C | I | R |
R = Responsible · A = Accountable · C = Consulted · I = Informed
Anticipate rather than react.
Each risk is rated for probability and impact, with upfront mitigation and a contingency plan ready to trigger.
| Risk | Prob. | Impact | Mitigation |
|---|---|---|---|
| Incomplete input data | Medium | High | Detailed initial review, Design Basis sign-off upfront |
| Cross-discipline clashes | Medium | Medium | 3D clash detection, weekly cross-reviews |
| Review or approval delays | Low | Medium | Shared milestone schedule, automatic reminders |
| Non-compliance with standards | Low | High | QA/QC checklists per package, double sign-off |
| Cyber risk and confidentiality | Low | High | NDA, access rights, document encryption |
| HSE incident on site | Low | High | Safety briefing before every mission, standard PPE |
Proven tools, international standards.
Team mobilised within 5 working days, on site in under 72 hours anywhere in Morocco.
| Domain | Tools |
|---|---|
| CAD | 2D / 3D design software and digital models |
| Calculation & simulation | Finite elements, piping flexibility, process and mould-fill simulation |
| Electrical & instrumentation | Network sizing, selectivity, lighting, electrical schematics |
| Planning & tracking | Multi-project scheduling, critical path, progress tracking |
| QHSE & OPEX | Performance dashboards, mapping, Lean tools |
| Collaboration & document control | Secure collaboration platforms and document management |