Contracts¶
Use this dialog to select contract used to link quantities to contract posts (RS, pcs., m, m² and m³).
Where do I find this dialog?¶
On the toolbar, select the icon for Gemini Terrain Settings... - Project - Contracts.
Using contracts¶
If you want to link quantities to contract posts (RS, pcs., m, m² and m³) in your Gemini Terrain project, check Use contracts. You have two methods to choose contract with contract posts:
- Gemini Connected
- Local contract
Warning
It is not recommended to switch between the two methods after a method has been selected and quantity registration has started.
When the Use contracts option is active, the contract posts in the file will be available in both mass types and the attributes S_CONTRACTPOST, S_CONTRACTPOST2, S_CONTRACTPOST3 etc. in application layers.
Gemini Connected¶
With this method, Gemini Terrain retrieves the contract posts from the Gemini Connected project that the cloud project is part of. Here you can work with one or more contracts with any additional works.
Posts with post descriptions for contracts and additional work are made available for Gemini Connected by either:
- Uploading from Gemini ProAdm
- Creating them directly in the contract administration tool in Gemini Connected (for projects without access to Gemini ProAdm)
Note
The two methods cannot be combined.
Use the button Manage contracts... to display the list of contracts and contract posts, and manage which posts should be displayed at any time. The function is described in more detail in separate dialog help.
Warning
Do not change method (from Gemini Connected to Local contract) after quantity registration with Gemini QuantiFlow or Gemini Metrix has started.
Local contract¶
With Import... you can retrieve contract posts from one or more XML files that comply with the standard NS 3459. NS 3459 is a standard that describes file format for transfer of electronic tender information. You can import XML files with price inquiries and price offers.
Note
Item descriptions are not imported with this method, so using Gemini Connected for item management is recommended.
After import, the contract posts are placed in the text file ContractPosts.txt.
Excel is chosen as an editing tool for the content in this text file. This is to make the content more organized and simplify any editing. Click Edit Excel... and the program starts Excel and fills out the content in ContractPosts.txt.
Editing contract posts in Excel
Column description:
- Item no.: Item number formatted for display. This text does not need to be unique, and therefore cannot be used as item identification. Can be omitted.
- Standard code: This is the actual NS or Process code. Can be omitted.
- Id: Item identification. This is mandatory and must be unique within the project.
When you close Excel, you are asked to save ContractPosts.xls. If you choose to save, it is ContractPosts.txt that is updated. ContractPosts.xls is a temporary file that is not saved in the project.
When importing an XML file, you also get the Project name, Project ID, and Project number for the contract. You see this information directly in the dialog.
Use in application layers and mass types¶
Application layers¶
The program contains several predefined system properties for application layers. One of them is S_CONTRACTPOST. By adding this property to the various object types in application layers - line, point, polygon, and triangle net - you get a list of relevant contract posts from the selected method.
If needed, S_CONTRACTPOST2, S_CONTRACTPOST3, and so on can also be added as attributes, so that one object can be assigned several different contract posts for quantity registration.
As default setting, the program lists items with the following units for the various geometry types in an application layer:
- Point: pcs (count)
- Line: m (3D length)
- Polygon: m² (2D area)
- triangle net: m² (3D area) or m³ (volume)
If there is a need to be able to register on items with other units than in the list above, you can check Extended contract post list for objects in application layers. The list of available items will then be expanded with the units as described below, so that you can, for example, register a polygon on a pcs item:
| Geometry type | RS | Pcs | m | m² | m² (3D) | m³ |
|---|---|---|---|---|---|---|
| Point | X | X | X | X | X | X |
| Line | X | X | X | X | X | X |
| Polygon | X | X | X | X | X | X |
| triangle net | X | X | X | X | X | X |
| Point cloud | X | X | X | X | X | X |
Tip
Use the template Kontrakt.al_ to create application layers for quantity registration. This contains three attributes for S_CONTRACTPOST for each geometry type.
Mass types¶
In the dialog for mass types, you get a separate field for contract post. This field lists relevant contract posts for the various calculation types, so that volume gets listed the contract posts with unit m³, while area gets listed the contract posts with m². If the quantity is converted to, for example, tons, contract posts with unit tons will also be displayed in the list.
Tip
Use derived mass type if you want to use the same mass type definition against multiple contract posts.