Here, we used the Common Workflow Language (CWL) standards to describe our workflow and enable technical interoperability in MAW. There are three individual sub-workflows named MAW-R, MAW-MetFrag, and MAW-Py, each described using CWL. Each step has inputs (e.g., .mzML files as inputs for MAW-R), Docker-format software container images (e.g., zmahnoor/maw-r:1.0.8), scripts (e.g., MAW-R.r) or command line tools (e.g., MetFrag), arguments, and outputs (e.g., outputs of MAW-R include CSV and TXT files). The outputs from MAW-R are used as inputs in MAW-MetFrag and MAW-Py, and MAW-MetFrag also produces outputs that are inputs for MAW-Py (Figure ). MAW-Py then analyses the outputs of MAW-R and MAW-MetFrag to generate the final results. Data portability is supported by CWL's feature of explicitly differentiating between ordinary strings and file paths which enable MAW to run locally or remotely. Figure illustrates the sub-workflows of MAW, together with inputs and outputs.