Field name (portal): (no equivalent field) XML Tag name: MDFSiteID A combination of CSS exchange and district code. To which an existing line is attached or to which a new line is likely to be attached. e.g. WWNABB. Data may not be fully up-to-date due to: Delay in the data refresh for new orders or network This value is updated 48 hours after a valid provide order is complete. This would be refreshed on a monthly basis in case of any change to the exchange data. Field name (portal): PCP Id XML Tag name: PCPId Primary Cross-connection Point (cabinet) Identifier for an existing line or the designed PCP for an address. Delay in the data refresh for new orders or network This value is updated 48 hours after a valid provide order is complete. This would be refreshed on a monthly basis in case of any change to the exchange data. Field name (portal): FCP Id XML Tag name: FCPId Fibre Connection Point Identifier Currently not is use, reserved for future use. This parameter is currently reserved for future use.
Field name (portal): BT Post Code XML Tag name: RecordedPostCode The postcode that BT has associated with the line. This may be different from the postcode currently registered with the Post Office. Data may not be fully up to date due to: in the data refresh for new orders. Postcodes not available for new sites. This value is updated 48 hours after a valid provide order is complete. This would be refreshed on a monthly basis in case of any change to the post code data. Field name (portal): DP Number XML Tag name: DP The Distribution Point from which the line is served. Data may be not be fully up to date due to: Delay in the data refresh for new orders. This value is updated 48 hours after a valid provide order is complete. This would be refreshed on a monthly basis in case of any change to the DP data.
Field name (portal): ANFP Category XML Tag name: ANFPCategory The ANFP category given to the existing line or which will be given to any new line: U: short X: Extra short S: Short M: Medium L: Long This is defined in the Access Network Frequency Plan as the Categorisation of customer’s location in terms of electrical distance from the MDF, defined by loss values at 100 kHz, for a nominal line to the MDF. Data may not be fully up-to-date due to: Delays in the data refresh for new orders. Inconsistencies in measurement of Line Loss, Capacitance or line length. This value is updated 48 hours after a valid provide order is complete. This would be refreshed on a monthly basis in case of any change to the line data. Field name (portal): Circuit Line Length Estimate XML Tag name: CircuitLineLengthEstimate An estimate of the length (in metres) of the circuit (line) from the Exchange, calculated as follows: When existing line length records cover all segments from the exchange to the DP, their lengths are added. When multiple cables connect the same two points, the longest (worst-case) route is used. The distance from the DP is calculated using the grid reference of customers premise postcode and a pseudo grid-reference of the DP. The pseudo grid-reference of the DP This value is updated 48 hours after a valid provide order is complete. This be refreshed on a monthly basis in case of any change to the line length.
Field name (portal): A – Earth Capacitance XML Tag name: AECapacitance Capacitance between leg A and in nanofarads – this is measured on a new provide and updated monthly subject to line conditions. Only populated for line based checks. This is not applicable for MPF lines. Data may not be fully up to date due to: in the data refresh for new orders. Line test not performed/failures. Presence of DACS/TPON. DN excluded from routine testing. This value is normally updated 48 hours after a valid provide order is complete. However in some circumstances this value could take up to 2 weeks to appear on eMLC. This value will also be updated as part of the weekly data refresh. Field name (portal): B – Earth Capacitance XML Tag name: BECapacitance Capacitance between leg B and earth in nanofarads – this is measured on a new provide and updated monthly subject to line conditions. Only populated for line based checks. This is not applicable for MPF Data may not be up to date due to: Delay in the data refresh for new orders. Line test not performed/ failures. Presence of DACS/ TPON. DN excluded from routine testing. This value is normally updated 48 hours after a valid provide order is complete. However in some circumstances this value could take up to 2 weeks to appear on eMLC. This value will also be updated as part of the weekly data refresh.
This is being extracted in real time during the eMLC call. name (portal): PSTN Tie Cable ID XML Tag name: PSTNTieCableID This information represents the designation of the LLUL tie cable and is only returned if you own it, helping you to identify left-in jumpers. This is only returned if you own the tie cable while requesting the line characteristics check. This value is being extracted in real time during the eMLC call. Real time from master records Field name (portal): PSTN Tie Pair Number XML Tag name: PSTNTiePairNumber This is the actual pair within the LLUL to which the circuit is assigned. This is only retuned if you own the tie cable while requesting the line characteristics check. This value is being extracted in real time during the eMLC call. Real time from master records Field name : BET Enabled XML Tag name: BETEnabled BET data On an LLU SMPF or ALL Product call if the line loss is greater than the BET threshold or blank, for example 55db, then this flag indicates whether the line or local exchange is enabled for BET or not. Y – Exchange enabled and line has passed prequalification. R – Exchange enabled and line failed prequalification. E – Exchange enabled for BET. N – Exchange is not enabled for BET This is only present if the above BET threshold is crossed. NA name : BET data NA
Field name : ONT Serial Number XML Tag name: ONTSerialNumber For FTTP open orders: This would indicate the serial number of the ONT the order is against. This would be returned on eMLC response only if the requested product is LLU SMPF, LLU MPF, Generic Ethernet Access or All. This value is being extracted in real time during the eMLC call. Real time from master records Field name : ONT Port Number XML Tag name: PortNumber For FTTP open orders: This indicate the port number that the order is against. For example: 1 This would be returned on eMLC response only if the requested product is LLU SMPF, LLU MPF, Generic Ethernet Access or All Products. This value is being extracted in real time during the eMLC call. Real time from master records name : ONT Port type XML Tag name: PortType For FTTP open orders: This would indicate the port type that the order is against. For example: Data or Voice This would be returned on eMLC response only if the requested product is LLU SMPF, LLU MPF, Generic Ethernet Access or All Products. This value is being extracted in real time during the eMLC call. Real time from master records Field name : Fault type For open faults: Real time from master records
Field name : Compatibility Indicator XML Tag name: CompatablityIndiacator This would indicate the compatibility of the requested service to be provided on the line. This value is being derived in real time during the eMLC call. See Appendix B for values. NA Technology Code fields Field name : Technology code XML Tag name: TechnologyCode This is the code to identify a technology associated with the installation. This value is being derived in real time during the eMLC call. See Appendix B for values. There can be more than one code and supporting text returned. e.g. M – MPF LLU Installation G – Generic Ethernet Access NA Field name : Technology text XML Tag name: TechnologyText This is the text associated with technology code. This is being derived in real time during the eMLC call. There can be more than one code and supporting text returned. e.g. M – MPF LLU Installation G – Generic Ethernet Access NA
18/2 SIM Availability XML Tag name: Bandwidth18x2SIMAvailable This holds one of two values: Y – The line meets the criteria for the GEA-FTTC 18/2 SIM Product to be ordered. N – The line does not meet the criteria for the GEA-FTTC 18/2 SIM Product to be ordered. SOGEA Availability Fields Field name : SOGEA (VDSL) Availability XML Tag name: SOGEA data At a line, DP and Address This holds one of these values Y – A SOGEA VDSL order can be placed. GEA-FTTC Infrastructure is in place and a downstream speed equal to, or above, the published threshold is achievable S – A SOGEA VDSL order cannot be placed. SOGEA Infrastructure is in place, but a downstream speed equal to, or above, the published threshold is not achievable P – A SOGEA VDSL order cannot be placed. SOGEA Infrastructure is planned and some early details known. N – A new SOGEA VDSL order cannot be placed. Either no current NA
PCP is enabled and PCP RFS dates are present. name : B Top Downstream Bandwidth: XML Tag name: VDSL data Speed predictions shown as a speed range. This represents the top downstream BW estimate for range B Returned on DN (line) and Address enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Range B Bottom Downstream Bandwidth: XML Tag name: VDSL data Speed predictions shown as a speed range. This represents the bottom downstream BW estimate for range B Returned on DN (line) and Address enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and
PCP RFS dates are present. Field name : Range B Top Upstream Bandwidth: XML Tag name: VDSL data Speed predictions shown as a speed range. This represents the top upstream BW estimate for range B Returned on DN (line) and Address based enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. name : B Bottom Upstream Bandwidth: XML Tag name: VDSL data Speed predictions shown as a speed range. This represents the bottom upstream BW estimate for range B Returned on DN (line) and Address based enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present.
name : Bandwidth Measure XML Tag name: VDSL data Indicates whether the is predicted or actual. Predicted speeds are based on cable records. Actual speeds are based on known HLOG based loss on the line or at the DP. Returned on line based and address enquires only. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. name : OHP District code XML Tag name: VDSL data A code identifying the CSS district code to which the VDSL fibre is attached – e.g. WW. OHP data will be blank if: No OHP data exists in the inventory system. DSLAM Port is yet to be connected logically with L2S port in the inventory system. Serving Cab is not being planned for VDSL. Available, as part of multi-day feed, after Inventory created. Field name : OHP Exchange Code XML Tag name: SOGEAVDSLAvailability/OHP/ ExchangeCode VDSL data A code identifying the CSS exchange code to which the VDSL fibre is attached – e.g. STB. OHP data will be blank if: No OHP data exists in the inventory system. Available, as part of feed, after Inventory created.
Returned on DN (line) and Address enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. loss is available at the DP This is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Range A Top Upstream Bandwidth: XML Tag name: G.fast data Speed predictions shown as a speed range. This represents the top upstream BW estimate for range A Returned on DN (line) and Address enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Range A Bottom Upstream Bandwidth: XML Tag name: G.fast data Speed predictions shown as a speed range. This represents the bottom upstream BW estimate for range A Returned on DN (line) and Address enquires only. Can be missing if: Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP
E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. This is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Range B Top Upstream Bandwidth: XML Tag name: G.fast data predictions shown as a speed range. This represents the top upstream BW estimate for range B Returned on DN (line) and Address based enquires only. Can be missing if: DP D-side data is not present. E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Range B Bottom Upstream Bandwidth: XML Tag name: G.fast data Speed predictions shown as a speed range. This represents the bottom upstream BW estimate for range B Returned on DN (line) and Address enquires only. Can be missing if: DP D-side data is not present. Available 48 hours after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP
E-side data is not available for CAL calculation for not a single line. CSS routing details are missing for all the lines. This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. Field name : Bandwidth Measure XML Tag name: G.fast data Indicates whether the is predicted or actual. Predicted speeds are based on cable records. Actual speeds are based on known HLOG based loss on the line or at the DP. Returned on line based and address enquires only. Available 48 after Copper order completion. Requires DP and E-side data to have been entered, or when measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Only displayed at a circuit level if the PCP is enabled and PCP RFS dates are present. name : OHP District code XML Tag name: G.fast data A code identifying the CSS district code to the G.fast fibre is attached – e.g. WW. OHP data will be blank if: No OHP data exists in the inventory system. Port is yet to be connected logically with L2S port in the inventory system. Serving Cab is not planned for VDSL. Available, as part of feed, after Inventory created.
Field name : FTTP Availability XML Tag name: FTTPAvailable GEA-FTTP data This holds one of these values Y – GEA-FTTP Infrastructure is in place Either ONTs already in place with spare ports or network infrastructure is in place with ready for service date today or in the past. D – GEA-FTTP Infrastructure is deduced and some details known. (not in current use) P – GEA-FTTP Infrastructure is planned and some details known. Potentially allow a pre-order to be placed. N – GEA-FTTP Infrastructure is not in place or currently there is no spare capacity. W - GEA-FTTP Infrastructure is in place, but there is currently no capacity for new orders. (No FTTP waiters list supported) Deduced flag gives an early indication of an area marked for GEA-FTTP (not in current use). NA Field name : only area products availability XML Tag name: GEA-FTTP data Indication of whether the “Fibre Only Area Products” are available at the identified location. NA
XML Tag name: ONTInstallLeadTime considering the TMA impact and ONT Install process Optional but will be populated alongside other FTTP data. Field name : ONT Install Process XML Tag name: ONTInstallProcess GEA-FTTP data This is derived from serving network notes and indicates number of stages/visits to be followed by engineer to perform ONT Installation at premise Optional field, but will be populated alongside other FTTP data. NA Field name : FTTP Available Date XML Tag name: AvailableDate GEA-FTTP data Tentative date by the network infrastructure will be available to install a new ONT on which FTTP and/or FVA service can be given. Ready for service date is only present when network is in planning stage hence FTTPAvailable or FVAAvailable = ‘N’/’P’/’D’ and there is a ready for service date recorded This field will be blank if: Any of the underlying RFS dates are blank. The RFS date is in the past and the GEA-FTTP infrastructure is enabled. NA Field name : FTTP OHP District code XML Tag name: DistrictCode GEA-FTTP data A code identifying the CSS district code to which the GEA-FTTP fibre is attached – e.g. WW. OHP data will be blank if: No OHP data exists in the inventory system. Available after inventory created as part of daily overnight feed. Field name : GEA-FTTP data Available after inventory created
FTTP OHP Exchange Code XML Tag name: OHPExchangeCode A code identifying the CSS exchange code to which the GEA-FTTP fibre is attached – e.g. STB. OHP data will be blank if: No OHP data exists in the inventory system. as part of daily overnight feed. Field name : FTTP OHP Exchange Name XML Tag name: OHPExchangeName GEA-FTTP data A code identifying the CSS exchange Name to the GEA-FTTP fibre is attached – e.g. St Albans. OHP data will be blank if: No OHP data exists in the inventory system. Available after inventory created as part of daily overnight feed. Field name : FTTP L2S XML Tag name: L2SId GEA-FTTP data The identifier of the L2S switch in the OHP exchange. This is the primary L2S ID identifying where a new ONT would be connected. L2S data will be blank if: No L2S data exists in the inventory system. Splitter node is not yet associated with IL2S. Available after inventory created as part of daily overnight feed. name : TMANoticeOrPermitRequired XML Tag name: TMANoticeOrPermitRequired GEA-FTTP data Identifies whether any one of network node (splitter, DP, manifold) falling under the traffic sensitive area. In order to perform engineering task, there is a need for traffic notice or permit to be obtained from concerned authority. Y/N Optional so can be blank. Available after inventory created as part of daily overnight feed. Field name : TMANoticeOrPermit GEA-FTTP data Identifies whether it’s a Notice or Permit required. Available after inventory created
XML Tag name: TMANoticeOrPermit Permit/Notice/Undetermined Optional field so can be blank. as part of daily overnight feed. Field name : Serving network notes XML Tag name: ServingNetworkNotes GEA-FTTP data Indicates the surveyor’s assessment during network rollout about the serving network at a particular location. Optional so can be blank. See Release specific Dialogue Service Data Items Enumeration List for values Available inventory created as part of daily overnight feed. Field name : Premise Type XML Tag name: PremisesType GEA-FTTP data Indicates the surveyor’s assessment during network rollout about the type of the premise at a particular location. Optional so can be blank. See Release specific Dialogue Service Data Items Enumeration List for values Available after inventory created as part of daily overnight feed. name : MDU Status XML Tag name: MDUstatus GEA-FTTP Data Shows the build status of the MDU infrastructure. See Release specific Dialogue Service Data Items Enumeration List for values Available after Inventory created as part of daily overnight feed. Field name : MDU for service date XML Tag name: MDUReadyForServiceDate GEA-FTTP Data If MDU infrastructure is planned, but not yet enabled this fields the Ready For Service date. This field will be blank if - No MDU infrastructure is planned Available after Inventory created as part of daily overnight feed.
Returned on postcode enquiries. Field name : Worst Bandwidth Measure XML Tag name: WorstBandwidthMeasure GEA-FTTC data Only applicable for post code calls Indicates whether the worst speed is predicted or actual. Predicted speeds are on cable records. Actual speeds are based on known HLOG based loss on the line or at the DP. Returned on postcode enquiries. First Available either 3 to 6 weeks after DP and E-side data has been entered, or once measured HLOG loss is available at the DP This value is refreshed on a monthly basis. Field name : FTTC Percentage Coverage XML Tag name: FTTCPercentageCoverage GEA-FTTC Data Postcode only response Gives the percentage of the postcode planned for GEA-FTTC This field will show 0% if no is planned for that postcode. Note: Relies on PMO updates Once planned, available after monthly load process by the PMO Field name : FTTP Percentage Coverage XML Tag name: FTTPPercentageCoverage GEA-FTTP Data Postcode only response the percentage of the postcode planned for GEA-FTTP This field will show 0% if no is planned for that postcode. Note: Relies on PMO updates Once planned, available monthly load process by the PMO Field name : No Coverage GEA-FTTP Data Postcode only response NA
XML Tag name: (No equivalent tag) Gives the percentage of the postcode with no planned coverage This is deduced from the FTTCPercentageCoverage and FTTPPercentageCoverage fields and displayed on the Portal only. GEA-FTTP On Demand fields Field name : FTTP On Demand available XML Tag name: FTTPOnDemandAvailable GEA-FTTP on demand data Indicates whether infrastructure is available to provide FTTP On Demand Service. Y - FTTC infrastructure should be available in the area and the Exchange should be enabled for FTTP on Demand. P - When FTTC infrastructure is planned in the area. N- When FTTC infrastructure is not available in the area or the Exchange is not enabled for FTTP on Demand. NA Field name : Ready For Service Date XML Tag name: ReadyForServiceDate GEA-FTTP on demand data Tentative date by which the FTTP on Demand network infrastructure will be available. This field will be blank if: Any of the underlying RFS dates are blank. Available after inventory created as part of daily overnight feed.
The RFS date is in the past and the GEA-FTTP infrastructure is enabled. name : OHP District code XML Tag name: DistrictCode GEA-FTTP on demand data A code identifying the CSS district code to which the GEA-FTTP fibre will be attached – e.g. WW. OHP data will be blank if: No OHP data exists in the inventory system. Available after inventory created as part of daily overnight feed. Field name : OHP Exchange Code XML Tag name: OHPExchangeCode GEA-FTTP on demand data A code identifying the CSS exchange code to which the GEA-FTTP fibre will be attached – e.g. STB. OHP data will be blank if: No OHP data exists in the inventory system. Available after inventory created as part of daily overnight feed. Field name : OHP Exchange Name XML Tag name: OHPExchangeName GEA-FTTP on demand data A code identifying the CSS exchange Name to which the GEA-FTTP fibre will be attached – e.g. St Albans. OHP data will be blank if: No OHP data exists in the inventory system. Available after inventory created as part of daily overnight feed. Service Information Field name (portal): CP Name XML tag name: Name The name of the contracted CP to whom Openreach provides the MPF or the SMPF service. Only provided where MPF or SMPF is active on the line. This value is updated 48 hours after a valid order is completed.
Field name (portal): CP contact number XML tag name: Telephone The contact number for the above contracted CP. Only provided where MPF or SMPF is active on the line. This value is updated 48 hours after a valid order is completed. name (portal): GEA CP Name XML tag name: Name The name of the contracted CP to whom Openreach provides the service. Only provided where is active on the line. This value is updated 48 hours after a valid order is completed. Field name (portal): GEA CP contact number XML tag name: Telephone The contact number for the contracted CP. Only provided where is active on the line. This value is updated 48 hours after a valid order is completed. name (portal): Line ID XML Tag name: AccessLineID Access Line ID – this is a unique line identifier. This value is being extracted in real time during the eMLC call. Real time from master records Field name (portal): Line Status XML Tag name: AccesLineStatus The line status of the WLR/LLU service values are ‘stopped’ or ‘working’ Real time from master records Field name (portal): Line Status (VDSL) XML Tag name: The line status of the VDSL service values are blank, ‘stopped’ or ‘working’ Real time from master records
service and is not a DN on the BT network. N SLU SMPF A line that has the SLU SMPF product on it. The SMPF part is unbundled the cabinet and tied across to the SLU CPs cabinet. The voice part is brought back to re-join its original path to the exchange. For SMPF orders, the customer needs to approach their new broadband supplier and place a migration order. For MPF the migration will convert the voice service to MPF and will automatically remove the SLU SMPF. For full details see new process for SLU to LLU transfers. O SOGEA The line being queried has a GEA connection (SOGEA). A line that already has a GEA SOGEA service on it cannot additionally support SMPF, MPF or FTTC. A controlled migration order is the only way to avoid creating a tag issue. R BBR This line has BBR – Broadband Repeater Technology. This technology improves ADSL (SMPF and MPF) performance. S SLU MPF A line that has the SLU MPF product on it. Fully unbundled at the cabinet and tied across to the SLU CPs cabinet. Place the LLU order and this will result in the AoT message to be sent to the losing CP. For full details see new process for SLU to LLU transfers. T TPON TPON is a fibre optic network that is used in certain parts of the country. TPON cannot support MPF or SMPF products. However if a suitable copper cable exists at the site overlaying the fibre then the service could be transferred to the copper network overcoming the incompatibility problems. Orders for LLU will be accepted on TPON lines and a manual check will be made for a copper overlay. Customers should be warned that the check will delay the process and that there is a significant chance that no overlay will be found and the order will then be rejected. V Featurenet Featurenet is a product sold by BT to businesses. It connects multiple lines together into a single virtual network. The only option in this instance is for the customer to contact the provider of the Featurenet and request that it be removed and the line to revert to PSTN. Z Line clear The line appear to have no compatibility issues. A standard provision should be placed.
2154 Line ID not recognised format. The Line ID is not in the expected format. 2155 Only one identifier allowed. More than one identifier has been supplied. There should be either a Telephone Number or a Service ID or a Line ID. 2156 DP Identity not recognised format. The DP Identity fields are not in the expected format. They should comprise of an MDFSite ID and a DP number. 2157 Postcode not recognised format. The postcode is not in the expected format. 2158 Data cannot be returned for this Telephone Number. Data could not be returned for the Installation Directory Number (DN) given. 2159 Data cannot be returned for this Service ID. It has not been possible to return data for the service ID. 2160 Data cannot be returned for this Line ID. It has not been possible to return data for the given Line ID. 2161 Data cannot be returned for this DP Identity. It has not been possible to return data for the given DP Identity. 2162 Data cannot be returned for this postcode. Data couldn’t be returned for the postcode given. The postcode given may be: 1) A refrained postcode with no Openreach presence, or