forked from buildingSMART/IFC4.3.x-output
-
Notifications
You must be signed in to change notification settings - Fork 0
/
IfcProcessExtension.pot
642 lines (461 loc) · 34.1 KB
/
IfcProcessExtension.pot
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
# Industry Foundation Classes IFC.
# Copyright (C) 2020 buildingSMART
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2020-09-25 10:09+0200\n"
"X-Crowdin-SourceKey: msgstr\n"
"Language-Team: buildingSMART community\n"
#:IFC.xml:26824
msgid "IfcEvent"
msgstr "IfcEvent"
msgid "IfcEvent_DEFINITION"
msgstr "An [[IfcEvent]] is something that happens that triggers an action or response. HISTORY New entity in IFC4 .use head Use definitions [[IfcEvent]] is used to capture information about particular things that happen or that may happen. Particularly used in work plans or process maps they identify e.g. a point at which a message containing information may be issued or at which a rule or constraint is invoked. bSI Documentation"
#:IFC.xml:3595
msgid "IfcEvent_EventOccurenceTime"
msgstr "EventOccurenceTime"
msgid "IfcEvent_EventOccurenceTime_DEFINITION"
msgstr "EventOccurenceTime"
#:IFC.xml:26845
msgid "IfcEvent_PredefinedType"
msgstr "PredefinedType"
msgid "IfcEvent_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:26833
msgid "IfcEvent_EventTriggerType"
msgstr "EventTriggerType"
msgid "IfcEvent_EventTriggerType_DEFINITION"
msgstr "Identifies the predefined types of event trigger from which X 0D the type required may be set."
#:IFC.xml:26838
msgid "IfcEvent_UserDefinedEventTriggerType"
msgstr "UserDefinedEventTriggerType"
msgid "IfcEvent_UserDefinedEventTriggerType_DEFINITION"
msgstr "A user defined event trigger type, the value of which is X 0D asserted when the value of an event trigger type is declared X 0D as USERDEFINED."
#:IFC.xml:26857
msgid "IfcEventTriggerTypeEnum"
msgstr "IfcEventTriggerTypeEnum"
msgid "IfcEventTriggerTypeEnum_DEFINITION"
msgstr "The [[IfcEventTriggerTypeEnum]] defines the range of different types of event trigger that can be specified. The definition of event trigger types has been adopted from the Business Process Modeling Notation BPMN , which is also used in the Information Delivery Manual IDM for defining business processes. More detailed information about the use of event trigger types can be found in these specifications. HISTORY New type in IFC4 bSI Documentation"
#:IFC.xml:26865
msgid "IfcEventType"
msgstr "IfcEventType"
msgid "IfcEventType_DEFINITION"
msgstr "An [[IfcEventType]] defines a particular type of event that may be specified. HISTORY New entity in IFC4 An [[IfcEventType]] provides for all forms of types of event that may be specified. Usage of [[IfcEventType]] defines the parameters for one or more occurrences of [[IfcEvent]] . Parameters may be specified through property sets that may be enumerated in the [[IfcEventTypeEnum]] data type or through explicit attributes of [[IfcEvent]] . Event occurrences [[IfcEvent]] entities are linked to the event type through the [[IfcRelDefinesByType]] relationship. bSI Documentation"
#:IFC.xml:26886
msgid "IfcEventType_PredefinedType"
msgstr "PredefinedType"
msgid "IfcEventType_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:26874
msgid "IfcEventType_EventTriggerType"
msgstr "EventTriggerType"
msgid "IfcEventType_EventTriggerType_DEFINITION"
msgstr "Identifies the predefined types of event trigger from which X 0D the type required may be set."
#:IFC.xml:26879
msgid "IfcEventType_UserDefinedEventTriggerType"
msgstr "UserDefinedEventTriggerType"
msgid "IfcEventType_UserDefinedEventTriggerType_DEFINITION"
msgstr "A user defined event trigger type, the value of which X 0D is asserted when the value of an event trigger type is X 0D declared as USERDEFINED."
#:IFC.xml:26898
msgid "IfcEventTypeEnum"
msgstr "IfcEventTypeEnum"
msgid "IfcEventTypeEnum_DEFINITION"
msgstr "The [[IfcEventTypeEnum]] defines the range of different types of event that can be specified. HISTORY New type in IFC4 bSI Documentation"
#:IFC.xml:26904
msgid "IfcEventTypeEnum_STARTEVENT"
msgstr "STARTEVENT"
msgid "IfcEventTypeEnum_STARTEVENT_DEFINITION"
msgstr "An initiating event of a process."
#:IFC.xml:26902
msgid "IfcEventTypeEnum_ENDEVENT"
msgstr "ENDEVENT"
msgid "IfcEventTypeEnum_ENDEVENT_DEFINITION"
msgstr "A terminating event of a process."
#:IFC.xml:26903
msgid "IfcEventTypeEnum_INTERMEDIATEEVENT"
msgstr "INTERMEDIATEEVENT"
msgid "IfcEventTypeEnum_INTERMEDIATEEVENT_DEFINITION"
msgstr "An event that occurs at an intermediate stage of a process."
#:IFC.xml:26905
msgid "IfcProcedure"
msgstr "IfcProcedure"
msgid "IfcProcedure_DEFINITION"
msgstr "An [[IfcProcedure]] is a logical set of actions to be taken in response to an event or to cause an event to occur. HISTORY New entity in IFC2x2 .change ifc2x4 IFC4 CHANGE ProcedureType renamed to PredefinedType and made optional upward compatible . Where rules WR1 and WR2 have been removed. .use head Use definitions [[IfcProcedure]] is used to capture information about stepped processes such as calibration, start stop procedures for equipment items, designated actions to take in the event of an emergency etc. A procedure is not a task, but may describe a set of tasks and their order of occurrence in response to or to cause an event. As shown in Figure 11, [[IfcProcedure]] does not restrict anything but describes specific steps of how something should happen. While a procedure does control restrict in the sense of indicating this is how the task should be performed by nature of describing inner detail, this is not different than parts of a product indicating this is how the parts should be assembled . Consequently, it doesn t restrict the outer item as a whole but provides inner detail of the item. procedure example .. .. .. .. .. .. figures ifcprocedure example.png Figure 1 Procedure relationships bSI Documentation"
#:IFC.xml:26916
msgid "IfcProcedure_PredefinedType"
msgstr "PredefinedType"
msgid "IfcProcedure_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:26928
msgid "IfcProcedureType"
msgstr "IfcProcedureType"
msgid "IfcProcedureType_DEFINITION"
msgstr "An [[IfcProcedureType]] defines a particular type of procedure that may be specified. HISTORY New entity in IFC4 An [[IfcProcedureType]] provides for all forms of types of procedure that may be specified. Usage of [[IfcProcedureType]] defines the parameters for one or more occurrences of [[IfcProcedure]] . Parameters may be specified through property sets that may be enumerated in the [[IfcProcedureTypeEnum]] data type or through explict attributes of [[IfcProcedure]] . Procedure occurrences [[IfcProcedure]] entities are linked to the procedure type through the [[IfcRelDefinesByType]] relationship. bSI Documentation"
#:IFC.xml:26935
msgid "IfcProcedureType_PredefinedType"
msgstr "PredefinedType"
msgid "IfcProcedureType_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:26947
msgid "IfcProcedureTypeEnum"
msgstr "IfcProcedureTypeEnum"
msgid "IfcProcedureTypeEnum_DEFINITION"
msgstr "The [[IfcProcedureTypeEnum]] defines the range of different types of procedure that can be specified. HISTORY New type in IFC2x2 bSI Documentation"
#:IFC.xml:26956
msgid "IfcProcedureTypeEnum_ADVICE_NOTE"
msgstr "ADVICE NOTE"
msgid "IfcProcedureTypeEnum_ADVICE_NOTE_DEFINITION"
msgstr "Additional information or advice that should be taken note of as a procedure or when carrying out a procedure."
#:IFC.xml:26955
msgid "IfcProcedureTypeEnum_ADVICE_CAUTION"
msgstr "ADVICE CAUTION"
msgid "IfcProcedureTypeEnum_ADVICE_CAUTION_DEFINITION"
msgstr "A caution that should be taken note of as a procedure or when carrying out a procedure."
#:IFC.xml:26957
msgid "IfcProcedureTypeEnum_ADVICE_WARNING"
msgstr "ADVICE WARNING"
msgid "IfcProcedureTypeEnum_ADVICE_WARNING_DEFINITION"
msgstr "A warning of potential danger that should be taken note of as a procedure or when carrying out a procedure."
#:IFC.xml:26959
msgid "IfcProcedureTypeEnum_DIAGNOSTIC"
msgstr "DIAGNOSTIC"
msgid "IfcProcedureTypeEnum_DIAGNOSTIC_DEFINITION"
msgstr ""
#:IFC.xml:26958
msgid "IfcProcedureTypeEnum_CALIBRATION"
msgstr "CALIBRATION"
msgid "IfcProcedureTypeEnum_CALIBRATION_DEFINITION"
msgstr "A procedure undertaken to calibrate an artifact."
#:IFC.xml:26960
msgid "IfcProcedureTypeEnum_SHUTDOWN"
msgstr "SHUTDOWN"
msgid "IfcProcedureTypeEnum_SHUTDOWN_DEFINITION"
msgstr "A procedure undertaken to shutdown the operation an artifact."
#:IFC.xml:26961
msgid "IfcProcedureTypeEnum_STARTUP"
msgstr "STARTUP"
msgid "IfcProcedureTypeEnum_STARTUP_DEFINITION"
msgstr "A procedure undertaken to start up the operation an artifact."
#:IFC.xml:26962
msgid "IfcRelSequence"
msgstr "IfcRelSequence"
msgid "IfcRelSequence_DEFINITION"
msgstr "[[IfcRelSequence]] is a sequential relationship between processes where one process must occur before the other in time and where the timing of the relationship may be described as a type of sequence. The relating process [[IfcRelSequence]].RelatingProcess is considered to be the predecessor in the relationship has precedence whilst the related process [[IfcRelSequence]].RelatedProcess is the successor. [[IfcRelSequence]] is defined as one to one relationship therefore it assigns one predecessor to one successor. HISTORY New entity in IFC1.0. .change ifc2x4 IFC4 CHANGE Relocated to IfcProcessExtension schema. TimeLag and SequenceType made optional. USERDEFINED added to the IfcSequenceType enumeration. UserDefinedSequenceType attribute added. WHERE rule controlling use of the USERDEFINED enumeration added. .use head Use definitions [[IfcRelSequence]] is used to describe the logical sequence relationship that exists between two processes. This logical relationship identifies that there is a predecessor or relating process and a successor or related process. In IFC, there may be one predecessor and one successor in the relationship. Many occurrences of [[IfcRelSequence]] may exist to describe the sequence relationships of a predecessor task with many successor tasks or of many predecessor tasks with one successor task, thus enabling a m n sequence relationship between tasks. Please note that sequence relationships can be used to define dependencies between process occurrences but also between process types for further information see [[IfcRelDefinesByObject]] and [[IfcTaskType]] . In case of defining dependencies between process occurrences sequence relationships should stay within the limits of a directed, non cyclic graph. A sequence type may be set for a sequence. For tasks assigned to a work schedule, it is expected that the sequence type will be asserted. For a process map, where the sequence relationship between processes is simply a logical flow, it need not be asserted. A time lag may be assigned to a sequence, and the sequence type defines the way in which the time lag applies to the sequence either as a ratio or percentage of time duration e.g. start successor task when predecessor is 50 complete or as a time measure e.g. start successor task 1 week after commencement of the predecessor task . Care should be used when assigning a time lag to a sequence depending on the setting of the sequence type since there is no checking that the time lag value is in keeping with the sequence type set. bSI Documentation"
#:IFC.xml:3647
msgid "IfcRelSequence_TimeLag"
msgstr "TimeLag"
msgid "IfcRelSequence_TimeLag_DEFINITION"
msgstr "TimeLag"
#:IFC.xml:20469
msgid "IfcRelSequence_RelatedProcess"
msgstr "RelatedProcess"
msgid "IfcRelSequence_RelatedProcess_DEFINITION"
msgstr "RelatedProcess"
#:IFC.xml:20495
msgid "IfcRelSequence_RelatingProcess"
msgstr "RelatingProcess"
msgid "IfcRelSequence_RelatingProcess_DEFINITION"
msgstr "RelatingProcess"
#:IFC.xml:26971
msgid "IfcRelSequence_SequenceType"
msgstr "SequenceType"
msgid "IfcRelSequence_SequenceType_DEFINITION"
msgstr "The way in which the time lag applies to the sequence."
#:IFC.xml:26976
msgid "IfcRelSequence_UserDefinedSequenceType"
msgstr "UserDefinedSequenceType"
msgid "IfcRelSequence_UserDefinedSequenceType_DEFINITION"
msgstr "Allows for specification of user defined type of the sequence X 0D beyond the enumeration values START START, START FINISH, X 0D FINISH START, FINISH FINISH provided by SequenceType X 0D attribute of type [[IfcSequenceEnum]] . When a value is X 0D provided for attribute UserDefinedSequenceType in X 0D parallel the attribute SequenceType shall have X 0D enumeration value USERDEFINED. X 0D X 0D .change ifc2x4 X 0D IFC4 CHANGE Attribute added"
#:IFC.xml:26983
msgid "IfcSequenceEnum"
msgstr "IfcSequenceEnum"
msgid "IfcSequenceEnum_DEFINITION"
msgstr "[[IfcSequenceEnum]] is an enumeration that defines the different ways in which a time lag is applied to a sequence between two processes. HISTORY New entity in IFC1.0 bSI Documentation"
#:IFC.xml:26991
msgid "IfcTask"
msgstr "IfcTask"
msgid "IfcTask_DEFINITION"
msgstr "An [[IfcTask]] is an identifiable unit of work to be carried out in a construction project. A task is typically used to describe an activity for the construction or installation of products, but is not limited to these types. For example it might be used to describe design processes, move operations and other design, construction and operation related activities as well. Quantities of resources consumed by the task are dealt with by defining the [[IfcElementQuantity]] for the resource and not at the instance of [[IfcTask]] . HISTORY New entity in IFC1.0. Renamed from IfcWorkTask in IFC2x. .change ifc2x4 IFC4 CHANGE Attributes TaskTime and PredefinedType added. IfcMove and IfcOrderRequest has been removed in IFC4 and are now represented by [[IfcTask]] . IfcRelAssignsTasks relationship has been removed as well. .use head Attribute use definition Each occurrence of [[IfcTask]] is given a name that is indicative of its content [[IfcRoot]].Name . A textual description of the task may be provided and this may be further elaborated by a narrative long description [[IfcProcess]].LongDescription . A work method may be declared for the method of work used in carrying out a task. A task is identified as being either a milestone task or not. A milestone task is defined by the marker IsMilestone . and has no duration. A status and priority for each task may also be set. .use head Time and duration use definition Compared to previous IFC releases, basic task time information scheduled start time, scheduled finish time, duration is now directly attached to [[IfcTask]] through the TaskTime attribute. Regular tasks are defined through [[IfcTaskTime]] . Recurring tasks are defined through [[IfcTaskTimeRecurring]] . In case a regular task is derived from a recurring task both tasks should be linked together through a [[IfcRelNests]] relationship, where [[IfcRelNests]].IsNestedBy points to the recurring task and [[IfcRelNests]].Nests points to all regular tasks that have been derived from the recurring task. .use head Representation of other activities The use definitions for [[IfcTask]] have been generalised to represent other activities as well, including activities that had been defined by own entities in previous IFC releases. This includes Order actions Move operations [[IfcTask]] represents an order that might be carried out by a Helpdesk acting the role of interface for the organization between the facility user and the functional requirement of fulfilling their needs. The actual task represented by the [[IfcTask]] entity is turning a request into an order and initiating the action that will enable the order to be completed. The [[IfcProjectOrder]] or one of its subtypes including maintenance work order, is related to the [[IfcTask]] using [[IfcRelAssignsToControl]] . [[IfcTask]] can also be used to describe an activity that moves people, groups within an organization or complete organizations together with their associated furniture and equipment from one place to another. It thus replaces the previous IFC entity IfcMove. The functionality is represented in [[IfcTask]] as follows Move from The place from which actors and their associated equipment are moving. Use [[IfcRelAssignsToProcess]] where RelatingProcess points to the task and RelatedObjects holds the location s from which to move. Move to The place to which actors and their associated equipment are moving. Use [[IfcRelAssignsToProduct]] where RelatedObjects points to the task s and RelatingProduct points to the location to which to move. Punch list A list of points concerning a move that require attention. Use LongDescription or else identify sub tasks to track punch list items individually via [[IfcRelNests]] . bSI Documentation"
#:IFC.xml:3950
msgid "IfcTask_TaskTime"
msgstr "TaskTime"
msgid "IfcTask_TaskTime_DEFINITION"
msgstr "TaskTime"
#:IFC.xml:27022
msgid "IfcTask_PredefinedType"
msgstr "PredefinedType"
msgid "IfcTask_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27000
msgid "IfcTask_Status"
msgstr "Status"
msgid "IfcTask_Status_DEFINITION"
msgstr "Current status of the task. X 0D X 0D NOTE Particular values for status are not specified, these should be determined and agreed by local usage. Examples of possible status values include Not Yet Started , Started , Completed ."
#:IFC.xml:27005
msgid "IfcTask_WorkMethod"
msgstr "WorkMethod"
msgid "IfcTask_WorkMethod_DEFINITION"
msgstr "The method of work used in carrying out a task. X 0D X 0D NOTE This attribute should not be used if the work method is specified for the [[IfcTaskType]]"
#:IFC.xml:27010
msgid "IfcTask_IsMilestone"
msgstr "IsMilestone"
msgid "IfcTask_IsMilestone_DEFINITION"
msgstr "Identifies whether a task is a milestone task TRUE or not X 0D FALSE . X 0D X 0D NOTE In small project planning applications, a milestone task may be understood to be a task having no duration. As such, it represents a singular point in time."
#:IFC.xml:27015
msgid "IfcTask_Priority"
msgstr "Priority"
msgid "IfcTask_Priority_DEFINITION"
msgstr "A value that indicates the relative priority of the task in X 0D comparison to the priorities of other tasks ."
#:IFC.xml:27034
msgid "IfcTaskType"
msgstr "IfcTaskType"
msgid "IfcTaskType_DEFINITION"
msgstr "An [[IfcTaskType]] defines a particular type of task that may be specified for use within a work control. HISTORY New entity in IFC4 An [[IfcTaskType]] provides for all forms of types of task that may be specified. It is a reference definition for a unit of work that may be broken down into a sequence of subtasks. Please note that a reference definition can not be part of a workflow definition, i.e. [[IfcTaskType]] instances define the most abstract level of a reference process without dependencies to other reference processes. Usage of [[IfcTaskType]] defines the parameters for one or more occurrences of [[IfcTask]] . Parameters may be specified through property sets that may be enumerated in the [[IfcTaskTypeEnum]] data type or through explict attributes of [[IfcTaskType]] . Task occurrences [[IfcTask]] entities are linked to the task type through the [[IfcRelDefinesByType]] relationship. Figure 1 shows the definition of a task type that is part of a task template library. Please note that in this example the task type is further subdivided into tasks that define task times for example, duration and or a task sequence. task type instantiation diagram .. .. .. .. .. .. figures ifctasktype instantiation diagram.png Figure 1 Task type relationships bSI Documentation"
#:IFC.xml:27046
msgid "IfcTaskType_PredefinedType"
msgstr "PredefinedType"
msgid "IfcTaskType_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27039
msgid "IfcTaskType_WorkMethod"
msgstr "WorkMethod"
msgid "IfcTaskType_WorkMethod_DEFINITION"
msgstr "The method of work used in carrying out a task."
#:IFC.xml:27058
msgid "IfcTaskTypeEnum"
msgstr "IfcTaskTypeEnum"
msgid "IfcTaskTypeEnum_DEFINITION"
msgstr "The [[IfcTaskTypeEnum]] defines the range of different types of task that can be specified. HISTORY New type in IFC4 bSI Documentation"
#:IFC.xml:27082
msgid "IfcTaskTypeEnum_REMOVAL"
msgstr "REMOVAL"
msgid "IfcTaskTypeEnum_REMOVAL_DEFINITION"
msgstr "Removal of an item from use and taking it from its place of use."
#:IFC.xml:27078
msgid "IfcTaskTypeEnum_MAINTENANCE"
msgstr "MAINTENANCE"
msgid "IfcTaskTypeEnum_MAINTENANCE_DEFINITION"
msgstr "Keeping something in good working order."
#:IFC.xml:27077
msgid "IfcTaskTypeEnum_LOGISTIC"
msgstr "LOGISTIC"
msgid "IfcTaskTypeEnum_LOGISTIC_DEFINITION"
msgstr "Transporation or delivery of something."
#:IFC.xml:27081
msgid "IfcTaskTypeEnum_OPERATION"
msgstr "OPERATION"
msgid "IfcTaskTypeEnum_OPERATION_DEFINITION"
msgstr "A procedure undertaken to start up the operation an artifact."
#:IFC.xml:27075
msgid "IfcTaskTypeEnum_DISPOSAL"
msgstr "DISPOSAL"
msgid "IfcTaskTypeEnum_DISPOSAL_DEFINITION"
msgstr "DISPOSAL"
#:IFC.xml:27073
msgid "IfcTaskTypeEnum_DEMOLITION"
msgstr "DEMOLITION"
msgid "IfcTaskTypeEnum_DEMOLITION_DEFINITION"
msgstr "Demolishing or breaking down something."
#:IFC.xml:27074
msgid "IfcTaskTypeEnum_DISMANTLE"
msgstr "DISMANTLE"
msgid "IfcTaskTypeEnum_DISMANTLE_DEFINITION"
msgstr "Taking something apart carefully so that it can be recycled or reused."
#:IFC.xml:27079
msgid "IfcTaskTypeEnum_MOVE"
msgstr "MOVE"
msgid "IfcTaskTypeEnum_MOVE_DEFINITION"
msgstr "Moving things from one place to another."
#:IFC.xml:27076
msgid "IfcTaskTypeEnum_INSTALLATION"
msgstr "INSTALLATION"
msgid "IfcTaskTypeEnum_INSTALLATION_DEFINITION"
msgstr "Installing something equivalent to construction but more commonly used for engineering tasks ."
#:IFC.xml:27072
msgid "IfcTaskTypeEnum_CONSTRUCTION"
msgstr "CONSTRUCTION"
msgid "IfcTaskTypeEnum_CONSTRUCTION_DEFINITION"
msgstr "CONSTRUCTION"
#:IFC.xml:27071
msgid "IfcTaskTypeEnum_ATTENDANCE"
msgstr "ATTENDANCE"
msgid "IfcTaskTypeEnum_ATTENDANCE_DEFINITION"
msgstr "Attendance or waiting on other things happening."
#:IFC.xml:27083
msgid "IfcTaskTypeEnum_RENOVATION"
msgstr "RENOVATION"
msgid "IfcTaskTypeEnum_RENOVATION_DEFINITION"
msgstr "Bringing something to an as new state."
#:IFC.xml:27084
msgid "IfcWorkCalendar"
msgstr "IfcWorkCalendar"
msgid "IfcWorkCalendar_DEFINITION"
msgstr "An [[IfcWorkCalendar]] defines working and non working time periods for tasks and resources. It enables to define both specific time periods, such as from 7 00 till 12 00 on 25th August 2009, as well as repetitive time periods based on frequently used recurrence patterns, such as each Monday from 7 00 till 12 00 between 1st March 2009 and 31st December 2009. HISTORY New entity in IFC4. A work calendar is a subtype of [[IfcControl]] and thus inherits the feature for controlling other objects through [[IfcRelAssignsToControl]] , which is used to define a work calendar for tasks [[IfcTask]] and resources [[IfcResource]] . It also inherits a name and description attribute, whereas a name shall be given and a description may be given as an indication of its content and usage. The definition of time periods can be derived from a base calendar and or modified defined by a set of working times and non working exception times. All time periods defined by [[IfcWorkCalendar]].ExceptionTimes override the time periods inherited from the base calendar base calendar is defined as the next applicable calendar for the task or resource . Thus, exception times replace the working times from the base calendar. Figure 1 shows the definition of a work calendar, which is defined by a set of work times and exception times. The work times are defined as recurring patterns with optional boundaries applying from and or to a specific date . The shown example defines a simple work calendar with working times Monday to Thursday 8 00 to 12 00 and 13 00 to 17 00, Friday 8 00 to 14 00 and as exception every 1st Monday in a month the work starts one hour later i.e. the working time on every 1st Monday in a month is overriden to be 9 00 to 12 00 and 13 00 to 17 00. Both the working time and the exception time is valid for the period of 01.09.2010 till 30.08.2011. task type instantiation diagram .. .. .. .. .. .. figures ifcworkcalendar instantiation diagram.png Figure 1 Work calendar instantiation bSI Documentation"
#:IFC.xml:4063
msgid "IfcWorkCalendar_ExceptionTimes"
msgstr "ExceptionTimes"
msgid "IfcWorkCalendar_ExceptionTimes_DEFINITION"
msgstr "ExceptionTimes"
#:IFC.xml:4075
msgid "IfcWorkCalendar_WorkingTimes"
msgstr "WorkingTimes"
msgid "IfcWorkCalendar_WorkingTimes_DEFINITION"
msgstr "WorkingTimes"
#:IFC.xml:27091
msgid "IfcWorkCalendar_PredefinedType"
msgstr "PredefinedType"
msgid "IfcWorkCalendar_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27103
msgid "IfcWorkCalendarTypeEnum"
msgstr "IfcWorkCalendarTypeEnum"
msgid "IfcWorkCalendarTypeEnum_DEFINITION"
msgstr "An [[IfcWorkCalendarTypeEnum]] is an enumeration data type that specifies the types of work calendar from which the relevant control can be selected. If given it should help to identify base calendars. HISTORY Introduced in IFC4. bSI Documentation"
#:IFC.xml:27109
msgid "IfcWorkCalendarTypeEnum_THIRDSHIFT"
msgstr "THIRDSHIFT"
msgid "IfcWorkCalendarTypeEnum_THIRDSHIFT_DEFINITION"
msgstr "Belongs to the third shift."
#:IFC.xml:27107
msgid "IfcWorkCalendarTypeEnum_FIRSTSHIFT"
msgstr "FIRSTSHIFT"
msgid "IfcWorkCalendarTypeEnum_FIRSTSHIFT_DEFINITION"
msgstr "Belongs to the first shift."
#:IFC.xml:27108
msgid "IfcWorkCalendarTypeEnum_SECONDSHIFT"
msgstr "SECONDSHIFT"
msgid "IfcWorkCalendarTypeEnum_SECONDSHIFT_DEFINITION"
msgstr "Belongs to the second shift."
#:IFC.xml:27110
msgid "IfcWorkControl"
msgstr "IfcWorkControl"
msgid "IfcWorkControl_DEFINITION"
msgstr "An [[IfcWorkControl]] is an abstract supertype which captures information that is common to both [[IfcWorkPlan]] and [[IfcWorkSchedule]] . HISTORY New entity in IFC2x .change ifc2x4 CHANGE IFC4 Corrected assignment of resources to work control in documentation. Assignment of tasks to work control updated based on changes of task time definitions and the introduction of a summary task. Identifier has been renamed now Identification and promoted to supertype [[IfcControl]] A work control may have resources assigned to it. This is handled by the [[IfcRelAssignsToControl]] relationship. A work control should also define a context that gives further information about its usage. If no special context information is required then the [[IfcProject]] instance as a global context should be used instead. An explicit link between the work control and the [[IfcProject]] via [[IfcRelDeclares]] should then be provided. The attribute [[IfcWorkControl]].Purpose is used to define the purpose of either a work schedule or a work plan. In the case of [[IfcWorkPlan]] , the purpose attribute can be used to determine if the work plan is for cost estimating, task scheduling or some other defined purpose. bSI Documentation"
#:IFC.xml:301
msgid "IfcWorkControl_Creators"
msgstr "Creators"
msgid "IfcWorkControl_Creators_DEFINITION"
msgstr "Creators"
#:IFC.xml:27111
msgid "IfcWorkControl_CreationDate"
msgstr "CreationDate"
msgid "IfcWorkControl_CreationDate_DEFINITION"
msgstr "The date that the plan is created."
#:IFC.xml:27116
msgid "IfcWorkControl_Purpose"
msgstr "Purpose"
msgid "IfcWorkControl_Purpose_DEFINITION"
msgstr "A description of the purpose of the work schedule."
#:IFC.xml:27121
msgid "IfcWorkControl_Duration"
msgstr "Duration"
msgid "IfcWorkControl_Duration_DEFINITION"
msgstr "The total duration of the entire work schedule."
#:IFC.xml:27126
msgid "IfcWorkControl_TotalFloat"
msgstr "TotalFloat"
msgid "IfcWorkControl_TotalFloat_DEFINITION"
msgstr "The total time float of the entire work schedule."
#:IFC.xml:27131
msgid "IfcWorkControl_StartTime"
msgstr "StartTime"
msgid "IfcWorkControl_StartTime_DEFINITION"
msgstr "The start time of the schedule."
#:IFC.xml:27136
msgid "IfcWorkControl_FinishTime"
msgstr "FinishTime"
msgid "IfcWorkControl_FinishTime_DEFINITION"
msgstr "The finish time of the schedule."
#:IFC.xml:27144
msgid "IfcWorkPlan"
msgstr "IfcWorkPlan"
msgid "IfcWorkPlan_DEFINITION"
msgstr "An [[IfcWorkPlan]] represents work plans in a construction or a facilities management project. HISTORY New entity in IFC2.0 A work plan contains a set of work schedules for different purposes including construction and facilities management . Contained work schedules are defined through the [[IfcRelAggregates]] relationship. Through inheritance from [[IfcWorkControl]] it is also possible to define references to activities for example, [[IfcTask]] and resources used in the work plan. A work plan has information such as start date, finish date, total free float, and so on. [[IfcWorkPlan]] can also refer to the construction project represented by the single [[IfcProject]] instance please also check the definition of [[IfcWorkControl]] . Figure 1 shows the backbone structure of a work plan that defines 1 contained work schedules through [[IfcRelAggregates]] and 2 , if not assigned otherwise to contained work schedules, assigned tasks and resources through [[IfcRelAssignsToControl]] . If an assigned [[IfcTask]] is a root level task, such task must be declared on the [[IfcProject]] using the [[IfcRelDeclares]] relationship. work plan instantiation diagram .. .. .. .. .. .. figures ifcworkplan instantiation diagram.png Figure 1 Work plan relationships bSI Documentation"
#:IFC.xml:27151
msgid "IfcWorkPlan_PredefinedType"
msgstr "PredefinedType"
msgid "IfcWorkPlan_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27163
msgid "IfcWorkPlanTypeEnum"
msgstr "IfcWorkPlanTypeEnum"
msgid "IfcWorkPlanTypeEnum_DEFINITION"
msgstr "An [[IfcWorkPlanTypeEnum]] is an enumeration data type that specifies the types of work plan from which the relevant control can be selected. HISTORY Introduced in IFC4. Derived from IfcWorkControlTypeEnum that was introduced in IFC2.0. bSI Documentation"
#:IFC.xml:27168
msgid "IfcWorkPlanTypeEnum_BASELINE"
msgstr "BASELINE"
msgid "IfcWorkPlanTypeEnum_BASELINE_DEFINITION"
msgstr "BASELINE"
#:IFC.xml:27167
msgid "IfcWorkPlanTypeEnum_ACTUAL"
msgstr "ACTUAL"
msgid "IfcWorkPlanTypeEnum_ACTUAL_DEFINITION"
msgstr "ACTUAL"
#:IFC.xml:27169
msgid "IfcWorkPlanTypeEnum_PLANNED"
msgstr "PLANNED"
msgid "IfcWorkPlanTypeEnum_PLANNED_DEFINITION"
msgstr "PLANNED"
#:IFC.xml:27170
msgid "IfcWorkSchedule"
msgstr "IfcWorkSchedule"
msgid "IfcWorkSchedule_DEFINITION"
msgstr "An [[IfcWorkSchedule]] represents a task schedule of a work plan, which in turn can contain a set of schedules for different purposes. HISTORY New entity in IFC2.0. .use head Declaration Use Definition [[IfcWorkSchedule]] can reference a project the single [[IfcProject]] instance via [[IfcRelDeclares]] . Figure 1 shows the backbone structure of a work schedule that defines 1 a context through [[IfcRelDeclares]] not necessarily the project and 2 controls tasks typically the schedule summary task and resources. Please note that a work calendar shall be assigned to the summary task and not the work schedule. If an assigned [[IfcTask]] is a root level task, such task must be declared on the [[IfcProject]] using the [[IfcRelDeclares]] relationship. work schedule instantiation diagram .. .. .. .. .. .. figures ifcworkschedule instantiation diagram.png Figure 1 Work schedule relationships bSI Documentation"
#:IFC.xml:27177
msgid "IfcWorkSchedule_PredefinedType"
msgstr "PredefinedType"
msgid "IfcWorkSchedule_PredefinedType_DEFINITION"
msgstr "PredefinedType"
#:IFC.xml:27189
msgid "IfcWorkScheduleTypeEnum"
msgstr "IfcWorkScheduleTypeEnum"
msgid "IfcWorkScheduleTypeEnum_DEFINITION"
msgstr "An [[IfcWorkScheduleTypeEnum]] is an enumeration data type that specifies the types of work schedule from which the relevant control can be selected. HISTORY Introduced in IFC4. Derived from IfcWorkControlTypeEnum that was introduced in IFC2.0. bSI Documentation"
#:IFC.xml:27193
msgid "IfcWorkScheduleTypeEnum_ACTUAL"
msgstr "ACTUAL"
msgid "IfcWorkScheduleTypeEnum_ACTUAL_DEFINITION"
msgstr "ACTUAL"
#:IFC.xml:27195
msgid "IfcWorkScheduleTypeEnum_PLANNED"
msgstr "PLANNED"
msgid "IfcWorkScheduleTypeEnum_PLANNED_DEFINITION"
msgstr "PLANNED"
#:IFC.xml:27194
msgid "IfcWorkScheduleTypeEnum_BASELINE"
msgstr "BASELINE"
msgid "IfcWorkScheduleTypeEnum_BASELINE_DEFINITION"
msgstr "BASELINE"
#:IFC.xml:27196
msgid "Pset_WorkControlCommon"
msgstr "Pset WorkControlCommon"
msgid "Pset_WorkControlCommon_DEFINITION"
msgstr "Properties common to the definition of all occurrences of [[IfcWorkPlan]] and [[IfcWorkSchedule]] subtypes of [[IfcWorkControl]] . bSI Documentation"
#:IFC.xml:27197
msgid "Pset_WorkControlCommon_WorkDayDuration"
msgstr "WorkDayDuration"
msgid "Pset_WorkControlCommon_WorkDayDuration_DEFINITION"
msgstr "The elapsed time within a worktime based day. For presentation purposes, applications may choose to display [[IfcTask]] durations in work days where [[IfcTaskTime]].DurationType WORKTIME. This value must be less than or equal to 24 hours an elapsed day if omitted then 8 hours is assumed."
#:IFC.xml:27202
msgid "Pset_WorkControlCommon_WorkFinishTime"
msgstr "WorkFinishTime"
msgid "Pset_WorkControlCommon_WorkFinishTime_DEFINITION"
msgstr "The default time of day a task is scheduled to finish. For presentation purposes, if the finish time of a task matches the WorkFinishTime, then applications may choose to display the date only. Conversely when entering dates without specifying time, applications may automatically append the WorkFinishTime."
#:IFC.xml:27207
msgid "Pset_WorkControlCommon_WorkMonthDuration"
msgstr "WorkMonthDuration"
msgid "Pset_WorkControlCommon_WorkMonthDuration_DEFINITION"
msgstr "The elapsed time within a worktime based month. For presentation purposes, applications may choose to display [[IfcTask]] durations in work months where [[IfcTaskTime]].DurationType WORKTIME. This value must be less than or equal to 744 hours an elapsed month of 31 days if omitted then 160 hours is assumed."
#:IFC.xml:27212
msgid "Pset_WorkControlCommon_WorkStartTime"
msgstr "WorkStartTime"
msgid "Pset_WorkControlCommon_WorkStartTime_DEFINITION"
msgstr "The default time of day a task is scheduled to start. For presentation purposes, if the start time of a task matches the WorkStartTime, then applications may choose to display the date only. Conversely when entering dates without specifying time, applications may automatically append the WorkStartTime."
#:IFC.xml:27217
msgid "Pset_WorkControlCommon_WorkWeekDuration"
msgstr "WorkWeekDuration"
msgid "Pset_WorkControlCommon_WorkWeekDuration_DEFINITION"
msgstr "The elapsed time within a worktime based week. For presentation purposes, applications may choose to display [[IfcTask]] durations in work weeks where [[IfcTaskTime]].DurationType WORKTIME. This value must be less than or equal to 168 hours an elapsed week if omitted then 40 hours is assumed."