USER GUIDE

DIMO MAINT – Siège social www.dimomaint.com DIMO MAINT – Nantes

561, allée des Noisetiers 5 Rue du Tertre
69760 LIMONEST 44470 CARQUEFOU
Standard +33 (0)4 72 86 01 90 Standard +33 (0) 02 40 25 27 12
Fax +33 (0)4 72 86 01 99
 Table of contents
USER GUIDE 1
PRESENTATION OF DIMO Maint MX 28
Basic concepts 28
Work requests (WR) 28
Work order (WO) 28
Preventive work (PW) 28
Tree structure and assets 29
Stock - Part 29
Movement 29
Partner 30
Technician 30
Diagnosis 30
Job - Task 30
Functional interface 30
GDPR: General Data Protection Regulations and Terms of Use (TOU) 31
Logging in/logging out 31
File management 32
Navigation by tabs 32
Menus and sub-menus 33
User strip 34
"Question mark" icon 35
Display blocks 35
Entering and saving data 36
General lists, filters and sorts 38
Advanced filters 43
Translation 43
Double-click in the tree views 44
Selection pop-in 44
Icon description 44
Repository 46
Actions common to the reference tables 46
RELEASE 22 - NEW FEATURES 48
MX Developments 48
General 48
Import/New features and changes 48
Export/New features and changes 49
New columns/New fields/Field modification/New blocks 49
MX fixes 49
DMA Developments 50
List of assets - Ergonomics when flashing an Asset QR Code 50
Inventory form - Ergonomics when flashing a Part QR Code 50
TAF 2002 - WO form - Stock management and storage location for the part 50
TAF 2369 - WO form - New Diagnostics tab 50
Improved synchronisations 50
DMA fixes 50

- 2-
ALERTS - NOTIFICATIONS 52
Configuration and activation of alerts - Notifications 52
Upper strip indicators and sending emails 52
Widget alert on the home screen 54
Triggering alerts 55
Triggering the WO alert 55
Triggering the WR alert 55
Triggering the restock alert 55
Triggering the contract expiry alert 56
Triggering the alert for open WOs for which I am the technician 56
Triggering the alert for open WOs for which I am the issuer 56
HOME SCREEN 57
My favourite menus widget 57
Tree widget 57
Work Request widget 58
My WR info widget 60
My schedule widget 62
Work details 63
Report entry 63
Unassigned work widget 64
WO info widget 66
My delayed WR alerts widget 67
My delayed WO alerts widget 67
My restock alerts widget 68
Purchase request widget 68
Asset models 70
List of asset models 70
Create a model 70
Deleting a model 70
Archiving/De-archiving a model 70
Duplicating a model 71
Creating an asset 71
Advanced filters 72
List of asset models 72
74
Asset model form 74
Header block 75
Comment block 75
General information block 75
Suppliers block 76
Photos block 76
Associated files block 76
Parts list block 77
Meters Block 77
Jobs block 78
Measurements block 78
Asset block 78
Additional Fields Block 79

- 3-
Assets 80
List of assets 80
Creating an asset 80
Deleting an asset 80
Duplicating an asset 80
Archiving/De-archiving an asset 81
Moving an asset 81
Printing QR Codes 82
Assets 82
List of assets 82
Creating an asset 82
Deleting an asset 83
Duplicating an asset 83
Archiving/De-archiving an asset 83
Moving an asset 84
Printing QR Codes 84
Asset form 85
Header block 86
Comment block 86
General information block 86
Technical information block 87
Photos block 87
Associated files block 87
Parts list block 87
Work orders block 88
Work requests block 88
Preventive works block 88
Movements Block 89
Downtimes block 89
Meters Block 89
Changing meter readings 90
Jobs block 91
Contracts block 91
Additional Fields Block 91
Costs block 92
Measurements block 92
Asset tree structure 94
Principle 94
Display preferences 94
Actions available 94
Searching for an asset 95
Moving an asset 95
Asset groups 96
List of asset groups 96
Creating an asset group 96
Deleting an asset group 96
Duplicating an asset group 96
Archiving/De-archiving an asset group 96

- 4-
 Asset Group form 97
Header block 98
Asset Block 98
Contracts 99
List of contracts 99
Creating a contract 99
Deleting a contract 100
Duplicating a contract 100
Terminating a contract 100
Archiving/De-archiving a contract 100
Advanced filters 101
Contracts 102
List of contracts 102
Creating a contract 102
Deleting a contract 102
Duplicating a contract 102
Terminating a contract 103
Archiving/De-archiving a contract 103
Advanced filters 103
Contract form 104
Header block 105
Cost management in contracts: 105
Contract termination: 105
Comment block 106
Conditions block 106
Asset block 106
Amendments Block 107
General information block 107
Comment block 107
Asset block 107
Period block 108
Associated files block 108
Work orders block 108
List of triggers 108
Creating a trigger 108
Deleting a trigger 109
Archiving/De-archiving a trigger 109
Duplicating a trigger 109
Trigger form 110
Header block 110
Periodic calendar block 110
Aperiodic calendar block 110
Periodic meter block 111
Aperiodic meter block 111
Preventive works block 111
Work models 111
List of work models 111
Create a model 111

- 5-
 Deleting a model 112
Archiving/De-archiving a model 112
Duplicating a model 112
112
112
Creating a PW 113
Advanced filters 114
List of work models 114
Work models 115
Work model form 115
Header block 115
116
Comment block 116
General information block 117
Resources block 117
Resources - Model workforce 118
Resources - Model part 118
Resources - Model subcontractor 119
Resources – Downtime 119
Jobs block 120
Associated files block 121
Legal information block 122
Work orders block 122
Objects Block using the model 122
Triggers Block 123
List of preventive work 124
Creating a PW 124
Deleting a PW 124
Archiving/De-archiving a PW 125
Duplicating a PW 125
Converting a single PW occurrence into a WO (PW on one asset) 126
Converting a grouped PW occurrence into a grouped WO (PW on several assets) 126
Preventive works 128
Preventive work form 128
Header block 129
Asset block 130
Distribution 130
Jobs 131
General information block 131
Comment block 131
Trigger block 131
Resources block 132
Resources - PW workforce 133
Resources – PW parts 133
Resources - PW subcontractors 133
Resources – PW downtimes 134
Occurrences block 134
Costs block 135

- 6-
 Associated files block 136
Asset files block 136
Work orders block 136
Grouped work orders block 136
Tree structures block 136
Priority preventive work 137
List of priority preventive work 137
Creating a priority PW 138
Deleting a priority PW 138
Archiving/De-archiving a priority PW 138
Priority preventive work 140
Priority preventive work form 140
Header block 140
Comment block 140
Preventive works block 140
141
141
Occurrences block 142
List of work requests 144
Creating a WR 144
Deleting a WR 145
Archiving/De-archiving a WR 145
Duplicating a WR 145
Cancelling a WR 146
Closing a WR 146
Reopening a WR 146
Converting a WR into a WO 146
Accept the work 147
Refuse the work 147
Work request form 149
Header block 149
Comment block 150
General information block 151
Tree structures block 151
Work orders block 151
Associated files block 151
Asset files block 151
Completion preference block 152
Work orders 152
List of work orders 152
Creating a WO 152
Deleting a WO 153
Duplicating a WO 153
Archiving/De-archiving a WO 154
Closing a WO 154
Reopening a WO 155
Cancelling a WO 156

- 7-
 Advanced filters 156
Work order form 157
Header block 157
WO status changes 158
160
Comment block 160
General information block 161
Resources block 161
Resources - WO workforce 163
Resources – WO parts 164
Resources - WO subcontractors 165
Resources – Downtimes 165
Diagnosis block 166
Jobs block 166
168
Tree structures block 169
Costs block 169
Associated files block 169
Asset Files block 169
WR files block 169
PW files block 169
Legal information block 169
Meters block – Entering a meter reading 169
Signature block 170
Measurements block 171
Grouped work orders block 172
List of grouped work orders 172
Advanced filters 172
Creating a grouped WO 173
Deleting a grouped WO 173
Duplicating a grouped WO 174
Archiving/De-archiving a grouped WO 175
Closing a grouped WO 175
Reopening a grouped WO 176
Cancelling a grouped WO 176
Printing a grouped WO 176
Grouped work order form 177
Measurements 185
List of measurements 185
Creating a measurement 185
Deleting a measurement 185
Archiving/De-archiving a measurement 186
Duplicating a measurement 186
Advanced filters 186
List of measurements 186
Measurement form 187
Header block 187
Asset block 188

- 8-
 Value range block 188
Work orders block 189
Technician schedule 191
Table Summarising the display and actions that can be performed by type of account 192
Meaning of colours - Key 192
Actions 192
Technician schedule 193
Table Summarising the display and actions that can be performed by type of account 194
Meaning of colours - Key 195
Actions 195
Asset schedule 196
Meaning of colours - Key 197
Actions 197
Timetable 197
Technician timetable and work in a WO or grouped WO 198
Adding a time slot 198
Scheduling for a periodic time slot 199
Modifying a time slot 199
Modifying a periodic time slot 200
Moving and resizing time slots in the timetable 200
Deleting a time slot 200
Deleting a periodic time slot 200
200
The following confirmation message is displayed: 200
Copying and pasting a time slot 201
Visualising a time slot 201
Distinction between a team’s time slot and a member’s time slot 201
Visualisation of the Timetable by Company / Entity hours 201
Identification of not worked hours based on Team hours 202
Identification of hours not worked based on User hours 202
Movements form 203
Header block 203
Part Block 204
Assignment Block 204
Entry of part managed in stock 205
Removal of part managed in stock 205
Entries and issues of parts not managed in stock 205
Movements 206
List of movements 206
Advanced filters 206
Movements 207
List of movements 207
Advanced filters 207
Movements form 208
Header block 209
Part Block 209
Assignment Block 210

- 9-
 Entry of part managed in stock 211
Removal of part managed in stock 211
Entries and issues of parts not managed in stock 211
Interwarehouse movements form 211
Header block 212
Part Block 212
Assignment Block 213
Purchase requests 214
List of purchase requests 214
Creating a PR 214
Deleting a PR 214
Archiving/De-archiving a PR 214
Duplicating a PR 215
Closing a PR 215
Reopening a PR 215
Cancelling a PR 215
Converting a PR into an order 216
Purchase request form 219
Header block 219
Comment block 220
Parts block 221
Associated files block 221
Orders block 221
Orders 222
List of orders 222
Creating an order 222
Deleting an order 222
Archiving an order 222
Duplicating an order 223
Closing an order 223
Reopening an order 224
Cancelling an order 224
Delivering an order 224
Part order delivery 224
Subcontracting order delivery 224
Advanced filters 225
Order form 226
Header block 226
Conditions block 228
Comments block 228
Order line block 229
Part type lines 229
Subcontracting type lines 230
Costs block 231
Associated files block 231
Links between orders and work orders 231
Inventories 233
List of inventories 233

- 10 -
 Creating an inventory 233
Deleting an inventory 233
Archiving/De-archiving an inventory 233
Duplicating an inventory 234
Closing an inventory 234
Printing an inventory 235
Inventory form 236
Header block 236
Comment block 237
Inventory block 237
Adding parts to the inventory 238
Entering inventory readings 238
Associated files block 238
Parts to restock 240
List of parts to restock 240
Print the list of parts to restock 240
Advanced filters 240
Parts to restock 240
Parts to restock 242
List of parts to restock 242
Print the list of parts to restock 242
Advanced filters 242
Parts to restock 242
Parts to restock 244
List of parts to restock 244
Print the list of parts to restock 244
Advanced filters 244
Parts to restock 244
Parts to restock 246
List of parts to restock 246
Print the list of parts to restock 246
Advanced filters 246
Parts to restock 246
Parts 248
List of parts 248
Creating a part 248
Selecting a part 248
Deleting a part 248
Archiving/De-archiving a part 248
Printing QR Codes 249
Parts 249
List of parts 249
Creating a part 249
Selecting a part 250
Deleting a part 250
Archiving/De-archiving a part 250
Printing QR Codes 251

- 11 -
 Parts 252
Part form 252
Header block 252
Comment block 253
Stocks block 253
Asset block 254
Suppliers block 255
Equivalent parts block 255
Photos block 255
Movements Block 255
Work orders block 256
Preventive works block 256
Orders block 256
Purchase requests block 256
Associated files block 257
Parts stocked by warehouse 258
List of parts stocked by warehouse 258
Advanced filters 258
List of parts stocked by warehouse 258
Parts stocked by warehouse 260
List of parts stocked by warehouse 260
Advanced filters 260
List of parts stocked by warehouse 260
Effects 262
List of effects 262
Creating an effect 262
Deleting an effect 262
Archiving/De-archiving an effect 262
Duplicating an effect 263
Effects 263
List of effects 263
Creating an effect 263
Deleting an effect 263
Archiving/De-archiving an effect 264
Duplicating an effect 264
Effects form 265
Header block 265
Comment block 265
Technologies block 265
Asset block 266
Causes block 266
Remedies block 266
Causes 267
List of causes 267
Creating a cause 267
Deleting a cause 267
Archiving/De-archiving a cause 267

- 12 -
 Duplicating a cause 268
Causes form 269
Header block 269
Comment block 269
Technologies block 269
Asset block 270
Effects block 270
Remedies block 270
Remedies 271
List of remedies 271
Creating a remedy 271
Deleting a remedy 271
Archiving a remedy 271
Duplicating a remedy 272
Remedies form 273
Header block 273
Comment block 273
Technologies block 273
Asset block 273
Jobs block 273
Effects block 274
Causes block 274
Partners 274
List of partners 274
Creating a partner 274
Deleting a partner 274
Duplicating a partner 274
Archiving a partner 275
Partner form 276
Identity block 276
Comment block 276
Conditions block 276
Categories block 277
Addresses block 277
Contacts block 277
Associated files block 277
Asset block 278
Parts block 278
Contracts block 278
Orders block 278
Jobs 279
List of jobs 279
Creating a job 279
Deleting a job 279
Duplicating a job 279
Archiving/De-archiving a job 279
Job form 281
Header block 281

- 13 -
 Tasks block 282
Comment block 282
Asset block 282
Summary of resources block 282
Associated files block 283
Tasks 283
List of Tasks 283
Creating a task 283
Deleting a task 283
Duplicating a task 283
Archiving/De-archiving a task 284
Task form 285
Header block 285
Comment block 285
Resources block 285
Jobs block 286
Associated files block 286
Budgets 287
Budget list 287
Create a budget 287
Delete a budget 287
Duplicate a budget: 287
Archiving/De-archiving a budget 288
Budget form 289
Header block 289
Comment block 290
Budget detail block 290
Associated files block 290
Users 290
List of users 290
Creating a user 290
Deleting a user 291
Duplicating a user 291
Archiving/De-archiving a user 291
Advanced filters 292
List of users 292
User form 293
Identity block 293
Password block 294
Photos block 295
Entity block 295
Time block 295
User profiles 295
List of user profiles 295
Creating a profile 295
Deleting a profile 296
Duplicating a profile 296
Archiving/De-archiving a profile 296

- 14 -
 Moving a profile 297
User profile form 298
Screen configuration 298
Duplicating the configuration 298
Header block 299
Menu restrictions block 301
My widgets block 301
My favourite menus block 303
Entity settings 304
Default entity configuration 304
Duplicating an entity's configuration 304
Role block 305
Notifications 305
Category block 305
Types of contract managed 305
Rights block 306
Codifications block 306
Shared data rights block 307
Profile tree structure 308
Principle 308
Actions available 308
Searching for a profile 309
Moving a profile (Drag & Drop) 309
Configuration 310
Company 310
Opening hours block 310
Licence Block 310
Photos block 310
Module Block 311
Stock module 311
Subcontractor module: 311
Jobs module 312
Multi-warehouse module 312
Multi-time zone module 313
Multi-lingual module 313
Subcontractor Contracts module 314
Orders module 314
Reading Management module 314
Diagnostics module 316
Budgets module 316
Additional Fields module 316
Grouped work module 316
User timetables module 317
Tree partioning module 317
Measurements module 317
UBleam module 318
MX Analytics module 319
PW Prioritisation Module 319

- 15 -
 TVA Module 319
Configuration 319
Company 319
Opening hours block 320
Licence Block 320
Photos block 320
Module Block 321
Stock module 321
Subcontractor module: 321
Jobs module 322
Multi-warehouse module 322
Multi-time zone module 323
Multi-lingual module 323
Subcontractor Contracts module 324
Orders module 324
Reading Management module 324
Diagnostics module 325
Budgets module 326
Additional Fields module 326
Grouped work module 326
User timetables module 326
Tree partioning module 327
Measurements module 327
UBleam module 328
MX Analytics module 329
PW Prioritisation Module 329
TVA Module 329
Configuration 329
Company 329
Opening hours block 330
Licence Block 330
Photos block 330
Module Block 331
Stock module 331
Subcontractor module: 331
Jobs module 332
Multi-warehouse module 332
Multi-time zone module 333
Multi-lingual module 333
Subcontractor Contracts module 334
Orders module 334
Reading Management module 334
Diagnostics module 335
Budgets module 336
Additional Fields module 336
Grouped work module 336
User timetables module 336
Tree partioning module 337

- 16 -
 Measurements module 337
UBleam module 338
MX Analytics module 339
PW Prioritisation Module 339
TVA Module 339
General settings 339
Screen configuration 339
Configuration of PDF printing 340
Duplicating the configuration 340
General 341
Default time zone 341
Help default language 342
Password management 342
Default password for importing users / when a user is created or it is reset by the administrator / when
changed by the user 342
Purchase requests 343
Default recipient of the PRs 343
Stock 343
Valuation calculation 343
Main warehouse 344
Preventive works 344
Default PW triggering time 344
Default meters PW into WO trigger method 344
Trigger threshold for default meters converting PW into WO 344
Days of the week without PW trigger 344
Statuses of assets without PW trigger 344
E-mail sending administration 345
Duplicating the configuration 346
Settings block 347
Work request, Work order, Purchase request and Order blocks 347
WR status administration 347
Duplicating the configuration 348
Automatic changes block 348
Actions by status block 349
WO status administration 350
Duplicating the configuration 350
PR status administration 350
Duplicating the configuration 350
Automatic changes block 351
Actions by status block 352
Order status administration 352
Duplicating the configuration 352
Automatic changes block 352
Actions by status block 353
WR recipient administration 353
Additional fields 354
Duplicating the configuration 354
Asset form 354

- 17 -
 Additional Fields Block 355
Customised languages - Customisation of the application's descriptions 355
Tree partition 357
List of tree partitions 357
Creating a tree partition 357
Deleting a tree partition 358
Advanced filters 358
Tree partition form 358
Identity block 358
Authorised asset block 359
Authorised Objects block 360
Assigned users block 361
362
362
362
363
363
364
364
364
Configuration of PDF screens and printing 364
Screen configuration 364
Configuration of screens on the asset file 365
Configuration of WO form screens 366
Grouped WO form screens settings 369
WR form screen settings 369
WR widget screen settings (home screen) 370
Inventory form screen settings 370
Budget screen configuration 371
Screen configuration in the general settings: default configuration 371
Screen configuration by user profile 371
Apply the default screens configuration 371
Configuration of PDF printing 372
Configuration of asset form printing 372
Configuration of WO form printing 372
Configuration of WR form printing 373
General settings 373
Currency 373
General settings 374
Currency 374
Team 375
List of teams 375
Creating a team 375
Duplicating a team 375
Deleting a team 375
Archiving/De-archiving a team 376

- 18 -
 Team Forms 377
Header block 377
Time block 377
Members block 377
Legal information 377
Payment terms 378
Unit 378
Measurement types 378
Brand 379
Entities 379
List of entities 379
Creating an entity 379
Deleting an entity 380
Duplicating an entity 380
Archiving/De-archiving an entity 381
Entity form 382
Identity block 382
Opening hours block 383
Associations block 383
Asset settings 383
Criticality 383
Asset settings 384
Criticality 384
Asset status 384
Asset families tree 384
List of asset families 385
Brand 386
Types of contract 386
Work settings 386
Technician category 386
Work settings 387
Technician category 387
Partner category 387
WO status 387
WR status 388
Cost allocation tree 389
List of cost allocations 390
Type of work 390
WR type 390
Technology 391
Priority 391
Stock settings 391
Terms of delivery 391
Stock settings 392
Terms of delivery 392
Order status 392
PR status 393

- 19 -
 Storage location 394
Warehouse 394
Part family tree 395
List of Part families 395
Anonymisation 396
User block 396
Partner contacts block 396
Translation - Bulk translator 396
File administration 397
Monitoring block 397
Associated files block 398
Unified authentication 400
VAT 401
VAT 401
Work analyses 402
Advanced filters 403
Failure tree 403
Subcontractor category 405
Technician category 406
Technician 406
Work settings 407
Maintenance 407
Assets pareto 408
Pareto by family 409
Pareto by technology 409
Pareto by type of work 410
Cost allocation pareto 410
Responsiveness to each work order 411
Subcontractor 412
Preventive work completion rate 412
Reference dates taken into account for the application of conversion rates 413
Work analyses 414
Advanced filters 415
Failure tree 416
Subcontractor category 417
Technician category 418
Technician 418
Work settings 419
Maintenance 420
Assets pareto 420
Pareto by family 421
Pareto by technology 421
Pareto by type of work 422
Cost allocation pareto 423
Responsiveness to each work order 423
Subcontractor 424
Preventive work completion rate 424

- 20 -
 Reference dates taken into account for the application of conversion rates 425
Stock analyses 426
Advanced filters 426
Stock status 427
Contract analyses 429
Advanced filters 429
Inventory analyses 431
Advanced filters 431
Inventory discrepancies 431
Analyses - Preventive annual schedule 432
Default settings 432
Selection of fields displayed 432
Actions analysed 433
Advanced filters 434
Part consumption analyses 437
Advanced filters 437
Details by date 437
Details by part and warehouse 438
Details by part family and warehouse 439
Details by cost allocation and warehouse 440
Details by asset and warehouse 440
Unlisted parts 441
Order analyses 443
Advanced filters 443
Orders by date 443
Orders by supplier 445
Orders by part 446
Orders by asset 447
Activity analyses 449
Advanced filters 449
Work orders 449
Work requests 450
Analyses - Analysis Settings / Preventive annual schedule 451
Data imports/exports settings 452
List of imports/exports 452
Creating an import/export 452
Deleting an import/export 452
Archiving/De-archiving an import/export 452
Duplicating an import/export 453
Advanced filters 453
Data imports/exports settings 454
List of imports/exports 454
Creating an import/export 454
Deleting an import/export 454
Archiving/De-archiving an import/export 454
Duplicating an import/export 455

- 21 -
 Advanced filters 455
Data imports/exports settings 456
List of imports/exports 456
Creating an import/export 456
Deleting an import/export 456
Archiving/De-archiving an import/export 456
Duplicating an import/export 457
Advanced filters 457
Import/export form 459
Configuration export/Configuration import 459
Header block 460
Data format block 461
Communication settings block 461
Actions block 462
Error and log management 464
Field length 464
Current process monitoring console 465
Time zones/format 465
Import details 466
Sage X3 purchase request progress 466
Sage X3 order progress 467
Work orders (History) 468
Work orders/Downtime (History) 469
Work orders/Comments 470
Work orders/Jobs 470
Work orders/Status change histories 470
Work orders/Labour (History) 471
Work orders/Parts (History) 471
Work orders/Subcontractors (History) 472
Grouped work orders (History) 473
Grouped work orders/Machine downtimes (History) 474
Grouped work orders/Work orders (children) 475
Grouped work orders/Comments 475
Grouped work orders/Status change histories 475
Grouped work orders/Labour (History) 475
Grouped work orders/Part (History) 476
Grouped work orders/Subcontractors (History) 477
Budgets 477
Budgets/Detail 478
Causes(Diagnoses) 478
Causes/Assets 478
Causes/Technologies(Diagnoses) 479
Partner categories 479
Technician categories 479
Orders 479
Orders/Comments 480
Order/Part lines 480
Orders/Subcontractor lines 481

- 22 -
Terms of delivery 481
Contracts 482
Contracts/Assets 482
Additional fields 483
Additional fields/Values in the lists 483
Additional fields/Assets 484
Tree partitions 484
Criticality 485
Triggers 486
Triggers/Aperiodic Calendars 486
Triggers/Aperiodic Meters 487
Purchase requests 487
Purchase requests/Comments 487
Purchase requests/History of status changes 488
Purchase requests/Parts 488
Work requests 488
Work requests/Comments 489
Work requests/History of status changes 490
Work requests/Preferences 490
Currencies/Conversions 490
Effects(Diagnoses) 490
Effects/Assets(Diagnoses) 491
Effects/Technologies(Diagnoses) 491
Timetable 491
Entities 491
Assets 492
Assets/Meters 493
Assets/Tree partitions 493
Asset statuses 494
WO statuses 494
Order statuses 494
494
PR statuses 495
WR statuses 495
Asset families 495
Part families 495
Files 495
Jobs 496
Jobs/Assets 496
Jobs/Tasks 497
Asset groups 497
Asset groups/Assets 497
Sage X3 movements history 497
Allocations 499
Preventive works 499
Preventive work/Shutdowns 500
Preventive work/Assets 500
Preventive work/Jobs 501

- 23 -
Preventive work/Labour 501
Preventive work/Parts 501
Preventive work/Subcontractor 502
Brands 502
Measurements 502
Models 503
Storage locations 503
Acceptance lines with movement 503
Stock rooms 504
Payment terms 504
Movements 505
Parts list 505
Partners 505
Partners/Addresses 506
Partners/Categories 506
Partners/Contacts 507
Partners/Assets 507
Parts 507
Equivalent parts 508
Parts/Suppliers 508
Parts/Images 508
Parts/Warehouses 509
Meter readings 509
Measurement readings 509
Measurement statements/History 510
Remedies (Diagnoses) 510
Remedies/Assets (Diagnoses) 511
Remedies/Jobs (Diagnoses) 511
Remedies/Technologies (Diagnoses) 511
Parts stock 511
Stock of parts without movement (Sage X3) 512
Tasks 512
Tasks/Shutdowns 513
Tasks/Labour 513
Tasks/Parts 513
Tasks/Subcontractors 513
Technologies 514
VAT 514
Types of contract 514
Type of time slot 514
WR type 515
Types of work 515
Measurement types 515
Units 515
Units/Conversions 515
Priorities 516
Users 517
Users/Tree partition 517

- 24 -
 WR retrieval open webservice (export) 518
WR creation open webservice 519
Export details 519
Code attached to the operation type 519
Expected downtimes 519
Achieved downtimes 520
Work requests 520
Work orders 521
Purchase order 522
Assets 523
Assets/Additional fields 523
Assets/Meters 524
Assets/Jobs 524
Assets/Parts 524
Preventive works 524
Preventive work/Triggers 525
Part Order lines 526
Purchase request lines 526
Planned workforce lines 527
Actual workforce lines 527
Movements 528
Expected parts 529
Achieved parts 529
Users 530
Parts stock 530
Expected subcontractors 531
Achieved subcontractors 531
Data imports/exports settings 532
Imports of data and Webservices (SWAGGER) 532
Grouped operations 535
Principle 535
Settings - Enabling a module 535
Asset Groups 535
Grouped preventive work 535
Grouped work orders 536
Including the grouped WOs in the list of WOs 536
Taking the grouped WOs into account in the asset form 536
Taking the grouped WOs into account in the list of WO alerts 536
Taking the grouped WOs into account in the schedule 536
Taking the grouped WOs into account in the home screen Widgets 537
Taking the grouped WOs into account in the analyses 537
Managing how emails are sent with grouped WOs 537
Configuring the grouped WO screen and print settings 537
Multi-organisation 539
Principle 539
Terms and definitions 539
Activation - Deactivation 539
Access to the entities 539

- 25 -
New entities 540
Entity configuration - Associations block 540
Duplicating the configuration 541
E-mail sending administration 541
WR, PR WO and order status administration 542
WR recipient administration 542
General settings 542
Users 543
User settings - Entities block 543
Configuration of user profiles on the entities - Settings by entity block 544
Default entity configuration 544
Duplicating an entity's configuration 544
Roles by entity 545
Notifications by entity 545
Categories by entity 545
Type of contract by entity 545
Codification by entity 545
Rights by entity 545
User profile configuration for shared data - Shared data right block 546
Creation of shared data - Data sharing 547
Creation of unshared data 547
Data (shared or unshared) association with and dissociation from an entity 547
Entity-related rules applicable to the documents 548
Work request 549
Work order 549
Preventive work 549
Moving an asset or changing entity 549
Moving an unshared asset: 549
Moving a shared asset: 549
Actions performed during a move: 550
Moving an asset that belongs to an asset group 550
Moving an asset that is part of a grouped work item 550

- 26 -
 PRESENTATION OF DIMO Maint MX

The fruit of over 20 years of expertise in developing software solutions for maintenance, DIMO Maint MX is
the latest generation of DIMO Maint CMMS solutions. DIMO Maint MX takes advantage of all the latest
technologies.
Dimomaint MX provides a powerful and fully web-based response to the management of your main-
tenance. An expert and user-definable software suite, it adapts to your business sector so that it covers all
the processes linked with your CMMS.

Simpler, faster work for the service technicians

An effective management tool from a single screen
A number of automatic features to avoid having to spend too much time using the tool
Different profiles for different uses: supervisor, user, requestor or guest

The advantages of DIMO Maint MX The characteristics of DIMO Maint MX

Web architecture Multi-browser
Completely redesigned innovative ergonomics Multi-organisation
More intuitive navigation Multi-lingual – Unicode support
Cloud/SaaS service: subscription service hosted in our hos- Multi-time zone, Multi-currency
ting centre Multi-platform: PC, tablet and smartphone
Collaborative 2.0 QR Code, RFID
Mobility: DIMO Maint App

- 27 -
 PRESENTATION OF DIMO Maint MX

Basic concepts
Work requests (WR)

A work request form is used to express a work request for any type of work. The work request is issued by a department of the company to
the maintenance department. The work request must provide at least the following information:
o geographical location of the work
o asset number
o requester name and department
o request date and time
o a comment giving the reason for the request

The work request is intended to inform the maintenance technician for:

o preparation of the work (location, drawing, tools)

o preliminary diagnosis (operator comments)
o work prioritisation

A work order can be generated on the basis of a work request. The essential information is transferred from the work request to the work
order.

Work order (WO)

The work order is used to prepare the work and to record the work done by the maintenance technician. The work report must provide at
least the following information:

o name of the technician

o work start time, end time and duration
o type of work (mechanical, electrical, etc.)
o references and quantities of replaced parts.

A technical record describing the completed work.

The work record is used to keep a trace of the completed work, in order to compile an asset history.
The work order can be produced as works proceed, or automatically through triggering of preventive works (PW) and work requests (WR).

Preventive work (PW)

Preventive maintenance is carried out on an asset before it fails.

It is intended to:

o reduce priority work

o avoid pre-failure periods of degraded operation
o make repair possible
o increase safety
Two types of preventive maintenance:

n Scheduled (periodic) preventive maintenance

Periodic inspections and work planned according to a schedule to ensure that an asset is in working order at any time.
It is intended to:

o determine the probable cost of maintenance

o define system maintenance time intervals
o schedule tasks and reinforce safety measures

n Condition-based preventive maintenance

Carried out according to readings, meters, measurements or checks revealing the degraded condition of the asset.
It makes fault detection more effective, so that availability can be improved by operation scheduling.
It is intended to:

o avoid unnecessary disassembly related to scheduled maintenance, which may result in failures

o increase the safety of persons

o avoid priority work following the development of incipient faults.

Tree structure and assets

The assets are organised in a tree structure. Changes (moves) can be made by simple drag & drop, and all moves are traced. As many levels
as needed are allowed.

Each asset has a complete form recording its technical characteristics, its production data, its parts list and its associated documents. It also
displays the maintenance history, the preventive maintenance schedule, the associated meters and the traceability of the asset moves.

Stock - Part

To ensure availability of parts, reduce storage costs and control purchasing costs effectively, the stock module enables you to:

n browse the complete list of items necessary for preventive or corrective maintenance that are managed or not managed in stock
n view the technical characteristics of the part and its management parameters (quantity, family, WAUP, suppliers, photos, storage
location and unit, etc.)
n view part movements and completed jobs
n enrich the parts lists automatically
n link equivalent parts

The parts are organised in family trees and can be managed in stock in one or more warehouses.

Movement

Entry and removal movements can be applied to the parts.

Various stock valuation methods are available by default in the application (WAUP, LPP, FIFO, LIFO, MEFO). The valuation calculation
method can also be selected per part or per warehouse. A history of each part movement enables precise tracing of your consumption.

Partner

A partner is an external resource which can:

n carry out work

n supply maintenance parts

It is associated with one or more categories and is differentiated according to several types:

n Subcontractor
n Supplier
n Manufacturer

Technician

The technicians can be internal (workforce) or external (subcontractor) to the company. A technician must be associated with at least one
technician category.
The hourly cost of a technician can be defined for a technician category or be specific to a technician.

Diagnosis

Diagnosis is an important phase of corrective maintenance. The effectiveness of the work depends on its pertinence and its rapidity. The
application can manage a list of diagnoses.

The failure diagnosis comprises an effect, a cause and a remedy, and can consequently be associated with maintenance work.
Each element of a diagnosis can be assigned to a technology and/or an asset.

Job - Task

A job is a set of ordered tasks to be carried out during work.

In the work order, it takes the form of a check-list enabling the technician to confirm (or not) the completion of each task.

A task is an action to be performed during the work. It consists of a detailed description and lists the resources necessary for it to be carried
out (workforce, subcontractor, downtime, part, duration, quantity, etc.).

Functional interface
GDPR: General Data Protection Regulations and Terms of Use (TOU)

On 25 May 2018, a new European regulation came into effect. The GDPR covers the processing of personal data in the European Union.
To ensure the data entrusted to us are protected, each application user must validate the MX Terms of Use (TOU).

The Terms are displayed the first time the user logs in, and must be accepted to access the application.

The Terms of Use are accessed in the header banner, by clicking on the Help -> Terms of Use

Here, users can cancel their selection and invalidate the conditions, they are then automatically disconnected from the software.

Logging in/logging out

The following checks are carried out each time a user logs on:

n Login credentials: Consistency check between user name and password. Caution: the password becomes invalid after 5 incorrect
login attempts and the user account is locked for 20 minutes.
n Check of the licence key validity and expiry date :
 o If the date has expired, a pop-in appears (with a temporary key) to allow the user to enter their
new licence key.
o If the date is still valid, the user is allowed to log on to the application.

n Check on the entities to which the user is attached:

o If a user is not linked to an entity or if all the entities to which they are linked are archived, the
user is prevented from logging on and an error message appears.
o A user may log on if at least one entity to which they are linked is not archived.

n The application can only be opened in a single browser tab.

n A 40 min time-out - corresponding to a period of screen inactivity - is planned (automatic log out after 40 mins of inactivity).

File management
Download file size is limited to 15 MB.
The following extensions are not allowed: action,a-
de,adp,apk,app,asp,-
bas,-
bat,-
bin,-
cer,chm,cmd,cnt,-
com,command,cpl,crt,csh,der,diagcab,exe,fxp,gadget,grp,hlp,hpj,hta,inf,inf1,ins,inx,ipa,isp,isu,its,jar,jnlp,job,js,jse,ksh,lnk,mad,maf,
mag,-
mam,-
maq,-
mar,-
mas,-
mat,-
mau,-
mav,-
maw,mcf,m-
da,mdb,mde,mdt,mdw,mdz,msc,msh,msh1,msh1xml,msh2,msh2xml,mshxml,msi,msp,mst,msu,ops,osd,osx,out,paf,pcd,pif,pl,plg,prf,
prg,-
prin-
terex-
port,ps1,ps1xml,ps2,ps2xml,psc1,psc2,psd1,psdm1,pst,-
reg,rgs,run,scf,scr,sct,shb,shs,theme,tmp,u3p,url,vb,vbe,vbp,vbs,vbscript,vsmacros,vsw,webpnp,website,workflow,
ws,wsc,wsf,wsh,xbap,xll,xnk,config

Navigation by tabs

The application provides multi-tab navigation for fast, simple use.

n Opening tabs
All pages open in a new tab, so the user can view or modify several records at the same time.

The current tab being modified by the user is displayed in blue.

Tabs with unsaved changes are displayed in orange.

n Closing tabs

Each tab can be closed separately, in two ways:

o by clicking on the cross on the right outer edge of the tab

o by clicking on the Close button located at the top-right of the page

A message is displayed if any changes in the tab have not been saved.

All the tabs can be closed simultaneously by clicking on the cross in the tabs sidebar.

A message is displayed if changes in any tab have not been saved.

Menus and sub-menus

The menu bar is always visible in the application.

The user can navigate to a menu or sub-menu even during an action.

Clicking on a menu or sub-menu opens the page in a new tab, without closing the tab currently being viewed
or modified.
 Click on the back button to return to the main menu from a sub-menu.

Menu visibility restrictions and user rights can be configured by user profile. The settings are defined in the menu [Settings-Users-User pro-
files-Menu restrictions and rights].

If the user does not have the rights to any of the menu or sub-menu options, a warning message is displayed.

User strip

The user can access certain information or modify it directly by clicking on his photo or his name, at the top right of the application.

The user strip enables one to view and/or modify the following information:

n Password
n Application description language
n Display language
n Currency
n Time zone
n DIMO Maint App configuration QR code
n Favourite menus

By clicking on his photo, he may access his user form (depending on his rights)
"Question mark" icon

By clicking the icon, the user obtains the menu:

This menu enables access to the following information:

n DIMO Maint MX Full: application version

n Version " ": number of the current version
n Online help: access to online help in the user's language
n What's new: access to the online help new features page in the user's language
n www.supportdimo.com: access to the DIMO Software support page
n Third-party licences: list of licences used for MX
n General terms and conditions of use: concerning the DIMO Maint MX user space
n MX Store: access to the website dedicated to software solutions and connectors enabling the MX functional scope to be enhanced

Display blocks

For better ergonomics, each form of the application is divided into display blocks. The user selects the information blocks to be displayed.
Each block may be unfolded by clicking on the arrow or folded by clicking on the arrow .

One click on the button closes all the blocks.

One click on the button opens all the blocks.

A red left edge informs the user that the block contains required fields.
A blue left edge indicates that the block does not contain any required fields.

Entering and saving data

n Required fields
 Required fields have red outlines, and passing the mouse poin-
ter over the field opens a tooltip.

n Non-modifiable fields

Non-modifiable fields are displayed on a grey ground. When the mouse pointer is placed on a non-modifiable field, it changes to a no entry
symbol.

n Drop-down selection lists

The drop-down selection lists are used to select data from the repository.
.

The list displays all the items containing the entered character(s).

Some lists only display the description, others display the code +
the description. The search is then carried out in both fields.

The search is not case-sensitive (upper/lower case), but it is accent-sensitive.

Some search fields accept a replacement character: use the %.
E.g. Entering "a%" searches for labels that begin with the letter "a" and are followed by one or more other characters. Enter "%a%" to search
for all words containing the letter "a".

The symbol gives access to the pop-in of the reference table associated with the list.
The pop-in enables the user to add, modify or delete a repository item.

This feature and the various accesses to the reference tables depend on the rights defined in the user profile. [Settings-Users-User profiles]
 n Entering dates and times

Manual entry or entry using the calendar

The same principle applies for the entry of times.

General lists, filters and sorts

 n Action buttons

The action buttons are located above each list of items.

Accesses the new item creation form

The user profile must have editing rights over the object.
 Deletes one or more items.
A confirmation message is displayed.
The user profile must have deletion rights over the object.
Archives one or more items.
If archiving is not possible, a warning message is displayed.
The user profile must have archiving rights over the object.
  De-archives one or more items.
The user profile must have archiving rights over the object.

 Exports the whole list to Office Excel.

For certain actions, the item(s) must first be checked in the list by clicking on the button which is shown on the object line.

This check selects or deselects all the lines of the list, on all the pages.

Other buttons may appear, and are specific to each list.

n Line buttons

Link or action buttons are located on each line of a list of items. They differ according to the list opened.

 : Access the form of the item

 : Duplicate the item

This triangle displays the various actions that can be applied according to the selected item.

For each of these buttons, the user profile must have the rights over the action to be performed.
 n Filters

The active filters are selection criteria.

They are displayed above the list. To deactivate a filter, click on the directly in the filter.

To deactivate all filters, click on the located on the right of the wording "Active filters".

The applied filter is displayed with a blue ground.

To display only non-archived items, click on the Not archived button.
To display all the items and cancel the filter, click again on the Not archived button. It is then displayed
on a white ground.

n Search

To run a search, enter one or more character(s) in the search field.

The list displays all the items containing the entered character(s).

The search is not case-sensitive (upper/lower case), but it is accent-sensitive.

n Sorts

When a list is opened, the default sort is ascending order on the first column. The sort type and the sort column are indicated by a symbol:

: Sort in ascending order (alphabetical or numerical)

: Sort in descending order (alphabetical or numerical)
: Sort priority, if several sorts are applied to several columns

Click on the arrow or on the column heading to activate ascending or descending sort or to de-activate the sort.

Customised lists
Currently, this section only concerns the list of WOs.

The new features available are as follows:

n Moving columns

A simple ‘drag&drop’ move (hold down left-click on the column header + move cursor + release left-click) enables you to move the whole
column across the width of the table and position it where you want.

n Fixing columns

Right-clicking on the column header gives you access to a menu, where the choice to ‘Fix’, with the ‘Left’ and ‘Right’ options, enables you to
position and block the column when moving it either to the right or to the left of the table.

(to move it again where you want, you then have to ‘Detach’ it in the same menu).

n Single and multiple sorting

Left-clicking on the column header enables you to sort it. Left-clicking again reverses the sorting order.

Sorting is cancelled by right-clicking on the column header to access the pop-up menu, then choosing to ‘Delete sorting’.

Multiple sorting follows the same principle as above for the choosing the 1st column, then for the following columns, you right-click on the
header to access the pop-up menu, then choose to sort in ‘Increasing order’ or ‘Decreasing order’.

n Selecting columns to be displayed

Left-clicking on the icon gives access to a non-exhaustive list of column names that can be selected by checking the corresponding
box.

Any unchecked name enables you to no longer display the column in question.

n Highlighting of lines hovered over and selected

Hovering the cursor over a line or left-clicking on a line selection highlights it.

n Saving the layout

Left-clicking on the icon enables you to save the presentation for the logged-in user. Each user can therefore customise their own
list of work orders.

The layout items saved are: list of columns, column position and size, sorting order, pagination choice.

The filters are not memorised for the time being.

Advanced filters

The advanced filters enable a user to filter the various lists (Assets, WR, WO, PW, triggers, etc.) according to various criteria.

The list displays only the items corresponding to the active filters. (see Filters)

Translation

Sometimes the following icon appears above a field: when it is clicked, it opens a pop-in where the translation of the original term can
be entered in the target languages.

For example, the term “Repair” will be entered as follows in the pop-in:

For more detailed information, refer to theTranslation - Bulk translation pages (translation of data categories) and Customised languages -
Customisation of application labels (customisation of the translation according to the user).
Double-click in the tree views

In tree views for which a form can be opened (asset form, user profile form, etc.), double-clicking on a node opens the item's form.

In tree views for which no forms can be opened (reference tables, cost allocations, asset families, etc.), double-clicking on a node opens the
line being modified in the corresponding block.

In item selection tree views (item selection pop-in), a double-click selects the item and closes the pop-in.

Selection pop-in

By clicking the icon (Twins) on the right of an input field, a selection pop-in is displayed, which enables one to make a choice with a tree
and/or a multi-criteria tab.

Icon description

: see the Translation selection above

: when this icon does not refer to WOs or is not associated with another legend, it enables the entry of a work report form:

l Work order form, Meters block

l My schedule widget
l Work model form, Resources block
l Work order form, Resources block
l Grouped work order form, Resources block

: this icon enables access to a history of the following items:

 l Asset form, Header block
l Asset form, Meters block
l Asset form, Measurements block
l Contract form, Header block
l Work order form, Header block
l Work order form, Meters block
l Grouped work order, Header block
l Work request form, Header block
l Purchase request form, Header block
l Order form, Header block
l Inventory form, Header block
l Part form, Stocks block

not to be confused with:

, used for conversion in tables accessible through:

l Currency TDR, List of currencies block, Conversions action

or with:

, enabling access to the history of work reports in:

l Work order form, Resources block

: this icon enables access to the "Measurement reading" in:

l Asset form, Measurements block

: gives a task comment:

l Work order form, Jobs block

l Work model form, Jobs block

: anonymisation:
 l Anonymisation form, Users block and Partner contacts block

: Jobs: found in the List of jobs tab and in the tab of any Job form, (created or being created), as well as in:

l Preventive work form, Assets block

Repository
The application includes a set of reference tables, completed or not with a set of trade data:
Work General Stock Asset
o Partner category o Currency o Warehouse o Asset family
o Technician category o Team o Storage location o Criticality
o Cost allocation o Payment term o Part family o Brand
o Type of work o Unit o Terms of delivery o Model
o WR type o Legal information o Order status o Asset status
o Technology o Type of time slot o PR status o Type of contract
o Priority
o WO status
o WR status

Users can add data specific to their occupational activity to each table.

Actions common to the reference tables

The following actions can be performed for the various reference tables (general settings, asset, stock, works):

n Deletion: or  The item cannot be deleted if it is used in the documents (PW, WO, Asset, Parts,
etc.).

n Archiving: or An icon appears next to the document title in the page header. Archived items no lon-
ger appear in the lists or the search fields.

n De-archiving: or  De-archived items reappear in the lists and search fields.

 n Cancellation: or Cancel the current action (archiving, de-archiving or deletion).

n Data sharing: Used to share a selection of data in multi-organisation mode. (check the "shared data" box)

n Association with an entity: Used to associate a selection of shared data with one or more enti-
ties in multi-organisation mode.

n Filters on the non-archived items:

n Filter on the archived items:  : Displays the archived items

n Filter on all the items:  : Displays all the items, archived and not archived. Archived items are iden-

tified by the icon at the beginning of the line.

n Multi-selection: An action can be performed on several items simultaneously by checking the Select/Deselect all box.

Search for items in the list: To run a search, enter one or more character(s) in the search field. The list displays all the items containing the
entered character(s). The search is not case-sensitive or accent-sensitive.

The items displayed as well as the actions that can be performed depend on the user rights settings: Rights over entities and rights over sha-
red data. [Settings-User-User profiles].
 What's new

RELEASE 22 - NEW FEATURES

R2- R21 R20 R19 R18

2
Download the full user guide

MX Developments

General

n The term 'ADFS' has been replaced by 'Unified Authentication'

n Asset model form, Asset block: assets added to the model have their information overwritten by the model's infor-
mation, after using a reset or confirmation button when saving the model
n 'Complete resources' button added to the Resources block of the Work order form and the Grouped work order
form: enabling the resources to be completed in a batch, converting the 'Estimate' to 'Actual' in one click
n Work order form, Jobs block: impossible to respond to tasks if the WO is in 'Done' status, tasks without a response may
take the value 'Cannot be completed' (after validation of a confirmation message) when changing a WO status
manually ("Done" or "Closed")
n TAF 1720 - TTP 836 - Grouped WO from a grouped PW: the cost allocation of child WOs is either the cost allocation
entered in PW, or the cost allocation of their asset if the PW cost allocation is not entered
n Preventive work form, General information block: for a simple PW, when its cost allocation is the same as the asset's,
a change to the asset cost allocation is automatically applied to the PW
n TAF 5592 - User profile rights for Purchase Orders: extended to Printing
n TAF 5691 - User profile form for user profiles: access to the Analyses menu and its sub-menus in the Menu restrictions
block
n TAF 6904 - Trees: selecting an object in the search window enables it to be immediately displayed (without scrolling)
n TAF 6861 - Printing QR Codes: Correction of the discrepancy through Adobe/Acrobat Reader allowing their label to
appear with a limit extended to 2 lines and 52 characters
n TTP 843 - User Import: the format "es-mx" in the list of language codes, referring to Mexican Spanish, has been added
to online help
n TAF 5382: the 'Help' button on the Online help administration file page redirects to the right page
n TAF 6702 - Details of imports and exports: correction of online help
n Link between Resources --> Parts --> Create a part page and Partform: correction of online help

Import/New features and changes

When Purchase requests are imported, theCurrency ISO Code field is added to import the PRs' currency and retrieve the prices
and currencies from PR lines.
When Purchase requests/parts are imported, the Unit price excl. tax field is added to import the part unit price.

- 48 -
 What's new

When Contracts are imported, the Contract/Subcontractor/Code field is added to import the partner through their code (pre-
viously, the partner could be imported by their name alone).
We have also added the Contract/Cost and Currency ISO code fields.

A Contracts/Assets import has been created.

Export/New features and changes

When Purchase Request lines are exported, 2 field labels have been added: Part/Unit price excl. tax and Part/Currency ISO code.

New columns/New fields/Field modification/New blocks

The Currency field has been added to the Header block of the Purchase request form to manage the notion of unit price in the PR
part lines.
The Unit price excl. tax + Currency field has been added to the PR lines (Parts block of the Purchase request form) with the same
aim.
The change to the process for converting a PR into an order is detailed here.

A Work model field has been added to the Header block of the Job form.

On the Work model form, an Objects using the model block has been created to add objects that generate a WO, i.e. mea-
surements, PWs and jobs.
The latter can be accessed by tabs that can be selected in the block header (respectively: 'Measurements', 'Preventive work' and
'Jobs').
This reorganisation of the Work model form deletes the Measurements and Preventive work blocks.

MX fixes

n TAF 5835: Fix - 'Priority' field must replace 'Technology' in processing follow-ups for PW imports
n TAF 6460 (R21): Fix - Deadline updated following a change to resources
n TAF 6639 : Fix - Imports - Task/Parts Imports: Cannot import without part code: error
n TAF 6699 (R21): : Fix - Work order - PDF of the work order containing attachments (that cannot be printed) of up to
several Mb
n TAF 6712 (R21): : Fix - Visual of favourite menu labels KO
n TAF 6725 : Fix - Partner Form - Failure of the delivery conditions link without active Purchase Order module
n TAF 6744 (R21): : Fix - WO - Cannot save WO 2021BI04255 in customer database
n TAF 6749: Fix - Stocks analysis - Crash in customer database
n TAF 6757 (R21): Fix - Technician schedule: Error when displaying details when the work order has a comment
n TAF 6846 (R21): Fix - WO fix: Change in the status of child work orders making it impossible to save the grouped work
order
n TAF 6874 (R21): Fix - Error when receiving order (Pb partnerpartnercategory.HourlyCostCurrencyId NULL)
n TAF 6879: Fix - Partner form, Category tab: Currency can be deleted

- 49 -
 What's new

n TAF 6896 (R21): Fix - Meter triggers: PW occurrence blocking the reading following reset because value/total com-
parison
n TAF 6903: Fix - User profiles, rights over menus: Menu tree retracts at each click
n TAF 6918: Fix - Performance improvement - Work analysis: Extremely slow

Letter and digits 'R21' displayed for TAFs integrated in a patch.

This list is not exhaustive, other points may have been corrected and are not mentioned. For more details, please contact DIMO
Maint support.

DMA Developments

List of assets - Ergonomics when flashing an Asset QR Code

You can flash the QR Code of an asset from the list of assets. In this case, the corresponding asset form will open directly

Inventory form - Ergonomics when flashing a Part QR Code

In an inventory from the list of parts, you can flash the QR Code of a part. In this case, the quantity input window of the cor-
responding part will open directly.

TAF 2002 - WO form - Stock management and storage location for the part

In the 'Parts' tab of the WO form, new information is visible for each part: whether the part is under stock management or not in
the warehouse selected and the storage location of the part in the warehouse selected. If the part does not have a storage loca-
tion, the field will not be visible.

TAF 2369 - WO form - New Diagnostics tab

A new tab is available in the WO form (for creation or existing). It contains three drop-down lists with effects, causes and reme-
dies.

Improved synchronisations

If there is no item to be sent, pressing the 'Synchronisation' icon in the list of WOs or the list of WRs, or pressing the complete
WO, differential WO, complete WR or differential WR menus will not launch upward synchronisation (blocking) but only down-
ward synchronisation (not blocking).

DMA fixes

- 50 -
 What's new

n TAF 5763: Readings -After a reset on an asset's meter, you can take a reading below the reading before the reset (but
above the reset value)
n TAF 6871: Play / Pause - After launching 'play/ pause' and navigating on the WO form, the 'play/ pause' time is no lon-
ger reduced

- 51 -
 Alerts - Notifications

ALERTS - NOTIFICATIONS

Alerts warn the user about work to perform, stock to replenish, contracts to renew or terminate, etc.
Alert items are displayed:

Directly on the ele-

ments lists and forms
with the alert symbol

In the upper strip indi-

cators with the alert
icons

In the widgets on the

user's customised home
screen

Alerts may also trigger the sending of an email.

They are configurable for the following elements:

- Work requests
- Work orders and grouped work orders (if the grouped work module is enabled). Only grouped WOs are taken into account in
the alerts. Child WOs are not taken into account.
- Stocks (if the Stock module is enabled)
- Contracts (if the Contract module is enabled)

Configuration and activation of alerts - Notifications

This symbol is automatically displayed, without prior configuration, as soon as an item is in alert:
- in the lists (WO, WR, parts, contracts, etc.)
- on the forms of objects in alert

Upper strip indicators and sending emails

These alert indicators are enabled by user profile, and by entity if multi-organisation mode is enabled.
For each user profile, in the configuration by entity – Notifications Block, add the alerts indicating which users must be notified.

- 52 -
 Alerts - Notifications

For each alert, 2 options may be enabled:

n Indicator display: if this option is ticked, an indicator in the shape of a lozenge will be displayed in the user's upper rib-
bon. It indicates the number of items in alert.

In multi-organisation mode, the number displays the total items in alert for all the entities to which the user is attached and for
which the alert is enabled.

Representation of each alert in the indicator:

WR alert WO alert Restock alert Contract alert

Clicking on the indicator displays the list of items on alert, sorted by end date of the current amendment for contracts and by
end date for WOs and WRs (from the most recent to the oldest).
Clicking on the Restock alert displays the list of parts between the Restock point and the Minimum stock, and those that have rea-
ched their Minimum stock are shown in the list by an alert indicator.
Sorting is in alphabetical order of the Code (Part).
You can access the item form by clicking on it (depending on user permissions).

- 53 -
 Alerts - Notifications

n Email sending : if this option is ticked, the user will receive an email summarising the items that are in alert. In multi-
organisation mode, an email is sent by the entity with which the user is associated

Widget alert on the home screen

Items in alert may also be displayed directly on the user's home screen.

These widgets are configured in the user profile – My Widgets Section.

l The "My delayed WO alerts" Widget displays orders on alert, on the WO start date.
l The "My delayed WR alerts" Widget displays WRs on alert, on the WR creation start date.
l The "My restock alerts" Widget displays the parts on alert by warehouse. (available if the stock module is enabled)

- 54 -
 Alerts - Notifications

For more information on each Widget, see the Widgets-Home section.

Triggering alerts

Triggering the WO alert

A WO is in alert when the conditions below are met:

• If the WO is a PW occurrence or created directly

- The order status = To do or in progress (or equivalent statuses)
- If the time elapsed since the WO start date > (WO priority time-limit - 3 days)
The day's date - (WO start date-WO priority time-limit)=<3 days -> Alert
The day's date - (WO start date-WO priority time-limit)>3 days -> No alert
E.g. WO start date = 01/02/2017, priority = 5D, the WO appears in Alert on 03/02/2017.

• If the WO originates from a WR:

- The order status = To do or in progress (or equivalent statuses)
- If the time elapsed since the WR creation date > (WO priority time-limit - 3 days)
The day's date - (WR creation date-WO priority time-limit)=<3 days -> Alert
The day's date - (WR creation date-WO priority time-limit)>3 days -> No alert

This display is shown if the following conditions are met:

- the WO status is "To do" or "In progress" (or equivalent statuses)
- the day's date is on or later than (Deadline - 3 days)
- WOs that do not have a Deadline are not in alert
- Child WOs of Grouped WOs are not in alert
]

These conditions are applicable to grouped WOs (not child WOs) and to WOs that have a Deadline.

Triggering the WR alert

A WR is in alert when the conditions below are met:

l The WR status = To be processed (or equivalent)

l The WR has not been transformed into a WO
l Configured deadline - the day's date <= 3 days

Triggering the restock alert

A part is on alert when:

l for at least one warehouse line where the part is in stock, the quantity available (=actual quantity – reserved quantity +
quantity ordered) is lower than or equal to the restock threshold (=minimum threshold)

A part is no longer on alert when the conditions below are met:

- 55 -
 Alerts - Notifications

l Available quantity=(Actual quantity - Reserved quantity + Quantity ordered) > Restock threshold
l the order containing the part changes to ‘Sent’ status (or equivalent)

Triggering the contract expiry alert

A contract is in alert when it reaches expiry when the conditions below are met:

In non-tacit renewal mode:

l Contract status=Enabled
l The Renewal alert date entered has been reached

In tacit renewal mode:

l Contract status=Enabled
l The time remaining before the end of the contract (Notice period) is 1 month by default and can be changed (should
remain >0)
l Renewal alert date= End date current amendment period - Notice period, entered has been reached

Note: : the Renewal alert date cannot be changed directly, but is recalculated automatically if the Notice period changes and is
updated if the amendment is renewed.

Triggering the alert for open WOs for which I am the technician
For this notification, only e-mail sending is configurable. E-mail is sent when the conditions below are met:

l The status of the WO is To-Do, In progress, or equivalent

l The user is in one of the resource lines of the WO not marked completed
l The date of the resource line is less than or equal to D+3

Only one e-mail is sent with the list of open WOs.

Triggering the alert for open WOs for which I am the issuer
For this notification, only e-mail sending is configurable. E-mail is sent when the conditions below are met:

l The status of the WO is To-Do, In progress, or equivalent

l The user is the issuer of the WO
l The date of the resource line is less than or equal to D+3

Only one e-mail is sent with the list of open WOs.

- 56 -
 HOME SCREEN

The application is opened directly from the user’s customised home screen.

n Work request
n Tree
n My WR info
n My favourite menus
n My schedule
n WO Info
n Unassigned work
n My delayed WO alerts
n My delayed WR alerts
The home screen can be customised by user profile. n My stock alerts (if the Stock
The screen is customised in the menu [Settings-Users-User profiles-My Widgets]. module is enabled)
n My PR info (if the Orders module
The widgets can be configured by user profile: is enabled)
n Purchase request (if the Orders
The Widget blocks can be opened or closed independently of each other by clicking on or module is enabled)
simply on the block title bar
The Home tab cannot be closed.

My favourite menus widget

The My favourite menus widget displays the favourite menus defined in the user profile menu [Settings-Users-User profiles-My favourite
menus].

This gives the user rapid access to the most frequently-used features.
Clicking on a menu opens the page in a new tab.

Tree widget

The Tree widget displays the asset tree and enables various actions on the assets directly from the user's home screen.
 Actions available 

o Create an asset
o Create a child asset
o Create WO
o Create WR
o Create a PW
o Access the form of an asset
o Access the list of WOs
o Access the list of WRs
o Access the list of PWs

The actions can be performed in two ways:

o The action buttons

Click on the arrow to view the other actions available.

o The pop-up menu : Right-clicking on an asset displays the actions that can be performed on the selected asset.

The actions that are displayed and can be performed from the Tree structure widget take account of the rights defined for the user profile
(Edit/View/None).

The search field is used to find an asset in the tree easily. The search displays all the assets with codes or descriptions that contain the ente-
red characters. It is not case-sensitive (upper/lower case) or accent-sensitive.

WR alert in progress on the asset: when clicking to create a WR, if the WR statuses are "To be processed" or "In progress" (or equivalent)
on the selected asset, the existing WR alert pop-up displays with the list WRs in progress. In multi-organisation, the list displays all WRs,
even those that are on non-user-managed entities

Work Request widget

The work request widget enables the user to create a WR directly from the home screen.

n Title (required)
n Asset
n Location
n Code (required) -> Not visible if automatic codification on WR enabled
n WR type
n Priority (list)
n Comment (required)
n Attached file (to be checked as visible and modifiable in screen configuration)

WR alert in progress on the asset: when selecting the asset, if the WR statuses are "To be processed" or "In progress" (or equivalent) on the
selected asset, the existing WR alert pop-up displays with the list WRs in progress. In multi-organisation, the list displays all WRs, even those
that are on non-user-managed entities
The data displayed in the WR widget can be customised and configured.
All the fields in the WR form can be:

n Displayed or hidden
n Required or optional
n Modifiable or not modifiable

These settings can either be configured by default or by user profile. See the Screen settings section for more details.
Files can also be added as attachments to the request if the “Attached file” field is displayed.

The user can change tab during entry; the fields in which entries have already been made are kept on return to the WR.
The WR takes on the status configured in the WR status administration if the "Create WR" action is enabled, otherwise it takes on "In pre-
paration" status
If the "Recipient" field is displayed: depending on the WR type selected, displays the recipient(s) defined in the WR recipient administration
by default

The Save button is not available for user profiles that do not have work request creation rights.

My WR info widget

Archived WRs do not appear and are not counted.

From R18, a "nut" icon has been added to the widget bar:

Clicking on the "nut" icon opens the pop-in entitled: "Configuration of my WR info"
where 3 filters are available:

"WR to be displayed":

There are three filter possibilities for work requests:

o All WRs
o WRs for which I am the requester: displays information on WRs requested by the connected user
o WRs for which I am the recipient: displays information on WRs for which the connected user is the recipient

Supervisors and users see all three choices. Guests and Requesters can see the "All WRs" and "WRs for which I am the requester" filters.

The widget is refreshed each time the filter is changed.

"Asset (+ "With children" check box)usual asset selection (and of any "children")

"WR type" usual selection of the work type

The filters applied after clicking the "Save" button on the pop-in are memorised and enable each user to find their most recent choices by
logging out/logging back in.

These indicators display the number of WRs for which the user is requester and which are in the status indicated.

n To be processed or equivalent status

n In progress or equivalent status
n Completed or equivalent status
n Closed or equivalent status
n Cancelled or equivalent status

Clicking on an indicator opens the list of WRs filtered according to the requester, the selected status and the filters applied, in a new tab.
The list does not yet filter to WRs that have an equivalent status.
When the user creates a WR using the Work Request widget, the My WR info widget is updated directly with the new WR.

The list of events concerning the requestor's WRs over the last 7 days is displayed below the indicators.
To access the WR form, click on the button

My schedule widget

The My schedule widget displays, by date and for a technician, the list of incomplete work, for the dates preceding day D and for the next 7
days.
Work not completed beyond the next 7 days is not visible.

The widget takes into account all the incomplete resource lines of the WOs for which the user is the technician.
If the grouped work module is enabled, it displays the resource lines originating from the grouped WOs and the child WOs.

Cancelled and closed WOs are consequently not visible.

From the schedule, the technician can complete the work:

n Either by clicking on the WO button, then on the Entry and Detail button, in the resource line associated with the WO
n Or by clicking directly on the Report button.

The dates before and after day D are visible on a blue ground.
The current date is visible on an orange ground.

 : Displays, for each date, the meter indicating the number of incomplete works scheduled for the technician.
  : Access to the work details.

Work details
WO title, WO code + WO title, Asset photo + Asset description
WO general information
Photo of the technician + Name + First name, WO priority colour
Task block Displayed if the work line originates from a task.
Displayed if Part or Shutdown resource lines originate from the same task or if Part or
Associated resources block
Shutdown resource lines are assigned to the work line.
Displayed if there are other resource lines not originating from a task and not assigned to
Other WO resources block
another resource line.
Comment block Displayed if the WO contains a comment.
Meter block Displays the latest meter readings from the WO asset or sub-assets.

 : Opening of the WO in a new tab.

The user profile must have WO viewing rights.

 : Enables the technician to carry out the work directly from the schedule
The user profile must have WO editing rights.

Report entry
A colour bar indicates the WO priority colour
WO title, WO code + WO title, Asset photo + Asset description
WO general information
Photo of the technician + Name + First name
In the case of a grouped WO, all the assets are listed.
Enter the start date, end date, hourly cost, total cost and duration of the work. If the work
is completed, check the Completed box.

In the case of single WOs, if the resource line originates from a task, the user can check the
completion of the task: "Completed OK", "Completed NOK" or "Cannot be completed".

Meter/Measurement field:
Work entry block
* only selection field (drop-down menu),
* by default displays the meter saved upstream for this job task attached to the WO,
* otherwise displays the only meter by default if only one meter is attached to the WO
asset,
* otherwise blank with the possibility to select a meter from among those attached to the
WO asset,
* HSR on 17/08, the choice of meter or measurement cannot be changed if it has already
 been entered (and saved in the database) for a technician
- Response input field:
- blank by default,
* blank and cannot be modified if no meter entered in the Meter/Meter/Measurement field

In the case of grouped WOs, the response to the tasks is made in the Tasks Block below
Display of Part and Downtime resources defined in the WO and assigned to the technician:
Type, Planned start date, Description, Planned quantity/duration, Actual quantity/duration,
Completed.
Associated resources block
On a line, the following work information must be entered:
Part: Quantity used, Unit, Completed
Shutdown: Start date, End date, Duration, Completed
Display of Part and Downtime resources defined in the WO and not assigned to the tech-
nician: Type, Planned start date, Description, Planned quantity/duration, Actual quan-
tity/duration, Completed.
Other resources block
On a line, the following work information must be entered:
Part: Quantity used, Completed
Shutdown: Start date, End date, Duration, Completed
Comment block Enter a comment on the work
Tasks block Visible for all grouped WOs, if the WF line originates from a task: used to add responses to
the work tasks:
The Completed column contains the list of possible responses to the task (OK, NOK, cannot
be completed).
If a response has already been entered for the line’s asset, it is preselected
If a comment already exists, it is entered automatically
Meters Block Option of taking a meter reading. For more information on inputting a reading, please refer
to the section Meters block – Input a meter reading

Grouped WOs: Lists all the asset meters.

Save your entries. The WO is updated:

n If the work is not completed, the WO status changes to In progress or the status defined in the menu [Settings-Work-WO status
administration].
n If the work is completed, the WO status changes to Completed or the status defined in the menu [Settings-Work-WO status admi-
nistration].
n On the technician line in the WO, a new completion entry is added
n If a response has been entered in the task, it is updated in the WO.
n If no response has been entered in the task, the response already entered in the WO is kept.
n For the resource lines on which the user has entered times or quantities, new completion entries are added.
n For the resource lines on which no entries have been made, the WO is not modified.
n If a comment is entered, a new comment is added to the WO.

Unassigned work widget

In order to quickly distribute the work to be carried out, an unassigned work widget can be displayed on the home screen.

Foreseen unassigned work is displayed: they correspond to the staff lines of work orders whose category is without a technician.
If the grouped work module is enabled, it also displays the WF lines originating from the grouped WOs.
Technician lines that are ticked "Finished" are not displayed.

The Supervisor account type sees all the work

The User account type can only see work in the categories to which s/he is assigned.

For each line, the information displayed is as follows:

n Order code - Order title

n Status - Asset
n Type of work - Technology
n Designation of the task (if the line originates from a task)
n Technician category
n The priority colour appears as a sidebar to the left of the work.

For each line, it is possible:

o To access the work detail pop-up by clicking on the button .

o To view the work order by clicking on .

The user must have WO viewing rights for these two actions.
 o To allocate the work directly to the connected user via the button

n If work corresponds fully or partly to a non-productive range from the logged-in user’s team, or specific to the logged-in user, the fol-
lowing warning message is displayed: : "The technician is not available from DD/MM/YYYY HH:MM to dd/mm/yyyy hh:mm".

All lines with a technician are updated on saving.

The button empties all the drop-down lists.

WO info widget

This widget is used to monitor the progress of work orders.

If the grouped work module is enabled, the display takes the grouped WOs into account.
The indicators display the number of WRs that are in the status indicated.

n To do or equivalent status
n In progress or equivalent status
n Done or equivalent status
n Closed or equivalent status
n Cancelled or equivalent status

Clicking on an indicator opens, in a new tab, the list of WOs filtered according to the selected status. (The list does not yet filter to WOs that
are in an equivalent status)

A summary of the status changes of the last 7 days is displayed beneath the indicators.
On each line there is:
- The work order code, title and issuer
- the status colour bar
- the description of the status change
- the date and time of the status change

- a button to access the order This button is only available to users with work order reading rights.
Archived orders are not counted.

My delayed WR alerts widget

This widget displays WR that are in alert for the logged in user.
They are classified by WR creation date and in chronological order.

The symbol displays the number of WRs that are in alert on this date
The vertical bar corresponds with the colour of the request priority.

The button gives access to the WR form. It is only available to users with WR reading rights.

See the specific documentation on Alerts for more information

My delayed WO alerts widget

This widget displays WOs that are in alert for the logged in user.
If the grouped work module is enabled, it also displays the grouped WOs in alert.
They are classified by WO start date and in chronological order.

The symbol displays the number of WOs that are in alert on this date
The vertical bar corresponds with the colour of the order priority.

The button gives access to the work order form. It is only available to users with WO viewing rights.
See the specific documentation on Alerts for more information

My restock alerts widget

This widget displays parts that are on alert for the logged-in user, sorted by Description (Warehouse), and for each warehouse by Code (Part)
in increasing alphabetical order.

It displays the parts that have reached Minimum stock, designated by to facilitate their priority processing.
It also displays the list of parts to restock (that have reached the Restock point) in the same mode.

The symbol displays the number of parts that are in alert for the warehouse.

The button gives access to the part form. It is only available to users with parts viewing rights.

See the specific documentation on Alerts for more information

Purchase request widget

This widget enables the user to create a PR directly from the home screen.

n Title (Text) (Required)

n Code (Text): Visible and required if automatic codification is not enabled.
n Entity: Visible only if multi-organisation mode is enabled.
n Part (list of parts choices) (Required)
n Quantity (Positive decimal) (Required)
n Unit (List of units convertible with the default unit of the part) (Required)
n Comment (Large text area)

The user can change tab during entry; the fields in which entries have already been made are kept on return to the PR.
When saving, the PR is saved, the date (current date/time), the status (according to configuration), the requester (logged in user) and the
recipient (according to default recipient configuration) are automatically entered.

The Save button is not available for user profiles that do not have purchase request creation rights.
Asset models

List of asset models

The list is accessible through the menu [Work-Models].
The list displays all the non-archived models, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Create a model

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating models, refer to the Model form.

Deleting a model

To delete a team:

n click on the button on the list or form.

n from the list, click on the "Delete" action at the end of the line.

A confirmation message is displayed to confirm the deletion.

Archiving/De-archiving a model

To archive a team:

n click on the button in the list.

The icon is displayed to the left of the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

 n click on the button in the list.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a model

To duplicate a team:

n click on the button on the form.

n from the list, click on the button at the end of the line.

Duplication copies the model selected to a new model. All the information is duplicated (except the Description field of the Header block
(and the Comments and Measurements blocks)).

At the moment, the "Archive", "Dearchive" and "Duplicate" buttons are not available in the list of asset models or the asset model form.

Creating an asset

To create an asset:

n click on the button on the form.

n from the list, click on the "Create an asset" action at the end of the line.

The display of these buttons, which enables you to create models with identical characteristics, is linked to the Asset editing right.

By clicking from a model, a new asset initialisation pop-in is opened:

and presents the following fields:

 n Code: Text field. Required and unique
n Description: Text field. Required.
n Asset status: Selection list.
n Shared data: Checkbox.
n Entities: List of choices from the model entities.
n Parent asset: Typeahead/standard asset search window, filtered to the logged-in user’s entity/ies or selection pop-in ("Twins"
icon).
n Time zone: Selection list. By default, the zone defined in the general settings.
n Start-up date: Date field or selection pop-in ("Calendar" icon).
n Theoretical operating time: double HH type field: MM
n Supplier: List of choices from the List of partners.
n Purchase cost: Numerical field. If the asset purchase date is entered, the purchase cost is converted with the current conversion
rate on the date of purchase, otherwise it is converted with the conversion rate of the day.

Initialisation follows several steps (you can navigate from step to step with the "Previous" and "Next" buttons), and the second step
concerns meters — if the model has any.
In this case, the model meters are displayed and you can choose which meter to inherit from.
When making this choice, the Initialisation date and Initialisation value are required.

When you confirm the initialisation choices, a new tab opens on an Asset form for creation.
The asset fields are initialised from that of the model and initialisation choices made.
The Asset form may be completed.

Advanced filters

This block, which is closed by default, shows the following fields:

n Description: Text field. Automatic filter upon entry.

n Brand: List of choices from the Brand TDR
n Criticality: List of choices from the Criticality TDR
n Asset family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated with:
“With children” check box.
n Manufacturer: Selection list.
n Archived: Yes/No/All ("No" by default).
n Entity: Selection list.
n Shared data: Yes/No/All ("All" by default).

List of asset models

This block, which is always unfolded, has the following columns:

n Description: Text field. Automatic filter upon entry.

n Brand: List of choices from the Brand TDR

 n Criticality: List of choices from the Criticality TDR

n Asset family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated with: “With
children” check box.

n Manufacturer: Selection list.

n Manufacturer reference: Text field. Automatic filter upon entry.

n
Asset models
Asset model form
Accessible from the Settings menu [Settings-Asset].
Model settings are configured in the user profiles:

l Menu restrictions ("Asset model")

l Added to My favourite menus ("Asset model")
l Rights levels (viewing, printing, deletion, etc.)
l Configuration of notifications-alerts
l Rights [those of the "Maintenance repository"]

Click the button to access the form being created or the button to view a model.

The available actions depend on the user rights. [Settings-Users-User profiles].

The icons provide access to the various forms or to the corresponding repositories (Brand, Asset Family and Cost Allocation) so that
information can be viewed or modified during input.

The "New", "Delete", "Archive", "Duplicate" and "Create an asset" buttons are explained in the actions of the List of asset models

At the moment, the "Archive", "Dearchive" and "Duplicate" buttons are not available in the list of asset models or the asset model form.

When the form is saved, a question is asked: "Do you want to apply the changes made to the asset model to all the assets of this model?"
There are 2 possible answers:
 l "Do not apply": only the asset model will be saved
l "Apply": the asset model will be saved AND all the assets associated with this model will be updated with the changes to the
model input in progress

There is no impact on entities, supplier lines or meters.

Header block

This block defines the main information of the contract.

n Description: Text field. Automatic filter upon entry. Required.

n Asset family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated with:
“With children” check box.
n Criticality: List of choices from the Criticality TDR
n Brand: List of choices from the Brand TDR
n Shared data: Check box.
n Entities: Drop-down list enabling one choice of a logged-in user's entity. Main entity of the logged-in user, by default. As soon as
the model entity is changed, you are offered to reset the document and clear the fields that do not have the new entity of the
model in common. The entity cannot be edited once the model has been saved.

Unicity of the Description-Brand pair

Comment block

A comment can be entered, optionally, in the following standard block:

General information block

The user can select or enter additional information relating to the work model:

n Manufacturer: Selection list

n Manufacturer reference: Typeahead. Text field.

n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies. icon
giving access to the List of cost allocations.
n Hourly downtime cost: Numerical field, expressed in currency.

In an unshared model, the information entered must be associated with the asset model entity.
In a shared model, the information entered for the asset model entities is automatically associated, with a preliminary check of the validity of
the association.

Suppliers block

Enables you to list the suppliers that offer the asset model. Click on the button and select a supplier from the list of part-
ners.

n Supplier: List of choices from the List of partners.

n Reference: Text field.
n Unit price: Numerical field, expressed in currency (the supplier's).
n Time (D): Numerical field, expressed in days.
n Price validity: Date field or selection pop-in (entry possible with "Calendar" icon)
n Last update: Date field or selection pop-in (entry possible with "Calendar" icon)
n Main: Checkbox.

Click the button to validate the input. Click on the saved line to view or modify the entry.

Photos block

Enables the user to add a panel of photos to the asset model form. A main photo can be defined, which is then visible in the 'Header' block
of the asset model form.

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Associated files block

Files necessary for completing work can be linked with the model.
Click the button then select an existing file from the dropdown list, or a new file with the "Choose a new file (max 15
Mb)" button.

The files are downloaded on the server; the description is optional.

The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Parts list block

Enables you to add and view the parts associated with this asset model.

n Part: Typeahead or selection pop-in ("Twins" icon). Required.

n Quantity: Numerical field. Required.

n Unit: Typeahead and standard unit search window, filtered to the logged-in user’s entity/ies. icon giving access to the List of
units. Required.
n Comment: Text field.

Meters Block
Enables you to view and modify the meters associated with the asset.

When clicking the block line, the input fields are as follows:

n Description: Text field. Required and unique.

n Unit: List of choices from the Unit TDR. icon giving access to the List of units. Required.

n Threshold: Numerical field. Not required.

n Daily maximum value: Numerical field. Not required.

Jobs block

Enables the jobs to be attached to the asset model via a list of choices from the List of jobs.
Displays all the jobs associated with the asset.

Click on the icon to open the Job form in a new tab.

The user must have the appropriate rights to view the item.

Measurements block

Accessible to a Supervisor account type.

Displays the list of measurements attached to the model, and their number.
This block enables you to view the following columns on the measurement line: Code, Description, Unit.
Also enables you to add a measurement with the following field suggestions:

n Measurement: Typeahead on Code - Description of a measurement. Required. Only measurements with at least one entity in com-
mon with the asset are suggested.
n Unit: Text field (read-only). Retrieves the unit of the measurement selected.

Clicking the icon at the end of the line opens the Measurement form in a new tab.

Asset block

Used to associate assets with the asset model.

Click the button then select an asset from the tree. Enter the quantity, unit and a comment if necessary. Click the button

to validate the input.

Click on the saved line to view or modify the entry.

When assets have been added, saving the asset model displays a confirmation pop-in with the question: "Do you want to update the assets
associated with the asset model with the model information?". If the answer is yes, all the data of the assets added to the current input will
be overwritten by the model's data.

A 'Reset from the model' button is in the block header and on each asset line, and enables the assets to be updated with the model infor-
mation.

The model is automatically added to the asset model nomenclature and is taken away from this nomenclature if the asset is deleted (in this
case, the Model field is blank).

Additional Fields Block

Enables you to input the data of additional fields relating to the asset model.
The fields are displayed according to the asset family.
If this is modified, the additional fields will be updated.

See the Additional fields section for more details.

The user must have the appropriate rights to view the item.
 Assets

Assets

List of assets

The list of assets is accessible through the menu [Assets-Assets].

The list displays all the non-archived assets, sorted in ascending order of the asset codes.

The available actions depend on the user rights. [Settings-Users-User profiles].

If the "Tree partitioning" module is enabled, the list of visible assets, for User and Guest accounts, is restricted to the assets
authorised.

Creating an asset

An asset can be created:

n with the button on the list of assets or in the tree-

view.

n by clicking on the asset form button .

For further explanation on creating an asset, refer to the asset form.

Deleting an asset

To delete a team:

n click on the button on the form or list of assets.

n From the list of assets, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An asset used in the application (in jobs, WOs, WRs, PW, diagnoses, etc.) cannot be deleted.
If the asset has unused child assets, they are also deleted -> a warning message is displayed.

Duplicating an asset

To duplicate a team:

n by clicking on the asset form button .

n from the list of assets, click on the button at the end of the line.

Duplication copies the selected asset to a new asset, reproducing certain information:

- 80 -
 Assets

n Asset photo/thumbnail
n header block: all fields are copied except code and description
n comment bloc: duplicated
n general information block: duplicated
n technical information block: duplicated
n Associated files block: duplicated
n parts list block: duplicated
n Meters block: the following information is copied: description, unit and threshold.

Archiving/De-archiving an asset

An asset can be archived:

n by clicking on the button on the list of assets, the asset form or the tree.

n From the list of assets, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the asset code and description, indicating that the asset is archived.
Archived assets are no longer visible in the drop-down lists, the search fields or the tree.
An asset cannot be archived:

n if it is used in a current WO or WR (status other than cancelled or closed)

n if any of its child assets are used in a current WO or WR (status other than cancelled or closed)

An asset may be archived if all the PWs of the asset and its children are archived.
An asset can be de-archived:

n by clicking on the button on the list of assets, or the asset form.

n From the list of assets, by clicking on the arrow at the end of the line.

The asset is no longer archived and is displayed again in the selection lists, search fields and tree.

Various cases may be encountered:

n De-archiving of an asset with no child assets -> de-archives the asset.

n de-archiving of a parent asset with child assets -> de-archives the parent asset only,
n de-archiving of a child asset -> de-archives the child asset and the parent asset.

Moving an asset

An asset can be moved:

n in the asset form, by changing the selected parent asset,

n in the tree, by Drag & Drop of the asset,
n in the home screen tree, also by Drag & Drop.

A confirmation message is displayed to confirm the move.

- 81 -
 Assets

Several cases may be encountered:

n moving an asset with no child assets: moves the asset to its new location, and updates the parent asset and the move-
ment tab in the asset form
n moving an asset with child assets: moves the whole branch, parent asset + child assets, to the new location, and
updates the parent asset and the movement tab in the parent asset form.
n Moving an "Is a node" asset: its parent assets become nodes

Also refer to the multi-organisation section for more information on entities, moving assets with entities, shared and unshared
data, etc.

Printing QR Codes

The button displays the editing of asset QR codes, by default in Avery L7160 format.

For an optimal result, when you obtain the print preview, you must download the PDF document and start printing from
Acrobat Reader (direct printing from the preview not recommended because risk of discrepancy).

When the button is clicked on, a PDF document opens and displays all of the QR codes of the assets selected in the list.
If no asset is selected, the QR codes of the entire asset list are printed.
It is therefore important to select the lines before printing and to limit the pagination to a maximum of 100 lines.
Under each QR code there is a reminder of the code and description of the asset.
The QR code contains (Code+ Description) (Asset) on a maximum of 2 lines and 52 characters.

Advanced filters as well as filters on archived or non-archived items are not taken into account for editing.

Assets

List of assets

The list of assets is accessible through the menu [Assets-Assets].

The list displays all the non-archived assets, sorted in ascending order of the asset codes.

The available actions depend on the user rights. [Settings-Users-User profiles].

If the "Tree partitioning" module is enabled, the list of visible assets, for User and Guest accounts, is restricted to the assets
authorised.

Creating an asset

An asset can be created:

n with the button on the list of assets or in the tree-

view.

n by clicking on the asset form button .

For further explanation on creating an asset, refer to the asset form.

- 82 -
 Assets

Deleting an asset

To delete a team:

n click on the button on the form or list of assets.

n From the list of assets, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An asset used in the application (in jobs, WOs, WRs, PW, diagnoses, etc.) cannot be deleted.
If the asset has unused child assets, they are also deleted -> a warning message is displayed.

Duplicating an asset

To duplicate a team:

n by clicking on the asset form button .

n from the list of assets, click on the button at the end of the line.

Duplication copies the selected asset to a new asset, reproducing certain information:

n Asset photo/thumbnail
n header block: all fields are copied except code and description
n comment bloc: duplicated
n general information block: duplicated
n technical information block: duplicated
n Associated files block: duplicated
n parts list block: duplicated
n Meters block: the following information is copied: description, unit and threshold.

Archiving/De-archiving an asset

An asset can be archived:

n by clicking on the button on the list of assets, the asset form or the tree.

n From the list of assets, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the asset code and description, indicating that the asset is archived.
Archived assets are no longer visible in the drop-down lists, the search fields or the tree.
An asset cannot be archived:

n if it is used in a current WO or WR (status other than cancelled or closed)

n if any of its child assets are used in a current WO or WR (status other than cancelled or closed)

- 83 -
 Assets

An asset may be archived if all the PWs of the asset and its children are archived.
An asset can be de-archived:

n by clicking on the button on the list of assets, or the asset form.

n From the list of assets, by clicking on the arrow at the end of the line.

The asset is no longer archived and is displayed again in the selection lists, search fields and tree.

Various cases may be encountered:

n De-archiving of an asset with no child assets -> de-archives the asset.

n de-archiving of a parent asset with child assets -> de-archives the parent asset only,
n de-archiving of a child asset -> de-archives the child asset and the parent asset.

Moving an asset

An asset can be moved:

n in the asset form, by changing the selected parent asset,

n in the tree, by Drag & Drop of the asset,
n in the home screen tree, also by Drag & Drop.

A confirmation message is displayed to confirm the move.

Several cases may be encountered:

n moving an asset with no child assets: moves the asset to its new location, and updates the parent asset and the move-
ment tab in the asset form
n moving an asset with child assets: moves the whole branch, parent asset + child assets, to the new location, and
updates the parent asset and the movement tab in the parent asset form.
n Moving an "Is a node" asset: its parent assets become nodes

Also refer to the multi-organisation section for more information on entities, moving assets with entities, shared and unshared
data, etc.

Printing QR Codes

The button displays the editing of asset QR codes, by default in Avery L7160 format.

For an optimal result, when you obtain the print preview, you must download the PDF document and start printing from
Acrobat Reader (direct printing from the preview not recommended because risk of discrepancy).

When the button is clicked on, a PDF document opens and displays all of the QR codes of the assets selected in the list.
If no asset is selected, the QR codes of the entire asset list are printed.
It is therefore important to select the lines before printing and to limit the pagination to a maximum of 100 lines.
Under each QR code there is a reminder of the code and description of the asset.
The QR code contains (Code+ Description) (Asset) on a maximum of 2 lines and 52 characters.

Advanced filters as well as filters on archived or non-archived items are not taken into account for editing.

- 84 -
 Assets

Asset form
Accessible from the tree, menu [Assets-Tree], or from the list of assets, menu [Assets-Assets].

Click the button to access the form being created or on the button to view an asset.

The available actions depend on the user rights. [Settings-Users-User profiles].

The icons give access to the various forms or to the corresponding repositories. (Asset form, asset statuses, small tables of
criticalities, brands, models, etc.) so that information can be viewed or modified during entry.

The New, Delete, Archive, and Duplicate buttons are explained in the actions of the Asset list.

Also refer to the multi-organisation section for more information on entities, moving assets with entities, shared and unshared
data, etc.

- 85 -
 Assets

Header block

The header block defines the main information of the asset.

n Code: Required unique field.

n Description: Required field.
n Asset status: Selection list (optional).

The icon displays the status change history of the asset. (Date, status and user name)

n Location: Entry field (optional).

n Parent asset: Selection list (optional). Opens the asset tree pop-in. To find out more about the asset tree, please refer
to the Asset tree section.
n Asset family: Selection list (optional). Opens the asset family tree pop-in. The additional fields are displayed according
to the family selected.
n Working: Checkbox (checked by default). Depends on the asset status settings in the menu [Settings-Assets-Asset sta-
tuses].

o If the asset status is defined as In service in the settings, the box is checked automatically and can no longer
be changed.

o If the asset status is defined as out of service in the settings, the box is unchecked and cannot be changed.

n Start-up date: Date type field (optional)

n Criticality: Selection list (optional). The criticality colour defined for the asset is shown in the list of assets, criticality
column.

If the criticality is linked with a priority, the priority is retrieved automatically in the work (WO, WR, etc.) when the asset is selec-
ted.

n Time zone: Selection list (required). By default, the zone defined in the general settings.
n Is a node: Check box. Makes it possible to differentiate between a standard asset and a "tree node" type asset.

o if the box is checked, the parent assets down to the root are declared as nodes.
o if the box is unchecked, and if one of the child assets is a node, the following blocking message is displayed: "Cannot
perform operation, a child asset is declared as a node".
n Interface key: Input field, blank by default (if text entered already exists, tooltip: "This Interface Key has
already been used")

Comment block

Entry of a comment is optional.

General information block

Enables the user to define additional information about the asset:

n Brand: Selection list (optional).

n Model: Selection list (optional). Displays only the models linked with the brand in the settings.
n Serial number: Entry field (optional).

- 86 -
 Assets

n Supplier: Selection list (optional). Displays only the partners defined as suppliers in the settings.
n Manufacturer: Selection list (optional). Displays only the partners defined as manufacturers in the settings.
n Manufacturer reference: Entry field (optional).
n Cost allocation: Selection list (optional). Opens the cost allocation tree pop-in.
n Group: Selection list (optional).

Technical information block

Enables the user to select or enter the technical characteristics related to the asset:

n Under warranty: Checkbox (No by default).

n Warranty expiry date: Date type field (optional).
n Theoretical operating time: Numerical field (optional), less than 24 hours.
n Hourly downtime cost: Numerical type field (optional).
n Purchase date: Date type field (optional).
n Otherwise, convert the purchase cost with the conversion rate of the day
n Date of manufacture: Date type field (optional).
n Purchase cost: Digital type field (not required). If the asset purchase date is entered, the purchase cost is converted
with the current conversion rate on the date of purchase, otherwise it is converted with the conversion rate of the
day.
n Work forbidden in service: Checkbox (No by default).

Photos block

Enables the user to add a panel of photos to the asset form. A main photo can be defined, which is then visible in the 'Header'
block of the asset form.

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Associated files block

Files (manuals, documents) necessary for carrying out work can be linked with the asset.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.
The files are downloaded on the server; the description is optional.
The asset files are then retrieved in the various work documents (WO, WR, PW, etc.).
2 different assets can have 2 different documents bearing the same name as associated files (e.g. User guide).

Parts list block

- 87 -
 Assets

Used to add and view the parts associated with the asset and which might be needed in the maintenance work.
The parts list is automatically updated when a work order linked to the asset is closed.

n Part: List of choices or selection pop-in (required)

n Quantity: Numerical fields (required)
n Unit: Selection list (required)
n Comment: Entry fields

Work orders block

Displays the work order history for the asset. The list can be used to view the following information for each WO: priority, start
date ('Day: Hour: Minute" format), code, title, status, type of work, technology.

n Click on the WO line to view additional information: end date ("Day: Hour: Minute" format), issuer, cost allocation.

n Click on the icon to open the WO form in a new tab.

If the grouped work module is enabled, an access button to the grouped WO is displayed at the end of each child WO
line.
The user must have the appropriate rights to view the item.

Work requests block

Displays the work request history of the asset. The list can be used to view the following information for each WR: priority, crea-
tion date, code, title, status, type of work, technology.

n Click on the WR line to view additional information: deadline date/time, issuer, cost allocation.

n Click on the icon to open the WR form in a new tab.

The user must have the appropriate rights to view the item.

Preventive works block

Displays the preventive works history of the asset. The list can be used to view the following information for each PW: priority,
date of next occurrence, code, title, type of work, technology.

n Click on the PW line to view additional information: issuer.

n Click on the icon to open the PW form in a new tab.

n Click the filter to select active PWs or not. "Unarchived" value by default. If filter disabled, all
the PWs are displayed.

When an asset status does not involve a preventive work trigger (e.g. “Inactive”), changing the asset status to a preventive work
possibility (e.g. “Active”) does not generate any occurrence on the period covering the initial status.

- 88 -
 Assets

The user must have the appropriate rights to view the item.

Movements Block

Displays the history of the moves:

n of the asset itself

n of the child assets of the asset
n of other assets to the asset
n of other assets to the child assets of the asset.

The list can be used to view the following information: Date, asset moved, original asset, destination asset.

n Click on the line of the move to view additional information: employee and comment.
n Click on the icons to view the various items (asset form, employee, etc.).

The user must have the appropriate rights to view the item.

Downtimes block

Displays the downtime history for the asset. The list can be used to view the following information for each downtime: start
date, end date, duration, cost, WO code.
Scheduled downtimes are not displayed.

n Click on the line of a downtime to view additional information: WO title and status.

n Click on the icon to open the WO form in a new tab.

The user must have the appropriate rights to view the item.

Meters Block

Enables viewing and modification of the meters associated with the asset. Visible if the "readings management" module is
enabled in the company form.

When clicking the block line, the input fields are as follows:

n Description: Entry field (required and unique)

n Unit: Selection list (required)
n Threshold: Numerical field (not required). You can change it once the reset has been done, and until a new reading
has been input after reset.
n Value: Numerical field (required by default). Displays the value of the most recent reading.

The icon displays the meter reading input history (Reading date, Value, User, Work order, Meter reset).

n Update date: Date/Time field (required, by default, the actual date and time). Displays the date of the most recent
reading.

- 89 -
 Assets

n Total: Read-only numerical field = [Nbr of meter rotations * [Threshold + 1] + Value]. This field updates with the rea-
dings.
n Daily maximum value: Numerical field. Defines the maximum average daily value between two readings.

In modification, the Value, Update date and Threshold fields are read only.
The threshold can no longer be modified once a new reading has been taken after a reset.

Changing meter readings

At the end of the "Meter reading history "Meter Description"" line (obtained from the icon), a "Change" button displays the
"Change the meter reading "Meter Description"" form.
This form contains the fields (reset with the reading data):

l Reading Date/Time
l Value
l Total (read-only)

and the "Save" and "Cancel" buttons.

This change can be made according to the following restrictions:

o A reading and the readings prior to the origin of a PW trigger to WO on reaching reading cannot be changed (blocking
message: "Change impossible. Occurrences have been triggered")
o A reading and its readings prior to the last reset cannot be changed (blocking message: "Change impossible. Reading
earlier than a reset")
o Date of the reading must be prior to the day's date (if the rule is not followed, blocking message: "Entry date later than
the day's date")
o Maximum daily value observed in relation to the previous reading (if the rule is not followed, warning message:"The
daily average calculated ({Value calculated}) is above the max daily value authorised ({Maximum daily value of the
meter}) on the meter")

Between two other readings, the change has the following characteristics:

o Date of the modified reading must be later than the previous reading (if the rule is not followed, blocking message:
"Date entered earlier than previous reading")
o Date of the reading must be earlier than the date of the next reading (if the rule is not followed, blocking message:
"Entry date later than the next reading")
o Value of the modified reading must be later than the previous reading (if rule not followed, blocking message: "Value
entered lower than the previous reading")
o Value of the modified reading must be below the next reading (if the rule is not followed, blocking message: "Vaue
entered higher than the next reading")

When the last meter reading does not have a threshold, the change has the following characteristics:

o Date of the modified reading must be later than the previous reading (if the rule is not followed, blocking message:
"Date entered earlier than previous reading")
o Value of the modified reading must be later than the previous reading (if rule not followed, blocking message: "Value
entered lower than the previous reading")

When the last meter reading has a threshold, the change has the following characteristics:

o Date of the modified reading must be later than the previous reading (if the rule is not followed, blocking message:
"Date entered earlier than previous reading")

- 90 -
 Assets

o If Reading date/time > date (last reading) AND Value < value (last reading) OR Reading date/time < date (last reading)
AND Value > value (last reading), a warning message is displayed when saving: "N.B. This reading will cause a meter
rotation. Are you sure you want to continue?"

The total is updated like this:

o For meters without a threshold, changing a reading changes the total to the same value as the modified reading
o For meters with a threshold, changing a reading changes the total according to the new modified value entered

To take a meter reading, please refer to the section Meters block – Input a meter reading.

Click the icon to open the Meter reset pop-in. The block has the following entry fields:

l Old value date

l Old value
l Reset date
l New value

If a reset has been done, you cannot input a reading from a date prior to the reset (when the threshold is entered), and you see
the
blocking message: “The reading date cannot be prior to the reset on “Reset date”.

Jobs block

Displays all the jobs associated with the asset.

Click on the icon to open the Job form in a new tab.

The user must have the appropriate rights to view the item.

Contracts block

Visible if the contracts module is enabled, this block displays the contracts that are linked to the asset.
In multiple entities, the user sees the contracts associated to the entities to which the user is attached as well as shared
contracts.

Click on the icon to open the form in a new tab.

The costs are displayed in the WO currency.

The user must have the appropriate rights to view the item.

Additional Fields Block

Enables one to input the data of additional fields relating to the asset.
The fields are displayed according to the asset family.

- 91 -
 Assets

Some additional fields may be filled if the asset is not linked to a family, others may be filled for all the assets without taking
their family into account.

See the Additional fields section for more details.

The user must have the appropriate rights to view the item.

Costs block
The "Costs" block displays the asset cost summary by month and year for the different types of resources:

o Workforce
o Subcontracting
o Parts
o Downtimes

Each cost displays the amount of completed work associated with the resource category in the user's currency.

Measurements block

Accessible to a Supervisor account type.

Displays the list of measurements [and their number count] attached to the asset:
This block is used to:

n View the column measurement line: Code, Description, Value and Reading date.
n View following information in the measurement line details: Value (icon ), Unit, Reading date, Measurement.
n Click "Delete" (button in the block header, or command at the end of the measurement line) to delete the link bet-
ween the Asset and Measurement forms and the measurement reading history.
n Click ‘Add’ to add a measurement with the following field suggestions:
n Measurement: Typeahead on Code - Description of a measurement (required). Only measurements with at
least one entity in common with the asset are suggested.
n Unit: Text field (read-only). Retrieves the unit of the measurement selected.
n Value: Digital field (editable). Enables you to initialise a 1st measurement value.
n Reading date: Date/Time field (editable). Enables you to initialise the date/time of the 1st measurement.
Filling in this field makes it mandatory (and vice versa)

- 92 -
 Assets

n Click the "Reading" button ( icon at the end of the measurement line) to enter a new measurement reading.
This button is only available if the asset/measurement link is saved (=need to save the asset form when the mea-
surement is added).
A "New "Description" measurement reading" entry window is displayed with the fields:
n Old value date: Date/Time taken from the last reading (read-only)
n Old value: value taken from the last reading (read-only)
n New value date: Date/Time (default = "Now")
n New value: Numerical field (blank by default; required)

n Click the button in the details of measurement line.

A ""Description" measurement reading history" entry window is displayed with the fields:
n Reading date: Date/Time
n Value: Numerical field
n User: Text field. Name of the user who made the change.
n Work order: Text field. Code of the WO containing the measurement reading.
n Meter reset

Check on reading entry

The New value date must be strictly later than the Old value date.
If this is not observed, when the entry is added, a blocking message is displayed: "Measurement: Description (Measurement).
The date/time of the new value must be later than the date/time of the old value".

The New value date must be strictly before the day’s date/time.
If this is not observed, when the entry is added, a blocking message is displayed: "Measurement: Description (Measurement).
Date entered later than the day’s date"

If Min value and Max value entered in the measurement, then Max value >= value entered >=Min value
If value entered > Max value, blocking message "Measurement: Description (Measurement). Value entered above Max value"
If value entered < Min value, blocking message "Measurement: Description (Measurement). Value entered below Min value"

No check on the value in relation to the previous values.

Asset duplication

When an asset linked to one or more measurements is duplicated, the asset created also has these measurements but without
value or history. Only the Asset/Measurement link is created.

- 93 -
 Assets

Asset tree structure

The asset tree is accessible through the menu [Assets-Tree structure].

Principle
The asset tree displays a graphic representation of the list of assets. 
The use of a tree structure facilitates the definition of the asset settings.
The user views the different tree levels and can distinguish easily between parent assets and child assets.
The cascading set of parent and child assets is also referred to as a tree Node or Branch.

Display preferences

the icon in the tree view block (Home screen widget and Tree form) allows the logged-in user to select their viewing pre-
ferences.

Information to be displayed in the tree and sorting the items: Code, description and/or serial number of the assets.
The code and description fields are displayed by default. The code is sorted.

The selected display settings are saved so that the user can find them each time the tree form is displayed

Actions available

n The actions are explained in the paragraph Creating an asset

n The buttons are used to create a WO, a WR or a PW for the selected asset.

n The buttons respectively open the list of WOs, WRs or PWs, filtered according to
the selected asset.

These actions can also be performed through the pop-up menu opened by a right-click on an asset:

- 94 -
 Assets

WR alert in progress on the asset: when clicking to create a WR, if the WR statuses are "To be processed" or "In progress" (or
equivalent) on the selected asset, the existing WR alert pop-up displays with the list WRs in progress. In multi-organisation, the
list displays all WRs, even those that are on non-user-managed entities.

Searching for an asset

The search field is used to find an asset quickly in the tree.

The results display lists the assets with a code or description that contains the entered character(s).
The target asset is highlighted in the tree.

The search is not case-sensitive (upper/lower case) or accent-sensitive.

Moving an asset
This screen is used for rapid movement of an asset or an asset node by Drag & Drop.
After user confirmation of the move, the changes are visible immediately in the tree.

For further information on moving assets, refer to the section Moving an asset.

- 95 -
 Assets

Asset groups

List of asset groups

This list is available from the [Assets] menu if the [Grouped work] module is enabled.
Asset groups are mostly used in grouped work items. See the Grouped work section for more details.
The list displays all the unarchived asset groups.
The available actions depend on the user rights. [Settings-Users-User profiles].

Creating an asset group

These can be created:

n with the button on the list of asset groups.

n by clicking on the button on the form.

For further details on creating an asset group, refer to the asset group form.

Deleting an asset group

To delete a team:

n click on the button on the form or list of asset groups.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

If the group is memorised in a grouped PW, the memory is also deleted.

Duplicating an asset group

To duplicate a team:

n click on the button on the form.

n from the list, click on the button at the end of the line.

Duplication copies the selected asset to a new group containing the same data as the original group, except for the code and des-
cription which must be entered.

Archiving/De-archiving an asset group

To archive an asset group:

- 96 -
 Assets

n click on the button in the list.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the group code and description, indicating that it has been archived.
Archived groups are no longer visible in the drop-down lists or the search fields.
There are no specific rules that apply when archiving groups; all groups can be archived.

An asset can be de-archived:

n by clicking on the button on the asset form or list.

n From the list, click on the arrow at the end of the line.

The asset group is no longer archived and is again displayed in the selection lists, search boxes and tree.

Asset Group form

This can be accessed via the Assets - Asset groups menu.

Assets can be grouped together according to family, brand, model or serial number. Asset groups can then be used in grouped
work.

Click the button to access the form being created or on the button to view an asset group.

- 97 -
 Assets

The available actions depend on the user rights. [Settings-Users-User profiles].

The icons give access to the various forms or to the corresponding repositories. (Asset form, brand, model) thereby make it
possible to view or modify information during inputting.
The New, Delete, Archive, and Duplicate buttons are explained in the actions of the Asset group list.

See the Grouped work section for more information.

Header block

The header block defines the main asset group information.

n Code: Required unique field.

n Description: Required field.

Asset Block

This block is used to associate assets in the group according to a series of selection criteria (Asset families + child, Asset + child,
brand, model, serial number, etc.) and a distribution.
When a filter is selected, all the assets returned by the filter (that are not already in the group) are added to the group. Multiple
filters can be used.

- 98 -
 Assets

Filter combination memorisation: all the filters applied for adding assets to each group are memorised by the system. If, when a
new asset is created in a forthcoming version, that asset falls into any of the memorised group filter combinations, the user will
be prompted to automatically add it to the group.

The distribution and assets can still be modified after the assets have been added. However, the family can no longer be modi-
fied.

Distribution
Input is open and must be numerical. (percentage, value, etc.). When calculating costs, the system calculates the actual dis-
tribution according to the number of assets and their distribution.
E.g. AST1 = 1 and AST2=3 if the cost=100, the cost will be distributed as follows: AST1=25 and AST2=75.

Collective updating of the asset distribution keys in a grouped PW: the button is used to modify
the distribution of several assets simultaneously. Select the assets to modify, then click on the button. Fill in the desired dis-
tribution for these assets in the pop-in displayed.
Note : The button allocates a distribution of 1 if all the assets are selected.

Click on the icon to open the asset form.

Assets in a group can be deleted by clicking on the button .

In multi-organisation mode, the assets must belong to (at least) one of the group entities.

Contracts

List of contracts

The list can be accessed from the [Assets-Contracts] menu if the Subcontractor contracts module is enabled.
The list displays all the non-archived contracts, sorted in ascending order of the contract codes. It is also possible to sort by alert

status and future end date (by alert icon ).

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a contract

A contract can be created:

n with the button on the list of contracts.

n by clicking on the button on the contract form.

For further explanation on creating a contract, refer to the contract form.

- 99 -
 Assets

Deleting a contract

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A contract cannot be deleted:
- if it is in "Enabled" or "In progress" status
- if it is used in the application (in the WOs, etc.)
Deletion of contracts in "Terminated" status is authorised.

Duplicating a contract

To duplicate a team:

n click on the button on the contract form.

n from the list of contracts, click on the button at the end of the line.

Duplication copies the contract selected to a new contract, including certain information:

n Subcontractor
n Manager
n Type of contract
n Type of work
n Technology
n Shared data
n Entity (within the limits of user rights)
n Associated files block

It is initialised in "Enabled" status

In the new contract, an initial amendment is created reproducing all the information from the last amendment of the original
contract, except for the effective date, which is initialised on the day's date.

Terminating a contract

See the Terminating a contract section

Archiving/De-archiving a contract

A contract can be archived:

n by clicking on the button on the list or contract form.

n From the list of contracts, by clicking on the arrow at the end of the line.

- 100 -
 Assets

The icon is displayed to the left of the contract code and description, indicating that the contract is archived.
Archived contracts are no longer visible in the drop-down lists or the search boxes.

A contract cannot be archived:

n If it is in "Enabled" or "Being terminated" status

A "Terminated" contract can be archived.

A contract can be de-archived:

n by clicking on the button on the list or contract form.

n From the list of contracts, by clicking on the arrow at the end of the line.

The contract is no longer archived and is displayed again in the selection lists and search fields.

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Status: Drop-down list, with the choices: “Active”, “Being terminated”, “Terminated”.
n Subcontractor: Selection list.
n Manager: Selection list.
n Type of contract: Selection list.
n Renewal alert date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Technology: Selection list.
n Type of work: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Cost: Number field.[Decimal value]
n Term of payment: Selection list.
n Tacit renewal: Selection (list): Yes/No/All
n Work order: Text field. Automatic filter upon entry.

- 101 -
 Contracts

Contracts

List of contracts

The list can be accessed from the [Assets-Contracts] menu if the Subcontractor contracts module is enabled.
The list displays all the non-archived contracts, sorted in ascending order of the contract codes. It is also possible to sort by alert

status and future end date (by alert icon ).

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a contract

A contract can be created:

n with the button on the list of contracts.

n by clicking on the button on the contract form.

For further explanation on creating a contract, refer to the contract form.

Deleting a contract

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A contract cannot be deleted:
- if it is in "Enabled" or "In progress" status
- if it is used in the application (in the WOs, etc.)
Deletion of contracts in "Terminated" status is authorised.

Duplicating a contract

To duplicate a team:

n click on the button on the contract form.

n from the list of contracts, click on the button at the end of the line.

Duplication copies the contract selected to a new contract, including certain information:

- 102 -
 Contracts

n Subcontractor
n Manager
n Type of contract
n Type of work
n Technology
n Shared data
n Entity (within the limits of user rights)
n Associated files block

It is initialised in "Enabled" status

In the new contract, an initial amendment is created reproducing all the information from the last amendment of the original
contract, except for the effective date, which is initialised on the day's date.

Terminating a contract

See the Terminating a contract section

Archiving/De-archiving a contract

A contract can be archived:

n by clicking on the button on the list or contract form.

n From the list of contracts, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the contract code and description, indicating that the contract is archived.
Archived contracts are no longer visible in the drop-down lists or the search boxes.

A contract cannot be archived:

n If it is in "Enabled" or "Being terminated" status

A "Terminated" contract can be archived.

A contract can be de-archived:

n by clicking on the button on the list or contract form.

n From the list of contracts, by clicking on the arrow at the end of the line.

The contract is no longer archived and is displayed again in the selection lists and search fields.

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.

- 103 -
 Contracts

n Status: Drop-down list, with the choices: “Active”, “Being terminated”, “Terminated”.
n Subcontractor: Selection list.
n Manager: Selection list.
n Type of contract: Selection list.
n Renewal alert date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Technology: Selection list.
n Type of work: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Cost: Number field.[Decimal value]
n Term of payment: Selection list.
n Tacit renewal: Selection (list): Yes/No/All
n Work order: Text field. Automatic filter upon entry.

Contract form
Accessible from the Assets menu [Assets-Contracts] if the Subcontractor contracts module is enabled.
Configurations are made on contracts in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)
l Types of contract managed
l Configuration of notifications-alerts
l Rights on shared data (in multi-organisation)

Click the button to access the form being created or the button to view a contract.

The available actions depend on the user rights. [Settings-Users-User profiles].

- 104 -
 Contracts

The icons give access to the various forms or to the corresponding repositories. (Types of contract, Technologies, etc.) the-
reby make it possible to view or modify information during inputting.

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Contracts list.
Alerts on contracts can be configured in the user profiles. See the Alerts section for more details.

Header block

This block defines the main information of the contract.

n Code: Required and unique

n Title: Required
n Status: Required. Drop-down list (Active, being terminated and terminated)
n Subcontractor: Required. Drop-down list.
n Manager: Required. Drop-down list of supervisors. Initialised with the logged in user if he is a supervisor. When a
manager is selected, the list of contract types is filtered on the contract types managed by the manager (Con-
figuration by user profile entity)
o If the contract is not shared: displays all the contract entity users
o If the contract is shared across several entities: displays all the users who have at least all the contract enti-

ties
o If the contract is shared without an entity: displays all the users who have at least one entity from the log-

ged-in user's entities.

n Type of contract: Required. The list displays the contract types that are managed by the user. Authorisations are crea-
ted in the user's profile form - Configuration by entity Block - Contract types. When a contract type is selected, the list
of managers is filtered to those who manage this contract type (Configuration by user profile entity).
n Type of work: Drop-down list.
n Technology: Drop-down list
n Cost allocation of the current amendment (recovered from the amendment)
n Cost of the current amendment: See also the section Cost Management in Contracts

n Currency
n Number of current amendment (Non-modifiable, recovered from the current amendment)
n Effective date of current amendment (recovered from the current amendment, required)
n Period of the current amendment (recovered from the current amendment, required)
n Payment terms (recovered from the current amendment)
n Number of orders over the period: input the number of WOs to be completed over the period

In multi-entity, "Shared data" check box and list of entities.

Modifying a field linked to the current amendment also modifies this field in the corresponding amendment.

The icon displays the contract status change history. (Date, status and user name).

Cost management in contracts:

When entering a price in the Cost field of the amendment block, the sum is allocated for each asset.
When entering a cost on an asset, the Cost field in the header and on the amendment is updated with the sum of all costs ente-
red on all assets in the current amendment.

Contract termination:
When the contract status changes to "Being terminated":
- All the automatic renewal processes on the contract will no longer be carried out
- The current amendment remains valid until the end of the current period.
- It is impossible to create a new amendment
When the current period finishes, the contract automatically changes to "Terminated" status and nothing can be changed

- 105 -
 Contracts

Comment block
Corresponds to the comment entered in the current amendment.

Conditions block

These items set the conditions applicable to the contract:

n Tacit renewal (yes/no)

n Renewal duration (required if tacit renewal is yes) (numerical non-nil): in months
n Notice period (required if tacit renewal is yes) (numerical may be nil): in months

Management of tacit renewal:

When tacit renewal is activated and the contract status is active, a new period is created automatically when we reach the start
of the notice period.
For this new period:
- Start date: End date of the current period + 1 Day
- End date: Start date + Renewal duration
+ the other amendment information

When a new amendment takes effect, tacit renewal of all the previous amendments is stopped.

When the current amendment is under tacit renewal and a new amendment is entered at a future date, the current amendment
is valid until the effective date of the new amendment. When the new amendment takes effect, tacit renewal of the previous
amendment is stopped.

Management of explicit renewal:

When tacit renewal is deactivated, the normal rule consists of triggering an alert one month before the end of the agreement.

An alternative is possible using the Renewal alert date field: empty by default, in Date format, it can be modified as long as the
date is before (end of agreement - 1 month).
This results in an alert date before the one that is normally set, one month before the end of the contract.

Asset block

Used to assign one or more assets to the current amendment. If there is no current amendment but one or more future amend-
ments, the assets are added to the last amendment created.

n Asset: asset selection pop-up in the tree

Assets can be associated collectively to the contract according to determined selection criteria:

n Asset including its children

n Asset families (including their children)
n Brand
n Model

- 106 -
 Contracts

n Serial No.
n Asset groups

To add assets from the same family, click on the button, select asset family, then click on the but-
ton. All the assets linked to the family in question are added to the contract.
When the Add button is clicked, the assets corresponding to the selection that are not yet present in the amendment asset list
are added to this list.
Modifying the asset list in the contract form makes the same modification in the current amendment.

See also the section Cost Management in Contracts

In multi-organisation, the asset must have at least one common entity with the contract.

Amendments Block

This block contains the list of all the existing amendments to this contract.
They are sorted by amendment number in the list.
The first amendment is created automatically when the contract is created.

Click on the button to create a new amendment.

The button enables access to the amendment details.

Deletion is authorised only for the last amendment if it has not generated a WO.

If a field in the current amendment is modified, it is also modified in the contract form.
When creating a new amendment, the new amendment information is retrieved from the contract form.

General information block

Contains the information relating to each amendment:

n Number (required) (positive non nil integer)

n Effective date (required)
n Cost allocation
n Duration of the effective period (required) (numerical non-nil): duration in months
n Cost

During creation, the amendment is pre-filled with the information of the last amendment to date except for the effective date
which is the day's date.
The number is initialised with the largest number that already exists + 1
In multi-entities, the lists only display the data linked to the contract entity.

Comment block

This block is for entering a comment on the amendment.

Asset block

Click the button to add assets to the amendment.

- 107 -
 Contracts

The assets of the current amendment are then visible in the contract asset block.

See also the section Cost Management in Contracts

In multi-organisation, the asset must have at least one common entity with the contract.

Period block

This block enables us to view all the planned and completed work over the different contract amendment periods.
When a new amendment is created, a period line is added to the Periods block of the Contract form:

n Start date = effective date of the amendment

n End date = effective date of the amendment + period
n Amendment no. = No. of the amendment concerned
n Number of WOs planned: number of WOs planned in the amendment
n Number of WOs completed: 0 by default Then displays the number of orders closed in the period dates

If the period created is in conflict with the period of the previous amendment, the end date of this period is modified to the day
before the effective date of the new amendment.
Modifying an amendment causes the modification of the corresponding period.

Associated files block

Files can be linked to the contract (instructions, documents).

The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Work orders block

Displays the work orders that refer to this contract. 

The list can be used to view the following information for each WO: priority, start date ('Day: Hour: Minute" format), code, title,
status, type of work, technology.

n Click on the WO line to view additional information: end date ("Day: Hour: Minute" format), issuer, cost allocation.

n Click on the icon to open the WO form in a new tab.

The user must have the appropriate rights to view the item.

List of triggers
The list of triggers is accessible through the menu [Work-Triggers].
The list displays all the non-archived triggers, sorted in ascending order of the codes.

Creating a trigger

A trigger can be created:

n with the button on the list of triggers.

n by clicking on the button on the trigger form.

- 108 -
 Contracts

For further explanation on creating a trigger, refer to the Trigger form.

Deleting a trigger

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A trigger that is cited in a PW cannot be deleted. 

Archiving/De-archiving a trigger
A trigger can be archived:

n by clicking on the button on the list of triggers or the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the title, indicating that the trigger is archived.
Archived triggers are no longer visible in the drop-down lists or the search fields.

A trigger can be de-archived:

n click on the button on the list or form.

n from the list of triggers, by clicking on the arrow at the end of the line.

The trigger is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a trigger

To duplicate a team:

n click on the button on the form.

n on the list of triggers, click on the button .

Duplication copies the selected trigger to a new trigger. All the information is duplicated, except the description and the PW
block, for each type of trigger.

- 109 -
 Work settings

Trigger form
Accessible through the menu [Work-Triggers].

Click the button to access the form being created or on the button to view a trigger.
The user must have preventive works editing rights.

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Triggers list.

Header block

The header block defines the main information of the trigger.

n Description: Required field: the code of a trigger is unique.

n Type: a trigger can be one of the following types:

o Periodic calendar
o Aperiodic calendar

The following types of triggers are also visible if the "Reading management" module is enabled in the company form:

o Periodic meter
o Aperiodic meter

The trigger type cannot be changed if it is used in a PW.

Periodic calendar block

n Displayed if Periodic calendar type is selected.

n Number of periods: positive whole number only.
n Time interval: drop-down list with options: Day, Week, Month, Year.

When a trigger is updated, a message is displayed prompting the user to update the schedule of the associated PWs.

Aperiodic calendar block

- 110 -
 Work settings

n Displayed if aperiodic calendar type is selected.

n Date: date selection in a calendar.

Periodic meter block

Used to manage preventive works according to a meter interval.

n Displayed if Periodic meter type is selected.

n Interval: positive whole number.

Aperiodic meter block

Used to manage preventive works according to a list of meter values.

n Displayed if Aperiodic meter type is selected.

n Value: positive whole number.

Preventive works block

Displays all the PWs associated with the trigger.

The list can be used to view the following information for each PW: next occurrence, code, title, type of work.

n Click on the PW line to view additional information: issuer, priority.

n Click on the icon to open the PW form in a new tab.

n Click the filter to select active PWs or not. "Unarchived" value by default. If filter disabled, all
the PWs are displayed.

The user must have the appropriate rights to view the item.

Work models

List of work models

The list is accessible through the menu [Work-Models-Work models].
The list displays all the non-archived models, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Create a model

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

- 111 -
 Work settings

For further explanation on creating measurements, refer to the Model form.

Deleting a model

To delete a team:

n click on the button on the form or list.

n from the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

(It is impossible to delete an item that is cited in a document (WO, etc.))

Archiving/De-archiving a model

To archive a team:

n click on the button on the list or form.

n from the list, click on the arrow at the end of the line.

The icon is displayed to the left of the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

n click on the button on the list or form.

n from the list, click on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a model

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the model selected to a new model. All the information is duplicated (except the Code fields of the Header
block and the Comment, Measurements and Work orders blocks).

- 112 -
 Work settings

Creating a PW

To create a PW from a work model:

n click on the form's button.

n from the list, click on the "Create a PW" action at the end of the line.

These buttons are displayed if the "Preventive work" right is at least for editing.
A confirmation message is displayed to validate the creation of a PW if the model has been changed without saving.

If the work model used to create a PW does not contain a trigger (not required in the model but necessary for the PW creation
assistant), blocking message: "A trigger must be entered for PW models"
If the work model used to create a PW does not contain a type of work (not required in the model but required in PWs), blocking
message: "A type of work must be entered for PW models".

A validated click on the "Create PW" button opens a "PW creation assistant":

which presents the following fields:

n Entity: Required. User's main entity by default. Drop-down list suggesting the list of entities shared by the work model
and the logged-in user.
n Grouped PW: Boolean. Disabled by default. Depends on the activation of the "Grouped work" module.

Initialisation follows several steps (you can navigate from step to step with the "Previous" and "Next" buttons), and the second
step concerns assets:

l step 1: choice of entities and the PW type (grouped or not)

l step 2: choice of assets
l step 3: initialisation of the triggering of the different PWs
l step 4: recap and validation generating the new PWs

Upon assistant validation:

- 113 -
 Work settings

l if Grouped PW is enabled: creation of a single PW containing the assets selected

l if Grouped PW is disabled: creation of as many PWs as assets (one PW per asset)

When you confirm the initialisation choices, if Grouped PW = "Yes", a new tab opens on a PW form for creation.
The PW fields are initialised from that of the model and the initialisation choices made.
The PW form can be filled in.

If in single entity mode and the "Grouped Work" module has not been enabled then the assistant moves directly to step 2.
The model meters are displayed and you can choose which meter to inherit from.

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Type of work: Selection list.
n Priority: Selection list.
n Issuer: List of choices of users with an editing right over WOs.
n Creator: List of choices of users with an editing right over models.
n Creation date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Asset off: Yes/No/All "All" by default.
n Technology: Selection list.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Subcontractor category: Selection list.
n Technician: Selection list.
n Subcontractor category: Selection list.
n Subcontractor: Selection list.
n Part: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies.
n Job: Selection list.
n Measurement: Typeahead.
n Entity: Selection list.

List of work models

This block, which is always unfolded, has the following columns:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Entity: Text field. Automatic filter upon entry.
n Creator: Text field. Automatic filter upon entry.
n Creation date: Date/time field. Automatic filter upon entry.

- 114 -
 Work settings

Work models

Work model form

Accessible from the Work menu [Work-Model].
Model settings are configured in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)
l Configuration of notifications-alerts
l Rights [those of the "Models repository"]

Click the button to access the form being created or the button to view a model.

The available actions depend on the user rights. [Settings-Users-User profiles].

The icons give access to the various forms or to the corresponding repositories (Work type, Priority) so that information can
be viewed or modified during entry.

The "New", "Delete", "Archive", "Duplicate" and "Create PW" buttons are explained in the actions of the List of work models

Header block

This block defines the main information of the contract.

n Code: Text. Required and unique

n Title: Text. Required.
n Type of work: Drop-down list of work types according to entity. Required if a PW is linked to the model.
n Priority: Drop-down list. Required.
n Asset off: Yes/No. Default value "No".
n Creator: Drop-down list. Required. Logged-in user by default. Editable, offering the list of users with at least the right
to edit in the "Models repository" on the entity.

- 115 -
 Work settings

n Rolling schedule: Yes/No. Default value "No". Criterion with no impact if the trigger is aperiodic.
n Issuer: Drop-down list. Required. Default model creator. Editable, offering the list of users with the right to create on
work orders.
n Statuses of assets without PW trigger: Drop-down list of asset statuses that have at least one model entity. Entered
by default according to the Asset statuses without PW trigger setting of Company/Entity.
n Days of the week without PW trigger: Multiple choice list of the days of the week. Entered by default according to the
Days of the week without PW trigger setting of Company/Entity.
n Completion time limit: Text (Blank by default) + choice: hour(s)/day(s) ("day(s)" by default)
n Currency: Drop- down list of currencies. Required. Currency of the logged- in user by default. Non- editable if
resources.
n Entities: List of choices enabling multiple choice of the logged-in user's entities (if rights on "Model repository"). Main
entity of the logged-in user by default/if only entity present.
n Shared data: Yes/No. Default value "No". "Yes" value enabling additional entities to be added.

The Days of the week without PW triggering and Statuses of assets without PW triggering fields are initialised differently when a
new work model is created:

- if the Supervisor has creation rights over the "Model repository" (User profile form, Share data rights block) of its main
entity:

l the Entities field is then filled in with the user's main entity
l The Days of the week without PW triggering and Statuses of assets without PW triggering fields are initialised accor-
ding to the general settings of the main entity

- if the Supervisor has creation rights over the "Model repository" but not its entities:

l the Entities field is then blank and Shared data is checked

l the Days of the week without PW triggering and Statuses of assets without PW triggering fields are initialised according
to the Company/Entity settings

- if the Supervisor has creation rights over the "Model repository" over some entities but not its main entity:

l the Entities field is then filled in with a random entity

l the Days of the week without PW triggering and Statuses of assets without PW triggering fields are initialised according
to the general settings of the model entity

Comment block

A comment can be entered, optionally, in the following standard block:

- 116 -
 Work settings

General information block

The user can select or enter additional information relating to the work model:

n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.

icon giving access to the List of cost allocations.

n Recipient: Selection list.

n Technology: Selection list icon giving access to the TDR.

n Creation date: Date/Time. Read-only.
n Work forbidden in service: Check box. Value used in the PWs created from the work model. Its modification from the
PW linked to the model causes the pop-in of deletion of the link between PW and model.

Resources block

Several types of resources may be needed:

Workforce (WF)

Sub-contractor (SC)

Part

Downtime

This screen is used to plan or complete work for each type of resource.
The resources can also originate from the jobs linked to the model.

- 117 -
 Work settings

All the costs are displayed and converted into the model currency.

Resources - Model workforce

Any resource - Workforce added will be retrieved when triggering the work order.

Click the button then select the Workforce type.

Category is a required field. A technician category can be assigned to a WO without selecting a technician.
The list of technicians is then filtered to the users belonging to the defined category.
When a technician is selected, his or her main category is entered automatically. It can nevertheless be changed by selecting in
the list another category linked with the technician's user profile.
The list of technicians displays only the users whose profile includes the technician role.

Once the Category field or Technician field has/have been selected, click the button to confirm the entry.

Resources - Model part

Any resource - Part added will be retrieved when triggering the work order.

Click the button then select the Part type.

Orders for parts allocated to a work order are added directly to the work order. Refer to the Link between orders and work
orders section on the order form.

n Assign to: blank if there is no WF or SC resource in the WO. Otherwise, displays the list of technicians and sub-
contractors of the WO resources and the planned start date and duration. Used to assign the parts to the various
internal or external technicians of the WO.
n Part: Selection drop-down list or pop-in. Displays the descriptions of parts attached to the model entity.
n Description: Entry for a non-listed part in stock, filled in automatically for listed parts in stock. Required.

- 118 -
 Work settings

n Warehouse: Field blank by default. Drop-down list of all the non-archived warehouses. When a part is selected, dis-
plays the main warehouse, if the part is managed in stock there; otherwise, displays the warehouse in which the part
is managed in stock. If the part is managed in stock in several warehouses, the field remains blank to leave the choice
to the user.

For the parts listed in stock, the required fields are: Date, Part, Quantity, Unit, Warehouse. The unit price cannot be modified.
For the parts not listed, the required fields are: Date, Description, Quantity, Unit cost. The unit price must be entered.

Once the Description field and/or the Part field has/have been selected, click the button to confirm the entry.

Resources - Model subcontractor

Any resource - Subcontractor added will be retrieved when triggering the work order.

Click on the button then select the Subcontractor type.

Subcontracting orders allocated to a work order are added directly to the work order. Refer to the Link between orders and work
orders section on the order form.

n Category: Required. Displays the partner categories.

n Subcontractor: Drop-down list. Displays all the partners that are subcontractors.
n Planned duration: Hour type: Minute type in (in HH: MM).

The subcontractor category is a required field.

A subcontractor category can be assigned to the model without selecting a subcontractor.
The list of subcontractors is then filtered to display those belonging to the assigned category.
When a subcontractor is selected, its main category is entered automatically. It can nevertheless be changed by selecting ano-
ther of its categories in the list.

Once the Category or Subcontractor field has been selected, click the button to confirm the entry.

Resources – Downtime
Any resource - Downtime added will be retrieved when triggering the work order.

Click the button then select the Downtime type.

- 119 -
 Work settings

n Assign to: blank if there is no WF or SC resource in the model. Otherwise, displays the list of technicians and sub-
contractors of the model resources and the planned start date and duration. Used to assign the downtime to the
various internal or external technicians of the model.

Once the Assign to field has been selected, click the button to confirm the entry.

Jobs block

Used to link maintenance jobs with the work model.

Click the button and select a job in the selection dropdown list

Once the job has been selected, click the button to confirm the entry.

If the job tasks have assigned resources, a message prompts the user to add the task resources to the work model. The work
start date must then be entered.
Click on a job in the list to display the associated tasks.
When completing the work, there are three response options:

n the task is completed: OK

n the task is not completed: KO
n the task cannot be completed: Not feasible

To respond to the tasks associated with several jobs simultaneously:

- Check the jobs

- Click on the button

- Select the response to assign to all the tasks of the checked jobs
- Enter a comment if needed

- 120 -
 Work settings

- Click on the button

The selected response is applied to all the tasks in the selected jobs and the comment is entered against all the tasks.

The comment for each task can be seen by clicking on the button . It cannot be changed.

Details of a job:

The type of task is represented by three types of icons :

l "Standard":

l "Meter reading":

l "Measurement reading":

Associated files block

Files necessary for completing work can be linked with the model.

Click the button then select an existing file from the dropdown list, or a new file with the "Choose a new file
(max 15 Mb)" button.

- 121 -
 Work settings

The files are downloaded on the server; the description is optional.

The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Legal information block

You can add legal information which will be retrieved when triggering the work order(s) linked to the model.

Click the button and select legal information in the selection dropdown list.

Once the legal information has been selected, click the button to confirm the entry.

This block enables you to view the following fields:

l Description: selection list, providing the legal information attached to the model entity. Required.
l Legal information: filled in automatically with the legal information selected. Non-editable.

Work orders block

Displays the work orders triggered when the model is entered in a list. 
The following information for each WO can be viewed from the list: Start date ("Date: Hour: Minute" format), Code, Title, Status,
Asset (code+description concatenation), Reading date, Value.

Click the icon at the end of the line to open the WO form in a new tab.

Objects Block using the model

- 122 -
 Work settings

Displays in tabs the objects likely to trigger a WO: measurements, PWs and jobs.

If you unfold the block, you have three tabs: 'Measurements', 'Preventive work' and 'Jobs'.

n 'Measurements' (if 'Measurements' module enabled):

l content from the Measurements block in the Work model form used up to R21 inclusive
l displays the number of items and their list with the columns: Code, Description

l open the Measurement form by clicking

l 'Delete' button of the label of the block header converted into 'Delete link':

n 'Preventive works'

l content from the Preventive work block in the Work model form used up to R21 inclusive
l displays the number of items and their list with the columns: Code, Title, Assets, Date of next occurrence

l open the Preventive work form by clicking

n 'Jobs' (if 'Jobs' module enabled):

l Jobs block content used

l displays the number of items and their list with the columns: Code, Description

l open the Job form by clicking

l button block present in header

Triggers Block

Accessible to a Supervisor account type.

Displays the list of triggers of any type with at least one of the model entities and their number.
This block enables you to view the following columns on the trigger line: Trigger, Type, Time interval.
Adding the trigger enables you to enter a Default PW trigger time limit for the Calendar type and the Meter type with trigger
method for each Projection in time, and to enter a PW trigger threshold for the Meter type with trigger method for each Actual
achievement of the trigger value

Clicking the icon at the end of the line opens the Trigger form in a new tab.

- 123 -
 Work settings

If no PW is linked to the model, the trigger can be changed freely.

List of preventive work

The list is accessible through the menu [Work-Preventive work].
The list displays all the non-archived PWs, sorted in ascending order of the PW codes.

The “Date of next work” column displays the date of the next PW occurrence, if it has not been converted into a work order,
otherwise, the corresponding work order (or grouped work order) start date is displayed.

Grouped PWs : Grouped PWs involving several different assets are only displayed once (as opposed to as many times as assets
are included). The Asset column displays the description “Several assets”.
Refer to the section Grouped work.
Filtering on an asset brings up all the PWs and grouped PWs that reference the asset in question.

The available actions depend on the user rights. [Settings-Users-User profiles].

If the "Tree partitioning" module is enabled, the list of preventive work items visible, for User and Guest accounts, is restricted to
those with at least one authorised asset.

Creating a PW

A PW can be created:

n with the button on the list of PWs.

n from the assets tree by clicking on the button or by right-clicking on an asset/Create a PW.

n by clicking on the button on the PW form.

n from the home screen via the Widget tree by clicking on the button or by right-clicking on an asset/Create
a PW.

For further explanation on creating a PW, refer to the Preventive work form.

Deleting a PW

To delete a team:

n click on the button on the form or list of PWs.

n from the list of PWs, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A PW that is cited in another document (WO) cannot be deleted.

- 124 -
 Work settings

When the PW is linked to a work model, it is deleted from the Work model preventive work block.

Archiving/De-archiving a PW

A PW can be archived:

n by clicking on the button on the list of PWs, or the PW form.

n from the list of PWs, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the code and the PW title, indicating that the PW is archived.
Archived PWs are no longer visible in the drop-down lists or the search fields.

When the PW is linked to a work model, the link is maintained and it continues to be updated by model changes (and can be de-
archived later).

A PW can be de-archived:

n by clicking on the button on the list of PWs, or the PW form.

n from the list of PWs, by clicking on the arrow at the end of the line.

The PW is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a PW

To duplicate a team:

n click on the button on the PW form.

n in the list of PWs, click on the button .

Duplication copies the selected PW to a new PW. All the information is duplicated except:

n Code
n Initialisation date (-> initialised with the day's date)
n Issuer (-> initialised with the logged in user)
n Last work order generated
n Work orders
n Occurrences

If grouped work is enabled, asset filter memorisation is also duplicated.

When the PW is linked to a work model, the link is not maintained and the Model Code field does not appear in the new dupli-
cated PW.

- 125 -
 Work settings

Jobs associated with assets are duplicated.

Job task types are duplicated (with icon) and displayed before the new PW is saved.
The task description is displayed for the associated resource.

Converting a single PW occurrence into a WO (PW on one asset)

A WR can be converted to a WO:

n From the PW form, occurrences block, by clicking on the button.

n Automatically if PW automation is enabled (automatic conversion converts a maximum of 20 occurrences for the
same PW) unless the Actual achievement of the trigger value method has been chosen for the meter PW.

Converting an occurrence converts the occurrences selected as well as all the previous occurrences that have not been conver-
ted.
As soon as conversion is possible, the tab of the Work order form is highlighted (orange), and if the user closes the Work order
before saving it, the following confirmation is displayed:
"The following action requires a response from you: Save the work order before exiting".

For a PW on a single asset (single PW)

The WO generated is initialised with the PW information
The reference to the PW and the date of occurrence are stored on the WO generated

WO field initialisation from the PW fields:

o Code: blank
o Title: Title
o Status: To do
o Asset: Asset
o Type of work: Type of work
o Priority: Priority
o Start date: Date of the PW occurrence
o End date: Date of the PW occurrence
o Asset off: no
o Comment: Comment
o Issuer: Sender
o Creation date <- current date/time
o Duration: 1
o Technology: blank
o Cost allocation: retrieves the PW's cost allocation
o  Resources: the resources are added on the WO start date and the prices are retrieved at

moment T
o Jobs: for jobs with reading type tasks, the name of this reading to be taken is sent via the value

of the Meter/Measurement column if the asset only has one meter; if the asset has several
meters, the name will left to the user's choice

If a WO is to be generated when there is no automatic codification, alternative codification is established consisting of just a
numerical meter.

For a grouped PW on several assets (single PW)

Converting a grouped PW occurrence into a grouped WO (PW on several assets)

- 126 -
 Work settings

If the grouped work module is enabled and the PW is on several assets, converting the grouped PW generates a grouped work
order (grouped WO).
Refer to the section Grouped work.
The conversion is done

n by clicking on the button in the PW form occurrences block.

n Automatically if PW automation is enabled, unless the Actual achievement of the trigger value method has been cho-
sen for the meter PW.

Converting an occurrence converts the occurrences selected as well as all the previous occurrences that have not been conver-
ted.
The data from the PW is entered when grouped WO is generated.
The reference to the PW and the date of occurrence are stored in the grouped WO generated

As soon as conversion is possible, the tab of the Grouped work order form is highlighted (orange), and if the user closes the Grou-
ped work order before saving it, the following confirmation is displayed:
"The following action requires a response from you: Save the work order before exiting".

Conversion is identical to that of a single PW in the case of the following data (see paragraph above):
- Header
- General information
- Comment
- Resources
- Files

With automatic conversion:

A child WO is generated from the grouped WO on the Asset (if the asset is in a state other than a configured state without PW
triggering) for each PW asset line.
The distribution key defined for each asset is propagated to each child WO of the grouped WO
The jobs linked to the PW asset are inserted into the corresponding child WO jobs.

As far as all the other assets are concerned (that are not in a state that is compatible with PW triggering), no child orders are
generated.

With manual conversion

The relevant asset is added in the grouped WO (if the asset is in a state other than a configured state without PW triggering) for
each PW asset line
The distribution key defined for each asset is propagated to each asset of the grouped WO
The jobs linked to the PW asset are linked to the corresponding asset of grouped WO.

When the grouped WO is recorded, the child WOs are generated for each asset

- 127 -
 Work settings

Preventive works

Preventive work form

Accessible from the menu [Work-Preventive work].

Click the button to access the form being created or on the button to view a PW.

Grouped PWs can be created from this screen if the grouped work module is enabled.
Refer to the section on Grouped work.

The available actions depend on the user rights. [Settings-Users-User profiles].

- 128 -
 Work settings

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Preventive work list.

The icons give access to the various forms or to the corresponding repositories. (asset form, priority PW form, work type,
small priority tables, etc.) so that information can be viewed or modified during input.

Header block

The header block defines the main information of the PW.

n Code: Required field: the code of a PW is unique.

n Title: Required field.
n Entity: only if multi-organisation mode is enabled.
n Type of work: Selection list (required)
n Priority: Selection list (optional). The priority is displayed according to the criticality of the PW asset. If the grouped
work involves several assets and if the criticality of the asset in question is linked to a priority that is higher than that
of the PW, the PW priority is replaced by that of the asset when the asset is added. Refer to the section Grouped
work.
n Initialisation date: Date type field (required): by default, PW creation date.
n Asset off: Check box (by default = No)
n Rolling schedule: Check box (default = No) A PW with an aperiodic trigger cannot be rolling.
n Issuer: Entered by default with the connected user if s/he has editing rights on the WO: otherwise, the required field
is blank. In the latter case, the list, which indicates the users with editing rights on the WO, can be accessed.
n Completion time limit: Can be expressed in either hours or days. By default: blank field, unit in days. Possibility of deci-
mal value (2 digits after the comma).
n Priority PW code: If the PW is attached to a Priority PW, the field contains its code. Read-only. Priority PW access win-
dow.
n Model code: If the PW is attached to a work model, the field contains its code. Read-only. Work model access win-
dow.

The 3 settings below can be defined per PW and automatically retrieved from the general configuration in mono-entity mode
(Settings/general)
In multi-entity mode, the settings are retrieved from the general configuration of the entity selected in the header (Enti-
ty/Association block/general settings)

n Statuses of assets without PW trigger

n Days of the week without PW trigger
n PW trigger time: used to define how long before the date of a PW occurrence it is automatically converted into a WO.
n Currency: List of currencies used, required, user's default currency. The PW currency can be modified if there is no
subcontracting resource line in the PW.

Updating of the rolling preventive plan at the closure of a work order

l When a WO originating from a PW on a rolling scheduleis saved and changes status to Closed, the PW occurrences are
recalculated. The occurrences recalculation is based on the end date of the WO. (Does not reschedule an occurrence
on a date prior to any occurrence already converted into a WO).

l If an upcoming occurrence has already been converted to a WO, recalculates the occurrences, in the case of a rolling
schedule, from the end date of this WO.

l When a WO originating from a rolling periodic meter PW is closed, the date of the next occurrence is recalculated
according to the end date of the WO, to which the daily average of the meter is added.

- 129 -
 Work settings

Asset block

Used to allocate one or more assets to a preventive work item (if the grouped work module is enabled) and to allocate a dis-
tribution to them which will be used when calculating the work costs.
When the grouped work module is disabled, when changing a PW, it is not possible to add or delete the asset already listed, the
existing asset must be changed (to do so, click on the line and select a new asset by the field or the "Twins").

n Asset: pop-in for selecting the asset from the tree: only filter visible if grouped work has not been enabled.

With the grouped work module, assets can be associated collectively to the PW according to determined selection criteria:

n Order: automatically incremented and modifiable, if the order of assets is coherent (logical sequence; no duplicates)
when the PW form is saved.
n Asset + "With children": "Code - Description format.
n Asset families + "With children"
n Brand
n Asset model
n Serial number
n Asset group: If an asset group is selected, the assets are added with the distribution defined in the group. Otherwise,
they are added with a distribution of 1.

To add assets from the same family, click on the button, select asset family, then click on the but-
ton. All the assets linked to the family in question are added to the PW.

By deleting one or more lines from the block, by clicking on the button at the head of the block or on the

button at the end of the line(s), the asset order is recalculated when the PW form is saved.
This sends a coherent asset processing order when converting a PW into a grouped WO.

Filter combination memorisation: all the filters applied for adding assets to each PW are memorised by the system. If, when a
new asset is created in a forthcoming version, that asset falls into any of the memorised PW filter combinations, the user will be
prompted to automatically add it to the PW.

Assets do not have to have the same entity as the PW (in multi-organisation mode)

Distribution
Input is open and must be numerical. (percentage, value, etc.). When calculating costs, the system calculates the actual dis-
tribution according to the number of assets and their distribution.
E.g. AST1 = 1 and AST2=3 if the cost=100, the cost will be distributed as follows: AST1=25 and AST2=75.

- 130 -
 Work settings

Collective updating of the asset distribution keys in a grouped PW: the button is used to modify
the distribution of several assets simultaneously. Select the assets to modify, then click on the button. Fill in the desired dis-
tribution for these assets in the pop-in displayed.
Note : The button allocates a distribution of 1 if all the assets are selected or no asset is selected.

Jobs

To view or add the asset jobs, click on the button provided on each asset line.
When adding a job, a message prompts you to retrieve the job resources.

If the same task of the same job is present on another asset and in the same order of fulfilment, the resources accumulate (Quan-
tity and time). When a job is deleted, the resources are subtracted from the common line (quantity and time).

Resource lines with times or durations of 0 are automatically deleted.

The Task type and Meter/Measurement columns have the same characteristics as for the WO form, and are visible in the job line
details.

In the case of tree partitioning, for Guest and User accounts, the asset can be viewed if it is authorised, otherwise it is only visible
in the block.

General information block

n Cost allocation: Cost allocation tree pop-in. When the PW only contains one asset, when the PW is saved, the PW cost
allocation is the same as the asset's. If you edit the asset's cost allocation, this is automatically applied to the PW. The
PW's cost allocation can still be edited to be different to the asset's cost allocation and is not updated in this case
then the asset's cost allocation is edited. If you have grouped work generating a grouped WO, the cost allocation is
blank by default when saving. If the PW's cost allocation is not entered, then the child WOs' cost allocation is the cost
allocation of their asset. If the PW's cost allocation is entered, it applies to the grouped WO and all its child WOs.
n Recipient: Selection list. Displays the list of users that have the technician role.
n Technology: Selection list.
n Work forbidden in service: Check box. Retrieves the value of the work model, but can still be changed. Its modi-
fication causes the pop-in of deletion of the link between PW and model.
n Last generated work order: Code of the last WO, non-modifiable.
n Contract: if the subcontractor contract module is enabled, it is possible to link a contract with the PW. The list only
displays the contracts linked to at least the PW entity, and if all PW assets are in the contract. The contract that may
be linked depends on the technology and the type of work. When transforming a PW occurrence, this contract is reco-
vered in the work order generated.

Comment block

Used to enter detailed information about the work.

Trigger block

- 131 -
 Work settings

Click on the button and select a trigger in the selection list.

n The calendar triggers are displayed if no meter is assigned to the asset.

n The calendar and meter triggers are displayed if the asset is linked with a meter.

When selecting a meter type trigger:

l the user must select a meter in the selection list of the meters associated with the asset.
l the Initialisation threshold can be changed
l the Method for triggering the PW into a WO field can be changed
l the Method for triggering the PW into a WO field is initialised according to the general setting Method for triggering IP
meters to convert to WO by default

Note : If the grouped work module is enabled, several different assets can be added to the PW. Then, if one or more assets asso-
ciated with the PW are equipped with meters, meter-type triggers are proposed in the PW; if none are equipped with meters, no
triggers are proposed.
When adding a meter-type trigger, all the meters of all the PW assets are displayed in the list of meters along with the asset to
which they are linked.

Click the button to validate the input.

The occurrences are calculated when the PW is saved.
For further information about the types of triggers, refer to the Triggers section.
For details of occurrence scheduling, refer to the Occurrences block section.

Resources block

Several types of resources may be needed:

Workforce (WF)

Sub-contractor (SC)

Part

Downtime

This screen is used to plan work for each type of resource.

- 132 -
 Work settings

The resource lines indicate which task they originate from, if that is the case.

Resources - PW workforce

Click on the button then select the type of Workforce.

n The subcontractor category is a required field.

A technician category can be assigned to a PW without selecting a technician.

n The list of subcontractors is then filtered to the users belonging to the defined category.

When a technician is selected, his or her main category is entered automatically. It can nevertheless be changed by selecting in
the list another category linked with the technician's user profile.
The list of technicians displays only the users whose profile includes the technician role.

n Duration: Required. Planned work duration (hours).

When all the fields are filled, click the button to validate the entry or the button to ignore
the entry.
Resources – PW parts

Click on the button then select the type of Part.

n Assign to: blank if there is no WF or SC resource in the PW. Otherwise, displays the list of technicians and sub-
contractors of the PW resources and the planned duration. Used to assign the parts to the various internal or external
technicians of the PW.
n Part: Selection drop-down list or pop-in. Displays the descriptions of the parts.
n Description: Description for a part not listed in stock.
n Warehouse: Drop-down list. Offers the entity warehouses if the part is not in stock; displays the default warehouse of
the entity if the part is in stock. Enables you to specify in which warehouse the part will be reserved and/or desto-
cked.
n Planned quantity: indicates the planned quantity for the work.
n Planned unit: default unit of the part. The list displays only the units convertible with the default unit of the part.
n Reserved: Check box. Enabled by default when the part is added. If the box remains enabled, the quantity of the part
reserved and available is updated upon conversion of the PW to WO/grouped WO.

For the parts listed in stock, the required fields are: Date, Part, Quantity, Unit.
For the parts not listed, the required fields are: Date, Description, Quantity; the Warehouse field is blank and can be edited.
Resources - PW subcontractors

Click on the button then select the type of Subcontractor.

n Category: Required. Displays the partner categories.

n Subcontractor: Drop-down list. Displays all the partners that are subcontractors.

- 133 -
 Work settings

n Duration: Required. Planned work duration (hours).

n Part cost/Currency: the cost of the parts needed for the work in the PW currency

When all the fields are filled, click the button to validate the entry or the button to ignore
the entry.
When a subcontracting line is added via a job, if the part cost is input in a currency different to the PW currency in the task, it is
converted into the PW currency and the currency cannot be changed.
Resources – PW downtimes

Click on the button then select the type of Downtime.

n Assign to: blank if there is no WF or SC resource in the WO. Otherwise, displays the list of technicians and sub-
contractors of the WO resources and the planned start date and duration. Used to assign the downtime to the
various internal or external technicians of the WO.
n Duration: Required. Planned work duration (hours).

When all the fields are filled, click the button to validate the entry or the button to ignore
the entry.

Occurrences block

The occurrences are calculated when the PW is saved.

The list displays the occurrences that have not yet been converted to WOs in a Date column. The converted occurrences are
visible in the Work orders block of the PW.
The number of occurrences is limited to 20.

A second column, Trigger meter value, enables you to associate the trigger meter’s theoretical value with the theoretical date for
WO conversion.
This value is only shown for PWs with a periodic or aperiodic type trigger (irrespective of the trigger method).
It is not updated for non-rolling PWs.
It is updated for rolling PWs according to the reading at the origin of the trigger, or according to the reading entered in the WO.

- 134 -
 Work settings

For rolling PWs, you cannot close a WO that originates from them on a date prior to the date of the previous occurrence (calen-
dar trigger) or with a meter reading below the trigger value of the previous occurrence (meter trigger).

o Calendar trigger/rolling schedule

The reference date is the last end date of the closed work order or, failing this, the initialisation date of the PW.
The time interval of the PW trigger is added to the reference date.

o Calendar trigger/non-rolling schedule

The reference date is the PW initialisation date.

The time interval of the PW trigger is added to the reference date.

In all cases, the first occurrence has to be after the last start date of the work order originating from the PW.
 The occurrences are calculated over 2 years if their time interval is less than 2 years.

o Meter trigger

The meter PW occurrences are calculated when a meter reading is saved and when the PW is saved if there are already two
meter readings.
An occurrence is calculated by adding the daily average to the value of the meter in the WO and searching for the corresponding
dates at the same threshold value, at a regular frequency.

No occurrence dates prior to any end date of a work order originating from the PW, nor prior to any last WO reading, are cal-
culated.

o Meter trigger/rolling schedule

When a WO originating from a rolling periodic meter PW is closed, the date of the next occurrence is recalculated according to
the end date of the WO, to which the daily average of the meter is added.

o Meter trigger/non-rolling schedule

In the case of a non-rolling periodic meter PW, the date of the next occurrence is recalculated according to the occurrence date
of the last generated WO, to which the daily average of the meter is added.
No date prior to the last meter reading will enable occurrences to be calculated.

To initialise start and end times for a WO from the conversion of a PW projected in time (calendar or meter trigger) or a PW for
meter reading reached (meter trigger), the management rule for Company/Entity opening hours must apply.

In the case of tree partitioning, for Guest and User accounts, the button is only visible if all the
assets are authorised.

Costs block

- 135 -
 Work settings

Indicates the estimated costs for the PW resources in the PW currency:

n Workforce
n Subcontractor
n Parts
n Downtimes

Associated files block

Files necessary for completing work can be linked with the PW.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Asset files block

Displays the files associated with the asset; files cannot be added or deleted here.

Work orders block

Displays the work orders originating from the preventive work. The list can be used to view the following information for each
WO: priority, start date ('Day: Hour: Minute" format), code, title, status, type of work, technology.

n Click on the WO line to view additional information: end date ("Day: Hour: Minute" format), issuer, cost allocation.

n Click on the icon to open the WO form in a new tab.

The user must have the appropriate rights to view the item.
The WO generated uses the PW Part/Warehouse pair.

Grouped work orders block

Visible if the grouped work module is enabled, displays the grouped work orders from the preventive work. The list can be used
to view the following information for each grouped WO: priority, start date ("Day: Hour: Minute" format), code, title, status, type
of work, technology.

n Click on the WO line to view additional information 

n Click on the icon to open the WO form in a new tab.

The user must have the appropriate rights to view the item.

Tree structures block

Visible if the preventive work only has one asset, this block displays:
- The asset tree
- The asset families tree
- The cost allocation tree

These trees correspond to the current location of the asset.

- 136 -
 Work settings

Priority preventive work

Preventive maintenance works for the same asset can be triggered with different time intervals that are
sometimes linked to each other: a monthly, quarterly and annual visit.

As part of optimisation, in particular of the preventive schedule, the purpose of priority preventive works is
to enable the maintenance manager to define that the visit with the largest time interval becomes the
only visit triggered, as it encompasses both the monthly and quarterly visit.

A Priority preventive work will be linked to only one asset.

The type defined will ensure that for this asset, only periodic calendar preventive works (Calendar type)
or preventive works on the same periodic meter when a value is reached (Meter type) are linked to each
other.

A margin, in days for Calendar types or in meter units for Meter types, enables you to define the prio-
ritisation between preventive works.
When the difference between trigger dates or trigger meter values is strictly below the margin, the rule
will be to only trigger the preventive work with the largest time interval.

Example 1: a margin of 8 days defined. With a monthly preventive work scheduled for 01/07/2020 and a
quarterly preventive work scheduled on 05/07/2020, only the quarterly preventive work will be triggered.

Example 2: a margin of 500 meter units defined (hours in the example). With a preventive work scheduled
every 1,500 hours (occurrences at 1,500, 3,000, 4,500, etc.) and a preventive work scheduled every 3,000
hours (occurrences at 3,000, 6,000, 9,000, etc.), when you reach 3,000 hours, only the preventive work
every 3,000 hours will be triggered.

The Occurrences block on your priority preventive work form enables you to monitor this prioritisation with
the Comments column which indicates the lower priority occurrences that will not be triggered.
This Occurrences block is automatically updated every day by the PW trigger robot.
It is also updated when the priority preventive work form is opened to take into account any changes made
to the preventive works it includes.

List of priority preventive work

The list is accessible through the menu [Work-Priority preventive work].
The list displays all the non-archived priority PWs, sorted in ascending order of the priority PW codes.

Filtering to an asset brings up all the priority PWs that reference the asset in question.
All priority PWs only have one asset (unlike grouped PWs).

The available actions depend on the user rights [Settings-Users-User profiles].

If the "Tree partitioning" module is enabled, the list of priority preventive work items visible, for User and Guest accounts, is res-
tricted to those with at least one authorised asset.

- 137 -
 Work settings

Creating a priority PW

A PW can be created:

n with the button on the list of PWs.

n from the assets tree by clicking on the button or by right-clicking on an asset/Create a PW.

n by clicking on the button on the PW form.

n from the home screen via the Widget tree by clicking on the button or by right-clicking on an asset/Create
a PW.

For further explanation on creating a PW, refer to the Preventive work form.

Deleting a priority PW

To delete a team:

n click on the button on the form or list of priority PWs.

n from the list of priority PWs, click on the button at the end of the line.

Multiple deletion is possible.

A confirmation message is displayed to confirm the deletion.
You can delete a priority PW if the PWs it contains have not yet been deleted; you therefore have deletion in two stages:
1. Deletion of the preventive works block PWs
2. Deletion of the priority PW

Archiving/De-archiving a priority PW

A priority PW can be archived:

n by clicking on the button on the list of PWs, or the priority PW form.

n from the list of priority PWs, by clicking on the arrow at the end of the line.

Archiving the priority PW does not archive the PWs that it contains, but ends their prioritisation process (each PW goes back to its
individual trigger cycle).

The icon is displayed to the left of the code and the priority PW title, indicating that it has been archived.
Archived priority PWs are no longer visible in the drop-down lists or the search fields.

A PW can be de-archived:

- 138 -
 Work settings

n by clicking on the button on the list of PWs, or the PW form.

n from the list of PWs, by clicking on the arrow at the end of the line.

The PW is no longer archived and is displayed again in the selection lists and search fields.

- 139 -
 Priority preventive work

Priority preventive work

Priority preventive work form

Accessible from the menu [Work-Priority preventive work].

Click the button to access the form for creation or on the button to view a priority PW.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Priority preventive work list.

The icons give access to the various forms or to the corresponding repositories. (Asset form, type of work, small priority
tables etc.) so that information can be viewed or modified during entry.

Header block

The header block defines the main information of the PW.

n Code: Required field: the code of a PW is unique

n Title: Required field
n Entity: only if multi-organisation mode is enabled.
n Asset (+ Icon (Twins)): Selection list (+ Tree) required
n Type: Calendar/Meter
n Margin: Positive integer; "0" by default

Comment block

Used to enter detailed information about the priority preventive work.

Preventive works block

Displays the preventive work added to the priority preventive work.

PWs added are of the same type as their priority PW (Calendar or Meter).

- 140 -
 Priority preventive work

The list enables you to view the following information for each PW: code, title, trigger, date of next occurrence
("Day/Month/Year" format), rolling (choice: "Yes" / "No").

n Click on the icon to open the PW form in a new tab.

n Click on the button to open the PW selection pop-in entitled: "Select the preventive work for the asset
'Code - Description'"

The user must have the appropriate rights to view the item.
Aperiodic PWs and meter type PWs projected in time cannot be added to a priority PW form (only periodic PWs can be added).
Grouped PWs, just like PWs that are already present in a priority PW form, or PWs with the same time interval cannot be added
either.
To be added, Meter type periodic PWs cannot have different meters.

Margin control: the margin must be strictly below the smallest time interval of PWs added to the block.
Otherwise, for Calendar type PWs, a blocking message will appear: "Cannot save. The margin must be strictly below the smallest
time interval (XXX)" where XXX is the smallest PW time interval, in "Number of periods + time interval" format.
References:
1 Week: 7-day basis therefore maximum margin of 6 days
1 Month: 28-day basis therefore maximum margin of 27 days
1 Year: 364-day basis therefore maximum margin of 363 days

For Meter type PWs, a blocking message will appear: "Cannot save. The margin must be strictly below the smallest frequency
(XXX)" where XXX is the smallest PW time interval, in trigger "Frequency value" format.

Modification of a PW that has been added :

- the manual conversion of a PW's occurrence into a WO results in the update of the priority PW occurrences block
- changes to a PW's occurrences (by modifying the trigger, the initialisation date or the initialisation threshold) result in the modi-
fication of priority PW occurrences
- if the PW time interval becomes below or equal to the priority PW's margin, the following blocking message is generated:

l Calendar PW: "Cannot save. The time interval (Number of periods + time interval) is below or equal to the margin of
the priority preventive work 'Code - Title'. First modify the margin to save your changes"
l Meter PW: "Cannot save. The frequency (Frequency value) is below or equal to the margin of the priority preventive
work 'Code - Title'. First modify the margin to save your changes"

- modification of the trigger type: in Aperiodic, from Calendar to Meter with the value being reached or vice versa, generates the
blocking message: "Cannot save. First delete this work in the priority preventive work 'Code - Title' to save your changes. The trig-
ger is incompatible with the priority preventive work"
- adding an asset to a PW, converting it from a single PW to a grouped PW, generates the blocking message: "Cannot save. First
delete this work in the priority preventive work 'Code - Title' to save your changes. A multi-asset PW cannot belong to a priority
preventive work"

Deletion of a PW that has been added (from the form or the PW list) :
- if the PW has generated a WO, deleting the PW generates the blocking message: "Cannot delete. Used in the work order 'Code -
Title'"
- if the PW has not generated a WO, deleting the PW generates the blocking message: "Cannot delete. Used in the priority pre-
ventive work 'Code - Title'"

- 141 -
 Priority preventive work

Archiving a PW that has been added (from the form or the PW list): not allowed if the PW has not first been deleted from the pri-
ority PW form, generating the blocking message: "Cannot archive. Used in the priority PW 'Code - Title'. First delete this work in
the priority preventive work to save your changes.

Sorting PWs: the PWs present in the block are sorted by increasing time interval for Calendar types and by increasing frequency
for Meter types; the same sorting rules apply to the PW selection pop-in, with the presence of a "Meter" column for Meter type
PWs as the difference, resulting in an initial sorting by meter code

Management of rolling PWs: closing a WO originating from a rolling PW belonging to a priority PW results in all the rolling PW
occurrences on the priority PW being rescheduled; and the non-rolling PW occurrences not being rescheduled.

The rescheduling that applies to each occurrence is the difference between the closed WO end date and its initial date of occur-
rence.

Example 1: All the PWs of my priority PW are rolling

Rolling Monthly PW scheduled on the 1st of each month: 01/01, 01/02, 01/03…
Rolling Quarterly PW scheduled on 5/03 then 05/06...
Rolling Annual PW scheduled on 10/06

My WO of the monthly PW for January is closed with an end date on 05/01 i.e. a "positive" difference of 4 days. This difference is
added to all the PW occurrences.
Next occurrences:
- Monthly PW: 05/02, 05/03…
- Quarterly PW: 09/03, 09/06…
- Annual PW: 14/06

Example 2: Some of the PWs of my priority PW are rolling

Rolling Monthly PW scheduled on the 1st of each month: 01/01, 01/02, 01/03…
Rolling Quarterly PW scheduled on 5/03 then 05/06...
Non-rolling Annual PW scheduled on 10/06

My WO of the monthly PW for January is closed with an end date on 05/01 i.e. a "positive" difference of 4 days. This difference is
added to all the rolling PW occurrences.
Next occurrences:
- Monthly PW: 05/02, 05/03…
- Quarterly PW: 09/03, 09/06…
- Annual PW with no change because not rolling: 10/06

Occurrences block

The occurrences are calculated when the PW is saved in the previous block.
The list displays the occurrences that have not yet been converted into WOs in a Date column for period of 24 months.
A second column, Trigger meter value, enables you to associate the trigger meter’s theoretical value with the theoretical date for
WO conversion.
This value is only indicated for PWs with a Meter type trigger.

- 142 -
 Priority preventive work

Update

l daily, by the PW robot

l when the form is saved, when adding a PW or modifying the priority PW's margin
l when opening the priority PW form, to take into account any changes to the attached PWs.

Calculation method

l Calendar type PW

When the different PWs' occurrence dates have a difference below or equal to the margin (in days) defined in the form header,
then the PW that has the trigger with the largest time interval takes priority and will be the only one triggered.
The occurrences of the other PWs are not triggered and carry the phrase: "Will not be triggered - PW ('XXX') takes priority".

l Meter type PW

When the different PWs' occurrences' trigger meter values have a difference below or equal to the margin (in meter units)
defined in the form header, then the PW that has the trigger with the largest time interval takes priority and will be the only one
triggered. The occurrences of the other PWs are not triggered and carry the phrase: "Will not be triggered - PW ('XXX') takes pri-
ority".

- 143 -
 Priority preventive work

List of work requests

The list is accessible through the menu [Work-Work requests].
The list displays the non-archived WRs, sorted in ascending order of the WR codes. It is also possible to sort by alert status and

deadline (by alert icon ).

Taking into account the restriction due to tree partitioning, only WRs on the authorised assets and WRs without assets of the
authorised entities are displayed.

The available actions depend on the user rights and the WR status [Settings-User-User profiles] and [Settings-Work-WR status
administration].

Creating a WR

A WR can be created:

n with the button on the list.

n from the assets tree by clicking on the button or by right-clicking on an asset/Create a WR.

n by clicking on the button on the WR form.

n from the home screen by the Widget tree by clicking on the button or by right-clicking on an asset/Create
a WR.
n from the home screen by Work Request widgets, "My WR info" and "My delayed WR alerts".

For further explanation on creating a WR, refer to the WR form.

- 144 -
 Priority preventive work

Deleting a WR

To delete a team:

n click on the button on the form or list of WRs.

n from the list of WRs, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A WR cannot be deleted:
- if it is cited in another document (WO)
- if it has been converted into a work order
- if it is in In progress, Completed or Closed status

Archiving/De-archiving a WR

A WR can be archived:

n by clicking on the button on the list of WRs, or the WR form.

n from the list of WRs, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the code and the WR title, indicating that it is archived.
Archived WRs are no longer visible in the drop-down lists or the search fields.

Only cancelled or closed WRs can be archived.

A WR can be de-archived:

n by clicking on the button on the list of WRs, or the WR form.

n from the list of WRs, by clicking on the arrow at the end of the line.

The WR is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a WR

To duplicate a team:

n by clicking on the button on the WR form.

n from the list of WRs, by clicking on the arrow at the end of the line.

Duplication copies the selected WR to a new WR. All the information is duplicated except:

- 145 -
 Priority preventive work

n Code
n Description
n Status: initialised at "To be processed"
n Requester: initialised with the logged-in user
n Creation date: initialised with the day's date
n Deadline time/date: initialised according to the creation date and the priority
n Comment

Cancelling a WR

A WR can be cancelled:

n by clicking on the button on the WR form.

n from the list of WRs, by clicking on the arrow at the end of the line.
n by changing the WR status to Cancelled.

During cancellation:

n The WR takes on Cancelled status or the status configured in the administration of WR settings for this action, if it is
enabled.

It is possible to configure authorisations for WR modifications according to their status in the menu [Settings-Work-Admin-
istration of WR statuses]. Therefore, a cancelled WR can become non-modifiable.

Closing a WR

A WR is closed by changing its status to Closed.

It is possible to configure authorisations for WR modifications according to their status in the menu [Settings-Work-Admin-
istration of WR statuses]. Therefore, a closed WR can become non-modifiable.

Reopening a WR

A WR can be reopened:

n by clicking on the button on the WR form.

n from the list of WRs, by clicking on the arrow at the end of the closed WR line.

When it is reopened, the WR takes on the status configured in the administration of WR status settings for this action.

The user must have the "Reopen WR" role in the settings of his or her Profile – Roles block.
The "Reopen WR" action must be enabled in the WR status administration settings.

Converting a WR into a WO

A WR can be converted into a WO:

- 146 -
 Priority preventive work

n By clicking on the button on the WR form, in the list of WRs.

n From the WR form, by clicking on the button .

It is possible to authorise or forbid conversion of WRs into WOs depending on the WR status. It is configured through the menu
[Settings-Work-Administration of WR statuses]. Therefore, a closed WR can no longer be converted into a WO.
As soon as conversion is possible, the tab of the Work order form is highlighted (orange), and if the user closes the Work order
before saving it, the following confirmation is displayed:
"The following action requires a response from you: Save the work order before exiting".

A WR can be converted into a WO several times. However, several WRs can only generate a single WO.
The reference to the WR is stored on the WO generated. The WOs generated are displayed in the WR Work orders block.

The reference to the PW and the occurrence date are stored in the generated WO.

WO field initialisation from the WR fields:

o Code: blank
o Title: Title
o Status: To do 
o Asset:
o Type of work: Type of work
o Priority: Priority
o Technology: Technology
o Start date: Days' date
o End date: Days' date
o Asset off: Asset off
o Comment: Comment
o Issuer: logged-in user
o Creation date: Days' date
o Duration: 1
o Technology: Technology
o Cost allocation: Cost allocation

If a WO is to be generated when there is no automatic codification, alternative codification is established consisting of just a
numerical meter.

For further explanation on creating a WR, refer to the WR form.

Accept the work

Once the WR has been completed, it is possible to accept the work by clicking on the button .
This action can be performed:
- If the WR is in "Completed" status
- If the "Accept work" action is enabled in WR status administration or email administration.

The WR then changes to configured status in WR status administration.

Refuse the work

- 147 -
 Priority preventive work

Once the WR has been completed, it is possible to refuse the work by clicking on the button and entering
a comment in order to explain the refusal.
This action can be performed:
- If the WR is in "Completed" status
- If the "refuse work" action is enabled in WR status administration or email administration.

The WR then changes to configured status in WR status administration.

- 148 -
 Work settings

Work request form

Accessible from the menu [Work-Work requests].
The available actions depend on the user rights and the WR status. [Settings-Users-User profiles] and [Settings-Configuration-WR
status administration]

The New, Delete, Archive, Convert into WO and Duplicate buttons are explained in the actions of the Work requests list.

The icons give access to the various forms or to the corresponding repositories. (Asset form, type of work, small priority
tables etc.) so that information can be viewed or modified during entry.

Some actions performed on the WR may trigger an email notification: WR creation, WR conversion into a WO, reopening a WR,
etc.
For more information about activation and configuration, refer to the Email administration section.

Header block

The header block defines the main information of the WR.

n Code: Required field: the code of a WR is unique.

n Title: Required field.
n Status: List of choices (required) of reference statuses and equivalent. When created, a WR has the status defined in
the WR status administration for the "Create WR" action if it is enabled. If it is disabled, the WR status is "To be pro-
cessed" by default.

See the [WR statuses] and [WR status administration] sections for more information.
The status of WRs can be changed:

n Manually, in the WR form, by selecting the status in the list of available statuses,
n Automatically according to the actions performed, depending on the settings defined through the menu [Settings-
Work-WR status administration].

If a WO changes to 'Done' or 'Closed' status manually, if you accept the work from the form of a WR in 'Completed' status, you
have an automatic response to job tasks without response. They take the value 'Cannot be completed'.

- 149 -
 Work settings

The status change history of a WR can be viewed by clicking on the icon in the WR header block. The pop-in displays the
date, the status and the user for each status change.

n Requester: List of choices of users with the Requester role (required). By default, the logged-in user, if the user has
the requester role.
n Entity: Visible only if the number of entities in the licence key is above 1. The WR must be associated with an entity
(and can only be associated with one entity).

The user's main entity is retrieve and the non-archived entities are displayed in the list.
The user must as least have editing rights for work requests (for each entity displayed).

Some WR fields are filtered according to the entity selected:

- WR type
- Asset family

When the WR entity is changed, the data is updated:

- the data selected are kept, if it is associated with the new entity
- the data is blank, if it is not associated with the new entity.

n Asset: Tree pop-in or Typeahead, only suggesting assets authorised by the tree partition
n Location:
n Creation date: (Required) the current date by default
n Priority: Selection list (optional). The priority is displayed according to the criticality of the asset.
n Asset off: Check box (by default = No)
n Recipient: List of choices of users with the Technician role (required). Multiple recipients can be selected. Depending
on the WR type, displays the recipient(s) defined in the WR recipient administration by default
n Effect: Selection list (displayed only if the diagnosis module is enabled in the company form)

Comment block

Comments are displayed in discussion mode in order to have a trace of their history.
Comment are displayed in chronological order, from the most recent to the oldest.
Their number is displayed on the Comments block if it is folded.

Click on the button to open the comment input pop-in. Enter the comment then click on the button

to go back to the WR.

- 150 -
 Work settings

The comment is added to the list of comments, with the name and photo of the user who entered it. It is possible to zoom on
the photo.
Each comment can be unfolded and folded.

A comment entered by another user cannot be modified or deleted.

General information block

Enables the user to define additional information about the WR:

n Type of work: Selection list (required); it is possible to configure WR recipients according to the WR type. See the WR
recipient administration section.
n Technology: Selection list
n Cost allocation: Cost allocation tree pop-in. Retrieves the asset cost allocation.
n Deadline date/time: The WR deadline date/time is automatically recalculated according to the WR creation date and
the lead time defined in terms of priority.
n WR type: Selection list.

Tree structures block

The tree structures block screen displays the histories of the various trees of the WO at the time of the order:

n asset tree
n asset families tree
n cost allocation tree

Work orders block

Displays the work orders originating from the work request. The list can be used to monitor the resolution of the failure and view
the following information for each WO: priority, start date "Day: Hour: Minute" format), code, title, status, type of work, tech-
nology.

n Click on the WO line to view additional information: end date ("Day: Hour: Minute" format), issuer, cost allocation.

n Click on the icon to open the WO form in a new tab.

In the case of tree partitioning, for Requester, Guest and User accounts, the WO can be viewed if its asset(s) is/are authorised,
otherwise it is only visible in the block.

The user must have the appropriate rights to view the item.

Associated files block

Files necessary for completing work can be linked with the WR.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Asset files block

Displays the files associated with the asset; files cannot be added or deleted here.

- 151 -
 Work settings

Completion preference block

Used to suggest the most favourable periods for the work by selecting date and time intervals.

Click on the button to enter date/time preferences.

n Start date: date/time, required

n End date: date/time, required
n Comment: text field

Default sorting is chronological and adding dates enables you to insert new completion preferences in the same ascending order.

If the Start date and End date are entered, these start/end dates/times are used to initalised the start/end date/times of the WO
header.

If no completion preference is entered the conversion date/time becomes the WO Start date and the WO End date is equal to
the Start date + 1H.

Work orders

List of work orders

The list of work orders is accessible through the menu [Work-Work orders].
The list displays all the non-archived WOs, sorted in ascending order of the WO codes. It is also possible to sort by alert status

and deadline (by alert icon ).

Once opened in a tab, the list of WOs must be updated as soon as a new item is created (necessity associated with the per-
formance gain of the list display).

The available actions depend on the user rights and WO status. [Settings-Users-User profiles] and [Settings-Work-WO status
administration]

Grouped WO : If the grouped work module is enabled, the grouped WO will not be displayed in this list, only the child WOs with

a button at the end of the line for accessing the grouped WO . A filter is nevertheless provided in the advanced filters allo-
wing you to find the child WOs linked to the grouped WO.
Refer to the sections grouped work and list of grouped WOs.

Creating a WO

A WO can be created:

n with the button on the list of WOs.

n from the assets tree by clicking on the button or by right-clicking on an asset/Create a WO.

n by clicking on the button on the WO form.

- 152 -
 Work settings

n from the home screen by the Widget tree by clicking on the button or by right-clicking on an asset/Create
a WO.
n by converting a WR to a WO,
n by converting a PW to a WO.

For further explanation on creating a WO, refer to the WO form.

Deleting a WO

To delete a team:

n click on the button on the form or list of WOs.

n from the list of WOs, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A WO cannot be deleted:

- if it is cited in another document

- if it has completion information in the resources
- if any of its tasks are checked as completed
- if its status is Completed or Closed
- if it has included a meter reading.

When a WO is deleted, the stock is updated with the quantities of parts reserved and not consumed.

Duplicating a WO
To duplicate a team:

n by clicking on the button on the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

Duplication copies the WO to a new WO, reproducing certain information:

n Header block:

o duplicated fields: title, asset, type of work, priority, asset off

o fields not duplicated: code, status –> To do, start date -> current date, end date -> current date

n Comment bloc: not duplicated

n General information block

o duplicated fields: technology, cost allocation,

o fields not duplicated: issuer -> logged-in user, date of creation, duration = 1

n Resources block

- 153 -
 Work settings

o duplicated fields: planned durations and quantities, assignment

o fields not duplicated: resource date -> new WO start date, completed durations and quantities

n Diagnosis bloc: duplicated

n Jobs block: duplicated except completion
n Tree structures block: duplicated
n Costs block: The data correspond to the duplicated resources
n Associated files block: duplicated
n Asset files block: duplicated

The jobs' task types are duplicated (order, icon, task description).
The meter name or the measurement saved are duplicated (or blank if no value saved).
The responses are deleted (value/date input or Not completed box checked).

Archiving/De-archiving a WO

A WO can be archived:

n by clicking on the button on the list of WOs or the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the code and the WO title, indicating that the WO is archived.
Archived WOs are no longer visible in the drop-down lists or the search fields.

Only cancelled or closed WOs can be archived.

A WO can be de-archived:

n by clicking on the button on the list of WOs, or the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

The WO is no longer archived and is displayed again in the selection lists and search fields.

Closing a WO

A WO can be closed:

n by clicking on the button on the list of WOs or the WO form.

n from the list of WOs, by clicking on the button at the end of the line.

To close a work order automatically, without having to change the status manually, you must enable the ‘Close WO’ action in
WO status administration and configure an arrival status. Otherwise the WO cannot be closed.

n by manually changing the WO status to Closed (or equivalent).

- 154 -
 Work settings

Under all circumstances, the user must have the 'Close WO' role in the settings of his or her profile – Roles block.

l Resources update

On closing the WO, all the resource lines are marked completed so that they are no longer seen in the schedules of the tech-
nicians.
For all part lines on which the quantity used is less than the reserved planned quantity -> the reserved quantity is reduced by the
difference between planned and used quantities.

l Parts list update

l Job parts list update

l Diagnoses update

If the asset is not associated with the items in the WO, the association is established.

l Calendar preventive plan update

o When a work order originating from a PW on a rolling schedule is saved and changes status to Closed or equi-
valent, the PW occurrences are recalculated. The occurrences recalculation is based on the end date of the
WO. (Does not reschedule an occurrence on a date prior to any occurrence already converted into a WO).

o  If an upcoming occurrence has already been converted to a WO, recalculate the occurrences, in the case of a
rolling schedule, from the end date of this WO.

l Meter preventive plan update

When a WO originating from a rolling periodic meter PW is closed, the date of the next occurrence is recalculated according to
the end date of the WO, to which the daily average of the meter is added.

l Automatic response to job tasks without response

When a WO is closed from the list of WOs or grouped WOs, we have an automatic response to tasks without response. They
take the value 'Cannot be completed'.

Reopening a WO

A WO can be reopened:

n by clicking on the button on the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

During reopening:

n The WO changes to the status defined for the Reopen work order action in the WO status administration settings
n If the WO includes lines of reserved parts with quantities not consumed, the reservations in the stock are updated.
n If the WO resource dates are not included between its Start date and End date, you can still reopen it

The user must have the Reopen work order role in the settings of his or her profile – Roles block.
The Reopen work order action must be enabled in the WO status administration settings.

- 155 -
 Work settings

Cancelling a WO

A WO can be cancelled:

n by clicking on the button on the list of WOs.

n from the list of WOs, by clicking on the arrow at the end of the line.
n by changing the WO status to Cancelled or equivalent.

During cancellation:

n The WO status changes to Cancelled or equivalent

n If the WO includes lines of reserved parts with quantities not consumed, the reservations in the stock are cancelled.

The user must have the Close work order role in the settings of his or her profile – Roles block in order to be able to cancel a WO.

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Status: Drop-down list, with the choices: - “To do”, “In progress”, “Done”, “Cancelled” and “Closed” + equivalent sta-
tuses.
n Asset family: Typeahead and standard search window of asset families, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Asset: Typeahead and standard search window on assets filtered to the authorised assets and their parents (even if
not authorised) of the logged-in user's entities. Associated with: “With children” check box.
n Criticality: Selection list.
n Type of work: Selection list.
n Priority: Selection list.
n Issuer: Selection list.
n Start date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n End date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Creation date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Asset off: Choices: Yes/No/All
n Technology: Selection list.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Subcontractor category: Selection list.
n Technician: Selection list.
n Subcontractor category: Selection list.
n Subcontractor: Selection list.
n Part: Typeahead and standard part search window, filtered to the logged-in user’s entity/ies.
n Effect: Selection list.
n Cause: Selection list.
n Remedy: Selection list.
n Job: Selection list.
n Preventive work: Text field. Automatic filter upon entry. Only returns PWs with at least one authorised asset.

- 156 -
 Work settings

n Work request: Text field. Automatic filter upon entry. Only returns the list of requests with an authorised asset and
the requests with no assets of the logged-in user's entities.
n Deadline (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon. Sets the
work completion time limit.
n Grouped work order: Text field. Automatic filter upon entry. Only returns grouped WOs with at least one Child WO on
an authorised asset and the grouped WOs with no assets (without Child WOs) of the logged-in user's entities.
n Work model: Text field. Automatic filter upon entry. Blank by default. List of WOs filtered according to the "Code-
Title" of the work model selected.

Work order form

Accessible from the menu [Work-Work orders].

Click the button to access the form being created or on the button to view a WO.

The available actions depend on the user rights and WO status. [Settings-Users-User profiles] and [Settings-Configuration-WO
status administration].
The New, Delete, Archive, and Duplicate buttons are explained in the actions of the Work orders list.

The icons give access to the various forms or to the corresponding repositories. (Asset form, type of work, small priority
tables etc.) so that information can be viewed or modified during entry.

Some actions performed on the WO may trigger an email notification: WO creation, adding a technician line, WO closure, etc.
For more information about activation and configuration, refer to the sections on Email administration and Managing how
emails are sent with grouped WOs (if the grouped work module is enabled).
Late WOs can trigger a alerts (visual alerts or email notifications). Refer to the section Alerts-Notifications.

How the blocks and fields are displayed and the mandatory fields for saving can be configured by user profile. Refer to the sec-
tion Screen settings.

Header block

The header block defines the main information of the WO.

- 157 -
 Work settings

n Code: Required field: the code of a WO is unique.

n Title: Required field.
n Status: Selection list (required). When created, a WO has the status defined in the WO status administration for the
Create work order action if it is enabled. If it is not enabled, the status of the WO is To do. In order for the Closed and
Cancelled (and equivalent) statuses to be displayed in the list of WO statuses, the user must have the 'Close work
order' role in the settings of his or her Profile-Role block.

WO status changes

The status of WOs can be changed:

n manually, in the WO form, by selecting the status in the list of available statuses,
n Automatically according to the actions performed, depending on the settings defined through the menu [Settings-
Configuration-WO status administration].

The status change history of a WO can be viewed by clicking on the icon in the WO header block. The pop-in displays the
date, the status and the user for each status change.
The following statuses are available:

n To do or equivalent
n In progress or equivalent
n Done or equivalent
n Cancelled or equivalent
n Closed or equivalent

In order for the Closed and Cancelled (or equivalent) statuses to be displayed in the list of WO statuses, the user must have the
'Close work order' role in the settings of his or her Profile-Role block.

l WO changing to To do status or equivalent:

o for all active actions in the WO status administration settings for which this status is defined,
o if the actions are inactive, the WO status is To do:

n when a new WO is created

n when a WR is converted to a WO
n when a PW is converted to a WO.

l WO changing to Cancelled status or equivalent -> see the Cancelling a WOsection

l WO changing to Closed status or equivalent -> see the Closing a WOsection

For more information on WO statuses, see the WO statuses and WO status administrationsections

n Asset: Asset: tree pop-in (required)

n Type of work: Selection list
n Priority: Selection list (optional). The priority is displayed according to the criticality of the PW asset.
n Start date: "Day: Hour: Minute" type (DateTime, in the format DD/MM/YYYY HH: MM): WO creation date by default
(=WO trigger date if it is from a PW triggered by actually reaching a value)
n End date: "Day: Hour: Minute" type (DateTime, in the format DD/MM/YYYY HH: MM): WO creation date by default +1

The start and end dates of the WO are updated according to the start and end dates of the planned or actual resources for the
work.

Initialisation of WO start and end times based on the start and end times of the resource to avoid blocking messages:

- 158 -
 Work settings

- Modification of the start date of the WO/grouped WO to the start date of the first resource: the time must be initialized at the
minimum time of the first resource regardless of the Company or Entity times.
- Modification of the end date of the WO/grouped WO to the end date of the last resource: the time must be initialized at the
maximum time of the last resource regardless of the Company or Entity times.
- If the start date of the WO/grouped WO is strictly below the start date of the first resource, no change to the initial behaviour.
- If the end date of the WO/grouped WO is strictly above the end date of the last resource, no change to the initial behaviour.

The WO start and end times are initialised according to the following rules:
1. If a WO is created on the current day, the start time is the creation time and the end time is 00:00;
2. If no opening time is defined for the Company or Entity, then the opening hours are considered to be from Monday to Sunday
from 00:00 to 00:00 for each day;
3. If the opening hours are defined for the Company and not for the Entity, the Company opening hours apply;
4. If the opening hours are defined for the Entity, they take precedence over those of the Company;
5. If the opening hours are defined for the Entity but not for all the days of the week and a WO is created for one of these days
without times, we apply 00:00 to 00:00;

The start and end times can be changed independently from one another, according to the same rules as stipulated above.

n Asset off: Check box (by default = No)

n Currency: List of currencies used. Default user currency. If the work order originates from a PW, it retrieves the PW
currency. The currency can no longer be changed if the work order contains a resource line. All the costs are conver-
ted into the WO currency
n PW code: Displays the PW from which the WO originates.
n WR code: Displays the WR from which the WO originates.
n Deadline. DateTime type field "Day: Hour: Minute", editable. Sets the work completion time limit.

Initialisation of the Deadline

Initialisation take place as follows for a manual WO:

- default value = Start date (WO) + Time limit (WO priority) (=Deadline date/time(WR))
- blank if no WO priority level
- updated if the Start date (WO) and Time limit(WO priority) fields and Resources block are edited

Initialisation take place as follows for a WO from a WR:

- default value = Creation date (WR) + Time limit (WO priority)

- blank if no WO priority level
- updated if the Creation date (WO) and Time limit(WO priority) fields are edited

Initialisation take place as follows for a WO from a PW:

1. if the Completion time limit (PW) field is filled in

- default value = Start date (WO) + Completion time limit (PW)
- updated if the Start date (WO) and Completion time limit(PW) fields and Resources block are edited

2. if the Completion time limit (PW) field is not filled in and the Priority (PW) field is filled in
- default value = Start date (WO) + Time limit (WO priority)
- updated if the Start date (WO) and Time limit(WO priority) fields and Resources block are edited

3. if the Completion time limit (PW) field is not filled in and the Priority (PW) field is not filled in

- 159 -
 Work settings

- blank by default
- updated if the Start date (WO) field and Resources block are edited, or if the Time limit fields (WO priority), Completion time
limit (PW) are added

Initialisation take place as follows for a grouped WO:

1. in the form of a parent WO created independently

- default value = Start date (grouped WO) + Time limit (grouped WO priority)
- blank if no grouped WO priority level
- updated if the Start date (grouped WO) and Time limit(grouped WO priority) fields and Resources block are edited

2. in the form of a parent WO from a PW

2.1. if the Completion time limit (PW) field is filled in
- default value = Start date (grouped WO) + Completion time limit (PW)
- updated if the Start date (grouped WO) and Completion time limit(PW) fields and Resources block are edited

2.2. if the Completion time limit (PW) field is not filled in and the Priority (PW) field is filled in
- default value = Start date (grouped WO) + Time limit (grouped WO priority)
- updated if the Start date (grouped WO) and Time limit(grouped WO priority) fields and Resources block are edited

2.3. if the Completion time limit (PW) field is not filled in and the Priority (PW) field is not filled in
- blank by default
- updated if the Start date (grouped WO) field and Resources block are edited, or if the Time limit fields (grouped WO priority),
Completion time limit (PW) are added

3. in the form of a child WOWOWO form

- blank by default
- non-editable
- no update if Time limit edited (parent or child WO priority)

Comment block

Comments are displayed in discussion mode in order to have a trace of their history.
Comment are displayed in chronological order, from the most recent to the oldest.
Their number is displayed on the Comments block if it is folded.

Click on the button to open the comment input pop-in. Enter the comment then click on the button

to go back to the WO.

- 160 -
 Work settings

The comment is added to the list of comments, with the name and photo of the user who entered it. It is possible to zoom on
the photo.
Each comment can be unfolded and folded.

A comment entered by another user cannot be modified or deleted.

General information block

The user can select or enter additional information relating to the WO:

n Issuer: Selection list (required): filled in by default with the identifiers of the logged-in user.
n Creation date: Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM): by default is equal to the day's date.
n Duration: Hour: Minute type in (in HH: MM). The field is updated automatically according to the start and end dates
of the WO. Manual entry is possible in the duration field, and has an impact only on the end date of the WO.
n Technology: Selection list
n Cost allocation: Cost allocation tree pop-in. Retrieves the asset cost allocation.
n Contract: Selection list. Displayed if the contracts module is enabled. The list displays non-archived contracts, with
"Active " or "Being terminated" status. Contracts are filtered with the fields already entered in the WO: Asset, tech-
nology, type of work and entity (E.g. if the WO has a technology entered, then the list of contracts only displays
contracts with this technology).

l When selecting a contract, the WO technology and type of work are automatically set as those of the
contract. If one of them is modified, the contract is de-selected.
l When selecting a contract, the WO asset is automatically set as the contract asset (if the contract only
concerns one asset). If the asset is modified and it is not managed by the contract, the contract is de-
selected.

The work order start and end dates must be within one of the application periods of one of the amendments.
The work order is then visible in the WO block of the contract form.

Resources block
Several types of resources may be needed:

Workforce (WF)

Sub-contractor (SC)

Part

Downtime

This screen is used to plan or complete work for each type of resource.
Resources can also originate from the jobs linked with the WO or from the preventive works.

All the costs are displayed and converted into the WO currency.

When the WO is closed, all the resource lines are marked completed so that they are no longer seen in the schedules of the tech-
nicians.

Planning work

- 161 -
 Work settings

Click on the button then select the chosen type of resource.

l Workforce
l Subcontracting
l Part
l Downtime

When all the fields are filled, click the button to validate the entry or the button to ignore
the entry.

Entering a report/Performing work

For each planned work line, click on the button to enter a new work report.

Completing resources

Select the resource lines from the list of WOs and click the button to complete the resources in a
batch.

Once the resource lines have been selected from the list of WOs, we have the following save process:

l the message: "Input of actual figures taken into account" is displayed

l for each line, the 'Estimated' becomes 'Actual'

l each resource line changes to 'Completed'

The 'Completed' column enables us to filter the non-completed lines.

Management rules:

l If 'Estimated' lines have been input and validated but filled in incorrectly (no technician identified for the workforce or
subcontractor), a non-blocking message is displayed: "Resources: Some lines could not be completed because infor-
mation is missing."

l If the lines are already completed, the can still be modified ('Estimated' changed and additional input of 'Actual')

l If lines are already completed then re-selected, clicking 'Complete resources' does not recreate any 'Actual' for these
lines

l If 'Estimated' = 0 then 'Actual' = 0 (no check on the information entered in 'Estimated')

//!\\ No impact on the entry and/or editing of additional 'Actual' with the old buttons.
//!\\ Automatic changes to the input of 'Actual' on all resource lines (email, status change) observed.

Displays the history of the reports:

For each line, all report entries can be viewed by clicking on the work report history button
Click on each entry line to view its details or modify it.

- 162 -
 Work settings

After modification, click on the or buttons to return to the WO form.

A report may also be deleted. The deletion of an actual line is done when the WO is recorded.

The duration and the overall cost are updated with all the work completed. The "Completed" checkbox is checked if all the
entries are completed. (Modifiable)

When the WO is closed, all the resource lines are marked completed.

Resources - WO workforce

The technician category is a required field. A technician category can be assigned to a WO without selecting a technician.
The list of technicians is then filtered to the users belonging to the defined category.
When a technician is selected, his or her main category is entered automatically. It can nevertheless be changed by selecting in
the list another category linked with the technician's user profile.
The list of technicians displays only the users whose profile includes the technician role.

The start and end dates/times of the WO are updated according to the start and end dates/times of the planned or completed
resources entered, if:
- if the resource start date/time is before the WO start date/time;
- if the resource end date/time is after the WO end date/time;
However the WO start and end dates/times are not modified if the start and end dates/times of the resources entered are within
their limits.

Planning work

n Planned start date: "Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work start date (WO start date by default).
n Planned end date: Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work end date (WO end date by default). The field is updated according to the work duration entered.
n Duration: Hour: Minute type in (in HH: MM). Planned work duration (hours). Updates the planned work end date. Ini-
tialised at 00 by default: 00.
n Planned hourly cost: the hourly cost of the category assigned to the profile of the technician is retrieved. If no tech-
nician is selected, displays the hourly cost of the category. The hourly cost can be modified.
n Currency: WO currency, cannot be changed.
n Planned cost: calculation of the planned overall cost = hourly cost * work duration.

Technician timetable check

When adding or editing a technician line in a WO or grouped WO, the technician's timetable must be checked. It is also applied
to time ranges from the technician's team.
The technician's timetable hours are compared to the planned hours.
A warning message is displayed if the technician is not available for all or part of the work: "The technician is not available from
DD/MM/YYYY HH:MM to dd/mm/yyyy hh:mm".
If a time slot is "non-productive", it is considered outside the technician's working hours.

Completing work

A technician must be entered in order to access the completion of the work.

Entries must be made in the following fields:

- 163 -
 Work settings

n Start date: the current date by default. Modifiable

n End date: the current date by default. Modifiable. The field is updated according to the work start date and duration
entered.
n Duration: completed work duration (hours). Updates the actual work end date.
n Hourly cost: reproduces the planned hourly cost for the work.
n Currency: WO currency, cannot be changed.
n Workload: different from the Estimated duration.
n Completed checkbox: indicates completion of the work.

Resources – WO parts
Orders for parts allocated to a work order are added directly to the work order. Refer to the Link between orders and work
orders section on the order form.

n Assign to: blank if there is no WF or SC resource in the WO. Otherwise, displays the list of technicians and sub-
contractors of the WO resources and the planned start date and duration. Used to assign the parts to the various
internal or external technicians of the WO.
n Part: Selection drop-down list or pop-in. Displays the descriptions of the parts.
n Description: Description for a part not listed in stock.
n Warehouse: Field blank by default. Drop-down list of all the non-archived warehouses. When a part is selected, dis-
plays the main warehouse, if the part is managed in stock there; otherwise, displays the warehouse in which the part
is managed in stock. If the part is stocked in several warehouses (other than the main one) the field remains blank to
leave the choice to the user.

For the parts listed in stock, the required fields are: Date, Part, Quantity, Unit, Warehouse. The unit price cannot be modified.
For the parts not listed, the required fields are: Date, Description, Quantity, Unit cost. The unit price must be entered.

Planning work

n Planned end date: Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Indicates the planned work start
date (WO start date by default).
n Planned quantity: indicates the planned quantity of parts for the work.
n Planned unit: storage unit of the selected warehouse. The list displays only the units convertible with the storage unit
of the part.
n Planned unit price: For parts managed in stock in the warehouse, the price is recovered based on the stock (Part/Wa-
rehouse) and the valuation type, it is non-modifiable. For parts not managed in stock, the price is to be entered as
free-text entry.
n Planned cost: calculation of the planned overall cost = unit cost * quantity.
n Currency: WO currency, cannot be changed.
n Reserved checkbox: checked to reserve the part in stock. Updates the available quantity of the part in the warehouse.

The quantities reserved or available in stock are updated when the WO is saved, for the reserved or de-reserved parts.

Completing work

n Date/time: initialised as "Now" (day's date/time). Modifiable.

n Completed quantity: quantity of the part used for the work.
n Completed unit price: retrieves the planned unit price of the part for the work. For parts managed in stock in the
warehouse, the price is recovered based on the stock (Part/Warehouse) and the valuation type, it is non-modifiable.
For parts not managed in stock, the price is to be entered as free-text entry.
n Completed cost: calculation quantity * unit price.
n Currency: WO currency, cannot be changed.
n Completed checkbox: indicates completion of the work.

- 164 -
 Work settings

The stock movements and the updating of the available, actual and reserved quantities are carried out when the WO is saved.
When a part is withdrawn, the withdrawal movement is made in the work order currency. The same applies for entry move-
ments made after the cancellation of a part withdrawal on a work order.
Entries/withdrawals of unreferenced parts are also tracked through a movement that is searchable in the list of movements.

Movement is forbidden when the date is before the part status changes from “Managed in stock” to “Not managed in stock”,
and when its date is after the days’ date.

Resources - WO subcontractors
Subcontracting orders allocated to a work order are added directly to the work order. Refer to the Link between orders and work
orders section on the order form.
Category: Required. Displays the partner categories.
Subcontractor: Drop-down list. Displays all the partners that are subcontractors.

The subcontractor category is a required field.

A subcontractor category can be assigned to the WO without selecting a subcontractor.
The list of subcontractors is then filtered to display those belonging to the assigned category.
When a subcontractor is selected, its main category is entered automatically. It can nevertheless be changed by selecting ano-
ther of its categories in the list.

Planning work

n Planned start date: "Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work start date (WO start date by default).
n Planned end date: Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work end date (WO end date by default). The field is updated according to the work duration entered.
n Duration: Hour: Minute type in (in HH: MM). Required. Planned work duration (hours). Updates the planned work
end date. Initialised at 00 by default: 00.
n Planned subcontracting cost: retrieves the hourly cost of the category assigned to the subcontractor * Duration of the
work. The hourly cost can be modified.
n Planned part cost: the cost of the parts needed for the work.
n Planned cost: calculation of the planned overall cost = subcontracting cost + part cost.
n Currencies: WO currency (cannot be changed)

Completing work

n Start date: the current date by default. Modifiable

n End date: the current date by default. Modifiable. The field is updated according to the work start date and duration
entered.
n Completed duration: completed work duration (hours). Updates the actual work end date.
n Completed subcontracting cost: hourly cost for the work * duration.
n Completed part cost: to be entered.
n Completed cost: calculates the overall cost = subcontracting cost + part cost.
n Currencies: WO currency (cannot be changed)
n Completed checkbox: indicates completion of the work.

The completed duration, completed subcontracting cost, completed part cost and completed overall cost are updated with all
the work completed. The "Completed" checkbox is checked if all the entries are completed. (Modifiable)

Resources – Downtimes

- 165 -
 Work settings

n Assign to: blank if there is no WF or SC resource in the WO. Otherwise, displays the list of technicians and sub-
contractors of the WO resources and the planned start date and duration. Used to assign the downtime to the
various internal or external technicians of the WO.

Planning work

n Planned start date: "Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work start date (WO start date by default).
n Planned end date: Day: Hour: Minute type (in the format DD/MM/YYYY HH: MM). Required. Indicates the planned
work end date (WO end date by default). The field is updated according to the work duration entered.
n Duration: Hour: Minute type in (in HH: MM). Required. Planned work duration (hours). Updates the planned work
end date. Initialised at 00 by default: 00.
n Planned hourly cost: retrieves the downtime cost of the WO asset (modifiable).
n Planned cost: calculation of the planned overall cost = hourly cost * duration.
n Currencies: WO currency (cannot be changed)

Completing work

n Start date: the current date by default. Modifiable

n End date: the current date by default. Modifiable. The field is updated according to the work start date and duration
entered.
n Completed duration: completed downtime (hours). Updates the actual work end date.
n Hourly cost: reproduces the hourly cost for the planned work. Modifiable.
n Completed cost: calculates the overall cost = hourly cost * duration.
n Currencies: WO currency (cannot be changed)
n Completed checkbox: indicates completion of the work.

Diagnosis block

This block is displayed if the diagnosis module is enabled in the company form.

A user can define the partial or total failure diagnosis relating to a work order. The diagnosis gives details of the failure symp-
toms and the actions necessary to repair the failure.

A complete diagnosis consists of:

n an effect
n a cause
n a remedy.

The icons give access to the various forms or to the corresponding repositories.

Jobs block

Used to link maintenance jobs with the work order.

- 166 -
 Work settings

Click on the button and select a job in the selection dropdown list

Click the button to validate the input.

If the tasks of the job have assigned resources, a message prompts the user to add the task resources to the WO. The work start
date must then be entered.
Click on a job in the list to display the associated tasks.
When completing the work, there are three response options:

n the task is completed: OK

n the task is not completed: KO
n the task cannot be completed: Not feasible

Type column:

Displays an icon representing the choices "Standard" , "Meter reading" and "Measurement reading" depending
on the task.

ColumnMeter/Measurement:

Enables you to select a meter or a measurement from those attached to the WO asset according to the reading type.
Displays the only meter or measurement according to the default reading type if only one meter or measurement is attached to
the WO asset; otherwise, if the Task type is "Standard", the Meter/Measurement column is blank (no selection field).

If you change asset, the Meter/Measurement field is cleared (you keep the same behaviour as the display of Meters and Mea-
surements blocks).
For Technician type accounts: it is impossible to change the choice of a meter or measurement that has already been entered
(reading type task)

Completed column:

This column has been renamed Response in R19 (S113).

For a "Meter reading" or "Measurement reading" type task:

- the original selection field becomes an input field that is blank by default, followed by the unit written in full
- the column also has a Date/Time type input field that is blank by default,
- the column also has a "Cannot be completed" check box, which is unchecked by default, next to the Date/Time field,
- if the input field is filled in, the input date/time is initialised with the current date/time and can be changed,
- if the Meter/Measurement column is blank, the input and date/time fields are blank and cannot be changed,
- if the Meter/Measurement column is filled in, the input and date/time fields can be changed,

- 167 -
 Work settings

- the response (input of the reading + start date + "Cannot be completed" box) is saved in the database when the WO is saved
(after the checks have been approved)

Cannot respond to tasks if the WO is in 'Done' status.

Automatic response to tasks without response

If a WO changes to 'Done' or 'Closed' status manually, we have an automatic response to tasks without response. They take the
value 'Cannot be completed'.

Rules for task reading dates/times

Cannot take a measurement reading for a task on the WO Measurements block at the same date/time.
Blocking message: "Measurement: 'Measurement description': A measurement reading at this date and time already exists".
Cannot take a reading of the same measurement/asset on 2 different tasks at the same date/time.
Blocking message: "Measurement: 'Measurement description': A measurement reading at this date and time already exists".

Cannot take a meter or measurement reading for a task on the WO Meters block at the same date/time.
Blocking message: "Meters: 'Meter name': A meter reading at this date and time already exists",
Measurement: 'Measurement description': A measurement reading at this date and time already exists".
Cannot take a reading of the same meter or a reading of the same measurement/asset on 2 different tasks at the same date/-
time.
Blocking message: "Meters: 'Meter name': A meter reading at this date and time already exists",
"Measurement: 'Measurement description': A measurement reading at this date and time already exists".

To respond to the tasks associated with several jobs simultaneously:

- Check the jobs

- Click on the button

- Select the response to assign to all the tasks of the checked jobs
- Enter a comment if needed

- Click on the button

The selected response is applied to all the tasks in the selected jobs and the comment is entered against all the tasks.

The comment for each task can be seen by clicking on the button . It cannot be changed.

Cannot take a reading of the same meter on 2 different tasks at the same date/time, Blocking message: "Meters: Meter name: A
meter reading at this date and time already exists".

- Cannot take a meter reading for a task on the WO Meter block at the same date/time, Blocking message: "Meters: Meter
name: A meter reading at this date and time already exists".
- Cannot take a reading of the same meter on 2 different tasks at the same date/time, Blocking message: "Meters: Meter name:
A meter reading at this date and time already exists".

- Cannot take a measurement reading for a task on the WO Meter block at the same date/time, Blocking message: "Mea-
surement: Measurement description: A measurement reading at this date and time already exists".
- Cannot take a reading of the same meter on 2 different tasks at the same date/time, Blocking message: "Measurement: Mea-
surement description: A measurement reading at this date and time already exists".

- 168 -
 Work settings

Following the deletion of a job with associated reading tasks (meter or measurement):

The input made for a reading:

- is always saved in the database
- remains displayed in the Meters or Measurements block of the WO and Asset forms concerned
- remains displayed in the history of the asset concerned

Tree structures block

The tree structures block screen displays the histories of the various trees of the WO at the time of the order:

n asset tree
n asset families tree
n cost allocation tree

Costs block

Gives the planned and completed costs for the resources:

n Workforce
n Subcontractor
n Parts
n Downtimes

Associated files block

Files necessary for completing work can be linked with the WO.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Asset Files block

Displays the files associated with the asset; files cannot be added or deleted here.

WR files block

Displays the list of files associated with the WR; files cannot be added or deleted here.

PW files block

Displays the list of files associated with the PW; files cannot be added or deleted here.

Legal information block

It is possible to add legal information to work orders.

Those which are not archived are duplicated when their WO is duplicated.

Meters block – Entering a meter reading

- 169 -
 Work settings

The list displays the meters associated with the asset or with its child assets.

The meter readings are entered:

n In the WO form, Meters block.

n From the Home screen, My schedule widget, button on the WO line. The report entry form is dis-
played. The reading is entered in the Meters block.

The following information is displayed in read-only, non-modifiable form: asset, ("Code - Description format) meter description,
date of old value (displays the most recent reading date), old value.
The icon displays the meter reading input history (Reading date, Value, User, WO, Meter reset).

Entry fields:

n Date of new value: date field (required)

n New value: numerical integer field (required)

Enter the reading date and the reading value.

Meter readings with the following characteristics cannot be entered:
- above threshold
- above the maximum daily value allowed (blocking message: "New meter value XXXX incorrect. The daily average calculated
({Value calculated}) is above the max daily value allowed ({Meter max daily value}) on the meter." )
- reading lower than the previous reading
- at a date later than the day’s date

Meter readings entered on a date preceding the date of the most recent reading are allowed.

For a meter with a threshold, and if:

- New value date < date (last reading) AND New value > value (last reading)
- New value date > date (last reading) AND New value < value (last reading)

a warning message is displayed when saving: "N.B. This reading will cause a meter rotation. Are you sure you want to continue?"

The asset form is updated with the new readings:

n Update date
n Value
n Total

Signature block

Electronic signature of work orders available

- 170 -
 Work settings

Signatures are retrieved from the DMA mobile application. The following information is displayed:

n Signature date/time
n Signatory
n Link to the attached image file of the user's signature

When printing, a Date field appears, enabling you to enter the date manually.

Measurements block

Accessible to a User account type.

Displays the list of measurements [and their number count] linked to the WO asset:
This block is used to:

n View the measurements in the following columns:

n Asset: Code/Description (asset) (read-only)
n Description: Code/Description (measurement) (read-only)
n Old value date: Date/Time (read-only)
n Old value: concatenation (Value+Unit) (decimal; read-only)
n New value date: Date/Time (modifiable) Its entry makes the New value field mandatory.
n New value: (decimal; modifiable)
n Click "Delete" (button in the block header, or command at the end of the measurement line) to delete the link bet-
ween the Asset and Measurement forms and the [measurement] reading history.
n Click ‘Add’ to add a measurement with the following field suggestions:
n Measurement: Typeahead on Code - Description of a measurement (required). Only measurements with at
least one entity in common with the asset are suggested.
n Unit: Text field (read-only). Retrieves the unit of the measurement selected.
n Value: Digital field (editable). Enables you to initialise a 1st measurement value.
n Date/time: Date/Time field (editable). Enables you to initialise the date/time of the 1st measurement.
Filling in this field makes it mandatory (and vice versa)

Check on reading entry

The New value date must be strictly later than the Old value date.
If this is not observed, when the entry is added, a blocking message is displayed: "Measurement: Description (Measurement).
The date/time of the new value must be later than the date/time of the old value".

The New value date must be strictly before the day’s date/time.
If this is not observed, when the entry is added, a blocking message is displayed: "Measurement: Description (Measurement).
Date entered later than the day’s date"

If Min value and Max value entered in the measurement, then Max value >= value entered >=Min value
If value entered > Max value, blocking message "Measurement: Description (Measurement). Value entered above Max value"
If value entered < Min value, blocking message "Measurement: Description (Measurement). Value entered below Min value"

No check on the value in relation to the previous values.

Duplication of WO/grouped WO

When a WO/grouped WO is duplicated whose asset(s) is/are linked to one/several measurements, the WO/grouped WO created
also has these measurements.

Conditional WO case

- 171 -
 Work settings

When a conditional WO has been triggered after a measurement reading corresponding to a work model in the value range
concerned and this WO is in "To do" or "In progress" (or equivalent) status, any new measurement reading referring to the same
work model should not trigger a new WO.
This trigger avoids a redundant (therefore unnecessary) WO creation, which could happen if the first WO (or conditional WO)
was not yet processed.

WO content from a measurement reading according to a work model

It follows these rules:

l initialisation with the information entered in the original model for the blocks: General information (if the Issuer field is
not entered in the original model, in the WO it takes the value of the user who entered the measurement), Jobs, Asso-
ciated files and Legal information
l initialisation with the information entered in the original model and the WO Start date for blocks: Comment, Resources
l initialisation with the measurements relating to the asset and their last reading and update date, for the Mea-
surements block
l initialisation with the information contained in the original model header, for the Header block, shown in the following
format:
o Code: initialised according to the internal incremental meter (if no automatic codification of WOs)
o Title: uses model title, followed by the words "from a measurement reading" (in the issuer's language)
o Creation date: date of WO generation by the robot
o Start date: date of measurement causing the trigger
o End date: initialised according to the same rules as when a WO is created (Company/Entity times + priority)
o Deadline: initialised according to the same rules as when a WO is created (Company/Entity times + priority)
o Model code: uses the code of the model at the origin of the WO (same principle as PW code or WR code),

depending on the WO form screen setup

Grouped work orders block

List of grouped work orders

This list is available from the [Work-Grouped work orders] menu if the grouped work module is enabled.
The list displays all the non-archived WOs, sorted in ascending order of the WO codes. . It is also possible to sort by alert status

and deadline (by alert icon ).

Refer to the section Grouped work.

The available actions depend on the user rights and WO status. [Settings-Users-User profiles] and [Settings-Work-WO status
administration]

Advanced filters

Application is the same as for the list of single WOs except in the following cases:

n Asset family -> Grouped WOs with a child WO with an asset in this family
n Assets -> Grouped WOs with a child WO with an asset matching the filter
n Criticality -> Grouped WOs with a child WO with an asset with this criticality
n Effect -> Grouped WOs with a child WO with this effect
n Cause -> Grouped WOs with a child WO with this cause
n Remedy -> Grouped WOs with a child WO with this remedy

This block, which is closed by default, shows the following fields:

- 172 -
 Work settings

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Status: Drop-down list, with the choices: - “To do”, “In progress”, “Done”, “Cancelled” and “Closed” + equivalent sta-
tuses.
n Asset family: Typeahead and standard search window of asset families, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Asset: Typeahead and standard search window on assets filtered to the authorised assets and their parents (even if
not authorised) of the logged-in user's entities. Associated with: “With children” check box.
n Criticality: Selection list.
n Type of work: Selection list.
n Priority: Selection list.
n Issuer: Selection list.
n Start date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n End date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Creation date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Technology: Selection list.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Subcontractor category: Selection list.
n Technician: Selection list.
n Subcontractor category: Selection list.
n Subcontractor: Selection list.
n Part: Typeahead and standard part search window, filtered to the logged-in user’s entity/ies.
n Effect: Selection list.
n Cause: Selection list.
n Remedy: Selection list.
n Job: Selection list.
n Preventive work: Text field. Automatic filter upon entry. Only returns PWs with at least one authorised asset.
n Work request: Text field. Automatic filter upon entry. Only returns the list of requests with an authorised asset and
the requests with no assets of the logged-in user's entities.
n Deadline (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon. Sets the
work completion time limit.

Creating a grouped WO

A grouped WO can be created:

n with the button on the list of grouped WOs.

n by clicking on the button on the WO form.

n By converting a grouped PW to a grouped WO.

For further explanation on creating a WO, refer to the grouped WO form.

Deleting a grouped WO

To delete a team:

- 173 -
 Work settings

n click on the button on the form or list of grouped WOs.

n from the list of grouped WOs, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A grouped WO cannot be deleted:

- if it is cited in another document

- if it has completion information in the resources
- if any of its tasks are checked as completed
- if its status is Completed or Closed
- if it has included a meter reading.

And in the case of any of its children

- if it is cited in another document

- if it has completion information in the resources
- if any of its tasks are checked as completed
- if its status is Completed or Closed (or equivalent)
- if it has included a meter reading.

Deleting a grouped WO also deletes all its child WOs.

The stock is updated with the quantities of parts reserved and not consumed.

Duplicating a grouped WO

To duplicate a team:

n by clicking on the button on the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

Duplication opens a new grouped WO in a new tab.

All the grouped WO data is duplicated except for the:
Header
Code -> Blank
Status -> Grouped WO creation status
Start date -> Current date
End date -> Current date

Work orders
On the new grouped WO, for each child WO line of the old grouped WO, a new child WO is created.
It follows the standard single WO duplication rules.

Comment
Comments are not duplicated.

General information
Creation date -> current date/time

Resources

- 174 -
 Work settings

Scheduled resources date -> Current date

No resources data entered is duplicated

Note: :

In a tree partition, the button or the equivalent menu are only visible, for the User account, if all its
child WOs are attached to their authorised assets (or if it does not have any child WOs).

Jobs associated with assets are duplicated and displayed on the Jobs column before the new grouped WO is saved.
The task description is displayed for the associated resource.
Job task types are sent to the child WOs (with icon).
Meters/Measurements are sent to the child WO (displayed if only one meter/measurement for the asset, otherwise choice from
among the asset meters/measurements) and can be changed.

Archiving/De-archiving a grouped WO

A grouped WO can be archived:

n by clicking on the button on the list of grouped WOs or the WO form.

n from the list of grouped WOs, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the code and the WO title, indicating that the WO is archived.
Archived WOs are no longer visible in the drop-down lists or the search fields.

Archiving a grouped WO also archives all its child WOs.

Only cancelled or closed WOs can be archived.

A grouped WO can be de-archived:

n by clicking on the button on the list of WOs, or the WO form.

n from the list of WOs, by clicking on the arrow at the end of the line.

De-archiving a grouped WO also de-archives all its child WOs.

The WO is no longer archived and is displayed again in the selection lists and search fields.

Closing a grouped WO

A grouped WO can be closed:

n by clicking on the button on the list of grouped WOs or the WO form.

n from the list of grouped WOs, by clicking on the button at the end of the line.

- 175 -
 Work settings

To close a work order automatically, without having to change the status manually, you must enable the ‘Close WO’ action in
WO status administration and configure an arrival status. Otherwise the WO cannot be closed.

n by manually changing the WO status to Closed (or equivalent).

Changing the status of a grouped WO to closed (or equivalent) also changes the status of all the child WOs to closed except for
those that have already been closed or cancelled.

A grouped WO can only be switched to closed status in a tree partition, for User and Guest accounts, if all the child WOs are atta-
ched to authorised assets (or if it does not have any child WOs).

Under all circumstances, the user must have the 'Close WO' role in the settings of his or her profile – Roles block.

All the conventional single WO closure operations are carried out except parts list updating, because grouped WOs do not have
assets.

Reopening a grouped WO

The procedure is exactly the same as for reopening a single WO.

If the resource dates of the grouped WO and its child WOs are not included between its Start date and End date, you can still
reopen it.

Reopening a grouped WO causes the child WOs to reopen (without checking the dates of the child WOs and their resources).

A grouped WO can only be reopened in a tree partition, for User and Guest accounts, if all the child WOs are attached to autho-
rised assets (or if it does not have any child WOs).

Cancelling a grouped WO

A grouped WO can be cancelled:

n by clicking on the button in the list of grouped WOs.

n from the list of grouped WOs, by clicking on the arrow at the end of the line.
n by changing the WO status to Cancelled or equivalent.

Changing the status of a grouped WO to cancelled (or equivalent) also changes the status of all the child WOs to cancelled (when
the grouped WO is recorded). A grouped WO cannot be cancelled if any of its children have been closed.

A grouped WO can only be switched cancelled status in a tree partition, for User and Guest accounts, if all the child WOs are atta-
ched to authorised assets (or if it does not have any child WOs).

The procedure is exactly the same as for cancelling a single WO.

Printing a grouped WO
A grouped WO can be printed by clicking on the button on the list or WO form.
Printouts follow the screen configuration defined for the grouped WO form (fields and blocks hidden or displayed)

Certain additional options can be configured:

- 176 -
 Work settings

n Display company logo

n Display Address Blocks
n Display manager's signature block
n Add jobs as PDF attachments
n Display barcode
n Print child WOs

These options are defined by user profile under screen settings in the PDF printer settings by selecting the grouped WO form
[Profile form - Screen settings - PDF printer settings].

Grouped work order form

This is available from the [Work-Grouped work orders] menu if the grouped work module is enabled.
Grouped WOs are used to carry out work on several assets.
Refer to the section Grouped work.

Click the button to access the form being created or on the button to view a grouped WO.

The available actions depend on the user rights and WO status. [Settings-Users-User profiles] and [Settings-Configuration-WO
status administration].

The New, Delete, Archive, Duplicate, Close, Cancel, Reopen and Print buttons are explained in the actions of the Grouped work
orders list.

The icons give access to the various forms or to the corresponding repositories. (Asset form, type of work, small priority
tables etc.) so that information can be viewed or modified during entry.

Some actions performed on the WO may trigger an email notification: WO creation, adding a technician line, WO closure, etc.
For more information about activation and configuration, refer to the Email administration and Managing how emails are sent
with grouped WOs sections.

Late grouped WOs can trigger alerts (visual alerts or email notifications). Child WOs are not involved in WO alerts. Refer to the
section Alerts-Notifications.

How the blocks and fields are displayed and the mandatory fields for saving can be configured by user profile. Refer to the sec-
tion Screen settings.

- 177 -
 Work settings

Assets can be added to the grouped WO in the Work orders block.

Header block

Exactly the same as the Header block of a single WO. Only the Asset and Asset off fields are deleted.
In terms of the Code field, automatic coding is the same as for single WOs.

Grouped WO currency:

Required field, the user currency is used by default. Can be modified if there is no resource line in the grouped WO or any of its
child WOs.

n When a PW occurrence is converted into a grouped WO, the PW currency is retrieved on the grouped WO.
n When a resource line is added, the currency fields retrieve the currency of the grouped WO and the prices are converted. The
currency cannot be edited.
n The costs originating from tasks are also converted into the currency of the grouped WO
n When a part is withdrawn or a withdrawal is cancelled in the WO, the entry or withdrawal movement is made in the grouped
order currency.
n When child WOs are generated, they automatically retrieve the currency from the grouped WO. The currency cannot be edi-
ted in the child WO.
n Changing a grouped WO currency automatically changes all its child WO currencies

Changing statuses and impacts on the child WOs:

n Changing the status of a grouped WO to closed (or equivalent) also changes the status of all the child WOs to closed except for
those that have already been closed or cancelled.

n Changing the status of a grouped WO to cancelled (or equivalent) also changes the status of all the child WOs to cancelled
(when the grouped WO is recorded). A grouped WO cannot be cancelled if any of its children have been closed.

For more information, see the WO statuses and WO status administration sections

Status changes and tree partitioning:

For User and Guest accounts, you can only switch a grouped WO to closed/reopened or cancelled status if all its child WOs are
attached to authorised assets (or if it has no child WOs).

- 178 -
 Work settings

Application of automatic changes of status on grouped WOs

Automatic status changes can be configured in WO status administration.
For each action, if enabled, this is how these changes are applied to the grouped WOs and child WOs:

n When a grouped WO form is opened under creation, the grouped WO status is entered as the Create WO action
n If a preliminary time or task response has been entered against the grouped WO or any of its child WOs, the status of the grou-
ped WO changes to that of the action, Preliminary time or task response to all the order tasks, when the grouped WO is saved.
n If a preliminary time or task response has been entered on any of its child WOs or the grouped WO, the status of the grouped
WO changes to that of the action, Preliminary time or task response to all the order tasks, when a child WO is saved.
n If all the grouped WO resources are completed and all the resources of its child WOs are completed and all the tasks of its
child WOs have a response, the status of the grouped WO is changed to that of the Term of all the resource lines and response
to all the order tasks when the grouped WO is saved.
n If all the grouped WO resources are completed and all the resources of its child WOs are completed and all the tasks of its
child WOs have a response, the status of the grouped WO is changed to that of the Term of all the resource lines and response
to all the order tasks when a child WO is saved.
n When the Reopen grouped WO button is clicked, the status of the grouped WO and all its child WOs changes to action status
WO reopened.
n When the Reopen child WO button is clicked, the status of the child WO and the grouped WO changes to action status WO reo-
pened. The statuses of the other child WOs are unaffected.

How grouped WO and child WO dates are handled

The (start and end) dates of a grouped order must include the dates of all the resources (conventional behaviour) and the dates
of all its child dates.

If any of the grouped order dates become incompatible when the date of a child WO is changed, they are updated:
-> if the child order has a start date before that of the grouped WO -> the start date of the grouped WO is moved forward accor-
ding
-> if the child order has an end date after that of the grouped WO -> the end date of the grouped WO is moved back accordingly

If any of the new dates are incompatible with those of any of a grouped WO’s children when its dates are changed:
- If the child WO does not have a resource line -> the child WO dates are deferred
- If the child WO has scheduled resources or resources completed on dates that are all compatible with the dates of the grouped
WO -> the child WO dates are deferred
- If the child WO has at least one line of scheduled or completed resources that are incompatible with the dates of the grouped
WO -> an error message is displayed and the grouped WO date remains unchanged.

When a Grouped WO is closed:

- if the children WO status is "To do" (or equivalent) or "In progress" (or equivalent) ->the End date of the Grouped WO is sent to
them
- if the status of children WOs is "Cancelled" (or equivalent) or "Done" (or equivalent) or "Closed"(or equivalent) ->their End date
is not modified by the Grouped WO's end date

- 179 -
 Work settings

Work orders block

This block is used to:

n add grouped WO assets, following an automatically incremented and modifiable order. When the grouped WO is saved, child
work orders are generated for each asset added.
n view the child WOs related to the grouped WO.
n modify the order of child WOs and delete child WOs consistently (logical sequence; no duplicates). Recalculating the order,
when the grouped WO form is saved, enables you to send a coherent child WO processing order.
n to consult the associated jobs (the button opens on a pop-in of the associated jobs), in the same way as for the Jobs block of
the WO form.

- 180 -
 Work settings

Add assets/child WOs to the grouped WO

Click on the button to add an asset.

The following selection criteria are displayed:

n Asset + "With children"

n Asset families + "With children"
n Asset group
n Brand
n Model
n Serial number
n Work order (already exists)

Select the filters, then click on the button.

Assets corresponding to the selection (that do not yet have child WOs present in the list of grouped WO orders) are added to the
list.

If an asset group has been selected, the assets are added with the distribution defined in the group.
Otherwise, they are added with a distribution of 1.

You can select a WO that already exists to add it to the list of child WOs of a grouped WO
(searching in the Code and/or the Title, selecting in the Work order typeahead).

This possibility exists if the following conditions are met:

- the WO status is "To do" (or equivalent);
- the WO (from a non-grouped WR or PW) is not already part of a grouped WO;

You can add the same asset several times to a grouped WO (therefore have several child work orders with the same asset).

The start and end dates of the WO added may modify the start and end dates of the grouped WO according to the same rules as
for adding resources or modifying the start and end dates of a Child WO.

In multi-organisation mode, the assets must belong to the grouped WO entity.

The tree partition applies to grouped WOs with the possibility of adding the only assets authorised for the logged-in user.

- 181 -
 Work settings

Saving the grouped WO and Generating child WOs

When the grouped WO is saved, WOs are generated automatically for each new asset line added.
Each child WO takes its data from the grouped WO:

n Title
n Entity
n Type of work
n Start date: "Day: Hour: Minute" format.
n End date: "Day: Hour: Minute" format.
n Duration
n Technology
n Currency (cannot be changed)

The following data are entered as follows:

n Code -> Automatic coding or Alternative coding

n Status -> Destination status for the order creation action, as configured in WO status administration, otherwise, To do status
or equivalent
n Asset -> Line asset
n Asset off -> No
n Issuer -> logged-in user
n Creation date -> Current date/time
n Priority -> Grouped WO priority if entered, otherwise, priority related to the criticality of the line asset
n Cost allocation -> Grouped WO cost allocation if entered, otherwise, cost allocation related to the line asset

The jobs associated with the line asset are saved on the child order.
The job resources are not added to the child order but to the grouped WO.

Viewing child WOs

The list displays the data relating to the child WOs (Start date, Code, Title, Status, Asset and Distribution).
Click on any of the child WO lines to view details on it which include additional data.
Only the distribution can be changed.
All the child WOs can be viewed, even those attached to an unauthorised asset.

Click the button to access the child WOs attached to an authorised asset.

Click the check box at the start of the line to select the child WOs attached to an authorised asset
(if you check the general selection box, only the child WOs attached to an authorised asset are selected).

Collective distribution key update; Equal asset distribution button

The button is used to collectively update the asset distribution keys.

Select the asset and child WO lines whose distribution needs modifying, then click on the distribution button. Enter the dis-
tribution and confirm the entry.
The distribution key entered is assigned to all the selected asset lines.

If no order/asset line is selected, the asset keys remain unmodified.

If all the order/asset lines are selected, the distribution of all the order/asset lines changes to 1

- 182 -
 Work settings

Collective assignment of jobs to assets-Assign a job button

The button is used to collectively assign jobs to selected orders and assets

Select the asset and WO lines to assign the job to.

Enter the job.

The resources related to the job in question can be assigned to the grouped WO. If so, the resource date must be entered. (Time
zone of the issuer of the grouped order)

When you click on the Assign button, the job is assigned to all the selected assets and orders in the list.
If add resources is selected, the resources are added to the grouped WO on the specified date and the time and quantity are mul-
tiplied by the number of assets or orders selected.

The jobs are assigned to the child orders

The resources linked to the jobs are assigned to the grouped order.
Deleting a job on a child work order does not delete the resources linked to the job in the grouped WO.

Modifying an order status

To modify the status of several orders at the same time:
- Check the child orders

- Click on the button

- Select the new status to be assigned to all the checked WOs

- Click on the button

The selected status is assigned to all the checked WOs.

Asset lines not converted into child orders are not processed.

- 183 -
 Work settings

Responding to order tasks

To respond to the job tasks of several orders simultaneously:
- Check the child orders

- Click on the button

- Select the response to assign to all the tasks of the jobs on the orders that have been checked
- Enter a comment if needed

- Click on the button

The selected response is applied to all the tasks in the jobs in the selected WOs and the comment is entered against all the tasks.

Automatic response to tasks without response

If a grouped WO changes to 'Closed' status manually or if one of its child WOs changes to 'Done' or 'Closed' status, we have an
automatic response to tasks without response from the child WOs. They take the value 'Cannot be completed'.

Comment block
Exactly the same as the Comment block of a single WO.

General information block

Exactly the same as the General information block of a single WO.

Resources block
Resources are entered in exactly the same way in a grouped WO as they are in a single WO. See resources block of a single WO.
Each resource line indicates the task it originates from.

Costs block
It shows the sums of the costs of the grouped WO and its child WOs.

n Workforce
n Subcontractor
n Parts
n Downtimes

Associated files block

Files necessary for completing work can be linked with the WO.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

- 184 -
 Work settings

Meters Block
It shows the list of meters related to the child WO assets.
View of meters of authorised and unauthorised assets.
Only the meters of authorised assets can be modified.
Exactly the same as the meter block of a single WO.

The icon displays the meter reading entry history (reading date and value). It is the child WO that is displayed in the history.

The Meters block is printed if it contains data, if the "Visible" screen configuration is enabled and as soon as its grouped WO is
printed.

Signature block
Electronic signature of work orders available
The signatures are retrieved from the DMA mobile application.
See signature block of a single WO.

Measurements block
It displays the list of measurements (and their number count) associated with the child WO assets.
View of measurements of authorised and unauthorised assets.
Measurements
Only the measurements of authorised assets can be modified.
See measurement block of a single WO.
List of measurements
The list is accessible through the menu [Work-Measurements].
The list displays all the non-archived measurements, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a measurement

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating measurements, refer to the Measurements form.

Deleting a measurement

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

(It is impossible to delete an item that is cited in a document (WO, etc.))

- 185 -
 Work settings

Archiving/De-archiving a measurement

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a measurement

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the selected measurement to a new measurement. All the information is duplicated (except the Code field of
the Header block and the Work orders block).

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Type: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Asset family: Typeahead and standard asset family search window, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Shared data: Yes/No/All
n Entity: Selection list.

List of measurements

- 186 -
 Work settings

This block, which is always unfolded, has the following columns:

n Code: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Type: Text field. Automatic filter upon entry.
n Unit: Text field. Automatic filter upon entry.
n Asset: Text field. Automatic filter upon entry. Code/description of the asset if unique; "Several assets" if multiple.

Measurement form
Accessible through the Work menu [Work-Measurements] menu if the Measurements module is enabled.
The measurement settings are configured in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)
l Types of measurement managed
l Configuration of notifications-alerts
l Rights (Assets)

Click the button to access the form being created or the button to view a measurement.

The available actions depend on the user rights. [Settings-Users-User profiles].

The icons give access to the various forms or to the corresponding repositories. (Types of measurement, Unit) making it pos-
sible to view or modify information during entry.

The "New", "Delete", "Archive" and "Duplicate" buttons are explained in the actions of the List of measurements.

Header block

This block defines the main information of the contract.

- 187 -
 Work settings

n Code: Text. Required and unique

n Description: Text. Required and translatable.
n Measurement type: Drop-down list of measurement types according to entity
n Unit: Drop-down list. Required.
n Decimals: Integer between 0 and 5. Default value 2. If entry incorrect, field red and tooltip "The number of decimals
must be between 0 and 5".
n Entities: Drop-down list enabling one choice of a logged-in user's entity. By default, logged-in user's main entity.

Asset block

Used to link one or more assets to the measurement taken.

The list columns are as follows:

n Code
n Description
n Asset family

To add assets from the same family, click on the button, select asset family, then click on the but-
ton. All the assets linked to this family are added to the measurement.
When the Add button is clicked, the assets corresponding to the selection that are not yet present in the measurement asset list
are added to this list.

You cannot enter an asset that has already been entered on another line.
Display rules with the same principle as the asset groups.
You only see assets, asset families, asset groups, brands and models attached to the entity of the measurement in common.

Value range block

This block is used to define the maintenance conditions according to the values of a measurement.

- 188 -
 Work settings

Reading range section

- Min value: Decimal
- Max value: Decimal

The Min value can be entered without the Max value

The Max value can be entered without the Min value
If Min and Max entered, check that Max > Min.
If Min > Max then the 2 fields are in red + Tooltip: "The Max value must be strictly above the Min value"
/!\ Negative values are authorized.

Conditional Maintenance section

- Alarm max: Decimal
- Alert max: Decimal
- Target: Decimal
- Alert min: Decimal
- Alarm min: Decimal
- Max alarm/max alert/min alert/min alarm WO model: Search typeahead for work models only returning unarchived models.
The measurement and WO entities must be identical, as any change to the entity clears the model fields.

Check on the entry of different values

If Min value and/or Max value are entered, check for each value that it is between Min value and Max value (strictly above Min
value and strictly below Max value).
Incorrect values entered are in red, and the following tooltip is displayed: "The value entered must be strictly above the Min
value and strictly below the Max value";

The check on entering alarm and alert values between them is performed according to the following general rule:
Max alarm value > Max alert value > Target value > Min alert value > Min alarm value

If a value does not follow this rule, all the values entered are in red, and the following tooltip is displayed: "Incorrect values. Fol-
low the rule: Max alarm value > Max alert value > Target value > Min alert value > Min alarm value".

Work orders block

- 189 -
 Work settings

Displays a list of the work orders triggered when the measurement is entered. 
The list can be used to view the following information for each WO: start date ("Day: Hour: Minute" format), code, title, status,
asset, reading date, value.

Clicking the icon at the end of the line opens the WO form in a new tab.

Rules for triggering a WO on a meter reading

When a measurement has alarm or alert values defined and a work order model is defined for these value ranges, if a mea-
surement reading correspond to one of these alarm or alert criteria, then a work order based on the corresponding model is crea-
ted.

The cases for triggering WOs are as follows:

- measurement reading strictly above the Min value and Max value > Max alarm value
- measurement reading strictly above the) Max alert value < Min value and Max value =< Max alarm value
- Max alert value <Min value and Max value
- Min alarm value =<Min value and Max value < Min alert value
- Min value and Max value < Min alarm value

This trigger cases have been defined to work on the asset whose measures reach critical values.

Any measurement reading at the origin of a WO trigger (when the reading is added from an asset or when it saved from a WO or
grouped WO) generates the following warning message: "The WO "XXX" was generated following your measurement reading".

Conditional WO case

When a conditional WO has been triggered after a measurement reading corresponding to a work model in the value range
concerned and this WO is in "To do" or "In progress" (or equivalent) status, any new measurement reading referring to the same
work model should not trigger a new WO.
This trigger avoids a redundant (therefore unnecessary) WO creation, which could happen if the first WO (or conditional WO)
was not yet processed.

- 190 -
Technician schedule

Displays the work lines scheduled in the WOs (by technician or technician category if the line is not assigned) at the start date of the envi-
saged labour line.
Rights to work orders are applied in the schedule.

Advanced filters enable a display:

- by team: the filter displays the list of technicians and technician categories belonging to the teams attached to the logged-in user's entity;
- by technician: the filter does not display the technician line;
- by category: the filter displays the category line AND the list of technicians in the same category;

The selection of different filters results in the display of data corresponding to the combination of these filters.

If the "Tree partitioning" module is enabled, for User and Guest accounts, the only WOs and grouped WOs visible are those with at least one
authorised asset, and grouped WOs without child WOs.

The schedule can be displayed by month, week, day or time line (hours of the day) (View tab).

By selecting a date with the icon , you view the schedule either at the start of the current day, at the beginning of the working week, or
at the start of the month (depending on the View).
You can also use the navigation arrows "<" and ">" to view the schedule over previous or following periods (each click corresponds to a varia-
tion of 1 hour for the "Day" view, 1 day for the "Week" view and 1 week for the "Month" view).
And you can use the navigation arrows "<<" and ">>" to view the schedule over the previous or following periods (each click corresponds to
a variation of 1 day for the "Day" view, 1 week for the "Week" view and 1 month for the "Month" view).

The user’s location information related to his or her language is used to start the week on the day defined as the beginning of the week.
The items displayed as well as the actions that can be performed depend on the logged in user's type of account: Guest, User or Supervisor.

Table Summarising the display and actions that can be performed by type of account
Action/display GUEST USER SUPERVISOR
Cancelled or equivalent orders displayed NO NO NO
Closed or equivalent orders displayed YES YES YES
Possibility of creating a report for a closed (or equivalent) order NO NO NO
Display of technician lines for his categories (categories added to his user profile) YES YES YES
Display of technician lines for categories other than his own (categories not present in his user profile) YES NO YES
Display of lines of his technician categories (categories added to his user profile) YES YES YES
Moving the work to himself (if there is nothing achieved entered) NO YES YES
Moving work to another technician NO NO YES
Resizing one's work NO YES YES
Resizing the work of other technicians NO NO YES
Possibility of taking the work (if there is nothing achieved entered) NO YES YES
Categories and technicians filter: displays one's categories and the technicians attached YES YES YES
Categories and technicians filter: displays the other categories and the technicians attached YES NO YES
Archives filter: displays archived work orders NO NO YES

Work is displayed in the time zone of the order's asset.

If the grouped work module is enabled, the workforce resources originating from the grouped WOs are displayed.
How these resources are displayed depends on the same rules as their equivalents originating from a standard WO (Colour, moves, resizing,
etc.)

Meaning of colours - Key

The different colours of the work slots indicate the progress of work completion.

Closed work = WO in closed or equivalent status

Completed work = achieved line checked completed
Work in progress = achieved line input and not completed
Work not begun = no achieved line input
Work not assigned = technician not entered, the labour line only has the technician category

The work is always displayed on the scheduled start date, even if it is completed on another date.

Actions
List of actions that can be performed by the buttons or by a right-click on a work:
 n Details: Opens the work details pop-in displaying the general information of the WO (code, asset, title), the resources, the
meters, the tasks and the comment relating to the work. The information cannot be modified on this screen.

In the case of a grouped WO, all the grouped WO assets are listed, as are the meters associated with all the work assets.

n WO: Opens the WO in a new tab so that it can be modified.

n Description: Displayed in the tooltip relating to the work.
n Report: Accessible if the work is assigned to a technician. Opens the report entry pop-in. See the Report entry section for more
information.

Other actions:

n Accept the work: For work assigned to a category, if the logged-in user has the technician role. Automatically assigns the work-
force line to the user, retrieving the hourly cost of the category for the technician. If work corresponds fully or partly to a non-
productive range from the logged-in user’s team, or specific to the logged-in user, the following warning message is displayed: :
"The technician is not available from DD/MM/YYYY HH:MM to dd/mm/yyyy hh:mm".
n Moving work : work can be moved using drag & drop: to another time slot and/or another technician (this move is not possible
for a user profile). You can access the "Move" action by right-clicking, with a pop-up displayed where Start date and End date can
be changed. If work corresponds fully or partly to a non-productive range from the logged-in user’s team, or specific to the log-
ged- in user, the following warning message is displayed: : "The technician is not available from DD/MM/YYYY HH:MM to
dd/mm/yyyy hh:mm".
n Resizing the work: it is possible to extend or shorten the work duration by stretching or reducing the size of the work slot.

A double-click on a work item also displays its details in a pop-in.

Technician schedule

Displays the work lines scheduled in the WOs (by technician or technician category if the line is not assigned) at the start date of the envi-
saged labour line.
Rights to work orders are applied in the schedule.

Advanced filters enable a display:

- by team: the filter displays the list of technicians and technician categories belonging to the teams attached to the logged-in user's entity;
- by technician: the filter does not display the technician line;
- by category: the filter displays the category line AND the list of technicians in the same category;

The selection of different filters results in the display of data corresponding to the combination of these filters.

If the "Tree partitioning" module is enabled, for User and Guest accounts, the only WOs and grouped WOs visible are those with at least one
authorised asset, and grouped WOs without child WOs.
The schedule can be displayed by month, week, day or time line (hours of the day) (View tab).

By selecting a date with the icon , you view the schedule either at the start of the current day, at the beginning of the working week, or
at the start of the month (depending on the View).
You can also use the navigation arrows "<" and ">" to view the schedule over previous or following periods (each click corresponds to a varia-
tion of 1 hour for the "Day" view, 1 day for the "Week" view and 1 week for the "Month" view).
And you can use the navigation arrows "<<" and ">>" to view the schedule over the previous or following periods (each click corresponds to
a variation of 1 day for the "Day" view, 1 week for the "Week" view and 1 month for the "Month" view).

The user’s location information related to his or her language is used to start the week on the day defined as the beginning of the week.

The items displayed as well as the actions that can be performed depend on the logged in user's type of account: Guest, User or Supervisor.

Table Summarising the display and actions that can be performed by type of account
Action/display GUEST USER SUPERVISOR
Cancelled or equivalent orders displayed NO NO NO
Closed or equivalent orders displayed YES YES YES
Possibility of creating a report for a closed (or equivalent) order NO NO NO
Display of technician lines for his categories (categories added to his user profile) YES YES YES
Display of technician lines for categories other than his own (categories not present in his user profile) YES NO YES
Display of lines of his technician categories (categories added to his user profile) YES YES YES
Moving the work to himself (if there is nothing achieved entered) NO YES YES
Moving work to another technician NO NO YES
Resizing one's work NO YES YES
Resizing the work of other technicians NO NO YES
Possibility of taking the work (if there is nothing achieved entered) NO YES YES
Categories and technicians filter: displays one's categories and the technicians attached YES YES YES
Categories and technicians filter: displays the other categories and the technicians attached YES NO YES
Archives filter: displays archived work orders NO NO YES

Work is displayed in the time zone of the order's asset.

If the grouped work module is enabled, the workforce resources originating from the grouped WOs are displayed.
How these resources are displayed depends on the same rules as their equivalents originating from a standard WO (Colour, moves, resizing,
etc.)

Meaning of colours - Key

The different colours of the work slots indicate the progress of work completion.

Closed work = WO in closed or equivalent status

Completed work = achieved line checked completed
Work in progress = achieved line input and not completed
Work not begun = no achieved line input
Work not assigned = technician not entered, the labour line only has the technician category

The work is always displayed on the scheduled start date, even if it is completed on another date.

Actions
List of actions that can be performed by the buttons or by a right-click on a work:

n Details: Opens the work details pop-in displaying the general information of the WO (code, asset, title), the resources, the
meters, the tasks and the comment relating to the work. The information cannot be modified on this screen.

In the case of a grouped WO, all the grouped WO assets are listed, as are the meters associated with all the work assets.

n WO: Opens the WO in a new tab so that it can be modified.

n Description: Displayed in the tooltip relating to the work.
n Report: Accessible if the work is assigned to a technician. Opens the report entry pop-in. See the Report entry section for more
information.

Other actions:

n Accept the work: For work assigned to a category, if the logged-in user has the technician role. Automatically assigns the work-
force line to the user, retrieving the hourly cost of the category for the technician. If work corresponds fully or partly to a non-
productive range from the logged-in user’s team, or specific to the logged-in user, the following warning message is displayed: :
"The technician is not available from DD/MM/YYYY HH:MM to dd/mm/yyyy hh:mm".
 n Moving work : work can be moved using drag & drop: to another time slot and/or another technician (this move is not possible
for a user profile). You can access the "Move" action by right-clicking, with a pop-up displayed where Start date and End date can
be changed. If work corresponds fully or partly to a non-productive range from the logged-in user’s team, or specific to the log-
ged- in user, the following warning message is displayed: : "The technician is not available from DD/MM/YYYY HH:MM to
dd/mm/yyyy hh:mm".
n Resizing the work: it is possible to extend or shorten the work duration by stretching or reducing the size of the work slot.

A double-click on a work item also displays its details in a pop-in.

Asset schedule

The asset schedule enables one to view an asset's work over time: It displays WOs and PWs that are not archived.
The WOs and PWs are displayed according to the mode: Asset/line and Date/column.
The grouped PW and grouped WO occurrences are also displayed for each asset if the Grouped work module is enabled.
Assets are grouped by sections of asset family, with the assets without family at the top of the schedule.
If the "Tree partitioning" module is enabled, for User and Guest accounts, the only assets visible on the schedule are those that are autho-
rised (to which their parents are added when you are in search on the Asset advanced filter).

A View tab enables you to select a view by week (by default) or month.
By selecting a date with the icon, you view the schedule either at the start of the working week, or at the beginning of the month (depen-
ding on the View).
You can also use the navigation arrows "<" and ">" to view the schedule over the previous or following periods (each click corresponds to a
variation of 1 day for the "Week" view and 1 week for the "Month" view).
You can use the navigation arrows "<<" and ">>" to view the schedule over the previous or following periods (each click corresponds to a
variation of 1 week for the "Week" view and 1 month for the "Month" view).
A WO/PW filter enables you to choose the WO or PW value (by default, all the WOs/PWs are displayed).
A Status filter enables you to choose the WO Status (by default, all the WO statuses are displayed; cannot be changed if WO/PW=PW).
The advanced filters display the schedule according to certain criteria (WO/PW, Status, Asset, Asset family, Type of work, Priority, Tech-
nology, Cost allocation, etc.); the archived values of the Asset, Asset family and Cost allocation fields are not taken into account.

Work orders are represented by a coloured bar which extends from the work order start date to end date.
The items displayed in the WO infobubbles, that can be accessed by moving the cursor over the WOs, are:

l WO code - WO title
l WR code or PW code if from WR or PW
l Status
l Start/end hours
l Type of work
l Priority
l WF: Estimated/Actual
l Shutdown: Yes/No
l Stoppage time: Estimated/Actual

Work is displayed taking into account the time zone of the order's asset.

Preventive work is scheduled on the date of the occurrence (theoretical trigger date).
The items displayed in the PW infobubbles, that can be accessed by moving the cursor over the PWs, are:
 l PW code - PW title
l Type of work
l Priority
l WF: Estimated/Actual
l Shutdown: Yes/No
l Stoppage time: Estimated/Actual

The rights to WOs and PWs (per entity) are applied.

For a PW belonging to a priority PW, PW occurrences obey prioritisation rules. A "warning" type icon appears in the first line of priority PWs,
followed by:
" 'Code-Title (PW triggered)' + 'priority' "

Meaning of colours - Key

The different colours of the work slots indicate the work progress. They correspond to the work order’s status (or equivalent status).
The five statuses defined are: To do, In progress, Completed, Closed and Cancelled.
Note: : Completed = Completed or equivalent status

Actions
List of actions that can be performed by the buttons or by a right-click on a work:

n OPEN button: Access to the form of the item selected (WO or PW)
n PRINT button: Prints the whole asset schedule, by default in landscape mode and A4 format, with the following characteristics:
o 1st page with a summary of the items displayed (title, printing date/time, advanced filters with values used)
o following pages with the content displayed (including, if possible, on each page: the title in the header, the legend in

the footer, reminder of the family of assets in the same family if they do not fit completely on the previous page),
without the presence of "View: Month/Week", "calendar" and "View navigation"

n Right-click on WO or PW: Opens the item in a new tab so that it can be modified.

To access the grouped WO of a child WO, right-click on the child WO and select Open grouped WO.

Other actions:

n Moving work : WOs whose status is "In progress", "To do" or "Completed" can be moved using drag & drop, but only to another
time slot. Moving PWs, cancelled or closed WOs and moving to other assets are forbidden.
n Resizing work: it is possible to extend or shorten the duration of WOs by stretching or reducing the work slot. Only resizing WOs
with "In progress", "To do" or "Completed" status is authorised. The action is impossible for cancelled or closed PWs or WOs.

During moving and resizing, the consistency between work order dates and resource dates is checked.
Double-clicking on a work item also displays its form.

Timetable

The timetable menu is subject to activation of the Timetable module in the Company form.
To enter the availability of a team or user, add time slots to the timetable.
The types of time slots are created beforehand.

Selecting a team filters the list of users, which only displays the team members.
Selecting a user filters the list of teams, which only displays the teams to which the user is linked.

It is possible to select a team without selecting a user and vice versa.

If a team is selected, the team's timetable is displayed.

If a user is selected, the user's timetable is displayed.

Attention: entering the timetable requires a recording.

Technician timetable and work in a WO or grouped WO

When adding or modifying a technician line in a WO or grouped WO, the technician's timetable must be checked.
The timetable hours are compared to the planned hours.
A warning message is displayed if the technician is not available for all or part of the work: "The technician is not available from
DD/MM/YYYY HH:MM to dd/mm/yyyy hh:mm".
If a time slot is "non-productive", it is considered outside the technician's working hours.

Adding a time slot

After selecting a team and/or user, click on the button.

Select the time slot and the type and validate the entry.
Each time slot entered in the timetable appears in the form of a coloured bar at the date and time of the time slot.
The colour corresponds to the one set in the time slot types.

Initialisation rules:
- the start time remains initialised to the start time of the time slot entered
- the end time is initialised with the value: start time + 1h

In multi-organisation mode, the proposed time slot types are the ones linked to at least one entity of the selected team or user.
Scheduling for a periodic time slot
To gain time during entry, enter a time slot that, by default, repeats daily in the same way for the “Day”, “Week”, and “Month” views.

The button is displayed in the list of Buttons, is active upon selection of a team or user,
and triggers display of an “Add periodic time slot” pop-in whose characteristics are as follows:

l Generic:

* restrictive period selection,

* start date initialised with the current date but may be modified,
* start time initialised with the entry time of the slot and the end date initialised to “+ 1h” by default, modifiable,
* end date empty by default, modifiable (maximum of 2 years),
* Type of time slot field listing the various types of time slots (Productive and Non-productive) attached to at least one team entity or to a
selected user, empty by default,
* availability of “Validate” and “Close” buttons,

l Specific to a daily periodic time slot:

* display of an associated text (every X days, with X=1 by default, modifiable, 1<X<999)

l Specific to a weekly periodic time slot:

* display of an associated text (every X weeks, with X=1 by default, modifiable, 1<X<999),
* display of days,
* multiple selection of desired days of the week,
* no selection of day by default,

l Specific to a monthly periodic time slot:

* display of an associated text (for week Y, with Y=1 by default with selections in a drop-down menu where Y=1;2;3;4; Last; for months of
repetition, no month selected by default and multiple selections possible),
* display of days based on Company / Entity schedules,
* restricted selection of desired days of the week,
* no selection of day by default,

l all required fields,

l calculation rule depending on display of days in the timetable,
l no consequences in time slot on not-worked schedules by Team,
l no option to copy-paste,
l entry for a team is copied to its members when the timetable is saved,
l display of the icon on the periodic time slots before the time in order to distinguish from conventional time slots,

Modifying a time slot

To change the availability of a team or a user, double-click on the desired time slot in the timetable.
Modifying a periodic time slot
To modify the availability of a team or user, it is possible to:

- either double-click on the preferred periodic time slots in the timetable;

The following confirmation message is displayed:
“Do you want to modify this time slot or the entire series of periodic time slots?”
with the following options: “This time slot”; “The entire series” and the buttons: “OK”; “Cancel”.
(before this confirmation message, during input, modifying a periodic time slot extends automatically to the entire series)

- extend or shorten the time slot directly in the timetable;

If an occurrence of a periodic time slot is modified, and if the series of occurrences of this slot is modified, the modified occurrence is over-
written by the change to the series.
A warning tooltip is then displayed:
“A specific change to a time slot in the series has been performed. It will be overwritten by an update to this series.”

Modification options are reserved for a Team (and are forbidden for all Users).

Moving and resizing time slots in the timetable

To move a time slot, drag and drop by selecting the time slot and dragging the selection to the desired location. Option to move on different
days or times.

To resize a time slot (increase or decrease its duration), select one end of the time slot and stretch or reduce the duration

The corresponding time slot is changed in the timetable of the team or user concerned.

Calculation and display of the first dates originating from a periodic time slot
To see the input range, the user can see an overview of the series of dates originating from the periodic time slot.

To do so, in the pop-in for adding a periodic time slot, a “Calculate” button enables the launch of a simulation process for up to 12 dates and
a display of the results, regardless of the duration of the periodic time slot (“Daily”, “Weekly”, or “Monthly).

Once the result has been displayed, the user can choose to change his/her settings, and as soon as a field is modified, the results of the list
of provisional dates is erased, permitting a new simulation.

Deleting a time slot

Select the time slot in the timetable and click the button.

Deleting a periodic time slot

Select the periodic time slot in the timetable or the entire series in the timetable and click the button.

The following confirmation message is displayed:

“Do you want to delete this time slot or the entire series of periodic time slots?”
with the following options: “This time slot”; “The entire series” and the buttons: “OK” and “Cancel”
(before this confirmation message, during input, modifying a periodic time slot extends automatically to the entire series)

Modification options are reserved for a Team (and are forbidden for all Users).

Copying and pasting a time slot

An existing time slot in a timetable, for the “Day”, “Week”, and “Month” views, can be copied and pasted under the following conditions:
- only in the same view and with the same category of filters (Teams / Users);
- for the Users category, only an “individual” time slot, and not a time slot from a team;
- in the “Month” view, the time of the copied slot is kept;
- in the “Day” and “Week” views, the slot is pasted at the time indicated by the mouse pointer (or the selected space);

Visualising a time slot

A time slot defined for a team should be visible in its members’ timetables.
It is only available to be viewed; the user does not have the right to modify or move it.
Visualisation:
- is valid for the "Day”, “Week”, and “Month” views;
- is valid for a user who is part of several teams;
- occurs when saving a team’s time slot;
- is not saved in the history when a user leaves a team;

Distinction between a team’s time slot and a member’s time slot

Two distinct icons have been created for the “Day”, “Week”, and “Month” views:

- for time slots originating with a team;

- for time slots originating with a user;

these two icons may be displayed in the same timetable if the user works on time slots that are his/hers alone as well as on those assigned
to his/her team.

Visualisation of the Timetable by Company / Entity hours

The timetable is displayed according to the following rules:

l for the “Day” and “Week” views:

- of the Entity if hours are entered for a single entity:

* the largest range is maintained (e.g.: if the ranges are Monday from 07:00 to 19:00 and Friday from 07:00 to 13:00, then 07:00 to 19:00 is
displayed),
* rounded off to the preceding or subsequent hour (e.g.: 07:00 is displayed for a start at 07:30, and 18:00 is displayed for an end at 17:30),
* no display of weekends if not entered in the Entity’s hours,

- of the Company if hours are entered and not entered for a single entity (or entered for a multi-entity):

* the largest range is maintained (e.g.: if the ranges are Monday from 07:00 to 19:00 and Friday from 07:00 to 13:00, then 07:00 to 19:00 is
displayed),
* rounded off to the preceding or subsequent hour (e.g.: 07:00 is displayed for a start at 07:30, and 18:00 is displayed for an end at 17:30),
* no display of weekends if not entered in the Company’s hours,

Note: - in “Day” view, when accessing a day that is not included in the (Entity/Company) hours that have been entered, the following day of
the Timetable is displayed (and so on, depending on the entered or not entered days, moving the view forward day by day).

* the current display is maintained if the Entity and Company hours are not set, or if the hours have only been entered in multi-entity mode:

* days displayed: Monday through Sunday,

* hours displayed: from 00:00 to 23:00,

l for the “Month” view:

- no display of hours,
- weekends not displayed if not entered in the relevant hours (Entity or Company).

Identification of not worked hours based on Team hours

To have a more precise timetable, not worked hours are distinguished by being greyed or crossed out [depending on the Team hours set
and the time range displayed]:

l for the “Day” and “Week” views:

* visible only upon selection of a team or a user,

* informational message if Team hours are outside Society / Entity hours (partly or completely),
* display of a tooltip: "The user is in several teams" if a user is selected on several teams and not filtered by Team,

l for the “Month” view:

* no display of hours,
* days greyed out if an entire day is not worked (aside from days not entered in the Company / Entity hours),

Identification of hours not worked based on User hours

With the same aim as above, hours not worked are distinguished by being greyed or crossed out [depending on the User hours configured
and the time range displayed]:

l for the “Day” and “Week” views:

* visible only upon selection of a user without Team filter,

* blocking message: "User Hours entered outside the Entity/Company hours" if User hours outside Company/Entity hours (at least partially),
* display of a tooltip: "The user is in several teams" if a user is selected on several teams and not filtered by Team,

l for the “Month” view:

* no display of hours,
* day greyed out if an entire day is not worked for the user without Team filter (aside from days not entered in the Company/Entity hours),
 Stock/Movements

Movements form

Part movements are accessible through the menu [Stocks-Purchases/Part movements].

Header block

The header block defines the main information of the movement to be carried out.

n Movement type: Part entry or withdrawal

n Date: Required, current date/time by default. Cannot be prior to the current date
n Title: Text, blank by default
n Employee: List of users
n Entity: List of entities, main entity by default

See the Part entry or Part removal section.

- 203 -
 Stock/Movements

Part Block

Used to select the part for the entry or removal movement.

n Part: Part selection drop-down list or pop-in. Required. Automatic selection of warehouse.
n Quantity: Required. If negative stock is forbidden in the warehouse, and if the Quantity entered is greater than the
Actual quantity for the part, a blocking message appears.
n Unit: Drop-down list of the units. Required. When a part is selected, the default unit selected is the storage unit of
the part. The list displays all the convertible units with the storage unit.
n Unit price: Required. (cannot be modified for parts removals; the unit price is retrieved from the part depending on
the valuation)
o For part entries :
o If the valuation type is by part: the price entered is the overall WAUP of the part (or the LPP if LPP

valuation)
o If the valuation type is by warehouse: the priced entered is the warehouse WAUP of the part (or the

LPP if LPP valuation).

o For part withdrawals : depends on the settings of the valuation type (WAUP, LPP, LIFO, FIFO, MEFO)
o part or warehouse WAUP or LPP according to the calculation method defined in the settings
o LIFO, FIFO, MEFO: Prices calculated according to the batches to be picked in the corresponding

order.

n Currency: Required.
o For part entries : When the warehouse is selected, the part price and warehouse currency are automatically

entered and can still be changed. The movement is recorded in the price and currency entered. Stock valua-
tions take into account the conversion of the movement price entered in the warehouse currency. Stocks
remain recorded in the warehouse currency. Batches are converted and recorded in the warehouse currency.
o For part withdrawals : When the warehouse is selected, the price is displayed in the warehouse currency.
They cannot be changed.

n Warehouse: Required. Automatically selected based on the part selected:

o if the part is under stock management in the main warehouse, this is selected
o if the part is under stock management in only one warehouse (other than the main warehouse), this ware-

house is selected
o if the part is under stock management in multiple warehouses (other than the main warehouse), or in

none of the warehouses, then no warehouse is selected

Movements are made at the date/time in the warehouse time zone (if the module is enabled).

Stock information displayed as read-only in a "Warehouse quantities before movement" part (at the day's Date/Time and not on
the movement date)

n Actual: represents the actual quantity of the warehouse selected before movement.
n Reserved: represents the reserved quantity of the warehouse selected before movement
n Ordered: represents the quantity ordered of the warehouse selected before movement
n Storage location: represents the location of the part in the warehouse selected and is displayed in "Code - Description"
format

Assignment Block

Used to allocate the movement to different elements:

- 204 -
 Stock/Movements

n Asset: Asset tree ("Code - Description" format). Entered automatically when a WO is selected. Updates the WO list.
Box to be checked: “With children”.
n Work order: List of WOs that are not archived, closed or cancelled. The list is filtered according to the selected asset
and/or cost allocation.
n Cost allocation: Cost allocation tree. Entered automatically when a WO is selected. Updates the WO list.

Entry of part managed in stock

When an entry of a part managed in stock is saved:

n Updating of the stock: quantity and price

o Calculation method: Actual quantity = Actual quantity + Entry quantity

o LPP = EntryPrice
o WAUP = [(ActualQty * WAUP) + (EntryQty * EntryPrice)]/(ActualQty + EntryQty)

n Creation of a batch: Date, Part, Warehouse, Entry quantity, Unit, Unit price, Currency, Current quantity
n Generation of a part movement: Date, Title, Employee, Item, Entry quantity, Unit, Price, Currency, Warehouse. The
movement can be viewed in the Part form Movements block.

Removal of part managed in stock

When a removal of a part managed in stock is saved:

n Updating of the stock for the warehouse: Quantity and price. Calculation method: Actual quantity = Actual quantity -
Removal quantity Impact on the Quantity available.
n Updating of the batches: deduction of the current quantity of the batches. The order in which the batches are taken
into account depends on the valuation type.
n Generation of a part movement: Date, Title, Employee, Item, Removal quantity, Unit, Price, Currency, Warehouse.
The movement can be viewed in the Part form Movements block.

Entries and issues of parts not managed in stock

Movements of items not managed in stock can be managed in warehouses in order to keep a trace of them.

When the entry or removal movement is saved:

n no change in the quantity in stock

n no batches created
n Generation of a movement (as in cases where the part is managed in stock) viewable in the Movements block of the
part
n Movement forbidden if the movement date is prior to changing the part status to “not under stock management”

- 205 -
 Stock/Movements

Movements

List of movements
This list is available from the [Stock/Purchases-Parts movements] menu (if the stocks module is enabled).
The list displays all the parts movements completed (including parts movements not listed on order delivery or report entry)
The available actions depend on the user rights [Settings-User-User profile]

Click on the button to view a movement.

Click on the button to create a part entry or withdrawal movement.

Click on the button to access the page for creating interwarehouse movements.

Pressing the duplication button opens a movement form in create mode but does not duplicate any of the move-
ment data.

For further details, refer to the movement form.

Advanced filters

This block, which is closed by default, shows the following fields:

n Movement type: Drop-down list, with the choices: “All”, “Part entry”, “Part withdrawal”.
n Date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Title: Text field. Automatic filter upon entry.
n Employee: Selection list.
n Part: Typeahead and standard part search window, filtered to the logged-in user’s entity/ies.
n Part family: Typeahead and standard search window of asset families, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Warehouse: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Work order: Text field. Automatic filter upon entry.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Delivery note: Text field. Automatic filter upon entry
n Operation type: Selection list.
The operation types are:
- WO when the movement results from a WO
- Grouped WO when the movement results from a Grouped WO
- Order when the movement results from a delivery
- Inventory when the movement results from an inventory
- Movement when the movement results from a manual movement

- 206 -
 Stock/Movements

- Transfer when the movement results from a transfer between warehouses

Specific cases of manual movements :

If the movement is of withdrawal type and is not attached to a WO, then Operation type=Movement;
If the movement is of withdrawal type and is attached to a WO, then Operation type=WO;
If the movement is of entry type, in every case Operation type=Movement;

Consideration of imports :
For the Sage X3 movements history import, the Operation type=Movement
For the Stock import, the Operation type=Movement
For the Movements import, the Operation type=Movement

- if the Work order field (Code) is not filled in, Operation type=Movement
- if the Work order field (Code) is filled in and Movement type=Entry, Operation type=Movement
- if the Work order field (Code) is filled in and Movement type=Withdrawal, Operation type=WO

Movements

List of movements
This list is available from the [Stock/Purchases-Parts movements] menu (if the stocks module is enabled).
The list displays all the parts movements completed (including parts movements not listed on order delivery or report entry)
The available actions depend on the user rights [Settings-User-User profile]

Click on the button to view a movement.

Click on the button to create a part entry or withdrawal movement.

Click on the button to access the page for creating interwarehouse movements.

Pressing the duplication button opens a movement form in create mode but does not duplicate any of the move-
ment data.

For further details, refer to the movement form.

Advanced filters

This block, which is closed by default, shows the following fields:

n Movement type: Drop-down list, with the choices: “All”, “Part entry”, “Part withdrawal”.
n Date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Title: Text field. Automatic filter upon entry.
n Employee: Selection list.

- 207 -
 Stock/Movements

n Part: Typeahead and standard part search window, filtered to the logged-in user’s entity/ies.
n Part family: Typeahead and standard search window of asset families, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Warehouse: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Work order: Text field. Automatic filter upon entry.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Delivery note: Text field. Automatic filter upon entry
n Operation type: Selection list.
The operation types are:
- WO when the movement results from a WO
- Grouped WO when the movement results from a Grouped WO
- Order when the movement results from a delivery
- Inventory when the movement results from an inventory
- Movement when the movement results from a manual movement
- Transfer when the movement results from a transfer between warehouses

Specific cases of manual movements :

If the movement is of withdrawal type and is not attached to a WO, then Operation type=Movement;
If the movement is of withdrawal type and is attached to a WO, then Operation type=WO;
If the movement is of entry type, in every case Operation type=Movement;

Consideration of imports :
For the Sage X3 movements history import, the Operation type=Movement
For the Stock import, the Operation type=Movement
For the Movements import, the Operation type=Movement

- if the Work order field (Code) is not filled in, Operation type=Movement
- if the Work order field (Code) is filled in and Movement type=Entry, Operation type=Movement
- if the Work order field (Code) is filled in and Movement type=Withdrawal, Operation type=WO

Movements form

Part movements are accessible through the menu [Stocks-Purchases/Part movements].

- 208 -
 Stock/Movements

Header block

The header block defines the main information of the movement to be carried out.

n Movement type: Part entry or withdrawal

n Date: Required, current date/time by default. Cannot be prior to the current date
n Title: Text, blank by default
n Employee: List of users
n Entity: List of entities, main entity by default

See the Part entry or Part removal section.

Part Block

Used to select the part for the entry or removal movement.

- 209 -
 Stock/Movements

n Part: Part selection drop-down list or pop-in. Required. Automatic selection of warehouse.
n Quantity: Required. If negative stock is forbidden in the warehouse, and if the Quantity entered is greater than the
Actual quantity for the part, a blocking message appears.
n Unit: Drop-down list of the units. Required. When a part is selected, the default unit selected is the storage unit of
the part. The list displays all the convertible units with the storage unit.
n Unit price: Required. (cannot be modified for parts removals; the unit price is retrieved from the part depending on
the valuation)
o For part entries :
o If the valuation type is by part: the price entered is the overall WAUP of the part (or the LPP if LPP

valuation)
o If the valuation type is by warehouse: the priced entered is the warehouse WAUP of the part (or the

LPP if LPP valuation).

o For part withdrawals : depends on the settings of the valuation type (WAUP, LPP, LIFO, FIFO, MEFO)
o part or warehouse WAUP or LPP according to the calculation method defined in the settings
o LIFO, FIFO, MEFO: Prices calculated according to the batches to be picked in the corresponding

order.

n Currency: Required.
o For part entries : When the warehouse is selected, the part price and warehouse currency are automatically

entered and can still be changed. The movement is recorded in the price and currency entered. Stock valua-
tions take into account the conversion of the movement price entered in the warehouse currency. Stocks
remain recorded in the warehouse currency. Batches are converted and recorded in the warehouse currency.
o For part withdrawals : When the warehouse is selected, the price is displayed in the warehouse currency.
They cannot be changed.

n Warehouse: Required. Automatically selected based on the part selected:

o if the part is under stock management in the main warehouse, this is selected
o if the part is under stock management in only one warehouse (other than the main warehouse), this ware-

house is selected
o if the part is under stock management in multiple warehouses (other than the main warehouse), or in

none of the warehouses, then no warehouse is selected

Movements are made at the date/time in the warehouse time zone (if the module is enabled).

Stock information displayed as read-only in a "Warehouse quantities before movement" part (at the day's Date/Time and not on
the movement date)

n Actual: represents the actual quantity of the warehouse selected before movement.
n Reserved: represents the reserved quantity of the warehouse selected before movement
n Ordered: represents the quantity ordered of the warehouse selected before movement
n Storage location: represents the location of the part in the warehouse selected and is displayed in "Code - Description"
format

Assignment Block

Used to allocate the movement to different elements:

n Asset: Asset tree ("Code - Description" format). Entered automatically when a WO is selected. Updates the WO list.
Box to be checked: “With children”.
n Work order: List of WOs that are not archived, closed or cancelled. The list is filtered according to the selected asset

- 210 -
 Stock/Movements

and/or cost allocation.

n Cost allocation: Cost allocation tree. Entered automatically when a WO is selected. Updates the WO list.

Entry of part managed in stock

When an entry of a part managed in stock is saved:

n Updating of the stock: quantity and price

o Calculation method: Actual quantity = Actual quantity + Entry quantity

o LPP = EntryPrice
o WAUP = [(ActualQty * WAUP) + (EntryQty * EntryPrice)]/(ActualQty + EntryQty)

n Creation of a batch: Date, Part, Warehouse, Entry quantity, Unit, Unit price, Currency, Current quantity
n Generation of a part movement: Date, Title, Employee, Item, Entry quantity, Unit, Price, Currency, Warehouse. The
movement can be viewed in the Part form Movements block.

Removal of part managed in stock

When a removal of a part managed in stock is saved:

n Updating of the stock for the warehouse: Quantity and price. Calculation method: Actual quantity = Actual quantity -
Removal quantity Impact on the Quantity available.
n Updating of the batches: deduction of the current quantity of the batches. The order in which the batches are taken
into account depends on the valuation type.
n Generation of a part movement: Date, Title, Employee, Item, Removal quantity, Unit, Price, Currency, Warehouse.
The movement can be viewed in the Part form Movements block.

Entries and issues of parts not managed in stock

Movements of items not managed in stock can be managed in warehouses in order to keep a trace of them.

When the entry or removal movement is saved:

n no change in the quantity in stock

n no batches created
n Generation of a movement (as in cases where the part is managed in stock) viewable in the Movements block of the
part
n Movement forbidden if the movement date is prior to changing the part status to “not under stock management”

Interwarehouse movements form

Interwarehouse movements are accessible from the [Stocks-Purchases/Parts movements] menu, after having clicked on the but-

ton .

- 211 -
 Stock/Movements

Header block

The header block defines the main information of the movement to be carried out.

n Date: Required, current date / time by default

n Title: Text, blank by default
n Employee: List of users
n Entity: List of entities, main entity by default

Part Block

Used to select the part for the entry or removal movement.

n Original Warehouse: List of the entity’s warehouses (except for the Destination warehouse if selected first), required.
Represents the original warehouse for the withdrawn part.
n Destination Warehouse: List of the entity’s warehouses (except for the Original Warehouse if selected first), required.
Represents the destination warehouse for the entry part.
n Part: Part selection drop-down list or pop-in, required, empty by default. Automatic selection of warehouse.
n Part label: Based on the selected part, non-modifiable.
n Quantity: Required, value of 0.00 by default. If negative stock is forbidden in the warehouse, and if the Quantity ente-
red is greater than the Actual quantity for the part, a blocking message appears.
n Unit: Drop-down list of the convertible units with the storage unit, required, empty by default. When a part is selec-
ted, the default unit selected is the storage unit of the part of the Original Warehouse.
n Unit price: Required, non-modifiable for part withdrawals.
o For part entries :
o If the valuation type is by part: the price entered is the overall WAUP of the part (or the LPP for LPP

valuation).
o If the valuation type is by warehouse: the priced entered is the WAUP in the warehouse of the part

(or the LPP for LPP valuation).

o For part withdrawals : depends on the settings of the valuation type (WAUP, LPP, LIFO, FIFO, MEFO)
o part or warehouse WAUP or LPP according to the calculation method defined in the settings.
o LIFO, FIFO, MEFO: Prices calculated according to the batches to be picked in the corresponding

order; in the case of a transfer involving several batches in the original warehouse: unit price cor-
responding to the WAUP of the corresponding batches.

- 212 -
 Stock/Movements

n Currency: Required.
o For part entries : When the warehouse is selected, the part price and warehouse currency are automatically

entered and can still be changed. The movement is recorded in the price and currency entered. Stock valua-
tions take into account the conversion of the movement price entered in the warehouse currency. Stocks
remain recorded in the warehouse currency. Batches are converted and recorded in the warehouse currency.
o For part withdrawals : When the warehouse is selected, the price is displayed in the warehouse currency.
They cannot be changed.

Sub-block Original Warehouse:Quantities before transfer:

n Actual: Represents the actual quantity in the original warehouse before transfer.
n Reserved: Represents the reserved quantity in the original warehouse before transfer.
n Ordered: Represents the ordered quantity in the original warehouse before transfer.
n Storage location: “Code - Description” format (likewise Stocks block, Part form). Represents the location of the part
under stock management in the original warehouse.

All of these fields are calculated upon selection of the part to be transferred and are non-modifiable.

Sub-block Original Warehouse Quantities before transfer:

n Actual: Represents the actual quantity in the destination warehouse before transfer.
n Reserved: Represents the reserved quantity in the destination warehouse before transfer.
n Ordered: Represents the ordered quantity in the destination warehouse before transfer.
n Storage location: “Code - Description” format (likewise Stocks block, Part form). Represents the location of the part
under stock management in the destination warehouse.

All of these fields are calculated upon selection of the part to be transferred and are non-modifiable.

Movements are made at the date/time in the warehouse time zone (if the module is enabled).

Movements are forbidden in two cases:

1. The part is not in stock on the transfer date (either in one of the warehouses, or in both at the same time)
2. The part, which is in stock in both warehouses on the transfer date, has changed stock management status since this transfer
date (either in one of the warehouses or in both at the same time)
(this is the case when the part's status changes from "In stock" to "Not in stock", then to "In stock" again).

Assignment Block

Used to allocate the movement to different elements:

n Asset: Asset tree, empty by default. Entered automatically when a WO is selected. Updates the WO list.
n Work order: List of WOs that are not archived, closed or cancelled, empty by default. The list is filtered according to
the selected asset and/or cost allocation.
n Cost allocation: Cost allocation tree, empty by default. Entered automatically when a WO is selected. Updates the
WO list.

- 213 -
 Stock/Movements

Purchase requests

List of purchase requests

This list is available from the [Stock/Purchases-Purchase requests] menu (if the order module is enabled).
The list displays all the non-archived PRs, sorted in ascending order of the PR codes.

The available actions depend on the user rights and the PR status. [Settings-User-User profiles] and [Settings-Configuration-PR
status administration]
Creating a PR

A PR can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating an asset, refer to the purchase request form.
Deleting a PR

To delete a team:

n click on the button on the form or list of PRs.

n from the list of PRs, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

It is impossible to delete a PR that is in Closed, Sent or Processed status.
It is authorised to delete PRs in Cancelled or In preparation status.

Archiving/De-archiving a PR

A PR can be archived:

n by clicking on the button on the list of PRs or the PR form.

n from the list of PRs, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the code and the PR title, indicating that it has been archived.
Archived PRs are no longer visible in the drop-down lists or the search fields.

Only cancelled or closed PRs can be archived.

It is impossible to archive PRs in In preparation, Sent or Processed status.

A PR can be de-archived:

- 214 -
 Stock/Movements

n by clicking on the button on the list of PRs, or the PR form.

n from the list of PRs, by clicking on the arrow at the end of the line.

The PR is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a PR

To duplicate a team:

n click on the button on the PR form.

n from the list of PRs, click on the button at the end of the line.

Duplication copies the selected PR to a new PR. All the information is duplicated except:

l Code: blank
l Status: configuration of the administration of PR statuses or “In preparation” if no configuration is set
l Creation date: Current Date/Time
l Requester: Connected user
l (PR code)

Closing a PR

A PR can be closed by changing the PR to Closed status.

A closed PR cannot be changed, it is read only.
A closed PR cannot be converted into an order.

It is possible to configure authorisations for PR modifications according to their status in the menu [Settings-Configuration-PR sta-
tus administration]. Therefore, a closed PR can become non-modifiable.

Reopening a PR

To reactivate a closed PR, click on the button located to the top right of the form.
It then takes on the status defined in PR status administration if it is configured. Otherwise it changes back to "In preparation"
status.

Cancelling a PR

A PR is cancelled by changing its status to Cancelled.

A cancelled PR cannot be changed, it is read only.

To reactivate a cancelled PR, click on the button located to the top right of the form.
It then takes on the status defined in PR status administration if it is configured. Otherwise it changes back to "In preparation"
status.

- 215 -
 Stock/Movements

It is possible to configure authorisations for PR modifications according to their status in the menu [Settings-Configuration-PR sta-
tus administration]. Therefore, a cancelled PR can become non-modifiable.

Converting a PR into an order

To convert a PR into an order, the user must have all the editing rights (at least) for orders on the purchase request entity.

The conversion can be done:

n By clicking on the button on the PR form, in the list of PRs.

n From the PR form, by clicking on the button .

It is possible to authorise or forbid conversion of PRs into orders depending on the PR status. It is configured through the menu
[Settings-Configuration-Administration of PR statuses]. Therefore, a closed PR can no longer be converted into a WO.
As soon as conversion is possible, the tab of the Order form is highlighted (orange), and if the user closes the Order before saving
it, the following confirmation is displayed:
"The following action requires a response from you: Save the order before exiting".

If a supplier is entered, the PR currency is retained and the unit prices excl. tax of the PR lines are used in the purchase order.

If no supplier is entered, a window is displayed enabling us to choose the supplier with whom to place the order. The order will
be initialised with this supplier. In this list, we only see partners who are suppliers and associated with the PR entity.

Whether or not the supplier as a currency identical to the PR, the PR currency is retained and the unit prices excl. tax of the PR
lines are used in the purchase order.

When a supplier is selected then confirmed ('Convert into a purchase order' button), if the PR lines have parts listed with this sup-
plier, then a pop-in is displayed with the following message:
"Parts are listed with this supplier. Do you want to update the unit prices excl. tax for these part lines?"
Choices: Yes/No/Cancel.

o Yes: We retrieve the prices listed. Conversion in to the PR currency if different supplier.

o No: We retain the prices of PR lines

o Cancel: Back to the supplier's window of choice with the Supplier field blank, enabling a potential return to the PR.

The order generated is initialised with the PR information.

o Title -> Title

o Entity -> Entity
o Supplier -> Supplier
o Part lines -> Part lines
o Part -> Part
o Description -> Description
o Quantity -> Quantity
o Unit -> Unit
o Warehouse -> Warehouse
o Code -> PR code in read only

- 216 -
 Stock/Movements

The information that can be retrieved from the Part/Supplier link is retrieved.

For further explanation on creating a PR, refer to the PR form.

If an order is to be generated when there is no automatic coding, alternative coding is used which consists solely of a numerical
meter.
If the logged-in user at least has editing rights for orders on the purchase request entity, there is a "Convert into order" button
(icon: cart3) (in 2nd position after the opening button)

A PR can be converted into an order several times.

The reference to the PR is stored on the order generated.

- 217 -
 Stocks - Purchases

Purchase request form

Accessible through the [Stock/Purchases-Purchase requests] menu (if the orders module is enabled).

The available actions depend on the user rights and the PR status [Settings-User-User profile] and [Settings-Configuration-PR sta-
tus administration].

Configurations are made on purchase requests in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)
l Configuration of notifications-alerts

The New, Delete, Archive, Convert into order and Duplicate buttons are explained in the actions of the Purchase requests list.

The icons give access to the various forms or to the corresponding repositories (parts, users, small reference tables, etc.) so
that information can be viewed or modified during entry.

Some actions performed on the PR may trigger an email notification: PR creation, PR conversion into an order, reopening a PR,
etc.
For more information about activation and configuration, refer to the Email administration section.

Header block

The header block defines the main information of the PR.

n Code: Required field: the code of a PR is unique. Automatic codification can be enabled in the user profile.
n Title: Required field.
n Requester: Selection list (required). List of users of the PR entity. Initialised with the logged in user.
n Entity: Required field, visible only if the number of entities in the licence key is above 1. The PR must be associated
with an entity (and can only be associated with one entity).
n Creation date: Date/Time (required)
n Recipient: Selection list. List of users of the PR entity. Initialised with the PR recipient entered by default in
the configuration [Configuration/General settings] or Association block/General settings of the entity if

- 219 -
 Stocks - Purchases

multi-organisation mode).
n Supplier: Selection list. List of supplier partners.
n Currency: Required field. When the PR is created, the currency is initialised with that of the requester, corresponding
to the logged-in user, and can be edited (according to a change in requester, with the new requester's currency taken
into account). If the supplier is entered, the currency is initialised with the supplier's currency and cannot be edited
(unless the supplier is changed, with the new supplier's currency used).
n Status: Selection list (required). When created, a PR has the status configured in PR status administration for the
"Create PR" action if it is enabled. If it is disabled, the PR status is "In preparation" by default. The statuses available
are: In preparation, Sent, Processed, Cancelled, Closed.

See the PR statuses and PR status administration sections

For more information on closing, reopening and cancelling PRs, see the PR list section.
The status of PRs can be changed:

n Manually, in the PR form, by selecting the status in the list of available statuses,
n Automatically according to the actions performed, according to a configuration made in the menu [Settings-Con-
figuration-PR status administration] or [Association block/Administration of PR statuses of the entity if multi-orga-
nisation mode]

The status change history of a PR can be viewed by clicking on the icon in the PR header block. The pop-in displays the
date, the status and the user for each status change.

The user's main entity is retrieve and the non-archived entities are displayed in the list.
The user must at least have editing rights for purchase requests (for each entity displayed).

When the PR entity is changed, the data is updated:

- the data selected are kept, if it is associated with the new entity
- the data is blank, if it is not associated with the new entity.

Comment block

Comments are displayed in discussion mode in order to have a trace of their history.
Comment are displayed in chronological order, from the most recent to the oldest.
Their number is displayed on the Comments block if it is folded.

Click on the button to open the comment input pop-in. Enter the comment then click on the button

to go back to the PR.

The comment is added to the list of comments, with the name and photo of the user who entered it. It is possible to zoom on
the photo.

- 220 -
 Stocks - Purchases

Each comment can be unfolded and folded.

A comment entered by another user cannot be modified or deleted.

Parts block

Enables one to add parts cited or not cited to the request:

n Part: List of choices or selection pop-in (required)

n Description: Description of the part selected (grey) or open input if no part is selected
n Quantity: numerical field (required)
n Unit: Selection list (required)
n Warehouse: Selection list
n Unit price excl. tax + Currency: Required field. Price can be changed and initialised with the supplier's price if supplier
entered and part listed with this supplier (otherwise, initialised at '0.00'); price set according to a choice pop-in if sup-
plier entered after the creation of PR lines ("There are parts listed with this supplier. Do you want to update the unit
prices excl. tax for these part lines?"; choice: Yes/No/Cancel). Currency initialised and can be changed (without price
recalculation) according to the currency of the Header block

It is authorised to add parts that are not managed in stock.

In multi-organisation mode, the lists taken the PR entity into account.

Associated files block

Forms can be linked with the PR.

The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Orders block

Displays the orders relating to the purchase request.

The list is used to view the following information for each order:

n Creation date
n Code: linked to the order
n Title
n Scheduled delivery date
n Status
n Supplier

The following actions are possible:

n Click on the order line to view additional information

n Click the icon to open the Order form in a new tab

n Filter in each column
n Sort in each column or in combination
n Sort by default by Creation date then Code

The user must have read rights for the order for it to be visible and accessible

- 221 -
 Stocks - Purchases

Orders

List of orders
This list is available from the [Stock/Purchases-Orders] menu (if the order module is enabled).
The list displays all the non-archived orders, sorted in ascending order of the codes.

The available actions depend on the user rights and the order status [Settings-User-User profile] and [Settings-Configuration-
Order status administration]
Creating an order

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating an order, refer to theorder form.

Deleting an order

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

It is impossible to delete an order that is in Closed, Sent or Processed (or equivalent) status.
Deleting orders in Cancelled or In preparation (or equivalent) status is authorised.

It is not possible to delete an order line that has already had deliveries made.

Archiving an order

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the title, indicating that it has been archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

Only cancelled or closed orders (or equivalent statuses) can be archived.

It is impossible to archive orders in In preparation, Sent or Processed (or equivalent) status.

To de-archive, proceed as follows:

- 222 -
 Stocks - Purchases

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating an order

To duplicate a team:

n click on the button on the form.

n From the list, click on the arrow at the end of the line.

Duplication copies the element selected. All the information is duplicated except:

l Code: blank
l Status: configuration of order status administration or “In preparation” if no configuration is set
l Creation date: Current Date/Time
l Issuer: Connected user
l Supplier order reference: blank
l Scheduled delivery date: blank

Comments block
All the comments are duplicated

Order line block

PART LINES
Scheduled delivery date: Creation date + time
Balanced: no
All the delivery information is duplicated.

SUBCONTRACTOR LINES
Scheduled delivery date: blank
Balanced: no
All the delivery information is duplicated.

Closing an order

An order can be closed by changing the order to Closed status.

A closed order cannot be changed, it is read only.

Part/Supplier link
When an order is closed, for all the Part type lines, if the link between the supplier and the part does not exist, it is created:

l Supplier, reference, discount, order unit, unit price

l Time (d) -> Delta between Order creation date and Last delivery date
l Main -> YES If first link with a supplier for the part
l Minimum purchase quantity -> 0
l Price validity -> blank
l Last update -> Order creation date

- 223 -
 Stocks - Purchases

Reopening an order

To reactivate a closed order, click on the button located to the top right of the order form.
It then takes on the status defined in order status administration if it is configured.

Cancelling an order

An order is cancelled by changing its status to Cancelled.

A cancelled order cannot be changed, it is read only.

To reactivate a cancelled order, click on the button located to the top right of the order form.
It then takes on the status defined in order status administration if it is configured.

It is not possible to cancel an order line that has already had deliveries made.

Delivering an order

Order deliveries can be made on orders that are in Sent or Processed status (if the user has editing rights on orders for the order
entity).

To make a delivery, click on the button located at the end of the order line (for parts of subcontracting).
This button is available to the user even if they do not have order editing rights.

Part order delivery

The following information must be entered in the order delivery window:

n Delivery note: open input (Required)

n Delivery date: (Date/Time) (Required) (Current Date/Time by default). If this date is prior to the date for potentially
changing the part from “Managed in stock” to “Not managed in stock”, or after the days’ date, the order is forbidden.
n Quantity accepted (Decimal) (Required) > 0!
n Unit: cannot be changed -> Order line unit
n Warehouse (Required): displays the order line warehouse by default. Changing the warehouse for the delivery is autho-
rised. The quantity ordered is deducted at delivery.
n Balanced: If the sum of all the quantities delivered is above the quantity ordered, the Balanced field is checked auto-
matically but can still be changed.

Subcontracting order delivery

The following information must be entered in the order delivery window:

n Delivery note: open input (Required)

n Delivery date (Required). If the date is prior to the days’ date, the order cannot be placed.
n Actual duration (Required) > 0
n Part cost
n Balanced: if the sum of all the quantities completed/delivered is above the duration ordered, the Balanced field is che-
cked automatically but can still be changed.

Also see the section Link between order and work orders for the specific features of the subcontracting order line delivery allo-
cated to a work order

- 224 -
 Stocks - Purchases

To view deliveries in detail, click on the button in the order header.

The summary is displayed by delivery date.
For a part line, the following information is displayed:
- Delivery note code - Part (or Description if not listed)
- Quantity accepted - Warehouse

For a subcontracting line we have the following info:

- Delivery note code - Description
- Actual duration - Part cost

It is impossible to cancel or delete an order that has begun to be delivered.

Advanced filters

This block, which is closed by default, shows the following fields:

n Code: Text field. Automatic filter upon entry.

n Title: Text field. Automatic filter upon entry.
n Status: Drop-down list, with the choices: “Active”, “Being terminated”, “Terminated”.
n Issuer: Selection list.
n Creation date (Entry): DateTime type field "Day: Hour: Minute”, with manual input or via the “calendar” icon.
n Supplier: Selection list.
n Part: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies.
n Warehouse: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Work order: Text field. Automatic filter upon entry.
n Cost allocation: Typeahead and standard cost allocation search window, filtered to the logged-in user’s entity/ies.
Associated with: “With children” check box.
n Supplier order reference: Text field. Automatic filter upon entry.

- 225 -
 Stocks - Purchases

Order form
Accessible through the [Stock/Purchases-Orders] menu. (If the orders module is enabled)

The available actions depend on the user rights and the order status [Settings-User-User profile] and [Settings-Configuration-
Order status administration]

Configurations on orders are made in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)

The New, Delete, Archive, Reopen order and Duplicate buttons are explained in the actions of the Orders list.

The icons give access to the various forms or to the corresponding repositories. (parts, users, small reference tables, etc.) so
that information can be viewed or modified during entry.

Some actions performed on the order may trigger an email notification: order creation, partial or complete delivery, order clo-
sure, etc.
For more information about activation and configuration, refer to the Email administration section.

Click on the button to display a summary of deliveries relating to the order.

For more details on the delivery, see the "Delivering an order" section of the Orders list.

Header block

The header block defines the main information of the order:

- 226 -
 Stocks - Purchases

n Code: Required if no automatic codification on the order entity

n Title: Required
n Status: Drop-down list. When created, the order takes on the status configured in the order status administration for
the "Create order" action if it is enabled. If it is disabled, the order status is "In preparation" by default. The statuses
available are: In preparation, Sent, Processed, Cancelled, Closed and equivalent (non-archived) statuses. Orders can be
made non-modifiable depending on their status.

For more information on order statuses, see the Order status and Order status administration sections
For more information on closing, reopening and cancelling orders, refer to the Order list section.
Changing an order to Sent or Processed status:
- makes the supplier compulsory if it has not been entered.
- makes it impossible to change the supplier.
- updates the quantity of parts ordered which are in stock in the order line warehouse.
- adds a part type resource line to the work order (if the line is allocated to a work order and the warehouse has been entered) -
> see below in the section Links between orders and work orders
- makes delivery of the order possible-> see the Order delivery section

It is impossible to change an order back to "In preparation" status when it has already changed status.

n Entity: Drop-down list of entities with user right (Required and unique, Visible in multiple entities)
n Creation date: Date/Time (Required)
n Issuer: Drop-down list of order entity users
n PR code: Cannot be modified, the field is displayed when the order originates from a PR. Used to view the PR.
n Supplier: Drop-down list of supplier or subcontractor type partners. Selecting a supplier automatically retrieves the sup-
plier currency to the order. The supplier is not required as long as the order has not been sent. It can no longer be
modified once it has been sent.

When the supplier has been selected for each part line filled in:
- if the supplier reference is blank, the supplier reference is automatically retrieved from the Part/Supplier link
- if the quantity is below the minimum purchase quantity, the quantity is automatically retrieved from the Part/Supplier link
- if the quantity is below the minimum purchase quantity, the unit is automatically retrieved from the Part/Supplier link
- If the price is 0, the unit price is automatically retrieved from the Part/Supplier link including the currency

n Currency: List of currencies used in the application (Required). The currency automatically retrieves the currency of the
supplier selected and can no longer be changed.
n Cost allocation
n Work order: List of work orders
n Asset
n Warehouse
n Contact: Drop-down list of supplier contacts, blank if no supplier selected.
n Supplier order reference
n Scheduled delivery date: Cannot be changed, the date is updated with the scheduled delivery date furthest from the
order lines.

Order status changes can be made:

n Manually, in the form, by selecting the Status in the list of available statuses.
n Automatically according to the actions performed, based on a configuration made in the menu [Settings- Con-
figuration-Order status administration] or [Association block/Administration of entity order statuses if multi-orga-
nisation mode]

The status change history of an order can be viewed by clicking on the icon in the Header block. The pop-in displays the
date, the status and the user for each status change.

- 227 -
 Stocks - Purchases

The user's main entity is retrieve and the non-archived entities are displayed in the list.
The user must at least have editing rights for orders (for each entity displayed).

When the order entity is changed, the data is updated:

- the data selected are kept, if it is associated with the new entity
- the data is blank, if it is not associated with the new entity.

When an order line is created, some fields are initialised based on the header information: work order, cost allocation, asset or
warehouse.

When the VAT module is enabled, the following fields are added:

n VAT (%): Not required. Selection list from the TDR VAT and relating to the entities of the concerned user.

Conditions block

This block enables us to enter the different conditions applicable for the order:

n Payment terms: Drop-down list of terms of payment

n Term of delivery: Drop-down list of terms of delivery
n Order footer: Open input

The first two fields are initialized, when an order is created or when a PR is changed into an order, when they are defined in the
Partner form.
If they are entered when a purchase order is created without a supplier, these values will be overwritten when a supplier with
them is selected.

Comments block

Comments are displayed in discussion mode in order to have a trace of their history.
Comment are displayed in chronological order, from the most recent to the oldest.
Their number is displayed on the Comments block if it is folded.

Click on the button to open the comment input pop-in. Enter the comment then click on the button

to go back to the order.

- 228 -
 Stocks - Purchases

The comment is added to the list of comments, with the name and photo of the user who entered it. It is possible to zoom on
the photo.
Each comment can be unfolded and folded.

A comment entered by another user cannot be modified or deleted.

Order line block

When an order line is created, some fields are initialised based on the header information: work order, cost allocation, asset or
warehouse.

Is used to order and deliver:

- parts
- subcontracting
In multi-organisation mode, the lists take the order entity into account.

For more details on delivery, read the specific section: Order delivery.
Part type lines
Enables one to add listed or unlisted parts to the order: The part or the description are required

n Part: List of choices or selection pop-in (Required). If a part is selected, the description is grey.
n Description: Description of the part selected (grey) or open input if no part is selected. If a description is selected, the
part is grey
n Supplier reference: Text
n Quantity ordered: Positive decimal (Required)
n Unit: List of units (Required). Convertible units with the default unit of the part.
n Unit price excl. tax: Required.
n Amount excl. tax excl. discount: Price (Read only = Quantity * Price)
n Discount (%): Decimal.
n Discount: Price.
n Amount excl. tax: Price. Calculates the total line amount with discount. Amount excl. VAT = (Unit price excl. tax*
Quantity ordered) - Discount
n VAT (%): Rate, decimal. Not required, empty by default, initialized according to process, can be changed until the
order is closed. Drop-down list of rates.
n Amount incl. tax: Calculates the total line amount with discount and with VAT. Amount incl. tax = Amount excl. tax +
(Amount excl. tax *VAT)
n Scheduled delivery date: When the supplier is selected, if there is a Part/Supplier link, the date is initialised taking into
account the Order creation date + Part/Supplier link time
n Last delivery date: Non-modifiable
n Quantity received: Non-modifiable. = Sum of quantities received from different deliveries from the line.
n Warehouse: Selection list.
n Storage location: Selection list. Displays the storage locations of the warehouse selected.
n Cost allocation: WO cost allocation if it is entered.
n Work order: Drop-down list. The list is filtered according to the asset and/or cost allocation entered. When a work
order is selected, the asset and the cost allocation are entered from the work order info. See the section below: Link
between orders and work orders
n Asset: WO asset if it is entered.
n Comment
n Balanced: Yes/No

If a work order, a cost allocation or an asset are entered in the document header then this information will be pre-entered in the
corresponding fields on the part lines.
It is authorised to add parts that are not managed in stock, if the date of their movement is not before the change of the part sta-
tus from “Managed in stock” to “Not managed in stock”.

- 229 -
 Stocks - Purchases

When a part is selected, if the supplier is entered:

- the supplier reference is automatically retrieved from the Part/Supplier link
- The quantity is initialised from the minimum purchase quantity of the Part/Supplier link
- The order unit is initialised from the order unit of the Part/Supplier link
- The unit price is initialised from the unit price of the Part/Supplier link taking into account any conversion in the header cur-
rency

When the supplier has been selected for each part line filled in:
- if the supplier reference is blank, the supplier reference is automatically retrieved from the Part/Supplier link
- if the quantity is below the minimum purchase quantity, the quantity is automatically retrieved from the Part/Supplier link
- if the quantity is below the minimum purchase quantity, the unit is automatically retrieved from the Part/Supplier link
- If the price is 0, the unit price is automatically retrieved from the Part/Supplier link including the currency

Click on the button to perform a delivery on the order line.

For more details on delivery, read the specific section: Order delivery.
An order summary can be viewed in the Orders block on the Part form.

Subcontracting type lines

Used to add subcontractors to the order. When a line is added, if the supplier is entered, its main category and hourly rate are
automatically retrieved.

n Title: Required
n Partner categories: List of categories linked to the partner.
n Supplier reference: Text.
n Scheduled duration: Required.
n Unit price excl. tax: Required -> converted in the supplier’s currency. Retrieves the unit price from the category selec-
ted.
n Currency: Supplier currency, cannot be changed.
n Amount excl. tax excl. discount: Price, cannot be changed.
n Discount (%): Decimal.
n Discount: Discount amount. In the supplier currency.
n Amount excl. tax: Total price with discount. Amount excl. VAT = (Unit price excl. tax* Quantity ordered) - Discount
n VAT (%): Rate, decimal. Not required, empty by default, initialized according to process, can be changed until the
order is closed. Drop-down list of rates.
n Amount incl. tax: Calculates the total line amount with discount and with VAT. Amount incl. tax = Amount excl. tax +
Amount VAT (Amount excl. tax *VAT)
n Actual duration: Cannot be changed, sum of accepted durations of the different deliveries of the line.
n Scheduled delivery date: Open input.
n Last delivery date: Non-modifiable.
n Work order: Drop-down list. The list is filtered according to the asset and/or cost allocation entered. When a work
order is selected, the asset and the cost allocation are entered from the work order info. See the section below: Links
between orders and work orders
n Asset: Selection pop-in.
n Cost allocation: Selection pop-in.
n Comment: Text.
n Balanced: Yes/No

The order creation date is the reference date for the application of conversion rates (conversions into the supplier’s currency
and/or the user’s currency).
For all the price fields, the currency cannot be changed and applies the supplier currency.

- 230 -
 Stocks - Purchases

If a work order, a cost allocation or an asset are entered in the document header then this information will be pre-entered in the
corresponding fields in the subcontracting lines.

Click on the button to perform a delivery on the order line.

For more details on delivery, read the specific section: Order delivery.
An order summary can be viewed in the Order block on the Partners form.

Costs block

Displays a summary of order costs:

n Amount excl. tax excl. general discount: Cannot be changed = sum of the amounts of all the lines.
n General discount (%): Decimal: percentage discount desired on the order total is input.
n General discount: Desired discount amount is input.
n Costs: Amount of fees applicable to the order.
n Total amount: Cannot be changed; calculates the total sum with discount deducted and fees.

Amounts are displayed in the order currency

For the other price type fields (Discount, Fees), the order currency is applied by default, and cannot be changed.

The date the order is created is the reference date for the application of conversion rates.

When the VAT module is enabled, the following fields are added to the previous ones:

n Total amount VAT excl. general discount

n Amount excl. tax after general discount
n Total amount VAT after general discount
n Total amount incl. tax

Associated files block

Files can be linked with the order.

The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Links between orders and work orders

Changing an order from In preparation status to Sent or Processed status (or equivalent statuses)
- For each Part type line with allocation to a work order, a part line is added in the work order resources if the warehouse is ente-
red:

n Part -> Part

n Description -> Description
n Warehouse -> Warehouse
n Date -> Planned delivery date if it is entered otherwise work order start date
n Quantity/Unit -> Quantity/Unit ordered
n Unit price -> Unit price
n Reserved -> Yes

- For each Subcontractor type line with allocation to a work order, a subcontracting line is added to the work order resources if
the category is entered in the order line and the partner is a subcontractor:

- 231 -
 Stocks - Purchases

n Category -> Category

n Subcontractor -> Order supplier
n Start date -> Planned delivery date if it is entered otherwise work order start date
n End date -> Planned delivery date + Duration ordered
n Duration -> Duration ordered
n Subcontractor cost -> Amount

If the supplier is not entered in the order, no subcontracting line is added to the work order.

PURCHASE ORDER: Change of the quantity ordered of a part line allocated to the work order of an order that has already been
sent
The planned quantity of the corresponding work order line is modified, if it still exists

PURCHASE ORDER: Change of the duration ordered of a subcontracting line of an order that has already been sent
The planned duration of the corresponding work order line is modified, if it still exists

PURCHASE ORDER: Delivery of a subcontracting order line allocated to a work order

If the line of the corresponding work order still exists, a completion line is added to this planned work order line:

n Start date -> Delivery date

n End date -> Delivery date + Actual duration delivered
n Duration -> Actual duration delivered
n Subcontractor cost -> (Duration * Order line unit price) - (Duration * Order line unit price * Order line percentage dis-
count)
n Part cost -> Delivery part cost
n Completed -> Balanced

If the corresponding work order line no longer exists, a new line is added:

n Category -> Category

n Subcontractor -> Order supplier
n Start date -> Delivery date
n End date -> Delivery date + Actual duration delivered
n Duration -> Actual duration delivered
n Subcontractor cost -> (Duration * Order line unit price) - (Duration * Order line unit price * Order line percentage dis-
count)
n Part cost -> Delivery part cost
n Completed -> Balanced

WO: Input of a completion line on a subcontracting line from an order in a work order

-> only done when a completion line is created
A delivery line is created on the corresponding subcontracting line in the order:

n Delivery note -> WO code

n Start date -> Start date
n Actual duration delivered -> Duration
n Part cost -> Part cost
n Balanced -> Completed

- 232 -
 Stocks - Purchases

Inventories

List of inventories
This list is available from the [Stocks/Purchases-Inventories] menu. (If the stock module is enabled)
The list displays all the unarchived inventories.

The available actions depend on the user rights and the inventory status. [Settings-User-User profiles]

Creating an inventory

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating an asset, refer to the inventory form.

Deleting an inventory

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

Inventories with Completed or Closed status cannot be deleted.

Archiving/De-archiving an inventory

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the title, indicating that it has been archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

Only cancelled or closed inventories can be archived.

To de-archive, proceed as follows:

- 233 -
 Stocks - Purchases

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating an inventory

To duplicate a team:

n click on the button on the form.

n from the list, click on the button at the end of the line.

Duplication copies the element selected. All the information is duplicated except:

n Code -> field left blank

n Description -> field left blank
n Status (In preparation, In progress, Completed, Closed, Cancelled) -> The status of the new inventory is In preparation

The Inventory block is taken from the original inventory, minus the readings entered by the user.
The new inventory is not archived when the old one is.

Closing an inventory

An inventory can be closed by changing its status to Closed. This action is final.
A closed inventory cannot be changed and can only be viewed.

The stock is updated to correct any discrepancies between the theoretical quantity entered in the CMMS and the quantity read.

Stock movements between the theoretical date and the reading date entered, inclusive, are taken into account. They determine
the quantity used in the recalculation of the stocks.
As regards each part line in the Inventory block, if there is a discrepancy between the quantity reported on MX and the actual
quantity, the requisite movements are made to correct the stock (entry or withdrawal of the discrepant part).
If no discrepancies are observed, no movements are made.

Detail of the movement made

If the quantity obtained is below the quantity read, an entry movement equal to the difference between the two quantities is
made:

n Title: Stock correction on <Inventory code> inventory

n Date: Date reading entered
n Unit price: Current WAUP of the affected warehouse. The LPP is not updated.

If the quantity obtained is above the quantity read, a withdrawal movement equal to the difference between the two quantities
is made:

n Title: Stock correction on <Inventory code> inventory

n Date: Date reading entered
n Unit price: Depends on the stock valuation setting.

- 234 -
 Stocks - Purchases

Under multi-organisation, the movement entity is:

- The entity of the inventory if there is only one of them
- The entity common to the part and the inventory if there is only one of them
- The main entity of the user if it is common to the part and the inventory

Only a user with archiving rights for all the inventory entities can close it.

Printing an inventory
An inventory can be printed by clicking on the button on the list or form.
Printouts follow the screen settings defined for the inventory (fields and blocks hidden or displayed).

These options are defined by user profile under screen settings [Profile form - Screen settings ].

- 235 -
 Stocks - Purchases

Inventory form
Accessible through the [Stocks-Inventories] menu. (If the stocks module is enabled)

The available actions depend on the user rights and the inventory status. [Settings-Users-User profiles].

The inventory settings are configured in the user profiles:

l Menu restriction
l Adding to favourite menus
l Rights levels (viewing, printing, deletion, etc.)

The New, Delete, Archive, Duplicate, Print buttons and other permitted actions (Close) are explained in the List of inventories
actions.

The icons give access to the various forms or to the corresponding repositories. (parts, small reference tables, etc.) so that
information can be viewed or modified during entry.

How the blocks and fields are displayed and the mandatory fields for saving can be configured by user profile. Refer to the sec-
tion Screen settings.

The discrepancy input and withdrawal movements are performed when the inventory is closed. See the section Closing an inven-
tory.

In multi-organisation mode, the lists take the inventory entity into account.

Header block

This block defines the main information of the inventory:

n Code (required)
n Description (required): can be translated into the data languages (with the multi-lingual module)
n Status (In preparation, Completed, Closed, Cancelled) (drop-down list, required).
o Parts can only be added when the status is In preparation.
o Inventory readings are entered when the status is In progress or Completed.
o When the inventory status changes to In progress, it cannot go back to In preparation.
o Any part movement before the date theoretical quantities are taken into account for the statuses "In pro-

gress" or "Done", or on the reading date for the status "Closed", is forbidden.

Changing the status of an inventory to Closed or Cancelled is final. These inventories can no longer be modified.

- 236 -
 Stocks - Purchases

n Creation date (Date/time) (required) -> entered as the current date/time

n Warehouse (required)
n Shared data and Entities (in multi-organisation mode)
n Date the theoretical quantities are taken into account: entered as the date/time the inventory status changes to In pro-
gress (cannot be modified). This date is used to calculate the theoretical quantities that correspond to the actual quan-
tities of parts on the date the inventory status changes (to In progress status).

The status change history of an inventory can be viewed by clicking on the icon in the header block. The pop-in displays the
date, the status and the user for each status change.

The user's main entity is retrieve and the non-archived entities are displayed in the list.
The user must at least have editing rights for inventories (for each entity displayed).

When the inventory is changed, the data is updated:

- the data selected are kept, if it is associated with the new entity
- the data is blank, if it is not associated with the new entity.

Comment block

Comments are displayed in discussion mode in order to have a trace of their history.
Comment are displayed in chronological order, from the most recent to the oldest.

Click on the button to open the comment input pop-in. Enter the comment then click on the button

to go back to the form.

The comment is added to the list of comments, with the name and photo of the user who entered it. It is possible to zoom on
the photo.
Each comment can be unfolded and folded.
A comment entered by another user cannot be modified or deleted.

Inventory block

Used to add and view the parts to inventory:

n Code: Part code

n Description: Part description
n Storage location: Storage location description
n Theoretical quantity: empty. Displays the actual quantity on the date the reading was entered.
n Reading date:
n Quantity read:
n Default unit:
n Manufacturer reference

When a reading date is entered, the theoretical quantity is automatically entered as the actual quantity of the part on the date
the theoretical quantities were taken into account.
This quantity is re-updated when the Date of the reading is changed.

- 237 -
 Stocks - Purchases

Calculating the theoretical quantity

1-calculation of all the movements carried out on the part for the warehouse and storage location in question, between the date
the reading was entered and the current date.
2-The movement quantity is added to each actual quantity of the part in this warehouse for each part withdrawal.
3-The movement quantity is subtracted from each actual quantity of the part in this warehouse for each part entry.
4-The quantity obtained is the theoretical quantity for the line in question.*

n Date of the reading: Date/Time type field

n Quantity read: Decimal type field
n Unit: Displays the default storage unit of the part and the list of convertible units. This unit can be modified by a conver-
tible unit.

Parts can only be added and deleted when the inventory status is In preparation. Readings can be entered when the inventory
status changes to In progress.
The limit is set as 5,000 parts, above which value the following blocking message will be displayed: "The maximum number of
parts per inventory is 5,000. Change your selection filters."

Adding parts to the inventory

Parts can only be added when the inventory status is In preparation.

Click the button to add all the parts in stock in the warehouse selected.

Click on the button to select the parts to inventory according to defined criteria.

The following selection filters are displayed

n Part + Icon (Twins)/selection pop-in

n Parts family + Include children
n Storage locations (Drop-down list) -> Add all the parts associated with this storage location
n Asset + Include children -> Add all the parts in the parts list of this asset
n Manufacturer (Drop-down list) -> Add all the parts associated with this manufacturer
n Supplier (Drop-down list) -> Add all the parts associated with this supplier

Click on the button . All the parts corresponding to the selection that are managed as stock and not archived in
the warehouse which are not already in the inventory are added.

Entering inventory readings

Entries can be made when the inventory status is In progress or Done (quantity and date read). New parts can then no longer be
added and deleted.
The date of the reading is required when a read quantity is entered. It cannot be earlier than the date the theoretical quantities
were incorporated or later than the current day's date.
When a reading date is entered, the theoretical quantity is automatically entered as the actual quantity of the part on the date
the theoretical quantities were taken into account. (see the theoretical quantity calculation above)

In multi-organisation mode, the lists take the inventory entity into account.

Associated files block

Files can be linked to the inventory.

The files are downloaded on the server; the description is optional.

- 238 -
 Stocks - Purchases

The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

- 239 -
 Stocks - Purchases

Parts to restock
List of parts to restock
This list is accessible from the [Stocks/Purchases-Parts to restock] menu.
The list displays all the non-archived parts to restock, sorted in ascending order of the codes. It is also possible to sort by alert sta-

tus (by alert icon ).

This list is a summary of the parts to order.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user rights. [Settings-User-User profile].

Print the list of parts to restock

The list can be printed by clicking the button.
Printouts follow the screen configuration defined for the list of parts to restock (fields and blocks hidden or displayed)

The printout is in landscape format, from the filtered list of parts to restock.

These options are defined by user profile under screen settings [Profile form - Screen settings ].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier reference: Text field. Automatic filter upon entry.
n Warehouse: Multiple choice list.
n Storage location: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Criticality: Selection list.
n Supplier: Selection list.
n Entity: Selection list.
n Shared data: Choices: Yes/No/All

Parts to restock

The table listing the parts to restock has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code: text field. Automatic filter upon entry.

- 240 -
 Stocks - Purchases

n Description: text field. Automatic filter upon entry.

n Unit: part storage unit.
n Warehouse: Description
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity
n Back order: sum of quantities remaining on order lines
n Quantity to be ordered = Maximum stock - Quantity available - Back order

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 241 -
 Stocks - Purchases

Parts to restock
List of parts to restock
This list is accessible from the [Stocks/Purchases-Parts to restock] menu.
The list displays all the non-archived parts to restock, sorted in ascending order of the codes. It is also possible to sort by alert sta-

tus (by alert icon ).

This list is a summary of the parts to order.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user rights. [Settings-User-User profile].

Print the list of parts to restock

The list can be printed by clicking the button.
Printouts follow the screen configuration defined for the list of parts to restock (fields and blocks hidden or displayed)

The printout is in landscape format, from the filtered list of parts to restock.

These options are defined by user profile under screen settings [Profile form - Screen settings ].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier reference: Text field. Automatic filter upon entry.
n Warehouse: Multiple choice list.
n Storage location: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Criticality: Selection list.
n Supplier: Selection list.
n Entity: Selection list.
n Shared data: Choices: Yes/No/All

Parts to restock

The table listing the parts to restock has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code: text field. Automatic filter upon entry.

- 242 -
 Stocks - Purchases

n Description: text field. Automatic filter upon entry.

n Unit: part storage unit.
n Warehouse: Description
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity
n Back order: sum of quantities remaining on order lines
n Quantity to be ordered = Maximum stock - Quantity available - Back order

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 243 -
 Stocks - Purchases

Parts to restock
List of parts to restock
This list is accessible from the [Stocks/Purchases-Parts to restock] menu.
The list displays all the non-archived parts to restock, sorted in ascending order of the codes. It is also possible to sort by alert sta-

tus (by alert icon ).

This list is a summary of the parts to order.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user rights. [Settings-User-User profile].

Print the list of parts to restock

The list can be printed by clicking the button.
Printouts follow the screen configuration defined for the list of parts to restock (fields and blocks hidden or displayed)

The printout is in landscape format, from the filtered list of parts to restock.

These options are defined by user profile under screen settings [Profile form - Screen settings ].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier reference: Text field. Automatic filter upon entry.
n Warehouse: Multiple choice list.
n Storage location: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Criticality: Selection list.
n Supplier: Selection list.
n Entity: Selection list.
n Shared data: Choices: Yes/No/All

Parts to restock

The table listing the parts to restock has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code: text field. Automatic filter upon entry.

- 244 -
 Stocks - Purchases

n Description: text field. Automatic filter upon entry.

n Unit: part storage unit.
n Warehouse: Description
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity
n Back order: sum of quantities remaining on order lines
n Quantity to be ordered = Maximum stock - Quantity available - Back order

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 245 -
 Stocks - Purchases

Parts to restock
List of parts to restock
This list is accessible from the [Stocks/Purchases-Parts to restock] menu.
The list displays all the non-archived parts to restock, sorted in ascending order of the codes. It is also possible to sort by alert sta-

tus (by alert icon ).

This list is a summary of the parts to order.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user rights. [Settings-User-User profile].

Print the list of parts to restock

The list can be printed by clicking the button.
Printouts follow the screen configuration defined for the list of parts to restock (fields and blocks hidden or displayed)

The printout is in landscape format, from the filtered list of parts to restock.

These options are defined by user profile under screen settings [Profile form - Screen settings ].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description: Text field. Automatic filter upon entry.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier reference: Text field. Automatic filter upon entry.
n Warehouse: Multiple choice list.
n Storage location: Selection list.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n Criticality: Selection list.
n Supplier: Selection list.
n Entity: Selection list.
n Shared data: Choices: Yes/No/All

Parts to restock

The table listing the parts to restock has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code: text field. Automatic filter upon entry.

- 246 -
 Stocks - Purchases

n Description: text field. Automatic filter upon entry.

n Unit: part storage unit.
n Warehouse: Description
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity
n Back order: sum of quantities remaining on order lines
n Quantity to be ordered = Maximum stock - Quantity available - Back order

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 247 -
 Resources

Parts

List of parts
The list is accessible through the menu [Resources-Parts].
The list displays all the non-archived parts, sorted in ascending order of the codes. It is also possible to sort by alert status and

corresponding WO end date (by alert icon ).

The available actions depend on the user rights. [Settings-User-User profile].

Creating a part

A part can be created:

n with the button on the list of parts.

n by clicking on the button on the part form.

For further explanation on creating a part, refer to the Parts form.

Selecting a part

A part can be selected in three different ways:

l by ticking the header box on the part line, on the List of parts block

You then have access to the available actions depending on the user rights.

l by performing a search in the Equivalent part input field

This action enables you to add the part after a search filtering its Code and Description.

l by clicking the icon (Twins) on the right of the Equivalent part input field

This action displays a pop-in and enables you to choose the part with one of its tabs:
1. “Multi-criteria” (par default): tick the part line selected
2. “Part family”: unfold the tree to the part selected
Deleting a part

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A part that is cited in a document (PW, WO, equivalent part, inventory, etc.) cannot be deleted.

Archiving/De-archiving a part

- 248 -
 Resources

To archive a part:

n click on the button on the list of parts, or the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the title, indicating that the part is archived.
Archived parts are no longer visible in the drop-down lists or the search fields.

A part can be de-archived:

n click on the button on the list or form.

n From the list of parts, by clicking on the arrow at the end of the line.

The part is no longer archived and is displayed again in the selection lists and search fields.

Printing QR Codes

The button displays the editing of part QR codes, by default in Avery L7160 format.

For an optimal result, when you obtain the print preview, you must download the PDF document and start printing from
Acrobat Reader (direct printing from the preview not recommended because risk of discrepancy).

When the button is clicked on, a PDF document opens and displays all the QR codes of the parts selected in the list.
If no part is selected, the QR codes of the entire list are printed.
It is therefore important to select the lines before printing and to limit the pagination to a maximum of 100 lines.
Under each QR code there is a reminder of the code and description of the part.
The QR code contains (Code+ Description) (Part) on a maximum of 2 lines and 52 characters.

Advanced filters as well as filters on archived or non-archived items are not taken into account for editing.

Parts

List of parts
The list is accessible through the menu [Resources-Parts].
The list displays all the non-archived parts, sorted in ascending order of the codes. It is also possible to sort by alert status and

corresponding WO end date (by alert icon ).

The available actions depend on the user rights. [Settings-User-User profile].

Creating a part

A part can be created:

- 249 -
 Resources

n with the button on the list of parts.

n by clicking on the button on the part form.

For further explanation on creating a part, refer to the Parts form.

Selecting a part

A part can be selected in three different ways:

l by ticking the header box on the part line, on the List of parts block

You then have access to the available actions depending on the user rights.

l by performing a search in the Equivalent part input field

This action enables you to add the part after a search filtering its Code and Description.

l by clicking the icon (Twins) on the right of the Equivalent part input field

This action displays a pop-in and enables you to choose the part with one of its tabs:
1. “Multi-criteria” (par default): tick the part line selected
2. “Part family”: unfold the tree to the part selected
Deleting a part

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A part that is cited in a document (PW, WO, equivalent part, inventory, etc.) cannot be deleted.

Archiving/De-archiving a part

To archive a part:

n click on the button on the list of parts, or the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the title, indicating that the part is archived.
Archived parts are no longer visible in the drop-down lists or the search fields.

A part can be de-archived:

- 250 -
 Resources

n click on the button on the list or form.

n From the list of parts, by clicking on the arrow at the end of the line.

The part is no longer archived and is displayed again in the selection lists and search fields.

Printing QR Codes

The button displays the editing of part QR codes, by default in Avery L7160 format.

For an optimal result, when you obtain the print preview, you must download the PDF document and start printing from
Acrobat Reader (direct printing from the preview not recommended because risk of discrepancy).

When the button is clicked on, a PDF document opens and displays all the QR codes of the parts selected in the list.
If no part is selected, the QR codes of the entire list are printed.
It is therefore important to select the lines before printing and to limit the pagination to a maximum of 100 lines.
Under each QR code there is a reminder of the code and description of the part.
The QR code contains (Code+ Description) (Part) on a maximum of 2 lines and 52 characters.

Advanced filters as well as filters on archived or non-archived items are not taken into account for editing.

- 251 -
 Resources

Parts

Part form
Accessible from the menu [Resources-Parts].

Click the button to access the form being created or the button to view a part.

The available actions depend on the user rights. [Settings-User-User profile].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Parts list.

The icons give access to the various forms or to the corresponding repositories. (Units, Manufacturer reference, Part family,
etc.) making it possible to view or modify information during inputting.

Header block

This block defines the main information of the part.

n Code: Required: the code of a part is unique.

n Description: Required.
n Part family: Required. Part families tree.
n Manufacturer: List of manufacturer partners.
n Manufacturer reference: Text field.
n Default unit: Required. 

The default unit of the part cannot be changed:

n if there is at least one warehouse with a quantity in stock, a reserved quantity or an ordered quantity <> 0.
n If the part is cited in a document (WO, PW, Task, etc.)

n Quantity, Quantity available, Overall WAUP, Last total purchase price: read only, display an overall stock status.

l Overall actual quantity = Sum of the actual quantities of the warehouses in which the part is managed in stock.

l Overall available quantity = Sum of the available quantities of the warehouses in which the part is managed in stock.

l Overall WAUP = Average of the WAUPs of the warehouses in which the part is managed in stock.

- 252 -
 Resources

l Last overall purchase price = Last price entered over all the warehouses in which the part is managed in stock. For parts
not managed in stock, the LPP updates after the last order or the last movement.

n Standard price: Format "Decimal, positive - Currency (logged in user)". Used if the part is not under stock management
in the selected warehouse. Valid for use in WO, grouped WO, withdrawal movement.
n VAT (%): Not required. Selection list from the TDR VAT and relating to the entities of the concerned user.

Comment block

A free comment can be entered.

Stocks block

Used to define the warehouses in which the part is managed in stock.

Displays for each warehouse, whether managed in stock or not, the following information:

n Warehouse: Non-modifiable
n Under stock management: Checkbox to manage the stock in the warehouse

If the box is unchecked when the part is created, a confirmation message is displayed:
“The part is listed as not managed in stock in any of your warehouses.
Part movements prior to creation date do not affect the part stock even after the stock management status is changed (to Under
stock management).
Do you want to confirm part creation?”,
requiring the user’s response (“Yes”/“No”).

If the box is unchecked and if Actual quantity<>0, a blocking message appears: “The part’s actual quantity must be equal to 0”.
If the box is unchecked, Actual quantity=0 and Quantity ordered and Quantity reserved <>0, a validation message appears: “The
quantities ordered and reserve will be reset to 0”.

If the box is unchecked and if Actual quantity< 0, a warning message appears: “Parts have a negative stock. Withdrawal move-
ments are not permitted. Edit the list from the stock analysis”.

The part management history can be viewed by clicking on the icon in the Stocks block. For each status
change (Managed/Not managed in stock), the pop-in displays the Date, the Status and the Username for each status change.

- 253 -
 Resources

n Storage location: List of storage locations, filtered according to the warehouse of the line.
n Storage unit: Required if the part is under stock management in this warehouse
n Actual quantity: Non-modifiable. If negative stock is forbidden in the warehouse, and if the Quantity entered is grea-
ter than the Actual quantity for the part, a blocking message appears: “Negative stock is not allowed in this ware-
house. The entered quantity is greater than the actual part quantity (Actual quantity + Storage unit).”
n Quantity available: Non-modifiable. Actual quantity – reserved quantity
n Quantity ordered: Non-modifiable. The quantities ordered take into account the orders in "Sent" or "Processed" sta-
tus (or equivalent statuses).
n Quantity reserved: Non-modifiable. Quantity reserved in the WOs for this warehouse
n WAUP: Non-modifiable ((ActualQty * WAUP) + (EntryQty * EntryPrice))/(ActualQty + EntryQty)
n LPP: Non-modifiable. Corresponds to the last part purchase price. For parts not managed in stock, the LPP updates
after the last order or the last movement.
n Stock value: Non-modifiable. Actual quantity * WAUP
n Restock point: Must be below the maximum threshold. Does not appear/no longer appears when the part is not/no
longer in stock.
n Minimum stock: Must be below the maximum stock. Does not appear/no longer appears when the part is not/no lon-
ger in stock.
n Maximum stock: Must be above the restock point and minimum stock. Does not appear/no longer appears when the
part is not/no longer in stock.

Inspection rules for restock point, minimum stock and maximum stock (only applied to parts in stock):

Restock point >= Minimum stock

Entering negative values is authorised for the Restock point and Minimum stock.

If entry: Minimum stock > Restock point => Restock point= Minimum stock
If entry: Restock point < Minimum stock, Minimum stock= Restock point
If entry: Maximum stock < Restock point and Maximum stock < Minimum stock => Restock point= Maximum stock and Minimum
stock= Maximum stock
If entry: Restock point > Maximum stock, Maximum stock= Restock point

Restock Alert Triggering:

The restock alert is triggered when:

[Actual quantity - Reserved quantity + Quantity ordered] =< Restock threshold

Furthermore, the change to 'Sent' status or equivalent of a purchase order containing a part on alert for which [Actual quantity -
Quantity reserved + Quantity ordered] > Restock point must update the Restock alert and delete the part from the list.

Asset block

Used to associate assets with the part.

Click the button then select an asset from the tree. Enter the quantity, the unit (unit convertible with the unit

of the part) and any comment. Click the button to validate the input.
Click on the saved line to view or modify the entry.
The part is added automatically to the parts list of the asset.
The Asset field contains both the code and the description, in the format "Code - Description".

- 254 -
 Resources

Suppliers block

Used to associate suppliers for the part. Click on the button and select a supplier in the list of supplier part-
ners.

n Reference: text field.

n Discount (%): percentage discount
n PO unit: List of units convertible with the default unit of the part.
n Unit price: unit price of the part (supplier currency)
n Lead time: expressed in days
n Main: a main supplier is required.
n Minimum purchase quantity: numerical field
n Price validity: date field
n Last update: date field

Click the button to validate the input. Click on the saved line to view or modify the entry.
The link between parts and the partner is made automatically when orders are closed.

Equivalent parts block

Used to define equivalent parts in case of stockout.

Click the button and select an equivalent part in the list of parts (selection list or pop-in). Reciprocity is true if
each of the parts can replace the other.

Click the button to validate the input. Click on the saved line to view or modify the entry.

Photos block

Enables the user to add a panel of photos to the part form. A main photo can be defined, which is then visible in the Header
block of the part form.

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Movements Block

- 255 -
 Resources

Displays the list of movements made for the part in all the warehouses, including those in which the part is not managed in
stock.
The following information can be viewed: Movement date, type (entry, removal, etc.), quantity, unit price, amount, warehouse,
employee.

The movements of inventories carried out when the inventory is closed are also displayed. For more information on these move-
ments, refer to the section Closing an inventory.

Work orders block

Displays all the work orders for which the part is assigned as a resource. The list can be used to view the following information
for each WO: priority, start date ('Day: Hour: Minute" format), code, title, status, type of work, technology.

n Click on the WO line to view additional information: end date ("Day: Hour: Minute" format), issuer, cost allocation.

n Click on the icon to open the WO form in a new tab.

The user must have the appropriate rights to view the item.

Preventive works block

Displays all the PWs for which the part is assigned as a resource.
The list can be used to view the following information for each PW: next occurrence, code, title, type of work.

n Click on the PW line to view additional information: issuer, priority.

n Click on the icon to open the PW form in a new tab.

n Click the filter to select active PWs or not. "Unarchived" value by default. If filter disabled, all
the PWs are displayed.

The user must have the appropriate rights to view the item.

Orders block

Displays the history of part orders.

The list is used to view the following information for each order: Date created, code, title, status, supplier, etc.

n Click on the order line to view additional information

n Click on the icon to open the order form in a new tab.

The user must have the appropriate rights to view the item.

Purchase requests block

Displays the history of part purchase requests.

The list is used to view the following information for each PR: Date created, code, title, status, requester, etc.

n Click on the PR line to view additional information: recipient, etc.

n Click on the icon to open the PR form in a new tab.

- 256 -
 Resources

The user must have the appropriate rights to view the item.

Associated files block

Files can be linked with the part.

The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

- 257 -
 Resources

Parts stocked by warehouse

List of parts stocked by warehouse
The list can be accessed through the menu [Resources - Parts stocked by warehouse] by Supervisor, User and Guest type
accounts.
Only shown if the "Stock" module is enabled.

The list displays all the parts under stock management, sorted in ascending order of the codes. It is also possible to sort by alert

status (by alert icon ).

This list is a summary, warehouse by warehouse (non-archived), of the parts available in stock.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user's "Parts" rights. [Settings-User-User profile].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description/Part: Text field. Automatic filter upon entry.
n Warehouse: (Steven). Multiple choice list of the warehouses of the user's entities. Initialised by default with the ware-
houses of the user's main entity.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer: Drop-down/selection list
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier: Supplier partners typeahead.
n Supplier reference: Text field. Automatic filter upon entry.
n Storage location: Typeahead.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n In ordering: Choices: Yes/No/All. "All" by default. If "Yes", only returns the parts present in an order line of an unar-
chived, non-cancelled order whose "Balanced" box is set to "False".
n Entity: Drop-down/selection list.
n Shared data: Choices: Yes/No/All. "All" by default.
n Archived: Choices: Yes/No/All. "All" by default.

List of parts stocked by warehouse

The table listing the parts stocked by warehouse has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code/Part: Text field. Automatic filter upon entry.

- 258 -
 Resources

n Description/Part: text field. Automatic filter upon entry.

n Code/Warehouse: Text field. Automatic filter upon entry.
n Description/Warehouse: Text field. Automatic filter upon entry.
n Unit: part storage unit.
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 259 -
 Resources

Parts stocked by warehouse

List of parts stocked by warehouse
The list can be accessed through the menu [Resources - Parts stocked by warehouse] by Supervisor, User and Guest type
accounts.
Only shown if the "Stock" module is enabled.

The list displays all the parts under stock management, sorted in ascending order of the codes. It is also possible to sort by alert

status (by alert icon ).

This list is a summary, warehouse by warehouse (non-archived), of the parts available in stock.

A Part form can be accessed by clicking the button at the end of each line of the list.

The available actions depend on the user's "Parts" rights. [Settings-User-User profile].

Advanced filters

This block, which is closed by default, shows the following fields:

n Code/Part: Text field. Automatic filter upon entry.

n Description/Part: Text field. Automatic filter upon entry.
n Warehouse: (Steven). Multiple choice list of the warehouses of the user's entities. Initialised by default with the ware-
houses of the user's main entity.
n Part family: Typeahead and part family standard search window, filtered to the logged-in user's entity/ies. Associated
with: “With children” check box.
n Manufacturer: Drop-down/selection list
n Manufacturer reference: Text field. Automatic filter upon entry.
n Supplier: Supplier partners typeahead.
n Supplier reference: Text field. Automatic filter upon entry.
n Storage location: Typeahead.
n Asset: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.
n In ordering: Choices: Yes/No/All. "All" by default. If "Yes", only returns the parts present in an order line of an unar-
chived, non-cancelled order whose "Balanced" box is set to "False".
n Entity: Drop-down/selection list.
n Shared data: Choices: Yes/No/All. "All" by default.
n Archived: Choices: Yes/No/All. "All" by default.

List of parts stocked by warehouse

The table listing the parts stocked by warehouse has the following columns:

n "Alert" icon: present if part on alert, with sorting possible based on the same principle as WRs and WOs.
n Code/Part: Text field. Automatic filter upon entry.

- 260 -
 Resources

n Description/Part: text field. Automatic filter upon entry.

n Code/Warehouse: Text field. Automatic filter upon entry.
n Description/Warehouse: Text field. Automatic filter upon entry.
n Unit: part storage unit.
n Storage location: Description:
n Main supplier: Description, if defined (otherwise, blank).
n Actual quantity:
n Reserved quantity
n Available quantity
n Ordered quantity

This list displays the list of parts in stock (warehouse/part links), whose restock point is above or equal to (Actual quantity - Reser-
ved quantity + Quantity ordered).
Tooltips giving better legibility are shown on the list columns (from the Storage location column).

- 261 -
Effects

List of effects
The list is accessible through the menu [Resources-Effects].
The list displays all the non-archived effects, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating an effect

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating an effect, refer to the Effects form.

Deleting an effect

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An effect that is cited in another document (WR, WO, etc.) cannot be deleted.

Archiving/De-archiving an effect
To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

- 262 -
 n click on the button on the list or form.

n from the list, by clicking on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating an effect

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the selected effect to a new effect. All the information is duplicated, except the description and the Causes
and Remedies blocks.

Effects

List of effects
The list is accessible through the menu [Resources-Effects].
The list displays all the non-archived effects, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating an effect

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating an effect, refer to the Effects form.

Deleting an effect

To delete a team:

- 263 -
 n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An effect that is cited in another document (WR, WO, etc.) cannot be deleted.

Archiving/De-archiving an effect
To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

n click on the button on the list or form.

n from the list, by clicking on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating an effect

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the selected effect to a new effect. All the information is duplicated, except the description and the Causes
and Remedies blocks.

- 264 -
 Diagnosis

Effects form
Accessible through the menu [Resources-Effects].

Click the button to access the form being created or the button to view an effect.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Effects list.

The icons give access to the various forms or to the corresponding repositories. (Technologies, assets, etc.) thereby make it
possible to view or modify information during inputting.
Header block

Used to enter the description.

Comment block

Used to enter a related comment.

Technologies block

- 265 -
 Diagnosis

Used to define the trade to which the effect is applicable.

Click on the button then select the chosen technologies.

Asset block
Used to link assets with the effect.

Click on the button then select the chosen assets.

Causes block

Used to view the causes that cause this effect most often.
 The list gives all the causes with the number of times when each cause is associated with this effect in the WOs.
The list is sorted by the number of occurrences.

Remedies block

Used to view the remedies that resolve the effect most often.
 The list gives all the remedies with the number of times when each remedy is associated with this effect in the WOs.
The list is sorted by the number of occurrences.

- 266 -
 Diagnosis

Causes

List of causes
The list is accessible through the menu [Resources-Causes].
The list displays all the non-archived causes, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a cause

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating a cause, refer to the Causes form.

Deleting a cause

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An item that is cited in another document (WO, etc.) cannot be deleted.

Archiving/De-archiving a cause

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

- 267 -
 Diagnosis

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a cause

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the selected cause to a new cause. All the information is duplicated, except the description and the Effects
and Remedies blocks.

- 268 -
 Diagnosis

Causes form
Accessible through the menu [Resources-Causes].

Click the button to access the form being created or the button to view a cause.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Cause list.

The icons give access to the various forms or to the corresponding repositories. (Technologies, assets, etc.) thereby make it
possible to view or modify information during inputting.

Header block

Used to enter the description.

Comment block

Used to enter a related comment.

Technologies block
Used to define the trade to which the cause is applicable.

- 269 -
 Diagnosis

Click on the button then select the chosen technologies.

Asset block

Used to link assets with the cause.

Click on the button then select the chosen assets.

Effects block

Used to view the effects most often linked with the cause.
The list gives all the effects with the number of times when each effect is associated with this cause in the WOs.
The list is sorted by the number of occurrences.

Remedies block

Used to view the remedies associated with the cause most often.
 The list gives all the remedies with the number of times when each remedy is associated with this cause in the WOs.
The list is sorted by the number of occurrences.

- 270 -
 Diagnosis

Remedies

List of remedies
The list is accessible through the menu [Resources-Remedies].
The list displays all the non-archived remedies, sorted in ascending order.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a remedy

A model can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating a remedy, refer to the Remedies form.

Deleting a remedy

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

An item that is cited in another document (WO, etc.) cannot be deleted.

Archiving a remedy

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the description, indicating that the item is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

- 271 -
 Diagnosis

n click on the button on the list or form.

n from the list, by clicking on the arrow at the end of the line.

The item is no longer archived and is displayed again in the selection lists and search fields.

Duplicating a remedy

To duplicate a team:

n click on the button on the form.

n from the list, click on the button .

Duplication copies the selected remedy to a new remedy. All the information is duplicated, except the description and the
Effects and Causes blocks.

- 272 -
 Diagnosis

Remedies form
Accessible through the menu [Resources-Remedies].

Click the button to access the form being created or the button to view a remedy.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Remedies list.

The icons give access to the various forms or to the corresponding repositories. (Technologies, assets, etc.) thereby make it
possible to view or modify information during inputting.

Header block

Used to enter the description.

Comment block

Used to enter a related comment.

Technologies block

Used to define the trade to which the remedy is applicable.

Click on the button then select the chosen technologies.

Asset block

Used to link assets with the remedy.

Click on the button then select the chosen assets.

Jobs block

Used to associate jobs with the remedy in order to define the tasks to be completed to remedy the problem.

- 273 -
 Diagnosis

Click on the button then select the necessary jobs.

Effects block

Used to view the effects linked with the remedy most often.
 The list gives all the effects with the number of times when each effect is associated with this remedy in the WOs.
The list is sorted by the number of occurrences.

Causes block

Used to view the causes linked with the remedy most often.
The list gives all the causes with the number of times when each cause is associated with this remedy in the WOs.
The list is sorted by the number of occurrences.

Partners

List of partners
The list is accessible through the menu [Resources-Partners].
The list displays all the non-archived partners, sorted in ascending order of the names.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a partner

A partner can be created:

n with the button on the list of partners.

n click on the button on the partner form.

For further explanation on creating a partner, refer to the Partners form.

Deleting a partner

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A partner that is cited in a document (PW, WO, part, task, etc.) cannot be deleted.

Duplicating a partner

To duplicate a team:

- 274 -
 Diagnosis

n click on the button on the partner form.

n in the list of partners, click on the button .

Duplication copies the selected partner to a new partner. All the information is duplicated, except the name and the asset block.
In the Parts block, the parts are duplicated, but the supplier is not assigned as main supplier.

Archiving a partner

To archive a partner:

n clicking on the button on the list of partners, or the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the name, indicating that the partner is archived.
Archived partners are no longer visible in the drop-down lists or the search fields.

A partner can be de-archived:

n click on the button on the list or form.

n from the list of partners, by clicking on the arrow at the end of the line.

The partner is no longer archived and is displayed again in the selection lists and search fields.

- 275 -
 Resources

Partner form
Accessible through the menu [Resources-Partners].

Click the button to access the form being created or the button to view a partner.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Partners list.

The icons give access to the various forms or to the corresponding repositories. (Categories, assets, etc.) thereby make it
possible to view or modify information during inputting.

Identity block

The identity block defines the main information of the partner.

n Name: Required: the name or company name of the partner

n Code: required and unique
n Web site: web site of the partner.
n Subcontractor: . If the partner is a subcontractor, it may be selected as a resource in the WO, PW, tasks work etc.
n Supplier: If the partner is a supplier, it can be selected as supplier for the parts of the stock.
n Manufacturer 
n Currency: the supplier's currency will be retrieved when an order is created or a part or category is linked, etc.
n Website
n E-mail
n VAT (%): Not required. Selection list from the TDR VAT and relating to the entities of the concerned user.

Comment block

A free comment can be entered.

Conditions block

This block is visible only if the Supplier box of the Identity block is checked.

There are two fields:

- 276 -
 Resources

n Payment terms: Drop-down list

n Term of delivery: Drop-down list

Categories block

Used to associate categories with the partner to indicate its specialisation(s).

Click the button then select a category from the list. Enter the hourly cost and, if appropriate, define the selec-
ted category as the main category.

Only one category may be defined as a main category.

Click the button to validate the input.

Click on the saved line to view or modify the entry.

In the WOs and tasks in the Resources block, the list is filtered to show the partners in the selected category.
When a subcontractor is selected but no category is entered, the main category of the subcontractor is shown by default in the
list.

If the partner is a subcontractor, it must have a main category. The partner categories can be defined through the menu [Set-
tings-Work]

Addresses block

Used to enter the addresses associated with the partner.

Click the button then fill in the fields: Name, Address, Post code, Town, Region, Country, Telephone, Fax,
Main. If at least one address is entered, one address must be defined as the main address.

Click the button to validate the input.

Click on the saved line to view or modify the entry.

Contacts block

Used to enter the contacts associated with the partner.

Click the button then fill in the fields: Position, Mobile, E-mail, Name, First name, Fax, Telephone, Title,
Main. If at least one contact is entered, one contact must be defined as the main contact.

Click the button to validate the input.

Click on the saved line to view or modify the entry.

Associated files block

Files can be linked with the partner.

The files are downloaded on the server; the description is optional.

- 277 -
 Resources

The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Asset block

Used to associate assets supplied by the partner.

 Click the button then select the assets from the tree.

Click the button to validate the input.

Only one supplier permitted per asset. If the selected asset already had a supplier, the supplier is replaced by the partner.

Parts block

Displayed only if the partner is a supplier.

Used to associate parts supplied by the partner.

 Click the button then select the parts from the selection list or pop-in. Fill in the fields:

n Reference: text field.

n Discount (%): percentage discount
n PO unit: List of units convertible with the default unit of the part.
n Unit price: unit price of the part
n Lead time: expressed in days
n Main: a main supplier is required.
n Minimum purchase quantity: numerical field
n Price validity: date field
n Last update: date field

Click the button to validate the input.

Click on the saved line to view or modify the entry.

The link between parts and the partner is made automatically when orders are closed.

Contracts block

Visible if the contracts module is active, this block displays the contracts that are linked to the partner.
In multiple entities, the user sees the contracts associated to the entities to which the user is attached as well as shared
contracts.

Click on the icon to open the form in a new tab.

The user must have the appropriate rights to view the item.

Orders block

Displays the history of orders for which the partner is the order supplier.
The list is used to view the following information for each order: Date created, code, title, status, supplier, etc.

- 278 -
 Resources

n Click on the order line to view additional information: issuer, work order, asset, etc.

n Click on the icon to open the order form in a new tab.

The user must have the appropriate rights to view the item.

Jobs

List of jobs
The list is accessible through the menu [Resources-Jobs].
The list displays all the non-archived jobs, sorted in ascending order of the codes.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a job

A job can be created:

n with the button on the list of jobs.

n by clicking on the button on the job form.

For further explanation on creating a job, refer to the Jobs form.

Deleting a job

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A job that is cited in another document (PW, WO, task, etc.) cannot be deleted.

Duplicating a job

To duplicate a team:

n click on the button on the job form.

n from the list of jobs, click on the button .

Duplication copies the selected job to a new job. All the information is duplicated, except the code and the description.

Archiving/De-archiving a job

- 279 -
 Resources

To archive a job:

n click on the button on the list of jobs or on the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the description, indicating that the job is archived.
Archived jobs are no longer visible in the drop-down lists or the search fields.

To de-archive a job:

n click on the button on the list or form.

n from the list of jobs, click on the arrow at the end of the line.

The job is no longer archived and is displayed again in the selection lists and search fields.

- 280 -
 Resources

Job form
Accessible through the menu [Resources-Jobs].

Click the button to access the form being created or the button to view a job.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Jobs list.

The icons give access to the various forms or to the corresponding repositories. (Tasks, assets, etc.) thereby making it pos-
sible to view or modify information during inputting.

Header block

This block defines the main information of the part.

n Code: Required: the code of a job is unique.

n Description: Required.
n Shared data: Check box

- 281 -
 Resources

n Entities
n Work model: Typeahead. Blank by default. Modifiable

The icon gives access to the Work model form.

Rules for entities:

- do not block the addition of a new entity to the job if the work model does not already have this new entity,
- do not block the deletion of an entity from the work model if it is attached to a job with this entity

Tasks block

Used to associate maintenance tasks with the job, in a specific order in the work.

Click on the button then select a task from the list. Define the order in which the task must be completed
during the work.

Click the button to validate the input.

Click on the saved line to view or modify the entry.
A task can be moved directly in the list by Drag & Drop.

The icon gives access to the Task form.

When changing a job or a task that corresponds to it, any models attached to this job are updated.
This update means that these changes will be taken into account in the WOs triggered later.

Comment block

A free comment can be entered.

Asset block

Used to define the assets to which the job is applied.

Click on the button then select an asset from the tree.

Click the button to validate the input.

Click on the saved line to view or modify the entry.

Summary of resources block

Displays all the resources linked with the job so that the quantity of work necessary to complete the tasks can be viewed quickly.
The list summarises the resources of the tasks making up the job, with the sum of the quantities or times for each resource (non-
modifiable):

- 282 -
 Resources

n Technician times
n Subcontractor times
n Parts quantities
n Downtimes

Associated files block

Files can be linked with the job in order to provide the documents necessary for completion of the work.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Tasks

List of Tasks
The list is accessible through the menu [Resources-Tasks].
The list displays all the non-archived tasks, sorted in ascending order of the codes.

The available actions depend on the user rights. [Settings-Users-User profiles].

Creating a task

A task can be created:

n with the button on the list of tasks.

n by clicking on the button on the tasks form.

For further explanation on creating a task, refer to the Tasks form.

Deleting a task

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

A task that is cited in another document (PW, WO, task, etc.) cannot be deleted.

Duplicating a task

To duplicate a team:

- 283 -
 Resources

n click on the button on the tasks form.

n in the list of tasks, click on the button .

Duplication copies the selected task to a new task. All the information is duplicated, except the description and the jobs block.

Archiving/De-archiving a task

A task can be archived:

n by clicking on the button of the list of tasks, or the form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the description, indicating that the task is archived.
Archived tasks are no longer visible in the drop-down lists or the search fields.

A task can be de-archived:

n click on the button on the list or form.

n from the list of tasks, by clicking on the arrow at the end of the line.

The task is no longer archived and is displayed again in the selection lists and search fields.

- 284 -
 Resources

Task form
Accessible through the menu [Resources-Tasks].

Click on the button to access the form being created or on the button to view a task.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Tasks list.

The icons give access to the various forms or to the corresponding repositories. (Category, technician, partner, part, etc.)
thereby make it possible to view or modify information during inputting.

Header block

n The only entry is the task description.

Comment block

A free comment can be entered.

This comment will be displayed during printing of the WO or Grouped WO including the job associated with the task.

Resources block

Several types of resources may be needed:

Workforce (WF)

Sub-contractor (SC)

Part

Downtime

This screen is used to plan work for each type of resource.

Each resource line can be duplicated by clicking on the Duplicate button at the end of the line.

- 285 -
 Resources

Click on the button then select the chosen type of resource.

The following information is displayed or to be entered:

n For Workforce:
o Technician category: Required
o Duration (required)
o Technician (drop-down list)

n For Subcontracting:
o Subcontractor category: Required.
o Duration: Required.
o Subcontractor: List of subcontracting partners, linked with the category if it is selected.
o Part cost: to be entered. Retrieves the subcontractor currency (can be changed)

n For the Parts:

o Assignment: associates the part with a WF or SC line in the resources.
o Part (for listed part) or description (for non-listed part): Required
o Quantity and unit

n For the Downtimes:

o Assignment: associates the downtime with a WF or SC line in the resources.
o Duration 

When changing a task's resources, any models attached to this task (through a job) are updated.
This update means that these changes will be taken into account in the WOs triggered later.

Jobs block
Displays the list of jobs in which the task is included.
The following information for each job can be viewed from the list: Code, description.

n Click on the line of the job to view the comment.

n Click on the icon to open the job form in a new tab.

Task-job interdependence:

n archiving a task:
o the task can no longer be added to a job
o the task is still present in the jobs to which it had been added

n deletion of a job task:

o the task is no longer present when the job is added to a WO/Grouped WO/PW
o the task is still present on jobs that have already been added to a WO/Grouped WO
o the task is no longer present on jobs that have already been added to non-triggered PW (and in the work

model)

Associated files block

Files can be linked with the task in order to provide the documents necessary for completion of the work.
The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

- 286 -
 Resources

Budgets

Budget list
The list is accessible through the menu [Resources-Budgets].
The list displays all the non-archived budgets, sorted in ascending order of the codes.

The available actions depend on the user rights. [Settings-Users-User profiles].

Create a budget

A budget can be created:

n with the button on the list.

n by clicking on the button on the form.

For further explanation on creating a budget, refer to the Budgets form.

Delete a budget

To delete a team:

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

Duplicate a budget:

To duplicate a team:

n click on the button on the form.

n in the list of budgets, click on the button.

Duplication copies the selected budget to create a new budget.

By default, dates are initialised using the date range that follows on from the duplicated budget.
ex1: Initial budget: - 01/01/2018 to 31/12/2018
=> New budget: - 01/01/2019 to 31/12/2019

ex2: Initial budget: - 01/01/2018 to 31/03/2018

=> New budget: - 01/04/2018 to 30/06/2018

All data (header, comment, detail, files) are duplicated except Code, Dates (new dates entered in the pop-up)

Amounts are initialised upon being saved

- 287 -
 Resources

If the entry is per month, the amounts are reflected in the months that correspond in the new date range

ex1: January 2018 -> January 2019

February 2018 -> February 2019
...

ex2: January 2018 -> April 2018

February 2018 -> May 2018

Archiving/De-archiving a budget

To archive a budget:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the code and the description, indicating that the budget is archived.
Archived budgets are no longer visible in the drop-down lists or the search fields.

A budget can be de-archived:

n click on the button on the list or form.

n from the list of budgets, by clicking on the arrow at the end of the line.

The budget is no longer archived and is displayed again in the selection lists and search fields.

- 288 -
 Resources

Budget form
Accessible through the menu [Resources-Budgets].

Click the button to access the form being created or the button to view a budget.
A budget can be prepared overall or per month, based on the date range, and based on two types of groupings: by cost allo-
cation and type of work.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Budgets list.
The budget entry screen can be configured by user profile using the screen configuration.

Header block

The header block defines the main information of the budget.

n Code (required if no automatic codification); In multi-organisation, for the budgets that are shared, the automatic codi-
fication applied is that of the default entity settings of the user's profile.
n Description
n Start date (required) (current date by default)
n End date (required) (current date by default)

A budget's date range cannot exceed one (1) year: from 1st January to 31st December, from 1st February to 31st January, etc.

n Frequency (Selection: "Overall" or "Per month") (Required, per month by default)

n First grouping level: Drop-down list with the selections "Cost allocation" and "Type of work". The first grouping level
chosen cannot then be selected as the second grouping level.
n Second grouping level: Drop-down list with the selections "Cost allocation" and "Type of work". The second grouping
level chosen cannot be selected as the first grouping level.
n Currency: the user currency is used by default.
n Shared data and entities: in multi-organisation

- 289 -
 Resources

The planned costs are entered in the budget detail block.

Comment block

A free comment can be entered.

Budget detail block

The display depends on the grouping levels selected in the header: none, by type of work, by cost allocation or the two embed-
ded.
The grouping level selection is not mandatory, the budget can be defined without a grouping level.

The budget is entered by clicking on each grouping line.

E.g.
If the budget is defined from 1st January to 31st December, per month and grouped by cost allocation, then an amount will have
to be entered for each cost allocation line and for each month

When at least one amount has been entered, all budget header data, except the description, is no longer modifiable.

In multi-organisation mode, the data displayed have at least one common entity with the budget.

l A new cost allocation automatically appears in the budget tree with amounts initialised at 0.
l Deleting a cost allocation also deletes the budgets.
l Archiving a cost allocation hides it in the budgets. The budgets that are entered are saved.
l When a cost allocation is unarchived, it reappears in the budget tree. Amounts that were already entered are reco-
vered.
l When linking an entity to a cost allocation, in all budgets by cost allocation that now have a common entity, the cost
allocation appears in the budget tree. Amounts are initialised at 0 for this cost allocation
l When an entity is separated from a cost allocation, all amounts entered in the relevant budgets that no longer have a
common entity are deleted.

These rules are identical for the types of work

Associated files block

Files can be linked with the budget.

The files are downloaded on the server; the description is optional.
The size of an attachment is limited to 15 MB; a blocking message will appear if this limit is exceeded.

Users

List of users

The list of users is accessible through the menu [Settings-Users-Users].

The list displays all the non-archived users, sorted in alphabetical order of user names.
Creating a user

From the button on the list of users or the button on the user form.
For further explanation on creating a user, refer to the User form.

- 290 -
 Resources

Deleting a user

To delete a team:

n click on the button on the form or list of users.

n from the list of users, click on the arrow at the end of the line of the user to be deleted

The user cannot be deleted if it is being used (issuer of or technician in a WO, issuer of or technician in a PW, issuer of a WR, tech-
nician on a task).

Duplicating a user

To duplicate a team:

n click on the button on the user form.

n from the list of users, click on the button at the end of the line.

Duplication copies the selected user to a new user, reproducing certain information:

o Photo
o Account type
o Language
o Type (internal/external)
o Partner
o User profile
o E-mail
o Time zone

Information not reproduced by the duplication:

o Name
o First name
o Identifier
o Password

Archiving/De-archiving a user

A user can be archived:

n by clicking on the button on the list of users or the user form.

n From the list of users, by clicking on the arrow at the end of the line.

The icon is displayed to the left of the user name/first name, indicating that the user is archived.

- 291 -
 Resources

Archived users are still visible for the work in which they have been involved. However, they can no longer be selected in the drop-
down selection lists (technician, issuer, requester, etc.). They no longer appear in the search fields.

Logging in with an archived user is not allowed.

A user can be de-archived:

n by clicking on the button on the list of users or the user form.

n from the list of users, by clicking on the arrow at the end of the line.

The user is no longer archived and is displayed again in the selection lists and search fields.

Advanced filters

This block, which is closed by default, shows the following fields:

n Name: Text field. Automatic filter upon entry.

n First name: Text field. Automatic filter upon entry.
n User name: Text field. Automatic filter upon entry.
n User profile: Typeahead and standard profile search window, filtered to the logged-in user’s entity/ies. Associated
with: "Twins" icon and with: “With children” check box.
n Account type: Selection list.
n Type: Internal/External/All. "All" by default.
n Language: Selection list.
n Requester: Yes/No/All. "All" by default.
n Technician: Yes/No/All. "All" by default.
n Subcontractor category: Selection list.
n Entity: Selection list.
n Display language: Selection list.
n DIMO Maint MX access: Yes/No/All. "All" by default.
n Dimo Maint App access: Yes/No/All. "All" by default.
n Phone: Text field. Automatic filter upon entry.

List of users

This block, which is always unfolded, has the following columns:

n Name: Text field. Automatic filter upon entry.

n First name: Text field. Automatic filter upon entry.
n User name: Text field. Automatic filter upon entry.
n User profile: Typeahead. Automatic filter upon entry.
n Account type: Selection list. Automatic filter upon entry.

- 292 -
 Users

User form

Accessible from the list of users, [Settings-Users-Users] menu, with the buttons or .

The New, Delete, Archive and Duplicate buttons are explained in the actions of the users list.

n Refresh: Updates the form with the changes made.

n Change password: enables the password to be changed. The entry form records:

o Current password
o New password
o Confirmation of the new password, which must be identical to the previous field.

n Reset password: enables the user to define a new password if the current password is lost. Entry of the current pass-
word is not requested.
n Unfold: Unfolds all the blocks of the form
n Fold: Folds all the blocks of the form

Identity block

The identity block is used to view or enter all the personal information of the user:

n Name: entry field (required).

n First name: entry field (required).
n Identifier: entry field (required): the identifier of a user is unique.
n Account type: selection list (required). The account type is retrieved from the user profile. It can be changed. In this
case the user must select a user profile corresponding to the selected account type. The types of account are detailed
in the user profiles – Header block

- 293 -
 Users

n Language: list of languages available for displaying the application's descriptions. The application is translated into the
following languages: English, Spanish, German, Italian, Dutch, Portuguese, Vietnamese and Russian. All the des-
criptions may also be adapted and customised with the creation of one or more customised languages (See the Cus-
tomised languages section).
n Type: radio buttons (required): internal by default. If the user type is external, a partner can be selected in the dis-
played list.

The user profile must have rights over the partners.

n Partner: selection list visible only if the user type is “External”.

n User profile: selection list (required). Only the profiles corresponding to the selected account type are displayed. If no
account type is selected, all the profiles are included in the drop-down selection list.
n E-mail: entry field.
n Telephone: Text type input field.
n Time zone: selection list (required). By default, the zone defined in the general settings.
n Display language: Displayed if the multi-languages module is enabled. Used to display the application data in the lan-
guage selected. The list retrieves the data languages configured in the general settings.
n Currency: required. By default, the currency in the general settings. The prices and amounts will be displayed in the
user's currency, with the decimals taken into account if defined.
n Separation character for CSV exports: When exporting CSV from a list, this character is used to delimit fields.
n Dimomaint MX access: checkbox. Right to access and log on to the Web application.
n Dimomaint App access: checkbox. Right to access and log on to the mobile application.
n Service account: checkbox. Unchecked by default. To be checked when an account is created that will only be used as
part of the Webservices (via the swagger). The account is not counted in the number of licenses and is not subject to
the rules for checking the password validity.

Details on creating a service account

* If the account exists and the Service Account box is checked, the user's original password is verified. If the password is too
weak, a blocking message will be displayed: "Please reset the user's password".
* If the Service Account box is checked and the access boxes for MX and/or DMA are also checked, a blocking message indicates
that a service account cannot connect to DimoMaint MX/App. In this case, the access boxes for MX and/or DMA must be unche-
cked.
* A service account inherits the rights of the account type entered in its form. These rights therefore apply to the Webservices.

The following settings are visible only for Supervisor accounts:

n Profile management: allows user profiles to be created, modified and deleted. The menus [Settings-Users-User pro-
files and Profile tree structure] are displayed only if the user is a profiles manager.
n User management: allows users to be created, modified and deleted. The menu [Settings-Users-Users] is displayed
only if the user is a user manager. A supervisor who does not manage users may only change the language and time
zone.

There must be at least one supervisor who manages users and one supervisor who manages profiles (per entity if multi-entity
mode is enabled).

Password block

Block visible only when a new user is being created. This block is masked during routine viewing of a user form.

- 294 -
 Users

n New password: entry field (required).

n Password confirmation: entry field (required)

The entry must be identical to the new password field.

Changing and resetting the password are subject to a strength indicator.

See how to manage it in General settings.

Photos block

This block is used to add one or more photos to a user form. When a photo is defined as “main”, a thumbnail of the photo is dis-
played in the header of the user form.
The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Entity block

This block is used to associate entities with users. It is visible only if multi-organisation mode is enabled:

View the form on the multi-organisation module for further information.

Time block

This block defines a user's hours if they have the role of Technician in at least one of their entities.

n Day: Drop-down list of days of the week ordered based on the user's location (required initialised on 1st day of the
drop-down list)
n Start time: Time (required, initialised at 00:00)
n End time: Time (required, initialised at 00:00)

An end time entry = 00:00 is midnight.

To enter a full day: Start time = 00:00 and End time = 00:00.
Two date ranges cannot overlap

The list of times is sorted by default by day of the week, then by start time.

This block has "Add" and "Delete" buttons.

You can change the data when you select an hour line.

User profiles

List of user profiles

The list is accessible through the menu [Settings-Users-User profiles].
The list displays all the non-archived user profiles, sorted in ascending order of user profile codes.

Creating a profile

A profile can be created:

- 295 -
 Users

n with the button on the list of profiles or on the tree

view.

n by clicking on the button on the profile form.

For further explanation on creating a profile, refer to the profile form.

Deleting a profile

To delete a team:

n click on the button on the form or list of profiles.

n from the list of profiles, click on the arrow at the end of the line.

A profile assigned to a user, or a profile that has a child profile assigned to a user, cannot be deleted.

Various cases may be encountered:

n Deletion of a parent profile, not assigned to a user, with no child profiles -> Deletes the profile.
n Deletion of a parent profile, not assigned to a user, with child profiles assigned to a user -> Does not delete the
parent profile or the child profiles.
n Deletion of a parent profile, not assigned to a user, with child profiles not assigned to a user -> Deletes the parent pro-
file and the child profiles.
n Deletion of a parent profile, assigned to a user, with no child profiles -> Does not delete the profile.
n Deletion of a parent profile, assigned to a user, with child profiles -> Does not delete the parent profile or the child
profiles.

Duplicating a profile
To duplicate a team:

n click on the button on the profile form.

n from the list of profiles, click on the button at the end of the line.

Duplication copies the selected profile to a new profile, reproducing all the information except:

n Code
n Description

Archiving/De-archiving a profile
A profile can be archived:

n by clicking on the button on the list of profiles, the profile form or the profile tree.

n From the list of profiles, by clicking on the arrow at the end of the line.

- 296 -
 Users

The icon is displayed to the left of the code and the profile name, indicating that the profile is archived.
Archived profiles are no longer visible in the drop-down lists of profiles, the search fields or the profile tree.

A profile can be de-archived:

n by clicking on the button on the list of profiles or the profile form.

n From the list of profiles, by clicking on the arrow at the end of the line.

The profile is no longer archived and is displayed again in the selection lists, search fields and profile tree.

Moving a profile
A profile can be moved:

n by changing its parent asset in the profile form,

n by drag & drop in the profile tree.

When the profile is moved, a message automatically prompts the inheritance of the settings of the new parent profile.

A confirmation message is displayed to confirm the move.

Several cases may be encountered:

n movement of a profile with no child profiles: moves the profile to its new location, updates the parent profile,
n movement of a profile with child profiles: moves the whole branch, parent profile + child profiles, to the new loca-
tion, updates the parent profile.

- 297 -
 Users

User profile form

The user profiles are accessible through the menu [Settings-Users-User profiles] or [Settings-Users-Profile tree].

The user settings are defined in the user profile form. The user inherits the attributes that have been defined in his or her profile.

The New, Delete, Archive, and Duplicate buttons are explained in the actions of the User profiles list

Screen configuration

The button enables you to customise the application forms (Asset, WR, WO) by displaying or
hiding certain blocks or certain fields, by requiring an input, or on the other hand, by making it impossible to change other items.

Screen configuration applied from the profile form is specific to the user profiles and will be applied for all the profile users.
A more general default configuration is possible from general settings [Settings-Configuration].

Profiles may retrieve the default configuration of the different files by clicking on the button

For more details, see the Screen configuration section.

Duplicating the configuration

The button enables one to copy all or part of the configuration from a user profile to other pro-
files, in the chosen entities.

- 298 -
 Users

The user selects the configuration sections to be duplicated: Restrictions menus, favourite menus, roles by entity, codification by
entity etc.
S/he then determines the profiles and entities for which the configuration must be duplicated and confirms the selection.
The profile list only displays profiles with the same account type as the duplicated profile. (Requester, user, supervisor or guest).

For each user profile user, the following information can be defined:

n account type (user, supervisor, guest, etc.)

n menu restrictions
n home page widgets
n Favourite menus.
n entity settings

o roles (requester, technician, closing of WOs, WRs, etc.)

o Notifications (WO alerts, WR, Stock, contract etc.)
o profile categories (mechanic, etc.)
o types of contract (with the subcontractor contracts module)
o automatic codification
o rights for each object

n Shared-data rights (in multi-entity mode)

The configuration of each block is detailed in the paragraphs below.

Header block

Displays the general information of a user profile:

n Code: required entry field: the code of a user profile is unique.

n Name: required entry field.
n Parent profile: selection list.

When a profile is assigned to a parent profile, a message is displayed prompting inheritance of all the parent profile settings. In
this way, the whole branch of lower-level profiles receives the characteristics of the selected parent profile. (Refer to the profile
tree here)

n Account types: selection list (required).

There are 4 account types that can be assigned to a user profile.

- 299 -
 Users

n Supervisor
n Requester
n User
n Guest

The settings are different according to the account type linked with the profile.

SUPERVISOR USER REQUESTER GUEST

Menus The supervisor can see The user can see all the The requester does not The guest can see all the
the whole menu. menus except the Set- see any menu. menus except the Set-
Only Supervisor account tings menus They only see WR crea- tings and Stock/Part
types have access to the tion in the favourites movementmenus
Settingsmenu menu
Rights over entities All the possible rights - Maximum reading - Maximum editing - Maximum editing
levels across all the rights for the objects rights for WRs rights for WRs
objects (WR, WO, PW, PW, Diagnosis, Job, - Editing and viewing - Maximum reading
repositories, resources, Asset, Part, Partner, rights for PRs rights for the other
etc.) Contract, Movements - No rights for the other objects (WOs, Orders,
and Budgets objects or repositories PWs, PRs, Inventories,
- Maximum editing Movements, Budgets,
rights for the objects etc.)
Inventories, Work - No rights for repo-
orders, Orders, PRs and sitories
WRs
- No rights for repo-
sitories
Roles (Requester, tech- All possible roles All possible roles Only "Requester" pos- Only "Requester" pos-
nician, reopening WOs, sible sible
WRs, etc.)
Favourite menus All possible favourites Some favourites menus Possible to create WRs Some favourites menus
are not accessible: and PRs are not configurable:
- Settings - "Purchase requests" - Settings
- Analyses - Stock
My WR info widget The supervisor sees the The user sees the 3 fil- Viewing two filters: Viewing two filters:
3 filters ters - All WRs - All WRs
- All WRs - All WRs - WRs for which I am - WRs for which I am the
- WRs for which I am - WRs for which I am the requester requester
the requester the requester
- WRs for which I am - WRs for which I am
the recipient the recipient
Unassigned work wid- The supervisor can see The user can only see Inaccessible Inaccessible
get all work (not only work work from categories to
in the categories to which he belongs.
which he belongs)
Rights to shared data All possible rights - Maximum document No possible right for - Maximum document
reading rights shared data reading rights
- no rights for repo- - No rights for repo-
sitories sitories

- 300 -
 Users

If the profile is assigned to a user, the account type can no longer be changed.
The menus displayed also depend on the modules that are enabled in the company form (diagnoses, stock, etc.).

Menu restrictions block

The settings for display of the various menus can be defined by user profile.
The menu restrictions can be different according to the account type selected in the header. (See Header Block). If the account
type does not enable certain menus, they do not appear in the menu tree.

 The sub-menus are unfolded. Click on the arrow to fold the sub-
menus.
Click on the arrow to unfold the sub-menus

 All the menus and sub-menus are restricted

Some sub-menus are restricted and other sub-menus are unres-

tricted

All the menus and sub-menus are enabled

The menus displayed also depend on the modules that are enabled in the company form (diagnoses, stock, etc.) and on the type
of user account.
My widgets block

The widgets are visual items that can be displayed on the user's home page:

n Tree
n Work request
n My WR info
n My schedule
n My favourite menus
n Unassigned work
n WO Info
n My delayed WR alerts
n My delayed WO alerts
n My stock alerts (if the stock module is enabled)
n Purchase request (if the Orders module is enabled)
n My PR info (if the Orders module is enabled)

- 301 -
 Users

Adding a widget to the home screen

Click the button , select the display order that you want on the home screen (see paragraph below to define
an order) and select the Widget in the list of available Widgets. Entry of the order is not required. If the order is not entered, it is
calculated automatically according to the previous menu.

Then click one of the buttons to confirm or cancel the entry.

Ordering the widgets on the home screen

The order in which the widgets appear on the home screen can be defined.

The order of the widgets can be changed, moving them on the screen by Drag & Drop.

The order defined in the settings is displayed as below on the home screen:

The order alternates left/right for the display of the following widgets.

If the user enters an order that is already used, the system shifts the widget automatically when saving it.
To view the detailed information on each Widget, refer to the Home screen paragraph (See Home)

- 302 -
 Users

My favourite menus block

The My favourite menus screen defines the favourite menus for a user profile.
The favourite menus can then be added to the user’s home screen with the widget settings accessible in the menu [Settings-
Users-User profiles-My widgets] (See My widgets block)

The order of the widgets can be changed, moving them on this screen by Drag & Drop.

Adding a favourite menu

Click the button .The order entered corresponds to the display order on the home screen. It is filled in auto-
matically, but can be changed manually (refer to the paragraph below for defining an order).
Select the favourite menu that you want in the list of available menus.
The menus displayed depend on the modules that are enabled in the company form (diagnoses, stock, etc.) and on the type of
user account.

Select a colour in the proposed palette.

Then click one of the buttons to confirm or cancel the entry.

You may add as many favourite menus as there are in the drop-down selection list.

Ordering the favourite menus

The order in which the widgets appear on the home screen can be defined. The order is subsequently displayed on the home
screen as shown below:

- 303 -
 Users

Sixteen favourite menus are displayed here, but others can be added; the order of the next menus follows this example.

Deletion of a favourite menu recalculates the display order automatically. The next menu in the order takes the place of the dele-
ted menu, and all the menus are shifted in this way.
Entity settings

This block displays the list of non-archived entities.

Clicking the button enables you to access the configuration details for each entity.

For more specific details on configuration by entity, see the module multi-organisation form.

Default entity configuration

The button is visible only if the multi-organisation module is enabled. It initialises profiles
with these settings when a new entity is created.
--> for all profiles (depending on the type of account), the configurations of roles, notifications, categories, contract types, codi-
fications and rights are automatically filled in for the new entity from the default data.

Duplicating an entity's configuration

The button is visible only if the multi-organisation module is enabled. It enables

one to copy part or all of the configurations from one entity to other profile entities.

- 304 -
 Users

The user selects the original entity from which the configuration must be duplicated.
It then determines the configuration sections to be duplicated: Roles, codifications, rights etc. then the entities to which he
wishes to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

Role block

The Role block defines the roles in a user profile:

n Requester: Enables the user to request WRs

n Technician: Enables the user to be added to the resources of a task, a PW or a WO as technician.
n WO closing: Enables closing of a WO. Only users that have this role can view a WO and select “Closed” status in it.
n WO reopening: Enables reopening of a WO.
n WR reopening: Enables reopening of a WR.

The WO closing, WO reopening and WR reopening roles are enabled only for the Supervisor and User account types.
The technician role is not enabled for the Requester and Guest account types.

Notifications

This section allows you to configure the notifications (or alerts) that appear, as well as the e-mails that are sent for the profile on
each entity.
The following alerts can be added:

l WO alert delayed
l WR alert delayed
l Restock alert (if the stock module is enabled)
l Contract due alert (if the contract module is enabled)
l Open WOs for which I am the issuer
l Open WOs for which I am the technician

For further information on the different notifications, see the specific documentation on Alerts

Category block

Several technician categories can be added to a given profile. In such cases, definition of a main category is required.

The hourly cost of a technician category may be different according to the user profile.
The technician category settings can be defined in the menu [Settings-Work].

Types of contract managed

- 305 -
 Users

This block is displayed if the contracts module is enabled and only for "Supervisor" type accounts. It defines the contract types
that are managed by user profiles (and by entity in multi-entity mode)
In the contract form, only types of contracts managed by the contract manager may be selected.

Rights block

The rights block is used to specify the rights level for each object according to the user profile.
The rights levels can be different according to the account type selected in the header. (See Header Block)

n Deletion: highest right level. Enables deletion, archiving, creation, modification and viewing.
n Archiving: enables archiving, creation, modification and viewing. Deletion is not enabled.
n Editing: enables item viewing, modification and creation.
n Association (not present for all objects): enables the allocation of an item in shared data to the entity configured
n Viewing: enables only viewing of an item.
n None: lowest right level. No rights granted on the item.

The rights are defined on the following objects:

n Asset
n Diagnosis (Effect + Cause + Remedy) -> (if the diagnosis module is activated)
n Job (Job + Task)
n Part
n Preventive work (trigger + preventive work)
n Partner
n Work order
n Work request
n Contract (if the contract module is enabled)
n Purchase request (if the order module is enabled)
n Order (if the order module is enabled)
n General repository: Settings-General
n Maintenance repository: Settings-Assets and Settings-Work
n Models repository: Work - Models - Work models
n Stock repository: Settings-Stock
n Inventories (If the stock module is enabled)
n Movements (if the stock module is enabled) This right only affects direct movement creation, not automatic move-
ment generation from, for example, a WO.
n Budgets (if the budget module is enabled)

Codifications block

Automatic codification can be activated on WRs, PWs, WOs, budgets (if the budgets module is enabled), orders and purchase
requests and its settings defined (if the order module is enabled).
The user does not have to enter the code of the item manually. Saving the form generates a unique, non-modifiable code auto-
matically.

The following settings are available:

n Prefix: used to select a prefix for the meter: Day, Week, Month or Year.
n Letters: any
n Meter: numerical required
n Minimum length of the meter: Defines the number of characters of the meter

- 306 -
 Users

n Padding character: If the code does not reach the minimum length of the meter, the length is made up by adding a
padding character, repeated as many times as necessary, between the prefix+letter(s) and the meter.

E.g. 2BT00001, where 2 is the prefix, WO are the letters, 1 is the meter and 0 is the padding character (repeated as necessary), if
the minimum length of the meter entered is 5.

Shared data rights block

This block is visible only if multi-organisation mode is enabled. It defines the profile's level of rights over shared data.
The maximum rights levels authorised depend on the profile account type.
Requesters have no rights over shared data
Guests:
- Document reading rights
- No rights for repositories
The users :
- document reading rights
- No rights for repositories
Supervisors have all the rights to shared data.

See the form on the multi-organisation module for further information.

- 307 -
 Users

Profile tree structure

The profile tree is accessible through the menu [Settings-Users-Profile tree].

The Create profile and Create child profile buttons are explained in the paragraphs Creating a profile to De-archiving a profile.

Principle
The use of tree structures facilitates the definition of the user profile settings.
The user views the different tree levels and can distinguish easily between parent profiles and child profiles.

The child profile is located under the parent profile; consequently, if the user so chooses, it can receive all the settings from the
level above. It can also have its own configuration and inherit only part of the characteristics of its parent profile.

Actions available

Select a profile then click on the button to display the list of users attached to this profile.

Various actions are also available through the pop-up menu opened by right-click on a profile:

The Create profile and Create child profile actions are explained in the paragraph Creating a profile

- 308 -
 Users

Searching for a profile

The search field is used to find a profile quickly in the tree.

The results display lists the profiles with a code or description that contains the entered character(s).
The target profile is highlighted in the tree.

The search is not case-sensitive (upper/lower case) or accent-sensitive.

Moving a profile (Drag & Drop)

Profiles can be moved on this screen by Drag & Drop.
For further information on moving profiles, refer to the section Moving a profile.

- 309 -
 Settings

Configuration

Company
Accessible through the menu [Settings-Configuration]
The Company form is used to enter the general information about the company: address, telephone, region, country, NAF code
(French business sector code), SIRET No. (French company facility identification code), VAT No., etc.

- if mono-organisation mode is enabled, the button enables access to the entity configuration.

- if multi-organisation mode is enabled, the button is displayed and gives access to the list and to confi-
guration of the different entities.

See the form on the multi-organisation module for further information.

Opening hours block

This block defines the company's opening hours and is used to pre-configure the technicians' hours.

n Day (Drop-down list of days of the week ordered based on the user location)
n Start time
n End time

An end time entry of 00:00 is midnight

To enter an entire day: start time 00:00 and end time 00:00
Two date ranges cannot overlap

It is possible to duplicate a company or an entity's opening hours to the opening hours of one or more entities.
This duplication enables you to avoid re-entering the hours for the entity and to overwrite any initial hours for the entity
(with a "Duplicate" button that is accessible when the hours are saved).

The opening hours have an impact on the WO start and end time initialisations.

In multi-organisation mode, when creating a new entity, times are automatically entered using those of the company.

Licence Block

The licence block displays the summary of the licences for the application.

n Expiry date 
n Disk space allowed
n Number of entities
n Number of supervisor licences and number remaining 
n Number of user licences and number remaining
n Number of guest licences and number remaining
n Number of requester licences and number remaining

Photos block

- 310 -
 Settings

Enables the user to add a panel of photos to the company form. A main photo can be defined, which is then visible in the print
settings (according to the PDF printing configuration).

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Module Block

This block displays the activation status of modules in the application

Modules that have been enabled by the licence key are checked by default. It is possible to disable/re-enable them.
Those that have not been enabled by the licence key cannot be enabled without the licence being updated.
For any additional information concerning module and licence management, our sales department is at your disposal.

Stock module

Used for managing stocks and parts in warehouse.

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block: "Parts", "Stock repository" and “Inventories” lines added the "Acti-
- Menu block: "Stock/Purchase", "Resources\Parts", "Settings\Stock" and "Parts movements" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Part creation", "Part family", "Storage column are
location", "Warehouse", "Parts movements", "Parts", “Inventories, Movements, etc.” not visible.

Asset form: Parts List block displayed. The module

PW form: Part type added to the resource addition. cannot be
WO form: Part type added to the resource addition. disabled if:
Task form: Part type added to the resource addition. - parts are
Partner form: Parts block displayed. being used
Order form: Part type added for order lines
in PWs,
tasks or
orders that
are still
open.
- the multi-
warehouse
module is
enabled.

Subcontractor module:

- 311 -
 Settings

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Menu block: No mandatory restrictions for "Settings\Works\Partner category". the "Acti-
- Favourite menus block: Displayed in the list of suggested menus: "Partner category" vation" column
are not visible.
- PW form: Subcontractor added to the resource addition.
- WO form: Subcontractor added to the resource addition. The module
- Task form: Subcontractor added to the resource addition. cannot be disa-
- Partner form: Subcontractor checkbox added. bled if sub-
Categories block added. contracting
- User form: Choice between "internal" and "external" displayed.
lines are ente-
- Order form: Subcontracting type added for order lines
red in PWs,
tasks or work
orders that are
still open.

Disabling the
module will
update all the
users to "Inter-
nal".
Jobs module

ENABLE DISABLE
1. Profile form (for all profiles): The items in
Right block: Jobs line added. the "Acti-
Menu block: Authorisation possible for "Resources/Jobs", "Resources\Tasks" (no mandatory restrictions on the vation"
menu). column are
Favourites Menu Block: are displayed in the list of menus suggested: "Job creation", "Task creation", "Jobs", not visible.
"Tasks"
The module
2. PW form cannot be
Job block displayed. disabled if
jobs are
3/ WO form being used
Job block displayed.
in PWs,
remedies or
4. Remedy form
work orders
Job block displayed.
that are still
open.
Multi-warehouse module

Used to manage stocks across several warehouses

ENABLE DISABLE
Warehouse database table: More than one warehouse may be created. Only one
warehouse
may be crea-
ted.

- 312 -
 Settings

May not be
disabled if
there is
more than
one ware-
house.

Multi-time zone module

ENABLE DISABLE
- Time zone displayed in the asset form. Disabling the
- Time zone displayed in the user form. module will
- Time zone column displayed in the Warehouse reference table. update all
assets, users
and ware-
houses to
the time
zone in the
general set-
tings.

If the multi-
time zone
module is
not enabled,
changing the
time zone in
the general
settings will
update all
the assets,
users and
warehouses.

Multi-lingual module

Application data translation

ENABLE DISABLE
- "Languages used" displayed in the general settings. Used to select the languages used within the organisation so If the
that data may be translated accordingly. Languages that are being used by users cannot be deleted when the multi-lin-
multi-lingual module is enabled. gual
- "Data display language" displayed in the user form and the user banner. The date will then be displayed in the module is
language of the user. disabled,
- Translation menu displayed for translation into bulk data (Settings-utility programs) the data
display lan-
guage for
all users is
that confi-
gured in

- 313 -
 Settings

the general
settings.

Subcontractor Contracts module

ENABLE DISABLE
- "Contracts" menu displayed in the "Assets" menu The items in
- "Contract types" reference table added in "Settings-Assets" the "Acti-
- Contract types managed in the profile-configuration form added by entity vation"
- In rights and shared data rights, configuration of rights to contracts column are
- Possibility of activating contract alerts - notifications in the user profile not visible.
- Contracts Alerts Widget added in the user profile
- User profile: Contracts added in menu restrictions and favourite menus Deactivation
- Asset form/Contracts block is impossible
- Partner form/Contracts block if there are
- WO form/Contract field
non-ter-
minated
contracts or
if there are
non-can-
celled or
non-closed
orders asso-
ciated with a
contract.

Orders module

ENABLE DISABLE
- "Purchase requests" and "Orders" menus displayed in the "Stocks/Purchases" menu The items in
- User profile: Purchase requests and orders displayed in menu restrictions and favourites menus. PR and order the "Acti-
status administration displayed. vation"
Settings/Stocks/Terms of delivery, PR status and order status menu displayed column are
- Rights: configuration of rights on purchase requests and orders not visible.
- Automatic codification of PRs and orders
- General settings and configuration by entity: Default recipient of the PRs
- Configurations and settings by entity: PR and order status administration
- Export of PR lines in Imports/exports
- Part form: PR block and orders block
- Partner form: Orders block

Reading Management module

Used to manage asset meter readings

ENABLE DISABLE
- Asset form: Meters block added The
- Trigger form: Periodic Meter and Aperiodic Meter trigger types added module
cannot be

- 314 -
 Settings

disabled:
- if some
assets have
meters
- if there
are meter
type trig-
gers.

If it is disa-
bled, it is
impossible
to:
- de-
archive a
"Meter rea-
ding" type
task
- de-
archive a
job with
"Meter rea-
ding" type
tasks
- reopen
WOs with
jobs with
"Meter rea-
ding" type
tasks
- de-
archive a
PW or a
work
model with
a job with
"Meter rea-
ding" type
tasks
- de-
archive a
periodic or
aperiodic
meter trig-
ger
- reopen a
grouped
WO with
child WOs
with jobs
that use

- 315 -
 Settings

"Meter rea-
ding" type
tasks
Diagnostics module

Used to manage effects, causes and remedies in the work items.

ENABLE DISABLE
If the Diagnostics module is enabled:
- Profile form/Restriction menus: Effects, causes and remedies added
- Profile form/Favourite menus: Following favourite menus added: Creation of effects, causes and remedies as well
as access to the Effects, Causes and Remedies menus.
- Profile form/configuration by entity: Rights added to diagnoses.
- WR form: "Effect" area added
- WO form: Diagnoses added

Budgets module

Operating budgets management

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block and shared data rights block: "Budgets" line added the "Acti-
- Menu block: "Resources/budgets" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Creation of budget", "Budgets" column are
not visible.

Additional Fields module

Used to manage additional asset fields.

ENABLE DISABLE
Settings->Configuration->Additional fields menu displayed Authorisations
Profile form/Favourites menus and menu restrictions: management of additional fields on additional
Configuration of additional fields in screen configuration fields are disa-
Additional fields displayed in the asset form bled and invi-
sible

Grouped work module

Used to manage grouped work on a number of assets.

ENABLE DISABLE
Used to display the Work/Grouped Work orders menu Grouped WO
Profile form, option of adding the grouped work orders and Create grouped WOs in the favourites menu authorisations
(depending on account type) are disabled.
Grouped work order form added to the screen settings
Filter on grouped WOs added to the list of WOs.
Grouped WO block added to the PW form

- 316 -
 Settings

User timetables module

Technician timetable management

ENABLE DISABLE
Schedule/Timetable menu displayed The
Time slot types displayed in the Settings/General menu menus
Timetable imports and time slot types displayed in the list of imports are disa-
Profile form, option of adding Timetable and Time slot type menus in the favourites menu (depending on account bled.
type)

Tree partioning module

Selection of the partitioning mode, according to the Users assigned and the Assets authorised, for Supervisor accounts.

ENABLE DISABLE
Settings/Configuration menu displayed The
Blocks: "Identity", "Authorised assets", "Users assigned". menus
Possibility of changing the type of partition, and changing the partitioning level. are disa-
bled.

Measurements module

Management of measurements [linked in WOs and assets], for Supervisor accounts.

ENABLE DISABLE
Display of the following menus: Work/Measurements; Settings/General/Measurement type The menus are
Blocks: "Assets", "Work orders", "Value range". disabled,
except if the fol-
Measurements block added to the Asset and Work Order forms lowing are
Creation of "Measurement reading" type Tasks. present:
"Measurement reading" type Tasks added to Job forms. - non-archived
"Measurement
reading" type
task
- non-archived
job using an
archived mea-
surement rea-
ding task or not
- unclosed (and
non-cancelled)
WO using an
archived job or
not, with an
archived mea-
surement rea-
ding task or not
- non-archived

- 317 -
 Settings

PW using an
archived job or
not, with an
archived mea-
surement rea-
ding task or not
- non-archived
work model
using an archi-
ved job or not,
with an archi-
ved mea-
surement
reading task or
not

Impossible to:
- de-archive a
"Measurement
reading" type
tasks
- reopen WOs
with jobs with
"Measurement
reading" type
tasks
- de-archive a
job with "Mea-
surement rea-
ding" type tasks
- de-archive a
PW with a job
with "Mea-
surement rea-
ding" type tasks
- de-archive a
work model
with a job with
"Measurement
reading" type
tasks

Re-enabling the
module after it
has been disa-
bled leaves old
"Measurement
reading" type
tasks archived.

UBleam module

- 318 -
 Settings

Access to a menu in DMA whose selection is displayed in augmented reality

ENABLE DISABLE
The following menu is displayed: Home/ Ubleam --> "Asset" form, "WR creation (Asset)" form The
Direct access by asset scan to the menu: "Asset" form, "WR creation (Asset)" form menus
are disa-
bled.

MX Analytics module

Analysis management.

ENABLE DISABLE
The following menu is displayed: Analyses/ MX Analytics The
"MX Analytics" block on the "Analyses Settings" page. menus
"MX Analytics" menu in the "Menu restrictions" block on the "User Profile" page. are disa-
bled.

PW Prioritisation Module

Priority preventive work management.

ENABLE DISABLE
The following menu is displayed: Work/Priority preventive work Grouped prio-
Profile form: possibility of adding the Priority preventive work and Priority preventive work creation menus rity PW autho-
(only for Supervisor accounts) in the My favourite menus block, and the Priority preventive work choice in the risations are
Menu restrictions block (if Supervisor, User or Guest accounts) disabled.

TVA Module

VAT management for Supervisor accounts.

ENABLE DISABLE
The following menu is displayed: Settings/General/VAT Price dis-
Profile Form: possibility of adding the VAT menu (only for Supervisor accounts) in the My favourite menus block, plays
and the VAT choice in the Menu restrictions block. with VAT
are disa-
Display of VAT in the "Part" and "Subcontractor" order lines ("Order Lines" block) and the "Costs" block of the Order bled.
form.
VAT initialization process (automatic information) when creating a command line or transforming a WR into an
order.

Configuration

Company
Accessible through the menu [Settings-Configuration]

- 319 -
 Settings

The Company form is used to enter the general information about the company: address, telephone, region, country, NAF code
(French business sector code), SIRET No. (French company facility identification code), VAT No., etc.

- if mono-organisation mode is enabled, the button enables access to the entity configuration.

- if multi-organisation mode is enabled, the button is displayed and gives access to the list and to confi-
guration of the different entities.

See the form on the multi-organisation module for further information.

Opening hours block

This block defines the company's opening hours and is used to pre-configure the technicians' hours.

n Day (Drop-down list of days of the week ordered based on the user location)
n Start time
n End time

An end time entry of 00:00 is midnight

To enter an entire day: start time 00:00 and end time 00:00
Two date ranges cannot overlap

It is possible to duplicate a company or an entity's opening hours to the opening hours of one or more entities.
This duplication enables you to avoid re-entering the hours for the entity and to overwrite any initial hours for the entity
(with a "Duplicate" button that is accessible when the hours are saved).

The opening hours have an impact on the WO start and end time initialisations.

In multi-organisation mode, when creating a new entity, times are automatically entered using those of the company.

Licence Block

The licence block displays the summary of the licences for the application.

n Expiry date 
n Disk space allowed
n Number of entities
n Number of supervisor licences and number remaining 
n Number of user licences and number remaining
n Number of guest licences and number remaining
n Number of requester licences and number remaining

Photos block

Enables the user to add a panel of photos to the company form. A main photo can be defined, which is then visible in the print
settings (according to the PDF printing configuration).

- 320 -
 Settings

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Module Block

This block displays the activation status of modules in the application

Modules that have been enabled by the licence key are checked by default. It is possible to disable/re-enable them.
Those that have not been enabled by the licence key cannot be enabled without the licence being updated.
For any additional information concerning module and licence management, our sales department is at your disposal.

Stock module

Used for managing stocks and parts in warehouse.

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block: "Parts", "Stock repository" and “Inventories” lines added the "Acti-
- Menu block: "Stock/Purchase", "Resources\Parts", "Settings\Stock" and "Parts movements" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Part creation", "Part family", "Storage column are
location", "Warehouse", "Parts movements", "Parts", “Inventories, Movements, etc.” not visible.

Asset form: Parts List block displayed. The module

PW form: Part type added to the resource addition. cannot be
WO form: Part type added to the resource addition. disabled if:
Task form: Part type added to the resource addition. - parts are
Partner form: Parts block displayed. being used
Order form: Part type added for order lines
in PWs,
tasks or
orders that
are still
open.
- the multi-
warehouse
module is
enabled.

Subcontractor module:

ENABLE DISABLE
- Profile form (for all profiles): The items in

- 321 -
 Settings

- Menu block: No mandatory restrictions for "Settings\Works\Partner category". the "Acti-

- Favourite menus block: Displayed in the list of suggested menus: "Partner category" vation" column
are not visible.
- PW form: Subcontractor added to the resource addition.
- WO form: Subcontractor added to the resource addition. The module
- Task form: Subcontractor added to the resource addition. cannot be disa-
- Partner form: Subcontractor checkbox added. bled if sub-
Categories block added. contracting
- User form: Choice between "internal" and "external" displayed. lines are ente-
- Order form: Subcontracting type added for order lines
red in PWs,
tasks or work
orders that are
still open.

Disabling the
module will
update all the
users to "Inter-
nal".
Jobs module

ENABLE DISABLE
1. Profile form (for all profiles): The items in
Right block: Jobs line added. the "Acti-
Menu block: Authorisation possible for "Resources/Jobs", "Resources\Tasks" (no mandatory restrictions on the vation"
menu). column are
Favourites Menu Block: are displayed in the list of menus suggested: "Job creation", "Task creation", "Jobs", not visible.
"Tasks"
The module
2. PW form cannot be
Job block displayed. disabled if
jobs are
3/ WO form being used
Job block displayed.
in PWs,
remedies or
4. Remedy form
work orders
Job block displayed.
that are still
open.
Multi-warehouse module

Used to manage stocks across several warehouses

ENABLE DISABLE
Warehouse database table: More than one warehouse may be created. Only one
warehouse
may be crea-
ted.
May not be
disabled if
there is

- 322 -
 Settings

more than
one ware-
house.

Multi-time zone module

ENABLE DISABLE
- Time zone displayed in the asset form. Disabling the
- Time zone displayed in the user form. module will
- Time zone column displayed in the Warehouse reference table. update all
assets, users
and ware-
houses to
the time
zone in the
general set-
tings.

If the multi-
time zone
module is
not enabled,
changing the
time zone in
the general
settings will
update all
the assets,
users and
warehouses.

Multi-lingual module

Application data translation

ENABLE DISABLE
- "Languages used" displayed in the general settings. Used to select the languages used within the organisation so If the
that data may be translated accordingly. Languages that are being used by users cannot be deleted when the multi-lin-
multi-lingual module is enabled. gual
- "Data display language" displayed in the user form and the user banner. The date will then be displayed in the module is
language of the user. disabled,
- Translation menu displayed for translation into bulk data (Settings-utility programs) the data
display lan-
guage for
all users is
that confi-
gured in
the general
settings.

- 323 -
 Settings

Subcontractor Contracts module

ENABLE DISABLE
- "Contracts" menu displayed in the "Assets" menu The items in
- "Contract types" reference table added in "Settings-Assets" the "Acti-
- Contract types managed in the profile-configuration form added by entity vation"
- In rights and shared data rights, configuration of rights to contracts column are
- Possibility of activating contract alerts - notifications in the user profile not visible.
- Contracts Alerts Widget added in the user profile
- User profile: Contracts added in menu restrictions and favourite menus Deactivation
- Asset form/Contracts block is impossible
- Partner form/Contracts block if there are
- WO form/Contract field
non-ter-
minated
contracts or
if there are
non-can-
celled or
non-closed
orders asso-
ciated with a
contract.

Orders module

ENABLE DISABLE
- "Purchase requests" and "Orders" menus displayed in the "Stocks/Purchases" menu The items in
- User profile: Purchase requests and orders displayed in menu restrictions and favourites menus. PR and order the "Acti-
status administration displayed. vation"
Settings/Stocks/Terms of delivery, PR status and order status menu displayed column are
- Rights: configuration of rights on purchase requests and orders not visible.
- Automatic codification of PRs and orders
- General settings and configuration by entity: Default recipient of the PRs
- Configurations and settings by entity: PR and order status administration
- Export of PR lines in Imports/exports
- Part form: PR block and orders block
- Partner form: Orders block

Reading Management module

Used to manage asset meter readings

ENABLE DISABLE
- Asset form: Meters block added The
- Trigger form: Periodic Meter and Aperiodic Meter trigger types added module
cannot be
disabled:
- if some
assets have
meters

- 324 -
 Settings

- if there
are meter
type trig-
gers.

If it is disa-
bled, it is
impossible
to:
- de-
archive a
"Meter rea-
ding" type
task
- de-
archive a
job with
"Meter rea-
ding" type
tasks
- reopen
WOs with
jobs with
"Meter rea-
ding" type
tasks
- de-
archive a
PW or a
work
model with
a job with
"Meter rea-
ding" type
tasks
- de-
archive a
periodic or
aperiodic
meter trig-
ger
- reopen a
grouped
WO with
child WOs
with jobs
that use
"Meter rea-
ding" type
tasks
Diagnostics module

- 325 -
 Settings

Used to manage effects, causes and remedies in the work items.

ENABLE DISABLE
If the Diagnostics module is enabled:
- Profile form/Restriction menus: Effects, causes and remedies added
- Profile form/Favourite menus: Following favourite menus added: Creation of effects, causes and remedies as well
as access to the Effects, Causes and Remedies menus.
- Profile form/configuration by entity: Rights added to diagnoses.
- WR form: "Effect" area added
- WO form: Diagnoses added

Budgets module

Operating budgets management

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block and shared data rights block: "Budgets" line added the "Acti-
- Menu block: "Resources/budgets" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Creation of budget", "Budgets" column are
not visible.

Additional Fields module

Used to manage additional asset fields.

ENABLE DISABLE
Settings->Configuration->Additional fields menu displayed Authorisations
Profile form/Favourites menus and menu restrictions: management of additional fields on additional
Configuration of additional fields in screen configuration fields are disa-
Additional fields displayed in the asset form bled and invi-
sible

Grouped work module

Used to manage grouped work on a number of assets.

ENABLE DISABLE
Used to display the Work/Grouped Work orders menu Grouped WO
Profile form, option of adding the grouped work orders and Create grouped WOs in the favourites menu authorisations
(depending on account type) are disabled.
Grouped work order form added to the screen settings
Filter on grouped WOs added to the list of WOs.
Grouped WO block added to the PW form

User timetables module

Technician timetable management

- 326 -
 Settings

ENABLE DISABLE
Schedule/Timetable menu displayed The
Time slot types displayed in the Settings/General menu menus
Timetable imports and time slot types displayed in the list of imports are disa-
Profile form, option of adding Timetable and Time slot type menus in the favourites menu (depending on account bled.
type)

Tree partioning module

Selection of the partitioning mode, according to the Users assigned and the Assets authorised, for Supervisor accounts.

ENABLE DISABLE
Settings/Configuration menu displayed The
Blocks: "Identity", "Authorised assets", "Users assigned". menus
Possibility of changing the type of partition, and changing the partitioning level. are disa-
bled.

Measurements module

Management of measurements [linked in WOs and assets], for Supervisor accounts.

ENABLE DISABLE
Display of the following menus: Work/Measurements; Settings/General/Measurement type The menus are
Blocks: "Assets", "Work orders", "Value range". disabled,
except if the fol-
Measurements block added to the Asset and Work Order forms lowing are
Creation of "Measurement reading" type Tasks. present:
"Measurement reading" type Tasks added to Job forms. - non-archived
"Measurement
reading" type
task
- non-archived
job using an
archived mea-
surement rea-
ding task or not
- unclosed (and
non-cancelled)
WO using an
archived job or
not, with an
archived mea-
surement rea-
ding task or not
- non-archived
PW using an
archived job or
not, with an
archived mea-

- 327 -
 Settings

surement rea-
ding task or not
- non-archived
work model
using an archi-
ved job or not,
with an archi-
ved mea-
surement
reading task or
not

Impossible to:
- de-archive a
"Measurement
reading" type
tasks
- reopen WOs
with jobs with
"Measurement
reading" type
tasks
- de-archive a
job with "Mea-
surement rea-
ding" type tasks
- de-archive a
PW with a job
with "Mea-
surement rea-
ding" type tasks
- de-archive a
work model
with a job with
"Measurement
reading" type
tasks

Re-enabling the
module after it
has been disa-
bled leaves old
"Measurement
reading" type
tasks archived.

UBleam module

Access to a menu in DMA whose selection is displayed in augmented reality

ENABLE DISABLE

- 328 -
 Settings

The following menu is displayed: Home/ Ubleam --> "Asset" form, "WR creation (Asset)" form The
Direct access by asset scan to the menu: "Asset" form, "WR creation (Asset)" form menus
are disa-
bled.

MX Analytics module

Analysis management.

ENABLE DISABLE
The following menu is displayed: Analyses/ MX Analytics The
"MX Analytics" block on the "Analyses Settings" page. menus
"MX Analytics" menu in the "Menu restrictions" block on the "User Profile" page. are disa-
bled.

PW Prioritisation Module

Priority preventive work management.

ENABLE DISABLE
The following menu is displayed: Work/Priority preventive work Grouped prio-
Profile form: possibility of adding the Priority preventive work and Priority preventive work creation menus rity PW autho-
(only for Supervisor accounts) in the My favourite menus block, and the Priority preventive work choice in the risations are
Menu restrictions block (if Supervisor, User or Guest accounts) disabled.

TVA Module

VAT management for Supervisor accounts.

ENABLE DISABLE
The following menu is displayed: Settings/General/VAT Price dis-
Profile Form: possibility of adding the VAT menu (only for Supervisor accounts) in the My favourite menus block, plays
and the VAT choice in the Menu restrictions block. with VAT
are disa-
Display of VAT in the "Part" and "Subcontractor" order lines ("Order Lines" block) and the "Costs" block of the Order bled.
form.
VAT initialization process (automatic information) when creating a command line or transforming a WR into an
order.

Configuration

Company
Accessible through the menu [Settings-Configuration]
The Company form is used to enter the general information about the company: address, telephone, region, country, NAF code
(French business sector code), SIRET No. (French company facility identification code), VAT No., etc.

- 329 -
 Settings

- if mono-organisation mode is enabled, the button enables access to the entity configuration.

- if multi-organisation mode is enabled, the button is displayed and gives access to the list and to confi-
guration of the different entities.

See the form on the multi-organisation module for further information.

Opening hours block

This block defines the company's opening hours and is used to pre-configure the technicians' hours.

n Day (Drop-down list of days of the week ordered based on the user location)
n Start time
n End time

An end time entry of 00:00 is midnight

To enter an entire day: start time 00:00 and end time 00:00
Two date ranges cannot overlap

It is possible to duplicate a company or an entity's opening hours to the opening hours of one or more entities.
This duplication enables you to avoid re-entering the hours for the entity and to overwrite any initial hours for the entity
(with a "Duplicate" button that is accessible when the hours are saved).

The opening hours have an impact on the WO start and end time initialisations.

In multi-organisation mode, when creating a new entity, times are automatically entered using those of the company.

Licence Block

The licence block displays the summary of the licences for the application.

n Expiry date 
n Disk space allowed
n Number of entities
n Number of supervisor licences and number remaining 
n Number of user licences and number remaining
n Number of guest licences and number remaining
n Number of requester licences and number remaining

Photos block

Enables the user to add a panel of photos to the company form. A main photo can be defined, which is then visible in the print
settings (according to the PDF printing configuration).

- 330 -
 Settings

The photo size is limited to 15 MB; a blocking message will appear if this limit is exceeded.
Only files with photo formats are permitted: bmp, gif, jfif, jpeg, jpg, png, tiff, and HEIC.

Module Block

This block displays the activation status of modules in the application

Modules that have been enabled by the licence key are checked by default. It is possible to disable/re-enable them.
Those that have not been enabled by the licence key cannot be enabled without the licence being updated.
For any additional information concerning module and licence management, our sales department is at your disposal.

Stock module

Used for managing stocks and parts in warehouse.

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block: "Parts", "Stock repository" and “Inventories” lines added the "Acti-
- Menu block: "Stock/Purchase", "Resources\Parts", "Settings\Stock" and "Parts movements" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Part creation", "Part family", "Storage column are
location", "Warehouse", "Parts movements", "Parts", “Inventories, Movements, etc.” not visible.

Asset form: Parts List block displayed. The module

PW form: Part type added to the resource addition. cannot be
WO form: Part type added to the resource addition. disabled if:
Task form: Part type added to the resource addition. - parts are
Partner form: Parts block displayed. being used
Order form: Part type added for order lines
in PWs,
tasks or
orders that
are still
open.
- the multi-
warehouse
module is
enabled.

Subcontractor module:

ENABLE DISABLE
- Profile form (for all profiles): The items in

- 331 -
 Settings

- Menu block: No mandatory restrictions for "Settings\Works\Partner category". the "Acti-

- Favourite menus block: Displayed in the list of suggested menus: "Partner category" vation" column
are not visible.
- PW form: Subcontractor added to the resource addition.
- WO form: Subcontractor added to the resource addition. The module
- Task form: Subcontractor added to the resource addition. cannot be disa-
- Partner form: Subcontractor checkbox added. bled if sub-
Categories block added. contracting
- User form: Choice between "internal" and "external" displayed. lines are ente-
- Order form: Subcontracting type added for order lines
red in PWs,
tasks or work
orders that are
still open.

Disabling the
module will
update all the
users to "Inter-
nal".
Jobs module

ENABLE DISABLE
1. Profile form (for all profiles): The items in
Right block: Jobs line added. the "Acti-
Menu block: Authorisation possible for "Resources/Jobs", "Resources\Tasks" (no mandatory restrictions on the vation"
menu). column are
Favourites Menu Block: are displayed in the list of menus suggested: "Job creation", "Task creation", "Jobs", not visible.
"Tasks"
The module
2. PW form cannot be
Job block displayed. disabled if
jobs are
3/ WO form being used
Job block displayed.
in PWs,
remedies or
4. Remedy form
work orders
Job block displayed.
that are still
open.
Multi-warehouse module

Used to manage stocks across several warehouses

ENABLE DISABLE
Warehouse database table: More than one warehouse may be created. Only one
warehouse
may be crea-
ted.
May not be
disabled if
there is

- 332 -
 Settings

more than
one ware-
house.

Multi-time zone module

ENABLE DISABLE
- Time zone displayed in the asset form. Disabling the
- Time zone displayed in the user form. module will
- Time zone column displayed in the Warehouse reference table. update all
assets, users
and ware-
houses to
the time
zone in the
general set-
tings.

If the multi-
time zone
module is
not enabled,
changing the
time zone in
the general
settings will
update all
the assets,
users and
warehouses.

Multi-lingual module

Application data translation

ENABLE DISABLE
- "Languages used" displayed in the general settings. Used to select the languages used within the organisation so If the
that data may be translated accordingly. Languages that are being used by users cannot be deleted when the multi-lin-
multi-lingual module is enabled. gual
- "Data display language" displayed in the user form and the user banner. The date will then be displayed in the module is
language of the user. disabled,
- Translation menu displayed for translation into bulk data (Settings-utility programs) the data
display lan-
guage for
all users is
that confi-
gured in
the general
settings.

- 333 -
 Settings

Subcontractor Contracts module

ENABLE DISABLE
- "Contracts" menu displayed in the "Assets" menu The items in
- "Contract types" reference table added in "Settings-Assets" the "Acti-
- Contract types managed in the profile-configuration form added by entity vation"
- In rights and shared data rights, configuration of rights to contracts column are
- Possibility of activating contract alerts - notifications in the user profile not visible.
- Contracts Alerts Widget added in the user profile
- User profile: Contracts added in menu restrictions and favourite menus Deactivation
- Asset form/Contracts block is impossible
- Partner form/Contracts block if there are
- WO form/Contract field
non-ter-
minated
contracts or
if there are
non-can-
celled or
non-closed
orders asso-
ciated with a
contract.

Orders module

ENABLE DISABLE
- "Purchase requests" and "Orders" menus displayed in the "Stocks/Purchases" menu The items in
- User profile: Purchase requests and orders displayed in menu restrictions and favourites menus. PR and order the "Acti-
status administration displayed. vation"
Settings/Stocks/Terms of delivery, PR status and order status menu displayed column are
- Rights: configuration of rights on purchase requests and orders not visible.
- Automatic codification of PRs and orders
- General settings and configuration by entity: Default recipient of the PRs
- Configurations and settings by entity: PR and order status administration
- Export of PR lines in Imports/exports
- Part form: PR block and orders block
- Partner form: Orders block

Reading Management module

Used to manage asset meter readings

ENABLE DISABLE
- Asset form: Meters block added The
- Trigger form: Periodic Meter and Aperiodic Meter trigger types added module
cannot be
disabled:
- if some
assets have
meters

- 334 -
 Settings

- if there
are meter
type trig-
gers.

If it is disa-
bled, it is
impossible
to:
- de-
archive a
"Meter rea-
ding" type
task
- de-
archive a
job with
"Meter rea-
ding" type
tasks
- reopen
WOs with
jobs with
"Meter rea-
ding" type
tasks
- de-
archive a
PW or a
work
model with
a job with
"Meter rea-
ding" type
tasks
- de-
archive a
periodic or
aperiodic
meter trig-
ger
- reopen a
grouped
WO with
child WOs
with jobs
that use
"Meter rea-
ding" type
tasks
Diagnostics module

- 335 -
 Settings

Used to manage effects, causes and remedies in the work items.

ENABLE DISABLE
If the Diagnostics module is enabled:
- Profile form/Restriction menus: Effects, causes and remedies added
- Profile form/Favourite menus: Following favourite menus added: Creation of effects, causes and remedies as well
as access to the Effects, Causes and Remedies menus.
- Profile form/configuration by entity: Rights added to diagnoses.
- WR form: "Effect" area added
- WO form: Diagnoses added

Budgets module

Operating budgets management

ENABLE DISABLE
- Profile form (for all profiles): The items in
- Right block and shared data rights block: "Budgets" line added the "Acti-
- Menu block: "Resources/budgets" menus displayed vation"
- Favourites Menu Block: are displayed in the list of menus suggested: "Creation of budget", "Budgets" column are
not visible.

Additional Fields module

Used to manage additional asset fields.

ENABLE DISABLE
Settings->Configuration->Additional fields menu displayed Authorisations
Profile form/Favourites menus and menu restrictions: management of additional fields on additional
Configuration of additional fields in screen configuration fields are disa-
Additional fields displayed in the asset form bled and invi-
sible

Grouped work module

Used to manage grouped work on a number of assets.

ENABLE DISABLE
Used to display the Work/Grouped Work orders menu Grouped WO
Profile form, option of adding the grouped work orders and Create grouped WOs in the favourites menu authorisations
(depending on account type) are disabled.
Grouped work order form added to the screen settings
Filter on grouped WOs added to the list of WOs.
Grouped WO block added to the PW form

User timetables module

Technician timetable management

- 336 -
 Settings

ENABLE DISABLE
Schedule/Timetable menu displayed The
Time slot types displayed in the Settings/General menu menus
Timetable imports and time slot types displayed in the list of imports are disa-
Profile form, option of adding Timetable and Time slot type menus in the favourites menu (depending on account bled.
type)

Tree partioning module

Selection of the partitioning mode, according to the Users assigned and the Assets authorised, for Supervisor accounts.

ENABLE DISABLE
Settings/Configuration menu displayed The
Blocks: "Identity", "Authorised assets", "Users assigned". menus
Possibility of changing the type of partition, and changing the partitioning level. are disa-
bled.

Measurements module

Management of measurements [linked in WOs and assets], for Supervisor accounts.

ENABLE DISABLE
Display of the following menus: Work/Measurements; Settings/General/Measurement type The menus are
Blocks: "Assets", "Work orders", "Value range". disabled,
except if the fol-
Measurements block added to the Asset and Work Order forms lowing are
Creation of "Measurement reading" type Tasks. present:
"Measurement reading" type Tasks added to Job forms. - non-archived
"Measurement
reading" type
task
- non-archived
job using an
archived mea-
surement rea-
ding task or not
- unclosed (and
non-cancelled)
WO using an
archived job or
not, with an
archived mea-
surement rea-
ding task or not
- non-archived
PW using an
archived job or
not, with an
archived mea-

- 337 -
 Settings

surement rea-
ding task or not
- non-archived
work model
using an archi-
ved job or not,
with an archi-
ved mea-
surement
reading task or
not

Impossible to:
- de-archive a
"Measurement
reading" type
tasks
- reopen WOs
with jobs with
"Measurement
reading" type
tasks
- de-archive a
job with "Mea-
surement rea-
ding" type tasks
- de-archive a
PW with a job
with "Mea-
surement rea-
ding" type tasks
- de-archive a
work model
with a job with
"Measurement
reading" type
tasks

Re-enabling the
module after it
has been disa-
bled leaves old
"Measurement
reading" type
tasks archived.

UBleam module

Access to a menu in DMA whose selection is displayed in augmented reality

ENABLE DISABLE

- 338 -
 Settings

The following menu is displayed: Home/ Ubleam --> "Asset" form, "WR creation (Asset)" form The
Direct access by asset scan to the menu: "Asset" form, "WR creation (Asset)" form menus
are disa-
bled.

MX Analytics module

Analysis management.

ENABLE DISABLE
The following menu is displayed: Analyses/ MX Analytics The
"MX Analytics" block on the "Analyses Settings" page. menus
"MX Analytics" menu in the "Menu restrictions" block on the "User Profile" page. are disa-
bled.

PW Prioritisation Module

Priority preventive work management.

ENABLE DISABLE
The following menu is displayed: Work/Priority preventive work Grouped prio-
Profile form: possibility of adding the Priority preventive work and Priority preventive work creation menus rity PW autho-
(only for Supervisor accounts) in the My favourite menus block, and the Priority preventive work choice in the risations are
Menu restrictions block (if Supervisor, User or Guest accounts) disabled.

TVA Module

VAT management for Supervisor accounts.

ENABLE DISABLE
The following menu is displayed: Settings/General/VAT Price dis-
Profile Form: possibility of adding the VAT menu (only for Supervisor accounts) in the My favourite menus block, plays
and the VAT choice in the Menu restrictions block. with VAT
are disa-
Display of VAT in the "Part" and "Subcontractor" order lines ("Order Lines" block) and the "Costs" block of the Order bled.
form.
VAT initialization process (automatic information) when creating a command line or transforming a WR into an
order.

General settings
Accessible through the menu [Settings-Configuration].

From R16, the page is displayed in blocks.

Screen configuration

- 339 -
 Settings

The button enables you to customise the application forms (Asset, WR, WO) by displaying or
hiding certain blocks or certain fields, by requiring an input, or on the other hand, by making it impossible to change other items.

The screen configuration created from the general settings is a default configuration for the different forms.

This default configuration may then be quickly assigned to a selection of user profiles by clicking on the button

Specific configuration can be applied for each user profile directly from the profile form.

For more details, see the Screen configuration section.

Configuration of PDF printing

In the screen configuration form, the button is used to customise printing of the appli-
cation’s forms (Asset, WR or WO) by displaying or hiding certain information (company logo, addresses, client or technician signa-
ture boxes, etc.)

Specific configuration can be applied for each user profile directly from the profile form.

For more details, see the Screen configuration section.

Duplicating the configuration

The button copies part or all of the general settings of this screen to the target entities.

The user selects the configuration sections to be duplicated: Main warehouse, default WR recipient, default PR recipient, PW
trigger time, Days of the week without PW triggering, Asset statuses without PW triggering... then the entities for which he
would like to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.
If a data item is not compatible with the target entity, the previous value is not overwritten.

This action can also be performed from the general settings of each entity. It enables one to duplicate the configuration from a
specific entity to one or more other entities.

- 340 -
 Settings

See the form on the multi-organisation module/association block for further information.

General

Default currency
The application is multi-currency, enabling storage of a conversion rate between a reference currency and another currency.
A default currency must be defined in the application settings, menu [Settings-Configuration-General settings].
The user can then define the conversion rates between the various currencies used.
The list of currencies and the conversion rates are managed through the menu [Settings-General-Currency].

One default currency is configurable in the User form.

Default time zone

Used to define the main time zone in order to inherit this time zone by default.
If the multi-time zone module is not enabled, changing the time zone will update all the assets, users and warehouses.

Languages used

This setting is used to define the languages used within the organisation so that data may be translated accordingly.
A language must be selected. The default language of blank databases is English.

n Multiple languages may be added when the multi-languages module is enabled. A language selected by a user cannot
be deleted. The data in the application become translatable in all the configured languages:

o Either by clicking the icon in the forms next to the data to be translated

o Or by clicking on the "Translation" link in the

These links open the following translation page:

Once the various translations have been entered for each language, the item will appear in each logged-in user's display lan-
guage.

n If the multi-languages module is not enabled, only one language may be added.

- 341 -
 Settings

The display language of all the users is updated whenever the language used is changed.
Each user’s display language is configured in the user form (or in the user banner).

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

Help default language

The online help is displayed in each page and provides additional information for the users.
The online help is displayed in the language of the user.
This setting defines the default language of the online help if it is not available in the language of the user.

Automatic codification reset at change of year

Choices: Yes/No; "Yes" by default.

Password management

This block translates the password policy established for any new user

Default password for importing users / when a user is created or it is reset by the administrator / when
changed by the user
This password is automatically assigned to users when users are imported.
When the user logs in for the first time, he is obliged to change his password.
If the user is already known in the database, no password change; if the user is new, forced password reset.

A strength indicator enables the user to make a valid choice.

It is viewed with the following characteristics:

o Display and update according to the password entered

o Length (password entered) > = 8 characters
o Password strength, scored from 1 to 5, with colours corresponding to the different scores (1/2 = red, 3 = orange, 4/5 =
green)
o Password can be saved (validation button enabled) if:
l number of characters > = 8

l strength > = 3

l password and its confirmation identical (rule already exists)

o When saving, an error message is displayed if the password corresponds to the user ID.

Note: imports of existing users with a weak default password will be blocked.
In this case, the administrator must change the default password when importing users.

X last passwords banned

This setting has the following features:

o Name: "X last passwords banned"

o Format: Integer
o Unit: Days or Months
o Default value: 3 (modifiable; must be >=1 with a maximum value =5)
o If using a previous password banned, error message: "You have entered one of your previous passwords, please try
again."

- 342 -
 Settings

Application of configuration:
* when password changed by the administrator or user

Password validity period

This setting has the following features:

o Name: "Password validity period"

o Format: Integer
o Unit: Day or Months ("999" maximum if entered in Days; "36" maximum if entered in Months)
o Default value: 3 months (the value may be equal to 0; the day after the last day of validity, the user cannot log in)
o If value = 0:

l user passwords defined with the new password management will still be valid
l the other passwords must be reset the next time the user(s) concerned log in

Application of configuration:
* when password created by the administrator
* when password changed by the administrator or user

A warning is given 10 days from the end of password validity.

Purchase requests

Default recipient of the PRs

To route the PRs to the right user, this setting defines the default recipient of the PRs.
The list displays all the users.
When a new PR is created, the default recipient is entered in the recipient field automatically.

Stock

Valuation type
The user can choose between different valuation types for stock management and entry/removal movements:

o WAUP: weighted average unit price

o LPP: last purchase price
o LIFO: Last In, First Out
o FIFO: First in, First Out
o MEFO: Most Expensive First Out

For the “by part” calculation method, only the WAUP and LPP valuation types are available. (See Valuation calculation )

Valuation calculation
A setting provides a choice between two stock valuation calculation options:

- 343 -
 Settings

o By warehouse
o By part
For the “by part” calculation method, only the WAUP and LPP valuation types are available. (See Type of valuation)

Main warehouse
Movements are made for the main warehouse by default. Displays the list of non-archived warehouses.
In the WOs, the parts needed for the tasks in the resources are assigned to the main warehouse if they are managed in stock in
this warehouse; if not, they are not assigned to any warehouse.

Preventive works

Default PW triggering time

Positive whole number field + choice between day(s) and month(s); 1 month by default It is used to define how long before the
date of a PW occurrence it is automatically converted into a WO.

Default meters PW into WO trigger method

Its initialisation enables you to define the default PW conversion method with a meter trigger.

Two choices are possible:

n Actual achievement of the trigger value: the PW will be converted into a WO if the meter has actually achieved the trig-
ger value.
n Projection in time: the PW will be transformed into a WO based on the last readings performed, according to a pro-
jection in time calculation estimate. This method was the only one applied before R13. Now, you can also use the
Actual achievement of the trigger value method.

A Trigger block on the Preventive work form enables you to change this setting by default.

Trigger threshold for default meters converting PW into WO

Enables you to define the threshold that triggers conversion of meters PW into WO by default.

A Trigger block on the Preventive work form enables you to change this setting by default.

Days of the week without PW trigger

Used to define the days on which PWs must not be triggered.

o Multi-selection possible

o By default, no day is selected, at least one day must not be selected.

Statuses of assets without PW trigger

Used to define the asset statuses for which PWs must not be triggered.

o Multi-selection possible

o Selection list of the configured asset statuses.

The occurrences that are not transformed into WOs are transformed when the asset returns to a status that allows the trigger.

- 344 -
 Settings

E-mail sending administration

Accessible through the menu [Settings-Configuration]
This screen is used to configure the settings for sending e-mails and to define the actions for which an e-mail must be sent auto-
matically.
E-mails are sent in the recipient's language (data and descriptions displayed in the recipient's native language).

When a WR is created, an email is sent to each recipient and to the requester with the template below:

Subject

Work Request [(WR)code] - [Name(Entity)]: Creation

Email body

The email body contains the following information:

- Code
- Title
- Status
- Asset
- Location
- Requester
- Creation date
- Priority
- WR type
- Technology
- Comments: if there are any we have a list of comments

This email template has been sent with the replacement of "Creation" (in "Subject") during the following actions on the WR:

- change of recipient ("Change of recipient")

- first conversion into a WO ("1st Conversion into a WO [(WO)code]")
- completion of all WOs ("All the WOs are complete")
- closure of all WOs ("All the WOs are closed")
- agreement for work ("Work accepted")
- work refused ("Work refused")
- WR cancellation ("Cancellation")
- WR re-opened ("Re-opening")

Attachment

For any action on a WR that generates an email, this will contain the WR ([(WR)code] - [Name(Entity)]) in an attachment that is
identical to the document generated when printing.

For any action on a WO that generates an email, this will have a similar template to the template linked to the WR ("WR" being
replaced by "WO", and "Work Request" by "Work Order"), with the other changes contained in the "Subject" being:
- "Technician description" (addition/modification of a technician)
- "Subcontractor description" (addition/modification of a subcontractor)
- "Resource limit/task response" (limit to a resource line or response to a task)
- "Resource limit/task response" (limit of all the resources and responses to all tasks)
- "Closure" (closure of WO)

- 345 -
 Settings

- "Cancellation" (closure of WO)

The following information is in the body of the email generated by an action on a WO or a grouped WO.

- Code
- Title
- Status
- Type of work
- Priority
- Technology
- Comments: if there are any we have a list of comments

This email template is sent with suitable labels, during the following actions on the WO or grouped WO:

Adding or editing a resource line

Adding or editing a subcontracting line
Resource line term or response to a task in the work order
Term for all the resource lines and response to all order tasks
Closure of the work order: sent to technicians
Closure of the work order: sent to subcontractors
Closure of the work order: sent to issuer
Closure of the work order: sent to requester
Cancellation of the work order: sent to technicians
Cancellation of the work order: sent to subcontractors
Cancellation of the work order: sent to issuer
Cancellation of the work order: sent to requester

The email will contain the WO ([(WO)code] - [Name(Entity)]) in an attachment that is identical to the document generated when
printing.

The order e-mail, at time of sending, includes essential information and more detailed information in the e-mail body (details
about the parts and delivery conditions in particular).

Duplicating the configuration

The button copies part or all of the email administration configurations from this screen to the
target entities.

- 346 -
 Settings

The user selects the configuration sections to be duplicated: Settings, work request, work order, etc. then the entities for which
he wishes to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action can also be performed from each entity's email administration configuration. It enables one to duplicate the confi-
guration from a specific entity to one or more other entities.

See the form on the multi-organisation module/association block for further information.

Settings block
Technical configuration:

n Port
n SMTP server
n SMTP user/SMTP password (encrypted)
n Sender e-mail address (sender)

For e-mail sending, the ONLY configuration possible is:

l port: 25
l SMTP server: smtp
l Neither SMPT user or SMTP password
l Sender e-mail address: sender with an existing @domain (e.g. [email protected])

Work request, Work order, Purchase request and Order blocks

Used to define:

n For which actions performed on the WRs, WOs, PRs and orders an email notification must be sent.
n to which recipient(s) the e-mails are transmitted.

The configuration for orders and PRs is only visible if the Orders module is enabled.

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form
If the grouped work module is enabled, refer to the section Managing how emails are sent with grouped WOs

WR status administration
Accessible through the menu [Settings-Configuration]

- 347 -
 Settings

This screen is used to manage the work request flows.

Duplicating the configuration

The button copies some or all of the WR status administration configurations from this screen to
the target entities (visible only if the multi-organisation module is enabled)

The user selects the configuration sections to be duplicated: Automatic changes, actions by status... then the entities for which
he wishes to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action can also be performed from each entity's WR status administration configuration. It enables one to duplicate the
configuration from a specific entity to one or more other entities.
See the form on the multi-organisation module/association block for more information, in particular on the management of equi-
valent statuses in configuration duplication.

Automatic changes block

Automatic WR status change settings can be defined according to the action performed. See the [WR statuses] section for status
management.

- 348 -
 Settings

If the action is enabled, the status of the WR when the action is performed will be the status defined on this screen.
If the action is disabled, the status of the WR when the action is performed will be the default status defined by the system.

In a single entity, all the non-archived reference statuses and equivalent statuses appear in the status list.
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses, whether archived or not. Equivalent statuses are not dis-
played.
- In configuration by entity: the list displays the non-archived reference statuses and equivalent statuses associated with the
entity.

Actions by status block

The statuses can also determine the actions allowed or forbidden for the users.
The WR editing or conversion rights consequently depend on the status of the WR.

In a single entity, this list displays all the reference statuses and equivalent statuses (including archived statuses).
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses and equivalent statuses, of all entities, including archived
statuses.
- In configuration by entity: the list displays all the reference statuses and equivalent statuses associated with the entity, inclu-
ding archived statuses.

Cancelled and Closed statuses (or equivalent statuses) do not allow editing or conversion.

- 349 -
 Settings

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

WO status administration
Accessible through the menu [Settings-Configuration]

Duplicating the configuration

The button copies some or all of the WO status administration configurations from this screen to
the target entities (visible only if the multi-organisation module is enabled)
The user selects the configuration sections to be duplicated: Automatic changes... then the entities for which he wishes to apply
these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action can also be performed from each entity's WO status administration configuration. It enables one to duplicate the
configuration from a specific entity to one or more other entities.
See the form on the multi-organisation module/association block for more information, in particular on the management of equi-
valent statuses in configuration duplication

This screen is used to manage the work order flows.

Automatic WO status change settings can be defined according to the action performed. See the [WO statuses] section for status
management.

If the action is enabled, the status of the WO when the action is performed will be the status defined on this screen.
If the action is disabled, the status of the WO when the action is performed will be the default status defined by the system.
Except for the Close WO action, work orders cannot be closed automatically if the action is disabled and an error message is dis-
played.

In a single entity, all the non-archived reference statuses and equivalent statuses appear in the status list.
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses, whether archived or not. Equivalent statuses are not dis-
played.
- In configuration by entity: the list displays the non-archived reference statuses and equivalent statuses associated with the
entity.

In multi-entity mode, these settings must be configured for each entity. To do so, refer to the Multi-organisation module
form

PR status administration
Accessible through the [Settings-Configuration] menu (If the orders module is enabled)
This screen is used to manage the purchase request flows.

Duplicating the configuration

- 350 -
 Settings

The button copies some or all of the PR status administration configurations from this screen to
the target entities (visible only if the multi-organisation module is enabled).
The user selects the configuration sections to be duplicated: Automatic changes, Actions by status... then the entities for which
they wish to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action can also be performed from each entity's PR status administration configuration. It enables one to duplicate the confi-
guration from a specific entity to one or more other entities.
See the form on the multi-organisation module/association block for more information, in particular on the management of equi-
valent statuses in configuration duplication.

Automatic changes block

Automatic PR status change settings can be defined according to the action performed.

If the action is enabled, the status of the PR when the action is performed will be the status defined on this screen.
If the action is disabled, the status of the PR when the action is performed will be the default status defined by the system.

In a single entity, all the non-archived reference statuses and equivalent statuses appear in the status list.
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses, whether archived or not. Equivalent statuses are not dis-
played.
- In configuration by entity: the list displays the non-archived reference statuses and equivalent statuses associated with the
entity.

- 351 -
 Settings

Actions by status block

The statuses can also determine the actions allowed or forbidden for the users.
- Changing a PR
- Converting a PR into an order
The PR editing or conversion rights consequently depend on the status of the PR.

In a single entity, this list displays all the reference statuses and equivalent statuses (including archived statuses).
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses and equivalent statuses, of all entities, including archived
statuses.
- In configuration by entity: the list displays all the reference statuses and equivalent statuses associated with the entity, inclu-
ding archived statuses.

Cancelled and Closed statuses do not allow for editing (cannot be configured).
Processed, Cancelled and Closed statuses do not allow for conversion (cannot be configured).

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

Order status administration

Accessible through the [Settings-Configuration] menu (If the orders module is enabled)
This screen is used to manage order flows.

Duplicating the configuration

The button copies some or all of the order status administration configurations from this screen
to the target entities (visible only if the multi-organisation module is enabled).

The user selects the configuration sections to be duplicated: Automatic changes,... then the entities for which they wish to apply
these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action can also be performed from each entity's order status administration configuration. It enables one to duplicate the
configuration from a specific entity to one or more other entities.
See the form on the multi-organisation module/association block for more information, in particular on the management of equi-
valent statuses in configuration duplication.

Automatic changes block

It is possible to configure automatic changes to orders statuses depending on the action performed.

- 352 -
 Settings

If the action is enabled, the order status will be the status configured on this screen when the action is performed.
If the action is disabled, the order status will be the default status defined by the system when the action is performed.

In a single entity, all the non-archived reference statuses and equivalent statuses appear in the status list.
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses, whether archived or not. Equivalent statuses are not dis-
played.
- In configuration by entity: the list displays the non-archived reference statuses and equivalent statuses associated with the
entity.

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

Actions by status block

The order editing rights depend on the status of the order.

If the box is checked, the change is allowed.
If the box is not checked, the change is prohibited. However, order receipt remains possible in a non-modifiable status (except
for cancelled, closed, and equivalent statuses).

In a single entity, this list displays all the reference statuses and equivalent statuses (including archived statuses).
If multi-organisation mode is enabled:
- In the default configuration: the list displays all the reference statuses and equivalent statuses, of all entities, including archived
statuses.
- In configuration by entity: the list displays all the reference statuses and equivalent statuses associated with the entity, inclu-
ding archived statuses.

Cancelled and closed statuses do not allow for editing (cannot be configured), or receipt.

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

WR recipient administration
Accessible through the menu [Settings-Configuration]

- 353 -
 Settings

This screen is used to set different recipients according to the WR type.

The list displays all non-archived WR types and non-archived users who are technicians.
It is also possible to set specific recipients if no WR type is selected.

When a WR type is archived, it is no longer displayed but its recipients' settings remain saved. This way, if the WR type is unar-
chived, users can find their settings.
Deleting a WR type also deletes all associated recipient settings.
When a user who is configured to receive a WR (overall and/or on entities) is deleted, the user is removed from these recipients.
When a user who is configured to receive a WR (overall and/or on entities) is archived, the user is not removed from these reci-
pients, but is no longer visible in the display. The user no longer receives e-mail alerts.
When the role of a user who is configured to receive a WR on an entity is deleted, the user is removed from the recipients.
When an entity of a user who is configured to receive a WR on this entity is deleted, the user is removed from the entity's reci-
pients.

In multi-entity mode, these settings may be configured for each entity. To do so, refer to the Multi-organisation module form

Additional fields
Accessible through the [Settings-Configuration] menu (If the additional fields module is enabled)
This screen enables us to manage additional fields for the asset file.

Duplicating the configuration

The button enables you to copy the configuration of additional fields to other items.

For the asset form, the user selects the asset families for which he wishes to apply the configuration displayed.
Duplication is only possible from one family to several other families.
When duplicating the configuration to a parent family, inheritance is not automatically applied.

This change overwrites the settings that existed before duplication.

Configuration enables us to differentiate between additional fields to be displayed according to certain criteria

Asset form
For the asset form, the additional fields can be configured per asset family:

- 354 -
 Settings

n None : corresponds to the additional fields displayed for assets that do not have an asset family
n All : corresponds to the additional fields displayed for all assets, whether they are allocated to a family or not.
n Asset family : corresponds to the additional fields displayed for the asset family selected.

In all cases, the additional fields in the "All" category will be displayed in all assets, in addition to the other additional fields confi-
gured (for assets that do not have a family and assets with a family).

Additional Fields Block

Click the button to insert a new additional field.

Different types of additional fields may be added: (list of Type choices)

n Boolean
n Date
n Date + time

n List of values: after adding a list of values type field, values are created by clicking on the button by opening the
line.
o The values are unique for each list. It is possible to have the same value twice in two different lists, but not in

the same list.

o When a value is archived, it can no longer be selected in the lists of values. It remains entered on the existing

forms.
o The values used in the application cannot be deleted.

n Decimal
n Duration
n Integer
n Time
n Price
n Text
n URL: when saving the form, the URL input can be clicked directly, and can then be opened in a new tab.

Unicity of additional fields :

Additional fields on the asset form: Two identical fields may exist in two different families, but not in the same family.

Translation of an additional field : Click the button to translate the description of the additional field. It will then be
displayed in the user's description language. Translation is possible on a reference language or a customised language.
Translation of the values in a list of values : Values associated with an additional list of values type field are translated into the
user’s display language.

Deletion of additional fields : When an additional field is deleted, it no longer appears on the existing forms. For a list of values,
the associated values are also deleted.

The display of additional fields is also configurable in the screen configuration.

Customised languages - Customisation of the application's descriptions

Accessible through the menu [Settings-Configuration - Customised languages]
All the application's descriptions can be changed and customised for your use. For each source language (French, English, Spa-
nish, etc.), it is possible to create several customised languages and allocate them to users.

- 355 -
 Settings

Configuration can only be done from a supervisor type profile

Entry fields:

n Code: unique and required

n Source description language: Displays the list of description languages available in the application (French, English,
German, etc.). It is used as a reference language for customisation. The descriptions to be customised will be dis-
played in the source language in the translation pop-in.

After having entered the new language code and selected the reference language, click the button to confirm.

Save the new language then click the button to display the customised translation input page.

- 356 -
 Settings

The page displays the list of all the application's descriptions, in the reference language. The Context and Description columns
provide clarification on the context for use and the page on which the description is displayed.

The customised descriptions are to be entered in the Translation field. Changing the page maintains the data input.
Non-customised descriptions will be displayed in the reference language.

N.B. certain reference descriptions may contain the characters: {0}, ou {1}. These variables must not be modified or deleted

because the application uses them to retrieve data (WO code created, asset code, etc.)

When all the replacement terms are input and saved, the new customised language can be allocated to users.

Users logged in with this customised language see the changed description. Non-customised descriptions are displayed in the
reference language.

Customised languages may be archived and de-archived. Archived languages no longer appear in the lists.
It is possible to delete a customised language if it is not used by any CMMS user.

Tree partition

List of tree partitions

The list is accessible from the menu [Settings-Configuration-Tree partition].

The list displays all the tree partitions, sorted in ascending order of tree codes.

Only Supervisor accounts have access to this menu.

Creating a tree partition

A tree partition can be created:

n with the button on the list of tree partitions.

n by clicking on the tree partition form button.

For further explanations on creating a tree partition, refer to the tree partition form.

- 357 -
 Settings

Deleting a tree partition

To delete a team:

n by clicking on the button on the form or the list of tree partitions.

n from the list of tree partitions, by clicking on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

Advanced filters

This block, which is closed by default, shows the following fields:

n Name: Text field. Filter automatic when entering the partition title.
n Type: Drop-down list, with the choices: "All", "Static", "Dynamic".
n First partition level: Drop-down list, with the choices: "All", "Tree nodes", "Asset family". In static mode, the list is
grey and inaccessible.
n Second partitioning level: Drop-down list, with the choices: "All", "Tree nodes", "Asset family". In static mode, the list
is grey and inaccessible. Any choice made in the first level cannot be found.
n Users: Drop-down list with the list of unarchived Requester, User or Guest type users who have access to DIMO Maint
MX and/or App. Filter on the logged-in user's entity/ies.
n Asset family: Typeahead and standard search window of asset families, filtered to the logged-in user's entity/ies. Asso-
ciated with: “With children” check box.
n Assets: Typeahead and standard asset search window, filtered to the logged-in user’s entity/ies. Associated with:
“With children” check box.

Tree partition form

Accessible from the list of partitions, menu [Settings-Configuration-Tree partition].

Click the button to access the form being created or the button to view a partition.

The icons give access to the various forms or to the corresponding repositories so that information can be viewed or modi-
fied during entry.

Identity block

- 358 -
 Settings

This block, which is open by default, defines the main information relating to the tree partition.

n Name: Required unique field. Defines the partition title.

n Type: Drop-down list, with the choices: "Static", "Dynamic". By default, "Static" is selected.
n First partitioning level: Drop-down list, with the choices: "Tree nodes", "Asset family". In static mode, the list is grey
and inaccessible.
n Second partitioning level: Drop-down list, with the choices: "Tree nodes" or "Asset family" depending on the choice of
first level. In static mode, the list is grey and inaccessible.
n Entities: filter, suggesting the logged-in user's entities by default.

Changing entities, type or level

Any change leads to:

l a confirmation message:

for a level change

for an entity or type change

Authorised asset block

This block is closed by default and displays a table of authorised assets for each partition.

Click on the button to access the selection pop-in.

Static type:

The "Select assets" selection window opens and suggests:

l "Assets", "Asset family" and "Cost allocations" selection buttons

l Typeahead search field for assets
l tree field depending on the "Assets", "Asset family" and "Cost allocation" selection ("Assets" by default) enabling the

- 359 -
 Settings

entry of assets with a checkbox

l "Select" and "Cancel" buttons

Selection rules:

l selecting a parent level automatically selects the child assets

l it is possible to select a child asset alone
l changing tree type (change from "Assets" to "Cost allocations" for example) resets the selections that may have been
made
l if you click "Select" after selecting assets, you return to the partition sheet and the list of assets authorised and filled in
according to the selections.
l if you click "Add", when the list of assets is already filled in, you find the memorised selection of this list with the pos-
sibility of changing it, in "Assets" choice by default
l no restriction on the deletion of assets in the list of authorised assets
l if no element is selected, a blocking message appears: “You must enter/select at least one element in each displayed
tree”

Display rule:

You only view assets that are checked as authorised

Authorised Objects block

This block, which is folded by default and replaces the Authorised assets block for Dynamic partitioning, displays a table of the
objects authorised for each partition.
The columns displayed are as follows:

l Object: Family or tree node depending on the type of selection in the first and second partitioning levels
l Code: Code of the family or tree node selected
l Description: Description of the family or tree node selected
l Entity: Entity of the family or tree node selected

Click on the button to access the selection pop-in.

Dynamic type:

The "Select objects" selection window opens and suggests:

- 360 -
 Settings

l one or two tree fields depending on the selection of "Tree nodes" or "Asset families" as partitioning levels
l "Select" and "Cancel" buttons

Selection rules:

Taken into account in the list of authorised assets:

Not taken into account in the list of authorised assets:

l the node tree only displays assets where "Is a node" is enabled, corresponding to the entities selected
l if you uncheck "Is a node", a blocking message will be displayed: "Cannot perform operation. This node is used in one
or more partitions". This allows you to not delete the partition's child assets when "Is a node" is used as a choice in a
dynamic partition.
l the family tree displays asset families corresponding to the entities selected
l if you click "Select" after selecting tree nodes and/or asset families, you return to the list of authorised assets. The list
displays the child assets of nodes selected and nodes taken into account
l if you click "Add", when the list of assets is already filled in, you find the memorised selection of this list with the pos-
sibility of changing it
l adding any assets or an asset branch (creation or movement) in a node taken into account in a partitioning level
updates the list of authorised assets
l deleting an asset or an asset branch under a node taken into account in a partition updates the list of authorised assets
l the archiving of an authorised asset will only be taken into account then the list of authorised assets is modified
l if no element is selected in at least one of the trees, a blocking message appears: “You must enter/select at least one
element in each displayed tree”

Case 1 - only 1 "Tree nodes" partitioning level

The asset selection window only suggests the asset node tree of the logged-in user's entities.
Selecting a parent node automatically selects the child nodes.
Selecting a child node does not automatically select the parent levels.

Case 2 - only one "Asset families" partitioning level

The asset selection window only suggests the asset families tree of the logged-in user's entities.
Selecting a parent family automatically selects the child families.
Selecting a child family does not automatically select the parent levels.

Case 3 - 2 "Tree nodes" - "Asset families" partitioning levels

The asset selection window only suggests the asset nodes of the logged-in user's entities.
The family selection window suggests the full asset families tree of the logged-in user's entities.
Tree nodes and asset families can be chosen freely but may create a blank list of authorised assets.

Click on the icon to open the Asset form in a new tab.

Display rule:

You see the child assets of nodes or families that are checked as authorised and the nodes taken into account.

Assigned users block

This block is closed by default and displays a table of users assigned to the partition.

- 361 -
 Settings

Click the button then select a category from the list suggested.

The "Add users" selection window opens and suggests:

l selection filter "Account type". Requester, User and Guest account types are available.

l tree field for entering user profiles or users that do not already belong to a partition of the same type. Profiles
other than the one selected appear in the tree, but you cannot select users that belong to them.
l "Select" and "Cancel" buttons

Selection rules:

l selecting a parent level automatically selects the child levels

l selecting a child of a parent level that has several children does not take into account the parent levels
l if you click "Add", when the list is already filled in, you find the memorised selection of this list with the possibility of
changing it
l deleting one or more users updates the list of users

Click the button after selecting the user line(s) to be eliminated, or the icon at the end of the line
selected.

Click on the icon to open the User form in a new tab.

IMPACT

Impact of partitioning on the tree (concerns the Tree widget and the (Assets - Tree) menu

l Static: you view the assets checked as authorised and the unauthorised parents
l Dynamic: you see the child assets of nodes that are checked as authorised and the parents that are taken into account
or not

The button after selecting unauthorised assets returns the error message "You cannot perform this action. Asset
is forbidden".

Impact on partitioning on WOs and on grouped WOs

l Tree widget

The and buttons for authorised assets enable the action to be triggered.

- 362 -
 Settings

The button for unauthorised assets returns the error message "You cannot perform this action. Asset is for-
bidden".

The button can be accessed for all assets displayed in the Tree widget but only returns a filled-in list for authorised
assets of the logged-in user's authorised entities.

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

l WO info, My late WO alerts, My schedule, Unassigned work widget

Viewing the widget gives access to or takes into account the WOs on the authorised assets of the logged-in user's authorised enti-
ties.

l Work orders menu - Advanced filters block - Asset field, Work request, Preventive work

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

l Grouped work orders menu - Advanced filters block - Grouped work order field

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

Impact of partitioning on WRs

l Tree widget

The and buttons for authorised assets enable the action to be triggered.

The button for unauthorised assets returns the error message "You cannot perform this action. Asset is for-
bidden".

The button can be accessed for all the assets displayed in the Tree widget, but only returns a filled-in list for autho-
rised assets and the WRs with no assets of the logged-in user's authorised entities.

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

l Work request widget - Asset field

- 363 -
 Settings

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

l My WR info, My late WR alerts

Viewing the widget gives access to or takes into account the WRs on the authorised assets and WRs with no assets of the logged-
in user's authorised entities.

l Work requests menu - Advanced filters block - Asset field

During search or typeahead, the selection of a non authorized asset returns the following error message: “You cannot carry out
this action. Asset is forbidden” as soon as the asset is selected.

Configuration of PDF screens and printing

The application enables one to customise the PDF display and printing of the application's forms through screen configuration.
The screens that can be configured are:

l Asset
l Work order
l Grouped work order
l Work request
l WR Widget on the home screen
l Inventories
l Budgets

You must log out/log back in after changing the screen configuration for the change to be applied.

Screen configuration

Screens are configured either generally or by user profile by clicking on the button in the gene-
ral settings or the profile form depending on needs.

- 364 -
 Settings

For each form, asset, WO, grouped WO, WR or WR Widget it is possible to define:
- blocks that are visible or hidden
- for each block the fields that are visible or hidden, required or optional, editable or read only.

The order of display of blocks and the order of display of fields can be changed:
- by drag & drop by selecting the line concerned and moving it to the level desired
- by directly changing the order in the line details

Data display takes into account modules that are enabled.

Some fields do however have specific features and cannot be hidden or are required and cannot be changed.

Configuration of screens on the asset file

Blocks that are always displayed : These blocks cannot be hidden

o Header block

Fields that are always displayed: These fields cannot be hidden

- 365 -
 Settings

o Header block: Code, Description, Time zone, Is a node

o Meters block: Description, Unit, Threshold, Value, Update date
o Associated files block: File
o Parts list block: Part

Fields that are always required:

o Header block: Code, Description

o Meters block: Description, Unit, Threshold, Value, Update date
o Associated files block: File
o Parts list block: Part

Editable block :

o Measurements block

Editable fields: These fields are editable (value: Yes/No)

o Header block: Is a node, Interface Key

o Measurements block: Code, Description, Value, Update Date/Time, Unit

Fields that are always read only: Non-modifiable

o All the block fields: Work orders, Work requests, Preventive work, Movements, Machine shutdowns, Jobs and Con-
tracts
o Meters block: Total

Configuration of WO form screens

These customisations are used to print the WO form.

Blocks that are always displayed : These blocks cannot be hidden

o Header block

Fields that are always displayed: These fields cannot be hidden

o Header block: Code, Asset, Deadline

o Workforce resources block: Technician category
o SC resources block: SC category
o Part resources block: Part description
o Downtime Resources block: Planned start date
o Job block: Routine
o Associated files block: File

Fields that are always Required:

o Header block: Code, Asset, Start date, End date, Sender, Creation date
o Workforce resources block: Technician category, Planned start date, Planned end date, Planned duration
o SC resources block: SC category, Planned start date, Planned end date, Planned duration
o Part resources block: Part, Description, Planned date, Planned quantity
o Downtime Resources block: Planned start date, Planned end date, Planned duration

- 366 -
 Settings

o Jobs block: Routine

o Associated files block: File

Fields that are always read only: Non-modifiable

o Header block: PW code, WR code

o Workforce resources block: Estimated cost, Actual duration, Actual cost
o SC resources block: Estimated cost, Actual duration, Actual SC cost, Actual part cost, Actual cost
o Part resources block: Estimated cost, Actual quantity, Actual unit, Actual cost
o Downtime Resources block: Estimated cost, Actual duration, Actual cost
o All the block fields Trees
o Costs
o Asset files
o WR files
o PW files
o Measurements block: Asset, Description, Old value date, Old value

Customising the various screens for displaying and entering planned and/or completed work order resources

Three options are available:

n Customising the WO form resource block screen

n Customising the report entry pop-up by resource type ( button of the WO form Resources block)

n Customising the work report history pop-up by resource type ( button of the WO form Resources block)

To customise the WO form resource block screen, select "Form"

A new list appears in the Resources block to customise the fields for each resource type:

n Workforce
n Subcontracting
n Downtime
n Part

- 367 -
 Settings

To customise the work report entry pop-up screen, select "Form" and then entry pop-up
A new list appears in the Resources block to customise the fields for each resource type:

n Pop-up for Labour work report entry

- 368 -
 Settings

n Pop-up for Subcontracting work report entry

n Pop-up for Downtime work report entry
n Pop-up for Part work report entry

Each pop-up opens a new form to customise each field.

To customise the work report history pop-up screen, select "Form" and then history pop-up
A new list appears in the Resources block to customise the fields for each resource type:

n Pop-up for Labour work report history

n Pop-up for Subcontracting work report history

n Pop-up for Downtime work report history
n Pop-up for Part work report history

Each pop-up opens a new form to customise each field.

Grouped WO form screens settings

Visible only if the grouped work module is enabled.

The common data settings are exactly the same as for a single WO.

WR form screen settings

Blocks that are always displayed : These blocks cannot be hidden

- 369 -
 Settings

o Header block

Fields that are always displayed: These fields cannot be hidden

o Header block: Code

o Associated files block: File
o Completion preference block: Start date, End date

Fields that are always Required:

o Header block: Code, Status, Requester, Entity, Creation date

o Associated files block: File
o Completion preference block: Start date, End date

Fields that are always read only: Non-modifiable

o All the block fields Trees

o Work orders

WR widget screen settings (home screen)

The WR form fields and thereby the widget are customisable: Display, required

o Title
o Status (Visible=No)
o Requester (Visible=No)
o Entity (if there is more than one entity on the licence)
o Asset
o Location
o Creation date (Visible=No)
o Asset off (Visible=No)
o Addressee (Visible=No)
o Effect (Visible=No)
o Priority
o WR type
o Code (must be checked; greyed out)
o Comment
o Type of work (Visible=No)
o Technology (Visible=No)
o Deadline (Visible=No)
o Cost allocation (Visible=No)
o Attached file (Visible=No)

Inventory form screen settings

(Only shown if the stock module is enabled)

Blocks that are always displayed : These blocks cannot be hidden

o Header block

Fields that are always displayed: These fields cannot be hidden

o Header block: Code, Description, Warehouse

- 370 -
 Settings

Fields that are always required:

o Header block: Code, Title -> cannot be changed to not required

o Warehouse: required by default, can be changed to not required

Fields that are always read only: Non-modifiable

o Header block: Date the theoretical quantity is taken into account

Budget screen configuration

Fields that are always displayed: These fields cannot be hidden

o Header block: Code

Fields that are always required:

o Header block: Code, Start date, End date, Frequency

Screen configuration in the general settings: default configuration

The screen configuration defined in the General settings [Settings-Configuration] corresponds to a default configuration that
enables one to quickly configure the screen configurations on each form.
This configuration can then be applied quickly in the User profiles
Refer to the Apply the default screens configuration section.

Screen configuration by user profile

The screen configuration defined in a profile form applies to all the profile users.
It is possible to retrieve the default configuration of the different forms that has been configured in the General settings by cli-

cking on the button .

Refer to the Apply the default screens configuration section.

Apply the default screens configuration

The button enables one to assign the default configuration of the different
forms directly to certain user profiles. This feature is available in General settings and in the User profile form.

- 371 -
 Settings

The user chooses the forms configured by default and the profiles to which he wishes to apply these configurations then
confirms the entry.

Configuration of PDF printing

PDF printing is configured in the same way, either generally or by user profile by clicking on the button

directly in the screen configuration in the general settings or the profile form depending
on the need.
It is used to customise printing of the application's forms (Asset, WR or WO) by displaying or hiding certain information (com-
pany logo, addresses, client or technician signature boxes etc.)
The screen configuration is used for the order and display of fields and blocks in prints.

The printing configuration created from the general settings is a default configuration for the different forms.
Specific configuration can be applied for each user profile directly from the profile form.

Configuration of asset form printing

The following information can be configured in printing:

n Company logo: main photo from the company form

Configuration of WO form printing

The following information can be configured in printing:

n Company logo: main photo from the company form

n Address: if there is at least one subcontracting line in the work order, the address displayed is the subcontractor’s
address from the first subcontracting line, otherwise no address is displayed.
At least one of the following 3 fields must be filled in in the address block for the data to be displayed: name, postcode
and town.
n Manager's signature
n Technician's signature

- 372 -
 Settings

n Client's signature
n Subcontractor's signature: "No" by default
n Work order jobs
n Bar code
n Detailed costs: display of the costs of the resource lines (not the Costs block)

Configuration of WR form printing

The following information can be configured in printing:

n Company logo: main photo from the company form

n Address: if there is a recipient on the WR, the last name and first name of the WR’s recipient are printed as well as the
WR entity’s address. If there is no recipient, the entity's name and address are printed. At least one of the following 3
fields must be filled in in the address block for the data to be displayed: name, postcode and town.
n Manager's signature
n Technician's signature
n Client's signature

General settings

Currency
Accessible through the menu [Settings-General]

Currency input field: Currency drop-down list automatically offered with three attributes:

l Currency ISO code: unique, required, cannot be changed

l Description: cannot be changed.
l Symbol: cannot be changed

Select the currency then click on the button to confirm the entry.

The List of currencies shows this information in the first two columns (Currency ISO code and Currency name).
In a third Number of decimals column, the number of decimals selected in accordance with the ISO standard for the currency
considered is displayed.
This number of decimals will be taken into account in the sections where it occurs (for example: Measurement form, "Analyses"
menu forms).

To enter the conversion rates between different currencies, click on the button at the end of the line.

The conversion rate history makes it possible to convert prices for any date. Click on the icon to access the conversion
history.
The most recent conversion rate appears for each currency.

It is possible to enter a new conversion rate by entering the date and the rate and clicking the button .

- 373 -
 Settings

In the application, the converted price displayed in the user currency takes into account the conversion rate applicable on the
reference date which may be, depending on the case, the document date, the line date, or the current date/time, depending on
the item displayed (most recent previous conversion rate)
If no conversion rate has been for logged for the reference date/time, the first rate entered is applied
If there is no conversion rate at all, a rate of '1' is applied.

E.g. :
For the hourly cost of labour in a WO, the reference date for the application of the conversion rate will be the line start date.
For the hourly cost of the category in the profile form, the reference date will be the current date.

The costs displayed in read-only mode (non-modifiable) are also displayed in the logged in user's currency.

It is not possible to delete currencies that are being used.

If a non-used currency is deleted, its corresponding conversion history will remain accessible.

For further information about the possible actions, refer to the Actions common to reference tables section.

General settings

Currency
Accessible through the menu [Settings-General]

Currency input field: Currency drop-down list automatically offered with three attributes:

l Currency ISO code: unique, required, cannot be changed

l Description: cannot be changed.
l Symbol: cannot be changed

Select the currency then click on the button to confirm the entry.

The List of currencies shows this information in the first two columns (Currency ISO code and Currency name).
In a third Number of decimals column, the number of decimals selected in accordance with the ISO standard for the currency
considered is displayed.
This number of decimals will be taken into account in the sections where it occurs (for example: Measurement form, "Analyses"
menu forms).

To enter the conversion rates between different currencies, click on the button at the end of the line.

The conversion rate history makes it possible to convert prices for any date. Click on the icon to access the conversion
history.
The most recent conversion rate appears for each currency.

It is possible to enter a new conversion rate by entering the date and the rate and clicking the button .

- 374 -
 Settings

In the application, the converted price displayed in the user currency takes into account the conversion rate applicable on the
reference date which may be, depending on the case, the document date, the line date, or the current date/time, depending on
the item displayed (most recent previous conversion rate)
If no conversion rate has been for logged for the reference date/time, the first rate entered is applied
If there is no conversion rate at all, a rate of '1' is applied.

E.g. :
For the hourly cost of labour in a WO, the reference date for the application of the conversion rate will be the line start date.
For the hourly cost of the category in the profile form, the reference date will be the current date.

The costs displayed in read-only mode (non-modifiable) are also displayed in the logged in user's currency.

It is not possible to delete currencies that are being used.

If a non-used currency is deleted, its corresponding conversion history will remain accessible.

For further information about the possible actions, refer to the Actions common to reference tables section.

Team

List of teams
The list of teams is accessible through the menu [Settings-General].
The available actions depend on the user rights [Settings-User-User profiles].

Creating a team

A team can be created:

n with the button on the List of teams.

n by clicking on the Team form button.

For further explanation on creating a team, refer to the Team form.

Duplicating a team

To duplicate a team:

n click on the button on the form.

n in the list of teams, by clicking on the button.

Duplication copies the selected team to a new team. All the information is duplicated, except the code and the description.
When a team is duplicated, all the information is duplicated except Code and Description
Timetables are not duplicated.

Deleting a team

To delete a team:

- 375 -
 Settings

n click on the button on the form or list.

n From the list, click on the arrow at the end of the line.

A confirmation message is displayed to confirm the deletion.

Links between team and members are deleted.
The timetables entered for the team are deleted.

Archiving/De-archiving a team

To archive a team:

n click on the button on the list or form.

n From the list, click on the arrow at the end of the line.

The icon is displayed to the left of the name, indicating that the team is archived.
Archived teams are no longer visible in the drop-down lists or the search fields.

To de-archive, proceed as follows:

n click on the button on the list or form.

n from the List of teams, click on the arrow at the end of the line.

The team is no longer archived and is displayed again in the selection lists and search fields.

- 376 -
 Resources

Team Forms
Accessible through the menu [Settings-General-Team]

Click on the button to access the form being created or on the button to view a team.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Teams list.

The icons give access to the various forms or to the corresponding repositories (Users) so that information can be viewed or
modified during entry.

Header block

This block defines the main information of the team.

n Code: required
n Description: required

Time block

Entry of team hours:

n Day (Drop-down list of days of the week ordered based on the user location)
n Start time
n End time

An end time entry of 00:00 is midnight

To enter an entire day: start time 00:00 and end time 00:00
Two date ranges cannot overlap

A "Duplicate" button, enabled once the hours have been saved, enables you to copy these hours to a User's hours.
(access to a duplication pop-in offering a Team member User selection field, with multiple selection possible).
Any duplication of Team hours to a User who already has hours is possible, but it overwrites the User's old hours.

Members block

Used to associate users with a team.

In multi-organisation mode, users are filtered on those that are linked to at least one of the team's entities.

Legal information
Accessible through the menu [Settings-General]
Entry fields:

n Description: required
n Legal information: text field

- 377 -
 Resources

Enter the description then click on the button to confirm the entry.
Legal information may be added to work orders but it is not then possible to delete it.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Payment terms
Accessible through the menu [Settings-General]
Entry fields:

n Description: required

Enter the description then click on the button to confirm the entry.
The payment terms are used in contracts in particular.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Unit
Accessible through the menu [Settings-General]
Entry fields:

n Code: unique and required

n Description: required

Enter the code and the description then click on the button to confirm the entry.

To enter the conversion rates between different units, click on the button at the end of the line.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Measurement types
Accessible through the [Settings-General] menu if the Measurements module is enabled.
The measurement types characterise measurements.
Entry fields:

n Code: unique and required

n Description: required

Fill in the input fields then click on the button to confirm the entry.

The measurement types are then used in measurements. Management of measurement types may be customised by user pro-
file (see Settings-User profiles-Configuration by entity).
The measurement types drop-down list only offers measurement types with the entity of the measurement in common.

- 378 -
 Resources

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Brand
Accessible through the menu [Settings-Assets]
This screen defines the brands of the assets.
Entry fields:

n Description: unique and required

Enter the description then click on the button to confirm the entry.
The brands are subsequently assigned on the asset forms.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Entities

List of entities

This list is accessible from the company form in the [Settings-Configuration-Company] menu via the but-
ton or the [Settings-Configuration-Entities] menu

The non-archived entities are displayed in ascending order.

The actions that may be taken in relation to the displayed entities depend on the user's rights: [Settings-Users-Users]
- Entities may be deleted, archived or de-archived only if the user is associated with them.

- The button is available only if the user is associated with the entity.
- Duplication is possible by all supervisor users.

See the form on the multi-organisation module for further information.

Creating an entity

An entity can be created:

n with the button on the list of entities.

n by clicking on the button on the entity form.

When creating a new entity, times are automatically entered from those of the company.

WO statuses associated with the creation of an entity

- If To do status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent shared
status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- 379 -
 Resources

- If Closed status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent shared
status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- If the statuses in progress, done and cancelled are not archived, they are automatically associated with the new entity.

WR statuses associated with the creation of an entity

- If In preparation status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent
shared status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- If Closed status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent shared
status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- If the statuses in progress, completed and cancelled are not archived, they are automatically associated with the new entity.

PR statuses associated with the creation of an entity

- If In preparation status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent
shared status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- If Closed status is not archived and shared, it is automatically associated with the new entity. Otherwise, an equivalent shared
status is associated with the new entity. If it doesn't exist, no status is associated with the new entity.

- If the statuses sent, processed and cancelled are not archived, they are automatically associated with the new entity.

For further explanation on creating an entity, refer to the entity form.

Deleting an entity

To delete a team:

n click on the button on the form or list of entities.

n from the list of entities, click on the arrow at the end of the line.

When an entity is deleted, its associations are deleted as well.

A confirmation message is displayed to confirm the deletion.

An entity may not be deleted if:
- it is associated with movements, WRs, WOs or PWs.
- if it is the last entity.

Duplicating an entity

To duplicate a team:

n click on the button on the entity form.

n from the list of entities, click on the button at the end of the line.

- 380 -
 Resources

Either action duplicates (copies) the selected entity to a new entity along with all the information in the identity block and asso-
ciations (name excepted).

If the button is not implemented in the Associations Block of the Entity form, it is hidden.

Archiving/De-archiving an entity

To archive an entity:

n click on the button on the list of entities or the entity form.

n From the list of entities, click on the arrow at the end of the line.

The icon appears to the left of the entity’s name to indicate that it has been archived.
Archived entities are no longer visible in the drop-down lists or the search fields.

Entity archival rules:

- The last non-archived entity may not be archived.
- An entity for which WOs are still open or are cancelled may not be archived.
- An entity for which WRs are still open or are cancelled may not be archived.

To de-archive an entity:

n click on the button on the list of entities or the entity form.

n From the list of entities, click on the arrow at the end of the line.

The entity is no longer archived and appears once again in the selection lists and search fields.

Entity de-archival rules:

- An entity may be de-archived only if non-enabled entities are still available in the licence.

- 381 -
 Entities

Entity form

The settings of the entities are accessible to supervisors:

n via the [Settings-Configuration-Company-Entity List or Entity Settings] menu

n via the [Settings-Configuration-Entities] menu

n via the user form, entity block, button

Click the button to access the form being created or on the button to view an entity.

If the supervisor user is linked to the entity, the page opens in edit mode. In all other cases, it opens in read-only mode.

The available actions depend on the user rights. [Settings-Users-User profiles].

The New, Delete, Archive and Duplicate buttons are explained in the actions of the Entity list.

Each entity must have at least a supervisor, a user manager and a profiles manager.

In multi-entity mode, see the form on the multi-organisation module for further information.

Identity block

- 382 -
 Entities

This block defines the main information of the entity.

n Name (Text). Required unique field.

n Address (text), ZIP/Post code (text), Town (text).
n Region (text), Country (text), Telephone (text).
n Fax (text), RCS number (text), NAF code (text).
n SIRET number (text), VAT number (text).

Opening hours block

This block defines the entity's opening hours and is used to pre-configure the technicians' hours.

n Day (Drop-down list of days of the week ordered based on the user location)
n Start time
n End time

An end time entry of 00:00 is midnight.

To enter a full day: Start time = 00:00 and End time = 00:00
Two date ranges cannot overlap

When creating a new entity, times are automatically entered from those of the company.

Associations block
This screen, which appears only if multi-organisation mode is enabled, is used to define the items to be associated with each
entity.
See the form on the multi-organisation module for further information.

Asset settings

Criticality
Accessible through the menu [Settings-Assets]
The criticality focuses maintenance operations on assets that risk generating significant losses for the company.
Criticality can be linked with a priority level which defines a work time limit.

Entry fields:

n Code: unique and required

n Description: required
n Priority: list of priorities
n Colour: association of a colour with criticality

Fill in the input fields then click on the button to confirm the entry.

The criticality can then be allocated to the assets. When an asset is selected in the various works, its criticality is assigned to the
work, informing the users of the priority level of the work.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

- 383 -
 Entities

Asset settings

Criticality
Accessible through the menu [Settings-Assets]
The criticality focuses maintenance operations on assets that risk generating significant losses for the company.
Criticality can be linked with a priority level which defines a work time limit.

Entry fields:

n Code: unique and required

n Description: required
n Priority: list of priorities
n Colour: association of a colour with criticality

Fill in the input fields then click on the button to confirm the entry.

The criticality can then be allocated to the assets. When an asset is selected in the various works, its criticality is assigned to the
work, informing the users of the priority level of the work.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Asset status
Accessible through the menu [Settings-Assets]
This screen is used to define the statuses that the assets can have. The status of an asset also determines whether it is in service
or out of service.

Entry fields:

n Description: unique and required

n The “Working” checkbox: indicates whether the asset is working or out of service when it is in the status selected

Enter the description of the status, then check the "Working" box to indicate whether the assets that have this status will be wor-

king, then click on the button to confirm the entry.

Some actions cannot be performed on assets that have an out-of-service status.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Asset families tree

Accessible through the menu [Settings-Asset-Asset family]

- 384 -
 Entities

The family is used to identify and group similar assets.

A search typeahead at the top of each tree structure enables you to identity an item in it quickly and select it.

The use of asset families enables analyses and reports to be generated on work for the same asset types.

The use of a tree structure makes it easier to define the settings of the family and sub-family levels.
The user views the different levels and easily distinguishes between the parent families and the child families.
This cascading set of families is also called a Node or Branch.

Click on the button to create a new family.

Select a family and click the button to modify an existing family.

Families can be moved by drag & drop.
The families are subsequently assigned to the assets.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Asset families are also configurable via the asset families list.

Deletion of a parent node also deletes the child nodes.

When deletion of a parent node is attempted, if any of the child nodes cannot be deleted, then the parent node is not deleted.
Archiving a parent node also archives the child nodes.

List of asset families

Accessible through the menu [Settings-Asset-Asset family]
The family is used to identify and group similar assets. The use of asset families enables analyses and reports to be generated on
work on the same asset types.

Entry fields:

n Code
: unique and required
n Description
unique and required
n Parent family:
possibility of selecting a parent family

Enter the code, the description and if applicable, the parent family then click on the button to confirm the entry.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Asset families may also be viewed in a tree structure.

Deletion of a parent family also deletes the child families.

When deletion of a parent node is attempted, if any of the child nodes cannot be deleted, then the parent node is not deleted.
Archiving a parent node also archives the child nodes.

- 385 -
 Entities

Brand
Accessible through the menu [Settings-Assets]
This screen defines the brands of the assets.
Entry fields:

n Description: unique and required

Enter the description then click on the button to confirm the entry.
The brands are subsequently assigned on the asset forms.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Types of contract
Accessible through the [Settings-Assets] menu if the Orders module is enabled.
The contract types characterise the contracts.
Entry fields:

n Code: unique and required

n Description: required

Fill in the input fields then click on the button to confirm the entry.

The contract types are then used in contracts. Management of contract types may be customised by user profile (see Settings-
User profiles-Configuration by entity)

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Work settings

Technician category
Accessible through the menu [Settings-Work]
The technicians can be grouped by specialisation. This screen lists the categories of technicians who can carry out maintenance
work, with their hourly cost (mechanic, electrician, etc.).
Entry fields:

n Code: unique and required

n Description: required
n Hourly cost

Fill in the input fields then click on the button to confirm the entry.
The technician categories are determined in the user profile, and the assignment of a main category is required for any profile
that has the technician role [Settings-User-User profile].
.

- 386 -
 Entities

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Work settings

Technician category
Accessible through the menu [Settings-Work]
The technicians can be grouped by specialisation. This screen lists the categories of technicians who can carry out maintenance
work, with their hourly cost (mechanic, electrician, etc.).
Entry fields:

n Code: unique and required

n Description: required
n Hourly cost

Fill in the input fields then click on the button to confirm the entry.
The technician categories are determined in the user profile, and the assignment of a main category is required for any profile
that has the technician role [Settings-User-User profile].
.
For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Partner category
Accessible through the menu [Settings-Work]
The external service providers can be grouped by specialisation. This screen lists the categories of partners that can carry out
maintenance work, with their hourly cost.

Entry fields:

n Code: unique and required

n Description: required
n Hourly cost

Fill in the input fields then click on the button to confirm the entry.
The partner categories are determined on the Partner form, and the assignment of a main category is required only if the part-
ner is a subcontractor [Resources-Partners].

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

WO status
Accessible through the menu [Settings-Work]
This screen is used to manage the different work order statuses.
The following statuses are the reference statuses available in the CMMS; they cannot be deleted:
- To do

- 387 -
 Entities

- In progress
- Done
- Cancelled
- Closed

It is possible to create as many equivalent statuses as desired, from these reference statuses.
Automatic status changes and the actions that can be performed according to the different statuses are configured in WO status
administration.

Entry fields:

n Description: unique and required

n Equivalent status: list of reference statuses. A new status must be based on one of the reference statuses. Some
actions on WOs as well as the analyses will depend on this status (Stock update, Calculation of PW occurrences, etc.)

Enter the status description, select the equivalent status, then click on the button to confirm the entry.

These statuses may be translated into all the display languages used in the application by clicking the translation button at the
end of the line of each item or with the bulk translator (if the multilingual module is enabled).

There must always remain a reference status or a non archived status equivalent to "To do" and "Closed" (per entity if the multi-
organisation module is enabled). All the other reference or equivalent statuses may be archived.

It is impossible to delete:

l a reference status (To do, In progress, Done, Cancelled and Closed)

l a status used in a WO
l a status referenced in WO status administrations (general and by entity)
l an entity’s last non-archived status equivalent to “To do”
l an entity’s last non-archived status equivalent to “Closed”

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.
If the multi-organisation module is enabled, see the Creating an entity section for more information on statuses associated with
new entities.

WR status
Accessible through the menu [Settings-Work]
This screen is used to manage the different work request statuses.
The following statuses are the reference statuses available in the CMMS; they cannot be deleted:
- To be processed
- In progress
- Completed
- Cancelled
- Closed

It is possible to create as many equivalent statuses as desired, from these reference statuses.
Automatic status changes and the actions that can be performed according to the different statuses are configured in WR status
administration.

Entry fields:

- 388 -
 Entities

n Description: unique and required

n Equivalent status: list of reference statuses. A new status must be based on one of the reference statuses. Some
actions on WRs will depend on this status.

Enter the status description, select the equivalent status, then click on the button to confirm the entry.

These statuses may be translated into all the display languages used in the application by clicking the translation button at the
end of the line of each item or with the bulk translator (if the multilingual module is enabled).

There must always remain a non-archived reference status or a “To be processed” and “Closed” equivalent status (per entity if
the multi-organisation module is enabled). All the other reference or equivalent statuses may be archived.

It is impossible to delete:

l a reference status (To be processed, In progress, Completed, Cancelled and Closed)

l a status used in a WR
l a status referenced in WR status administrations (general and by entity)
l an entity’s last non-archived status equivalent to “To be processed”
l an entity’s last non-archived status equivalent to “Closed”

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.
If the multi-organisation module is enabled, see the Creating an entity section for more information on statuses associated with
new entities.

Cost allocation tree

Accessible through the menu [Settings-Work]
Displays the various cost allocations in a tree.
A search typeahead at the top of each tree structure enables you to identity an item in it quickly and select it.
The use of a tree structure facilitates the definition of the cost allocation settings.
The user views the different cost allocation levels and can easily distinguish between the parent allocations and the child allo-
cations.
This cascading set of cost allocations is also called a Node or Branch.

Click on the button to create a new cost allocation.

Select a cost allocation and click the button to modify an existing cost allocation.
Cost allocations can be moved by drag & drop.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Cost allocations are also configurable via the list of cost allocations.

Deletion of a parent node also deletes the child nodes.

When deletion of a parent node is attempted, if any of the child nodes cannot be deleted, then the parent node is not deleted.
Archiving a parent node also archives the child nodes.

- 389 -
 Entities

List of cost allocations

Accessible through the menu [Settings-Work]
Displays the various cost allocations in a tree.
Entry fields:

n Code: unique and required

n Description: unique and required
n Parent cost allocation: possibility of selecting a parent cost allocation

Enter the code, the description and if applicable, the parent cost allocation then click on the button to confirm the
entry.

Cost allocations may also be viewed and archived in a tree structure.

Type of work
Accessible through the menu [Settings-Work]
The types of work characterise the works (Preventive, Troubleshooting, Adjustment, Inspection).
Entry fields:

n Code: unique and required

n Description: required

Fill in the input fields then click on the button to confirm the entry.
The types of work are subsequently defined on the various work forms (PW, WR, WO, etc.).

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

WR type
Accessible through the menu [Settings-Work]
The WR types characterise the work requests.

Entry fields:

n Code: unique and required

n Description: required

Fill in the input fields then click on the button to confirm the entry.
The WR types are subsequently defined in the work requests.

It is possible to configure WR recipients according to the WR type. This configuration is done in the WR recipient administration.
Deleting a WR type also deletes all associated recipient settings.
When a WR type is archived, it is no longer displayed in the WR recipient administration, but its recipients' settings remain
saved.

- 390 -
 Entities

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Technology
Accessible through the menu [Settings-Work]
The technologies define the trades that can carry out the works. (Mechanical, electrical, electronic, hydraulic, etc.).

Entry fields:

n Code: Unique, required

n Description: required

Fill in the input fields then click on the button to confirm the entry.
The technologies are subsequently defined in the various work forms (PW, WR, WO, etc.).
.
For further information about the possible actions (Archive, de-archive, delete, cancel), refer to the section Actions common to
reference tables.

Priority
Accessible through the menu [Settings-Work]
The preventive and corrective actions are performed according to the priority levels given for the works.

Entry fields:

n Code: Unique, required

n Description: required
n Deadline: in hours or days
n Colour

Fill in the input fields then click on the button to confirm the entry.
The priorities are subsequently retrieved on the various work forms (PW, WR, WO, etc.) and update the work dates of the WOs
according to the deadlines entered.
Their settings can also be defined according to the criticality of the assets. When an asset is selected, the work deadline and
consequently the priority level are displayed automatically according to the criticality. The criticalities are defined through the
menu [Settings-Assets]
.
For further information about the possible actions (Archive, de-archive, delete, cancel), refer to the section Actions common to
reference tables.

Stock settings

Terms of delivery
Accessible from the [Settings-Stocks] menu, the terms of delivery are used in particular in orders.

- 391 -
 Entities

Entry fields:

n Description: required

Fill in the input fields then click on the button to confirm the entry.

A term of delivery used in orders cannot be deleted.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Stock settings

Terms of delivery
Accessible from the [Settings-Stocks] menu, the terms of delivery are used in particular in orders.

Entry fields:

n Description: required

Fill in the input fields then click on the button to confirm the entry.

A term of delivery used in orders cannot be deleted.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Order status
Accessible through the menu [Settings-Stocks].
This screen is used to manage the different order statuses.
The following statuses are the reference statuses available in the CMMS:
- In preparation
- Sent
- Processed
- Cancelled
- Closed

It is possible to create as many equivalent statuses as desired, from these reference statuses.
Automatic status changes and the actions that can be performed according to the different statuses are configured in order sta-
tus administration.

Entry fields:

n Description: unique and required

n Equivalent status: list of reference statuses. A new status must be based on one of the reference statuses. Some
actions on orders will depend on this status (Stock update, etc.).

Enter the status description, select the equivalent status, then click on the button to confirm the entry.

- 392 -
 Entities

These statuses may be translated into all the display languages used in the application by clicking the translation button at the
end of the line of each item or with the bulk translator (if the multilingual module is enabled).

There must always remain a non-archived reference status or "In Preparation" and "Closed" equivalent status (per entity if the
multi-organisation module is enabled). All the other reference or equivalent statuses may be archived.

It is impossible to delete:

l a reference status (In preparation, Sent, Processed, Cancelled or Closed)

l a status used in an order
l a status referenced in order status administrations (general and by entity)
l an entity’s last non-archived status equivalent to “In preparation”
l an entity’s last non-archived status equivalent to “Closed”

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.
If the multi-organisation module is enabled, see the Creating an entity section for more information on statuses associated with
new entities.

PR status
Accessible through the menu [Settings-Stocks].
This screen is used to manage the different purchase request statuses.
The following statuses are the reference statuses available in the CMMS; they cannot be deleted:
- In preparation
- Sent
- Processed
- Cancelled
- Closed

It is possible to create as many equivalent statuses as desired, from these reference statuses.
Automatic status changes and the actions that can be performed according to the different statuses are configured in PR status
administration.

Entry fields:

n Description: unique and required

n Equivalent status: list of reference statuses. A new status must be based on one of the reference statuses. Some
actions on PRs will depend on this status.

Enter the status description, select the equivalent status, then click on the button to confirm the entry.

These statuses may be translated into all the display languages used in the application by clicking the translation button at the
end of the line of each item or with the bulk translator. (if the multilingual module is enabled).

There must always remain a non-archived reference status or "In Preparation" and "Closed" equivalent status (per entity if the
multi-organisation module is enabled). All the other reference or equivalent statuses may be archived.

It is impossible to delete:

- 393 -
 Entities

l a reference status (In preparation, Sent, Processed, Cancelled or Closed)

l a status used in a PR
l a status referenced in PR status administrations (general and by entity)
l an entity’s last non-archived status equivalent to “In preparation”
l an entity’s last non-archived status equivalent to “Closed”

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.
If the multi-organisation module is enabled, see the Creating an entity section for more information on statuses associated with
new entities.

Storage location
Accessible through the menu [Settings-Stocks]
The storage locations are used to locate the parts in the warehouses.

Entry fields:

n Code: unique and required

n Description: required
n Warehouse: required. Warehouse selection list

Fill in the input fields then click on the button to confirm the entry.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Warehouse
Accessible through the menu [Settings-Stocks]
In multi-warehouse mode, the user can manage the part stocks in several warehouses.

Entry fields:

n Code: unique and required

n Description: required
n Time zone: required. By default, the zone defined in the general settings.
n Currency: list of currencies used in the application. By default, the currency in the general settings. Changing a cur-
rency for a warehouse updates the stock values. The prices of stocks and batches are converted into the new ware-
house currency at the applicable conversion rate
n Negative Stocks: check box, unchecked by default

Fill in the input fields then click on the button to confirm the entry.
When a new warehouse is created, a stock line is associated with all the parts so that they can be managed in the warehouse.
However, the parts are not managed in stock in this warehouse by default.

When a warehouse is deleted, all the stock lines concerning it are also deleted.
A warehouse with a stock greater than 0 cannot be archived.

- 394 -
 Entities

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Part family tree

Accessible through the menu [Settings-Stocks-Part family]
The family is used to identify and group similar parts.

A search typeahead at the top of each tree structure enables you to identity an item in it quickly and select it.

The use of part families enables analyses and reports to be generated on the works for the same part types.

The use of a tree structure makes it easier to define the settings of the family and sub-family levels.
The user views the different levels and easily distinguishes between the parent families and the child families.
This cascading set of families is also called a Node or Branch.

Click on the button to create a new family.

Select a family and click the button to modify an existing family.

Families can be moved by drag & drop.
The families are subsequently assigned to the parts.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Part families are also configurable via the part families list.

Deletion of a parent node also deletes the child nodes.

When deletion of a parent node is attempted, if any of the child nodes cannot be deleted, then the parent node is not deleted.
Archiving a parent node also archives the child nodes.

List of Part families

Accessible through the menu [Settings-Stocks]
The family is used to identify and group similar parts. The use of part families enables analyses and reports to be generated on
the works for the same part types.

Entry fields:

n Code: unique and required

n Description: unique and required
n Parent family: possibility of selecting a parent family

Enter the code, the description and if applicable, the parent family then click on the button to confirm the entry.

For further information about the possible actions (Archive, de-archive, delete, cancel), refer to the section Actions common to
reference tables.

Part families may also be viewed in a tree structure.

- 395 -
 Entities

Deletion of a parent family also deletes the child families.

When deletion of a parent node is attempted, if any of the child nodes cannot be deleted, then the parent node is not deleted.
Archiving a parent node also archives the child nodes.

Anonymisation
Accessible to Supervisor type profiles via the menu [Settings-Utility programmes].
This screen is used to manage the anonymisation of the personal data of users who no longer want to appear in the application.

User block
Displays the list of users: Last Name, First Name, Username, Profile, Account Type

Select one or more users then click on the button at the top of the list or the button at the end
of the line. A confirmation message is displayed.

n The user's first and last name are replaced by random text
n The email address, telephone number and photos have been deleted

Partner contacts block

Displays the list of users: Partner Code, Partner Description, Last Name, First Name

Select one or more partner contacts then click on the button at the top of the list or the button
at the end of the line. A confirmation message is displayed.

n The contact's first and last name are replaced by random text
n The title, e-mail address, phone number, mobile number and fax number are deleted

Translation - Bulk translator

Accessible to Supervisor type profiles via the menu [Settings-Utility programmes] if the multilingual module is enabled.
This screen enables us to translate CMMS data quickly into different languages.

- 396 -
 Entities

Select the category of data to be translated (brands, models, jobs, tasks, list of additional field values, parts, profiles, etc.)
Choose the source display language and target display language then enter the translation for each item.

n Data: Drop-down list containing all the translatable items: Partner category, Technician category, asset, Asset status,
Part family, Asset family, Job, Technology, Unit type of work, Priority, etc.) (Required)
n Source display language: Drop-down list with the display languages used (Required)
n Display language to be translated: Drop-down list with the display languages used, by default the display language of
the user selected (Required)

Items translated will be visible to users who have the target display language configured in their user form.
l

File administration
The following file extensions are allowed: bmp,-
gif,jfif,jpeg,jpg,png,tif,HEIC,csv,doc,docx,log,msg,odp,ods,odt,pdf,ppt,pptx,rtf,txt,xls,xlsm,xlsx,xml,xps,dwg,GRF,GWF,DBF,DTF
The size of an attachment is limited to 15 Mb.
To add a file to a document you must upload a new file or select a file that is already stored.

Accessible to Supervisor type profiles via the menu [Settings-Utility programmes].

This screen page is equivalent to a console enabling you to manage the administration of attachments (display the file list, create
and read files, monitor file storage).

The actions available are: Refresh, Fold, Unfold, Help and Close.

Monitoring block
Displays the storage breakdown between authorised, used and remaining spaces as a pie chart.

- 397 -
 Entities

Associated files block

Displays the list of files (from the Associated files and Photos blocks in forms) on the column-fields: Document type, Document,
File name, File description, Date, File size.

Click the button to access the form being created or the button to view an associated file.

In both cases, you open the file detail pop-in, made up of the single Association block.

By clicking the button, two fields open for input:

l Document type: selection list, required

l Document: selection list, required

These two fields correspond to the two columns of the Association block, making a list of all the documents associated with the
file concerned.

Should the name of the associated file be shown in the file detail pop-in (above the Association block), you open or download
this file by clicking on it.

- 398 -
 Entities

Clicking the block or end of line action button associated with the file has effects on two different
levels:

l deleting the existing link between the file (identified by its name) and the type of document to which it has been asso-
ciated
l deleting the file itself from the database, when the file does not have a link with a type of document

- 399 -
 Entities

Unified authentication

For the technical scope covered by the feature, refer to the MX technical prerequisites.
For the configuration of Azure AD and the implementation of MX, refer to the DIMO Maint technical documentation — "Imple-
mentation of unified authentication for MX and DMA".

This is a new configuration enabling MX users to access the application via their Microsoft credentials (Windows session).

This page enables you to retrieve the ID and Password allocated to a user in the Active Directory.

Before enabling unified authentication in MX, you must contact our teams to ensure that this option has been enabled in our
hosting.

A Unified Authentication Supervisor account must be created before activation (linked to the customer's AD account) to log in
for the 1st time and if unified authentication is disabled.

"Unified Authentication" configuration is only accessible to Supervisors, by going to the menu: Settings ---> Utility program --->
Unified Authentication

As soon as the Supervisor has checked the "Enable Unified Authentication" box, two fields become required:

l Requestor profile: must correspond to the user profile

l Entities (Multi): to which the user must be attached

As soon as unified authentication is enabled, the "Change password" and "Reset password" buttons are no longer visible on the
User form.
This consequence translates an essential change: passwords are no longer managed via MX.

Furthermore, at the time of this activation, a check is made to check that a Supervisor account other than the administrator's has
already been created.
Otherwise, the error message "Please create a Unified Authentication Supervisor" appears.

When they first log in, a user sees a pop-in displayed to be filled in (Language, Display language, Time zone and Currency fields).

When the new user's info entry pop-in is validated, they are linked to the profile and the LDAP configuration entity created befo-
rehand.

- 400 -
 Entities

VAT
VAT
Accessible through the [Settings-General] menu if the VAT module is enabled.

The tab of the page is characterized by the icon:

VAT makes it possible to accurately specify order values, depending on where the purchase is made.
Entry fields:

n Code: unique and required

n Rate: required Positive decimal
n Shared data: disabled by default
n Entities: main entity of the logged-in user by default

Fill in the input fields then click on the button to confirm the entry.

VAT is then applied to the order values. Management of VAT may be customised by user profile (see Settings-User profiles-Con-
figuration by entity).
The VAT drop-down list only offers VAT with the entity of the order in common.

For further information about the possible actions (Archive, De-archive, Delete, Cancel), refer to the section Actions common to
reference tables.

Deletion is only possible if the VAT is not used in an order, regardless of its status (archived or not) or status ("In preparation",
"Sent", etc.), part or partner/supplier.

The rate can be modified as long as it is not used in an order. As soon as the VAT is used in an order (archived or not), the field
becomes greyed out and cannot be modified.

Once a VAT has been chosen or initialised, the rate can no longer be modified in the TDR.

Note: a filter error can occur with the VAT with the second decimal place of "0" and, in this case, prevent the VAT value from
being returned; this occurs when a comma "," is used for the decimal places instead of a full stop "." in the numeric keypad.

The rights on the TDR VAT are subject to the general repository.

- 401 -
Work analyses
The Analyses --> Work analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for work are:

n Failure tree
n Subcontractor category (work costs per subcontractor category)
n Technician category (work costs per technician category)
n Technician (work costs per technician)
n Work (history of work orders)
n Maintenance (MTBF, MTTR, failure rate, breakdown rate)
n Asset pareto (work costs per asset)
n Family pareto (work costs per asset family)
n Technology pareto (work costs per technology)
n Work type pareto (work costs per type of work)
n Cost allocation pareto (work costs per cost allocation)
n Responsiveness to each work order
n Subcontractor (work costs per subcontractor)
n Preventive work completion rate

Prices are displayed in the logged in user's currency. The conversion rate applied depends on the reference date. See the reference dates at
the bottom of the page for applying conversion rates here
The user display language is taken into account to display the item descriptions (Asset, Status, Technology, Type of work, Priority, Asset
family, Technician category, Subcontractor category, etc.)

Select the periods, the indicators to display, add the chosen filters, select the entity/ies with analyses then click the button

.
The table is displayed at the bottom of the page. Click on the arrows to view the different indicators:

Advanced filters

The filters available are

n Start date : Required; Format: "Date"(Date)

n End date : Required; Format: "Date"(Date)

n Indicators : List of indicators to be displayed. Multiple selection is possible. All the analyses selected will be displayed in the report
part.
n Top : For graphs, displays the top [No. selected] most expensive items. If no filter, displays all the results. E.g. for the technologies
pareto, will display the top 10 most expensive technologies.
n Asset : If the "With children" tick box is active, the result will take into account the child assets of the asset selected.
n Asset family : If the "With children" tick box is active, the result will take into account the child asset families of the asset family
selected.
n Cost allocation: If the "With children" tick box is active, the result will take into account the child cost allocations of the cost allo-
cation selected.
n Type of work
n Priority
n Technology
n Period : Selection list of period: Week, Month or Year. This filter is only applicable for maintenance indicator graphs
n Status : List of choices of WO statuses (reference statuses and equivalent). If no status is selected, all the statuses are taken into
account in the result. This filter is applicable for the indicators:
o Work (history of work orders).
o Assets pareto
o Asset families pareto
o Work types pareto
o Technologies pareto
o Summary by technician category
o Summary by technician
o Summary by subcontractor category
o Summary by subcontractor
o Maintenance indicators
o Work order responsiveness

The other indicators are only based on closed orders (or equivalent):
o Failure tree
o Preventive work completion rate (work completed)

n Entity : Required. Visible only if the multi-organisation module is enabled. The list of entities displays non-archived entities to
which the user is associated. When a filter is applied to entities, only the work orders associated with these entities are taken into
account in the results.
n Archived Grouped WOs/ WO : Choices: “Yes”, “No”, “All”, with a default value of “No”.

Failure tree
This analysis searches the diagnostics used in the work orders. The objective is to display the links between the work orders and their
effects, causes and remedies.

It uses the following filters: Start date, End date, Asset, Asset family, Cost allocation, Work type, Priority, Technology and Entity. It does not
use the Top, Period or Status filters.

For a work order to be displayed, its start and end dates must be between the filter start date and end date.

Only work orders with closed or equivalent status are included.

The links are displayed in tree format, as set out below:

Effect1 contained in an order
Cause1 linked to the effect contained in an order
Remedy1 linked to the cause contained in an order
Order1 including the effect/cause/remedy trio
Order2 including the effect/cause/remedy trio
Remedy2 linked to the cause contained in an order
Order1 including the effect/cause/remedy trio
Order2 including the effect/cause/remedy trio
Cause2 linked to the effect contained in an order
...
Effect2 contained in an order
...

If any of the orders do not include an effect, an “Effect not entered” line is displayed to account for them
For each of the effects, if any of the orders do not include a cause, a “Cause not entered” line is displayed to account for them
For each effect/cause, if any of the orders do not include a remedy, a “Remedy not entered” is shown to account for them

Occurrences view
Each effect line displays the number of times said effect is used in an order + the percentage of the total number of effects used in the
orders that this number represents.

Each cause line related to an effect displays the number of times said cause has been used in an order related to this effect + the percentage
of the total number of causes used in orders related to this effect that this number represents.

Each remedy line related to an effect and a cause displays the number of times said remedy is used in an order related to this effect and
cause + the percentage of the total number of remedies used in orders related to this effect and cause that this number represents.

The items are sorted by decreasing occurrence on each level

Time view
Indicates which diagnostic elements take the most time

Each order line displays the sum of the WF and SC hours spent on the order.
The orders are sorted by decreasing time spent

Each remedy line displays the sum of the time spent on orders related to the effect/cause/remedy trio
+ the percentage of the total time taken by orders related to the effect/cause duo that this time represents
Each cause line displays the sum of the time taken on orders related to the effect/cause duo
+ the percentage of the total time taken by orders related to the effect that this time represents

Each effect line displays the sum of the time spent on orders related to this effect
+ the percentage of the total time taken by these orders that this time represents

Costs view
Shows which diagnostic items generate most costs

Each order line displays the sum of the WF, SC, parts and stoppage costs completed on the order.

Each remedy line displays the sum of the costs spent on orders related to the effect/cause/remedy trio
+ the percentage of the total cost related to the effect/cause duo this cost represents

Each cause line displays the sum of the costs spent on orders related to the effect/cause duo
+ the percentage of the total cost of orders related to the effect this cost represents

Each effect line displays the sum of the costs spent on orders related to this effect
+ the percentage of the total cost of orders this cost represents

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Subcontractor category

Displays the summary of work grouped by partner/subcontractor category with a resource implemented in the period selected

n Partner category
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses)... Possibility of placing a filter on
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each category are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the category) + Sum(Scheduled WF time of the
grouped WOs related to the category)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Technician category

Displays the summary of work grouped by technician category with a resource implemented in the period selected

n Technician category
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each category are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the category) + Sum(Scheduled WF time of the
grouped WOs related to the category)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Technician

Displays the summary of work grouped by technician with a resource implemented in the period selected.

n Technician
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each technician are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the technician) + Sum(Scheduled WF time of the
grouped WOs related to the technician)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Work settings

Displays the history of work orders whose start and end date are included in the period selected.
Displays the history of work orders with at least one resource implemented in the period selected.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
The following information is displayed:

n Start date: Format: "Day: Hour: Minute"(DateTime)

n End date: Format: "Day: Hour: Minute"(DateTime)
n Code
n Title
n Status
n Asset
n Type of work
n Technology
n Priority
n Brand
n Model
n Serial number
n Asset family
n ....

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, the grouped WOs are shown in the analysis. The Asset, Brand, Model, Supplier, Serial number
and Asset family columns are not filled in on grouped WOs
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Maintenance

Maintenance indicators enable us to measure asset performance.

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
The work orders taken into account are those with a machine downtime resource implemented in the period selected.

n Operating period: Sum of theoretical operating times of assets returned

n Number of shutdowns: Number of machine shutdown lines completed in the orders
n Length of shutdowns: Number of machine downtime completed in the orders
 n MTBF = Mean Time Between Failure. Reliability indicator, it measures the asset failure rate. Calculation = (Sum(Operating time -
Shutdown time)) / Number of shutdowns

n MTTR = Mean Time To Repair. Maintainability indicator. Calculation = (Sum(Shutdown time)) / Number of shutdowns

RMA: Reliability, Maintainability, Availability:

RMA indicators enable us to rank machines according to their values and to decide on a policy or action priorities based on the cir-
cumstances.

n Reliability = Failure rate = 1 / MTBF

n Maintainability = Repair rate = 1 / MTTR
n Availability = MTBF / (MTBF + MTTR)

The analysis displays graphs for each indicator, with consolidations per period (per week, month or year depending on the filter selected in
advanced filters.)

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WO stoppages are not taken into account in the analysis.
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WO stoppage time calculations are concerned (only for the duration of the stoppages).

Assets pareto

Displays the summary of work grouped by asset with a resource implemented in the period selected. This analysis enables us to detect the
items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the asset in comparison to the total resources used on all assets.

n Asset
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of child WOs on
each asset are added to those of the single WOs (with asset distribution taken into account in the child WO).
For example, to calculate the WF time = Sum(WF time of the WOs linked to the asset) + Sum(WF time of the grouped WOs with the asset in
a child WO) * (Child WO distribution key/Sum of the distribution keys of all the child WOs in the grouped WO)

Pareto by family

Displays the summary of work grouped by asset family with a resource implemented in the period selected. This analysis enables us to
detect the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the asset family in comparison to the total resources used on all asset families.

n Asset family
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of child WOs
spent on each family are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate the WF time = Sum(WF time of the WOs linked to an asset in the family) + Sum(WF time of the grouped WOs with
an asset in the family in a child WO) * (Child WO distribution key/Sum of the distribution keys of all the child WOs in the grouped WO)

Pareto by technology

Displays the summary of work grouped by technology with a resource implemented in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the technology in comparison to the total resources used on all technologies.

n Technology
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
 n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each technology are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of WOs related to the technology) + Sum(WF time of grouped WOs related to the tech-
nology)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Pareto by type of work

Displays the summary of work grouped by work type with a resource implemented in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the type of work in comparison to the total resources used on all types of work.

n Type of work
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each type of work are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of the WOs related to the type of work) + Sum(WF time of the grouped WOs related to
the type of work)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Cost allocation pareto

Displays the summary of work grouped by cost allocation type with a resource used in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the type of work in comparison to the total resources used on all cost allocations.

n Type of work
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each type of work are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of the WOs related to the type of work) + Sum(WF time of the grouped WOs related to
the type of work)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Responsiveness to each work order

This analysis enables us to monitor the responsiveness of work in order to see the time needed to resolve failures. It requires calculating the
work responsiveness and delay

All work orders (issued from a work request) are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent sta-
tuses). You can place a filter on work order statuses.

The result of the analysis is displayed in a table with the following information:

n WO
n Asset
n Asset family
n Type of work
n Technology
n Priority
n Response time: Max(Actual End Date/Time of resources) - Date/Time WR created
n Delay: Max (Actual End Date/Time of resources) - Deadline Date/Time on the WR (No delay calculated if the WR deadline
Date/Time is not entered)

Sorting is in order of decreasing deadline.

If work is not delayed, nothing will appear in the corresponding box.
A graph displays the change in response time month by month -> For each month the average time for all the month's work orders is cal-
culated.

Another graph displays the change in the quantity and lateness of work month by month -> For each month, the quantity and average delay
of all the month's late work orders are displayed.

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Subcontractor

Displays the summary of work grouped by partner/subcontractor with a resource implemented in the period selected.

n Partner
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Preventive work completion rate

Indicates the completion rate of preventive work so that the percentage of work still needing to be carried out over a period of time can be
viewed.

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

TABLE 1

n Number of jobs to carry out: Total number of preventive maintenance occurrences scheduled to be completed during the selec-
ted period for the entity in the column. (including those that have been converted into WOs and those that have not, regardless of
order status)
n Number of jobs completed: The number of occurrences converted into orders whose orders are closed (or equivalent) and have
completed resource lines during the selected period for the entity in the column.
n Number of jobs not completed: The number of occurrences that have not been converted into a WO during the selected period
for the entity in the column, or, which have been converted and whose WO has been closed (or equivalent) without a completed
line.
 n Jobs in progress: Number of occurrences converted into WOs (not Closed or Cancelled or equivalent)
n jobs in progress by status: overall number including the reference status + their equivalent statuses
n jobs in progress - detail by status and equivalent status

TABLE 2

n Rate of jobs completed (%) = number of occurrences converted into orders and whose orders are closed (or equivalent) with com-
pleted /total number of occurrences lines for the entity in the column during the selected period.
n Rate of jobs not completed (%) = number of occurrences not converted into orders, or converted into orders and whose orders
are cancelled or closed (or equivalent) but without completed/total number of occurrences lines for the entity in the column
during the selected period.
n Rate of jobs in progress (%): Number of occurrences converted into WOs (not Closed or Cancelled or equivalent)/total number of
occurrences for the entity in the column during the selected period.
n jobs in progress by status: overall number including the reference status + their equivalent statuses/total number of
occurrences for the entity in the column over the selected period.
n jobs in progress: detail of each reference status and each equivalent status/total number of occurrences for the entity in
the column over the selected period.

Reference dates taken into account for the application of conversion rates

Assets pareto
Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Pareto by asset family

Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Pareto by type of work

Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Pareto by technology
Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Summary by technician category

Planned cost -> Start date of the planned labour line
Actual cost -> Start date of the labour completion line
Summary by technician
Planned cost -> Start date of the planned labour line
Actual cost -> Start date of the labour completion line

Summary by subcontractor category

Planned cost -> Start date of the planned subcontracting line
Actual cost -> Start date of the subcontracting completion line

Summary by subcontractor
Planned cost -> Start date of the planned subcontracting line
Actual cost -> Start date of the subcontracting completion line

Work analyses
The Analyses --> Work analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for work are:

n Failure tree
n Subcontractor category (work costs per subcontractor category)
n Technician category (work costs per technician category)
n Technician (work costs per technician)
n Work (history of work orders)
n Maintenance (MTBF, MTTR, failure rate, breakdown rate)
n Asset pareto (work costs per asset)
n Family pareto (work costs per asset family)
n Technology pareto (work costs per technology)
n Work type pareto (work costs per type of work)
n Cost allocation pareto (work costs per cost allocation)
n Responsiveness to each work order
n Subcontractor (work costs per subcontractor)
n Preventive work completion rate

Prices are displayed in the logged in user's currency. The conversion rate applied depends on the reference date. See the reference dates at
the bottom of the page for applying conversion rates here
The user display language is taken into account to display the item descriptions (Asset, Status, Technology, Type of work, Priority, Asset
family, Technician category, Subcontractor category, etc.)

Select the periods, the indicators to display, add the chosen filters, select the entity/ies with analyses then click the button

.
The table is displayed at the bottom of the page. Click on the arrows to view the different indicators:

Advanced filters

The filters available are

n Start date : Required; Format: "Date"(Date)

n End date : Required; Format: "Date"(Date)

n Indicators : List of indicators to be displayed. Multiple selection is possible. All the analyses selected will be displayed in the report
part.
n Top : For graphs, displays the top [No. selected] most expensive items. If no filter, displays all the results. E.g. for the technologies
pareto, will display the top 10 most expensive technologies.
n Asset : If the "With children" tick box is active, the result will take into account the child assets of the asset selected.
n Asset family : If the "With children" tick box is active, the result will take into account the child asset families of the asset family
selected.
n Cost allocation: If the "With children" tick box is active, the result will take into account the child cost allocations of the cost allo-
cation selected.
n Type of work
n Priority
n Technology
n Period : Selection list of period: Week, Month or Year. This filter is only applicable for maintenance indicator graphs
n Status : List of choices of WO statuses (reference statuses and equivalent). If no status is selected, all the statuses are taken into
account in the result. This filter is applicable for the indicators:
o Work (history of work orders).
o Assets pareto
 o Asset families pareto
o Work types pareto
o Technologies pareto
o Summary by technician category
o Summary by technician
o Summary by subcontractor category
o Summary by subcontractor
o Maintenance indicators
o Work order responsiveness

The other indicators are only based on closed orders (or equivalent):
o Failure tree
o Preventive work completion rate (work completed)

n Entity : Required. Visible only if the multi-organisation module is enabled. The list of entities displays non-archived entities to
which the user is associated. When a filter is applied to entities, only the work orders associated with these entities are taken into
account in the results.
n Archived Grouped WOs/ WO : Choices: “Yes”, “No”, “All”, with a default value of “No”.

Failure tree

This analysis searches the diagnostics used in the work orders. The objective is to display the links between the work orders and their
effects, causes and remedies.

It uses the following filters: Start date, End date, Asset, Asset family, Cost allocation, Work type, Priority, Technology and Entity. It does not
use the Top, Period or Status filters.

For a work order to be displayed, its start and end dates must be between the filter start date and end date.

Only work orders with closed or equivalent status are included.

The links are displayed in tree format, as set out below:

Effect1 contained in an order
Cause1 linked to the effect contained in an order
Remedy1 linked to the cause contained in an order
Order1 including the effect/cause/remedy trio
Order2 including the effect/cause/remedy trio
Remedy2 linked to the cause contained in an order
Order1 including the effect/cause/remedy trio
Order2 including the effect/cause/remedy trio
Cause2 linked to the effect contained in an order
...
Effect2 contained in an order
...

If any of the orders do not include an effect, an “Effect not entered” line is displayed to account for them
For each of the effects, if any of the orders do not include a cause, a “Cause not entered” line is displayed to account for them
For each effect/cause, if any of the orders do not include a remedy, a “Remedy not entered” is shown to account for them

Occurrences view
Each effect line displays the number of times said effect is used in an order + the percentage of the total number of effects used in the
orders that this number represents.

Each cause line related to an effect displays the number of times said cause has been used in an order related to this effect + the percentage
of the total number of causes used in orders related to this effect that this number represents.

Each remedy line related to an effect and a cause displays the number of times said remedy is used in an order related to this effect and
cause + the percentage of the total number of remedies used in orders related to this effect and cause that this number represents.

The items are sorted by decreasing occurrence on each level

Time view
Indicates which diagnostic elements take the most time

Each order line displays the sum of the WF and SC hours spent on the order.
The orders are sorted by decreasing time spent

Each remedy line displays the sum of the time spent on orders related to the effect/cause/remedy trio
+ the percentage of the total time taken by orders related to the effect/cause duo that this time represents

Each cause line displays the sum of the time taken on orders related to the effect/cause duo
+ the percentage of the total time taken by orders related to the effect that this time represents

Each effect line displays the sum of the time spent on orders related to this effect
+ the percentage of the total time taken by these orders that this time represents

Costs view
Shows which diagnostic items generate most costs

Each order line displays the sum of the WF, SC, parts and stoppage costs completed on the order.

Each remedy line displays the sum of the costs spent on orders related to the effect/cause/remedy trio
+ the percentage of the total cost related to the effect/cause duo this cost represents

Each cause line displays the sum of the costs spent on orders related to the effect/cause duo
+ the percentage of the total cost of orders related to the effect this cost represents

Each effect line displays the sum of the costs spent on orders related to this effect
+ the percentage of the total cost of orders this cost represents

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Subcontractor category

Displays the summary of work grouped by partner/subcontractor category with a resource implemented in the period selected
 n Partner category
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses)... Possibility of placing a filter on
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each category are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the category) + Sum(Scheduled WF time of the
grouped WOs related to the category)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Technician category

Displays the summary of work grouped by technician category with a resource implemented in the period selected

n Technician category
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each category are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the category) + Sum(Scheduled WF time of the
grouped WOs related to the category)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Technician
Displays the summary of work grouped by technician with a resource implemented in the period selected.

n Technician
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
for each technician are added to those of the single WOs
For example, to calculate scheduled times = Sum(Scheduled WF time of the WOs related to the technician) + Sum(Scheduled WF time of the
grouped WOs related to the technician)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Work settings

Displays the history of work orders whose start and end date are included in the period selected.
Displays the history of work orders with at least one resource implemented in the period selected.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
The following information is displayed:

n Start date: Format: "Day: Hour: Minute"(DateTime)

n End date: Format: "Day: Hour: Minute"(DateTime)
n Code
n Title
n Status
n Asset
n Type of work
n Technology
n Priority
n Brand
n Model
n Serial number
n Asset family
n ....

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
Note: if the grouped work module is enabled, the grouped WOs are shown in the analysis. The Asset, Brand, Model, Supplier, Serial number
and Asset family columns are not filled in on grouped WOs
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Maintenance

Maintenance indicators enable us to measure asset performance.

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
The work orders taken into account are those with a machine downtime resource implemented in the period selected.

n Operating period: Sum of theoretical operating times of assets returned

n Number of shutdowns: Number of machine shutdown lines completed in the orders
n Length of shutdowns: Number of machine downtime completed in the orders

n MTBF = Mean Time Between Failure. Reliability indicator, it measures the asset failure rate. Calculation = (Sum(Operating time -
Shutdown time)) / Number of shutdowns

n MTTR = Mean Time To Repair. Maintainability indicator. Calculation = (Sum(Shutdown time)) / Number of shutdowns

RMA: Reliability, Maintainability, Availability:

RMA indicators enable us to rank machines according to their values and to decide on a policy or action priorities based on the cir-
cumstances.

n Reliability = Failure rate = 1 / MTBF

n Maintainability = Repair rate = 1 / MTTR
n Availability = MTBF / (MTBF + MTTR)

The analysis displays graphs for each indicator, with consolidations per period (per week, month or year depending on the filter selected in
advanced filters.)

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WO stoppages are not taken into account in the analysis.
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WO stoppage time calculations are concerned (only for the duration of the stoppages).

Assets pareto

Displays the summary of work grouped by asset with a resource implemented in the period selected. This analysis enables us to detect the
items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the asset in comparison to the total resources used on all assets.

n Asset
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of child WOs on
each asset are added to those of the single WOs (with asset distribution taken into account in the child WO).
For example, to calculate the WF time = Sum(WF time of the WOs linked to the asset) + Sum(WF time of the grouped WOs with the asset in
a child WO) * (Child WO distribution key/Sum of the distribution keys of all the child WOs in the grouped WO)

Pareto by family

Displays the summary of work grouped by asset family with a resource implemented in the period selected. This analysis enables us to
detect the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the asset family in comparison to the total resources used on all asset families.

n Asset family
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of child WOs
spent on each family are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate the WF time = Sum(WF time of the WOs linked to an asset in the family) + Sum(WF time of the grouped WOs with
an asset in the family in a child WO) * (Child WO distribution key/Sum of the distribution keys of all the child WOs in the grouped WO)

Pareto by technology
Displays the summary of work grouped by technology with a resource implemented in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the technology in comparison to the total resources used on all technologies.

n Technology
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each technology are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of WOs related to the technology) + Sum(WF time of grouped WOs related to the tech-
nology)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Pareto by type of work

Displays the summary of work grouped by work type with a resource implemented in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the type of work in comparison to the total resources used on all types of work.

n Type of work
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each type of work are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of the WOs related to the type of work) + Sum(WF time of the grouped WOs related to
the type of work)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Cost allocation pareto

Displays the summary of work grouped by cost allocation type with a resource used in the period selected. This analysis enables us to detect
the items that generate the highest maintenance costs.
All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.
For resources, the report only counts resources used.
The percentages represent the share of resources used on the type of work in comparison to the total resources used on all cost allocations.

n Type of work
n Labour time and % Percentage
n Internal labour cost and % Percentage
n Subcontracting time and % Percentage
n Subcontracting cost and % Percentage
n Parts cost and % Percentage
n Downtime and % Percentage
n Shutdown cost and % Percentage
n Total cost and % Percentage

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Note: if the grouped work module is enabled, grouped WOs are not taken into account in the analysis. The time and costs of grouped WOs
spent on each type of work are added to those of the single WOs (with asset distribution being taken into account in the child WO)
For example, to calculate WF times = Sum(WF time of the WOs related to the type of work) + Sum(WF time of the grouped WOs related to
the type of work)
If filtering on an asset or asset family is selected, only that part of the distribution equating to the filtered assets is taken into account where
grouped WOs are concerned.

Responsiveness to each work order

This analysis enables us to monitor the responsiveness of work in order to see the time needed to resolve failures. It requires calculating the
work responsiveness and delay

All work orders (issued from a work request) are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent sta-
tuses). You can place a filter on work order statuses.
The result of the analysis is displayed in a table with the following information:

n WO
n Asset
n Asset family
n Type of work
n Technology
n Priority
n Response time: Max(Actual End Date/Time of resources) - Date/Time WR created
n Delay: Max (Actual End Date/Time of resources) - Deadline Date/Time on the WR (No delay calculated if the WR deadline
Date/Time is not entered)

Sorting is in order of decreasing deadline.

If work is not delayed, nothing will appear in the corresponding box.

A graph displays the change in response time month by month -> For each month the average time for all the month's work orders is cal-
culated.

Another graph displays the change in the quantity and lateness of work month by month -> For each month, the quantity and average delay
of all the month's late work orders are displayed.

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.

Subcontractor

Displays the summary of work grouped by partner/subcontractor with a resource implemented in the period selected.

n Partner
n Envisaged time
n Estimated cost
n Time spent
n Actual cost

All orders are taken into account by default: To do, In progress, Cancelled, Closed (and equivalent statuses). You can place a filter on work
order statuses.

For this indicator, the following words are displayed: "Period based on implemented resource end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
The scheduled times and estimated costs are calculated based on the resources implemented over the period selected.

Preventive work completion rate

Indicates the completion rate of preventive work so that the percentage of work still needing to be carried out over a period of time can be
viewed.

For this indicator, the following words are displayed: "Period based on work order start and end dates" under the line: "Period from
XX/XX/XXXX to XX/XX/XXXX" in the report header.
TABLE 1

n Number of jobs to carry out: Total number of preventive maintenance occurrences scheduled to be completed during the selec-
ted period for the entity in the column. (including those that have been converted into WOs and those that have not, regardless of
order status)
n Number of jobs completed: The number of occurrences converted into orders whose orders are closed (or equivalent) and have
completed resource lines during the selected period for the entity in the column.
n Number of jobs not completed: The number of occurrences that have not been converted into a WO during the selected period
for the entity in the column, or, which have been converted and whose WO has been closed (or equivalent) without a completed
line.
n Jobs in progress: Number of occurrences converted into WOs (not Closed or Cancelled or equivalent)
n jobs in progress by status: overall number including the reference status + their equivalent statuses
n jobs in progress - detail by status and equivalent status

TABLE 2

n Rate of jobs completed (%) = number of occurrences converted into orders and whose orders are closed (or equivalent) with com-
pleted /total number of occurrences lines for the entity in the column during the selected period.
n Rate of jobs not completed (%) = number of occurrences not converted into orders, or converted into orders and whose orders
are cancelled or closed (or equivalent) but without completed/total number of occurrences lines for the entity in the column
during the selected period.
n Rate of jobs in progress (%): Number of occurrences converted into WOs (not Closed or Cancelled or equivalent)/total number of
occurrences for the entity in the column during the selected period.
n jobs in progress by status: overall number including the reference status + their equivalent statuses/total number of
occurrences for the entity in the column over the selected period.
n jobs in progress: detail of each reference status and each equivalent status/total number of occurrences for the entity in
the column over the selected period.

Reference dates taken into account for the application of conversion rates

Assets pareto
Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Pareto by asset family

Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Pareto by type of work

Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line
Pareto by technology
Internal cost -> Start date of the labour completion line
External cost -> Start date of the subcontracting completion line
Part cost -> Date of the part completion line
Shutdown -> Start date of the shutdown completion line

Summary by technician category

Planned cost -> Start date of the planned labour line
Actual cost -> Start date of the labour completion line

Summary by technician
Planned cost -> Start date of the planned labour line
Actual cost -> Start date of the labour completion line

Summary by subcontractor category

Planned cost -> Start date of the planned subcontracting line
Actual cost -> Start date of the subcontracting completion line

Summary by subcontractor
Planned cost -> Start date of the planned subcontracting line
Actual cost -> Start date of the subcontracting completion line

Stock analyses
The Analyses --> Stocks analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for stocks are:

n Stock status

The user's data language is taken into account for displaying item descriptions (parts, warehouses, etc.)

Select the periods, the indicator to display, add the desired filters, select the entity/ies for analyses then click the button.

Advanced filters

The filters available are

n Stock on (date)
n Indicators : Selection list: Details by family/Details by storage location/Details by warehouse/Overall stock/Summary by family/
Summary by storage location/Summary by warehouse
n Part : List of choices or selection pop-in
n Part families
n Manufacturer
n Manufacturer reference
 n Warehouse
n Storage location
n Supplier
n Asset
n In stock : Selection list: Yes/No/All
n Entity : Visible only if multi-organisation module is enabled. The list of entities displays the unarchived entities to which the user is
linked. When a filter is applied to entities, only the work orders linked to these entities are taken into account in the results.
n Filed : Yes/No/All By default: "No"

Order of presentation of advanced filters:

1st line: Stock on (date) - Indicators

2nd line: Entity - Warehouse - Storage location
3rd line: Asset - Part family - Part
4th line: Supplier - Manufacturer - Manufacturer reference

Filters, apart from Manufacturer reference and In stock, only refer to data that belongs to at least one of the entities selected in the filter,
enabling analysis performance to be improved...

Stock status

The analysis displays the stock status for each part and for each warehouse on a given date, the start date selected in the filter. All the move-
ments made before this date are taken into account. The end date filter is not used for this analysis.
The first page displays the advanced filters that were selected.
Prices are displayed in the logged in user's currency.

n Part: extracted with its Code and Description, the Manufacturer reference and the Supplier reference of the main supplier
n Warehouse
n Storage location
n Under stock management: Yes/No
n Part families
n Quantity in stock: Calculates the quantity of parts present on the date of the status report at 00:00 for the warehouse concerned.
n Unit: Displays the part storage unit
n WAUP: Displays the WAUP of the part on the date of the status report at 00:00 for the warehouse concerned. The WAUP is dis-
played in the logged-in user's currency.
n Value: Quantity in stock * WAUP
Total Value: total value of the stock (sum of the Value column)

Parts not moved and are taken into account.

Movements on parts that are not in stock are differentiated, with the "In stock" column (Yes/No).
By default, if the "In stock" filter is blank, the analysis only displays parts kept in stock.

This Stock status, displayed by default on the second page of the analysis, corresponds to the Overall stock choice of the Indicators advan-
ced filter.

Using the Indicators advanced filter

The stock value, displayed on the second page takes on different characteristics according to the choice of filter:
l Details by family (displayed by default on the 6th page)
o displays the value of the parts stock by warehouse and part family
o warehouse tables are sorted in alphabetical order of Codes(Warehouse) and sub-sorted in alphabetical order of Codes

(Part family)
o Part column displays, on each line, Code(Part)-Description(Part)-Manufacturer reference(Part)- Supplier reference(Part)
o the last line of each warehouse table displays the total value of the warehouse stock
o warehouses whose Stock value= 0 are displayed
o families whose Stock value= 0 are displayed
o the last line on the page displays the total Stock value (sum of all the warehouses)

l Details by storage location (displayed by default on the 8th page)

o displays the value of the parts stock by storage location
o in each table header: "Storage location: Code(Storage location)-Description(Storage location)"
o storage location tables are sorted in alphabetical order of Codes(Storage location)
o Part column displays, on each line, Code(Part)-Description(Part)-Manufacturer reference(Part)- Supplier reference(Part)
o the last line of each storage location table displays the total value of the storage location
o storage locations whose Stock value= 0 are displayed
o the last line on the page displays the total Stock value (sum of all the warehouses)

l Details by warehouse (displayed by default on the 4th page)

o displays the value of the parts stock by warehouse
o in each table header: "Warehouse: Code(Warehouse)-Description(Warehouse)"
o warehouse tables are sorted in alphabetical order of Codes(Warehouse)
o Part column displays, on each line, Code(Part)-Description(Part)-Manufacturer reference(Part)- Supplier reference(Part)
o the last line of each warehouse table displays the total value of the warehouse stock
o warehouses whose Stock value= 0 are displayed
o the last line on the page displays the total Stock value (sum of all the warehouses)

l Summary by family (displayed by default on the 5th page)

o displays the value of the stock by part family
o on each line, the Part family column displays Code(Part family)-Description(Part family)
o the Part family column is sorted in alphabetical order of Codes(Part family)
o families whose Stock value= 0 are displayed
o a "Not entered" section groups and totals all the parts that do not have a family assigned

l Summary by storage location (displayed by default on the 7th page)

o displays the value of the stock by storage location
o on each line, the Storage location column displays Code(Part family)-Description(Part family)
o the Storage location column is sorted in alphabetical order of the Codes(Storage location)
o storage locations whose Stock value= 0 are displayed
 l Summary by warehouse (displayed by default on the 3rd page)
o displays the value of the stock by warehouse
o on each line, the Warehouse column displays Code(Warehouse)-Description(Warehouse)
o the Warehouse column is sorted in alphabetical order of Codes(Warehouse)
o warehouses whose Stock value= 0 are displayed

Stock calculation to date

General rules

Case 1. Part not in stock without status change since its creation
No change, the stock is 0 as well as the stock value.

Case 2. Part in stock without status change since its creation

- The basic calculation value is the stock value on the day’s date
- We take into account all the movements until the stock calculation date

Case 3. Part with status change since its creation

We look at what the part status was on the stock calculation date.

If part not in stock: see Case 1.

If part in stock:
- The basic calculation value is the stock value on the day’s date
- We only take into account the movements of periods when the part was in stock

When we want to edit the Stock analysis on the date DD/MM/YYYY, we display "DD/MM/YYYY 23:59" in the header of the results calculated
according to the part stock management rules above.

Contract analyses
The Analyses --> Contracts analysis sub-menu is visible for Supervisor and Guest account types.

The indicators available for contracts are:

n List of contracts
n Grouping by contract
n Grouping by asset family
n Grouping by subcontractor
n Grouping by technology
n Grouping by type of work
n Grouping by type of contract
n Grouping by asset

The different indicators display a summary of the activity of existing contracts.

Advanced filters
The filters available are
 n Start date
n End date
n Title :
n Status
n Entities
n Subcontractor
n Manager
n Type of contract
n Type of work
n Technology
n Indicators

Filters on dates are not applicable for the "Contract list" indicator.

Add the desired filters and select the entity(ies) with analyses, then click on the button.

The contract list indicator displays the following columns:

n Subcontractors
n Title
n Status
n Manager
n Type of contract
n Type of work
n Technology
n Number of amendments
n Asset family (header of the current amendment)
n Asset (header of the current amendment)
n Cost allocation (header of the current amendment)
n Cost (header of the current amendment)
n Date of effect of the current amendment
n End date of the current amendment
n Tacit renewal (yes/no) of the current amendment
n Number of WOs planned per period for the current amendment

Each grouping table has the following columns:

- Grouping item
- Number of WOs planned in the period selected
- Number of WOs created
- Rate (= Number of WOs created/Number of WOs planned)

The graphs visually represent the completion rate for work orders in a contract by grouping item selected. The completion rate monitors
the progress of work on assets covered by a contract.

l On the x-axis is the completion rate for orders on an asset which is under a contract, in the following tranches 0%, 0-20%, 20-40%,
40-60%, 60-80%, 80-100%, 100%.
l On the y-axis is the number of assets concerned by each tranche.
Inventory analyses
The Analyses --> Inventory analysis sub-menu is visible for Supervisor and Guest account types.

The indicators available for inventories are:

n Inventory discrepancies

The user’s display language is taken into account for displaying item descriptions (parts, storage locations, etc.)

Select the warehouse and inventory, apply the filters desired, then click the button:

Advanced filters
The filters available are:

n Warehouse : Selection list

n Inventory : Selection list (required and unique)
n Inventory movement Selection list: All (displays all parts, with discrepancy=0 for parts without discrepancy)/With discrepancies
(only displays parts with a discrepancy)
n Status : Closed/Done
n Entities : List of choices (only the user’s are suggested)

Inventory discrepancies

The analysis displays the discrepancies of a given inventory for a given warehouse (for each part on a given date) (the start date selected in
the filter).
All the inventory movements made may be taken into account, or only those with discrepancies. (The end date filter is not used for this ana-
lysis.)

n Parts
n Description
n Storage location
n Stock: following characteristics:

1. Date: date of inventory reading

2. Before inventory: in quantity of parts
3. After inventory: in quantity of parts
4. Inventory discrepancies: in quantity of parts, highlighted with a different colour depending on whether they are positive of nega-
tive
5. Value at FIFO: based on the general valuation type setting (Settings/Configuration/General settings), expressed in the Warehouse
currency

The sum of discrepancies appears at the bottom of the analysis table.

Analyses - Preventive annual schedule
The Analyses --> Preventive Annual Schedule sub-menu is visible to Supervisor account types.

It enables you to monitor the status of PW occurrences.

The preferred settings are defined by 3 blocks:

n Default settings
n Selection of fields displayed
n Actions analysed

Default settings

3 settings are proposed:

l Default period: Drop-down list with the choices:

n Current year (from 01/01 to 31/12)
n Rolling period (D to D+365): default value
l Type of work: List of multiple choices; ‘All’ by default. Offers the types of work used in PWs.
l Grouping: Drop-down list with the choices:
n Asset: default value
n Asset family
n Parent asset
n PW title
n Cost allocation
n Contract

Selection of fields displayed

Offers the fields displayed in the line header with an indication of the order number, based on the principle of mapping an import/export:

l Asset/Code
l Asset/Description
l PW/Code
l PW/Title

Actions analysed

Offers the list of actions analysed in tabular form:

Untriggered occurrences: Corresponds to the dates of untriggered PW occurrences planned over the status launch period.
WO to do or equivalent: On the status launch date (day's date), the WO is in "To do" or equivalent status and the day's date is before or on
the WO's deadline.
WO in progress or equivalent: On the status launch date (day's date), the WO is in "In progress" or equivalent status and the day's date is
before or on the WO's deadline.
WO done/closed or equivalent: On the status launch date (day's date), the WO is in "Done/Closed" or equivalent status and the date the
status is changed to "Done" or equivalent status is before or on the WO's deadline. If "Closed" and no change in "Done" status, the check is
performed on the date the status is changed to "Closed".
WO to do or equivalent, late: On the status launch date (day's date), the WO is in "To do" or equivalent status and the day's date is after or
on the WO's deadline.
WO in progress or equivalent, late: On the status launch date (day's date), the WO is in "In progress" or equivalent status and the day's
date is after or on the WO's deadline.
WO done/closed or equivalent, late: On the status launch date (day's date), the WO is in "Done/Closed" or equivalent status and the date
the status is changed to "Done" or equivalent status is after or on the WO's deadline. If "Closed" and no change in "Done" status, the check
is performed on the date the status is changed to "Closed".
WO cancelled: On the status launch date (day’s date), the WO is in "Cancelled" status.

Select the filters desired, then click the button.

The table is displayed at the bottom of the page. Click the arrows to view the different indicators (corresponding to the Selection of fields dis-
played):

Advanced filters

The filters available are:

 n Entity : List of user entity multiple choices; ‘All’ by default.
n Start date : Required; Editable; Format: "Day"(Date); Initialised by the Analysis Settings menu default settings.
n End date : Required; Editable (cannot exceed Start date + 365 d); Format: "Day"(Date); Initialised by the Analysis Settings menu
default settings.
n Type of work : List of multiple choices; "All" by default; Editable; Initialised by the Analysis Settings menu default settings (if the
values do not match the choice of entities, work types are deleted from the filter). Offers the types of work used in PWs.
n Grouped by: Drop-down list with single choice; Editable; Initialised by the Analysis Settings menu default settings. Indicates the
PW grouping method:
o Asset
o Asset families
o Parent asset
o PW title
o Cost allocation
o Contract

n Action: List of multiple choices; ‘All’ by default; Editable; Initialised by the Analysis Settings menu default settings. Offers the fol-
lowing actions:
o WO to do or equivalent
o WO in progress or equivalent
o WO done/closed or equivalent
o WO to do or equivalent, late
o WO in progress or equivalent, late
o WO done/closed or equivalent, late
o WO cancelled
o Completion time limit
o Planned occurrences
o Untriggered occurrences

n Field selection : List of multiple choices; ‘All’ by default; Editable; Initialised by the Analysis Settings menu default settings. Offers
the following fields:
o Asset
o Preventive work/Code
o Preventive work/Name

Process

Presentation

The table copies the different columns selected from the settings with a grouping according to the choice in settings.
Depending on the choice of dates, the corresponding months then the corresponding weeks are shown.
The current week is shown by a yellow background.

The actions selected and their corresponding icon are shown in the legend in a separate tab.

General rules
Archived PWs are not taken into account.
PWs with no occurrence or WOs generated in the period are not displayed.
For multi-asset PWs, only the grouped WO is displayed. No view of Child WOs.
The completion time limits are shown in relation to the WO deadline.

Actions analysed
The reference date is the occurrence date.
In the planned week of the occurrence, the action is indicated by:
- the icon or
- the background colour corresponding to the occurrence status or
- the background colour corresponding to the WO generated on the report launch date.
Part consumption analyses
The Analyses --> Part consumption analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for part consumption are:

n Details by date
n Details by part and warehouse
n Details by part family and warehouse
n Details by cost allocation and warehouse
n Details by asset and warehouse

The different indicators display a summary of the activity of existing part consumption.
Movement cancellations and corrections are taken into account.
The user's display language is taken into account for displaying item descriptions (parts, warehouses, assets, etc.).

Select the warehouse, part family and asset family, apply the filters desired, then click the button:

Advanced filters
The filters available are:

n Start date: Date field or selection pop-in ("Calendar" icon).By default, set to "D-1" month (day’s date). Filter on the movement
date.
n End date: Date field or selection pop-in ("Calendar" icon).By default, set to "D" (day’s date). Filter on the movement date.
n Indicators : Selection list.
n Warehouse : Selection list. Blank by default.
n Storage location : Selection list. Blank by default.
n Part families : Typeahead/standard part family search window, filtered to the logged- in user's entity/ies or selection pop- in
("Twins" icon) + Check box: "With children". Blank by default.
n Part: Typeahead/standard part search window, filtered to the logged-in user’s entity/ies or selection pop-in. ("Twins" icon). Blank
by default.
n Cost allocation: Typeahead/standard cost allocation search window, filtered to the logged-in user's entity/ies or selection pop-in
("Twins" icon) + Check box: "With children". Blank by default.
n Asset family : Typeahead/standard asset family search window, filtered to the logged- in user's entity/ies or selection pop- in
("Twins" icon) + Check box: "With children". Blank by default.
n Asset: Typeahead/standard asset search window, filtered to the logged-in user's entity/ies or selection pop-in ("Twins" icon) +
Check box: "With children". Blank by default.
n In stock : Yes/No/All.
n Filed : Yes/No/All. "No" by default.
n Entity : List of choices (only the user’s are suggested)

Details by date
This analysis enables you to obtain the list sorted by ascending date of part issue movements over the period selected and according to the
filters put in place.
Each part type resource is displayed on only one line.
Unlisted parts, which have their own indicator, do not appear in this analysis.

The different movements may come from:

- Part managed, not managed or not referenced type resource implemented from a WO
- Part managed, not managed or not referenced type resource implemented from a Grouped WO
- Part issue type movement
- Transfer type movement where the warehouses selected are Original Warehouse

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Details by date"

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:

n Date: Movement date in Date format only.

n Code: Part code. Blank if the part is not listed.
n Description: Part description.
n Quantity: Quantity of the part in the movement.
n Unit: Description of the part unit used in the movement.
n Cost: Total movement cost (Unit price at movement x Quantity) in the user’s currency. If the movement currency is different, take
the currency conversion in effect on the movement date.
n Warehouse: Description of the warehouse attached to the movement. Original warehouse for a transfer. For non-listed parts, the
field may be blank.
n Storage location: Description of the part storage location.
n Operation type: WO/Grouped WO/Movement/Transfer.
n Operation code: WO/Grouped WO for the corresponding operation types. Blank for Movement and Transfer.
n Title: WO/Grouped WO/movement/transfer title (according to the operation type). May be blank for Movement and Transfer
because title not required.
n Cost allocation: Description of the cost allocation if entered in the WO, Grouped WO, movement or transfer (depending on ope-
ration type).
n Asset: Code - Description (WO asset). Words "Several assets" if Grouped WO. Code - Description (movement/transfer asset, if ente-
red).
n Contract: Title (Contract) if the movement originates from a WO/grouped WO linked to a contract.
n User: Last name - First name (movement origin). Equivalent to the Used field of the List of movements.

For the indicator Details by date, PDF printing is not possible.

Only an EXCEL export can be created, on a specific tab

Details by part and warehouse

This analysis enables you to obtain the list of part issue movements sorted by part then by warehouse (one line per movement sorted by
date).
Each part type resource is displayed on only one line.
Unlisted parts, which have their own indicator, do not appear in this analysis.
Part presentation is in alphabetical order of the Codes (Part). Parts that are not listed are at the end of the list (no code).
The Part field returns the Code - Description (Part) pair or Description (Part) only for those that are not listed.
The last line of each part displays the sum of the part's costs.
Warehouse presentation is in alphabetical order of the Codes (Warehouse).
The Warehouse field returns the Code - Description pair (Warehouse).
The last line of each warehouse displays the sum of the warehouse's costs.
The last line of the grid displays the total value of the costs (sum of the different parts).

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Details by part and warehouse"

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:

n Date: Movement date in Date format only

n Quantity: Quantity of the part in the movement.
n Unit: Description of the part unit used in the movement.
n Asset: Code - Description (WO asset). Words "Several assets" if Grouped WO. Code - Description (movement/transfer asset, if ente-
red).
n Cost: Total movement cost (Unit price at movement x Quantity) in the user’s currency. If the movement currency is different, take
the currency conversion in effect on the movement date.

In the EXCEL export, the Details by part and warehouse indicator has a specific tab.

Details by part family and warehouse

This analysis enables you to obtain the list of part issue movements sorted by part family then by warehouse.
Unlisted parts, which have their own indicator, do not appear in this analysis.

If one part has several issue movements over the period in the same warehouse and in the same stock unit then only one line is displayed
totalling the quantities and costs.

The parts are sorted by family in order of the Code (Part).

Family presentation is in alphabetical order of the Codes (Part family).
The Part family field returns the Code - Description pair (Part family).
The last line of each family displays the sum of the family’s costs.
Warehouse presentation is in alphabetical order of the Codes (Warehouse).
The Warehouse field returns the Code - Description pair (Warehouse).
The last line of each warehouse displays the sum of the warehouse's costs.
The last line of the grid displays the total value of the costs (sum of the different families).

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Details by part family and warehouse"

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:
 n Code: Blank if the part is not listed.
n Description: Text field.
n Quantity: Total quantity of the part in the movement with the same unit.
n Unit: Description of the part unit used in the movement.
n Cost: Sum of the costs of movements with the same unit in the user's currency. If the movement currency is different, take the cur-
rency conversion in effect on the movement date.

In the EXCEL export, the Details by part family and warehouse indicator has a specific tab.

Details by cost allocation and warehouse

This analysis enables you to obtain the list of part issue movements sorted by cost allocation then by warehouse.

If one part has several issue movements over the period in the same warehouse and in the same stock unit then only one line is displayed
totalling the quantities and costs.

The parts are sorted by family in order of the Code (Part).

Cost allocation presentation is in alphabetical order of the Codes (Cost allocation).
The Cost allocation field returns the Code - Description pair (Cost allocation).
The last line of each cost allocation displays the sum of the cost allocation’s costs.
Warehouse presentation is in alphabetical order of the Codes (Warehouse).
The Warehouse field returns the Code - Description pair (Warehouse).
The last line of each warehouse displays the sum of the warehouse's costs.
The last line of the grid displays the total value of the costs (sum of the different cost allocations).

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Details by cost allocation and warehouse"

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:

n Code: Blank if the part is not listed.

n Description: Description (Part). Text field.
n Quantity: Total quantity of the part in the movement with the same unit.
n Unit: Description of the part unit used in the movement.
n Cost: Sum of the costs of movements with the same unit in the user's currency. If the movement currency is different, take the cur-
rency conversion in effect on the movement date.

In the EXCEL export, the Details by cost allocation and warehouse indicator has a specific tab.

Details by asset and warehouse

This analysis enables you to obtain the list of part issue movements sorted by asset then by warehouse.

If one part has several issue movements over the period in the same warehouse and in the same stock unit then only one line is displayed
totalling the quantities and costs.
The parts are sorted by family in order of the Code (Part).
Asset presentation is in alphabetical order of the Codes (Asset).
The Asset field returns the Code - Description pair (Asset).
The last line of each asset displays the sum of the asset’s costs.
Warehouse presentation is in alphabetical order of the Codes (Warehouse).
The Warehouse field returns the Code - Description pair (Warehouse).
The last line of each warehouse displays the sum of the warehouse's costs.
The last line of the grid displays the total value of the costs (sum of the different assets).

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Details by asset and warehouse"

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:

n Code: Blank if the part is not listed.

n Description: Description (Part). Text field.
n Quantity: Total quantity of the part in the movement with the same unit.
n Unit: Description of the part unit used in the movement.
n Cost: Sum of the costs of movements with the same unit in the user's currency. If the movement currency is different, take the cur-
rency conversion in effect on the movement date.

Grouped WOs are not taken into account because several assets are attached.

In the EXCEL export, the Details by asset and warehouse indicator has a specific tab.

Unlisted parts

This analysis enables you to obtain the list sorted by ascending date of part issue movements over the period selected and according to the
filters put in place.

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Unlisted parts"

Unlisted parts are sorted in order of movement date.

A line is assigned to each movement.
The last line of the grid displays the total value of the costs (sum of the different parts).

A table displays the Total cost for the period, which is the sum of costs for all the movements in the period, on the following columns:

n Date: Movement date in Date format only.

n Description: Description of the unlisted part.
n Quantity: Quantity of the part in the movement.
n Unit: Description of the part unit used in the movement (if indicated).
n Cost: Total movement cost (Unit price at movement x Quantity) in the user’s currency. If the movement currency is different, take
the currency conversion in effect on the movement date.
 n Warehouse: Description of the warehouse (if indicated, as the field may be blank).
n Cost allocation: Description of the cost allocation (if entered).
n Asset: Code - Description (WO asset). Words "Several assets" if Grouped WO. Code - Description (movement/transfer asset, if ente-
red).

In the EXCEL export, the Unlisted parts indicator has a specific tab
Order analyses
The Analyses --> Order analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for orders are:

n Orders by date
n Orders by supplier
n Orders by part
n Orders by asset

The different indicators display a summary of the activity of existing orders.

The user's display language is taken into account for displaying item descriptions (parts, warehouses, assets, etc.).

Select the warehouse, part family and asset family, apply the filters desired, then click the button:

Advanced filters

The filters available are:

n Start date: Date field or selection pop-in ("Calendar" icon).By default, set to "D-1" month (day’s date). Filter on the order creation
date.
n End date: Date field or selection pop-in ("Calendar" icon).By default, set to "D" (day’s date). Filter on the order creation date
n Indicators : Selection list. Blank by default.
n Entity : List of choices (only the logged-in user’s entities are suggested). If, after the different filters are selected, one or more enti-
ties are modified, the other filters are emptied.
n Warehouse : Multiple choice typeahead. Blank by default.
n Order statuses : Multiple choice typeahead. Proposes the list of order statuses and equivalent, except for ‘In preparation’. All by
default.
n Supplier : List of choices (partners or Suppliers = true). Blank by default.
n Part families : Typeahead/standard part family search window, filtered to the logged- in user's entity/ies or selection pop- in
("Twins" icon) + Check box: "With children". Blank by default.
n Part: Typeahead/standard part search window, filtered to the logged-in user’s entity/ies or selection pop-in. ("Twins" icon). Blank
by default.
n Cost allocation: Typeahead/standard cost allocation search window, filtered to the logged-in user's entity/ies or selection pop-in
("Twins" icon) + Check box: "With children". Blank by default.
n Asset family : Typeahead/standard asset family search window, filtered to the logged- in user's entity/ies or selection pop- in
("Twins" icon) + Check box: "With children". Blank by default.
n Asset: Typeahead/standard asset search window, filtered to the logged-in user's entity/ies or selection pop-in ("Twins" icon) +
Check box: "With children". Blank by default.
n Display order details : Boolean. Disabled by default. If enabled, the orders are unfolded to display the details.
n Filed : Yes/No/All. "No" by default.

Orders by date
This analysis enables you to obtain the list sorted by ascending date of orders over the period selected and according to the filters put in
place.

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Orders by date"

One line is displayed per order, with the possibility to see the order details.
A table displays the Total amount over the period, or the sum of order total amounts over the period.
The total amount of an order is the one shown in the Order costs block (including any discount and costs)

Columns for the order:

n Date sent: Date first moved to "Sent" status, in Date format only.
n Scheduled delivery date: Order header Scheduled delivery date field.
n Order code: Order header Code field.
n Order title: Title field of the order header.
n Supplier ref: Order header Supplier order reference code.
n Supplier: Order header Supplier field supplier name.
n Contact: Order header Contact field (First name - Last name).
n Total amount: Order cost block Total amount field.
n Currency: Order header Currency field (ISO code - Name).
n Warehouse: Order header Warehouse field Warehouse description.
n Cost allocation: Order header Cost allocation field (Code - Description).
n WO: Order header WO field (Code - Title).
n Asset: Order headerAssetfield (Code-Description).
n Status: Description of the order status field.

Columns for order details (order lines):

n Part Code: Part code. Blank if the part is not listed.

n Part description: Description of the part
n Quantity ordered: Part line quantity ordered
n Scheduled delivery date: Order line Scheduled delivery date field
n Quantity received: Order line quantity received
n Unit: Order line unit description
n Last delivery date: Order line Last delivery date field
n Amount: Order line Amount field
n Warehouse: Order line Warehouse field Warehouse description
n Cost allocation: Order line Cost allocation field (Code - Description)
n WO: Order line WO field (Code - Title)
n Asset: Order line Asset field (Code - Description)
n Balanced: Yes (box checked)/No (box unchecked)

For the indicator Orders by date, PDF printing is not possible.

Only an EXCEL export can be created, on a specific tab
Orders by supplier

This analysis enables you to obtain the list sorted in alphabetical order of the order supplier codes over the period selected and according to
the filters put in place.

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Orders by supplier"

One line is displayed per order, with the possibility to see the order details.
A table displays the Total amount over the period, or the sum of order total amounts over the period.
A total is displayed per supplier under the last details line of the last supplier order.
A general total of all the orders over the period selected is displayed on the last line.

Columns for the order:

n Date sent: Date first moved to "Sent" status, in Date format only.
n Scheduled delivery date: Order header Scheduled delivery date field.
n Order code: Order header Code field.
n Order title: Title field of the order header.
n Supplier ref: Order header Supplier order reference code.
n Contact: Order header Contact field (First name - Last name).
n Total amount: Order cost block Total amount field.
n Currency: Order header Currency field (ISO code - Name).
n Warehouse: Order header Warehouse field Warehouse description.
n Cost allocation: Order header Cost allocation field (Code - Description).
n WO: Order header WO field (Code - Title).
n Asset: Order header Asset field (Code - Description).
n Status: Description of the order status field.

Columns for order details (order lines):

n Part Code: Part code. Blank if the part is not listed.

n Part description: Description of the part
n Quantity ordered: Part line quantity ordered
n Scheduled delivery date: Order line Scheduled delivery date field
n Quantity received: Order line quantity received
n Unit: Order line unit description
n Last delivery date: Order line Last delivery date field
n Amount: Order line Amount field
n Warehouse: Order line Warehouse field Warehouse description
n Cost allocation: Order line Cost allocation field (Code - Description)
n WO: Order line WO field (Code - Title)
n Asset: Order line Asset field (Code - Description)
n Balanced: Yes (box checked)/No (box unchecked)

For the indicator Order by supplier, PDF printing is not possible.

Only an EXCEL export can be created, on a specific tab.
Orders by part

This analysis enables you to obtain the list sorted in alphabetical order of the orders' listed part codes over the period selected and accor-
ding to the filters put in place.
Unlisted parts (which have their own indicator) do not appear in this analysis.

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Orders by part"

One line is displayed per order, with the possibility to see the order details.
A table displays the Total amount for the period, which is the sum of costs for all the movements over the period.
A total is displayed per part under the last details line of the last part order: "Sum of the part line amounts".
A general total of all the orders over the period selected is displayed on the last line.

Columns for the order:

n Date sent: Date first moved to "Sent" status, in Date format only.
n Scheduled delivery date: Order header Scheduled delivery date field.
n Order code: Order header Code field.
n Order title: Title field of the order header.
n Supplier ref: Order header Supplier order reference code.
n Supplier: Order header Supplier field supplier name.
n Contact: Order header Contact field (First name - Last name).
n Total amount: Order cost block Total amount field.
n Currency: Order header Currency field (ISO code - Name).
n Warehouse: Order header Warehouse field Warehouse description.
n Cost allocation: Order header Cost allocation field (Code - Description).
n WO: Order header WO field (Code - Title).
n Asset: Order header Asset field (Code - Description).
n Status: Description of the order status field.

Columns for order details (order lines):

n Quantity ordered: Part line quantity ordered

n Scheduled delivery date: Order line Scheduled delivery date field
n Quantity received: Order line quantity received
n Unit: Order line unit description
n Last delivery date: Order line Last delivery date field
n Amount: Order line Amount field
n Warehouse: Order line Warehouse field Warehouse description
n Cost allocation: Order line Cost allocation field (Code - Description)
n WO: Order line WO field (Code - Title)
n Asset: Order line Asset field (Code - Description)
n Balanced: Yes (box checked)/No (box unchecked)
For the indicator Orders by part, PDF printing is not possible.
Only an EXCEL export can be created, on a specific tab.

Orders by asset

This analysis enables you to obtain the list sorted in alphabetical order of order asset codes or order lines linked to an asset over the period
selected and according to the filters put in place.

The first page displays the advanced filters that were selected.
The title of the second page is: "Period from Start date to End date - Currency:Currency(User)"
"Orders by asset"

One line is displayed per order, with the possibility to see the order details.
A table displays the Total amount for the period, which is the sum of costs for all the movements over the period.
A total is displayed per asset under the last details line of the last asset order.
A general total of all the orders over the period selected is displayed on the last line.

Columns for the order:

n Date sent: Date first moved to "Sent" status, in Date format only.
n Scheduled delivery date: Order header Scheduled delivery date field.
n Order code: Order header Code field.
n Order title: Title field of the order header.
n Supplier ref: Order header Supplier order reference code.
n Supplier: Order header Supplier field supplier name.
n Contact: Order header Contact field (First name - Last name).
n Total amount: Order cost block Total amount field.
n Currency: Order header Currency field (ISO code - Name).
n Warehouse: Order header Warehouse field Warehouse description.
n Cost allocation: Order header Cost allocation field (Code - Description).
n WO: Order header WO field (Code - Title).
n Status: Description of the order status field.

Columns for order details (order lines):

n Part Code: Part code. Blank if the part is not listed.

n Part description: Description of the part
n Quantity ordered: Part line quantity ordered
n Scheduled delivery date: Order line Scheduled delivery date field
n Quantity received: Order line quantity received
n Unit: Order line unit description
n Last delivery date: Order line Last delivery date field
n Amount: Order line Amount field
n Warehouse: Order line Warehouse field Warehouse description
n Cost allocation: Order line Cost allocation field (Code - Description)
n WO: Order line WO field (Code - Title)
n Balanced: Yes (box checked)/No (box unchecked)
For the indicator Orders by asset, PDF printing is not possible.
Only an EXCEL export can be created, on a specific tab.
Activity analyses
The Analyses --> Activity analysis sub-menu is visible for Supervisor and Guest account types.
The indicators available for activities are:

n Work orders
n Work requests

The different indicators display a summary of existing activities.

The user's display language is taken into account for displaying item descriptions (parts, warehouses, assets, etc.).

Select the start and end dates, assets, asset family, apply the filters desired, then click the button:

Advanced filters

The filters available are:

n Start date: Date field or selection pop-in ("Calendar" icon).By default, set to "D-1" month (day’s date). Filter on the order creation
date.
n End date: Date field or selection pop-in ("Calendar" icon).By default, set to "D" (day’s date). Filter on the order creation date
n Indicators : Selection list. Blank by default.
n Entity : List of choices (only the logged-in user’s entities are suggested). If, after the different filters are selected, one or more enti-
ties are modified, the other filters are emptied.
n Asset family : Typeahead/standard asset family search window, filtered to the logged- in user's entity/ies or selection pop- in
("Twins" icon) + Check box: "With children". Blank by default.
n Asset: Typeahead/standard asset search window, filtered to the logged-in user's entity/ies or selection pop-in ("Twins" icon) +
Check box: "With children". Blank by default.
n Priority : Selection list. Blank by default.
n Downtime : Yes/No/All. "No" by default.
n Filed : Yes/No/All. "No" by default.

Work orders

This analysis provides a list of WOs and grouped WOs, sorted by descending date and then by alphabetical WO code, of the tech-
nicians/contractors over the period selected and according to the filters put in place.

Columns:

n Work date: Labour/Subcontractor resource end date.

n WO code: Code field of the WO/Grouped WO header.
n WO title: Title field of the WO/Grouped WO header.
 n Priority: Priority code of the WO/Grouped WO to which the resource is assigned.
n Parent Asset Code: Parent asset code of the WO asset to which the resource is assigned (empty if grouped WO).
n Parent Asset Description: Parent asset description of the WO asset to which the resource is assigned (empty if grouped WO).
n Asset Code: Code of the WO asset to which the resource is assigned (empty if grouped WO).
n Asset Description: Description of the WO asset to which the resource is assigned (empty if grouped WO).
n Comments: Paired comments of the WO/Grouped WO to which the resource is assigned (skip to the line for the new comment if
paired).
n Issuer: Last name + First name of the WO/Grouped WO to which the resource is assigned.
n WO Status: Description of the status of the WO/Grouped WO to which the resource is assigned. Consideration of equivalent sta-
tuses.
n Technician: We wish to pair the Last name/First name of the technician + Actual Duration + Start time - End time of the resource.
n Subcontractor: We wish to pair the Last name/First name of the technician + Actual Duration + Start time - End time of the
resource.
n Actual WF duration: Cumulative Labour and Subcontractor time to work date.
n Consumed parts: Yes/No. Yes if there is at least one "Part" type resource line regardless of its date.
n Downtimes: Value Yes/No if machine stopped yes/no, or Yes if there is a "Machine stop" type resource line.
n Work Type: Work type code of the WO/Grouped WO to which the resource is assigned.
n Technology: Technology code of the WO/Grouped WO to which the resource is assigned.
n Cost allocation: Cost allocation code of the WO/Grouped WO to which the resource is assigned.

Work requests

This analysis provides a list of WRs, sorted by descending date and then by alphabetical WR code, over the period selected and according to
the filters put in place.

Columns:

n Request Date: WR creation date.

n WR Code: Code field of the WR header.
n WR title: Title field of the WR header.
n Requester: Last name + First name of the Requester.
n Priority: Priority code of the WR.
n WR date/time deadline
n Parent Asset Code: Parent asset code of the WR asset.
n Parent Asset Description: Description of the parent asset of the WR asset.
n Asset Code: Code of the WR asset.
n Asset Description: Description of the WR asset.
n Location: WR location
n Comments: Paired comments of the WR (skip to the line for the new comment if paired).
n WR Status: Description of the WR status. Consideration of equivalent statuses.
n Downtimes: Yes/No.
n WR Type: WR type code of the WR.
n Work Type: Work type code of the WR.
n Technology: Technology code of the WR.
 n Cost allocation: Cost allocation code of the WR.
n Generated WO: Yes/No or paired codes if more than one WO from the WR.

Analyses - Analysis Settings / Preventive annual schedule

The Analyses --> Analysis Settings sub-menu is accessible to Supervisor account types.

A drop-down list of analyses displays the blocks required for configuring these analyses — including placing default settings.

Currently, the drop-down list shows: Preventive annual schedule, MX Analytics.

 Data imports/exports settings

Data imports/exports settings

List of imports/exports

The data imports/exports can only be accessed with a Supervisor account and from the menu [Settings-Data Imports/Exports].

Creating an import/export

An import/export can be created:

n With the button on the list of data imports/exports.

n Click on the button on the import/export form.

For further explanation of the creation of an import/export, refer to the Import/Export form.

Deleting an import/export

To delete a team:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

A confirmation message is displayed to confirm the deletion.

Archiving/De-archiving an import/export

To archive an import/export:

- 452 -
 Data imports/exports settings

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

The icon is displayed to the left of the description and the title, indicating that the import/export is archived.

To de-archive, proceed as follows:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplicating an import/export

To duplicate an import/export:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplication of an import or an export duplicates all the data entered in all the blocks except the description.

Advanced filters

This block, which is closed by default, shows the following fields:

n Description: Text field. Automatic filter upon entry.

n Type: Typeahead.
n Flag: Text field.
n Field separator: Text field.
n Text delimiter: Text field.
n Decimal separator: Text field.
n Thousands separator: Text field.
n URL: Text field.
n Identification domain: Text field.
n User: Text field. User field in the Communication settings block of the Data Import/Export form used (and not the
Default user field of the Header block).
n Action: Typeahead.

- 453 -
 Data imports/exports settings

Data imports/exports settings

List of imports/exports

The data imports/exports can only be accessed with a Supervisor account and from the menu [Settings-Data Imports/Exports].

Creating an import/export

An import/export can be created:

n With the button on the list of data imports/exports.

n Click on the button on the import/export form.

For further explanation of the creation of an import/export, refer to the Import/Export form.

Deleting an import/export

To delete a team:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

A confirmation message is displayed to confirm the deletion.

Archiving/De-archiving an import/export

To archive an import/export:

- 454 -
 Data imports/exports settings

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

The icon is displayed to the left of the description and the title, indicating that the import/export is archived.

To de-archive, proceed as follows:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplicating an import/export

To duplicate an import/export:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplication of an import or an export duplicates all the data entered in all the blocks except the description.

Advanced filters

This block, which is closed by default, shows the following fields:

n Description: Text field. Automatic filter upon entry.

n Type: Typeahead.
n Flag: Text field.
n Field separator: Text field.
n Text delimiter: Text field.
n Decimal separator: Text field.
n Thousands separator: Text field.
n URL: Text field.
n Identification domain: Text field.
n User: Text field. User field in the Communication settings block of the Data Import/Export form used (and not the
Default user field of the Header block).
n Action: Typeahead.

- 455 -
 Data imports/exports settings

Data imports/exports settings

List of imports/exports

The data imports/exports can only be accessed with a Supervisor account and from the menu [Settings-Data Imports/Exports].

Creating an import/export

An import/export can be created:

n With the button on the list of data imports/exports.

n Click on the button on the import/export form.

For further explanation of the creation of an import/export, refer to the Import/Export form.

Deleting an import/export

To delete a team:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

A confirmation message is displayed to confirm the deletion.

Archiving/De-archiving an import/export

To archive an import/export:

- 456 -
 Data imports/exports settings

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

The icon is displayed to the left of the description and the title, indicating that the import/export is archived.

To de-archive, proceed as follows:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplicating an import/export

To duplicate an import/export:

n Use the button on the list of data imports/exports.

n Click on the button on the import/export form.

Duplication of an import or an export duplicates all the data entered in all the blocks except the description.

Advanced filters

This block, which is closed by default, shows the following fields:

n Description: Text field. Automatic filter upon entry.

n Type: Typeahead.
n Flag: Text field.
n Field separator: Text field.
n Text delimiter: Text field.
n Decimal separator: Text field.
n Thousands separator: Text field.
n URL: Text field.
n Identification domain: Text field.
n User: Text field. User field in the Communication settings block of the Data Import/Export form used (and not the
Default user field of the Header block).
n Action: Typeahead.

- 457 -
 Data imports/exports settings

- 458 -
 Data imports/exports settings

Import/export form
Accessible from the menu [Settings-Utility Programme-Data Import/Export].

Click the button to access the form being created or the button to view an import/export form.

The Create, Delete, Archive and Duplicate buttons are explained in the actions of the List of Imports/Exports

Configuration export/Configuration import

On the configuration of an existing import/export, the button extracts the configuration

in .json format (cannot be modified).
The following data is exported:

For the header:

l Description
l Type
l Flag
l Field separator
l Text delimiter
l Decimal separator
l Thousands separator
l Date format: If the time has not been entered when a date is imported, it is entered automatically as 00:00.
l Boolean values

For the actions:

l Order
l Action
l Source
l Active

For mapping:

l Order (reminder of the order of the action in the list)

l MX field
l Correspondence field

This configuration can then be used to create a new import/export by clicking on the button

a pop-in appears with the json file to be downloaded.

The "Import" button launches the configuration import and all the information of the new import/export is initialised with the
information entered in the configuration file.

The new configuration can then be saved.

This whole action is only possible if the imported file does not exceed a size or 15 Mb (otherwise, a blocking message warns the
user).

- 459 -
 Data imports/exports settings

Header block

The header block defines the main information of the import/export.

n Description: Required and unique

n Type: Selection list: CSV, Web Services, NAV Web Services.
n Flag: Text field. Character noting that the data has already been exported or imported.
n Default user : The settings (time zone, language) of this user are retrieved if the imports are run automatically by the
robot.
n Shared data: checkbox visible if multi-organisation mode is enabled. Enables one to choose the type of data to be
imported: shared or unshared.
n Entity: Displayed if multi-organisation mode is enabled. This field is required if the import involves unshared data (sha-
red data checkbox unchecked). Used to associate the imported data with one or more entities. By default, the entity
field is initialised with all the entities of the user. The user does not see the entities with which he or she is not linked.
If several entities are selected, the shared data checkbox must be checked and cannot be modified.

Importing shared and unshared data

When running the import/export, if the shared data checkbox is checked
sharing is checked
- For data imports that cannot be shared (movement, WR, PW, WO, PR), there is a run error
- The items imported are shared and associated with the entities entered
- For exports, only the entities entered are acknowledged - the shared data checkbox is not acknowledged

If the shared data checkbox is not checked

- The items imported are not shared and associated with the entity entered
- For exports, only the entity entered is acknowledged - the shared data checkbox is not acknowledged

The import types available are:

n CSV: CSV files must be encoded in UTF-8

n web service
n NAVISION web service.

Preparation of Excel .xls and .xlsx files for a .csv import

For an Excel file import to work, it is essential that it by encoded in UTF-8 format.
We do not recommended doing this directly in Excel, which does not handle the encoding of certain characters (accents for
example).
This is how to proceed:
- Prepare the Excel file and save it in .csv format.
- Open the file with the notepad (Right-click on the file/open with -> Select Notepad)
- Click on the File/Save as tab and the saving window will be displayed.
- In the Encoding section, select the type UTF-8.
- In the Type section, select .csv
- Save and close
The import file is correctly encoded and may be imported in MX.

When a data export is carried out, a line that has been exported correctly is marked in the database with the pre-set flag and the
date/time of the export.
A line that has not been exported correctly is not flagged.
Only the unflagged lines are exported.

- 460 -
 Data imports/exports settings

Data format block

Used to customise the available data format options necessary for the execution of a data import/export.

n Field separator
n Text delimiter
n Decimal separator
n Thousands separator
n Date format
n Boolean values
n Number of header lines: positive integer, default is 0: If the number of lines to skip is greater than 0, not all the lines
in the header are processed. This setting is only visible on .CSV imports

The following date formats are available:

n MM-DD-YYYY hh:mm
n DD/MM/YYYY hh:mm
n YYYY-MM-DD hh:mm
n YYYYMMDDHHmm
n YYYYMMDD (Sage X3)

If the time has not been entered when a date is imported, it is entered automatically as 00:00.

The following Boolean values are available:

n True/False
n T/F
n 1/0

These values must be entered in the import form for Boolean type fields.

Communication settings block

This block contains all the settings necessary for communication with other products. (SFTP address, server URL, port, credentials
etc.).

A Transfer method drop-down list offers the choices:

n Manual transfer
n DIMO Software SFTP

Manual transfer = Yes

If manual transfer is selected for CSV imports, then a “Transfer file” button is displayed in each action/import.
The file is transferred to the “Shared” server which corresponds to the contentpath tags in the dimomaint.config., in an
import/export directory.
Automatic scheduling cannot be configured for a file upload.
The name of the transferred file is entered automatically in the “source” field.

Manual transfer = No
Some settings are used only for webservice imports, others for CSV file imports.

- 461 -
 Data imports/exports settings

n Address (SFTP): Required (visible only if type = CSV).

n URL: Required (visible only if Type = Web Service or NAV Web Service); URL of the web service used.
n SOAP URL: Movement export automatic validation URL. Only for the NAVISION web service type.
n Identification domain
n User
n Password
n Run in automatic mode: Yes/No.

This function can be used for automatic scheduling of imports/exports at a fixed time or at a defined frequency.

n Scheduling mode: Fixed time/Frequency (h) expressed in UTC/GMT.

n Fixed time: HH/MM expressed in GMT
n Automatic validation in NAV of movement exports: Checkbox (visible if Type = NAV Web Service).

DIMO SFTP transfer method (to provide .csv files)

When you select the Dimo SFTP transfer method, you have 2 choices in terms of file management:

- 'Replace': if there is a file with the same name, it is replaced by the new file exported.

- 'Add': if there is a file with the same name, it has the data from the new export added to it. We therefore obtain a file contai-
ning the data from the previous exports and the last export.

Actions block

Used to add a series of import or export actions. Each action added to the block has an order number (sequential).

All the actions can be run one after the other by clicking on the button in the form header. (They are run in the defi-

ned order), or each action can be run separately from the others by clicking on the icon at the end of the action line.
Only "Active" actions are performed

n Order: Required (sequential number).

n Action: Required (list).
n Source: Required (name of the CSV file or the web service).
n Active: When performing all actions simultaneously, only active actions are taken into account.

- 462 -
 Data imports/exports settings

Import actions:

See the details of imports (Movements, Stock, Assets, Parts, etc.)

Export actions:

See the details of exports (Labour lines, Movements, etc.)

The following buttons are available for each action line:

n : Delete

n : Mapping

n : Run

Note: when several imports/exports are started simultaneously, they are run in parallel.

Data mapping
Data mapping enables a link to be established between CMMS data and data from an external product.

The mapping is specific to each action. It must be done for the required fields.

If no external product data is mapped with CMMS data, the information is not entered in the CMMS.

n If the import or export type is file, the CMMS data is mapped with a column index.

(Example: if 'Code...' is in the first column in the CSV, the index 1 must be placed in front of the MX field corresponding to the
'Code...'.)

n If the import or export type is webservice, the CMMS data is mapped with the name of the data in the other product

- 463 -
 Data imports/exports settings

Running and processing an import:

A data validity check is performed on all the lines to be imported.

o If the data are invalid or an error occurs during import, they are not imported and an error log is generated.
o If the data are valid, the line is imported.

Imports and currencies

For imports and costs, if the currency is not entered in the import, the currency of the user running the import is applied, only
when data is created. (except for parts that are created in the general configuration currency)
If an existing item of data is being modified, the currency saved is maintained. The system considers that the blank currency is
the user's currency and therefore performs the conversion at the rate applicable on the reference date.

Error and log management

When running a data import, only the valid lines are imported.

To view the logs, click on the button in the imports list header.

Field length

There are a certain number of fields with the following meaning:

Code: code
UserName: user form ID
Name: description/country/city/address
Email: e-mail
SimpleComment: short comment
Url: DMA website/url
Token: DMA device
FirstName: first name
LastName: last name
SerialNumber: serial number
Letter: telephone/fax/post code/NAF code/VAT/ SIRET/RCS/flag
ManufacturerReference: manufacturer reference
SupplierReference: supplier reference
Title: title (Mr/Mrs)
Character: decimal separator/csv separator/field separator/ text delimiter
UserTimeZone: time zone
UserType: type (In/Ex)

Their maximum size is as follows:

Code = 128,
UserName = 128,
Name = 255,
Email = 255,
SimpleComment = 255,
Url = 255,
Token = 255,
FirstName = 128,

- 464 -
 Data imports/exports settings

LastName = 128,
SerialNumber = 50,
Letter = 50,
ManufacturerReference = 50,
SupplierReference = 50,
Title = 10,
Character = 1,
UserTimeZone = 50,
UserType = 2,

Current process monitoring console

To monitor the progress of the imports/exports processing, a management console is available in the imports.

Click on the button to view the progress of each import.

The times indicated in the "Launch date" and "End date" fields are earlier because they are expressed in GMT - 1 hour's dif-
ference in winter and 2 hours' difference in summer.

If an import ends without any errors, the state will be “Completed”.

If an import ends with an error, the state will be “Completed with errors”.

Each large import corresponds to a batch of 1,000 items.

For example, an import of 5,000 lines creates 5 successive treatments to reach the global treatment of the import.

Time zones/format

Imports are subject to the time zone constraints of the entity considered.

List of time zones applied:

l UTC - 10:00: Hawaii, Aleutian Islands

l UTC - 09:30: Marquesas Islands
l UTC - 09:00: Alaska
l UTC - 08:00: Baja California, Pacific (United States and Canada)
l UTC - 07:00: Arizona, Chihuahua, La Paz, Rocky Mountains (United States and Canada)
l UTC - 06:00: Central America, Centre (United States and Canada,) Guadalajara, Mexico, Monterrey, Saskatchewan, Eas-
ter Island
l UTC - 05:00: Bogota, Lima, Quito, Rio Branco, Chetumal, East (United States and Canada), Havana, Haiti, Indiana (East),
Turks and Caicos Islands
l UTC - 04:00: Asuncion, Caracas, Cuiaba, Georgetown, La Paz, Manaus, San Juan, Atlantic Time (Canada), Santiago
l UTC - 03:30: Newfoundland and Labrador
l UTC - 03:00: Araguanã, Brasilia, Buenos Aires, Cayenne, Fortaleza, Greenland, Montevideo, Punta Arenas, Saint-Pierre-
et-Miquelon, Salvador
l UTC - 02:00: Central Atlantic - Old
l UTC - 01:00: Azores, Cape Verde
l UTC + 00:00: Dublin, Edinburgh, Lisbon, London, Monrovia, Reykjavik, São Tomé
l UTC + 01:00: Casablanca, Central/West Africa, Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna, Belgrade, Bra-
tislava, Ljubljana, Prague, Brussels, Copenhagen, Madrid, Paris, Sarajevo, Skopje, Warsaw, Zagreb
l UTC + 02:00: Amman, Athens, Bucharest, Beirut, Chisinau, Damascus, Gaza, Hebron, Harare, Pretoria, Helsinki, Kiev,
Riga, Sofia, Tallinn, Vilnius, Jerusalem, Kaliningrad, Khartoum, Cairo, Tripoli, Windhoek
l UTC + 03:00: Baghdad, Istanbul, Kuwait, Riyad, Minsk, Moscow, Saint Petersburg, Nairobi, Tehran

- 465 -
 Data imports/exports settings

l UTC + 04:00: Abu Dhabi, Muscat, Astrakhan, Ulyanovsk, Baku, Erevan, Izhevsk, Samara, Port Louis, Saratov, Tbilissi, Vol-
gograd
l UTC + 04:30: Kabul
l UTC + 05:00: Ashgabat, Tashkent, Yekaterinburg, Islamabad, Karachi, Kyzylorda
l UTC + 05:30: Chennai, Kolkata, Mumbai, New Delhi, Sri Jayawardenepura
l UTC + 05:45: Kathmandu
l UTC + 06:00: Astana, Dhaka, Omsk
l UTC + 06:30: Rangoon
l UTC + 07:00: Bangkok, Hanoi, Djakarta, Barnaul, Gorno-Altaysk, Hovd, Krasnoyarsk, Novosibirsk, Tomsk
l UTC + 08:00: Beijing, Chongqing, Hong Kong, Urumqi, Irkutsk, Kuala Lumpur, Singapore, Ulaanbaatar, Perth, Taipei
l UTC + 08:45: Eucla
l UTC + 09:00: Chita, Yakutsk, Osaka, Sapporo, Tokyo, Pyongyang, Seoul
l UTC + 09:30: Adelaide, Darwin
l UTC + 10:00: Brisbane, Canberra, Melbourne, Sydney, Guam, Port Moresby, Hobart, Vladivostok
l UTC + 10:30: Lord Howe Island
l UTC + 11:00: Chokurdakh, Magadan, Sakhalin, Bougainville Island, Norfolk Island, Salomon Islands, New-Caledonia
l UTC + 12:00: Anadyr, Petropavlovsk-Kamtchaktski, Auckland, Wellington, Fiji
l UTC + 12:45: Chatham Islands
l UTC + 13:00: Nuku'alofa, Samoa, Kiritimati (Îsland)

Import details

Sage X3 purchase request progress

Import enum code = PurchaseRequestProgressSageX3Import

Swagger model correspondence = PurchaseRequestProgressSageX3ImportModel

n Interface key (Text, Required). Corresponds to the AutoIncrementId of the export of PR lines.
n Status (Text, Required)
n Quantity received (Positive decimal)

If the interface key does not match any of the PurchaseRequestPart table IDs, an import error occurs, the quantity received is
ignored

If field Status = 1
It the Cancelled status is used on the PR entity, the PR status of the line is changed to Cancelled
Otherwise, the PR of the line is changed to the first status that is equivalent to Cancelled
If no status equivalent to Cancelled is used, nothing is done
If the PR is already Closed, its status does not change to Cancelled

If field Status = 2
If the Closed status is used on the PR entity, the PR status of the line is changed to Closed
Otherwise, the PR of the line is changed to the first status that is equivalent to Closed

No./Description/Type
1 Line identifier A
2 Status of line (1) A
3 Quantity received (2) N

- 466 -
 Data imports/exports settings

(1) Status of line: Possible values are 0: Pending, 1: Rejected, 2: Balanced, 3: Signed, 4: Ordered
(2) Quantity received: If there have been any receipts, the value will be greater than zero

Sage X3 order progress

Import enum code = PurchaseOrderProgressSageX3Import

Swagger model correspondence = PurchaseOrderProgressSageX3ImportModel

n Interface key (Text, Required). Corresponds to the AutoIncrementId of the export of order lines.
n Status (Text, Required)
n Quantity received (Positive decimal)

If the interface key does not match any of the PurchaseOrderPart table IDs, an import error occurs

If field Status = 1
If the Cancelled status is used on the order entity, the order of the line is changed to Cancelled
Otherwise, the order of the line is changed to the first status found that is equivalent to Cancelled
If no status equivalent to Cancelled is used, no action is carried out

If the order is already Closed, its status does not change to Cancelled

If field Status = 2
If the Closed status is used on the order entity, the order of the line is changed to Closed
Otherwise, the order of the line is changed to the first status found that is equivalent to Closed
Otherwise, nothing is done

No./Description/Type
1 Line identifier A
2 Status of line (1) A
3 Quantity received (2) N

(1) Status of line: Possible values are 0: Pending, 1: Rejected, 2: Balanced, 3: Signed, 4: Ordered
(2) Quantity received: If there have been any receipts, the value will be greater than zero

When importing a line from an X3 order progress import, automatic PR status changes are applied (Partial delivery, Full delivery):
- Status of an order from the PR changed to "Processed"
- Status of all orders from the PR changed to "Processed"
- Status of an order from the PR changed to "Closed"
- Status of all orders from the PR changed to "Closed"
- Status of all orders from the PR changed to "Cancelled"

Management rules on using the quantity received:

If the quantity received from the file is less than or equal to the sum of the quantities received from the order line corresponding
to the interface key, no action is taken.
If the sum of the quantities delivered is greater than or equal to the quantity ordered, the Balanced field is changed to "yes".
Automatic order status changes are applied, for full or partial delivery.

If the quantity received from the file is greater than the sum of the quantities received from the order line corresponding to the
interface key, a receipt is created on this order line:

Delivery note: numerical meter: First digit available for this order line

- 467 -
 Data imports/exports settings

Delivery date: Import Date/Time

Quantity received: Quantity received from file - Sum of quantities received from other receipts from the order line
Unit: Order line unit
Warehouse: 1. If warehouse on order line: Order line warehouse
2. Otherwise, if part is managed in stock at the main warehouse of the order entity: Main warehouse of the order entity
3. Otherwise, if part is managed in stock at a warehouse linked to the order entity: First warehouse found linked to the order
entity where the part is managed in stock
4. Otherwise, if a warehouse is the main warehouse of the order entity: Main warehouse of the order entity
5. First warehouse found linked to the order entity

Work orders (History)

Used to import or update work order data.

n Code
n Title
n Status Code **
n Status description: If this field is not filled in, the status selected is the reference status associated with the code. The
description field is used to identify the status (the code remains to create repositories on the fly later)
n Asset (required)
n Work type code
n Work type description
n Priority code
n Priority description
n Start date
n Deadline
n End date
n Asset off
n Sender
n Creation date
n Technology code
n Technology description
n Cost allocation code
n Cost allocation description
n Contract
n Effect
n Cause
n Remedy
n Currency: ISO code. If not entered, the currency in the general settings is assigned to the new WR.
n Grouped work order/Code (Text)
n Distribution (Positive integer)
n WR code (Text)
n PW code (Text)
n Meter/Value: taken into account if there is a PW code entered
n Archive

The WO can only have a WR code or a PW code. If a WR code or PW code already exists on the WO, it is replaced by the new WR
code or PW code.

Values to be entered in the file for the following status codes

CLOSED for Closed or equivalent
DONE for Done or equivalent
CANCELLED for Cancelled or equivalent
INPROGRESS for In progress or equivalent
TODO for To do or equivalent

- 468 -
 Data imports/exports settings

A WO import can only be included in a single entity

If the code is not entered, the automatic codification of the profile of the person running the import is applied
If this person does not have automatic codification configured, simple meter alternative codification is applied

If the creation date, start date or end date are not entered, they are entered as the day's date
If Boolean fields are not filled in, "no" is entered in them
If the sender is not entered, the person running the import is entered
If the status is not entered (code), it is initialised with the entity’s configuration for the Create WO action
If no configuration is entered, it is initialised with the reference status "To do"

During import, if the contract field does not match the information entered (asset, technology, work type, dates entered), an
error message will be displayed.

Grouped work:

n When importing a WO with a grouped WO code, that WO becomes the child WO of the grouped WO entered.
n If the distribution is entered, it is applied to the child WO in the grouped WO.
n If the distribution is not entered, the child WO has a distribution of 1 in the grouped WO
n If the distribution is entered but the WO has no grouped WO code, the distribution is ignored
n If the WO is already the child of a grouped WO -> Import error
n If the WO is already the child of a grouped WO but if the reference to a grouped WO has not been entered, the WO is
not modified.

Work orders/Downtime (History)

Import enum code = WorkOrderDownTimeHistoryImport

Swagger model correspondance = WorkOrderDownTimeHistoryImportModel

Used to import or update work order data.

n WO code (required)
n Planned start date
n Planned end date
n Estimated hourly cost
n Planned Currency ISO code
n Actual start date
n Actual end date
n Actual hourly cost
n Actual Currency ISO code
n Completed

If the planned start date is not entered, it is filled in with the current date/time.
If the planned end date is not entered, it is filled in with the planned start date.

If the estimated cost is not entered, it is entered as 0

If the actual start date is entered, the actual end date is required
If the actual end date is entered, the actual start date is required

If the 'actual' information is entered, an 'actual' line is created on the shutdown line
If the actual cost is not entered, it is filled in as 0

- 469 -
 Data imports/exports settings

If Completed is not entered, it is filled in as No

If the history is set to yes, no cost retrieval, valuation, removal etc. processing is carried out

Work orders/Comments

Import enum code = WorkOrderCommentImport

Swagger model correspondence = WorkOrderCommentImportModel

Used to import or update work order data.

n WO code (required)
n User (required)
n Comment
n HTML comment
n Date (Date/time)

Work orders/Jobs

Import enum code = WorkOrderJobImport

Swagger model correspondence = WorkOrderJobImportModel

Used to import or update work order data.

n WO code (required)
n Job code (required)
n Task description (required)
n Task/Order (required): task order
n Task/Response: waiting for the response to the task (related to the WO). Response "Not feasible" possible for a rea-
ding task (meter reading or measurement reading)
n Task/Comment: comment on task completion

When one adds a work order/job/1st priority task, the link between the work order and the job is created

For all lines, the link between the work order and the task is created

Work orders/Status change histories

Import enum code = WorkOrderStateHistoryImport

Used to import or update work order data.

n WO code (required)
n Date/Time (required)
n Status/Code (Required)
n Status/Description (Required)
n User (required)

Values to be entered in the file for the following status codes

CLOSED for Closed or equivalent
DONE for Done or equivalent
CANCELLED for Cancelled or equivalent
INPROGRESS for In progress or equivalent
TODO for To do or equivalent

- 470 -
 Data imports/exports settings

Work orders/Labour (History)

Import enum code = WorkOrderLabourHistoryImport

Swagger model correspondence = WorkOrderLabourHistoryImportModel

Used to import or update work order data.

Import name: history of work orders/Labour

n WO code (required)
n Technician category code (required)
n Technician category description
n Technician
n Planned start date
n Planned end date
n Estimate cost: hourly cost
n Planned Currency ISO code
n Actual start date
n Actual end date
n Actual hourly cost
n Actual Currency ISO code
n Completed (Boolean)

If the planned start date is not entered, it is filled in with the current date/time
If the planned end date is not entered, it is filled in with the planned start date/time

If the estimated cost is not entered, it is entered as 0

If the actual start date is entered, the technician and the actual end date are required.

If the actual end date is entered, the technician and the actual start date are required

If the 'actual' information is entered, an 'actual' line is created on the workforce line

If the actual cost is not entered, it is filled in as 0

If Completed is not entered, it is filled in as No

No cost retrieval, valuation, withdrawal etc. processing is carried out.

Work orders/Parts (History)

Import enum import = WorkOrderPartHistoryImport

Swagger model correspondence = WorkOrderPartHistoryImportModel

Used to import or update work order data.

n WO code (required)
n Part code (required if no description)
n Description (required if no part code)
n Warehouse (required if code entered)
n Planned date
n Planned quantity
n Planned unit code

- 471 -
 Data imports/exports settings

n Planned unit description

n Estimated unit price
n Planned Currency ISO code
n Actual date
n Quantity achieved
n Actual unit price
n Actual Currency ISO code
n Completed
n InterfaceKey

If the planned date is not entered, it is filled in with the current date/time.

If the planned quantity field is not filled in, it must be initialised at 0.

If the part is not listed and the estimated unit price is not entered, it is filled in as 0.

If the actual date is entered, an 'actual' line is created on the Part line.
If the actual quantity is not entered, it must be initialised at 0.

If the part is not listed and the actual unit price is not entered, it is filled in as 0.

Management of the stock withdrawal with part return:

If the interface key field (InterfaceKey) is filled in, then the actual part line is sought in relation to this ID. It must be specified that
it must be unique on the X3 side and required.
If the line is found, then the "planned" and "actual" information on this line is updated.
If not, the resource line is sought via the pair: WO code, Part code, Warehouse code, Planned Unit code.
If the resource is found, then the planned and creation information of an actual line is updated.
If not a new resource line is created with its actual information.

Work orders/Subcontractors (History)

Import enum code = WorkOrderSubContractorHistoryImport

Swagger model correspondence = WorkOrderSubContractorHistoryImportModel

Used to import or update partner categories.

n Code (required)
n Description (required)

Used to import or update work order data.

n WO code (required)
n Subcontractor category code (required)
n Subcontractor category description
n Subcontractor: Subcontractor name
n Planned start date
n Planned end date
n Estimated subcontractor cost
n Estimated SC cost currency ISO code
n Estimated part cost
n Estimated part cost currency ISO code
n Actual start date
n Actual end date
n Actual subcontractor cost

- 472 -
 Data imports/exports settings

n Actual SC cost currency ISO code

n Actual part cost
n Actual part cost currency ISO code
n InterfaceKey

If the planned start date is not entered, it is filled in with the current date/time.
If the planned end date is not entered, it is filled in with the planned start date.

If the estimated SC cost is not entered, it is filled in as 0

If the estimated part cost is not entered, it is filled in as 0

If the actual start date is entered, the subcontractor is required

If the actual start date is entered, the actual end date is required

If the actual end date is entered, the subcontractor is required

If the actual end date is entered, the actual start date is required

If the 'actual' information is entered, an 'actual' line is created on the SC line

If the actual SC cost is not entered, it is filled in as 0

If the actual part cost is not entered, it is filled in as 0

If Completed is not entered, it is filled in as No

No cost retrieval, valuation, withdrawal etc. processing is carried out.

Update of a subcontracting line:

If the interface key field (InterfaceKey) is filled in, then the actual part line is sought in relation to this ID.
If the line is found, then the "planned" and "actual" information on this line is updated.
If not, the resource line is sought via the pair: WO code, subcontractor code, subcontractor name.
If the resource is found, then the planned and creation information of an actual line is updated.
If not, the resource line is created with its actual information.

Grouped work orders (History)

Import enum code = WorkOrderGroupLabourHistoryImport

Swagger model correspondence = WorkOrderGroupLabourHistoryImportModel

Import name: History of grouped work orders.

n Work order/Code
n Work order/Title
n Work order/Status code
n Work order/Status description
n Currency (ISO code)
n Type of work/Code
n Type of work/Description
n Priority/Code
n Priority/Description
n Start date
n Deadline
n End date
n Issuer/ID
n Creation date
n Technology/Code

- 473 -
 Data imports/exports settings

n Technology/Description
n Cost allocation/Code
n Cost allocation/Description
n Contract/Code
n Archive

Values to be entered in the file for the following statuses:

CLOSED for Closed or equivalent
DONE for Done or equivalent
CANCELLED for Cancelled or equivalent
INPROGRESS for In progress or equivalent
TODO for To do or equivalent

A WO import can only be on one single entity.

If the code is not entered, the automatic codification of the profile of the person running the import is applied
If this person does not have automatic codification configured, simple meter alternative codification is applied.

If the creation date, start date and end date are not entered, they are entered as the day's date

Blank boolean fields are entered as ‘no’

If the sender is blank, the user running the import is entered
If the status is blank, it is initialised with the configuration of the entity for the Create WO action
If no configuration is entered, it is initialised with "To do" status

During import, if the contract field does not match the information entered (technology, work type, dates entered), the contract
field is not filled in.

Grouped work orders/Machine downtimes (History)

Import enum code = WorkOrderGroupDowntimeHistoryImport

Swagger model correspondence = WorkOrderGroupDowntimeHistoryImportModel

Import name: History of grouped work orders/Machine downtimes.

n Grouped work order/Code (required)

n Interface key
n Planned work/Currency ISO code
n Planned work/Hourly cost
n Planned work/Start date
n Planned work/End date
n Completed work/Start date
n Completed work/End date
n Completed work/Hourly cost
n Completed work/Currency ISO code
n Completed

If the planned start date is not entered, it is filled in with the current date/time
If the planned end date is not entered, it is filled in with the planned start date
If the estimated cost is not entered, it is entered as 0
If the actual start date is entered, the actual end date is required
If the actual end date is entered, the actual start date is required
If the 'actual' information is entered, an 'actual' line is created on the shutdown line
If the actual cost is not entered, it is filled in as 0

- 474 -
 Data imports/exports settings

If Completed is not entered, it is filled in as No

Grouped work orders/Work orders (children)

Import enum code = WorkOrderWorkOrderGroupHistoryImport

Swagger model correspondence = WorkOrderWorkOrderGroupHistoryImportModel

Used to import comments in grouped WOs.

n Grouped work order/Code (required)

n Work order/Code (Required)
n Distribution (Positive integer)

If the distribution is not entered, it is initialised at 1

Grouped work orders/Comments

Import enum code = WorkOrderGroupCommentImport

Swagger model correspondence = WorkOrderGroupCommentImportModel

Used to import comments in grouped WOs.

n Grouped work order/Code (required)

n Comment
n HTML comment
n Date created (Date/Time)
n User/Login (required)

Grouped work orders/Status change histories

Import enum code = WorkOrderGroupStateHistoryImport

Swagger model correspondence = WorkOrderGroupStateHistoryImportModel

Used to import histories of grouped WO status changes.

n Grouped work order/Code (required)

n Status/Code (Required)
n Status/Description
n User/ID (required)
n Date/Time (required)

Values to be entered in the file for the following status codes

CLOSED for Closed or equivalent
DONE for Done or equivalent
CANCELLED for Cancelled or equivalent
INPROGRESS for In progress or equivalent
TODO for To do or equivalent

Grouped work orders/Labour (History)

Import enum code = WorkOrderGroupLabourImport

Swagger model correspondence = WorkOrderGroupLabourHistoryImportModel

- 475 -
 Data imports/exports settings

Import name: History of grouped work orders/Labour.

n Grouped work order/Code (required)

n Interface key
n Technician category/Code (required)
n Technician category/Description
n Technician/ID
n Planned work/Start date
n Planned work/End date
n Planned work/Hourly cost
n Planned work/Currency ISO code
n Completed work/Start date
n Completed work/End date
n Completed work/Hourly cost
n Completed work/Currency ISO code
n Completed

If the planned start date is not entered, it is filled in with the current date/time
If the planned end date is not entered, it is filled in with the planned start date/time
If the estimated cost is not entered, it is entered as 0
If the actual start date is entered, the technician is required
If the actual start date is entered, the actual end date is required
If the actual end date is entered, the technician is required
If the actual end date is entered, the actual start date is required
If the 'actual' information is entered, an 'actual' line is created on the labour line
If the actual cost is not entered, it is filled in as 0
If Completed is not entered, it is filled in as No

Grouped work orders/Part (History)

Import enum code = WorkOrderGroupPartHistoryImport

Swagger model correspondence = WorkOrderGroupPartHistoryImportModel

Import name: History of grouped work orders/Part.

n Grouped work order/Code (required)

n Interface key
n Part/Code (required if no description)
n Part/Description (required if no part code)
n Warehouse (required if code entered)
n Planned work/Date
n Planned work/Quantity
n Unit/Code
n Unit/Description
n Planned work/Unit price
n Planned work/Currency ISO code
n Completed work/Date
n Completed work/Quantity
n Completed work/Unit price
n Completed work/Currency ISO code
n Completed

If the planned date is not entered, it is filled in with the current date/time
If the actual quantity is not entered, it must be initialised at 0

- 476 -
 Data imports/exports settings

If the part is not listed and the estimated unit price is not entered, it is filled in as 0
If the actual date is entered, an 'actual' line is created on the Part line
If the quantity is not entered, it is initialised at 0
If the part is not listed and the actual unit price is not entered, it is filled in as 0
If Completed is not entered, it is filled in as No

No movement is made on this import.

Grouped work orders/Subcontractors (History)

Import enum code = WorkOrderGroupSubContractorHistoryImport

Swagger model correspondence = WorkOrderGroupSubContractorHistoryImportModel

Import name: History of grouped work orders/Subcontractors.

n Grouped work order/Code (required)

n Interface key
n Subcontractor category/Code (required)
n Subcontractor category/Description
n Subcontractor/Code
n Planned work/Start date
n Planned work/End date
n Planned work/Subcontractor cost
n Planned work/SC cost Currency ISO code
n Planned work/Part cost
n Planned work/Part cost ISO currency code
n Completed work/Start date
n Completed work/End date
n Completed work/Subcontractor cost
n Completed work/SC cost Currency ISO code
n Completed work/Part cost
n Completed work/Part cost ISO currency code
n Completed (yes/no)

If the planned start date is not entered, it is filled in with the current date/time
If the planned end date is not entered, it is filled in with the planned start date
If the estimated SC cost is not entered, it is entered as 0
If the estimated part cost is not entered, it is filled in as 0
If the actual start date is entered, the subcontractor is required
If the actual start date is entered, the actual end date is required
If the actual end date is entered, the subcontractor is required
If the actual end date is entered, the actual start date is required
If the 'actual' information is entered, an 'actual' line is created on the SC line
(If the actual line already existed, it would have been updated)
If the actual SC cost is not entered, it is filled in as 0
If the actual part cost is not entered, it is filled in as 0
If Completed is not entered, it is filled in as No

Budgets
Import enum code = BudgetImport
Swagger model correspondence = BudgetImportModel

- 477 -
 Data imports/exports settings

n Code
n Description
n Start date (required)
n End date (required)
n Frequency (= ge for general or pm for Per month)
n First grouping level (= accountassignment for Cost allocation or workingtype for Type of work)
n Second grouping level (= accountassignment for Cost allocation or workingtype for Type of work)
n Currency
n Comment

If the currency is not entered -> user's currency.

If the frequency is not entered -> overall
If the first and second grouping levels are identical, the second level is not used.
If the code is not entered and automatic codification is configured, it is applied.
If the code is not entered and automatic codification is not configured, there is an error.

Budgets/Detail

Import enum code = BudgetDetailImport

Swagger model correspondence = BudgetDetailImportModel

Import name: import of budget details

Code

n Value of the first grouping level

n Value of the second grouping level
n Month
n Year
n Amount

If the imported budget is entered overall and the month or year are entered -> error
If the imported budget is entered by month and the month and year are not entered -> error
If grouping values do not match with what is configured in the budget header -> error

Causes(Diagnoses)

Import enum code = CauseImport

Swagger model correspondence = CauseImportModel

Used to import or update cause data for work diagnoses.

n Description (required)
n Comment

Causes/Assets

Import enum code = CauseAssetImport

Swagger model correspondence = CauseAssetImportModel

Used to import or update assets on causes.

- 478 -
 Data imports/exports settings

n Cause description (required)

n Asset code (required)

Causes/Technologies(Diagnoses)

Import enum code = CauseTechnologyImport

Swagger model correspondence = CauseTechnologyImportModel

Used to import or update cause technologies for work diagnoses.

n Cause description (required)

n Technology code (required)
n Technology description

Partner categories

Import enum code = PartnerCategoryImport

Swagger model correspondence = PartnerCategoryImportModel

Used to import or update partner categories.

n Code (required)
n Description (required)

Technician categories

Import enum code = TechnicianCategoryImport

Swagger model correspondence = TechnicianCategoryImportModel

Used to import or update technician categories.

n Code (required)
n Description (required)
n Hourly cost
n Hourly cost ISO currency code

If the hourly cost is empty, it is automatically entered as 0

If the ISO currency code is empty, the code in the general settings is entered.

Orders

Import enum code = PurchaseOrderImport

Swagger model correspondence = PurchaseOrderImportModel

Used to import or update orders.

n Order/Code -> if the code is not entered, automatic codification is applied if it is configured, otherwise it’s an alter-
native meter codification.
n Order/Title (required)
n Order/Status/Code **-> Order creation status if not entered
n Order/Status/Description -> If not entered, take the reference status of the code entered

- 479 -
 Data imports/exports settings

n Creation date -> day's date if not given

n Terms of delivery/description
n Purchase request/Code
n Sender/ID -> import user if not given
n Supplier/Code
n Currency ISO code
n Cost allocation/code
n Cost allocation/description
n Work order/Code
n Asset/Code
n Warehouse/Code
n Warehouse/description
n Contact/surname
n Contact/first name
n Supplier order reference
n Payment terms/description
n Terms of delivery/description
n Order footer
n Archive
n VAT/Code

If there is no supplier and a contact is entered -> import error

If the contact does not exist with the supplier -> import error

**Status codes:
CLOSED for Closed or equivalent
CANCELLED for Cancelled or equivalent
PROCESSED for Processed or equivalent
SENT for Sent or equivalent
TODO for In preparation or equivalent

Orders/Comments

Import enum code = PurchaseOrderCommentImport

Swagger model correspondence = PurchaseOrderCommentImportModel

Used to import or update order comments.

n Order/code (required)
n User/ID (required)
n Comment
n HTML comment
n Date (Date/time)
n Description (required)

Order/Part lines

Import enum code = PurchaseOrderPartImport

Swagger model correspondence = PurchaseOrderPartImportModel

Used to import or update order part lines.

- 480 -
 Data imports/exports settings

n Order/code (required)
n Part/code: required if part description not entered
n Part/description: required if part code not entered
n Supplier reference
n Comment
n Quantity ordered (required)
n Unit/code (required)
n Unit price excl. tax-> If not entered, price at 0
n Discount (%) -> If not entered, price at 0
n Discount -> If not specified, price at 0
n Warehouse/code
n Warehouse/description
n Storage location/code
n Storage location/description
n Cost allocation/code
n Cost allocation/description
n Work order/code
n Asset/code
n Balanced -> If not entered, balanced at false
n Scheduled delivery date (date)
n VAT/Code

Orders/Subcontractor lines

Import enum code = PurchaseOrderSubcontractorImport

Swagger model correspondence = PurchaseOrderSubcontractorImportModel

Used to import or update order subcontracting lines

n Order/code (required)
n Order line/title (required)
n Partner category/code
n Supplier reference
n Planned duration -> If not entered, duration at 0
n Unit price excl. tax-> If not entered, price at 0
n Discount (%) -> If not entered, price at 0
n Discount -> If not specified, price at 0
n Cost allocation/code
n Cost allocation/description
n Work order/code
n Asset/code
n Comment
n Balanced -> If not entered, balanced at false
n Scheduled delivery date (date)
n VAT/Code. Field present even if the VAT module is disabled. If code incorrect, standard error message.

Terms of delivery

Import enum code = DeliveryTermImport

Swagger model correspondence = DeliveryTermImportModel

Used to import or update delivery conditions.

- 481 -
 Data imports/exports settings

n Description (required)

Contracts

Import enum code = ContractImport

Swagger model correspondence = ContractImportModel

Used to import or update contracts.

n Contract/Code (required)
n Contract/Title (required)
n Contract/Status (Active if not entered)
n Subcontractor (required) (name of the partner)
n Contract/Subcontractor/Code (Partner code; if there is a conflict between the partner's Code and Name, the Code
takes priority)
n Contract/Manager/ID (required)
n Contract type/Code (required)
n Contract type/Description
n Type of work/Code
n Type of work/Description
n Technology/Code
n Technology/Description
n Contract/Renewal alert date
n Contract/Notice period (months)
n Contract/Renewal period (months)
n Contract/Tacit renewal
n Effective date (see below) (default value: now)
n Duration of the effective period (months) = Period (see below) (default value: 12)
n Contract/Cost (default value: 0.00)
n Contract/Currency ISO code (user's default value)

The Effective Date and Period fields will be used when a contract is created to generate an amendment. These fields are not used
when a contract is modified.
The Renewal alert date field is not taken into account if the renewal is tacit or if Renewal date > (End of agreement date - 1
month).

Only the active amendment is updated (contract header amendment no.)

Contracts/Assets

Import enum code = AssetContractImport

Swagger model correspondence = AssetContractImportModel

Used to import or update contracts.

n Contract code (required)

n Asset code (required)
n Amendment no. (optional)
n Cost (expressed in the contract's currency)

If the amendment number is not specified then the asset is added to the active amendment and following amendments if they
exist. The Asset block is updated.

- 482 -
 Data imports/exports settings

If the amendment no. is specified and it is not the active amendment, the asset is only added to the specified amendment. The
Asset block is not updated.

If the cost is entered without an amendment no. or with an active amendment no. then the cost of the contract's active amend-
ment (and header) is updated.
If the cost is entered with an non-active amendment no., only the cost of the specified amendment is updated, not the header
cost.

If the contract is not active, then there is a blocking message: "Cannot add asset. Contract XXX is not active"

Additional fields

Import enum code = AdditionalFieldConfigurationImport

Swagger model correspondence = AdditionalFieldConfigurationImportModel

Import name: Additional fields configuration import

Enables one to import additional fields.

n Additional field form (document type) -> Asset = ‘as’

n Allocation (required, all, no relationship, relationship selected) = TypicalRelationship**

You must enter:

- ‘none’ for no asset family.
- ‘all’ for all asset families.
- ‘selected’ for an asset family in particular.

n Relationship/code (required if type = relationship selected): asset family code

n Label (required): name of the additional field
n Type (required) = type of field

In the Type field you must enter:

- ‘in’ for an integer.
- ‘de’ for a decimal.
- ‘st’ for a character string.
- ‘da’ for a date.
- ‘ti’ for a time.
- ‘dt’ for a date with a time.
- ‘bo’ for a boolean.
- ‘cc’ for a price with a currency.
- ‘du’ for a duration.
- ‘va’ for a value list.

Complete this import with the imports:

- Additional fields/values in the lists
- Assets/additional fields = Import of data from additional fields on assets

In the Additional field allocation field, you must put the same value in the configuration import and in the additional field data
import.

Additional fields/Values in the lists

Import enum code = ValueListImport

Swagger model correspondence = ValueListImportModel

- 483 -
 Data imports/exports settings

Use to import values for additional value list type fields.

n Additional field form (required, today only asset possible)

n Form (required, today only asset possible)

n Allocation (required, all, no relationship, relationship selected) = TypicalRelationship**

- None: for no asset family

- All: for all asset families
- Selected: for the selected family

n Relationship/code (required if allocation = relationship selected): asset family code

n Additional field description (required)
n Value (required)

Additional fields/Assets

Import enum code = AdditionalFieldsValuesImport

Swagger model correspondence = AdditionalFieldsValuesImportModel

Used to import additional fields on assets.

Import name: Import of data from additional fields on assets

n Allocation (required, all, no relationship, relationship selected) = TypicalRelationship**

- None: for no asset family

- All: for all asset families
- Selected: for the selected family

n Document code = asset code (required)

n Additional field description (required)
n Value (required)

The data imported must follow the additional field type rules (according to the type or existing values in the value list) and asset
rules (this must be a field associated with the asset in question)
In the Additional field allocation field, you must put the same value in the configuration import and in the additional field data
import.

Tree partitions

Import enum code = TreePartitioningImport

Swagger model correspondence = TreePartitioningImportModel

The following data are used for mapping and import:

n Name: Required and unique

n Type: Required

- "dy" for dynamic

- "st" for static

This import will only enable you to import:

- one new static partition per asset selection

- 484 -
 Data imports/exports settings

- one new dynamic partition per asset node selection

If a partition has a Name that already exists, the line is rejected with the following message: "The partition XX already exists"
(use the message "is unique code") and number of the line concerned (no update to an existing partition).

The option to select by Asset family partition level is not proposed.

If the First partitioning level and Second partitioning level fields are not proposed in the mapping and when importing a Dynamic
type partition, the first partitioning level will be forced to Tree nodes (nodetree)

If Type unknown, the line is rejected with the message: "Type XX incorrect" (use the message "ErrorMes-
sageInvalidFieldWithValue") and number of the line concerned.

The Entities field of the tree partitioning form will be completed according to the entities entered in the import header.

Criticality

Import enum code = CriticalityImport

Swagger model correspondence = CriticalityImportModel

Used to import or update asset criticalities.

n Code (required)
n Description (required)
n Priority code
n Priority description
n Colour

If no colour is entered or the colour is unknown, it is initialised as white.

#5e626b
#999999
#795548
#ff3b3b
#ff7f00
#fecd55
#5ab77f
#3a9d23
#26619c
#7c4dff
#f4f4f4
#dadada
#a76726
#ea6463
#fd6c9e
#ffeb3b
#9fe855

- 485 -
 Data imports/exports settings

#c1e1fa
#28bbef
#b666d2

Triggers

Import enum code = TriggerImport

Swagger model correspondence = TriggerImportModel

Used to import or update trigger data for preventive work

n Description (required)
n Type (required)*
n Number of periods
n Frequency**
n Frequency (for periodic meter-type triggers only)
n Initialisation date
n Triggering time

*Typical trigger codes

Periodic calendar = t
Aperiodic calendar = d
Periodic meter = m
Aperiodic meter = v

**Periods
Years = y
Months = m
Week = w
Days = d

If the number of periods is not entered, it is filled in as 0

If the frequency is not entered, it is filled in with "day"
If the frequency is not entered, it is filled in as 0
For periodic meter triggers, enter the type, the description and the frequency
For aperiodic meter triggers, enter the type and the description; the values are imported via the aperiodic meter triggers import
For periodic calendar triggers, enter the type and description, the number of periods and the frequency (for a monthly trigger,
enter 1 in the number of periods and m in the frequency)

Updating the trigger type is only authorised if the trigger is not used on a PW.

Triggers/Aperiodic Calendars

Import enum code = TriggerAperiodicCalendarImport

Swagger model correspondence = TriggerAperiodicCalendarImportModel

Used to import or update trigger data for preventive work

n Trigger description (required)

n Date (required)

If the date does not exist, the occurrence is created.

If the date exists, nothing is done.

- 486 -
 Data imports/exports settings

Triggers/Aperiodic Meters

Import enum code = TriggerAperiodicMeterImport

Swagger model correspondence = TriggerAperiodicMeterImportModel

Used to import or update trigger data for preventive work

n Trigger description (required)

n Value (required)

If the value does not exist, it is imported.

If the value exists, nothing is done.

Purchase requests

Import enum code = PurchaseRequestImport

Swagger model correspondence = PurchaseRequestImportModel

Used to import or update purchase requests

n Code
n Status code** (required)
n Status description: Description of the reference status or equivalent status. If this field is not filled in, the status selec-
ted is the reference status associated with the code. The description field is used to identify the status.
n Requester
n Date/Time created
n Recipient
n Supplier (Partner code)
n Currency ISO code: If blank and supplier entered: supplier's currency; if blank and supplier not entered: requester's
currency if indicated, or import user's currency; if Currency ISO Code already entered and supplier entered incon-
sistently: no blockage, import of import values
n Archive

**Status codes:
CLOSED for Closed or equivalent
CANCELLED for Cancelled or equivalent
PROCESSED for Processed or equivalent
SENT for Sent or equivalent
TODO for In preparation or equivalent

A PR import can only be included in an import/export in one single entity

If the code is not entered, the automatic codification of the profile of the person running the import is applied
If this person does not have automatic codification configured, simple meter alternative codification is applied

If the creation date is not entered, it is entered as the day's date

If the requester is not entered, the person running the import is entered

If the status is not entered, it is initialised with the configuration of the entity for the Create PR action
If no configuration is entered, it is initialised with the reference status "In preparation"

Purchase requests/Comments

- 487 -
 Data imports/exports settings

Import enum code = PurchaseRequestCommentImport

Swagger model correspondence = PurchaseRequestCommentImportModel

Used to import or update purchase request comments

n PR code (required)
n User (required)
n Comment
n Date (Date/time)

Purchase requests/History of status changes

Import enum code = PurchaseRequestStateHistoryImport

Swagger model correspondence = PurchaseRequestStateHistoryImportModel

Used to import or update purchase request status change histories

n PR code (required)
n Date/Time (required)
n Status (Required)
n User (required)

Purchase requests/Parts

Import enum code = PurchaseRequestPartImport

Swagger model correspondence = PurchaseRequestPartImportModel

Used to import or update purchase request parts

n PR code (required)
n Part code (required if no description)
n Description (required if no part)
n Quantity
n Unit code (required)
n Unit description
n Unit price excl. tax: 0.00 if not entered; PR Header block currency
n Warehouse

If the quantity is not entered, it is initialised at 0

Work requests

Import enum code = WorkRequestImport

Swagger model correspondence = WorkRequestImportModel

Used to import or update work request data.

n Code
n Title
n Status code** (Description in the native language of the user who is importing)

- 488 -
 Data imports/exports settings

n Status description: If this field is not filled in, the status selected is the reference status associated with the code. The
description field is used to identify the status.
n Requester
n Asset
n Location
n Creation date
n Priority code
n Priority description
n Asset off
n Recipient
n Effect
n Work type code
n Work type description
n Technology code
n Technology description
n Deadline date/time
n Cost allocation code
n Cost allocation description
n WR type code
n WR type description
n Archive

**Status codes:
CLOSED for Closed or equivalent
DONE for Done or equivalent
CANCELLED for Cancelled or equivalent
INPROGRESS for In progress or equivalent
TODO for To do or equivalent

A WR import can only be included in a single entity

If the code is not entered, the automatic codification of the profile of the person running the import is applied
If this person does not have automatic codification configured, simple meter alternative codification is applied

If the creation date, start date or end date are not entered, they are entered as the day's date
If Boolean fields are not filled in, "no" is entered in them
If the sender is not entered, the person running the import is entered

If the status is not entered (code), it is initialised with the entity's configuration for the Create WR action
If no configuration is entered, it is initialised with the reference status "To be processed".

A WR import can only be included in a single entity

Work requests/Comments

Import enum code = WorkRequestCommentImport

Swagger model correspondence = WorkRequestCommentImportModel

Used to import or update work request data.

n Comment on WR:
n WR code (required)
n User (required)
n Comment

- 489 -
 Data imports/exports settings

n HTML comment
n Date (Date/time)

Work requests/History of status changes

Import enum code = WorkRequestStateHistoryImport

Swagger model correspondence = WorkRequestStateHistoryImportModel

Used to import or update work request data.

n History of status changes:

n WR code (required)
n Date/Time (required)
n Status (Required)
n User (required)

Work requests/Preferences

Import enum code = WorkRequestSchedulePreferenceImport

Swagger model correspondence = WorkRequestSchedulePreferenceImportModel

Used to import or update work request fulfilment preferences.

n WR code (required)
n Start date (required)
n End date (required)
n Comment

Currencies/Conversions

Import enum code = CurrencyConversionImport

Swagger model correspondence = CurrencyConversionImportModel

Used to import or update currency conversion rates.

n Currency 1 ISO code (Required) (Departure currency code)

n Currency 2 ISO code (Required) (Arrival currency code)
n Conversion
n Conversion Date/Time

If the conversion is left blank, it is entered as 1

If the date is left blank, it is entered as the current date/time.

Effects(Diagnoses)

Import enum code = EffectImport

Swagger model correspondence = EffectImportModel

Used to import or update effect data for work diagnoses.

- 490 -
 Data imports/exports settings

n Description (required)
n Comment

Effects/Assets(Diagnoses)

Import enum code = EffectAssetImport

Swagger model correspondence = EffectAssetImportModel

Used to import or update assets relating to effects for work diagnoses.

n Effect description (required)

n Asset code (required)

Effects/Technologies(Diagnoses)

Import enum code = EffectTechnologyImport

Swagger model correspondence = EffectTechnologyImportModel

Used to import or update technologies relating to effects for work diagnoses.

n Effect description (required)

n Technology code
n Technology description

Timetable

Import enum code = TimeSheetImport

Swagger model correspondence = TimeSheetImportModel

Used to import or update timetables of users and/or teams.

n Team code
n User (identifier)
n Start date (date/time, required)
n End date (date/time, required)
n Time slot type code (required)
n Description (required)
n Comment

You must enter a team code or a user identifier

If both are entered, the user's timetable is taken into account.

Entities

Import enum code = BodyImport

Swagger model correspondence = BodyImportModel

Used to import, create or update entities.

- 491 -
 Data imports/exports settings

n Name (Text, required)

n Address1 (Text, required)
n Address2 (Text, required)
n Address3 (Text, required)
n Postcode (Text)
n City (Text)
n Region (Text)
n Country (Text)
n Telephone (Text)
n Fax (Text)
n RCS (Text)
n NAF (Text)
n SIRET (Text)
n VAT no. (Text)

If the entity does not exist at the time of import, this entity is created.
If the entity exists at the time of import, it is updated.
When a new entity is created by import, the user - who must be an administrator - is associated with this entity.

Assets

Import enum code = AssetImport

Swagger model correspondence = AssetImportModel

Used to import or update assets in the application. The following data are used for mapping and import:

n Code: Required and unique (text).

n Description: Required (text).
n Status (description of the status).
n Location (text).
n Parent asset (code of the asset).
n Interface key (text).
n Asset family (code of the asset family).
n In service (Boolean).
n In-service date (date).
n Criticality (code of the criticality).
n Time zone (description of the time zone).
n Comment (text).
n Brand (description of the brand).
n Model (description of the model).
n Serial number (text).
n Supplier code (partner code).
n Manufacturer code (partner name).
n Manufacturer reference (text).
n Cost allocation (code of the cost allocation).
n Under warranty (Boolean).
n Warranty expiry date (date).
n Normal daily operating time (duration).
n Hourly downtime cost (decimal).
n Downtime hourly cost currency (ISO code).
n Purchase date (date).
n Purchase cost (decimal).
n Purchase cost currency (ISO code).

- 492 -
 Data imports/exports settings

n Date of manufacture (date).

n Maintenance work prohibited while in service (Boolean).
n Shared data (Yes/No)
n Entity (name)
n Is a node (check-box)

If the Shared data field is filled in the file, this field is not taken into account in the import header (and vice versa).
If an asset associated with several entities is modified, the Shared data field is not taken into account.

If the Entity field is filled in in the file, this field is not taken into account in the import header (and vice versa).
If an asset is associated with several entities, it is automatically shared.

Creation or Editing: import works differently according to whether it is in creation or editing.

Assets/Meters

Import enum code = AssetMeterImport

Swagger model correspondence = AssetMeterImportModel

Use to add meters to the assets already in the application (Meters block of the asset form). The following data are used for map-
ping and import:

n Update date
n Asset/Code: Required if Interface Key not entered (asset code).
n Interface key: Required if Code (Asset) not been entered, otherwise: Ignored
n Meter description: Required (text).
n Unit/Code: (code of the unit).
n Threshold: Optional (integer; blank if not entered).
n Delete Threshold: (boolean)
n Value: (integer).
n User/Identifier (identifier of the user).

Only the Asset/Code and Meter description fields are required under all circumstances.
There are two specific cases, where other fields must be filled in:
- being created; you must enter the Update date, Unit/Code and Value (the asset/meter link does not exist)
- being edited; you must enter Delete Threshold (the asset/meter link already exists)

If the meter has already done a rotation, it is impossible to delete. "Impossible to delete threshold. The meter has already done a
rotation".
The threshold must therefore be deleted by resetting the meter.

If in the import file, the Threshold is entered as well as Delete Threshold at T then the boolean is ignored and the threshold impor-
ted.

Assets/Tree partitions

Import enum code = TreePartitioningAssetImport

Swagger model correspondence = TreePartitioningAssetImportModel

The following data are used for mapping and import:

n Tree partition/Name: Required

n Asset/Code
n With child nodes (Boolean)

- 493 -
 Data imports/exports settings

If the partition is Dynamic type, the list of expected assets is a list of assets of the partition's entities, where "Is a node" is
enabled.
Once the import has been run, the list of authorised assets will be the imported nodes, the child nodes if With child nodes is
"True", and all the assets belonging to these nodes.

If the partition is Static type, the list of expected assets is a list of assets of the partition's entities.

The With child Nodes field is only taken into account when the tree partition is dynamic, otherwise, it is ignored.
If With child Nodes is "True", then all the child nodes of the imported node are taken into account in the tree partition.
If With child Nodes is "False", then the imported node is taken into account in the tree partition.

Inspections
If the partition name does not exist: Import completed with error. Message: "Partition XX unknown" (Existing message).
If the asset does not exist: Import completed with error. Message: "Asset code XX unknown" (Existing message).
If the asset does not belong to at least one of the partition's entity: Import completed with error. Message "Entity/ies of the
Asset code XX different to the partition XX" (Existing message).
For a dynamic partition, if the asset is not a node: Import completed with error. Message: "Asset code XX is not a node" (Existing
message).

Asset statuses

Import enum code = AssetStateImport

Swagger model correspondence = AssetStateImportModel

Used to import or update asset statuses

n Description (required)
n Working

If In service is left blank, it is automatically entered as Yes.

WO statuses

Import enum code = WorkOrderStateImport

Swagger model correspondence = StateImportModel

Used to import WO statuses.

n Description (required)
n Equivalent status/description (required): corresponds to the reference status (To do, In progress, done, cancelled, clo-
sed, etc.)

Order statuses

Import enum code = PurchaseOrderStateImport

Swagger model correspondence = StateImportModel

Used to import order statuses.

- 494 -
 Data imports/exports settings

n Description (required)
n Equivalent status/description (required): corresponds to the reference status (In preparation, Sent, etc.)

PR statuses

Import enum code = PurchaseRequestStateImport

Swagger model correspondence = StateImportModel

Used to import PR statuses.

n Description (required)
n Equivalent status/description (required): corresponds to the reference status (In preparation, sent, processed, can-
celled, closed, etc.)

WR statuses

Import enum code = WorkRequestStateImport

Swagger model correspondence = StateImportModel

Used to import WR statuses.

n Description (required)
n Equivalent status/description (required): corresponds to the reference status (To be processed, in progress, com-
pleted, cancelled, closed, etc.)

Asset families

Import enum code = AssetFamilyImport

Swagger model correspondence = CodeNameParentImportModel

Used to import or update asset families.

n Code (required)
n Description (required)
n Parent family code
n Parent family description

Part families

Import enum code = PartFamilyImport

Swagger model correspondence = CodeNameParentImportModel

Used to import or update part families.

n Code (required)
n Description (required)
n Parent family code
n Parent family description

Files

- 495 -
 Data imports/exports settings

Used to import or update files.

n Document type (required)*

n Document code (required)
n File name (required)
n Description

*Document types:
• "wr" -> WR
• "wo" -> WO
• "pa" -> Part
• "pt" -> Partner
• "as" -> Asset
• "pm" -> PM/PW
• "jb" -> job
• "ta" -> Task
• "ct" -> Contract
• "wg" -> Grouped WO
• "in" -> Inventory
• "pr" -> PR
• "or" -> Order

The import retrieves files from the directory that contains the import file.
The file name may contain a path.
E.g.
- the import file "name" is "Rep1\import.csv"
- the "name" of the file to be retrieved is "Rep2\Nom.jpg"
Then the import will get the associated file from "Rep1\Rep2\Nom.jpg"

In parallel to the file "database" import, the file is physically copied to the server.

Jobs

Import enum code = JobImport

Swagger model correspondence = JobImportModel

Used to import or update job data.

n Code (required)
n Description (required)
n Comment

Jobs/Assets

Import enum code = JobAssetImport

Swagger model correspondence = JobAssetImportModel

Used to import or update the data of assets linked to jobs.

n Job code (required)

n Asset code (required)

- 496 -
 Data imports/exports settings

Jobs/Tasks

Import enum code = JobTaskImport

Swagger model correspondence = JobTaskImportModel

Used to import or update the data of tasks linked to jobs.

n Job code (required)

n Task description (required)
n Order (required)

Asset groups

Import enum code = AssetGroupImport

Swagger model correspondence = AssetGroupImportModel

Used to import or update asset group data.

n Code (Text) (Required)

n Description (Text) (Required)

Asset groups/Assets

Import enum code = AssetGroupAssetImport

Swagger model correspondence = AssetGroupAssetImportModel

Used to import or update assets on asset groups.

n Asset group/Code (required) (Text)

n Asset/Code (required) (Text)
n Distribution (Positive integer)

If the distribution is not entered, it is initialised at 1

Sage X3 movements history

Import enum code = MovementImport X3

Swagger model correspondence = MovementImportX3Model

Used to import the movements history in Sage X3 format.

n Date (Date) (Required)

n Part/Code (Text) (Required)
n Warehouse/Code (Text) (Required)
n Unit/Code (Text) (Required)
n Quantity (Decimal, can be negative!!) (Required)
n Overall price (Positive decimal) (Required)
n Currency ISO code (Text)
n Batch (Text)
n Expiry date (Date)
n Movement type (Text) (Required)

- 497 -
 Data imports/exports settings

n Interface key (Text) (Required)

n User/Login (Text)

Importing a movement does not update the stock; the movement alone is saved to the database.

If the movement quantity is positive, the movement is an entry (in in the movementdirection column)
If the movement quantity is negative, the movement is a withdrawal (ou in the movementdirection column)
If any of the required fields are left blank, an import error is generated
When importing the movement, the unit price in the movement table = Overall price entered / Absolute value (Quantity ente-
red)
If the currency code is left blank, the import user’s currency is used
If the batch does not correspond to any identifier in the batch table, the data is ignored
The expiry date is ignored (no message for either)
If the movement with this interfacekey is already present in MX, it is not reimported
If no user has been entered for the movement, the import user is assigned to the movement

The movement type sent by X3 is a letter. The table of correspondence indicates what each letter corresponds to. Messages cor-
responding to the letters below go in the movement title

Number/Code/Message
1 E Miscellaneous entry
2 S Miscellaneous withdrawal
3 R Supplier reception
4 L Customer delivery
5 O OF Entry
6 F OF Withdrawal
7 C Change of location
8 Q Quality control
9 T Change of status
10 N Inter-site transfer reception (not used)
11 U Reception return
12 I Delivery return
13 V Inventory
14 A Inter-site transfer
15 B Transfer for subcontracting (not used)
16 D Reception for subcontracting
17 P Delivery ready
18 P Delivery return ready
19 G Restock
20 K Delivery for subcontracting
21 J Refractioning
22 X Storage plan
23 W Value change
24 M Service request
25 Y Resupply
26 Z Stock change
27 1 Internal transfer withdrawal
28 2 Internal transfer entry
29 3 Subcontracting order withdrawal
30 4 Reception ready (not used)
31 5 Reception return ready (not used)
32 6 Reception return for subcontracting
33 7 Delivery return for subcontracting
34 8 Analysis request

- 498 -
 Data imports/exports settings

Allocations

Import enum code = AccountAssignmentImport

Swagger model correspondence = CodeNameParentImportModel

Used to import or update data in the Cost Allocation TDR. The following data are used for mapping and import:

n Code: Required (text).

n Description: Required (text).
n Cost allocation: Optional (cost allocation code).
n Parent cost allocation: Optional (parent cost allocation code).

The parent cost allocation must have been imported before a child cost allocation can be imported. This requirement must
consequently be taken into account in the ordering of the import file lines.

Preventive works

Import enum code = PreventiveMaintenanceImport

Swagger model correspondence = PreventiveMaintenanceImportModel

Used to import or update preventive work data

n Comment
n Meter/PW trigger threshold
n Contract/Code
n Contract/Title
n Criticality/Code
n Criticality/Description
n Date of next occurrence
n Trigger/Name: (essential to make all the related fields operational; to be entered if you want to update the triggering
method)
n Completion time limit
n Last work order generated
n Recipient/Last name
n Recipient/First name
n Currency/Currency ISO code If not entered, the currency in the general settings is allocated to the new PW.
n Issuer/Last name
n Issuer/First name
n Entity/Name
n Asset/Code
n Asset/Description
n Issuer ID
n Cost allocation/Code
n Cost allocation/Description
n Maintenance work prohibited while in service (Boolean)
n Preventive work/Code
n Preventive work/Title
n Asset off
n Rolling schedule
n Distribution
n Technology/Code
n Technology/Description

- 499 -
 Data imports/exports settings

n Type of work/Code
n Type of work/Description
n PW trigger time limit unit
n Priority/Code
n Priority/Description

PW triggering method in WO (Selection "Actual achievement of the value of the meter" = ah or "Projection in time" = pt; to be
entered if you want to update it)

A PW import can only be included in a single entity.

If the code is not entered, the automatic codification of the profile of the person running the import is applied
If this person does not have automatic codification configured, simple meter alternative codification is applied
If the initialisation date is not entered, it is entered as the day's date
If Boolean fields are not filled in, "no" is entered in them
If the sender is not entered, the person running the import is entered
The Statuses fields without trigger and Days without trigger are filled in with the entity configuration values
If the trigger time is not entered, the entity configuration value is entered

If an Asset/Code is entered, an asset line is added to the PW with a distribution of 1

If an Asset/Code is entered and the asset in question is already associated with the PW, no asset line is added

If the "PW trigger method in WO" and "PW trigger threshold" fields are not entered, they are initialised with the entity confi-
guration
If the initialisation threshold field is not entered, it is initialised with 0
When the PW has a calendar trigger: The "Initialisation threshold", "PW trigger method in WO" and "PW trigger threshold" fields
are not imported
When the PW has a meter trigger:
- If the trigger method is Projection in Time, the "PW trigger threshold" field is not imported
- If the trigger method is Actual Achievement, the "PW trigger time limit" field is not imported

The Meter/PW trigger threshold and PW trigger time limit fields must be filled in together.

Preventive work/Shutdowns

Import enum code = PreventiveMaintenanceDownTimeImport

Swagger model correspondence = PreventiveMaintenanceDownTimeImportModel

Used to import or update preventive work data.

n PW code (required)
n Shutdown duration (required): (whole) in minutes -> decimals not permitted
n Task code

Preventive work/Assets

Import enum code = PreventiveMaintenanceAssetImport

Swagger model correspondance = PreventiveMaintenanceAssetImportModel

Used to import or update preventive work data.

n Asset/Code (required)
n Preventive work/Code(required)

- 500 -
 Data imports/exports settings

n Distribution

If the grouped work module is enabled, several assets can be imported for any PW.
(unlike the case where the module is disabled = each asset is then imported by overwriting the previous one by importing the
PW only).

Preventive work/Jobs

Import enum code = PreventiveMaintenanceJobImport

Swagger model correspondence = PreventiveMaintenanceJobImportModel

Used to import or update preventive work data.

n PW code (required)
n Job code (required)
n Asset/Code (Text)
Auto update of resources/tasks’ (Boolean). If this field has been left blank, it is automatically set to ‘true’. This field
enables us to determine whether the PW resources are updated when a task is changed.

If the asset code is left blank, the job imported into the PW is associated with all the PW assets.
If the asset code is entered, the job imported into the PW is associated with the asset.

Preventive work/Labour

Import enum code = PreventiveMaintenanceLabourImport

Swagger model correspondence = PreventiveMaintenanceLabourImportModel

Used to import or update preventive work data.

n PW code (required)
n Technician category code (required)
n Technician category description
n Technician (ID)
n Duration: (whole) in minutes -> decimals not permitted
n Task code

If the duration is not entered, it is initialised at 0.

The duration of a labour line must not be above 24H00 or 1,440 minutes
Categories: If the category code and category description do not match, the labour line is imported to the code of the category
entered.

Preventive work/Parts

Import enum code = PreventiveMaintenancePartImport

Swagger model correspondence = PreventiveMaintenancePartImportModel

Used to import or update preventive work data.

n Unit description (required if Unit/Code not entered)

n Part description (if entered and if Part/Code not entered, part line created is open and not listed)
n Preventive work/Code (required)
n Warehouse/Code (required if Part/Code entered)
n Part/Code
n Quantity

- 501 -
 Data imports/exports settings

n Reserved
n Task/Description
n Part/Code (required if Unit description not entered)

Unit description or Unit/Code must be valid in the database.

Preventive work/Subcontractor

Import enum code = PreventiveMaintenanceSubContractorImport

Swagger model correspondence = PreventiveMaintenanceSubContractorImportModel

Used to import or update preventive work data.

n PW code (required)
n Subcontractor category code (required)
n Subcontractor category description
n Subcontractor (Code)
n Duration: (whole) in minutes -> decimals not permitted
n Part cost
n Part cost currency ISO code
n Task code

If the duration is not entered, it is initialised at 0. Same for the part cost
If the currency code is not entered, the default currency is entered

Brands

Import enum code = BrandImport

Swagger model correspondence = NameImportModel

Used to import brands into the application. The following data are used for mapping and import:

n Description: required and unique (text)

Measurements

Import enum code = MeasurementImport

Swagger model correspondence = MeasurementImportModel

Used to import measurements into the application. The following data are used for mapping and import:

n Measurement/Code: required.
n Measurement/Description: required.
n Measurement type/Code
n Unit/Code
n Decimals: value = "2" by default.
n Min Value
n Max Value
n Alarm max value
n Alert max value
n Target value

- 502 -
 Data imports/exports settings

n Alert min value

n Alarm min value
n Work model if reading above alarm max/Code
n Work model if reading above alert max/Code
n Work model if reading below alert min/Code
n Work model if reading below alarm min/Code

Inspections:
If Decimals > 5, error message: "The number of decimals must be between 0 and 5".

If Max Value <= Min Value, error message:"The Max value must be strictly above the Min value".

If Min value and/or Max value are entered, check for each value that it is between Min value and Max value. If not observed,
error message "The alarm and alert values must be strictly above the Min Value and strictly below the Max Value"

The check on entering alarm and alert values between them is performed according to the following general rule:
Max alarm value > Max alert value > Target value > Min alert value > Min alarm value
If a value does not observe this rule, error message: "Incorrect values. Follow the rule: Max alarm value > Max alert value > Tar-
get value > Min alert value > Min alarm value"

Models

Import enum code = ModelImport

Swagger model correspondence = ModelImportModel

Used to import models into the application. The following data are used for mapping and import:

n Description: required Unicity by brand (Text)

n Brand: Description of the brand

Storage locations

Import enum code = StorageLocationImport

Swagger model correspondence = StorageLocationImportModel

Used to import storage locations into the application. The following data are used for mapping and import:

n Code: required and unique (text)

n Description: required (text)
n Warehouse: required (code of the warehouse)

Acceptance lines with movement

Import enum code = DeliveryWithMovementImport

Swagger model correspondence = DeliveryWithMovementImportModel

Enables you to import acceptance lines in order to update the order lines delivered. The following data are used for mapping and
import:

n AutoincrementId: required (=AutoincrementId(order line))

n Date/Time of acceptance: optional (=Date/Time(Import) if not sent)
n Quantity accepted: required

- 503 -
 Data imports/exports settings

n Warehouse/Code: optional
n Delivery note: required (calculated if not sent)
n Balanced: Yes/No

If the AutoincrementId field does not correspond to an ID of the PurchaseOrderPart table, error message "This value for the
AutoincrementID field is invalid: ID no."

The quantity received of the file follows these management rules:

o > (sum of quantities received in the order line corresponding to AutoincrementId) =>acceptance created on this order
line and Quantity accepted = file quantity received
o < (quantity ordered) => acceptance line created and Balanced = No (except if Balanced = Yes in the file received or in
the order line)
o >=(quantity ordered)=> Balanced = Yes (except if Balanced = No in the file received)

Values of the Warehouse/Code field:

o Warehouse/Code=0 if warehouse entered in the import: Warehouse (import)

o Warehouse/Code=1 if warehouse on order line: Warehouse (order line)
o Warehouse/Code=2 if part is in stock at the main warehouse of the order entity: Warehouse (main warehouse of the
order entity)
o Warehouse/Code=3 if part is in stock at a warehouse linked to the order entity: Warehouse (no.1 linked to the entity of
the order found where the part is in stock)
o Warehouse/Code=4 if a warehouse is the main warehouse of the order entity: Warehouse (main warehouse of the
order entity)
o Warehouse/Code= 5 if first warehouse linked to the order entity found

If the Delivery note field is not entered, it is calculated and takes on the first value available on the numerical meter (same as
Order X3 progress).

The unit is the order line unit

If the order status is "In Preparation" or equivalent, blocking message: "Acceptance impossible. The order is not in Sent status".
If the order status is "Cancelled" or equivalent, blocking message: "Acceptance impossible. The order has been cancelled".
If the order status is "Closed" or equivalent, blocking message: "Acceptance impossible. The order is closed".

Stock rooms

Import enum code = StoreImport

Swagger model correspondence = StoreImportModel

Used to import warehouses:

n Code (required)
n Description (required)
n Time zone
n Currency
n Negative Stock (checkbox)

If the time zone is left blank, the import user’s time zone is entered.
If the currency is left blank, the import user’s currency is entered.

Payment terms

- 504 -
 Data imports/exports settings

Import enum code = PaymentTermImport

Swagger model correspondence = PaymentTermImportModel

Used to import terms of payment:

n Description: required (text)

Movements

Import enum code = MovementImport

Swagger model correspondence = MovementImportModel

Used to import stock movements and update the stock. The following data are used for mapping and import:

n Type: Required (Entry or Withdrawal) -> -> "in" (entry) or "out" (withdrawal)
n Date: Required (Date/time in the selected format). If this date is prior to the date for changing the part from “Mana-
ged in stock” to “Not managed in stock”, or after the days’ date, the movement is forbidden.
n Title (Text).
n User: Required (identifier of the user).
n Part: Required (code of the part).
n Warehouse: Required (code of the warehouse).
n Quantity: Required (decimal). During a Type=Withdrawalmovement, if negative stock is forbidden in the warehouse,
and if the Quantity entered is greater than the Actual quantity for the part, a blocking message appears: “Negative
stock is not allowed in this warehouse”.
n Unit: Required (code of the unit).
n Unit price: Required (decimal).
n Currency: Required (ISO code of the currency).
n Asset (asset code).
n WO (code of the WO).
n Cost allocation (code of the cost allocation).

When a movements import is run, the valuation rules defined in the application are applied (WAUP by warehouse, LIFO, etc.).
For this reason, in the case of a part removal movement, the unit price used is the price calculated automatically by the appli-
cation, not the price entered in the import file.

Parts list

Import enum code = PartAssetImport

Swagger model correspondence = PartAssetImportModel

Used to update the part/asset link in the application (Asset block in a part form and Parts block in an asset form). The following
data are used for mapping and import:

n Part: Required (code of the part).

n Asset: Required (code of the asset).
n Quantity: Required (decimal).
n Unit: Required (code of the unit).
n Comment (text).

Partners

Import enum code = PartnerImport

- 505 -
 Data imports/exports settings

Swagger model correspondence = PartnerImportModel

Used to import or update partners in the application. The following data are used for mapping and import:

n Name
n Code: Required and unique (text)
n Web site (text).
n E-mail (text).
n Subcontractor: Boolean (=True, default value in creation)
n Supplier: Boolean (=True, default value in creation)
n Manufacturer: Boolean (=True, default value in creation)
n Comment (text).
n Main category: Required if subcontractor = yes (code of the partner category).
n Currency: Currency ISO code

The Code field, as it is unique, enables the Partner to be identified unambiguously.

If the currency is not entered, the currency in the general settings will be retrieved to create a new partner.
If the Supplier, Subcontractor and Manufacturer fields are left blank, they are automatically entered as "Yes" (True) when the
routine is run.

Partners/Addresses

Import enum code = PartnerAddressImport

Swagger model correspondence = PartnerAddressImportModel

Used to import or update the addresses of the partners already in the application (Addresses block of a partner form). The fol-
lowing data are used for mapping and import:

n Partner: Name of the partner. Required if the partner code has not been entered
n Code: Partner code (Text). Required if the partner name has not been entered
n Name (Address name): Required (text).
n Address 1 (text).
n Address 2 (text).
n Address 3 (text).
n Postcode (text).
n City (text).
n Region (text).
n Country (text).
n Telephone (text).
n Fax (text).
n Main (Boolean).

Either the code or Partner name is required.

Partner searching is related to the field entered. If both fields have been entered, the code has priority.

Partners/Categories

Import enum code = PartnerPartnerCategoryImport

Swagger model correspondence = PartnerPartnerCategoryImportModel

Used to import or update the categories of the partners already in the application (Categories block of a partner form). The fol-
lowing data are used for mapping and import:

- 506 -
 Data imports/exports settings

n Partner: Required (partner code).

n Category: Required (code of the partner category).
n Hourly cost (decimal).
n Hourly cost currency (ISO code)
n Main (Boolean).

Partners/Contacts

Import enum code = PartnerContactImport

Swagger model correspondence = PartnerContactImportModel

Used to import or update the contacts of the partners already in the application (Contacts block of a partner form). The following
data are used for mapping and import:

n Partner: Required (name of the partner).

n Code: Partner code (Text). Required if the partner name has not been entered
n Title (Text).
n First name (text).
n Name (text).
n Position (text).
n E-mail (text).
n Telephone (text).
n Extension (text).
n Mobile (text).
n Fax (text).
n Main (Boolean).

Either the code or Partner name is required.

Partner searching is related to the field entered. If both fields have been entered, the code has priority.

Partners/Assets

Import enum code = PartnerAssetImport

Swagger model correspondence = PartnerAssetImportModel

Used to import or update the assets linked to partners already in the application (Assets block of a partner form). The following
data are used for mapping and import:

n Partner: Required (partner code).

n Asset code (required)

Parts

Import enum code = PartImport

Swagger model correspondence = PartImportModel

Used to import or update parts in the application. The following data are used for mapping and import:

n Code: Required and unique (text).

n Description: Required (text).
n Part family: Required (code of the part family).
n Manufacturer (partner code).

- 507 -
 Data imports/exports settings

n Manufacturer reference (text).

n Default unit: Required (code of the unit).
n Comment (text).
n Standard price

By default, the imported parts are not under stock management.

Equivalent parts

Import enum code = PartEquivalentPartImport

Swagger model correspondence = PartEquivalentPartImportModel

Used to import or update equivalent part data.

n Part code (required)

n Equivalent part code (required)
n Reciprocity (Boolean)

Parts/Suppliers

Import enum code = PartSupplierImport

Swagger model correspondence = PartSupplierImportModel

Used to add to or update the parts supplier repository in the application (Suppliers block). The following data are used for map-
ping and import:

n Part: Required (code of the part).

n Partner/Name: Required (name of the partner).
n Partner/Code (Text) Either the code or Supplier name is required. Supplier searching is related to the field entered. If
both fields have been entered, the code has priority
n Reference (text).
n Discount (decimal).
n PO unit: Required (code of the unit).
n Unit price (decimal).
n Unit price currency (ISO code).
n Lead time (decimal).
n Main (Boolean).
n Minimum purchase quantity (decimal).
n Price validity (date).
n Last update (date).

Parts/Images

Import enum code = PartImageImport

Swagger model correspondence = PartImageImportModel

Used to import or update the parts repository in the application. The following data are used for mapping and import:

n Part code (required)

n File name (required)
n Main (YES/NO) if there is no image associated with the part, then the imported image is the main image, if there is

- 508 -
 Data imports/exports settings

already a main image and this field is set to YES, then the imported image becomes the main image. If when the
import is complete, there is no main image, then the former main image is again defined as the main image.

In parallel to the file "database" import, the file must be physically copied to the server.

Parts/Warehouses

Import enum code = PartStockImport

Swagger model correspondence = PartStockImportModel

Used to update the parts storage data in the application (Stocks block). The following data are used for mapping and import:

n Part: Required (code of the part).

n Warehouse: Required (code of the warehouse).
n Managed in stock (Boolean):
n Storage location (code of the storage location).
n Storage unit: Required if under stock management = Yes (code of the storage unit).
n Restock point (decimal).
n Minimum stock (decimal).
n Maximum stock (decimal).

The import of parts/warehouses will never overwrite the existing quantities.

In stock="False" => Restock point:=Minimum stock=Maximum stock=0

Meter readings

Import enum code = AssetMeterReadingImport

Swagger model correspondence = AssetMeterReadingImportModel

Used to import meter readings into the application. The following data are used for mapping and import:

n Work order/Code:
n Update date: Date/Time
n Meter description
n Asset/Code: Required if Interface Key not entered (asset code).
n Interface key: Required if Code (Asset) not been entered, otherwise: Ignored.
n User/Identifier
n Value

The rules applicable to the meter readings in an application WO are the same. The preventive plan is consequently updated
according to the imported meter readings.
When registering a reading, there is no processing of meter PWs linked to the meter.

Measurement readings

Import enum code = AssetMeterReadingImport

Swagger model correspondence = AssetMeterReadingImportModel

Used to import measurement readings into the application. The following data are used for mapping and import:

- 509 -
 Data imports/exports settings

n Update date: required Date/Time

n Asset/Code: required if Interface Key not entered (asset code).
n Interface Key: required if Code (Asset) not entered, otherwise: Ignored
n Measurement/Code: required
n User/Identifier
n Value: required

If Code (Asset) unknown, blocking message: "Asset code unknown".

If Code (Measurement) unknown, blocking message: "Measurement code unknown".
If Asset/Measurement link unknown, blocking message "Asset/Measurement link non-existent".

The Update date must be strictly above the date/time of the previous value.
If not observed, blocking message: "The update date must be later than the date/time of the old value".

The Update date must be strictly before the day’s date/time.

If not observed, blocking message: "The update date must be later than day's date".

If Min value and Max value entered in the Measurement, then Max value >= Value entered >=Min value
If value entered > Max value, blocking message: "Value entered above Max Value"
If value entered < Min Value, blocking message: "Value entered below Min value"

No check on the value in relation to the previous values.

Measurement statements/History

Import enum code = AssetMeterReadingHistoryImport

Swagger model correspondence = AssetMeterReadingHistoryImportModel

Used to import measurement readings into the application. The following data are used for mapping and import:

n Work order/Code
n Grouped work order/Code
n Update date: required Date/Time
n Asset/Code: required
n Measurement/Code: required
n User/Identifier
n Value: required

If Code (Asset) unknown, blocking message: "Asset code unknown".

If Code (Measurement) unknown, blocking message: "Measurement code unknown".
If Code (WO) unknown, blocking message: "Work order code unknown".
If Code (Grouped WO) unknown, blocking message: "Grouped work order code unknown".
If Code (WO) and Code (Grouped WO) are entered, blocking message: "The reading can only be linked to one WO or Grouped
WO".
If Asset/Measurement link unknown, blocking message "Asset/Measurement link non-existent".

The Update date must be strictly before the day’s date/time.

If not observed, blocking message: "The update date must be later than day's date".

No check on the value in relation to the previous values, or on the WO triggering according to alarm and alert values.

Remedies (Diagnoses)

- 510 -
 Data imports/exports settings

Import enum code = RemedyImport

Swagger model correspondence = RemedyImportModel

Used to import or update remedies for work diagnoses.

n Description (required)
n Comment

Remedies/Assets (Diagnoses)

Import enum code = RemedyAssetImport

Swagger model correspondence = RemedyAssetImportModel

Used to import or update assets linked to remedies for work diagnoses.

n Remedy description (required)

n Asset code (required)

Remedies/Jobs (Diagnoses)

Import enum code = RemedyJobImport

Swagger model correspondence = RemedyJobImportModel

Used to import or update jobs linked to remedies for work diagnoses.

n Remedy description (required)

n Job code (required)

Remedies/Technologies (Diagnoses)

Import enum code = RemedyTechnologyImport

Swagger model correspondence = RemedyTechnologyImportModel

Used to import or update remedy technologies for work diagnoses.

n Remedy description (required)

n Technology code (required)
n Technology description

Parts stock

Import enum code = StockImport

Swagger model correspondence = StockImportModel

Used to update the parts quantities and storage data in the application (Stocks block). The following data are used for mapping
and import:

n Part: Required (code of the part).

n Warehouse: Required (code of the warehouse).
n Managed in stock (Boolean):

- 511 -
 Data imports/exports settings

n Storage location (code of the storage location).

n Storage unit: Required if under stock management = Yes (code of the storage unit).
n Actual quantity (decimal). : if the quantity is entered, the WAUP is required. If negative stock is forbidden in the ware-
house, and if the Actual quantity is absolutely negative, a blocking message appears: “Negative stock is not allowed in
this warehouse”.
n PUMP (decimal). : required if the quantity is entered
n WAUP currency (ISO code).
n Restock point (decimal).
n Minimum stock (decimal).
n Maximum stock (decimal).

A stock import overwrites the previous stock. For batch management, all the existing batches for the part/warehouse pair are
marked as consumed.
The movements are made during this import.

In stock="False" => Restock point:=Minimum stock=Maximum stock=0

Stock of parts without movement (Sage X3)

Import enum code = StockImportWithoutMovement

The import without movement is only for clients who have stock management (regular update type) on a tool separate from MX
(e.g. ERP type stock management software).
The lack of movement means that this import must not be used to initialise the stock and Stock analysis must not be used.

The following warning message is given to the user: "Do not use this import when MX is stock master. The absence of movement
will not allow for stock to be issued with a useable date".

Used to update the stock from X3 and manage the movements separately.

n Part: Required (code of the part).

n Warehouse: Required (code of the warehouse).
n Managed in stock (Boolean):
n Storage location (code of the storage location).
n Storage unit: Required if under stock management = Yes (code of the storage unit).
n Actual quantity (decimal). : if the quantity is entered, the WAUP is required. If negative stock is forbidden in the ware-
house, and if the Actual quantity is absolutely negative, a blocking message appears: “Negative stock is not allowed in
this warehouse”.
n PUMP (decimal). : required if the quantity is entered
n WAUP currency (ISO code).
n Restock point (decimal).
n Minimum stock (decimal).
n Maximum stock (decimal).

A stock import overwrites the previous stock. No movement is made during this import.

In stock="False" => Restock point:=Minimum stock=Maximum stock=0

Tasks

Import enum code = TaskImport

Swagger model correspondence = TaskImportModel

Used to import or update task data:

- 512 -
 Data imports/exports settings

n Description: Required
n Comment
n Type: Optional. By default, or if not selected in the mapping, Type ="std"

3 task types are used:

¤ std => Standard type task
¤ mtr => Meter reading type task
¤ mer => Measurement reading type task

It is possible to change the task type of an existing task via import when the description of the existing task is used in the import.

Tasks/Shutdowns

Import enum code = TaskDownTimeImport

Swagger model correspondence = TaskDownTimeImportModel

Used to import or update task machine shutdowns:

n Task code (required)

n Shutdown duration (required)

Tasks/Labour

Import enum code = TaskLabourImport

Swagger model correspondence = TaskLabourImportModel

Used to import or update task labour:

n Task code (required)

n Technician category code (required)
n Technician category description
n Technician
n Duration

If the duration is not entered, it is initialised at 0.

Tasks/Parts

Import enum code = TaskPartImport

Swagger model correspondence = TaskPartImportModel

Used to import or update task parts:

n Task code (required)

n Part code (required if no description)
n Description (required if no part code)
n Quantity
n Unit Code (required if part listed)
n Unit description

Tasks/Subcontractors

Import enum code = TaskSubContractorImport

- 513 -
 Data imports/exports settings

Swagger model correspondence = TaskSubContractorImportModel

Used to import or update subcontractors attached to tasks:

n Task code (required)

n Subcontractor category code (required)
n Subcontractor category description
n Subcontractor
n Duration
n Part cost
n Part cost currency ISO code

Technologies

Import enum code = TechnologyImport

Swagger model correspondence = TechnologyImportModel

Used to import or update technologies.

n Code (required)
n Description (required)

VAT

Import enum code = VatImport

Swagger model correspondence = VatImportModel

Only available if the VAT module is enabled.

Enables you to import (and create) VATs but not to update them

n VAT/Code (required)
n VAT/Rate (required): Decimal

If the Code already exists, blocking message: "VAT code already exists".

Types of contract

Import enum code = ContractTypeImport

Swagger model correspondence = ContractTypeImportModel

Used to import or update contract types.

n Code (required)
n Description (required)

Type of time slot

Import enum code = TimeSlotTypeImport

Swagger model correspondence = TimeSlotTypeImportModel

Used to import or update types of time slots

- 514 -
 Data imports/exports settings

n Code (required)
n Description (required)
n Productive (yes/no)
n Colour (colour ISO code)

If Productive is not entered, the default is yes

If the colour is not entered, the default is white

WR type

Import enum code = WorkRequestTypeImport

Swagger model correspondence = WorkRequestTypeImportModel

Used to import or update WR types.

n Code (required)
n Description (required)

Types of work

Import enum code = WorkingTypeImport

Swagger model correspondence = WorkingTypeImportModel

Used to import or update work types.

n Code (required)
n Description (required)

Measurement types

Import enum code = MeasurementTypeImport

Swagger model correspondence = MeasurementTypeImportModel

Used to import or update measurement types.

n Code (required)
n Description (required)

Units

Import enum code = UnitImport

Swagger model correspondence = UnitImportModel

Used to import or update the units used in the application.

n Code: (required and unique) (Text)

n Description (required) (text)

Units/Conversions

Import enum code = UnitConversionImport

- 515 -
 Data imports/exports settings

Swagger model correspondence = UnitConversionImportModel

Used to import or update unit conversions:

n Unit 1 (required) (Start unit code)

n Unit 2 (required) (End unit code)
n Conversion

If the conversion is not entered, then the units cannot be converted with one another.

Priorities

Import enum code = UrgencyImport

Swagger model correspondence = UrgencyImportModel

Used to import or update work priorities.

n Code (required)
n Description (required)
n Type of lead time: h (for hours) or d (for days)
n Lead time
n Colour

If the lead time has been left blank, it is entered as 0

If the lead time type has been left blank, it is entered as “hours”
If no colour is entered or the colour is unknown, it is initialised as white.
#5e626b
#999999
#795548
#ff3b3b
#ff7f00
#fecd55
#5ab77f
#3a9d23
#26619c
#7c4dff
#f4f4f4
#dadada
#a76726
#ea6463
#fd6c9e
#ffeb3b
#9fe855
#c1e1fa
#28bbef

- 516 -
 Data imports/exports settings

#b666d2

Users

Import enum code = UserImport

Swagger model correspondence = UserImportModel

Used to import or update user data:

Beforehand, it is essential to define a default password in the application general settings [Settings-Configuration-General set-
tings]
Imported users then retrieve the password configured:

When the user logs in for the first time, he is obliged to change his password.

n Last name (required)

n First name (required)
n ID (required)
n User profile (required)
n E-mail
n Phone number
n Language (required)*: reference language of application labels
n Personalised language/Code: if entered, the personalised language is allocated to the user. Otherwise the (reference)
language code is allocated to them.
n Display language (required)*
n Time zone
n Currency
n Type (internal = in or external = ex)
n Partner
n DIMO Maint MX access (required)(Boolean)
n DIMO Maint App access (required)(Boolean)
n Separation character for CSV exports (example: , or ;). If it is not entered, ";" is used by default.

If the time zone is not entered, the time zone entered in the general configuration is filled in
If the currency is not entered, the currency entered in the general configuration is filled in
If the type is not entered, it is filled in as "Internal".
The user's account type will be the user profile account type.
The user will be automatically associated with the entities configured in the import.
User management and profile management are unchecked by default following an import of supervisor-type users.

*Language format:
- fr-fr (French)
- en-us (US English)
- en-gb (UK English)
- es-es (Spanish)
- es-mx (Spanish/Mexico)
- de-de (German)
- sv-se (Dutch)
- vi-ve (Vietnamese)

Users/Tree partition

- 517 -
 Data imports/exports settings

Import enum code = TreePartitioningUserImport

Swagger model correspondence = TreePartitioningUserImportModel

n Tree partition/Name (required)

n User profile/Code
n User/Identifier

This import is only available if the ‘Tree partitioning’ module is enabled.

This import enables you to import:

- profiles whose account types are Requester, User or Guest
- users belonging to profiles whose account types are Requester, User or Guest

If the User profile is entered then the User/ID field is ignored.

If the User profile is entered then all the child profiles, excluding Supervisor account type child profiles, and unarchived users
with at least one partitioning entity, are taken into account.

Inspections
If the partition name does not exist: Import completed with error. Message: "Partition XX unknown" (Existing message)
If the profile does not exist: Import completed with error. Message: "Profile code XX unknown" (Existing message)
If no profile entered, and if the user does not exist: Import completed with error. Message: "User ID XX unknown" (Existing mes-
sage)
If no profile entered, and if the user does not belong to at least one of the partition’s entities: Import completed with error. Mes-
sage "Entity/ies of the user XX different to the partition XX" (Existing message).
If it is a static partition import, and the user is already present in a static partition: message: "The user XX is already present in a
static partition"
If it is a dynamic partition import, and the user is already present in a dynamic partition: message:: "The user XX is already
present in a dynamic partition"

WR retrieval open webservice (export)

Send WRs to a third-party product.

n Code (text)
n Title (text)
n Status (code)
n Requester (identifier)
n Entity (name)
n Asset (code)
n Location (text)
n Date created (date/time)
n Priority (code)
n Asset off (yes/No)
n Effect (description)
n Type of work (code)
n Technology (code)
n Deadline (date/time)
n Cost allocation (code)
n WR type (code)

- 518 -
 Data imports/exports settings

n List of recipients: Identifier (user identifier)

n List of comments: Date (date/time), User (user identifier), Comment
n Completion preference list: Start date (date/time), End date (date/time), Comment (text)
n List of status changes: Date (date/time), User (user identifier), Status (description)

WR creation open webservice

Creates WRs from a third-party product.

n Code (text)
n Title (text)
n Status (code)
n Requester (identifier)
n Entity (name)
n Asset (code)
n Location (text)
n Date created (date/time)
n Priority (code)
n Asset off (yes/No)
n Effect (description)
n Type of work (code)
n Technology (code)
n Deadline (date/time)
n Cost allocation (code)
n WR type (code)

n List of recipients: Identifier (user identifier)

n List of comments: Date (date/time), User (user identifier), Comment
n Completion preference list: Start date (date/time), End date (date/time), Comment (text)

The same rules as for the WR import are applied

Export details

Code attached to the operation type

Depending on the object at the origin of the movement, the export sends the following codes:

WO: wo
Grouped WO: wg
Order: po
Inventory: iv
Manual movement: mv
Transfer: tr

Expected downtimes
Export enum code = WorkOrderDownTimeExpectedExport

- 519 -
 Data imports/exports settings

Swagger model correspondence: WorkOrderDownTimeExpectedExportModel

(Swagger model correspondence = model)

Enables export of expected downtimes that are not indicated as having already been sent. The following data are used for map-
ping and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Subcontractor category / Code (Resources block, Assigned to),
n Subcontractor code (Resources block, Assigned to/subcontractor or WF),
n Planned Currency ISO code (Resources block),
n Scheduled duration (Resources block),
n Estimated hourly cost (Resources block),
n Estimated total cost (Resources block),
n Start date (Header block, Date/time format),
n End date (Header block, Date/time format),
n Type of work/Code (Header block),
n Completed (Resources block),

Achieved downtimes
Export enum code = WorkOrderDownTimeAchievedExport
Swagger model correspondence = WorkOrderDowntimeAchievedExportModel

Enables export of actual downtimes that are not indicated as having already been sent. The following data are used for mapping
and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Subcontractor category / Code (Resources block, Assigned to),
n Subcontractor code (Resources block, Assigned to/subcontractor or WF),
n Achieved Currency ISO code (Resources block),
n Achieved duration (Resources block),
n Actual hourly cost (Resources block),
n Actual total cost (Resources block),
n Start date (Header block, Date/time format),
n End date (Header block, Date/time format),
n Type of work/Code (Header block),

Work requests
Export enum code = WorkRequestExport

- 520 -
 Data imports/exports settings

Swagger model correspondence = WorkRequestExportModel

Work requests that are not indicated as having been already sent are exported (Tag/Flag). The following data are used for map-
ping and export:

n Code (Header, Text)

n Title (Header, text),
n Status/Code (Header block),
n Status/Description (Header block),
n Requester/Login (Header block),
n Entity (Header block, Name),
n Asset/Code (Header block),
n Asset/Description (Header block),
n Location (Header block, Text),
n Creation date (Header block, Date/time format),
n Priority/Code (Header block),
n Priority/Description (Header block),
n Asset off (Header block, Yes/No),
n Effect (Header block, Text),
n Comment/Issuer (Information in the 1st comment),
n Comment/Date Time (Information of the 1st comment),
n Comment/Comment (Information of the 1st comment),
n Type of work/Code (General information block),
n Type of work/Description (General information block),
n Technology/Code (General information block),
n Technology/Description (General information block),
n Deadline date/time (General information block, Date/time format),
n Closure Date/Time
n Cost allocation/Code (General information block),
n Cost allocation/Description (General information block),
n WR type/Code (General information block),
n WR type/Description (General information block),
n WO generated (General information block, Yes/No),
n Archived (Yes/No),

The closure Date/Time corresponding to the Date/Time of the change to Closed or equivalent status appears.
If no flag is defined in the import/export form (Header block), all the work requests made in the MX application will be exported.
Conversely, if a flag is defined, only the ‘unflagged’ work requests will be exported.

Work orders
Export enum code = WorkOrderExport
Swagger model correspondence = WorkOrderExportModel

Work order that are not indicated as already having been sent are exported (Tag/Flag). The following data are used for mapping
and export:

n Code (Header block, Text),

n Title (Header block),
n Status/Code (Header block),
n Status/Description (Header block),
n Entity (Header block),
n Asset/Code (Header block, Text),
n Asset/Description (Header block, Text),

- 521 -
 Data imports/exports settings

n Type of work/Code (Header block),

n Type of work/Description (Header block),
n Priority/Code (Header block),
n Priority/Description (Header block),
n Start date (Header block, Date/time format),
n End date (Header block, Date/time format),
n Deadline (Header block, Date/time format),
n Asset off (Header block, Yes/No),
n WR Code (Header block),
n Grouped WO code,
n PW code,
n Currency (Header block),
n Comment/Issuer (Information of the last comment),
n Comment/Date Time (Information of the last comment),
n Comment/Comment (Information from the last comment, Text),
n Issuer (General information block, First name + User name),
n Creation date (General information block, Date/time format),
n Duration (General information block, Date/time format),
n Cost allocation/Code (General information block),
n Cost allocation/Description (General information block),
n Contract (General information block),
n Effect (Diagnosis block, Text),
n Cause (Diagnosis block, Text),
n Remedy (Diagnosis block, Text),
n Planned labour time (Resources block, total time),
n Actual labour time (Resources block, total time),
n Planned Subcontractor time (Resources block, total time),
n Actual Subcontractor time (Resources block, total time),
n Planned downtime (Resources block, total time),
n Actual downtime (Resources block, total time),
n Estimated labour cost (Cost block, total time),
n Actual labour cost (Cost block, total time),
n Estimated Parts cost (Cost block, total time),
n Actual Parts cost (Cost block, total time),
n Estimated Subcontractor cost (Cost block, total time),
n Actual labour cost (Cost block, total time),
n Estimated Machine shutdown cost (Cost block, total time),
n Actual Machine shutdown cost (Resources block, total time),
n Archived (Yes/No),

If no flag is defined in the import/export form (header block), all the work requests made in the MX application will be exported.
Conversely, if a flag is defined, only the ‘unflagged’ work requests will be exported.

Purchase order
Export enum code = PurchaseOrderExport
Swagger model correspondence: PurchaseOrderExportModel
(Swagger model correspondence = model)

Used to export the progress of order statuses. The following data are used for mapping and export:

- 522 -
 Data imports/exports settings

n Order/Code (Header block, Text),

n Order/Description
n Old status/Code
n Old status/Description
n New status/Code
n New status/Description
n Date/Time of status change
n User/Identifier
n User/Surname
n User/First name

We only export non-'flagged' records. Records correspond to the status change lines (StateHistory) and not orders.

Assets
Import enum code = AssetExport
Swagger model correspondence = AssetExportModel

Used to export assets. The following data is used for mapping:

n Code: (required and unique) (Text)

n Description (Text)
n Status (Description of the status)
n Location (Text)
n Parent asset (Asset code)
n Asset family (Asset family code)
n In service (yes/no)
n In-service date (Date)
n Criticality (criticality code)
n Time zone (Time zone name)
n Comment (Text)
n Brand (Brand name)
n Model (Model name)
n Serial number (Text)
n Supplier (Partner name)
n Manufacturer (Partner name)
n Manufacturer reference (Text)
n Cost allocation (code of the cost allocation).
n Under warranty (Yes/No)
n Warranty expiry date (Date)
n Normal daily operating time (Duration)
n Hourly downtime cost (Decimal)
n Purchase date (Date)
n Purchase cost (Decimal)
n Purchase cost ISO currency code
n Date of manufacture (Date)
n Maintenance work prohibited while in service (yes/no)
n Archived (Yes/No)
n Parent asset code
n Interface Key

When running the export, all the assets that have not yet been marked as sent are exported.

Assets/Additional fields

- 523 -
 Data imports/exports settings

Import enum code = AssetAdditionalFieldExport

Swagger model correspondence = AssetAdditionalFieldExportModel

Visible if the additional fields module is enabled, exports the additional fields associated with the assets:

n Asset (code of the asset)

n Additional field allocation
n Additional field description
n Value

Assets/Meters
Import enum code = AssetMeterExport
Swagger model correspondence = AssetMeterExportModel

Visible if the meter readings module is enabled, exports the meter readings associated with the assets:

n Asset (code of the asset)

n Description (Text)
n Unit (code of the unit).
n Threshold (whole number)
n Value (whole number)
n Update date (date/time)
n User (identifier of the user)

Assets/Jobs
Import enum code = AssetJobExport
Swagger model correspondence = AssetJobExportModel

Visible if the jobs module is enabled, exports the jobs associated with the assets (link between the assets and the jobs):

n Asset (code of the asset)

n Job (code of the job)

Assets/Parts
Import enum code = AssetPartExport
Swagger model correspondence = AssetPartExportModel

Visible if the stock module is enabled, exports the parts list of the assets (link between the assets and the parts):

n Asset (code of the asset)

n Part (code of the part)
n Quantity (decimal)
n Unit (code of the unit).
n Comment (Text)

Preventive works
Export enum code = PreventiveMaintenanceExport
Swagger model correspondence = PreventiveMaintenanceExportModel

Enables you to export the preventive work and analyse it from an Excel file. The following data are used for mapping and export:

- 524 -
 Data imports/exports settings

n Archive (Boolean)
n Comment
n Contract/Code
n Contrat/Title
n Criticality/Code
n Criticality/Description
n Date of next occurrence
n Trigger/Description
n Completion time limit
n Work order last generated/Code
n Recipient/Last name
n Recipient/First name
n Currency/Currency ISO code
n Issuer/ID
n Issuer/Last name
n Issuer/First name
n Entity/Name
n Asset/Code
n Asset/Description
n Cost allocation/Code
n Cost allocation/Description
n Maintenance work prohibited while in service (Boolean)
n Preventive work/Code
n Preventive work/Title
n Asset off (Boolean)
n Rolling schedule (Boolean)
n Distribution
n Technology/Code
n Technology/Description
n Type of work/Code
n Type of work/Description
n Priority/Code
n Priority/Description

For Grouped PWs containing several assets, the line is repeated as many times as there are assets.

No flag processing because PWs may be changed and therefore re-exported.

Preventive work/Triggers
(Export enum code = PreventiveMaintenanceExport)
(Swagger model correspondence = PreventiveMaintenanceExportModel)

Enables you to export the preventive work triggers and analyse them from an Excel file. The following data are used for mapping
and export:

n Preventive work/Code
n Preventive work/Title
n Meter/Description (concatenation of the asset code and meter)
n Initialisation date
n Trigger/Description
n Triggering time: field filled in if Calendar type trigger
n Triggering method: field filled in if Meter type trigger

- 525 -
 Data imports/exports settings

n Initialisation threshold: field filled in if Meter type trigger

n Triggering threshold: field filled in if Meter type trigger

No flag processing because PWs may be changed and therefore re-exported.

Part Order lines

Import enum code = PurchaseOrderPartExport
Swagger model correspondence = PurchaseOrderPartExportModel

For exporting order lines of the parts The following data is used for mapping:

n Interface key (for X3, PR line ID)

n Order code
n Blank field (for X3, enables you to add a blank field at the end of export)
n Interface key
n Order title
n Creation date
n Issuer (user ID)
n Supplier code (Supplier code)
n Supplier name (name of the supplier)
n Part code (Part code)
n Part description (Part description)
n Supplier reference
n Discount
n Discount (%)
n Discount/Currency ISO code
n Ordered quantity
n Unit (code of the unit).
n Unit price excl. tax
n Unit price excl. tax/Currency ISO code
n Unit price currency (currency ISO code)
n Discount percentage
n Warehouse (code of the warehouse)
n Storage location (code of the storage location)
n WO (code of the WO)
n Asset (code of the asset)
n Cost allocation (code of the cost allocation).
n Comments (order line comment)
n Balanced (Boolean)
n Scheduled delivery date
n VAT/Code
n VAT/Rate
n Received quantity
n Delivery slip no.
n Last delivery date
n Delivery Warehouse/Code

When running the export, all the order lines that have not yet been marked as sent are exported.

Purchase request lines

Import enum code = PurchaseRequestPartExport
Swagger model correspondence = PurchaseRequestPartExportModel

- 526 -
 Data imports/exports settings

For exporting completed Purchase request lines. The following data is used for mapping:

n Interface key (for X3, PR line ID)

n Blank field (for X3, enables you to add a blank field at the end of export)
n PR code
n PR title
n Creation date
n Requester (identifier of the user).
n Supplier (Code)
n Supplier (name of the supplier)
n Part code (Part code)
n Part description (Part description)
n Part/Unit price excl. tax
n Part/Currency ISO code
n Quantity
n Unit (code of the unit).
n Warehouse (code of the warehouse)
n Interface key

When running the export, all the PR lines that have not yet been marked as sent are exported.

Planned workforce lines

Import enum code = WorkOrderLabourExpectedExport
Swagger model correspondence = WorkOrderLabourExpectedExportModel

Used to export planned workforce lines from the application. The following data are used for mapping and import:

n Work order/Code
n Work order/Start date (Date/Time)
n Work order/End date (Date/Time)
n Work order/Title
n Technician category/Code (category code)
n Asset/Code
n Cost allocation/Code
n Technician/ID (technician ID)
n Technician/Name (technician’s name)
n Technician/First name (technician’s first name)
n Scheduled work/Currency ISO code
n Scheduled work/Cost (decimal)
n Scheduled work/Hourly cost (decimal)
n Scheduled work/Start date (Date/Time)
n Scheduled work/End date (Date/Time)
n Type of work/Code
n
n Currency (name of the currency).

Only the data defined in the mapping is exported. A file is generated after the first export is run. If the file already exists, it is
replaced each time a planned workforce lines export is run.

Actual workforce lines

Import enum code = WorkOrderLabourAchievedExport
Swagger model correspondence = WorkOrderLabourAchievedExportModel

- 527 -
 Data imports/exports settings

Used to export completed workforce lines from the application. The following data are used for mapping and import:

n Category (code of the category).

n Technician: (identifier of the technician).
n Start date (Date/time).
n End date (Date/time).
n Currency (name of the currency).
n Hourly cost (decimal).
n Cost (decimal).
n WO code
n WO start date
n WO end date
n Asset code
n Technician surname
n Technician first name
n WR title
n Cost allocation code
n Work type code

Only the data defined in the mapping is exported. A file is generated after the first export is run. If the file already exists, it is
replaced each time a completed workforce lines export is run.
Takes into account the information in all statuses (closed or not)

Movements
Import enum code = MovementExport
Swagger model correspondence = MovementExportModel

Used to export the stock movements executed in the application. The following data are used for mapping and export:

n Type
n Operation type
n Currency 
n Order/Code
n Date 
n Title
n User
n Part
n Warehouse
n Quantity
n Unit
n Unit price
n Asset
n WO
n Cost allocation
n Entry quantity
n Withdrawal quantity
n Interface key
n Blank field (x3)
n In stock (Boolean): "false" if part not listed; management status on movement date if part listed

If the exported movement is an entry movement, enter the quantity in the Entry quantity column.
If the exported movement is a withdrawal movement, enter the quantity in the Withdrawal quantity column.
Only the data defined in the mapping is exported. A file is generated after the first export is run. If the file already exists, it is
replaced each time a movement export is run.

- 528 -
 Data imports/exports settings

If no flag is set in the import/export form (header block), all the movements made in the MX application are exported. Con-
versely, if a flag is set, only the ‘unflagged’ movements are exported.

Expected parts
Export enum code = WorkOrderPartExpectedExport
Swagger model correspondence = WorkOrderPartExpectedExportModel

Enables export of resource lines of expected parts of a WO that are not indicated as having been sent (Tag/Flag). The following
data are used for mapping and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Type of work/Code (Header block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Part/Code (Resources block/Part),
n Part/Description (Resources block/Part),
n Part/Warehouse code (Resources block),
n Part/Expected date (Resources block),
n Part/Expected quantity (Resources block),
n Part/Expected Unit code (Resources block),
n Part/Expected unit price (Resources block),
n Part/Expected currency (Resources block),
n Part/Expected cost (Resources block),
n Part/Reserved (yes/no) (Resources block),
n Part/Completed (yes/no) (Resources block),
n Subcontractor category / Code (Resources block, Assigned to),
n Subcontractor code (Resources block, Assigned to/subcontractor or WF),

Achieved parts
Export enum code = WorkOrderPartAchievedExport
Swagger model correspondence = WorkOrderPartAchievedExportModel

Enables export of resource lines of completed parts that are not indicated as having been sent (Tag/Flag). The following data are
used for mapping and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Type of work/Code (Header block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Part/Code (Resources block/Part),
n Part/Description (Resources block/Part),
n Part/Warehouse code (Resources block),

- 529 -
 Data imports/exports settings

n Part/Actual date (Resources block or work report entry),

n Part/Actual unit code (Resources block or work report entry),
n Part/Actual unit price (Resources block or work report entry),
n Part/Actual currency (Resources block or work report entry),
n Part/Actual cost (Resources block or work report entry),
n Subcontractor category / Code (Resources block, Assigned to),
n Subcontractor code (Resources, Assigned to/subcontractor or WF), 

Users
Export enum code = UserExport
Swagger model correspondence = UserExportModel

 Flag not taken into account; everything is exported every time. The following data are used for mapping and export:

n Name,
n First name,
n User name,
n User Profile,
n Account type,
n Dimo Maint MX access
n Dimo Maint App access
n Main Entity,
n Date/Time of last connection,

Parts stock
Export enum code = Export
Swagger model correspondence = ExportModel

 Flag not taken into account; the Entities field on the Export form is used as a filter.
For each Parts/Warehouse link, when the part is stocked, the data used for mapping and export is:

n LPP currency ISO code

n WAUP currency ISO code
n LPP
n Storage location/Code
n Storage location/Description
n Warehouse/Code
n Warehouse/Description
n Part/Code
n Part/Description
n WAUP
n Overall WAUP
n Actual quantity:
n Ordered quantity
n Reserved quantity
n Restock point
n Maximum stock
n Minimum stock

- 530 -
 Data imports/exports settings

n Storage unit/code
n Storage unit/Description

Expected subcontractors
Export enum code = WorkOrderSubcontractorExpectedExport
Swagger model correspondence = WorkOrderSubcontractorExpectedExportModel

Enables export of expected subcontractors that are not indicated as having already been sent. The following data are used for
mapping and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Subcontractor category/Code (Resources block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Subcontractor/Code (Resources block),
n Subcontractor/Description (Resources block),
n Expected work/ISO Currency code (Resources block),
n Expected work/Subcontractor cost (Resources block),
n Expected work/Part cost (Resources block),
n Expected work/Cost (Resources block),
n Expected work/Start date (Resources block, Date/time format),
n Expected work/End date (Resources block, Date/time format),
n Expected work/Duration (Resources block, Time format),
n Work/Completed (Resources block),
n Type of work/Code (Header block),

Achieved subcontractors
Export enum code = WorkOrderSubcontractorAchievedExport
Swagger model correspondence = WorkOrderSubcontractorAchievedExportModel

Enables export of achieved subcontractors that are not indicated as having already been sent. The following data are used for
mapping and export:

n Work order/Code (Header block, Text),

n Work order/Start date (Header block),
n Work order/End date (Header block),
n Work order/Title (Header block),
n Subcontractor category/Code (Resources block),
n Asset/Code (Asset),
n Cost allocation/Code (General information block),
n Subcontractor/Code (Resources block),
n Subcontractor/Description (Resources block),
n Achieved work/ISO currency code (Resources block),
n Achieved work/Subcontractor cost (Resources block),
n Achieved work/Part cost (Resources block),
n Achieved work/Cost (Resources block),

- 531 -
 Data imports/exports settings

n Achieved work/Start date (Resources block, Date/time format),

n Achieved work/End date (Resources block, Date/time format),
n Achieved work/Duration (Resources block, Time format),
n Type of work/Code (Header block),

Data imports/exports settings

Imports of data and Webservices (SWAGGER)

Web services

Get WorkOrderConnector webservice : AssignedRessourceID added to retrieve the ID of the "Workforce"/"Subcontractor" line
assigned to the "Part"/"Machine downtime" lines

ContractImportModel webservice : ContractSubcontractorCode field, ContractCost field and CurrencyISOCode added

Filter AssetConnector webservice : Asset list retrieval

Partner Patch webservice : Update of partner information

Part Patch webservice : Update of entities of a part

Patch WorkOrder webservice : Creation of a webservice to provide information on the responses for the reading task types of
jobs for WOs

Get WorkOrder webservice : Creation of a webservice for recovering reading task types of jobs for WOs

Asset retrieval webservice : Creation of a webservice to retrieve the list of assets with the main asset attributes (getListE-
quipement(xxx))

WR creation open webservice: Creation of a WR creation webservice that can be called from outside the application

WR retrieval open webservice (export): Creation of a WR creation webservice that sends WRs to a third-party product (WorkRe-
questConnector)

Creation of a WR creation webservice that sends a list of WRs to a third-party product (WorkRequestConnector/Filter). The fields
retrieved are the same as before, and can be filtered according to the following:

n WR code,
n Title,
n Status,
n Asset/Code,
n Criticality/Code,
n Location,
n Requester,
n Creation date / Start
n Creation date / End,
n Priority/Code,
n Asset off (yes, no),
n Recipients (Firstname Surname),
n Type of work/Code
n Technology/Code

- 532 -
 Data imports/exports settings

n Deadline date/time / Start,

n Deadline date/time / End,
n Cost allocation/Code,
n WR type/Code,
n Work order,
n Entity (Name),
n Effect (Name)
n Date of last change / Start,
n Date of last change / End,
n Current page,
n Page size,
n Archive (yes/no)

Meter reading history import

Webservices error codes

The standard API REST response codes applied are as follows (list not exhaustive):

n 200 (OK)
n 400 (Bad Request)
n 401 (Unauthorized)
n 406 (Not Acceptable)
n 500 (Internal Server Error)

Modifying imports and webservices

Modification of part/warehouse import PartStockImportModel

R16 field obsolete/deleted R17:
Threshold alert - public string PartAlertValue { get; set; }
Field added (to replace the previous one):
Minimum stock - public string PartMinValue { get; set; }

Modification of part stock import StockImportModel

R16 field obsolete/deleted R17:
Threshold alert - public string PartAlertValue { get; set; }
Field added (to replace the previous one):
Minimum stock - public string PartMinValue { get; set; }

Modification of part stock import without movement StockImportWithoutMovementModel

R16 field obsolete/deleted R17:
Threshold alert - public string PartAlertValue { get; set; }
Field added (to replace the previous one):
Minimum stock - public string PartMinValue { get; set; }

Modifying the preventive work import

The following fields are added to take into account the new PW trigger method:

n Initialisation threshold
n PW trigger method in WO (Selection "Actual achievement of the value of the meter" or "Projection in time")
n PW trigger threshold

Modification of the import of the work order history

- 533 -
 Data imports/exports settings

The counter value field is added and taken into account if a PW code is entered.

Modification of the AssetImportModel asset import

Deleted field:
Manufacturer Name - public string ManufacturerName {get; set; }
Supplier Name - public string SupplierName { get; set; }
Added field:
Manufacturer Code - public string ManufacturerCode {get; set; }
Supplier Code - public string SupplierCode { get; set; }

Modification of part import: PartImportModel

Deleted field:
Partner Name - public string PartnerName { get; set; }
Added field:
Partner Code - public string PartnerCode { get; set; }

Modification of partner asset import: PartnerAssetImportModel

Deleted field:
Partner Name - public string PartnerName { get; set; }
Added field:
Partner Code - public string PartnerCode { get; set; }

Modification of partner category import: PartnerPartnerCategoryImportModel

Deleted field:
Partner Name - public string PartnerName { get; set; }
Added field:
Partner Code - public string PartnerCode { get; set; }

Modification of order import: PurchaseOrderImportModel

Deleted field:
Supplier Name - public string SupplierName { get; set; }
Added field:
Supplier Code - public string SupplierCode { get; set; }

Modification of purchase requests import: PurchaseRequestImportModel

Deleted field:
Partner Name - public string PartnerName { get; set; }
Added field:
Partner Code - public string PartnerCode { get; set; }

Modification of work order export: WorkOrderExportModel

Added field:
Partner name - public string WorkOrderGroupCode { get; set; }
Added field:
Partner Code - public string PreventiveMaintenanceCode { get; set; }

Modification of user export: UserExportModel

Deleted field:
Partner name - public string UserType { get; set; }
Added field:
Partner code - public string AccountType { get; set; }

New imports

- 534 -
 Data imports/exports settings

n Team and user timetable

n Types of time slots

Grouped operations

Principle
The grouped work module is used to schedule and carry out preventive or curative work on a series of assets.
These assets may or may not be of the same type, in the same location, etc. The tasks to carry out can involve each asset, only
part of the assets, or they can be completely different from one asset to another. Similarly, the times entered can be common to
all or separate for each asset.

Settings - Enabling a module

The grouped work module is an independent module which is
enabled in the company form:

Settings -> Configuration -> Company - Module Block: Check

Grouped work.

Enabling the module provides access to multi-asset preventive work (grouped PWs) and grouped work orders (grouped WOs)
These new functions can be subject to specific user profile rights (addition of a favourites menu on the home screen, menu res-
trictions, file viewing and access rights, etc.). “Requester” account types do not have access to grouped WOs or PWs.

See the Company form and Profile form for more details.

Asset Groups

These can be configured via the Assets - Asset groups menu.

Assets can be grouped together according to different criteria: their location, family, brand, model or serial number.
Each asset’s cost distribution is defined at group level
Once defined, one or more of these groups can be selected in the preventive works schedule or the grouped work orders.

See the section Asset groups.

Grouped preventive work

Grouped preventive work (grouped PW) is scheduled work on a number of assets.

Simply add all the assets affected by the work in the Assets block of a PW form. The following selection criteria are especially use-
ful when making collective additions: Location, asset family, brand, model and serial number.
Cost distribution is defined individually for each asset or collectively if the distribution is the same for several assets. If a group is
selected, the asset distribution is retrieved from the group.

- 535 -
 Data imports/exports settings

Jobs can also be assigned collectively to all the PW assets and all the resources linked to the jobs in question are added to the
grouped work.

When a grouped PW is converted, a grouped work order is generated.

Refer to the section PW form to find out more about creating a grouped PW.

Grouped work orders

A grouped work order (grouped WO) is comprised of a series of work orders on different assets. Grouped orders are comprised
of sub-orders by asset. These sub-orders are called child WOs.

Grouped WOs either originate from the conversion of grouped work or can be created manually using the Work - Grouped work
orders menu.

Assets can be added to the grouped WO in the Work orders block. Selection criteria can be used to quickly add a large number of
assets based on filters: location, asset family, brand, model and serial number.

When the grouped WO is saved, child work orders are generated for each asset added.

To facilitate data entry, certain actions can be performed collectively on all the child WOs at the same time:
- Asset distribution
- Job association
- Status change
- Task responses

The resources entered can either be the same on the grouped WO or different on each child WO.

See the Grouped work orders section for more information.

Including the grouped WOs in the list of WOs

A button for accessing the grouped WO is displayed at the end of each child WO line in the list of work orders.

Taking the grouped WOs into account in the asset form

A button for accessing the grouped WO is displayed at the end of each child WO line in the asset form Work Orders block.

Taking the grouped WOs into account in the list of WO alerts

Late grouped WOs can trigger alert-notifications. Child WOs are not involved in triggering the alerts.

Refer to the section Alerts-Notifications.

Taking the grouped WOs into account in the schedule

The workforce resources originating from the grouped WOs are displayed in the technician schedule.

- 536 -
 Data imports/exports settings

How these resources are displayed depends on the same rules as their equivalents originating from a standard WO (Colour,
moves, resizing, etc.)

The grouped WO linked to each child WO can be viewed by right-clicking on the child WO in question and choosing open grou-
ped WO from the context menu in the asset schedule.

The report entry window is designed for easy task response and meter reading of all the assets in the grouped WO.

Taking the grouped WOs into account in the home screen Widgets
The grouped WOs are taken into account in the following widgets:

n The WO info widget

n The My schedule widget
n Unassigned work widget

Refer to the section Home Screen-Widgets.

Taking the grouped WOs into account in the analyses

Grouped work is taken into account in the following analyses:

n Assets pareto
n Pareto by family
n Pareto by type of work
n Pareto by technology
n Work history
n Maintenance indicators
n Summary by technician
n Summary by technician category
n Summary by subcontractor category

Refer to the details of each Analysis for more information.

Managing how emails are sent with grouped WOs

The same rules are used as for single WOs, except for a few behaviour changes in terms of the grouped WOs and child WOs:

n Adding or modifying a technician line: Behaviour exactly the same as a single WO in a grouped WO or child WO
n Adding or modifying an SC line: Behaviour exactly the same as a single WO in a grouped WO or child WO
n Resource line term or response to a task in the order: Behaviour exactly the same as a single WO in a grouped WO or
child WO
n Term for all the resource lines and response to all the tasks: Email sending is not triggered on child WOs, only when all
the resource lines of the grouped WO and its children are completed and when all the child WO tasks have responses.
n Closing an order: Email sending is not triggered on child WOs, only when all the child WOs and group WO have been
closed.
n Cancellation of an order: Email sending is not triggered on child WOs, only when all the child WOs and group WO have
been cancelled.

Configuring the grouped WO screen and print settings

- 537 -
 Data imports/exports settings

How the grouped WO form is displayed (block and fields displayed, required entries, etc.) can be configured by user profile.
Select the grouped WO form under Screen settings in the profile.
Similarly, certain additional printing options can be configured (Configuration of PDF printing button): Display company logo, Dis-
play address block, Display manager’s signature, Display technician’s signature, Display customer’s signature, Display barcode
(Code 39), Print child WOs.

Refer to the section Configuration of PDF screens and printing.

- 538 -
Multi-organisation
Principle

The Multi-organisations or multi-entities module enables several entities to be managed within the same application. These enti-
ties can be sites, subsidiaries or departments that have different data, parameter settings and flows.
The application enables partitioning of data and parameter settings by organisation and makes it easy to share common data.

The entities can be administered independently while keeping an overall view of all the activities.
Each user is linked to one or more entities. Profile configuration then enables us to define the rights relating to each profile for
each entity.
Certain settings and configurations are specific to each entity and can be defined in the entity form Association block (admi-
nistration of WO and WR statuses, emails and general settings).

See an explanatory diagram of links between entities, profiles and users.

Terms and definitions

n Entity: An entity is a part of a company. (Subsidiary, department, site, etc.)

n Shared data: shared data is data common to several entities. They can be made available to all the entities of a com-
pany, and each entity can decide whether to use them.

n Unshared data: unshared data is data specific to a single entity, and is visible to and usable by this entity only.

n Association: the term association is used to define all the items (users, assets, parts, repository, etc.) linked with one or
more entities.

Activation - Deactivation
The multi-organisation module is activated automatically with the licence key when the number of entities is greater than 1.

In order to switch from multi-entity to single-entity mode, there must only be one active entity. The other entities must be dele-
ted or archived before updating. All the users are then attached to the remaining entity.

Access to the entities

The list of entities can be accessed by clicking on the button on the company form.[Settings-Con-
figuration-Company] or [Settings-Configuration-Entity].

- 539 -
The entities can also be accessed from the Entity block user form, button

Access to the different entities depends on the rights of the user on the entity concerned.

New entities
An entity can be created:

n with the button on the list of entities.

n by clicking on the button on the entity form.

Enter the entity identification information.

When a new entity is saved, the number of entities in the licence key is checked.
If the number of active entities has been reached already, the new entity is not saved and an error message is displayed. Entities
must be archived, or additional accesses must be purchased, in order to save the entity.

Each entity must have at least a supervisor, a user manager and a profiles manager.
When a user creates an entity, he is automatically attached to this entity.
To attach other users to the entity, one must manually link them in their users' form.

See also the entity form and the list of entities for more details on the different actions possible. (entity duplication, entity dele-
tion, entity archiving and de-archiving, etc.)

Entity configuration - Associations block

Some settings can be configured by entity. These settings can be found in the Entity-Association block form.

- 540 -
Duplicating the configuration

Some configurations can be copied to other entities with the button available in the following
forms:

l General settings
l WR status administration
l WO status administration
l Administration of the PR statuses
l Order status administration
l E-mail sending administration
l User

The user selects the configuration sections to be duplicated: Automatic changes, actions by status... then the entities for which
he wishes to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

This action is can also be performed from the default configurations [Settings-Configuration]. It enables one to initialise target
entities with the default configurations for selected sections.

E-mail sending administration

The settings for E-mail sending by action can be defined per entity.

- 541 -
When creating a new entity, these settings are initialised with those configured in the application Settings. [Settings-Con-
figuration-Email administration]. Refer to this section for further details.

WR, PR WO and order status administration

Changes to the automatic statuses of the different documents (PR, WR, WO, orders, etc.) can be configured by entity.
- In automatic change blocks: reference statuses and equivalent statuses (not archived) are displayed in the lists according to the
entity
- In Actions by status blocks, all the reference and equivalent statuses, including archived statuses, are displayed.
Rights to change or convert a document depending on its status may also be defined.
When creating a new entity, these settings are initialised with those configured in the application Settings. [Settings-Con-
figuration-Status administration of...]. Refer to this section for further details.

For duplication of the configuration of automatic changes to WO, WR, PR and order statuses:

o Duplication of the configuration of statuses from a source using reference statuses:

If the reference status exists for the target entity, then it is used.
Otherwise, if an equivalent status exists for the target entity for the reference status in question, it is retrieved.
If no equivalent status can be retrieved, the action is disabled and no status is selected

o Duplication of the configuration of statuses from a source using equivalent statuses:

If the status selected in the source entity configuration is also associated with the target entity, the configuration is duplicated.
Otherwise, the action is disabled for the target entity and no value is selected.

For duplication of action configuration by WR and PR status:

Duplication of actions by status only takes into account statuses associated with the source configuration and the target confi-
guration

WR recipient administration
This screen is used to configure different recipients for each entity, based on the type of WR selected in the work request.
When linking a WR type with an entity, it appears in the entity's WR recipient administration.
The recipients linked with it by default in the WR recipient administration and who are also linked with the entity are then auto-
matically linked with it in the entity’s WR recipient administration.

When separating an entity from a WR type, it no longer appears in the entity's WR recipient administration.
The links between the recipients and the WR type for the entity are deleted.

General settings
The following settings can be configured for each entity:

n Main warehouse: retrieved automatically in the various forms (part, movement, etc.)
n Default recipient of the PRs
n PW trigger time limit
n Meters PW into WO trigger method
n Meters PW into WO trigger threshold
n Days of the week without PW trigger
n Statuses of assets without PW trigger

- 542 -
When creating a new entity, these settings are initialised with those configured in the General settings of the application.[Set-
tings-Configuration-General-General settings]
Refer to this section for further details.

Users
This brick is used to directly link users to or separate users from each entity.
The pop-up displays two lists:

n The first displays all non-archived users who are not linked to the entity and allows them to be linked
n The second displays all non-archived users who are already linked to the entity and allows them to be separated

User settings - Entities block

A user can work on one or more entities. Users are linked with the various entities in the User-Entities block form. This block is
visible only if multi-organisation mode is activated and for the supervisors who are user managers.

Click on the button to attach the user to one or more entities and on the button to unlink the user
from the entity.
- The supervisor can add only the entities with which he or she is linked.
- The supervisor cannot delete an entity with which he or she is not linked.
- The supervisor cannot delete an entity for which the user of the form is the last linked supervisor.

A user who has at least one associated entity necessarily has a main entity. The main entity of a user is retrieved by default in the
various forms (WO, WR, PW, etc.).
- The first entity added is defined as the main entity.
- A user can have only one main entity.
- If the main entity of a user also linked with other entities is deleted, the system defines another main entity automatically.

Each entity must have at least a supervisor, a user manager and a profiles manager.

The user’s rights in each entity can also be defined according to their profile. A user may have creation rights on some entities
and viewing-only rights on other entities. Refer to the section below [User profile settings by entity/Rights].

- 543 -
Configuration of user profiles on the entities - Settings by entity block

Default entity configuration

The button is visible only if the multi-organisation module is enabled. It initialises profiles
with these settings when a new entity is created.
--> for all profiles (depending on the type of account), the configurations of roles, notifications, categories, contract types, codi-
fications and rights are automatically filled in for the new entity from the default data.

Duplicating an entity's configuration

The button is visible only if the multi-organisation module is enabled. It enables

one to copy part or all of the configurations from one entity to other profile entities.

- 544 -
The user selects the original entity from which the configuration must be duplicated.
It then determines the configuration sections to be duplicated: Roles, codifications, rights etc. then the entities to which he
wishes to apply these new configurations.

This editing overwrites the settings of the sections selected in the same sections of the target entities.

Roles by entity
The settings of the user profile roles can be defined and can be different for each entity (WO closing, Requester, Technician,
etc.).

Notifications by entity
Notifications or alerts can be configured by entity (WR, WO, Stock, contracts alerts, etc.)

Categories by entity
The settings of the user profile categories can be defined and can be different for each entity. The technician can belong to one
category for an entity and to another category for another entity.

Type of contract by entity

A user profile can manage different types of contract according to the entity. (if the Contracts module is enabled)
This block is only visible for "Supervisor" types of account.

Codification by entity
Automatic codification can also be configured by profile and by entity. This means that, for a given profile, the codification can
differ according to the entity to which it is applied.

Rights by entity
The rights on the entities can be defined by user profile.
Depending on each entity, the user profile has viewing, modification, association, archiving or deletion rights on the items of the
application. (Repository, assets, parts, etc.)
The association rights are specific to multi-entity mode. They enable or do not enable the association of items with entities.

The rights on the entities are not applicable for currencies or units, for which the rights on the shared data in the general repo-
sitory are taken into account.

- 545 -
For further information on the configuration of roles, codification, categories and rights, refer to the Set-
tings-Users-User profiles-Configuration by entity block] section

User profile configuration for shared data - Shared data right block

In multi-entity mode, the data may be:

l Unshared, specific to a single entity,

l Shared, common to several entities. They are made available to all the entities of a company, and each entity can
decide whether to use them.

The actions that can be performed (addition, modification, deletion) on shared data depend on the rights defined on the shared
data on this screen as well as on the rights on entities on which they are effectively shared.

The rights on the shared data are determined by profile for the following items:

n Budget
n Asset
n Diagnosis (Effect + Cause + Remedy)
n Job (Job + Task)
n Part
n Preventive work (the right only applies to triggers and not to PWs that cannot be shared)
n Inventory
n Partner
n Contract
n General repository: Settings-General
n Maintenance repository: Settings-Assets and Settings-Work
n Stock repository: Settings-Stock
n Model repository: Settings - Multi-entity work models

The rights levels can be different according to the account type selected in the header. (See User profiles-Header Block)
Requesters have no rights over shared data
Guests:
- Document reading rights
- No rights for repositories
Users:
- Document reading rights
- No rights for repositories
Supervisors have all rights to shared data.

- 546 -
 n Deletion: highest right level. Enables deletion, archiving, creation, modification and viewing.
n Archiving: enables archiving, creation, modification and viewing. Deletion is not enabled.
n Editing: enables item viewing, modification and creation.
n Viewing: enables only viewing of an item.
n None: lowest right level. No rights granted on the item.

Rights over WR, WO, PW and PR items are final documents that can only be associated with only one entity, therefore not sha-
red, and rights are defined only by entity (User profiles-Configuration by entity-Rights)

Creation of shared data - Data sharing

To share data, a user must have editing rights on the shared data.

Data can be shared:

l individually : in the item form by ticking the box then by associating the entities on which the data

is shared

l in bulk : from the list with multiple selection using the button then by associating the entities via the

button .

For items in a tree: it is not possible to share a child item if the parent is not shared.

Creation of unshared data

To create unshared data:

l Do not check the box

l Associate the entity with the data.

The created data is visible only by the profiles linked with the entity. (Subject to rights over the entity)

Data (shared or unshared) association with and dissociation from an entity

When an item can be associated with an entity, the Entity field displays the list of non-archived entities.

l If the data is shared:

l the entity is not required

l several entities can be selected and are subsequently modifiable

l the user can associate or dissociate only the entities for which he or she has at least the Association right on

the object

- 547 -
 l It is impossible to unlink an entity for which there is an item used in an open document (not closed or not can-
celled), except for assets: If all the existing work orders and work requests for the asset have been closed or
cancelled, it is possible to unlink the entity from the asset.
l Bulk association can be performed from the lists by selecting several shared items and clicking on the button

, which opens the window to associate with different entities.

If the parent item is not associated with one of the entities selected, then it is automatically associated with this entity

l If the data are unshared:

l the entity is required

l only one entity can be selected and it is no longer modifiable

l a user who adds an item can associate only with an entity for which he or she has at least the Editing right on

the object

The actions that can be performed depend on the rights of the user profile on the entities and on the shared data (refer to Pro-
file/Rights on the entities and rights on the shared data).

Special cases of items in trees (assets, parts families, cost allocations, asset families):

n - an entity cannot be associated with a child item if it is not also linked with the parent. (except in the specific case
where an asset is moved)

Entity-related rules applicable to the documents

The following rules are applicable in multi-entity mode:

- 548 -
Work request
l The WR can be associated with only one entity; the association is required.
l The drop-down list of Entities contains only non-archived entities for which the user has at least the Editing right on
the work requests.
l The entity of the WR is no longer modifiable if the WR has already been converted to a WO.
l When a WR form is opened, the rights and roles are applied according to the entity of the WR (default entity or selec-
ted entity).
l The items are filtered according to the entity (assets, WR types, jobs, priorities, etc.).

Work order
l The WO can be associated with only one entity; the association is required.
l The drop-down list of Entities contains only non-archived entities for which the user has at least the Editing right on
the work orders.
l The entity of the WO is modifiable during creation. Once the WO is saved, the entity is no longer modifiable.
l When a WO form is opened, the rights and roles are applied according to the entity of the WO (default entity or selec-
ted entity).
l The items are filtered according to the entity (assets, work types, parts, jobs, etc.).

Preventive work
l The PW can be associated with only one entity; the association is required.
l The drop-down list of Entities contains only non-archived entities for which the user has at least the Editing right on
the preventive works.
l The entity of the PW is modifiable.
l When a PW form is opened, the rights and roles are applied according to the entity of the PW (default entity or selec-
ted entity).
l The items are filtered according to the entity (triggers, assets, work types, jobs, etc.).

Moving an asset or changing entity

Possibility of modifying the entity of an unshared asset or moving an asset under another asset in a different entity.

Moving an unshared asset:

If the destination asset is an unshared asset, the move is made under the new asset -> the entity of the asset that has been
moved is modified
If the destination asset is a shared asset that does not have the original asset entity, the user chooses the entity from among the
list of entities of the destination asset.

Moving a shared asset:

If the destination asset is not shared, the move is not authorised,
If the destination asset is shared and linked to all the entities of the asset that has been moved -> the entity of the asset that has
been moved is modified,
If the destination asset is not linked to all the entities of the asset that has been moved and it does not have the rights to link the
missing entities -> the move is forbidden.

- 549 -
Actions performed during a move:
n The asset entity is modified
n The entity of all the asset PWs is modified with its new entity
n Then new asset entity is added to the entities of all its contracts
n Contracts that were not shared and that are on more than one entity are automatically shared
n All these actions are applied to all the children of the asset that has been moved

These actions do not taken into account the rights of the user making the move.

Moving an asset that belongs to an asset group

When an asset in the tree is moved and it generates an entity change, if that asset is part of one or more groups, then:

n If the group has no common entity with the moved asset, the new entity is added to the group.
n If the group was not shared beforehand, it is now shared (rights are ignored)

Moving an asset that is part of a grouped work item

If the asset appears in multi-asset PWs, a message is displayed when the asset is moved, prompting the user to remove the asset
from those PWs. If the user confirms the movement, the asset is deleted from the PW.

In the case of PWs that are not on this asset, the PW automatically replaces the entity with the new asset entity

- 550 -