EiDelivery is basically a request to a meter at an EMIXInterface, or to a data service hosting the meter data. The request is for the energy delivered for in each measurement interval during a request interval. The requestorParty is any authorized Party. The MarketContext will specify the measurement interval duration, units, injection Boolean, etc. Effectively, the payload for each measurement interval will be MarketContextUID, StartTime, and Quantity
It would seem that the only two services required are EIRequestDelivery and EiReplyDelivery. The current spec uses EiCreateDelivery and EiCreatedDeliver which is confusing.
If we think of CreateDelivery as creating the delivery record in memory it the meter or in a database, then CreateDelivery is out of scope, I assume.
Having reviewed the application of the simplified report structure and its use of streams, I can see no benefit and perhaps complexity and cost to that structure over EMIXBase for this application. Also since EiReport is new, I suggest we use EMIXBase for EiDelivery. EiReport can still be used by practitioners if it meets their needs for delivery information.
Note the UML Diagrams for EiDelivery are out of date.