TM Forum Community

 View Only
  • 1.  Characteristics of a site vs the address of site

    TM Forum Member
    Posted May 17, 2022 06:19
    Hi,

    I posted on this originally back in August last year but we are now just getting to thinking about the implementation of this and wanted to raise it again as there would seem to be a gap in the API specifications. What I'm interested in is defining things that are relevant to an address rather than the address itself, for example

    • Site restrictions - it's a secure site which has restrictions who can access or to contact before arriving
    • Hazard information - there are working at height requirements if accessing the property, or it's near water and needs specific equipment to work
    I can't see anything similar in either the previous or current APIs but these are a requirement for Openreach to be able to communicate with it's customers and partners to successfully deliver services and would like to see if a request to look at a formal specification in the APIs can be raised. Currently I'm thinking that a set of site characteristics with a specification file is the most extensible way to do it but I know from a comment by @Jonathan Goldberg last time he wasn't very much in favour of that, we could add specific sub-classes to the address such as "Hazards" and "SiteRestrictions" but then a tightly coupled solution requires API changes if we want to modify the details that are passed which I'd like to avoid too. Also, each region or country may have different requirements for their own site characteristics and end up with localised solutions which are non-conformant.​​
    #OpenDigitalArchitecture

    ------------------------------
    Steve Ranford-Bragg
    BT Group plc
    ------------------------------


  • 2.  RE: Characteristics of a site vs the address of site

    Posted May 18, 2022 03:22
    Hi Steve,

    In my humble opinion, site restrictions & hazards are not related to the address but to the site (related to the address and vice & versa). We traditionally add a "Site access" form that encloses every attribute such as where, how, and when to access.
    Do not hesitate to ping me on LinkedIn if you need any details...I also happen to be in London today & tomorrow if you want to meet shortly.

    Best reg,

    Jerome

    ------------------------------
    Jerome PERRET
    IT-Development
    ------------------------------



  • 3.  RE: Characteristics of a site vs the address of site

    TM Forum Member
    Posted May 18, 2022 04:50
    Hi,

    That's a fair point but there is no linkage currently from site to address with the address API. The site model does not have a lot of properties currently (status, place, relatedParty, relationship and a few more) so there currently isn't anywhere to store them there either.

    Taking your point then what I'm considering is extending the address API so that it has a link to a site which then can have characteristics and those characteristics have a specification to define them, in that way you can fetch the characteristics of a site with an address without the need to make two calls but also if the site API is used more later it could also be fetched there too.

    ------------------------------
    Steve Ranford-Bragg
    BT Group plc
    ------------------------------