System BuildIntermediateEngineering
Engineering Project Management System Planning Prompt
Plans modules and data model for an engineering project management system spanning multiple sites and contractors.
Audience: Engineering PMs, IT · Last updated 2026-07-17
Contents
Scenario
Plans modules and data model for an engineering project management system spanning multiple sites and contractors.
Applicable Industry or Company Size
- Engineering
Preparation Before Use
- Current project processes.
- Site reporting method (LINE / Excel / system).
Variable Reference
| Variable | Description |
|---|---|
| [Company Name] | Your company's official name |
| [Annual Project Count] | Order-of-magnitude number of projects executed in the past year |
| [Main Project Type] | e.g., data-center cabling, low-voltage systems integration |
Full Prompt
Prompt
You are a digital transformation consultant for engineering companies. Plan an engineering project management system. [Background] - Company: [Company Name] - Annual Project Count: [Annual Project Count] - Main Project Type: [Main Project Type] [Output] 1. Data model: project, phase, task, resource, material, change order, acceptance, defect. 2. Roles and usage scenarios at the site and office levels. 3. Progress-reporting mechanism (daily / weekly / milestone). 4. Risk and change management process. 5. Cost and margin calculation fields and rules. 6. Integration recommendations with CostFlow, ERP, and finance systems. 7. Recommended rollout phases. [Judgment Criteria] Must account for unstable site connectivity and the need for offline record syncing. [Handling uncertain information] If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data. [Prohibited] - Do not fabricate statistics, regulation numbers, certification names, or client case studies. - When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own. [Final self-check] After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.
Usage Steps
- Fill in the variables.
- Validate reporting habits by interviewing site supervisors.
- Build a mobile MVP first.
Example
Data-center cabling projects usually need to track by floor, rack, and fiber core count.
Common Mistakes
- Designing the system from an office-only perspective, so field crews don't actually use it.
Cautions
- Involves subcontractor data access; permissions must be set carefully.
Last updated 2026-07-17
Need further customization to fit your company's process and industry?
AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.
