MT2 20.16.2

Here will be list of changes and fixes that will be included in Maintenance release update 20.16.2 of MainManager FM on 19.04.2024

Small additions and changes

New scenario for BIM import of systems for Norwegian customer (EMM-1872)

A new scenario has been added <TFL location code and TFM type code>

In this scenario ifcSpace elements have following properties

where the Romnummer is the essential parameter

For components this is the parameters in the BIM model

Here the essential parameters used are <01_Samplet TFM> and <10_Parallell_ID-Typeunik>

When this scenario is selected the mapping set demands 2 parameters for component import

NOTE the Samlet TFM is a special translation of the MM parameter <Building component room number> (the reason for this as the parameter is that the room number is part of the <Samlet TFM> code

This two parameters are converted to standard MM attributes for the BIM element when processing the model

Example input

BuildingComponentRoomNumber (01_Samlet TFM): +SF.UU2=3600.0027-ST4058.0001

MainManagerTypeCode (10_Parelle_ID-Typeunik): ST4005T

Translated to following fields for MM BIM element

Identification: 3600.ST → Connection to Object type in master

RoomNumber: UU2.058 → Connection to building space in MM

SystemCode: 3600.0027 → Connection to NS system in MM

TypeUnqiue: True if ST4005T

Product number: 3600.ST4005T → Product data in digital delivery

Locator: +SF.UU2=3600.0027-ST4058.0001

Here is example of result of processing of system elements using this scenario

Here example of BIM element attributes for this scenario

The process after the processing of system elements is standard regarding

Creating of product data from product numbers→Digital delivery

Register system structures

Changes to Paymech calculations (EMM-1792)

Now it is possible to select from 3 scenarios for calculation of Paymech (NOTE Calculated unavailability from logged date was previously set through System setting Torc version, which has now been removed). The new scenario is <Calculated unavailability and demand price from logged date>

It is now also possible to calculate due dates based on number of core session instead of entering number of hours, both on <Response demand data> and <Response demand availability>

NOTE: When core sessions are used then for instance if core session for initial temporary rectification is 1 the session period the issue is registered in is calculated as one session. For instance if sessions are defined as 08:00-13:00-18:00 and date if issue is 12:55, then as wish from UK the deadline for temporary rectification is 13:00. That is the service partner has 5 minutes to make a temporary rectification otherwise he gets a deduction

The calculation formulas for both due dates and deductions where adjusted to these changes

Also to be able to test and quality check the paymech setup, the single select action <Test paymech calculations> was added

In the action you select the different parameters that are used in the paymech calculations, you see what due dates are calculated based on the selected parameters, you then enter date finished dates and execute the action and then you get a detailed report about the resulting calculated values

Bug fixes