Pathways and space in support of loT

 

The adopted changes to the Building Code of Australia appear not to address adequate pathways and space requirements for future deployment of Internet of Things technologies nor have a common carrier lead-in requirement.

 

The common carrier lead-in requirement may well be addressed in the next addition, if supported by industry as the cost variation of delivery on a new build will not be significant from the current practices and may well be reduced if a common requirement is established for each building type.

 

The emerging issue appears to relate to buildings under construction and their ability to accommodate deployment of Internet of things devices after construction.

 

At this stage it is unlikely to see the building code addressing IoT pathways and spaces within building code without cost modelling to support its inclusion. Given IoT technology is rapidly changing and there is not one specific deployment model agreed, a positive price modelling in the near future is unlikely. Buildings planned and built today may not cater for IoT deployment in 2025 without substantial investment.

 

IoT appears to be a high priority for government with industry projection of IoT having an opportunity for the Australian economy of up to AUD$120 billion by 2025.

 

International Standardisation on physical layer continues to address IoT related issues with ISO/IEC 11801 -Generic Cabling for Customer premises reaching FDIS Final Draft International standard- (no technical changes to be considered) in support of an international movement to embrace distributed services which is evident in:

 

·       Extending its coverage in some ISO/IEC 11801 supported deployment types from 2,000 m to 10,000m.

 

·       the inclusion of distributed services as part of ISO/IEC11801 series which includes a defined interface between generic and system cabling including WAP’s.

 

·       IEEE 802.3 working group looking at Ethernet on twisted pair to 1,000 m.

 

·       Remote powering to 95-100 watts over telecommunication cabling.

 

Irrespective of the success of any IoT technology, its associated market share and live expectancy there is a fundamental requirement to get communications and power to all IoT devices.

 

The deployment of adequate pathways and spaces to support IoT deployment will help protect the inherit value of the building over its projected life cycle and insure that a building remains fit for purpose.

 

The newly published

 

AS/NZS 3084:2017 Telecommunications installations - Telecommunications pathways and spaces for commercial buildings along with

 

AS/NZ ISO/IEC 14763.2 Information technology - Implementation and operation of customer premises cabling Planning and installation

 

provides requirements and recommendation of minimum spatial requirements along with pathways and other requirements however it should be noted that ensuring that a building is IoT ready may well require more than compliance to the standards.

 

Inadequate Pathways and spaces for IoT deployment within a building may well be the determining factor for limiting the inherit value and its longevity of a building irrespective of its use.

 

Recommendation

 

If you believe the IoT will be transformational than specify adequate pathways and spaces to accommodate IoT deployment within the building.

 

If you believe IoT is not going to be transformational than specify adequate pathways and spaces accordingly.

 

However, in both cases consider the impact if your assessment was flawed.

 

Ideally a code of practice/standard will be developed by industry to address pathways and spaces requirements for IoT beyond the network boundary which may also need to address requirements beyond the property boundary. The recommendation not adopted by the Building code on this matter may well be a good starting point for this document.

 

http://www.iot.org.au/ provides information regarding IoT.

© 2017 VTI Services | ABN 18 060 154 421 | Phone +61 2 9824 2412Site design by Codfish Design | Development, CMS and Data Processing by Behind the Page