Electrical Document Generation
Overview
An AI-native document generation skill that produces all electrical engineering documents through structured data injection into verified templates. Covers four phases: Concept, Design, Construction/Testing, and Commissioning with quality validation and version control.
When to Use This Skill
- Generating any electrical engineering deliverable document
- Producing SLDs, cable schedules, test reports, commissioning documentation
- Creating O&M manuals, certificate of compliance packages
- Producing regular reports (daily electrical logs, progress reports)
- Any structured electrical document requiring code-compliant content
Prerequisites
- Document template (verified and current with applicable codes)
- Structured input data (from power system models, calculations, test results)
- Standards and code references (IEC, NEC, NFPA 70E, local regulations)
- Template configuration (document type, voltage level, project context)
Step-by-Step Execution
Step 1: Select Document Template
- Identify document type from phase (Concept, Design, Construction, Commissioning)
- Select appropriate template with correct version number
- Verify template is current with applicable codes
- Load template configuration parameters
Step 2: Extract Data from Source Systems
- Pull structured data from power system models (bus data, equipment schedules)
- Extract calculation results (load flow, short circuit, protection settings)
- Retrieve test results (insulation resistance, continuity, earth resistance)
- Gather LOTO procedures, commissioning results, as-built changes
Step 3: Validate Data Completeness
- Verify all required data fields populated
- Check data ranges are within expected limits
- Confirm code references are current
- Flag any missing or inconsistent data
Step 4: Inject Data into Template
- Map structured data to template placeholders
- Apply conditional logic (include/exclude sections based on data)
- Generate narrative text from structured data
- Insert tables, diagrams, schedules as configured
Step 5: Quality Validation
- Run completeness check against document specification
- Verify code compliance (all referenced clauses current)
- Check cross-references within document resolve
- Validate numerical data against source systems
- Generate quality report with any issues found
Step 6: Generate Output
- Produce output in required format (PDF, DOCX, structured JSON, Excel)
- Apply project branding and formatting
- Include revision control information
- Generate metadata (author, date, version, applicable codes)
Step 7: Archive with Version Control
- Store document in document management system
- Create version record with change history
- Update document status (draft, review, approved, issued)
- Distribute to stakeholders per project workflow
Success Criteria
- 99%+ data accuracy vs source systems
- All required document sections complete
- Code references current and accurate
- Document format meets project specification
- Version control and audit trail maintained
Common Pitfalls
- Outdated Templates: Templates not updated when codes change → reference outdated requirements
- Missing Input Data: Calculation or test results not available → incomplete documents
- Code Changes: Standards updated but templates not reviewed → non-compliant documents generated
- Data Mismatch: Input data inconsistent with actual conditions → inaccurate documents
- Format Errors: Output generation fails due to template-data incompatibility → document delay
Cross-References
- 00860 Domain Knowledge: Document generation pipeline (Part 8, Part 12)
- Electrical SLD Processing: Provides power system model data
- Electrical Commissioning: Provides test results for commissioning documents
- LOTO Compliance: Provides procedures for safety documentation
- Standards: IEC 60617 (symbols), NEC, NFPA 70E
Usage Example
Scenario: Generate cable schedule for 11kV switchgear installation
Step 1: Select cable_schedule_11kv_v3.docx template
Step 2: Extract data from power system model (cable types, routes, terminations)
Step 3: Validate all cables have source/destination, size, type, length
Step 4: Inject data: cable ID → table row, routing → path description
Step 5: Quality check: all cables present, sizes match calculations, terminations consistent with SLD
Step 6: Generate cable_schedule_11kv_switchgear_revA.xlsx + .pdf
Step 7: Archive with revision A, distribute to cable laying team
Metrics
- Template coverage: 95%+ of document types supported
- Data accuracy: 99%+ vs source systems
- Review cycles: 50%+ reduction vs manual preparation
- Compliance: 100% of documents within regulatory timeframes
1---2name: electrical-document-generation3description: Electrical Document Generation4---56# Electrical Document Generation78## Overview9An AI-native document generation skill that produces all electrical engineering documents through structured data injection into verified templates. Covers four phases: Concept, Design, Construction/Testing, and Commissioning with quality validation and version control.1011## When to Use This Skill12- Generating any electrical engineering deliverable document13- Producing SLDs, cable schedules, test reports, commissioning documentation14- Creating O&M manuals, certificate of compliance packages15- Producing regular reports (daily electrical logs, progress reports)16- Any structured electrical document requiring code-compliant content1718## Prerequisites19- Document template (verified and current with applicable codes)20- Structured input data (from power system models, calculations, test results)21- Standards and code references (IEC, NEC, NFPA 70E, local regulations)22- Template configuration (document type, voltage level, project context)2324## Step-by-Step Execution2526### Step 1: Select Document Template27- Identify document type from phase (Concept, Design, Construction, Commissioning)28- Select appropriate template with correct version number29- Verify template is current with applicable codes30- Load template configuration parameters3132### Step 2: Extract Data from Source Systems33- Pull structured data from power system models (bus data, equipment schedules)34- Extract calculation results (load flow, short circuit, protection settings)35- Retrieve test results (insulation resistance, continuity, earth resistance)36- Gather LOTO procedures, commissioning results, as-built changes3738### Step 3: Validate Data Completeness39- Verify all required data fields populated40- Check data ranges are within expected limits41- Confirm code references are current42- Flag any missing or inconsistent data4344### Step 4: Inject Data into Template45- Map structured data to template placeholders46- Apply conditional logic (include/exclude sections based on data)47- Generate narrative text from structured data48- Insert tables, diagrams, schedules as configured4950### Step 5: Quality Validation51- Run completeness check against document specification52- Verify code compliance (all referenced clauses current)53- Check cross-references within document resolve54- Validate numerical data against source systems55- Generate quality report with any issues found5657### Step 6: Generate Output58- Produce output in required format (PDF, DOCX, structured JSON, Excel)59- Apply project branding and formatting60- Include revision control information61- Generate metadata (author, date, version, applicable codes)6263### Step 7: Archive with Version Control64- Store document in document management system65- Create version record with change history66- Update document status (draft, review, approved, issued)67- Distribute to stakeholders per project workflow6869## Success Criteria70- 99%+ data accuracy vs source systems71- All required document sections complete72- Code references current and accurate73- Document format meets project specification74- Version control and audit trail maintained7576## Common Pitfalls77- **Outdated Templates**: Templates not updated when codes change → reference outdated requirements78- **Missing Input Data**: Calculation or test results not available → incomplete documents79- **Code Changes**: Standards updated but templates not reviewed → non-compliant documents generated80- **Data Mismatch**: Input data inconsistent with actual conditions → inaccurate documents81- **Format Errors**: Output generation fails due to template-data incompatibility → document delay8283## Cross-References84- 00860 Domain Knowledge: Document generation pipeline (Part 8, Part 12)85- Electrical SLD Processing: Provides power system model data86- Electrical Commissioning: Provides test results for commissioning documents87- LOTO Compliance: Provides procedures for safety documentation88- Standards: IEC 60617 (symbols), NEC, NFPA 70E8990## Usage Example91```92Scenario: Generate cable schedule for 11kV switchgear installation93Step 1: Select cable_schedule_11kv_v3.docx template94Step 2: Extract data from power system model (cable types, routes, terminations)95Step 3: Validate all cables have source/destination, size, type, length96Step 4: Inject data: cable ID → table row, routing → path description97Step 5: Quality check: all cables present, sizes match calculations, terminations consistent with SLD98Step 6: Generate cable_schedule_11kv_switchgear_revA.xlsx + .pdf99Step 7: Archive with revision A, distribute to cable laying team100```101102## Metrics103- Template coverage: 95%+ of document types supported104- Data accuracy: 99%+ vs source systems105- Review cycles: 50%+ reduction vs manual preparation106- Compliance: 100% of documents within regulatory timeframes