Job
Job Status
Job Status is a very important field used on the job form and for producing reports. When defining Job Status, you need to weigh the benefits and tradeoffs of closely tracking where your jobs are at, and the time needed to keep each job’s status up to date. In other words, do you need to track job status very closely by defining a number of detailed status values, or are you better served with fewer, more broadly defined status values.
In the example below, we broke job status into a handful of broad stages. Notice that the production stage “In Progress” is a catch all. No attempt is made to pinpoint which department the job is in once it’s released to the shop floor.
Before making your decision regarding job status, keep in mind that ShopPAK has a number of ways of tracking and measuring job progress. If you define and use “Department”, you’ll be able to see which department the job is in, without adding department-oriented status values. The other thing to keep in mind is Job Item and Work Order. A large job will have several Job Items and Work Orders. If this is the case, it makes more sense to focus on individual Job Item or Work Order status. In fact, it is impossible to get a reading as to where the overall job is at if you have a bunch of work orders in various stages of ‘Pending’, ‘Engineering’, ‘Purchasing’, ‘Released’, etc.
If you want to keep the ProjectPAK project status in sync with the ShopPAK job status, make sure that the ProjectPAK Project status values EXACTLY match the corresponding ShopPAK Job status values.
When you change a job status in ShopPAK that matches a status value in ProjectPAK, ShopPAK automatically changes the ProjectPAK project status accordingly. The same is true in ProjectPAK. If you change a ProjectPAK project status, and the project has a corresponding ShopPAK job, ProjectPAK will automatically change the Job status value.
Job Type
Job Type is also a very important field. It is used for job costing so you can categorize and contrast profitability by job type.
