Final creation of the quotation and preparation of the Bill of Resources

Now CAP-Suite does the hard work.

The BOR Generation runs, for each module (local feature sheet) CAP-Suite uses a decision logic (based on the module being processed) and then reads the BOR defined in abas and then runs a decision logic for each BOR line.

The decision logics also retrieve the  pricing data for "dimensioned" items, stock items such as hardware will be priced late by the abas pricing routines. 

The detail lines of the BOR tell CAP-Suite whether the component is a stock item – hinge, mechanism etc. – or whether the item need to be processed by the decision logic.

From left to right the columns are –

Use – just a text to print on lists, to describe the function of the item

Component – this is an abas reference field to the part master – if filled the item is a fixed form component.

Quantity – the number to use

Dec Logic – the DL to run when processing this line

Height,Width,Thickness_Depth - The dimensions of items to be configured. Some of these draw dimensions from the ArtiCAD file – but most are fixed dimensions. E.g. a cupboard 600mm wide will have everything fixed – but some library items will have varying width, so that they fill the space in the room – these take the dimension from ArtiCAD on the text file – then the decision logic calculates size of panels, doors etc.

The BOR line expands to show more detail.

This is extra dimensioning for drawer panels and also edge detail for panels

The field “Multiplier if Cutdown” is used where the number of components will change depending on the size of the unit – say a cupboard can be between 300 and 1000mm wide – then if it is less than 500mm it has one door, more than that it has two doors. One door needs two hinges, two doors need four hinges. But there is only one shelf and four shelf pins regardless of size.

So decision logics are also used for standard components where the decision logic decides whether to include / exclude items and also to vary their quantity.

For example - there is an option (global and also locally overrideable) which is “soft close” – this is where a door or drawer will have a damper (shock absorber) option so that when it is specified the door / drawer will close softly with a cushion effect. This means changing slide and hinge components, and in the case of drawers the internal panels. You can see this in the “SCYES” and “MBYES” decision logics (MB_YES should really be SC_NO) but that is the way the customer named it.

The real work of CAP-Suite is in the selection and pricing of the variable items – the doors and panels. Here the price will depend on board selected, finish and style.

CAP-Suite automatically processes the feature sheets, explodes the BOR to generate the individual items, then summarises like components so we get only one line per requirement. 

In addition we keep track of the “where-used” reference so we know where items are to be placed at assembly time (e.g. in this example items in lines 1 and 2 belong to modules with plan eferences 8,10 and 11)