“Lifing” is a term used to describe the process of tracking how much use each part has had inside of a product. The easiest example of this is an engine, a new engine is built with new components, so 0 miles. This engine then runs for say 1000 miles, and certain components are changed, maybe their expected lifespan is 1100 miles. So, now the engine is made up of some new parts, and some parts with 1000 miles of use. You can see in a couple of iterations it would be difficult to remember this sort of information, after a while it would be almost impossible.
Mashoom has designed and deployed a solution to this through our ADP Cycle, where it was used to track racing engines. This was in at the deep end for a solution like this as an engine is a very complex thing to track each component. This module is up and running but we are afraid to say it will be a little while before it reaches public release; it’s by far the most complex bit of code on Mashoom.
On public release, this module will include the following:
- When a new part is made, it’s details are entered into Mashoom. We have spent a lot of time making the process very fast.
- QR code support; print or laser etch a QR code onto the part so it can be scanned to find out information about the part
- Manual assembly, assemble parts with other parts without a plan
- BOM assembly, use a BOM version to build a product. Start with a blank BOM and fill in all the physical parts as the product is assembled.
- Move assemblies/tree sections around. This is fundamentally supported; any part with children can be moved with its children in one go.
- Build sequencing, take snapshots of a build at points in time.
- Compare a build to a BOM spec, to find how complete the build is or if there are any parts of the wrong version etc.