By popular demand - you can now navigate directly to the WO in job tracking from the operations card.
The goal of this update is to give users more flexibility and keep work order data up to date. Previously, these functionalities were more restrictive — for example they did not support updates when a work order or associated jobs are in-progress. In general, the updated restrictions are:
When updating an outside processing operation via API, you could add a lead time, but not cost information. Now, there’s a new object called OutsideProcessingCost, structured as seen in the image. This allows you to set the cost of the outside processing operation as either a fixed or per unit cost.
Share ->We're releasing a substantial performance update to the items grid. Functionality should be unchanged, but this should fix timeouts that were observed when sorting or searching by values that required re-calculating data in the entire grid (such as sorting by supply or inventory).
Back by popular demand, we're reintroducing the "Has Timing Issue" filter and KPI for the demand and purchasing planning pages. This filter flags items for which there is unsatisfiable demand at any point in time, even if there will eventually be enough supply to cover that demand at a later date. This involves a significant refactoring of the data structures underlying the grids, so it'll be behind a feature flag at first. We also expect some moderate performance improvements with the feature flag enabled.
In addition, price break information will now be correctly respected on the Unit Cost and Total Cost columns of the purchasing planning grid, which had previously reflected the "un-broken" costs.
With raw materials, we needed to add some additional logic around how to split the material on each of the split operations. This has been shored up to ensure the appropriate amount of material is on each instance of the split operation.
It’s been possible to associated jobs to purchase orders in Fulcrum, but the association applied to the entire PO and couldn’t specify which line item was for which job. Now we’ve fully released the ability to associated job to PO’s on the line item level. This association is also visible in receiving, so that receivers can stage items as needed.
Share ->We’ve refreshed the PreOperation, In-Progress, and PostOperation Checkpoints experience in Job Tracking to better align with the rest of the Job Tracking interface.
What’s new:
Pre & Post Checkpoint Improvements: A more compact window for better visibility when working with attachments
In-Progress Checkpoint Improvements: Sticky label and description column for consistent visibility of target, tolerance range, and graphs while horizontally scrolling
Some customers are obligated to show how heavy things are to their shippers so that if the truck is pulled over they can show documentation for how much the parts weigh in total. We will now carry over part weights from two areas. If the item being shipped is a Fulcrum material item, we will carry over that weight automatically. If the item is a normal buy item or make item, we will carry over the weight from the Sales > Shipping section on the Item page.
Note: this currently only supports weight in pounds, as the Shipping section doesn't support other UOM conversions.
The team is continuing to enhance the materials workflows. Recently, they’ve been focused on purchase planning. Here are some of the improvements there:
By popular demand, you can now navigate directly to the WO in job tracking from the operations card on the job page. This was previously only available for non-work-ordered operations. We also added visibility to the work order status in operation instructions.
When you pick a buy item, we split the quantity across jobs and make separate pick transactions. However, that approach doesn’t work for material items because materials are consumed in whole units; we don’t want fractional picks showing up in inventory.
Previously, there wasn’t a clean way to both avoid decimals in inventory and allocate cost distribution of the material items with high precision.
This update fixes that. Material items will now be picked once to the work order, creating a single clean pick transaction. During job costing, the system will automatically allocate that pick’s value across jobs based on each job’s bounding box for that material.
Buy items can now be fully managed within a Work Order. You can add and remove buy items, edit their required quantities, and manage their associations to jobs. All modifications made to buy items flow back to the job, ensuring consistency between the Work Order and the job’s configuration.
Work Orders now provide expanded control over materials and material items. You can add or remove sheet-sized material items, view and update pick quantities, and make adjustments while the Work Order is in Needs Review status. These changes apply only to the Work Order and do not affect the Job BoM.
Job Logs have been added to track updates made through the Work Order, including changes to required items and buy items, providing a clear record of modifications.
Changes made through the Work Order are now logged where possible to provide visibility into updates
A sprinkling of import / export updates
Previously, the way demand planning worked is that whenever something changed that impacted demand, Fulcrum would run an update to that information and recalculate the new demand. This meant there was a delay between the update itself and what showed in demand planning, and required a complex calculation for every change.
Now that Fulcrum uses SQL, the data in demand planning can be efficiently calculated live - no more waiting for the calculations to refresh!
If you complete a job at the wrong quantity, you can now edit it directly on the job. This also applies and relevant downstream cost changes!