Sage 100

Wondering how you would approach this client issue using WO vs Job Ops. I have several years experience in W/O (none in Job Ops) and did not implement this particular client's Sage company. Just coming in fresh like you with the following stated facts: Work orders are structured using a single router. Assume single level BOM and WO. W/O is released and Raw Materials auto-issued. Let's say Component A requires 1,000 materials, 250 consumed every 2 weeks on this W/O. Client wants the benefits of JIT ordering and scheduled releases. To compound matters, Qty On WO is inaccurate due to the need to rebuild sort files often. 1) Using only the work order module, how would you approach? 2) In Job Ops, better way to handle? 3) Other enhancements / ideas? @Sage100Routine @Businessofconsulting @JobOps @JoeBisaha @MadelineStefanou

Are these WO for stock or for an order?

In terms of JIT ordering, JobOps has the Component Exception Manager (CEM) to identify material requirements and cut PO's. If continuing to use WO, then you can license the Purchase Agent program from Synergistic Software, which serves the same purpose and integrates with WO.

@BethBowers let's assume these WOs are for stock, using a single-level BOM and 1-step router. @JohnHoyt thank you. Does Component Exception Manager also address the timing or scheduling of release / issues on work orders? And would it require them to adjust their router to breakout steps in greater detail or does CEM address that by simplifying the routing maintenance in Sage somehow? For all, I just realized I should restate line 3 of my above facts to say ""Component A requires 1,000 units, of which 250 units are consumed every 2 weeks on this W/O."" To me this is a problem of - they cannot get the visibility to scheduled releases per component if they are not entering the details - such as scheduled release dates. That alone could mean they must split work orders into sub work orders so they can set scheduled release dates on each sub work order. That is my tendency on how to approach in Sage W/O - subject to contrary / better advice from the brain trust. I think this would need to be addressed regardless of CEM or Purchase Agent - but maybe I am missing something?

No, I agree - there is no way for Sage to know about the 4 different scheduled releases without being told!

@AndrewHagenbach I have some more details, but have to leave for some meetings. I'll send those later.

Thanks Beth and John.

you could go old school with MRP and plug in the demand. That will push out work orders.

Release Date Options Sage Manufacturing (JobOps) @AndrewHagenbach I agree with your statement that if you do not define the scheduled release dates, there is no way to report or act based on those dates. That is a requirement with WO or JO. Here are some options when dealing with Sage Manufacturing (JobOps). (1) Separate Lines on the Sales Order Create separate lines on the Sales Order with separate Work Tickets for each line based on release dates (Promise Date by line). This is the primary method we have recommended, because it is the easiest to understand and control. Because the work tickets are in a range under the same Sales Order number, they appear on reports together with consolidated totals. Potentially a production manager may claim that they need to control all the production on a single document, but I am not convinced this is necessary. (See other options below that approach this.) (2) Single Sales Order Line Create a single line on the Sales Order resulting in a single Work Ticket. This keeps all the production on a single document. You could then create separate ""sets"" of steps on the Work Ticket corresponding to each scheduled release. Promise dates may be changed for each component on a step to correspond to release dates, although this is somewhat tedious when dealing with many components. The Component Exception Manager (CEM) may then be run based on cutoff dates to match the release dates. An option which provides the separation in option 1 without having multiple Sales Order lines is to structure the work ticket so each release is defined as a subassembly and separate subassembly work tickets are created using CEM and later closed to the parent work ticket. I'm not sure this is an improvement over option 1, but it can be done. (3) CEM Solution This option would allow you to order based on the dates without having to create multiple lines and multiple work tickets while working within the CEM. A cutoff date may be specified when running CEM for inventory requirements. This would still require that components for each release date be separated so they have different promise dates. Assuming initial release date requirements have been met, only the next promise date would be applicable, since component line quantities that have been issued or are on a PO, are not considered. Reorder point parameters also may come in to play here.

@JohnHoyt thanks for the meat to chew on. With this being a primarily make to stock environment I will have some judgment calls to make.

Sage Manufacturing does make to stock as well as it does make to order, and all of the same functions and concepts apply.