Open APIs

 View Only

  • 1.  Parameters in the Service Ordering API

    Posted Feb 06, 2017 04:54
    Hi,

    I have a question about ordering APIs in SID, especially about the Service Ordering API.

    From my understanding, a service order will lead to the corresponding service instantiation after some order parameters checking.  Indeed, it seems logical to me that a service order contains parameters corresponding to the service specification characteristics.  However, in the service ordering API there is no mention of such parameters. A ServiceOrderItem is directly connected to an instance or a specification.

    I first thought that an order systematically implies an instantiation so that the parameters are stored. In this case, the instance would have an initial state that means it needs to be checked. It works for the add action of the service order item but not the modify action.

    So, I'd like to have your view on this.

    You'll the service order class diagram in the Service Ordering API.

    Thanks.

    ------------------------------
    Angely Dufour
    e-téra
    ------------------------------


  • 2.  RE: Parameters in the Service Ordering API

    Posted Feb 07, 2017 08:32
    Good afternoon,

    please find some elements below related to your 2 questions.

    1. The values of the service parameters are indeed part of the Service ordering API as you can see in the example page 18 under Service Characteristics:
    "serviceCharacteristic":[
    {
    "name":"Colour",
    "value":"White"
    },
    {
    "name":"Memory",
    "value":"16"

    2. If you look at the service state model page 12, you see that the state "feasibility checked" applies both to creation (arrow comes from initial) and to changes (amend:modify loop on the schema) e.g. I can change the color value attribute from "White" to "Black".

    With Best regards          Jean-Louis

    ------------------------------
    Jean-Louis BAILLY
    Orange
    ------------------------------

    Original Message


  • 3.  RE: Parameters in the Service Ordering API

    Posted Feb 08, 2017 08:22
    Hi,

    Thanks for your help.

    1. The values of the service parameters are indeed part of the Service ordering API as you can see in the example page 18 under Service Characteristics

    Yes but more precisely my question is: where these parameters are stored in the SID model?

    Because I could neither find the appropriate classes on the API document nor in some other SID documents (such as business interaction).

    Now, If you look at the class diagram page 9, a ServiceOrderItem references a Service (that is, an instance) that references some ServiceCharacteristic. From my understanding, these values are not order parameters but instance-specific characteristics values.


    ------------------------------
    Angely Dufour
    e-téra
    ------------------------------

    Original Message


  • 4.  RE: Parameters in the Service Ordering API

    Posted Feb 09, 2017 11:16
    Good afternoon,

    in the SID model R16.5 Excel format,  this is described in the "service domain" sheet,
    in the service ABE, see row 51 entity name = ServiceCharacteristicValue

    A ServiceCharacteristicValue object is used to define a set of attributes, each of which can be assigned to a corresponding set of attributes in a ServiceCharacteristic object. The values of the attributes in the ServiceCharacteristicValue object describe the values of the attributes that a corresponding ServiceCharacteristic object can take on

    This is where this information comes from.

    With Best Regards        Jean-Louis



    ------------------------------
    Jean-Louis BAILLY
    Orange
    ------------------------------

    Original Message


  • 5.  RE: Parameters in the Service Ordering API

    Posted Feb 10, 2017 07:32
    Hi,

    Well, I don't think it is related to order parameters at all.

    Indeed, a ServiceSpecification has some CharacteristicSpec that references some CharacteristicSpecValue (domain values). A ServiceCharacteristicValue, as you mentioned, represents a service instance-specific characteristic value. But as this stage, the instantiation has already been done and the characteristics values have already been allocated.

    My question concerns the step before instantiating the service. Like in any ticket system, you emit an issue with a description or better, with some parameters related to the requested service. These parameters have to be stored in the data model before the actual instantiation of the corresponding service.

    Regards,

    ------------------------------
    Angely Dufour
    e-téra
    ------------------------------

    Original Message


  • 6.  RE: Parameters in the Service Ordering API

    Posted Feb 13, 2017 07:22
    Good morning,

    it is both :
    • add :you can use the SO for creating a new service (in this case the installed base is empty) and you indicate in the SO all parameters of the new service you want to create.

    • modify : you can use the SO for updating an existing service (in this case the installed base already contains a service instance will all attributes already valued) and you indicate in the SO the values you want to update and the ID of the existing service you want to modify.

    For example the color was "black" and you want to update to "white" ; then depending on the order processing success or failure, the installed base will be updated or not : you will have a transition from "black" to "white" (or not) triggered by the SO on the service instance you designate in the SO.

    With Best Regards     Jean-Louis

    ------------------------------
    Jean-Louis BAILLY
    Orange
    ------------------------------

    Original Message


Related Content