XML Data Exchange Between Drain Cleaning Companies and Engineering Firms

Sewer inspections involve several parties: the contractor inspects pipes with a camera and documents findings, an engineering firm assesses their condition and plans repairs, and the client needs documentation that can be verified. For this chain to work, data has to be handed over in an agreed format. In practice, that is often an XML file.

Why XML for data exchange?

XML (Extensible Markup Language) describes data in a fixed, machine-readable structure. An associated schema – usually an XSD file – defines which elements may appear, which are required and which values are allowed. This makes it possible to check a file automatically before it is passed on.

For exchanges between different companies, this has a major advantage: sender and recipient don’t need to use the same software – they only need to agree on the format. In German-speaking countries, the sewer and wastewater sector uses established exchange formats, such as the ISYBAU exchange formats or formats based on the DWA M 150 guideline. Which format and version is required is usually specified by the client.

Common problems in practice

Anyone who organizes data exchange manually today knows the pitfalls:

• Missing required fields: the recipient rejects the file because individual fields are empty.
• Inconsistent coding: findings are recorded with different abbreviations or as free text.
• Missing media files: images or videos are referenced in the XML file but missing from the delivery – or vice versa.
• Version conflicts: sender and recipient work with different versions of the same format.
• Rework in the office: data from the inspection software is completed by hand before sending.
• Queries without context: responses arrive by email and first have to be matched to the right records.

Each of these points costs time – and every manual correction is another source of errors.

How an automated handover works

An interface turns the handover into a fixed, traceable process:

1. Capture: job and inspection data are recorded in a structured way – in the inspection software, a mobile app or job management.
2. Generate: the interface compiles the data and writes it in the required XML format.
3. Validate: the file is checked against the schema and against business rules. Errors are reported clearly.
4. Transfer: the validated file is sent – together with images and videos – to the engineering firm via the agreed channel.
5. Process responses: receipts and review results flow back and update the status of the job.

Validate before you transfer

The most important building block is validation before sending. It should cover several levels:

• Well-formedness: is the file technically correct XML?
• Schema: do elements, order and data types match the specified schema?
• Business plausibility: do values fit together, such as positions relative to the length of a section? Does every finding type have the required details?
• Completeness of the delivery: do all referenced image and video files exist?

The following heavily simplified example illustrates the principle:

<Inspection job="A-1042">
  <Section id="S-07" length="42.5">
    <Finding position="12.4" type="Crack" image="S07_0124.jpg"/>
    <Finding position="31.0" type="RootIntrusion" image="S07_0310.jpg"/>
  </Section>
</Inspection>

Don’t forget the responses

Many solutions stop once the file has been sent. For a closed loop, however, the way back is just as important: has the engineering firm received the data? Was it accepted, or is information missing? What is the resulting assessment? If this information is automatically assigned to the right job, the office can always see where a case stands – without follow-up calls or emails.

What to clarify before an interface project

• Which exchange formats and versions do your clients require?
• Who provides the schema files and code lists?
• Which details are required and which are optional?
• How are images and videos handed over, and how are they named?
• Which channel is used for the transfer – upload portal, secure file transfer or email?
• Who is notified when validation fails, and how are errors corrected?

Conclusion

An automated XML exchange between drain cleaning companies and engineering firms saves more than typing. It makes data quality verifiable, prevents rejected deliveries and creates a traceable status for everyone involved. What matters most is careful validation before sending – and a return channel that assigns responses to the right job.