So we have a very unique business and we’re in the process of moving to Kinetic 2025.2.
For reference, we make bulletproof solutions for commercial and private sector.
Our systems are mostly custom and but are sometimes comprised of make to stock parts. Sales Orders come in and MRP generates unform jobs. These get reviewed by our PMs who contact the customer and get a general idea of scope and and desired ship date.
They then go to engineering to create drawings which are sent back to customer for approvals. Once approved engineer cut sheets are made and the jobs are “approved for release” and sent to me to schedule and release via MES.
Leadership decided to run infinite scheduling (we do not have APS)
How do I check/compare the jobs I’m about to release against the existing load on the resources before I commit to see if they have capacity?
Also have been reading that unfirm jobs show up as load against resources which doesn’t make sense but want to clarify.
Is finite scheduling recognized by MRP during unfirm job creation, firming the job or when scheduling and releasing?
Sorry for all the questions but or contact helping us integrate is less then help or knowledgeable for that matter.
Without APS, can finite scheduling only be set at each resource or is there a global way of doing it?
Do unfirm jobs show load against resources? Seems only firm jobs should.
What I’m really looking to do is have a before and after comparison of existing load on the floor and how the firmed jobs ready for me to release would affect existing load. So I can see if I need to get with PMs to move the dates out.
Basically the best and cleanest way to have a existing vs potential.
I don’t worry about unfirm as there can be quite a bit of time between MRP creating an unfirm job and the PM reviewing it and then finally firming. Then even more time waiting for customer approval and the engineers approving for me to release to floor.
I have heard of global scheduling but I think that accounts for unfirm as well so that’s not what I want to see as unfirm jobs can clutter the results if putting load on a resource.
You are going to have to do some trial an error on this to know. All of us have done the work to know our environments and there are so many variables that you have figure out your scenarios.
I ended up not using mrp as we are so custom that I can create specific jobs from a dashboard faster than fixing an mrp created job.
