File size: 8,538 Bytes
93ea6b2 | 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 | {
"package": "hyper-ontology/1",
"designed_with": "Praxis",
"implemented_with": "Hyper Ontology",
"paper": {
"title": "Port Drone Watch: From Oil Sheen to Dispatched Work on the Port's Own Hardware in Germany",
"url": "https://codeatoms.ai/drone-detection-dispatch-port-germany/",
"doi": "10.5281/zenodo.23635729"
},
"sector": "maritime-and-ports",
"country": "Germany",
"scenario": "the operator is described by class, never by name: a maritime and ports authority in Germany with two port sites whose retained, docked drone network flies scheduled and on-demand missions under the European specific category, near Seveso perimeters and under GDPR",
"source": "chapter 5 of the paper (the object list and kinds in 5.1, the status vocabularies in 5.2, the recorded form of the Mission in 5.3) and the fourteen typed links and properties of Figure 4; anchors from Table 3, chapter 6.1 and chapter 9.5; the Drone Operator properties and status vocabulary from 10.1; the Coverage Statement vocabulary from 9.4.",
"objects": [
{
"id": "mission",
"label": "Mission",
"kind": "event",
"anchored_in": "The drone operator's mission and fleet system",
"properties": [
"Scheduled or on demand",
"Dock Station",
"Flight authorisation reference",
"Geofence zones crossed",
"Imagery hours produced"
],
"status_vocabulary": [
"Planned",
"Authorised",
"In flight",
"Complete",
"Aborted",
"Grounded by weather"
],
"links": [
{
"to": "dock-station",
"label": "launched from"
},
{
"to": "restricted-zone",
"label": "crosses"
},
{
"to": "flight-authorisation",
"label": "authorised by"
}
]
},
{
"id": "construction-work",
"label": "Construction Work",
"kind": "event",
"anchored_in": "The port's works register (confirmed at the interface survey)",
"properties": [
"Works package",
"Quay",
"Progress observations"
],
"status_vocabulary": [],
"links": [
{
"to": "quay-asset",
"label": "progresses on"
}
]
},
{
"id": "detection",
"label": "Detection",
"kind": "record",
"anchored_in": "Computed in the model from the drone imagery",
"properties": [
"Location",
"Confidence",
"Frames behind it"
],
"status_vocabulary": [
"Proposed",
"Confirmed",
"Rejected",
"Merged"
],
"links": [
{
"to": "mission",
"label": "produced by"
}
]
},
{
"id": "work-item",
"label": "Work Item",
"kind": "record",
"anchored_in": "Owned by this system and pushed to the responders' existing work systems",
"properties": [
"Named responder role",
"Location",
"Confidence"
],
"status_vocabulary": [
"Dispatched",
"Acknowledged",
"Resolved",
"Closed no action"
],
"links": [
{
"to": "responder-role",
"label": "dispatched to"
}
]
},
{
"id": "flight-authorisation",
"label": "Flight Authorisation",
"kind": "record",
"anchored_in": "Granted by the flight approvers under the European specific category",
"properties": [
"Mission",
"Zones covered",
"Approver"
],
"status_vocabulary": [],
"links": []
},
{
"id": "coverage-statement",
"label": "Coverage Statement",
"kind": "record",
"anchored_in": "Computed in the model from weather groundings",
"properties": [
"Area",
"Period",
"Detection classes affected"
],
"status_vocabulary": [
"Published",
"Superseded"
],
"links": [
{
"to": "detection",
"label": "declares"
}
]
},
{
"id": "berth",
"label": "Berth",
"kind": "site",
"anchored_in": "The port GIS berth plan",
"properties": [
"Berth number",
"Quay",
"Length and draft"
],
"status_vocabulary": [],
"links": [
{
"to": "quay-asset",
"label": "sits on"
}
]
},
{
"id": "dock-station",
"label": "Dock Station",
"kind": "site",
"anchored_in": "The drone operator's mission and fleet system",
"properties": [
"Site (one of two port sites)",
"Edge compute unit",
"Network path"
],
"status_vocabulary": [],
"links": []
},
{
"id": "restricted-zone",
"label": "Restricted Zone",
"kind": "site",
"anchored_in": "The port GIS",
"properties": [
"Site (one of two port sites)",
"Geofence polygon",
"Approval requirements",
"Responder-within-minutes rule"
],
"status_vocabulary": [],
"links": [
{
"to": "responder-role",
"label": "escalated to"
}
]
},
{
"id": "vessel",
"label": "Vessel",
"kind": "asset",
"anchored_in": "The vessel traffic feed (AIS/VTS)",
"properties": [
"Name",
"IMO number",
"Vessel type"
],
"status_vocabulary": [],
"links": [
{
"to": "berth",
"label": "occupies"
}
]
},
{
"id": "quay-asset",
"label": "Quay Asset",
"kind": "asset",
"anchored_in": "The port GIS asset register",
"properties": [
"Asset type (quay wall, fender, bollard, lock)",
"Asset ID"
],
"status_vocabulary": [],
"links": [
{
"to": "flight-authorisation",
"label": "inspected under"
}
]
},
{
"id": "drone",
"label": "Drone",
"kind": "asset",
"anchored_in": "The drone operator's mission and fleet system",
"properties": [
"Aircraft ID",
"Dock Station",
"Battery state"
],
"status_vocabulary": [],
"links": [
{
"to": "dock-station",
"label": "docked at"
}
]
},
{
"id": "responder-role",
"label": "Responder Role",
"kind": "actor",
"anchored_in": "The on-site identity service (Keycloak)",
"properties": [
"Detection classes owned",
"Contact path",
"Shift cover"
],
"status_vocabulary": [],
"links": [
{
"to": "detection",
"label": "owns"
}
]
},
{
"id": "drone-operator",
"label": "Drone Operator",
"kind": "actor",
"anchored_in": "The drone operator's service contract",
"properties": [
"Operator name",
"Authorisations held under the European specific category",
"Contract end date",
"Exit handover obligations"
],
"status_vocabulary": [
"In contract",
"Notice period",
"Changed"
],
"links": []
},
{
"id": "weather-observation",
"label": "Weather Observation",
"kind": "measure",
"anchored_in": "The dock weather station or the national meteo service (to confirm, chapter 9.5)",
"properties": [
"Wind speed",
"Visibility",
"Flight go or no-go basis"
],
"status_vocabulary": [],
"links": [
{
"to": "flight-authorisation",
"label": "gates"
}
]
}
],
"write_paths": [
"the adapter tier (the integration adapter family, schema mapping, provenance stamping and replay into the Kafka backbone, idempotent writes into the model)",
"the surfaces used by authenticated responders (Keycloak identities in named roles)",
"work records pushed out to the responders' existing work systems",
"the governed berth plan layer published back to the port GIS"
],
"human_loop": "people decide every response: a Detection stays Proposed until a responder confirms, rejects or merges it, every Work Item is acknowledged with reason codes by its named responder role, and flight approvers grant every mission; automatic acts are limited to confirmation re-flights and notification escalation"
} |