Documenting Real Engineering Projects

On 18 June 2026, the Association of Intelligent Engineering and Technology (AIET) held a workshop on writing engineering application cases. The exchange covered project facts, technical pathways, outcome statements, and appropriate boundaries for public communication. It was intended for project leads from member organizations, content authors, research assistants, and staff responsible for maintaining related materials.

The workshop emphasized that an engineering application case is first a verifiable project record and only then a communication document. A case should define its background, practical problem, participating parties, implementation scope, and period. It should not present conclusions without the conditions that produced them or describe intended objectives as completed outcomes.

Core Elements of a Case

• Project background: the engineering context, existing problem, and need for the work.
• Technical pathway: solution selection, implementation steps, system boundaries, and relationship to existing facilities.
• Evidence: traceable data, testing records, acceptance documents, or public materials supporting the account.
• Outcomes and limitations: validated results, applicable conditions, and matters requiring further observation.
• Organizational roles: a clear distinction among the client, implementer, technology provider, research team, and documentation party.

The exchange also addressed the use of data and images. Metrics should state their method, comparison basis, and period. Diagrams and site photographs require appropriate permission. Client names, internal systems, and non-public parameters should be authorized or appropriately anonymized before publication.

Avoiding Overstatement and Confusion

Titles and summaries should remain consistent with the evidence in the body and should avoid unsupported claims such as industry first or comprehensive leadership. Where several parties contribute, their responsibilities should be stated separately. AIET's organization, presentation, or evaluation of a case does not alter the original implementation or ownership relationship.

Next Steps

Participants may use the workshop structure to improve non-sensitive case materials. AIET will progressively organize content suitable for public release through the Engineering Application Cases section and add supporting notes where needed. Every public case should be based on authentic project materials, with original project files and formal evidence remaining authoritative.