-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathindex.html
More file actions
3051 lines (2999 loc) · 161 KB
/
index.html
File metadata and controls
3051 lines (2999 loc) · 161 KB
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
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<title>Ontology for Construction Quality Assurence (OCQA)</title>
<link rel="icon" type="image/png" sizes="32x32" href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAC40lEQVRYhe2UT0hUQRzHp6Iss1B3VZKIDbbdfW9mnoi4f3zzjkJQeOgS0SEIb1EWBGGlLLu460zQPQM1unUIIjA6rfpm6ZAhHjoIRVQUFUlEbG+euTsdXG1d3VL3bVD4g+9h+L35fT/8fvN7ADgY9aHY5fpIvK82HO9ysu66wxWOzbkjcekKx0a2ALYA/n2AGi3a6ArFezcidziecQygNhhrcUficjP6PwBqtGijKxy/thnVBePHywYoDsFhl53GV8SEcsTx4usCMLUewTVpc23BNvEzm6Neyf1+KcG2vwqwUjgrOJq2JmHftwmkVBRGTvncFodnbI7vChO/FRznCmHsNM7aHM9Yk7Df5iqsLMw9sMNOK2g+jS4IEz0UJv4iuJZb2RltWnB4UZqH6ioGAgAAGe5vtiZhtzDx7OoRadLmeM7m6IRjhnLMW2Vx1bA5GhAmnhIcz6/xNj4Ujsky8UspwfayjDPjsF2Y6L7N8Vzx/BfP+KPg6LbgSqd8DnfJW2CnbaLhfH5ephpqygJYvQU4Z3P82TLRsDDhUTnmrSq+Y3N0Mg+Xldy/zwEAnLMWZ3pHpNExmfLs/t0dOdVcbT0JeKxUwFP2VljjqiE47Jp53LTXNxhsUZjerTByXWX6VZWRs/4bIQ2ACv+UAomgDzLCISNZxAxZKMhIDjLy1JfsaK+I+eGBUBNk5E2x8RogX/PdcDZUqieWTSh5D6nOVKqfhoycUmlHFFIyu5RXqf7AcQDISCpv/tqbMBqK883RtmpISRoxQyJKPgGn3wNk5NEigDFa6hslqV/Kj+FdBQD0bshIDlKSLlVcoWQo36UhR80BAMB73lulMn0EMpJTqD6qJiOt3mho/8GbkT2BZNgDB/V+RI0fkOrT3kRIVQbaDizJm2hdNbINBxwk5xAj3yEjuV9rZ1iIkgxixkLBA83mz8uCjLwoGwAx0vOnFSy5mtR4VTaAQvVORMnwZgSpzkrV/QmdE2tKe46+MQAAAABJRU5ErkJggg==">
<link rel="icon" type="image/png" sizes="16x16" href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAABhklEQVQ4jbWPzStEURjG3yQLirlGKUnKFO45Z+SjmXvnnmthQcpCoVhYmD/AwmJiI3OvZuZc2U3UlKU0/gAslMw9JgvhHxAr2fko7r0jHSsl+TgbTz2Lt5731/MASEiJW9ONml2QyX6rsGalmnT74v8BDf12hxJfpV8d1uwNKUBYszabdFv84L8B9X0rESVmmUup2fme0cVhJWaZHw4NWL1Sew
EAfDe6H3Dy6Ll456WEJsRZS630MwCAOI20ei5OBpxse5zcBZw8eS4uPpfIuDiCainIg9umBCU0GZzgLZ9Hn31OgoATL+CkLDGB5H1OKj4nFd/FBxUXJ0UZNb4edw/6nLyJXaj5FeCVyPLNIVmYK8TG1IwWb16L1gEACAFV90ftoT8bdOX0EeyY99gxBXZMgRz6qGb1KantAACI0UvE6F5XJqEjpsdURouI0Vt5gGOUkUNnPu7ObGIIMfNaGqDmjDRi9FZldF1lRgYzeqUyeoiY4ag5Iy3RgOYRM8+/M2bG8efsO4hGrpmJseyMAAAAAElFTkSuQmCC">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<style>
#pylode {
position: fixed;
top: 130px;
left: -60px;
font-size: small;
transform: rotate(-90deg);
color: grey;
}
#pylode a {
font-size: 2em;
font-weight: bold;
text-decoration: none;
color: #005A9C;
}
#pylode a:hover {
color: #333;
}
.cardinality {
font-style: italic;
color: #aa00aa;
}
dt {
font-weight: bold;
padding: 5px 0 5px 0;
}
ul.hlist {
list-style-type: none;
border: 1px solid navy;
padding:5px;
background-color: #F4FFFF;
}
ul.hierarchy {
border: 1px solid navy;
padding: 5px 25px 5px 25px;
background-color: #F4FFFF;
}
ul.hlist li {
display: inline;
margin-right: 10px;
}
.entity {
border: 1px solid navy;
margin:5px 0 5px 0;
padding: 5px;
}
.entity th {
width: 150px;
vertical-align: top;
}
.entity th,
.entity td {
padding-bottom: 20px;
}
.entity table th {
text-align: left;
}
section#overview img {
max-width: 1000px;
}
h1, h2, h3, h4, h5, h6 {
text-align: left
}
h1, h2, h3 {
color: #005A9C; background: white
}
h1 {
font: 170% sans-serif;
line-height: 110%;
}
h2 {
font: 140% sans-serif;
margin-top:40px;
}
h3 {
font: 120% sans-serif;
margin-top: 3px;
padding-bottom: 5px;
border-bottom: 1px solid navy;
}
h4 { font: bold 100% sans-serif }
h5 { font: italic 100% sans-serif }
h6 { font: small-caps 100% sans-serif }
body {
padding: 2em 70px 2em 70px;
margin: 0;
font-family: sans-serif;
color: black;
background: white;
background-position: top left;
background-attachment: fixed;
background-repeat: no-repeat;
text-align: justify;
}
section {
max-width: 1500px;
}
.figure {
margin-bottom: 20px;
}
:link { color: #00C; background: transparent }
:visited { color: #609; background: transparent }
a:active { color: #C00; background: transparent }
.sup-c,
.sup-op,
.sup-fp,
.sup-dp,
.sup-ap,
.sup-p,
.sup-ni,
.sup-con,
.sup-col {
cursor:help;
margin-left: 3px;
}
.sup-c {
color:orange;
}
.sup-op {
color:navy;
}
.sup-fp {
color:lightskyblue;
}
.sup-dp {
color:green;
}
.sup-ap {
color:darkred;
}
.sup-p {
color:black;
}
.sup-ni {
color:brown;
}
.sup-con {
color:orange;
}
.sup-col {
color:darkred;
}
code {
font-size: large;
color: darkred;
}
/* less prominent links for properties */
.proplink {
color: #336;
text-decoration: none;
}
</style>
<script type="application/ld+json">
[
{
"@id": "https://w3id.org/ocqa#",
"@type": [
"https://schema.org/DefinedTermSet"
],
"https://schema.org/description": [
{
"@value": "<ul>\n<li>Version 0.3</li>\n<li>CoreModel</li>\n</ul>"
}
],
"https://schema.org/license": [
{
"@id": "https://creativecommons.org/licenses/by/1.0"
}
],
"https://schema.org/name": [
{
"@value": "Ontology for Construction Quality Assurence (OCQA)"
}
]
}
]
</script>
</head>
<body>
<div id="pylode">made by <a href="http://github.com/rdflib/pyLODE">
<span style="color:#329545;">p</span><span style="color:#f9cb33;">y</span>LODE</a>
<span style="font-size:smaller;">2.13.2</span>
</div>
<h1>Ontology for Construction Quality Assurence (OCQA)</h1>
<section id="metadata">
<h2 style="display:none;">Metadata</h2>
<dl>
<dt>URI</dt>
<dd><code>https://w3id.org/ocqa#</code></dd>
<dt><a class="proplink" href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/creator">Creator</a>(s)</dt>
<dd>
Sebastian Seiß<br/>
</dd>
<dt><a class="proplink" href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/modified">Modified</a></dt>
<dd>2024-03-18</dd>
<dt><a class="proplink" href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/issued">Issued</a></dt>
<dd>2022-01-01</dd>
<dt>Imports</dt>
<dd>
<a href="http://w3id.org/digitalconstruction/0.5/Units">http://w3id.org/digitalconstruction/0.5/Units</a><br/>
<a href="https://w3id.org/digitalconstruction/0.5/Information">https://w3id.org/digitalconstruction/0.5/Information</a><br/>
<a href="https://w3id.org/ocqa/catalog.html">https://w3id.org/ocqa/catalog</a><br/>
<a href="https://w3id.org/ocqa/contract.html">https://w3id.org/ocqa/contract</a><br/>
<a href="https://w3id.org/ocqa/regulation.html">https://w3id.org/ocqa/regulation</a><br/>
<a href="https://w3id.org/ocqa/rule.html">https://w3id.org/ocqa/rule</a><br/>
<a href="https://w3id.org/ocqa/adaptive.html">https://w3id.org/ocqa/adaptive</a><br/>
</dd>
<dt>License</dt>
<dd><a href="https://creativecommons.org/licenses/by/1.0">https://creativecommons.org/licenses/by/1.0</a></dd>
<dt>Ontology RDF</dt>
<dd><a href="https://w3id.org/ocqa/ocqa.ttl">RDF (turtle)</a></dd>
<dd><a href="https://SebSeis.github.io/OCQA/ocqa.jsonld">RDF (jsonld)</a></dd>
</dl>
<h2>Description</h2>
<div id="description">
<ul>
<li>Version 1.0</li>
<li>CoreModel</li>
</ul>
</div>
</section>
<section id="toc">
<h2>Table of Contents</h2>
<ol>
<li><a href="#overview">Overview</a></li>
<li><a href="#specification">Specification</a></li>
<li><a href="#modules">Modules</a></li>
<li><a href="#classes">Classes</a></li>
<li><a href="#objectproperties">Object Properties</a></li>
<li><a href="#datatypeproperties">Datatype Properties</a></li>
<li><a href="#annotationproperties">Annotation Properties</a></li>
<li><a href="#namedindividuals">Named Individuals</a></li>
<li><a href="#namespaces">Namespaces</a></li>
<li><a href="#legend">Legend</a></li>
</ol>
</section>
<section id="overview">
<h2>Overview</h2>
<p>This document provides a description of the Ontology for Construction Quality Assurance (OCQA), which is
designed to represent explicit knowledge about the domain of quality inspection planning. The ontology is
intended to provide a standardized vocabulary for describing concepts, entities, and relationships relevant
to inspection planning in construction execution. It is based on a set of axioms that define the properties
and relationships of the concepts within the ontology. This document includes an overview of the ontology
structure, the types of entities and relationships represented, and the intended applications of the
ontology. It also provides guidance on how to use and extend the ontology, and describes the processes used
to develop and maintain it. The development of the OCQA follows the Linked Open Terms (LOT) methodology and
is encoded using Semantic Web Ontology Language (OWL) to ensure machine-readability and alignment with other
ontologies. According to LOT, we provide the ontology requirements specification document (ORSD), which can
be found in the specification section. The OCQA is evaluated using various approaches, including automatic
consistency checking, competency questions, criteria-based evaluation, and focus group interviews. </p>
<p>The OCQA is based on four modules to fully describe the required data (see Figure below). Each of these
modules reflect construction domain knowledge that is directly related to the OCQA and thus to inspection
planning. In particular, DiCon is reused in the OCQA as a module to provide the basic terminologies and
concepts related to construction execution, as shown in Figures 4 and 6. DiCon is a higher-level domain
ontology that generically represents construction workflow knowledge with related entities and properties.
The DiCon ontology contains basic concepts for describing components, construction activities, materials,
agents, and more. For example, the goal of an inspection can be related to a component, activity, or person,
thus satisfying the high variance of inspections and possible inspection characteristics. Furthermore, DiCon
has built alignments with existing relevant ontologies that enable the direct integration of heterogeneous
systems in the construction domain. For example, DiCon has aligned with ifcOWL and BOT to integrate building
information models, organizational descriptions, and schedules. DiCon is implemented in the OCQA as hard
reuse via owl:imports, which reuses the imported ontology as it is and as a whole. In turn, the OCQA is
itself an extension of the DiCon ontology. The OCQA-Catalog module is used to store quality-related
information. The catalog module contains parameters about failure probabilities, performance and cost rates,
which can be used for example to estimate costs and durations of inspections. The OCQA-Regulations module is
used to store the corresponding norms, guidelines and standards, to which inspections or contracts refer.
Contracts are described via the OCQA-Contract module.</p>
<p>To keep the ontology lean and flexible, inspection-specific contents of the inspection planning were
modeled as extensions according to their trade-specific terminology. These extensions specify the classes of
the OCQA to fit their trade-specific terminology. The extensions are not limited to the OCQA but can also be
applied to modules like trade-specific regulations or catalogs. The extendibility of the ontology enables
the use of the OCQA in different contexts and the customization of the ontology depending on the needs of a
project. The extensions can be added to the ontology as needed, for example, to add the trades that are
required for the construction project or that are covered by a construction company. Moreover, the
modularization into trades not only simplifies the further development of the ontology, allowing different
users to extend it, but also paves the way for an expansive compilation of diverse trades.
</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/Overview_of_OCQA.png" alt="Italian Trulli" style=" height: 550px;">
<div class="caption"><strong>Figure 1:</strong>Overall architecture of OCQA</div>
</div>
</section>
<section id="specification">
<h2>Specification</h2>
<p>The objective of this section is to provide a formal specification document utilizing competency questions
(CQs) as requirements. The CQs are extracted from use cases, which are based on the intended purpose and
scope of the relevant ontology during the specification process. The subsequent table represents the
ontology requirements specification document (ORSD), which provides all results of the specification
process.</p>
<table style="width: 81%; border-collapse: collapse; border: none; margin-right: calc(19%);">
<caption><strong>Table 1:</strong>Ontology requirements specification document (ORSD)of OCQA</caption>
<tbody>
<tr>
<td colspan="2"
style="width: 450pt;border: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;height: 21pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;text-align:center;border:none;'>
<strong><span style="color:black;">Ontology Requirements Specification
Document</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">1</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Purpose</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
The purpose of the OCQA is to provide a structural basis for representing project-specific
inspection plan in construction execution and to support decision making in the process of
inspection planning. The objective is to ensure a transparent, objective, and rule-based
process for assigning building permit applications. The ontology will support civil
engineers in gaining a better understanding of inspection plans. Accordingly, the ontology
will provide terminology and semantics to describe inspections and inspection planning
knowledge.</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">2</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Scope</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
The OCQA aims to represent inspections and inspection plans in construction, applicable
across various trades in the construction domain. The terminology conforms to DIN 55350, ISO
9000, and ISO 9001 standards. It encompasses inspections and related entities such as
agents, equipment, procedures, norms, costs, instructions, and failure probabilities. The
ontology is therefore designed as a domain-specific model, aligning both
construction-specific and high-level ontologies to provide comprehensive knowledge
representation about inspection-related entities. Furthermore, the OCQA integrates
heterogeneous data from multiple knowledge domains, ensures the consistency of inspection
plans, facilitates inspection coordination within a company or project, and enables
information exchange among relevant parties.</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">3</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Implementation Language</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
The implementation language for the OCQA is OWL for the T-Box and SHACL for business rules
(i.e., the R-Box). This approach provides the necessary flexibility and expressiveness for
modeling the complex relationships between building permit authorities, building officials,
and building applications. The OCQA is operating bilingually in English and German.</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">4</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Intended End-Users</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
The primary end-users of the OCQA ontology are stakeholders in the construction execution
process and work preparation, including construction managers, experts, architects, work
planners, foremen, construction workers, and suppliers. These users interact with the
ontology indirectly through a software application, which serves as a user-friendly
interface. Developers will directly use the OCQA as a substructure for programming software
applications, enabling the storage and processing of inspection data from heterogeneous
sources.</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">5</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Intended Uses</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
The OCQA is used to support the following use cases:</p>
<div style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom: 0cm; margin-left: 23.7px;"><span class="fr-close-ol"></span><span
class="fr-close-ol"></span>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Description of inspection plans and relevant information</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Provision of knowledge to support decision making in the inspection planning</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
(Semi-)Automated planning of inspections</li>
</ol>
</div>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">6</span></strong>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Ontology Requirements</span></strong>
</p>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<ol style="margin-bottom:0cm;margin-top:0cm;" start="1" type="a">
<li
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Non-Functional Requirements</span></strong>
</li>
</ol>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
In addition to these use cases, the following nonfunctional requirements have been
identified as crucial for the OCQA:</p>
<div style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: decimal;">
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Coverage and sufficiency</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Consistency</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Usability</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Clear and concise terminology</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Reusability and extensibility</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Reliability and transparency</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Modularity</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Adherence to the FAIR principles (Findable, Accessible, Interoperable, and Reusable)
</li>
</ol>
</div>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;background: rgb(239, 239, 239);padding: 5pt;vertical-align: top;">
<ol style="margin-bottom:0cm;margin-top:0cm;" start="2" type="a">
<li
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
<strong><span style="color:black;">Functional Requirements: Lists or tables of
requirements written as Competency Questions (CQs) </span></strong>
</li>
</ol>
</td>
</tr>
<tr>
<td
style="width: 31.5pt;border-right: 1pt solid black;border-bottom: 1pt solid black;border-left: 1pt solid black;border-image: initial;border-top: none;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
<td
style="width: 418.5pt;border-top: none;border-left: none;border-bottom: 1pt solid black;border-right: 1pt solid black;padding: 5pt;vertical-align: top;">
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
Use Case 1: Description of inspection plans and relevant information</p>
<div style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: decimal;margin-left:52.05px;">
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What are the characteristics being inspected?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What type of inspection is it?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What are the related entities of an inspection?</li>
<ul>
<div
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: decimal;">
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What inspection procedure is used?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What inspection equipment is required for the inspection?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Where is the inspection located?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What agent processes or has processed the inspection?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which company hires the person who is responsible for the inspection?
</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Does the responsible person has the required skills to execute the
inspection?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Why is the inspection required?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
How often does the measurement of the inspection have to be done?</li>
</ol>
</div>
</ul>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What is the start and end date of an inspection?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
How are inspections interlinked in an inspection plan and interlinked with the
construction schedule?</li>
<ul>
<div
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: decimal;">
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What construction activity is related to the inspection?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What is the preceding/following construction activity of the inspection?
</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What is the precding/following inspection of the inspection?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which inspection can be done on a specific point of time?</li>
<li
style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What will be the best time point to do as many inspections in one site
inspection?</li>
</ol>
</div>
</ul>
</ol>
</div>
<p
style='margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
Use Case 2: Providing knowledge to support decision making in inspection planning</p>
<div style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: undefined;margin-left:52.05px;">
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which inspection types can be assigned or are required by an activity, building
object, or location?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which entities are required for an inspection type?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What are the time constraints of an inspection type?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which inspection characteristics can be inspected by an inspection type?</li>
</ol>
</div>
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
Use Case 3: (Semi-)Automated planning of inspections</p>
<div style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
<ol style="margin-bottom:0cm;list-style-type: undefined;margin-left:52.05px;">
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which inspection should be done for the specific construction project (considering
different information like schedule, contract, design (BIM), construction equipment,
norms and standards)?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
When should the inspection start and end?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
What should be the frequence and scope of the inspection?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Who should process the inspection?</li>
<li style='margin:0cm;line-height:115%;font-size:15px;font-family:"Arial",sans-serif;'>
Which inspection procedure and equipment should be used to execute the inspection?
</li>
</ol>
</div>
<p
style='margin:0cm;line-height:normal;font-size:15px;font-family:"Arial",sans-serif;border:none;'>
</p>
</td>
</tr>
</tbody>
</table>
</section>
<section id="modules">
<h2>Modules</h2>
<h3 id="core">OCQA - Core module</h3>
<p>
Building upon this foundations Figure 6 illustrates a simplified structure of the proposed concept of the
OCQA, with the class ocqa:Inspection in the center. The OCQA is designed to represent detailed inspection
plans. Therefore, the OCQA represents inspections and associated entities of an inspection, like inspection
equipment, inspectors, inspection objects, and inspection methods in detail. An inspection is designed as a
subclass of <i>dicp:Activity</i> in the OCQA. For this reason, an inspection can be assigned a start and end
date as well as a duration according to the activity. </p>
<p>The approach to model an inspection as an activity enables a deep integration of the inspections into the
construction process including the schedule and the alignment with various entities of the construction
process itself. Construction related entities are represented by the DiCon ontology and their alignments.
Together with the contract, regulation and catalog module the OCQA provides all relevant inspection planning
information. In addition, this enables the inspection planners to describe planned inspections in detail and
answer all the required W-Questions.</p>
<p>Likewise, entities to be inspected, such as dice:Location, dice:BuildingObject or <i>dicp:Activity</i> can be
assigned. The objective of an inspection can be any entity, which includes several characteristics to be
inspected. For this reason, the inspection refers not only to the entity to be inspected but also to the
inspection characteristics of the entity itself. The inspection characteristics are modeled as
<i>ocqa:Characteristic</i> and are aligned to the object being inspected as well as to the inspection
itself. The class ocqa:Characterisitc refers to an ocqa:AssignedCharacteristicValue as a requirement to be
achieved and an ocqa:ActualCharacteristicValue as a determined actual value. Accordingly, the
ocqa:AssignedCharacteristicValue can be used as a direct comparison value to determine the conformance of
the object regarding the inspection characteristic. The assigned characteristic value is required by
regulations like norms or any other entity defining specific requirements for the object in question.
Following the structure, the comparison of the assigned and actual characteristic can be done by
standardized rules using a query or rule language.
</p>
</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/Core.png" alt="Italian Trulli">
<div class="caption"><strong>Figure 2:</strong> Illustration of the core module</div>
</div>
<h3 id="catalog">Catalog module</h3>
<desc>Prefix:ocqa-cat; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/Catalog/OCQA-Catalog.ttl">https://w3id.org/ocqa/catalog</a></desc>
<p>To support the inspection planning process with essential data and knowledge, a catalog module is developed.
The master data comprises, for example, information on failure probabilities, performance rates for
inspection execution, and cost rates for failures or inspections. The feature catalog module is able to
describe several master datasets that are integral to inspection planning. The values of these master
datasets are stored as ocqa-cat:Features in a data catalog and are linked to ocqa:Inspection or other
classes via ocqa:hasFeature (see Figure 7). To provide fitting value relations, ocqa-cat:hasFeature can be
specialized by sub-properties, such as ocqa-cat:hasFailureProbabilityFeature to describe the failure
probability of an inspection. The features are stored in the catalog called ocqa-cat:SubFeatureCatalog,
which is defined as a dataset of ocqa-cat:FeatureCatalog. The ocqa-cat:Feature represents a subclass of
opm:Property and can therefore be updated with actual costing values according to the Ontology for Property
Management (OPM). The catalogs are designed according to the Data Catalog Vocabulary ontology and can be
differentiated into a main catalog and a sub-catalog. Resulting estimations for costs or time efforts based
on features can be aligned to inspections via a direct property.</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/Catalog.png" alt="Italian Trulli" style="height: 200px;">
<div class="caption"><strong>Figure 3:</strong> Illustration of the catalog module</div>
</div>
<h3 id="contract">Contract module</h3>
<desc>Prefix:ocqa-con; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/Contract/OCQA-Contract.ttl">https://w3id.org/contract</a>
</desc>
<p>The contract module will handle individual contracted quality requirements. Individual quality requirements
are contractually agreed upon directly between the project participants via individual contract components.
These requirements extend or reduce the general contracted quality requirements, which are contract
regulations that set only the minimum quality requirement. The agreed contractual terms not only define
the quality requirements but also specify inspections to be performed. The tasks of the contract module are
to support the planning of inspections and to refer planned inspections to the specified inspection
requirements defined in contractual documents. The contractual module is therefore based on several classes,
as illustrated in Figure below.</p>
<p>performance description occurs via a functional performance description or a BOQ. Accordingly,
ocqa-con:FunctionalPerformanceDescription and ocqa-con:BOQ are modeled as subclasses of
ocqa-con:PerformanceDescription. The BOQ is defined as a structured description of required work by a set of
ocqa-con:BOQItems, including a number, description, quantity, unit, and price. Both BOQs as well as
functional performance descriptions can directly require inspections, which is considered by the relation
ocqa-con:requiredby. Further contractual components that have to be considered in inspection planning are
ocqa-con:GeneralTerms and ocqa-con:GeneralTechnicalTerms.
</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/Contract.png" alt="Italian Trulli" style="height: 350px;">
<div class="caption"><strong>Figure 4:</strong> Illustration of the contract module</div>
</div>
<h3 id="contract">Regulation module</h3>
<desc>Prefix:ocqa-reg; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/Regulation/OCQA-Regulation.ttl">https://w3id.org/ocqa/regulation</a>
</desc>
<p>To handle inpsection planning knowledge provided by norms, standards, and guidelines we provide the
regulation module. The regulation module is used as a reference for all kind of rules relevant for
inspection planning. It does not matter, if this rules are provided by company internal standards or
guidelines or by external organisations like DIN or ISO.</p>
<p>Norms, standards, and guidelines are modeled in the OCQA as a regulation module to provide knowledge of norms
and standards for inspection planning. A norm is based on the consensus of experts participating in a
norming process. On the other hand, a standard refers to the standardization of dimensions, types,
procedures, and other factors without necessarily being based on a set of rules, a consensus, or a specific
procedure. A further aspect that has to be considered in the planning of inspections is manufacturer
guidelines, which also provide detailed requirements for the product and inspection tasks. Moreover,
company-specific guidelines can be represented in the ontology to ensure a comprehensive mapping of possible
sources of rules described in the rule module. Regulations are represented by the class ocqa-reg:Regulation
and the subclasses ocqa-reg:Norm, ocqa-reg:Standard, and ocqa-reg:Guideline (see Figure 4).
</p>
<h3 id="extension">Rule module</h3>
<desc>Prefix:ocqa-rule; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/Rule/OCQA-Rule.ttl">https://w3id.org/ocqa/rule</a></desc>
<p>The rules module accommodates different types of inspections, which 1) check the consistency of input data
for inspection planning, 2) perform inspection planning, and 3) validate planned inspections. These rules
share a common goal of supporting the inspection planner in the inspection planning process. It is important
to note that the described use cases for inspection planning are not exhaustive and can be expanded to
include compliance checks if necessary.</p>
<p>The rule module is remodelled according to the rule ontology illustrated by Zheng 2022. The rules are
represented by the class <i>ocqa-rule:Rule</i> and are linked to the <i>dice:Entity</i> through the object
property <i>ocqa-rule:inferredBy</i> (see Figure 5). This relationship ensures that each
subclass of <i>dice:Entity</i> such as <i>ocqa:Inspection</i>, <i>dicp:activity,</i>
<i>ocqa:InspectionEquipment</i> or <i>ocqa:InspectionProcedure</i> can be inferred by a rule. This
distinction allows rules to be categorized based on the inspection characteristics, which have to be planned
by the rules, as described earlier.
</p>
<p> The rules are linked to a SHACL shape, which defines the content of a rule using either a
<i>sh:NodeShape</i> or a <i>sh:PropertyShape</i>. In SHACL, a NodeShape is a type of shape that focuses on
validating individual nodes in an RDF data graph. When a target class is associated with a NodeShape, it
means that the constraints defined within that shape apply only to instances of the specified target class,
including any subclasses of <i>dice:Entity</i>. A PropertyShape, on the other hand, focuses on validating
the values of a specific property for a node in an RDF data graph. The properties to get validated are
defined as <i>dicv:Property</i> and are related to the <i>dice:Entity</i>. The rules themselves are defined
based on regulations, represented by <i>ocqa-reg:Regulation</i>. The connection between a rule and a
regulation is necessary to describe the rule's source and to identify all rules that must be applied due to
contractual constraints.
</p>
<p> In addition, the rules within the system can be categorized into two types: generic rules and specific
rules, denoted as <i>ocqa-rule:GeneralRule</i> and <i>ocqa-rule:SpecificRule</i> respectively. Generic rules
are designed to guide the planning of inspections for specific classes of inspections. An example of a
generic rule is setting the earliest start or end time for an inspection. Another instance is the automated
generation of geometric inspections based on the information extracted from the BIM model. On the other
hand, specific rules are tailored to address explicit requirements derived from the contract or regulations
module. For instance, a specific rule may dictate that the evenness of a screed must be assessed prior to
installation. For further classification of the rules, subclasses according to the task of the rule are
defined like <i>ocqa-rule:InspectionPlanningRule</i>, <i>ocqa-rule:InspectionPlanningEvaluationRule</i> and
<i>ocqa-rule:InspectionEvaluationRule</i>. Furthermore, the rules have additional information about the
creator via <i>dice:Agent</i>, the version of the rule using <i>ocqa-rule:hasVersion</i> and the creation
date of the rule using <i>ocqa-rule:HasCreationTime</i>.
</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/Rule.png" alt="Italian Trulli" style="height: 300px;">
<div class="caption"><strong>Figure 5:</strong>Screed-specific extension of the OCQA by subclasses.</div>
</div>
<h3 id="extension">Appraisal cost and Non-confirmity cost module</h3>
<desc>Prefix:ocqa-ac; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/AC/OCQA-AC.ttl">https://w3id.org/ocqa/ocqa-ac</a></desc>
<desc>Prefix:ocqa-risk; Namespace:<a
href="https://SebSeis.github.io/OCQA/Modules/AC/OCQA-RISK.ttl">https://w3id.org/ocqa/ocqa-risk</a></desc>
<p>The Appraisal cost and Non-confirmity cost modules contain a rich and comprehensive terminology to describe appraisal costs and non-conformity costs. The OCQA-AC uses a catalog containing cost values and SHACL rules to inference the appraisal costs of an inspection. The appraisal costs will be represented as ocqa-ac:hasAppraisalCost (see Figure 6). The OCQA-RISK uses the cost to fix a non-confirmity based on the percentange along the production cost. This costs are multiplied with probability of the non-confirmity to calculate the risk represented as ocqa-risk:hasPotentialNCC (see Figure 6). The estimation of the costs are done using SHACL-Rules.</p>
<p>The cost values of ocqa-ac:hasAppraisalCost and ocqa-risk:hasPotentialNCC enables us to do a cost comparison to minimize quality costs. To minimize qualiy costs and to therefore find the lowest total quality costs only inspection are done, if a potential financial impact of defects is greater or equal to the cost required for inspection activities (NCC ≥ AC). Therefore, it will be possible to reach the optimal QC level for the inspection plan as described in Figure \ref{fig:OptimumTotalCost}. The automated decision-making support mechanism was implemented using a SHACL rule. If the ACs are less than or equal to the NCCs, the inspection status is set to "planned." Conversely, if the ACs exceed the NCCs, the inspection status is set to "blocked." Notably, this inference rule serves as a decision-support tool and can be overridden by the user as needed.</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/OCQA-AC-NCC-Interaction.png" alt="Italian Trulli" style="height: 300px;">
<div class="caption"><strong>Figure 6:</strong>Screed-specific extension of the OCQA by subclasses.</div>
</div>
<p>An example case on how to use the OCQA-AC and OCQA-RIKS is provided in the following Figure 7. The exmaple illustrates the cost comparison of a flatness inspection for screed illustrating the cost to fix uneveness and the cost of an inspection.</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/OCQA-Risk-AC-Example.png" alt="Italian Trulli" style="height: 300px;">
<div class="caption"><strong>Figure 7:</strong>Example of interaction for OCQA-AC and OCQA-RISK.</div>
</div>
<h3 id="extension">Trade-specific extensions</h3>
<desc>Prefix:ocqa-screed; Namespace:<a
href="https://SebSeis.github.io/OCQA/Extensions/Screed/OCQA-Screed.ttl">https://w3id.org/ocqa-screed</a></desc>
<desc>Prefix:ocqa-insulation; Namespace:<a
href="https://SebSeis.github.io/OCQA/Extensions/Insulation/OCQA-ThermalInsulation.ttl">https://w3id.org/ocqa-insulation</a></desc>
<p>Task-specific inspection planning is covered by trade-specific extensions of the OCQA ontology. For
example, the extension OCQA-screed covers all inspections regarding the trade screed. The extensions are
defined in separate OWL-Ontologies, such as OCQA-Screed for the trade screed or OCQA-Insulation for
insulation trades. To ensure compatibility with the OCQA, these ontologies have to be aligned with the
OCQA core and modules. The extension is done by using rdfs:subClassOf to expand the generic classes of
OCQA and its modules for trade-specific use cases. An example of the extension for screed and insulation
is given in Figure 6. The use of extensions enables improved reusability of the ontology as it becomes
easier to share and extend trade-related knowledge between users. Furthermore, the complexity of the
ontology is reduced since only the trades necessary for the user have to be represented in the ontology.
</p>
<div class="figure">
<img src="https://SebSeis.github.io/OCQA/Pictures/ExtensionScreed.png" alt="Italian Trulli" style="height: 300px;">
<div class="caption"><strong>Figure 8:</strong>Screed-specific extension of the OCQA by subclasses.</div>
</div>
<section id="classes">
<h2>Classes <span style="float:right; font-size:smaller;"><a href="">↑</a></span></h2>
<ul class="hlist">
<li><a href="http://w3id.org/seas/Property">http://w3id.org/seas/Property</a></li>
<li><a href="https://w3id.org/digitalconstruction/0.5/Entities#Equipment">dice:Equipment</a></li>
<li><a href="https://w3id.org/digitalconstruction/0.5/Entities#Object">dice:Object</a></li>
<li><a href="https://w3id.org/digitalconstruction/0.5/Entities#Occurrent">dice:Occurrent</a></li>
<li><a href="https://w3id.org/digitalconstruction/0.5/Processes#Activity">dicp:Activity</a></li>
<li><a href="#actualcharacteristicvalue">actual characteristic value</a></li>
<li><a href="#characteristicvalue">characteristic value</a></li>
<li><a href="#Causation">Causation</a></li>
<li><a href="#Characteristic">Characteristic</a></li>
<li><a href="#Conformity">Conformity</a></li>
<li><a href="#ConstructionProcedure">ConstructionProcedure</a></li>
<li><a href="#Damage">Damage</a></li>
<li><a href="#Defect">Defect</a></li>
<li><a href="#Determination">Determination</a></li>
<li><a href="#Evaluation">Evaluation</a></li>
<li><a href="#ExternalResource">ExternalResource</a></li>
<li><a href="#FailureCategorie">Failure Categorie</a></li>
<li><a href="#Image">Image</a></li>
<li><a href="#Inspection">Inspection</a></li>
<li><a href="#InspectionEquipment">InspectionEquipment</a></li>
<li><a href="#InspectionPlan">InspectionPlan</a></li>
<li><a href="#InspectionProcedure">InspectionProcedure</a></li>
<li><a href="#Inspector">Inspector</a></li>
<li><a href="#Measurement">Measurement</a></li>
<li><a href="#MeasuringEquipment">MeasuringEquipment</a></li>
<li><a href="#Monitoring">Monitoring</a></li>
<li><a href="#Nonconformity">Nonconformity</a></li>
<li><a href="#Plan">Plan</a></li>
<li><a href="#procedure">procedure</a></li>
<li><a href="#ProgressEvaluation">ProgressEvaluation</a></li>
<li><a href="#Protocol">Protocol</a></li>
<li><a href="#qualitativecharacteristic">qualitative characteristic</a></li>
<li><a href="#quantitativecharacteristic">quantitative characteristic</a></li>
<li><a href="#Documentation">Documentation</a></li>
<li><a href="#Result">Result</a></li>
<li><a href="#Review">Review</a></li>
<li><a href="#Sample">Sample</a></li>
<li><a href="#Test">Test</a></li>
<li><a href="#Video">Video</a></li>
<li><a href="https://w3id.org/ocqa/contract#CostFeatureCatalog">ocqa-con:CostFeatureCatalog</a></li>
<li><a href="https://w3id.org/ocqa/contract#FailureProbabilityCatalog">ocqa-con:FailureProbabilityCatalog</a></li>
<li><a href="https://w3id.org/ocqa/contract#FeatureCatalog">ocqa-con:FeatureCatalog</a></li>
<li><a href="https://w3id.org/ocqa/contract#FeatureState">ocqa-con:FeatureState</a></li>
<li><a href="https://w3id.org/ocqa/contract#TimeRateCatalog">ocqa-con:TimeRateCatalog</a></li>
<li><a href="https://w3id.org/opm#Property">opm:Property</a></li>
<li><a href="https://w3id.org/opm#PropertyState">opm:PropertyState</a></li>
</ul>
<div class="entity class" id="Property">
<h3>
Property<sup title="class" class="sup-c">c</sup>
<span style="float:right; margin-right:10px; font-size:smaller;"><a href="#Property" title="fragment link to here">#</a> <a href="#classes" title="Classes Index">Classes</a></span>
</h3>
<table>
<tr>
<th>URI</th>
<td><code>http://w3id.org/seas/Property</code></td>
</tr>
<tr>