Optimumcut-1D v3 Product Development
The big feature we wanted in Optimumcut-1D v3 was the componentisation of items. Let’s use an example where you have a new project that requires 5 windows of type A and 8 windows of type B. Optimumcut-1D v2 would require you to enter this information like this.
Part Description | Length | Quantity |
Window A Horizontal | 600mm | 10 |
Window B Horizontal | 800mm | 16 |
Window A&B Vertical | 500mm | 26 |
As a project gets more complicated, this becomes increasingly difficult to manage. If you are suddenly told you now need an extra two type A windows, updating the correct quantities is time consuming and error prone. Additionally it prevents Optimumcut-1D from producing reports that are anything other than a simple list of parts.
Optimumcut-1D v3 allows you to group all of these items within a component. At the project level you can then define how many of each component you need.
Component | Part Description | Length | Quantity |
Window A x 5 | |||
Horizontal | 600mm | 2 | |
Vertical | 500mm | 2 | |
Window B x 8 | |||
Horizontal | 800mm | 2 | |
Vertical | 500mm | 2 |
By componentising the project, lots of additional data can be stored within the project against each component. This can include assembly timings or accessories such as handles and hinges. It also supports sheet materials so glazing can be included in the project. Optimumcut-1D is then able to produce component reports to aid in assembly and installation.
Once a component has been created or loaded, Optimumcut-1D remembers this component in an internal cache so that it can be re-used in future projects. Within a few mouse clicks, an entire window assembly that was used last week can be re-used in a new project..
Comments
0 comments
Article is closed for comments.