Preparation of data for formwork import

"price list" sheet - is a dictionary for the program to know what the assortment that appears in the program can be, so that users can choose the assortment for orders from it (but see below) and that the purchase (contract) prices are given - then, if the delivery is declared by the supplier, we can detect that in the delivery, the element X was entered with the price of PLN 120, and we have PLN 100 in the contract, and we can communicate this to you. If we had a unit weight (and we do not currently have this in this sheet), we can show how much a given order/return weighs in total (as far as I know, some contracts with suppliers provide free transport, but if the order/return has a weight > 6t, otherwise you have to pay) . The category (also not filled in the sheet) allows the user to select the assortment manually, he can narrow down what he is looking for, e.g. in other construction sites, we have it divided into systems, i.e. he selects the ORMA system and then we filter and show only the assortment with this filter). Elements from this sheet are used to check whether the elements from the "MG documents" sheet are good, i.e. whether the warehouse documents contain the assortment declared here.

KKK sheet - this is a transformation of the Cost Calculation Sheet that you create and then complete by the supplier. The key in it is the BAAN account (or account in general). On its basis, we "talk" with the supplier, i.e. if the supplier declares a delivery to account X, it means that this delivery goes exactly to a given structural element. In this sheet, each line has a separate structural element. Structural elements (EK) are grouped into objects (column C) and objects into contracts (here, there is only one contract, so we do not list it). The remaining fields contain information useful when creating automatic orders (i.e. we need to know who to address the order/return to, because it allows you to have 300 EK at the construction site, of which 200 from one supplier and 100 from another. The remaining data is data from the offer and is used for they can be used to analyze the progress (for reports).An important column is also the lease rate because on its basis the system calculates the lease for a given EK.

worksheet "execution plan". The execution plan is nothing more than a material list for each structural element. As far as we know, if a supplier wins a given contract, he starts designing a given object based on his offer and data (drawings, designing, counting, creating lists of materials). The material list is what you should order to fully implement a given structural element according to their design. Usually (ZTCW) these data appear successively, i.e. the supplier designs and provides you with projects and then you order from them. This sheet just contains a list of components for individual EC. I’ve seen "pretty" sheets with these elements meant for humans. For the computer, we have to present it in a more "digital" way. So this sheet should be supplemented (successively) with data based on projects from the supplier. On their basis, users can order elements for a given structural element. The assumption was that these plans after import would be visible to subcontractors and the subcontractor should enter the structural element, e.g. "WK-12 Schodnia" there, receive a list of what is needed, click the "Order" button and possibly add a few additional elements useful) and let such an order circulate. So this sheet is a material list useful for orders - be it a coordinator or subcontractors.

the last sheet is "MG documents". The assumption of this sheet is that usually when we start the system, the construction has already somehow "started" and some orders/deliveries have probably already appeared outside the system. This sheet was created to ensure that after starting the system all data in the system is complete, i.e. there are also those that appeared earlier than the system itself. This sheet contains only the "supplier" warehouse documents, i.e. what has been issued/returned. Based on this data, we automatically create a "path" in the system, which looks as if it was implemented entirely in the system, i.e. we create an order/delivery/warehouse document and update stock levels. After such an import, all data in the system corresponds to what has already happened before. Nevertheless, this sheet is optional, i.e. it is useful if something has already happened before the implementation of the system, but this is not always the case. The assumption is later that when the system starts, we do everything from the system level and there is no need to re-import this data.