Why a Systems Department
CMSL runs technically demanding, safety-governed work — metering, valve calibration, catalyst handling, loading-arm and EPCIC work — under ISO 9001, 14001 and 45001, across two sites, for clients who audit process discipline as closely as the work itself. That combination is exactly where manual processes cost the most: a job card that takes three days to reach accounts, a QHSE incident that sits in an inbox before anyone acts on it, or an inspection certificate that can't be located during a client audit are not just inefficiencies, they are risks to contracts with operators like NLNG, SPDC and Dangote Refinery who expect documented, repeatable systems.
A Systems Department gives the company one place responsible for closing that gap: mapping how work actually flows through the business, building or configuring the tools to run it digitally, and keeping the resulting systems of record (maintenance history, QHSE reporting, document control, procurement, HR) accurate enough to stand behind in a client or ISO audit. The plan below sizes that department at the minimum headcount that can realistically carry all of it, sequenced so early wins fund the board's confidence for what comes next.
This plan treats "Systems" as business-process automation and the systems of record that support it (workflow, ERP/CMMS, reporting, infrastructure) — not a general software house. Deep engineering/OT systems tied to specific client equipment remain with technical operations; the Systems Department automates the paperwork and coordination around that work.
Recommended Org Structure
A flat, five-person structure reporting through one manager to the MD keeps decisions fast and avoids adding a management layer the department doesn't yet need. All four specialist roles report to the Systems & Automation Manager, who reports directly to you.
As volume grows past this baseline — more sites, a formal CMMS with heavier support load, or a backlog the team can't clear — the natural next hires are a second IT Support Officer (one per site) and a Training/Change Management Officer, in that order. Section 05 flags the data points that justify each.
Minimum Staffing Plan
Five roles is the floor at which the department can run its own projects, keep the lights on, and not collapse when one person is on leave. Fewer than five means one person is both building and firefighting, which is how automation projects stall.
| Role | Level | Head-count | Reports to | Primary focus |
|---|---|---|---|---|
| Systems & Automation Manager | Mid/Senior | 1 | Managing Director | Strategy, prioritization, budget, stakeholder management |
| Business Process Analyst | Mid | 1 | Systems & Automation Manager | Process mapping, requirements, SOPs, change readiness |
| Systems Developer / Automation Engineer | Mid | 1 | Systems & Automation Manager | Builds workflows, integrations, low-code/custom apps |
| Database & ERP Administrator | Mid | 1 | Systems & Automation Manager | Systems of record, data integrity, reporting, backups |
| IT Infrastructure & Support Officer | Junior/Mid | 1 | Systems & Automation Manager | Network, hardware, helpdesk, basic security, both sites |
| Total | — | 5 | — | — |
Job Descriptions
Full role profiles for each of the five positions, ready to use for approval, advertising and the interview scorecards in Section 06. Each profile lists the certification required to be hired for the role and the roadmap for building toward full effectiveness on the job.
| Role | Prerequisite at hire | Roadmap to full effectiveness |
|---|---|---|
| Systems & Automation Manager | PMP or PRINCE2 Practitioner; ITIL 4 Foundation | ISO 9001 Internal Auditor (Yr 1) → CBPP or Prosci Change Management (Yr 2) |
| Business Process Analyst | IIBA Entry Certificate in Business Analysis (ECBA) | BPMN 2.0 / OCEB Fundamental (Yr 1) → CCBA + Lean Six Sigma Green Belt (Yr 1–2) |
| Systems Developer / Automation Engineer | Microsoft Power Platform Fundamentals (PL-900) | PL-100 + PL-500 (Yr 1) → PL-400 or equivalent RPA platform certification (Yr 1–2) |
| Database & ERP Administrator | A database administration certificate (e.g. Azure Database Administrator Associate, Oracle SQL Associate) | Certification on the chosen ERP/CMMS platform (Yr 1) → ITIL 4 Foundation + CDMP Associate (Yr 1–2) |
| IT Infrastructure & Support Officer | CompTIA A+; Network+ preferred | CompTIA Security+ (Yr 1) → MS-900 + CCNA if network complexity grows (Yr 1–2) |
Prerequisites are kept to one or two credentials so the candidate pool stays realistic for the Port Harcourt/Eket market; the roadmap column is what the Manager should budget and schedule in each role's first year, not a hiring bar. Because CMSL operates under ISO 9001/14001/45001, the Manager and Analyst roadmaps both point toward ISO Internal Auditor training — that's what lets the department's own systems stand up to the same audits the rest of the company already passes.
12-Month Rollout
Map the business, prove the department fast
Hire the Manager and Business Process Analyst first. Map the highest-friction processes (job card sign-off, QHSE incident reporting, procurement requisitions, leave/attendance) and pick 2–3 for a fast, low-code fix that department heads feel within weeks. Stand up basic IT hygiene (backups, MFA, access review) in parallel — it is cheap now and expensive to retrofit later.
Put in the systems of record that carry weight in an audit
Bring on the Developer and Database/ERP Administrator. Implement a proper maintenance/asset system (CMMS) tied to ISO document control, integrate leave/attendance with payroll, and build the MD/board dashboard for the metrics that matter (job cycle time, incident closure time, compliance status across both sites).
Extend coverage, formalize how the department runs
Hire the IT Infrastructure & Support Officer if not already on board, extend automation to remaining departments, and set a lightweight quarterly review with the MD (Section 06's Q49–50 cover exactly what that review should look for) to decide whether headcount needs to grow.
Interview Case Study Bank
50 scenario-based questions with model answers, grouped by the role they test most directly. Use them as case studies, not trivia: ask the candidate to think out loud, and score against whether their reasoning covers the same ground as the model answer, not whether the wording matches.
For each answer, rate 1–4: (1) misses the core issue, (2) identifies the issue but the approach is incomplete or risky, (3) sound approach covering the main considerations, (4) sound approach plus a consideration the model answer doesn't mention. A candidate scoring 3+ on 70% of their category's questions is a strong hire signal for that role.