TM Forum Community

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

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

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

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