Open APIs

TMF 646 Apointment Status Model

  • 1.  TMF 646 Apointment Status Model

    TM Forum Member
    Posted May 27, 2020 12:43
    Hi all,

    another question concerning the Apointment TMF 646, this time with respect to the Lifecycle of the appointment.

    First, it would be nice to add some paragraphs desribing the intention of each state.
    Second, we are confused by the state transition from "Confirmed" to "Final". This means that all but one state are final states and that (if we take the decision node "Take place?" into account) it is possible that an appointment neither takes place nor does not take place.
    Shouldn't an appoint always either take place  or not take place?

    Or is it meant the following way:

    1. The appointment takes place and is successful ("Completed") or unsucessful ("Failed").
    2. The appointment never takes place (the technician never went to the customer, the technician never called, etc.)

    But if it is meant this way, shouldn't there be another state, say "Not kept" and a transition from "Confirmed" to this new state which is then a final state?
    I know that this can also be achieved by comparing the end date to the current date (i.e. implicitly the appointment is in state "Not kept" if it is in state "Confirmed" and the current date is greater thant the end date), but having this explictily would be much easier.

    We were also wondering about the meaning of the state "Initialized", maybe someone could explain this one too. I suspect this is just a temporary state.

    Thanks for all help received.

    Markus Wolf
    T-Systems International Services GmbH