TM Forum Community

Expand all | Collapse all

TMF674 - storing characteristics of a site

  • 1.  TMF674 - storing characteristics of a site

    TM Forum Member
    Posted Aug 03, 2021 06:46

    Hi

    We're looking at registering sites following a survey as part of the deployment of fibre and in some cases we need to register them as a multi dwelling unit (say a block of flats)  with their associated owning and management companies, contacts etc. These all seem to fit fairly well into the TMF674 Geographic site, but there are additional things which are required to be stored such as details of the asbestos register, any wayleaves (permissions from the landowner to our equipment on their property) etc which don't seem to have an equivalent in any of the addressing APIs.

    We could just sub-class and extend with specific attributes but that seems very clumsy and doesn't group them together logically and I would have thought that the ability to store multiple different characteristics of "things" against a site would be general use – for example, a site may have hazards recorded against it (flat roof, restricted access, near water), specific security restrictions for access etc – and wondered if anyone had come across this issue yet and how it was solved?

    Thanks


    #OpenDigitalArchitecture

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


  • 2.  RE: TMF674 - storing characteristics of a site

    TM Forum Member
    Posted Aug 03, 2021 08:00
    Hi Steve
    I would think very hard, and then go away and think again, before using characteristics.
    The problem with unrestricted characteristics is that they are basically a bit bucket and a loosening of a contract between provider and consumer.
    If you had a corresponding characteristic specification, that limits the characteristics, you could perhaps do that.
    If specific jurisdictions, such as the UK, define or require specific information on sites, then a strongly-typed extension to site might be the preferred way to go.
    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: TMF674 - storing characteristics of a site

    TM Forum Member
    Posted Aug 03, 2021 08:15
    Thanks and I do agree that a unrestricted set of characteristics are not always a great idea, but my concern is that we have multiple groups of characteristics that need to be stored and strongly typing them would need a child class for each of them which could end up with a lot of additional classes and not be easy to make conformant. I would like to keep to being as conformant as possible and a more general class with characteristics would possibly make that easier?


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



  • 4.  RE: TMF674 - storing characteristics of a site

    TM Forum Member
    Posted Aug 03, 2021 08:25
    And meant to add that it would be a re-usable solution with could be used by others if adopted. I have to think that others would require the same capability to store details of things at a site?

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