How to Integrate ASAS-AI into Your Engineering Workflow
A practical walkthrough for civil and structural engineers in Qatar — covering how to set up ASAS-AI, use Smart Commands effectively, generate compliant documents, and embed the platform into real project tasks.
1. What ASAS-AI is — and what it is not
ASAS-AI is an AI assistant built specifically for engineers working in Qatar and the GCC. It runs on Claude, one of the leading large language models, and is layered with a detailed engineering knowledge base covering Qatar’s local codes, standard specifications, and project documentation formats.
Understanding its purpose helps you use it more effectively. ASAS-AI is a workflow tool, not a design software. It does not replace your structural analysis programs, BIM models, or QS software. What it does is handle the knowledge-intensive, writing-intensive, and document-intensive parts of engineering work — the tasks that consume time but rarely require a calculator.
Think of ASAS-AI as a technically fluent colleague who knows Qatar’s codes well, writes quickly, and is always available — not as an autonomous engineer. You direct the work; it executes and drafts.
What ASAS-AI handles well:
- ✓ Drafting FIDIC contract notices, letters, and formal correspondence
- ✓ Generating QCS-referenced specifications and submittals
- ✓ Preparing GSAS/LEED documentation and compliance checklists
- ✓ Explaining code clauses, design standards, and regulatory requirements
- ✓ Creating and formatting engineering reports, RFIs, and technical memos
- ✓ Producing DXF sketches, charts, and diagram visuals from a text description
- ✓ UPDA exam study notes, code summaries, and worked explanations
Always review AI-generated engineering content before submission. ASAS-AI can make errors on specific numeric calculations or code references. Use it as a first draft and apply your professional judgment — as you would with any junior colleague’s work.
2. Getting started: your first session
Access ASAS-AI at ai.asddconcept.com. Register with your email address — the Free plan activates immediately with 100,000 tokens per month and no credit card required.
Register and log in
Create your account at ai.asddconcept.com. Your membership tier, token balance, and reset date are visible in your profile dashboard.
Open a new conversation
Conversations are stateful — the assistant remembers what you have said earlier in the same session. Start each new project task in a fresh conversation to keep context clean.
Provide project context upfront
Before asking a question, briefly state your project type, location, applicable code, and your role. The more context you give, the more targeted and accurate the output will be.
Use Smart Commands or free-form chat
For structured document tasks, use the Smart Commands library. For open-ended questions, code interpretation, or brainstorming, use the chat interface directly.
Review, refine, and export
Iterate on the output within the conversation — ask for edits, additions, or a different tone. When satisfied, export to your required format: Word, PDF, Excel, PowerPoint, or DXF.
Instead of: “Write a FIDIC notice.” — try: “I am the contractor’s engineer on a road widening project under an Ashghal contract using FIDIC Red Book 1999. The employer’s representative has issued a variation instruction that extends our scope without adjusting the contract price. Draft a Clause 20.1 notice preserving our right to claim additional cost and time.”
3. Using Smart Commands in your workflow
Smart Commands are pre-built engineering workflows. Instead of writing a complex prompt from scratch, you select the relevant command, provide a few parameters, and receive a structured output. They are designed around real documentation tasks engineers perform regularly on Qatar projects.
There are currently 75+ commands across 14 categories:
Example: FIDIC Clause 20.1 — Notice of Claim
- Properly structured formal notice with contract reference and clause citation
- Notice date, event description, and claim basis under Sub-Clause 20.1
- Statement of intent to submit a fully detailed claim
- Correct signatory block and distribution list format
- Ready to export as Word or PDF
Example: GSAS compliance checklist
- Structured checklist mapped to GSAS 2019 credit categories
- Minimum point thresholds per category for 3-star target
- Applicable measures for the building type and climate zone
- Notes on documentation required at each GSAS submission stage
Commands produce the best results when you include: the project type, applicable code edition, the specific task, and any important constraints (deadlines, parties involved, contract clause numbers). Think of it as briefing a colleague, not searching a database.
4. Generating and exporting documents
Every conversation in ASAS-AI can be converted into a downloadable file. The document engine runs server-side — meaning the formatting and file generation happen on the platform, not in your browser, which produces cleaner and more reliably structured output.
Word Document
Formatted report, letter, notice, or submittal ready for review and signature.
Styled, paginated output suitable for formal submission or client distribution.
Excel Spreadsheet
Structured data tables, calculation summaries, and inspection record formats.
PowerPoint
Slide decks for design presentations, project updates, or technical briefings.
DXF / AutoCAD
AutoCAD-compatible drawing file generated from a text description of a layout or diagram.
Charts & Diagrams
ECharts data visualisations and Mermaid flowcharts rendered as vector graphics.
Export workflow
Generate the content in chat
Use a Smart Command or a free-form prompt to produce the document content. Iterate until the structure and information are correct.
Select the export format
Tell ASAS-AI which format you need: “Export this as a Word document” or “Generate a PDF version of this letter.”
Download and finalise
The file is generated and made available for immediate download. Open in your preferred application, add your signature block or company letterhead, and submit.
5. Working with Qatar regulatory standards
ASAS-AI is trained on the specific codes, standards, and procedures that govern engineering projects in Qatar. The following table summarises the main regulatory frameworks the platform covers and typical tasks where it is most useful.
| Standard / Body | Coverage | Typical use in ASAS-AI |
|---|---|---|
| QCS 2014 | Qatar Construction Specification — full code | Specification writing, clause interpretation, submittal checklists |
| GSAS / QSAS | Qatar sustainability rating system | Credit checklists, documentation summaries, compliance notes |
| Ashghal | Road design, infrastructure, drainage standards | Design requirement summaries, submission format guidance |
| KAHRAMAA | Electrical, water, and MEP regulations | MEP compliance checklists, regulation interpretation |
| UPDA | Engineer registration and exam framework | Exam preparation notes, code summaries, worked examples |
| FIDIC (Red/Yellow/Silver) | International construction contracts | Notices, claims, EOT letters, correspondence under specific clauses |
| Eurocode / BS | European structural and civil standards | Code clause lookups, design requirement explanations |
| ACI / AISC / AASHTO | American concrete, steel, highway standards | Design provision summaries, comparison with local code requirements |
When asking about a specific code, state the edition (e.g., “QCS 2014”, “FIDIC Red Book 1999”, “GSAS 2019”). Code editions differ — specifying the correct one ensures the response references the right clause numbers and requirements.
6. Real workflow scenarios
Below are four common engineering situations and how a practitioner would use ASAS-AI to handle them efficiently.
Scenario A — Contractor’s engineer, variation claim
FIDIC Red Book 1999 · Ashghal project · Structural worksScenario B — Consultant preparing a GSAS submission
GSAS 2019 · Mixed-use tower · Design stageScenario C — Structural engineer, design basis memo
Eurocode · RC frame building · Submittal to AshghalScenario D — Graduate engineer, UPDA exam preparation
UPDA Civil Engineering · Structural category7. Choosing the right plan
ASAS-AI uses a token-based model. Tokens measure AI usage — a short question uses fewer tokens than generating a multi-section report. The table below gives a practical guide to which plan fits different usage levels.
| Plan | Tokens/month | Price | Suited for |
|---|---|---|---|
| Free | 100,000 | $0 | Occasional use, exploration, UPDA study |
| Pro | 250,000 | $7 / mo | Individual engineers with regular document tasks — several per week |
| Elite | 1,000,000 | $17 / mo | Active practitioners producing multiple documents and reports daily |
| Elite Plus | 2,000,000 | $40 / mo | High-volume users, teams, or engineers managing multiple concurrent projects |
Begin on the Free plan to understand your actual usage patterns. Most individual engineers working on one to two active projects will find the Pro plan ($7/month) sufficient for day-to-day document and correspondence tasks.
8. Tips for getting better results
Give the platform your project context at the start
State the project name or type, the applicable contract form, relevant codes, your role (contractor / consultant / client), and the task at hand. ASAS-AI uses this context throughout the conversation.
Treat the first output as a draft
Ask for revisions within the same conversation: “Make the tone more formal,” “Add a section on programme impact,” or “Shorten the introduction.” The assistant remembers what it produced and refines accordingly.
Upload reference documents to anchor the response
You can attach PDFs — specifications, drawings, contracts — and ask ASAS-AI to work with them. For example: upload a specification section and ask “Does this clause comply with QCS 2014 Section 6.3?” or “Summarise the inspection requirements from this document.”
Break large documents into sections
For a 20-page report, generate section by section rather than asking for the whole document at once. This produces better-quality output and lets you review and redirect at each stage before continuing.
Use it as a code clause interpreter
Rather than searching through a 600-page specification, ask ASAS-AI directly: “What does QCS 2014 Section 5 say about compaction testing for sub-base?” The platform interprets and explains the requirement in plain language, with the clause reference.
Verify clause numbers and numeric values independently
ASAS-AI is highly reliable on document structure, tone, and general engineering knowledge. For specific clause references, acceptance criteria, and numeric design values, cross-check against the actual code before submitting work to a client or authority.
