We prepare complete AERMOD input files, organised project directories, and executable run scripts to ensure models run reliably without setup errors. All inputs are checked for consistency and structure to support reproducible work. Optional smoke tests are available to confirm the model initialises correctly and generates expected baseline outputs.
Review and validate all client-supplied project data, including site location, facility layout, emission sources, release parameters, pollutants, receptors of interest, building dimensions, terrain information, meteorological references, regulatory guidelines, and study objectives. Confirm completeness, accuracy, and consistency before model setup begins.
Prepare run-ready control files for AERMOD, AERMET, AERMAP, and BPIPPRM, based on the validated client inputs and agreed modelling assumptions. Ensure inputs are cleaned, structured, and internally consistent to avoid runtime errors and support reproducibility.
Deliver a well-structured project directory with executable run scripts (batch or PowerShell) and a clear README for operators. The directory layout is designed to promote transparency, traceability, and ease of handover across teams.
Conduct a short test run to verify that the models initialise correctly and produce expected baseline outputs. This is a functionality check only and does not constitute a full modelling assessment.
The service provides reproducible, executable model setups. Post-processing, detailed analysis, reporting, or regulatory submissions are not included unless separately contracted.
Summary of checks performed on client data (site, layout, sources, emissions, receptors, coordinates, buildings, terrain, met references, regulatory citations). Lists missing items, corrections made and items requiring client confirmation.
Clean, executable control files for AERMOD, AERMET, AERMAP and BPIPPRM. Files are formatted, validated and annotated where assumptions were applied.
Standardised directory layout separating inputs, preprocessors, logs and outputs. Includes a README describing file purpose, expected workflow and dependencies.
Executable .BAT and PowerShell scripts for model and preprocessor runs. Scripts include basic logging and inline notes for any required user edits.
Documented modelling assumptions, default values applied, and a concise change log of edits performed to client data. Designed to support auditability and regulatory review.
Short verification run to confirm models initialise and generate basic outputs. Delivered with a short results note and any immediate issues to address. Not a full validation or sensitivity analysis.
Package delivers reproducible, executable model setups and documentation. Post-processing, detailed analysis, reporting or formal regulatory submissions are outside this package unless separately agreed.
3–7 working days after intake and receipt of all required files and access credentials.
Complex projects may take longer; timeline confirmed during scoping. Expedited options may be available depending on capacity.
Small projects (e.g., single site, limited files)
Prices exclude third-party meteorological datasets and major rework. Larger or multi-site projects are quoted after intake and scoping.
No. By default, we deliver validated input files and project setup. We can run a short smoke test to confirm models initialise and produce baseline outputs. Full modelling runs, sensitivity cases and regulatory-ready reporting are handled under separate turnkey projects.
We require site location, facility layout, source characteristics, emission rates, pollutants, receptor locations or grids, building dimensions, terrain data, meteorological references, regulatory guidelines, and the study objectives. Clear, complete inputs are essential for producing run-ready files.
Yes. We provide batch (.BAT) or PowerShell scripts to automate runs of AERMOD and its preprocessors. These include basic logging and inline notes so your team can adapt them if needed.
A validated input package including: control files for AERMOD/AERMET/AERMAP/BPIPPRM, organised project folder structure, launch scripts, assumptions/change log, and (if requested) a smoke test confirmation note.
Minor adjustments (e.g. file corrections, naming updates) can usually be handled quickly. Significant changes, such as revised layouts, new scenarios or updated emissions, are scoped and quoted separately.
Yes. Control files are prepared using client-specified regulatory references and study objectives. However, responsibility for regulatory submissions, compliance demonstrations and reporting lies with the client unless a wider engagement is agreed.
No. Clients must provide meteorological data, terrain files and receptor specifications or confirm access to relevant sources. We clean and structure these datasets but do not generate them independently.
Post-processing, graphical outputs, compliance analysis, reporting, and direct regulatory submissions are not part of this package. These can be contracted separately if required.
We can tailor the scope to match your specific project needs — just let us know.