OMA Smart Data Models Mapping for Lighting
Note: This is an early Stage 1 checklist, kept as the record of the original municipality material. The current analysis lives in the OMA Semantic Capability Assessment and the Smart Data Models Semantic Capability Assessment.
Quantities to be measured
- Light on the surface of the streets. (would require a separate illuminance sensor)
- Lumens emitted by the luminaire (can be done by extending OMA data model)
- Watts consumed
- Time at which it was measured (time of completion, or start)
- Color temperature
- Weather at that time (out of scope)
- Weather forecast at that time (out of scope)
- Mains voltage and frequency. Stability.
- Active power, reactive power…
- Additional features: existence of additional elements connected to that branch.
- Location (not always provided by the device itself, but captured during installation)
Measurement conditions
- In each luminaire with Zagha connector
- At the head of the line (show how many luminaires are on it)
- Type of lighting fixtures (pedestrian zone or vehicles)
Data Models
- Outdoor Lamp Controller (OMA) Object #3416
- Electrical Monitor (OMA) Object #3418
- Street Light (Smart Data Models) Object #Streetlight
Mappable information
| OMA | FIWARE | Comments |
|---|---|---|
| Latitude (6/1) Longitude (6/2) | location | could have different attributes |
| Command in action (3416/2) Dimming level (3418/35) | powerState | |
| Timestamp (3418/5518) | observationDateTime | |
| Active power (3418/4) | powerConsumtpion | |
| Cumulated active energy (3418/6) | lifetimePowerConsumption | |
| Power factor (3418/5) | powerFactor | |
| Supply current (3418/2) | current | |
| Supply voltage (3418/1) | voltage | |
| Lamp ON timestamp | dateLastSwitchingOn | |
| Actual light color temperature (3416/40) | TODO | Model needs extension |
| TODO | dateLastSwitchingOff | |
| Sensor Value (3301/5700) | illuminanceLevel |
Another check is that the data type is fully compatible
It seems there is no possibility of control over dimming, but that could be absolutely acceptable. This also explains why the vast majority of the resources are related to the Electrical Monitor (3418) and not to the Outdoor Lamp Controller (3416) The nominal lamp output in lumen at 100% dimming should be added to the OMA Data Model The color temperature is not currently present in the Smart Data Model. It can be extended if there are examples
Tests
Data Models
Single-phase electrical meter (OMA) Object #3421
Three-phase electrical meter complement (OMA) Object #3422
Cabinet Controller Status (OMA) Object #600
Cabinet Controller Manager (OMA) Object #601
StreetlightControlCabinet (Smart Data Models) Object #StreetlightControlCabinet
Mappable information
| OMA | FIWARE |
|---|---|
| Latitude (6/1) Longitude (6/2) | location |
| Active power export (3421/x/17) | activePowerR activePowerS activePowerT |
| Active energy export Un (3422/18) | energyConsumed |
| Frequency (3421/11) | frequency |
| Instantaneous Power Factor (3421/x/13) | powerFactorR powerFactorS powerFactorT |
| Reactive energy export Un (3422/22) | reactiveEnergyConsumed |
| Reactive power export (3421/x/19) | reactivePowerR reactivePowerS reactivePowerT |
| Total active power export on the 3 lines (3422/9) | totalActivePower |
| Total reactive power import on the 3 lines (3422/10) | totalReactivePower |
| Voltage (3421/x/1) | voltageR voltageS voltageT |
Cabinet controller mapping may be somehow complex. Various data models have been defined over the years, with different level of details.