<aside> 💡
In Product model you can create templates for of components that are often used at the shipyard.
In this section, you will learn what are the templates and how to create them.
</aside>
List of content
The different component types inside the folder are pages to define the templates for the corresponding components. Their functionality is based on the same principles, and the only difference is that they create templates for different components. The Product will create product templates, Blocks will create block templates, etc.
[1a] Navigate to Projects from the home screen.
[1b] or select Projects from the menu in the top navigation bar (top-left corner of the page)
[2] Once inside the module, a list of options opens on the left side with the Projects list sorting options. The templates are inside application Setting.
[3] For the templates to work correctly for all the different component types the same properties need to be defined.
[4] The activities part of the template is where users define activities that get repeated every time the component is built.
💡 How the activities are set up is explained in more detail Activity tab - create a new Activity
[5] When the activities have been configured users can define on the template standard resources that get performed on each Activity.
💡 The setup of Resources is explained in detail ‣
[6] The standard predecessor and successors relations that always get repeated as well can be defined.
💡 The setup of the relationships is explained in detail ‣
💡 The auto relations are explained Auto realtions page use as reference ‣
The properties page is where users can set up different properties for the templates.
[1] Name: is the name of the template.
[2] Short Name: is a name abbreviation for the name.
[3] Remark: A field where users can write extra information regarding the template.
[4] Template Code: When importing a project plan from an external project planning software, where the plan contains only high-level planning. The external plan can contain template codes that Floor2Plan can use while importing. These codes are a way for the system to know what templates should be included in the plan.
[5] Template: the system makes it possible to reuse templates from an existing template as the base for the new one. This comes in handy when creating new components that have similar steps as are listed in an existing template. Users can use the existing template as a base for the new one. The template field that we are referring to here contains the name of the template that this template is a duplicate of.
[6] Cost code: the field is used when exporting to another system. For example, when exporting the time registration to an external system the assignments will have this cost code as their ERP code. Meaning that it's possible to link the data between the two different systems. This needs to be configured to work correctly at your shipyard.
[7] Icon: sets the icon seen in the tree.
[8] Parent: when building the templates in a hierarchical structure the parent is the property that dictates underneath what component these templates fall under. In this case, the field is filled in with Block which is at the top of the template tree shown on the figure.
[9] Remark: is a property that users can use to write any remarks regarding
[10] Enabled: is a check box that dictates whether or not the template is available. if the check box is unchecked and then the save button is clicked. The system does not currently have a way for users to retrieve the template back. The user has to contact Floorganise and our development team can retrieve the template back from the database.
[11] Allowed children: are the Id of the components that can be inside a parent-child hierarchy.
[12] Allowed Wor: are the Ids of the components that can have wor relationship.
