# Scheduling Engineer-to-Order Machine Builds When Designers and Test Floor Are Shared > Source: https://netray.co/resources/scheduling-engineer-to-order-machine-builds > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Knowledge Base ## Short answer How machine builders schedule several concurrent custom projects across a few designers, controls programmers and a shared build floor without overpromising dates. ## Category erp-general ## Content **Intro:** Scheduling engineer-to-order machine builds is a project resource problem: three to six concurrent projects compete for a handful of mechanical designers, one or two controls programmers, a fabrication cell, and limited test floor space. Quoted delivery dates usually assume each project gets its engineers full time, which is never true. Realistic dates come from loading engineering capacity by discipline and week, not from ERP shop routings. **Sections:** #### Engineering Is the Real Bottleneck **Body:** Most machine builders can add fabrication through outside vendors and overtime. They cannot easily add a controls programmer who knows their PLC standards, or a designer who knows their platform. A five-person engineering group might carry two projects each in different phases. When one customer slips on approvals, the whole queue shifts. Treat each engineer-discipline pair as a finite resource with weekly hours, subtract vacation and non-project time such as quoting support and service calls, and plan against the remainder, often only 60 to 75 percent of a calendar week. **Bullets:** - Plan by discipline: mechanical, electrical, controls, documentation - Subtract quoting support and service calls from capacity - Name the individual for scarce skills such as robot or vision programming - Show resource load across all active projects in one view #### Milestones That Drive Dates **Body:** Use a short list of gating milestones per project: kickoff, customer design approval, design freeze, long-lead PO release, mechanical build complete, controls checkout, FAT, shipment, and site acceptance. Customer approvals are dependencies you do not control, so record the approval date requested and the actual date, and let the schedule move automatically when the customer is late. That history is also your evidence in a change order or delay discussion. Long-lead items, servo drives, robots, custom gearboxes, and some controls hardware, should be ordered at the earliest safe milestone, and the schedule should show their lead times explicitly. #### Quote Dates Against Capacity, Not Optimism **Body:** Before giving a delivery date, check the load: how many engineering hours are already committed in the weeks this project needs, and which individuals are involved. If the answer is that controls is fully booked for ten weeks, the honest date starts after that, or you need contractor capacity. Some builders add a simple capacity check to their quote checklist. Others use project scheduling tools such as Microsoft Project, Smartsheet, or the ERP project module. The tool matters less than having a single list of resource hours that gets updated weekly. #### Shop Floor and Test Floor Capacity **Body:** Fabrication, assembly, and wiring follow engineering releases. A common failure is that three machines reach assembly together because their engineering slipped in the same direction, overloading wiring technicians and the test floor. FAT space is a resource, so schedule it like one, including time for customer visits. Use finite scheduling in the ERP for in-house machining if you have it, and a simpler weekly assembly board for build and test. Do not push project-level precision into the ERP if the data entry burden outweighs the benefit. #### Where AI Helps and Where It Does Not **Body:** AI can compare current resource loads against historical durations, for example how long similar mechanical designs actually took, and warn when a planned date is tighter than any comparable past project. It can summarize why previous projects slipped. It cannot negotiate with customers about approval dates or know that your best programmer is leaving. If you run two or three projects at a time, a shared spreadsheet and a weekly meeting are usually enough. **Cta:** Netray can pull historical durations and engineering hours from your ERP to sanity-check delivery dates before you promise them. **Faq:** #### How do you schedule multiple custom machine projects at once? **Answer:** Load engineering capacity by discipline and week across all projects, schedule gating milestones with customer approval dependencies, and update the plan weekly. Check available capacity before quoting a delivery date, rather than assuming dedicated engineers. #### What is a realistic lead time for a custom machine? **Answer:** Lead times vary widely with complexity, from a few months for modest machines to a year or more for large automated lines. Long-lead components and customer approval cycles often dominate. Base promises on your recent actual durations by project type. #### Does ERP finite scheduling work for ETO? **Answer:** It helps for the in-house machining and fabrication portion once routings exist. It is usually weak for engineering work, which happens before routings are defined. Most builders pair it with a project schedule or resource spreadsheet for design disciplines. ## Related Slugs - finite-capacity-scheduling-guide - ai-production-scheduling-optimization - engineer-to-order-erp-challenges - infor-ln-project-based-manufacturing ## Search terms scheduling engineer to order projects, machine builder project scheduling, engineering capacity planning custom machinery, ETO production scheduling, resource loading engineering projects, custom machine delivery date promising --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json