Key responsibilities
Capacity assessment and developer services
• Assess connection applications, developer enquiries and planning applications against the utility’s connection and capacity criteria.
• Carry out network capacity checks and detriment analysis to determine the impact of proposed development flows on existing customers.
• Calculate development demands and flow rates by development type and usage profile.
• Undertake desktop network assessment where no calibrated model exists, using GIS, asset records and engineering judgement.
• Recommend engineered solutions where criteria are not met — pipe upsizing, on-site boosting, storage provision or alternative points of connection.
• Prepare technical response letters and draft formal responses for issue in accordance with the client’s delegated-authority and QA procedures, and maintain enquiry tracking records.
Hydraulic modelling support
• Support model build, verification and calibration tasks including data collection and validation, water and reservoir balances, demand analysis, and flow and pressure calibration.
• Build and run peaked and future-scenario models for growth and design horizon assessment.
• Undertake fire flow analysis and level-of-service checks.
• Report data gaps, GIS anomalies and modelling inconsistencies to the project lead.
Delivery and communication
• Work to client turnaround targets across a high volume of concurrent enquiries.
• Coordinate directly with overseas counterpart teams on data requests and technical queries.
• Prepare maps, schematics and supporting documentation using GIS.
• Contribute to process improvement and workflow automation where opportunities are identified.
Quality assurance and delegated authority
This role carries real technical decision-making, within a defined and supervised framework. What you decide independently, and what must be checked before it leaves the team, is set out clearly from day one.
What the role decides independently
• Determination of standard connection and capacity enquiries that fall clearly within the client’s published criteria, following a supervised assessment period. That period is normally expected to be approximately three months, but is dependent on demonstrated competency and client requirements.
• Selection of assessment method — model-based or desktop — for routine enquiries, and the supporting demand and flow calculations.
• Day-to-day technical correspondence with counterpart teams on data, records and clarifications.
What requires second-party technical check before issue
• All outputs during the supervised assessment period, without exception.
• Any assessment recommending network reinforcement, capital works or client expenditure.
• Any refusal, rejection or conditional response to a developer.
• Any case where the network fails to meet the client’s level-of-service criteria.
• Non-standard, phased or large-scale developments, and any case where desktop engineering judgement substitutes for a calibrated model.
What must be escalated
• Any proposal to vary, interpret or depart from the client’s published design criteria — escalate to the Technical Delivery Lead. This role does not hold authority to vary client criteria or commit AECOM to a technical position outside the agreed scope.
• Data quality or model confidence issues material enough to undermine the assessment.
• Any query touching scope, programme or commercial terms.
Record and audit
• Self-check every assessment against the client QA/QC checklist before submitting it for review.
• Maintain an auditable record for each enquiry — assumptions made, data sources used, criteria applied and the basis of the determination — sufficient for a third party to reconstruct the decision.
The boar re-runs this search every day and emails you what’s new — scraped straight from company career sites, no recruiter spam. Free.