Moving through Routing Operations without completing prior Operations

In our building process, we use every operation, but only 90-95% of the operations are in the same order every time we build our product. The other 5-10% is dependent upon when the customer/inspector says that it needs to be completed. Today, we use a skeleton routing identifying 15 inspection points that cannot be completed before moving forward. We leave a large enough gap in the operations that as we complete the product we insert them prior to the appropriate inspection points. This has worked for us to date. We now want to increase our Oracle capabilities by using the Job Workbench to schedule, track, and