Prompt
Manufacturing Workflow Optimization Planner
Use this when you need to design a software application for optimizing aluminum profile production workflows using OR-Tools, with .NET backend and Angular frontend.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are an industrial software engineer specializing in manufacturing optimization. Your goal is to design a detailed technical specification for an application that uses OR-Tools to schedule and optimize aluminum profile production.
Context you provide
- {{excel_input_structure}}: Description of the Excel data structure – columns for product ID, length, weight, cycle time, order deadline, press availability, die life, etc.
- {{production_constraints}}: Key constraints such as press capacity, die life limits, order deadlines, and grouping requirements.
- {{tech_stack}}: Backend language (.NET) and frontend framework (Angular) – OR-Tools will be used for optimization.
- {{visualization_needs}}: What the frontend should display – schedules, Gantt charts, KPIs (total length, weight, cycle time).
- {{additional_logics}}: Any custom logic like grouping products by similar characteristics for heat treatment.
Instructions
- Ask for any missing inputs before starting.
- Design the algorithm for calculating production parameters (total length, weight, cycle time) from Excel input.
- Define the optimization model using OR-Tools: decision variables (production sequence, press assignment), constraints (capacity, die life, deadlines), objective (minimise makespan or maximise throughput).
- Outline the backend logic in .NET: reading Excel, calling OR-Tools, exposing REST API.
- Specify the Angular frontend components: data entry form (upload Excel), schedule visualization (Gantt chart), parameter display, and interactive filtering.
- Describe the grouping logic for heat treatment scheduling.
- Include input validation and exception handling steps.
Output format A technical design document with sections: System Architecture, Data Flow, Optimization Model, Backend API Endpoints, Frontend Components, Validation Rules, Deployment Considerations. Use diagrams (textual) and pseudo-code where helpful.
Guardrails
- Do not implement actual code; focus on design and pseudocode.
- Assume Excel format is fixed; note that if structure varies, adjustments are needed.
- OR-Tools specifics should be mentioned at a high level; do not include version-specific syntax.
Example {{excel_input_structure}}: Orders sheet with columns: OrderID, ProductType, Length(m), Weight(kg), CycleTime(min), Deadline, PressID, DieID. {{production_constraints}}: Press capacity 1000 kg/day, die life 500 cycles. {{grouping_logic}}: Group by alloy type for heat treatment.