# Infor VISUAL Manufacturing Scheduling Checklist > Source: https://netray.co/tools/visual-manufacturing-scheduling-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A practical checklist for finding why VISUAL schedules do not match the floor: calendars, resource data, routings, lead times and release habits. ## Category other-erp ## Erp Infor VISUAL ## Industry Discrete Manufacturing ## Audience - Production planner - Scheduler - Plant manager ## Tool **Kind:** checklist **Scoring Note:** Count the items you can answer yes to. Anything marked critical that is a no is the first thing to fix, because bad data here produces schedules nobody trusts. **Groups:** #### Calendars and resources **Items:** **Text:** Every resource used in a routing has a shop calendar assigned. **Critical:** true Holidays and planned shutdowns are loaded for the current and next year. **Text:** Shift patterns in the calendar match the shifts people really work. **Critical:** true Resource capacity (number of machines or people) is current. Retired or moved machines are removed or flagged inactive. Overtime is handled by an agreed rule, not by editing calendars ad hoc. #### Routing and operation data **Items:** **Text:** Setup and run times are reviewed against actual labor data at least yearly. **Critical:** true Run time units (per piece, per hundred, per thousand) are consistent and correct. **Text:** Every operation has a resource, not a blank. **Critical:** true Outside service operations carry realistic transit and vendor lead times. Operations that can overlap are set up to overlap, and others are not. Scrap or yield assumptions are reflected in order quantities. Obsolete routings are inactivated so they cannot be picked up. #### Lead times and planning parameters **Items:** **Text:** Part lead times reflect actual purchasing and manufacturing experience. **Critical:** true Safety stock and order policies are set deliberately, not left at defaults. Demand sources (customer orders, forecasts) are included or excluded on purpose. Planning horizon covers the longest lead time in your product structure. Purchased parts have current supplier lead times in the purchasing data. Make or buy flags are right for every part that changes behavior in planning. #### Work order release discipline **Items:** **Text:** Planned orders are reviewed and firmed on a regular cadence. **Critical:** true Released orders have material available or a known shortage plan. Past due work orders are reviewed weekly and either expedited or rescheduled. Orders are not released far ahead of need just to keep people busy. Partial shipments and splits are recorded so the schedule reflects reality. Closed orders are closed promptly so they do not appear as open load. #### Floor feedback and reporting **Items:** **Text:** Labor reporting happens at the operation level so progress is visible. **Critical:** true Operators and supervisors can see the dispatch list or equivalent daily. Schedule changes are communicated to the floor and to sales. Late order and on time delivery are measured the same way every month. Someone owns scheduling data quality and has time to maintain it. ## Content **Intro:** When a VISUAL schedule does not match what the floor does, the cause is almost always data and habits rather than the scheduling engine. This checklist walks through the five places to look, in the order that usually pays off. **Sections:** #### How to use this checklist **Body:** Work through the groups with a planner and a shop floor supervisor in the same room. Tick each item only if you can point to where it is true, for example a calendar record or a routing. Mark critical items that fail, then fix those before touching anything else. Export the result to PDF to attach to an improvement ticket, or to Excel to track follow up. Repeat quarterly, because routings and calendars drift as products and shifts change. #### Why schedules fail: calendars and routings **Body:** Finite scheduling can only be as realistic as its inputs. If a resource has no calendar, or runs three shifts on paper and one in practice, every date downstream is wrong. The same applies to routing times. Run times that were set when a part was first quoted often differ from actual by a wide margin. Comparing labor ticket history with standard times for your top parts is one of the cheapest accuracy gains available. **Bullets:** - Calendars: match real shifts and holidays. - Resources: current capacity, no ghosts. - Times: reviewed against actual labor. - Units: per piece versus per hundred is a classic error. #### Lead times, parameters and release habits **Body:** Planning parameters decide what gets planned and when. Lead times that are too short create orders that are born late, while lead times padded for safety stack across levels and push dates out of reach. Release discipline matters just as much. Releasing everything early floods the floor and hides the real priorities. A weekly review of past due orders, with a clear owner, keeps the schedule honest. #### Common mistakes **Body:** Teams often adjust dates manually to make the schedule look right, which hides the data problem and has to be repeated every cycle. Others change calendars to force overtime instead of recording overtime as a separate decision. Finally, scheduling data has no owner, so nobody corrects routing times after a process change. Name an owner, review a short list of parts each month, and the schedule improves steadily. **Cta:** If you want scheduling exceptions, past due orders and routing time variances surfaced automatically from your VISUAL data, we can build a read-only report or assistant for it. **Faq:** #### Does this checklist assume finite scheduling? **Answer:** It works for both finite and infinite approaches. Calendars, routings and release habits matter in either case. Items about resource capacity are most valuable when you schedule finite capacity, but they also help when you only use capacity for load reports. #### How often should I review routing times? **Answer:** At least once a year for all active parts, and sooner for your highest volume or highest value parts. Compare labor ticket actuals against standard setup and run times and update where the gap is persistent and not explained by one off problems. #### What is the fastest fix for late orders? **Answer:** Check whether the orders were late at creation because lead times are too short, or became late because of material or capacity. The fix differs. Lead time data, shortage reports and a calendar check will usually tell you which one it is. #### Who should own scheduling data? **Answer:** A named planner or production engineer with time set aside for it. Without an owner, routing times, calendars and parameters decay. Even two hours a week reviewing a short exception list keeps the data usable. ## Search terms visual manufacturing scheduling, infor visual finite scheduling checklist, visual manufacturing scheduling setup, visual manufacturing late work orders, visual resource calendar setup, visual manufacturing scheduling best practices, visual scheduling problems, visual planning checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json