nemocommon information models - nemo...
TRANSCRIPT
![Page 1: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/1.jpg)
NEMO COMMON INFORMATION MODELS
Dr. Evangelia Portouli
Senior Researcher, ICCSNeMo Stakeholder Forum Conference, Ehningen
(Stuttgart), 12 October 2017
![Page 2: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/2.jpg)
Rationale for the work
• Lack of Interoperability in electromobility services
• Lack of a common data and information model for objects and services
– typically, proprietary software and data formats to communicate/exchange necessary information
– proprietary data management and interfacing between actors
• Lack of standardisation regarding information exchange and services provision
• Electromobility actors are diverse
212 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
![Page 3: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/3.jpg)
NeMo Key Objective
• One of the pillars of NeMo Hyper-Network is
the possibility to exchange data using a
common NeMo meta-language
312 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
− Common Information Models (CIM)
− Data translators and common interfaces
− Smart Processing and Data Management algorithms
CIM
CIM
CIM
CIM
![Page 4: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/4.jpg)
Common Information Model
• Models physical objects and data structures
which are relevant for the use cases selected
in the project
• Based on previous relevant work and
integrates existing standards on information
modelling related to electromobility
• Creates a consistent format for data to be
available to others
412 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
![Page 5: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/5.jpg)
Common Information Model
512 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
Standardized model for
information sharing across
the NeMo Hyper-Network
Implementation of
the standardized CIM
![Page 6: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/6.jpg)
Methodology
– Based on the 7 NeMo Business Scenarios
– Identification of Business Objects (physical entities
and data structures) that need modelling
– Definition of attributes per Business Object
(name, definition, necessity, instances, format)
– Used the template of the eMi3 Electric Vehicle ICT
Interface Specifications Part 2
612 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
![Page 7: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/7.jpg)
Business Objects categorisation
• Electric Vehicle
• Charging Infrastructure
• Final User
• Charge Session
• Smart Charging Functionalities
• Marketplace for service creation and delivery
• Grid loads
• Vehicle preparation for drive-off
712 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
![Page 8: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/8.jpg)
Vehicle Business Objects
• Information from different sources, for example Neutral Server and a NeMo service
• Battery – BatteryID, VIN, BatteryType, BatteryCapacity, SoC, SoH,
BatteryFault, ChargeCompletionEstimatedTime, ChargingStatus
• Vehicle – VIN, Manufacturer, VehicleModel, ChargingMode, MaxPower,
VehiclePower, VehicleRange, VehicleSpeed, VehicleODO, VehicleConsumption, VehicleRemainingDistance, CurrentLocation, DestinationLocation, ExternalTemperature, VehicleHeatingStatus, VehicleACStatus, PreconditioningFunctionalities
NeMo, meeting/event title, Venue 8
![Page 9: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/9.jpg)
Charge session Business Objects
• Authorisation
• ChargeDetailRecord
– models the information about a finished charge
session (update of the eMI3 model)
• ChargingPeriodRecord
– One charging session consists of one or more
charging periods
NeMo, meeting/event title, Venue 9
![Page 10: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/10.jpg)
Smart Charge Business Objects
• UserMobilityNeed– data structure that is sent from an EMP or from a customer’s device, in order
to schedule a charging session for an EV before the next trip
• UserChargeNeed– calculated energy needs for the customer’s vehicle to perform the trip
planned in the customer’s request
• ChargeProposition– data structure with a list of EVSEs and offered charging profiles that can cover
the customer’s request
• ChargePropositionDetail– one offered charging profile and cost
• PropositionReservationRequest
• VariableOffers– information relevant to the electricity grid, i.e. available power, maximum
energy and price for charging per day and time in a specific area
NeMo, meeting/event title, Venue 10
![Page 11: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/11.jpg)
Examples
ATTRIBUTE DEFINITION INST. M/O Format
eMAID eMobility Account Identifier, as in ISO/IEC 15118. 1 M string
RequestID This is a unique identifier of the request 1 M string
Trip This is the description of the planned next trip 1 M complex “Trip”
Vehicle This is a reference to the description of the vehicle. 1 O complex
“Vehicle”
VehicleLoad This is the expected vehicle load (in kg) during the
next trip.
1 O double
NeMo, meeting/event title, Venue 11
UserMobilityNeed
![Page 12: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/12.jpg)
Examples
ATTRIBUTE DEFINITION INST. M/O Format
eMAID eMobility Account Identifier, as in ISO/IEC 15118. 1 M string
RequestID This is a unique identifier of the request 1 M string
Trip This is the description of the planned next trip 1 M complex “Trip”
Vehicle This is a reference to the description of the vehicle. 1 O complex
“Vehicle”
VehicleLoad This is the expected vehicle load (in kg) during the
next trip.
1 O double
NeMo, meeting/event title, Venue 12
ATTRIBUTE DEFINITION INST. M/O Format
eMAID eMobility Account Identifier, as in ISO/IEC 15118. 1 M string
RequestID This is a unique identifier of the request 1 M string
ItinerarySections The list of itinerary sections that comprise the
next trip
n M List of complex
“ItinerarySection”
Vehicle This is a reference to the description of the
vehicle.
1 O complex “Vehicle”
ItineraryEnergyNeed This is a list of the energy need (in kWh) of the
vehicle at the start of each itinerary section in
order to complete the next itinerary section
n M List of double
TripEnergyNeed This is the total energy need (in kWh) of the
vehicle in order to complete the next trip
1 M double
UserChargeNeed
![Page 13: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/13.jpg)
Marketplace Business Objects
• ServiceContract– signed between two entities
• ContractSection
• Terms
• BusinessPartner
• BusinessPartnerInformation
• AdditionalID
• Service– semantic service description exists within an OWL-S description that is
referenced from the Object
• Category– hierarchy allowing to navigate through the service catalogue
• ServiceContractOffering
NeMo, meeting/event title, Venue 13
![Page 14: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/14.jpg)
User Business Objects
• User
• UserProfile
– Preferences, history, recurrent places and trips
• UserChargingPreferences
• UserDrivingPreferences
• UserAgenda
NeMo, meeting/event title, Venue 14
![Page 15: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/15.jpg)
eMobility Reporting Business
Objects
• GetLoadReport
– data structure sent by an authority or energy retailer,
to get the list of CDRs and the energy delivered per
EVSE for a specific time period
• CPOLoadReport
• LoadDetails
• AreaLoadReport
• PoDDemand
– energy demand per DSO fiscal smart meter with time
NeMo, meeting/event title, Venue 15
![Page 16: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/16.jpg)
Vehicle preparation Business
Objects
• FleetMobilityNeed
• VehiclePredictedEnergyNeed
• PreconditioningProfile
– notifications for the preparation of vehicle
functionalities
• VehicleFunctionNotification
NeMo, meeting/event title, Venue 16
![Page 17: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/17.jpg)
EV Charging infrastructure
Business Objects
• Update of eMI3 specifications
• ChargingConnector
• EVSE (or Charging Point) can charge one EV at
a time
• ChargingStation, is a physical object with a
User Interface
• ChargingPool, one or more Charging Stations
operated by one CPO
NeMo, meeting/event title, Venue 17
![Page 18: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/18.jpg)
Support Objects
• AddressInfo
• AdminState
• Appointment
• Contact
• CostOffer
• ChargingProfile
• ChargingProfilePeriod
• CPO
• EnergyTime
• GeoCoordinate
• ItinerarySection
• LocationInfo
NeMo, meeting/event title, Venue 18
OpenHours
OperationalState
ParkingInfo
PowerTime
RecurrentUserPlace
RecurrentUserTrip
TimeFrequency
TimePeriod
Trip
UserComments
![Page 19: NEMOCOMMON INFORMATION MODELS - nemo …nemo-emobility.eu/wp-content/uploads/sites/10/2017/11/2017-NeMo-S… · – Used the template of the eMi3 ... • Data translators will enable](https://reader031.vdocument.in/reader031/viewer/2022030422/5aaa48b57f8b9a72188e0674/html5/thumbnails/19.jpg)
Conclusion
1912 October 2017 NeMo Stakeholder Forum Conference, Ehningen (Stuttgart)
• Common Information Models for electromobility business objects
• CIM will be updated as necessary during the project developments
• New services will generate and exchange data according to the CIM
• Data translators will enable the translation of data to the NeMo
CIM
• Interoperability of electromobility services
Data Translators
and Interfaces
Service Creation
and Provision
open
European Inter-Roaming
protocol
Common Information Models