44
Interface Functional Specification ManageServiceQualification Industry Interface NBN CO OSS PROGRAM This document forms part of NBN Co's Wholesale Broadband Agreement, which is a Standard Form of Access Agreement for the purposes of Part XIC of the Competition and Consumer Act 2010.

Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

  • Upload
    others

  • View
    5

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

Interface Functional Specification ManageServiceQualificationIndustry InterfaceNBN CO OSS PROGRAM

This document forms part of NBN Co's Wholesale Broadband Agreement, which is a Standard Form of Access Agreement for the purposes of Part XIC of the Competition and Consumer Act 2010.

Page 2: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 2 of 44

Copyright

This document is subject to copyright and must not be used except as permitted below or under the Copyright Act 1968 (Cth). You must not reproduce or publish this document in whole or in part for commercial gain without the prior written consent of NBN Co. You may reproduce and publish this document in whole or in part for educational or non-commercial purposes as approved by NBN Co in writing.

Copyright © 2012 NBN Co Limited. All rights reserved.

Disclaimer

This document predominantly sets out technical information in relation to NBN Co's B2B Gateway. It also sets out some of terms and conditions that apply in relation to NBN Co's B2B Gateway. Other terms and conditions in relation to NBN Co's B2B Gateway are set out elsewhere in the Wholesale Broadband Agreement between NBN Co and Access Seeker, including in the Product Description for the NBN Co Platform Interfacing Service and the NBN Co Operations Manual. Access Seeker is advised to familiarise itself with all of the terms and conditions that apply in relation to NBN Co's B2B Gateway, not just those terms and conditions set out in this document. Where NBN Co has provided recommendations or examples in this document, Access Seeker must not assume that NBN Co's networks, platforms or systems will support Access Seeker's implementation of such recommendations or examples. Information that is identified as important in this document is brought to Access Seeker's attention for practical purposes of understanding all information in context and should not necessary be accorded more weight than other information for implementation purposes.

Environment

NBN Co asks that you consider the environment before printing this document.

Page 3: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 3 of 44

Document Control

Title Interface Functional Specification: ManageServiceQualification

Revision HistoryVersion Date Details

V1.9 2012/04/06 First Release

V1.91 2012/08/29 Updated under Industry Interface 2.1.Updated touchpoint descriptions to:- clarify the use of DescribedBy and SpecifiedBy name/value pairs.- clarify the sequence of the specification blocks within a message.- clarify the behaviour of responseSingleSiteQualification touchpoint attributes 'ServiceabilityClass' and 'CSAID'.Updated sample messages to:- correct Transient IDs for NFAS/NWAS.- remove postcode from responses.

V2.0 2012/05/09 First draft for Industry Interface 3.0.Updated sample messages with Service Restoration SLA, Multicast and 2 UNI-Vs.

V2.1 2012/05/18 Updated sample messages with corrections.

V2.2 2012/06/11 Removed postcode from sample messages.

V2.3 2012/07/05 Updated touchpoint descriptions to:- clarify the use of DescribedBy and SpecifiedBy name/value pairs- clarify the sequence of the specification blocks within a message- clarify the behaviour of responseSingleSiteQualification touchpoint attributes 'ServiceabilityClass' and 'CSAID'

V2.4 2012/09/28 Updated sample messages to:- add Multicast to existing sample messages.- add Second UNI-V sample messages.- add Service Restoration SLA to existing sample messages.- removed VLAN Mode from order feasibility sample messages.- updated NTD Type and Location from External/Outdoor to Internal/Indoor.

Related DocumentsDocument Title Version

ManageServiceQualification Interface Technical Specification V2.4

Interface Common Objects Specification V1.6

Compare: Replace�
text
[Old text]: "Detailed" [New text]: "Version"The following text attributes were changed: font
Compare: Insert�
text
"Updated touchpoint"
Compare: Insert�
text
"2012/07/05"
Compare: Insert�
text
"V2.3"
Compare: Insert�
text
"Removed postcode from sample messages."
Compare: Insert�
text
"2012/06/11"
Compare: Insert�
text
"V2.2"
Compare: Insert�
text
"Updated sample messages with corrections."
Compare: Insert�
text
"2012/05/18"
Compare: Insert�
text
"V2.1"
Compare: Insert�
text
"Multicast and 2 UNI-Vs."
Compare: Insert�
text
"Updated sample messages with Service Restoration SLA,"
Compare: Insert�
text
"First draft for Industry Interface 3.0."
Compare: Insert�
text
"2012/05/09"
Compare: Insert�
text
"V2.0"
Compare: Insert�
text
"- remove postcode from responses."
Compare: Insert�
text
"- correct Transient IDs for NFAS/NWAS."
Compare: Insert�
text
"Updated sample messages to:"
Compare: Insert�
text
"touchpoint attributes 'ServiceabilityClass' and 'CSAID'."
Compare: Insert�
text
"- clarify the behaviour of responseSingleSiteQualification"
Compare: Insert�
text
"message."
Compare: Insert�
text
"- clarify the sequence of the specification blocks within a"
Compare: Insert�
text
"pairs."
Compare: Insert�
text
"- clarify the use of DescribedBy and SpecifiedBy name/value"
Compare: Insert�
text
"Updated touchpoint descriptions to:"
Compare: Insert�
text
"Updated under Industry Interface 2.1."
Compare: Insert�
text
"2012/08/29"
Compare: Insert�
text
"V1.91"
Compare: Insert�
text
"First Release"
Compare: Insert�
text
"2012/04/06"
Compare: Insert�
text
"V1.9"
Compare: Insert�
text
"Details"
Compare: Insert�
text
"Date"
Compare: Insert�
text
"to:"
Compare: Insert�
text
"- clarify the use of DescribedBy and SpecifiedBy name/value"
Compare: Insert�
text
"pairs"
Compare: Insert�
text
"- clarify the sequence"
Compare: Replace�
text
[Old text]: "changes can be found in" [New text]: "the specification blocks within a"
Compare: Insert�
text
"- clarify"
Compare: Insert�
text
"message"
Compare: Insert�
text
"behaviour of responseSingleSiteQualification"
Compare: Insert�
text
"touchpoint attributes 'ServiceabilityClass' and 'CSAID'"
Compare: Insert�
text
"V2.4"
Compare: Insert�
text
"2012/09/28"
Compare: Insert�
text
"Updated sample messages to:"
Compare: Insert�
text
"- add Multicast to existing sample messages."
Compare: Insert�
text
"- add Second UNI-V sample messages."
Compare: Insert�
text
"- add"
Compare: Replace�
text
[Old text]: "Design Change Log." [New text]: "Restoration SLA to existing sample messages."
Compare: Insert�
text
"- removed VLAN Mode from order feasibility sample messages."
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "- updated NTD Type and Location from External/Outdoor to"
Compare: Delete�
text
"Version"
Compare: Delete�
text
"Date2012/04/06"
Compare: Delete�
text
"First Release"
Compare: Replace�
text
[Old text]: "Details" [New text]: "Internal/Indoor."The following text attributes were changed: font
Compare: Insert�
text
"Version"
Compare: Insert�
text
"V2.4"
Compare: Insert�
text
"V1.6"
Compare: Delete�
text
"VersionV1.9V1.4"
Page 4: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 4 of 44

1. Introduction1.1 Purpose

The purpose of this document is to describe the service interface from a logical (functional) perspective.

1.2 ScopeThis document applies to: • The functional level interface description for the service• It details the service from a non-technical “black box” level to describe the service input and output

messages and concepts.

This document does NOT address: • Technical specifications, or physical design details of the service• Description of Functional and Non functional requirements

1.3 Target AudienceAudience Intended purpose

Business Stakeholder High-level understanding.Provide non-technical audience with a broad understanding of the service behaviour and constraints.

Project Team Project Planning.To support ongoing project planning.

Project Architects Project Architecture.To align other architectural views.

Nominated Reviewers Project Socialisation and Review.To understand service behaviour and constraints and to obtain objective feedback through the Peer Review & Ratification processes.

Integration Developers Input into detailed design.

Business Analysts Input into the Requirement Specification including service mapping documentation and schema designs.

Test Analysts High-level understanding & Next Phase.Provides a high level overview of the proposed service and used in conjunction with the System Requirement Specification, as input into their System Test documentation.

Service Consumer Stakeholders Input into detailed design and architecture for the systems consuming the service.

Service Provider Stakeholders Input into detailed design and architecture for the systems providing the service.

1.4 Document PrecedenceNBN Co’s Detailed B2B Specifications comprise a number of different documents. If there is any inconsistency between any of these documents, then that inconsistency will be resolved by giving precedence to the documents in the following order:1.The XSD, Product Definitions (XML), and the "NBN Co Product Attributes and Business Rules Matrix"2.The Interface Functional and Technical Specifications3.The Developer Guides and Message Examples

Page 5: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 5 of 44

2. Service DescriptionThe Manage Service Qualification interface includes mechanisms to determine serviceability of a location.Functions include:• Qualify whether or not a service can be ordered at a particular site (site qualification).• Determine if the product specified is serviceable at a particular site (order feasibility).

Page 6: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 6 of 44

2.1 Information ModelThis section describes the key entities and their relationships in the service schema represented as a class diagram.

Page 7: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 7 of 44

2.2. requestOrderFeasibilityCheck

Touchpoint DescriptionThis touchpoint is used to perform a check to see if a given product offering can be delivered to a specific location.When using this touchpoint, the Access Seeker can provide a valid NBN Location ID and Product Offering. They can also specify certain resources or services which should be used in the delivery of the product offering at the location.Validation RulesThis following validation rules apply to this operation. Failure to satisfy these validation rules can cause an input message to be rejected and the service invocation to result in an error.• Valid NBN Product Specification ID and Version must be provided in the request.• Valid Billing Account ID must be provided in the request.The touchpoint can be used to asses the feasibility of 'Connect' orders only.Characteristics• Non-Repudiable: No• Each request will be handled without regard to previous requests. If a duplicate request is received by the touchpoint, then this will be processed independently from the first

request. Each of the requests will result in a separate response.

Page 8: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 8 of 44

This section describes in detail all attributes required in the request message, including a description, type and any length/cardinality restrictions. The cardinality column reflects whether an attribute is mandatory in the request.

Name Description Type Cardinality

/ManageServiceQualificationRequest

serviceQualificationType This specifies the type of Service Qualification. Valid Values are: ProductOrder and ServiceQualification

string 1..1

ProductOrder Root element for Service Qualification Request - this contains details of the Location, Product and Appointment which will be used to determine the feasibility of the Order.

ProductOrder 1..1

/ManageServiceQualificationRequest/ProductOrder

AccessSeekerInteraction Contains the Access Seeker Order Correlation ID and/or Billing Account ID.

AccessSeekerInteraction 0..1

orderType The attribute contains the type of Product Order.Refer to the Appendix for a complete list of values for ProductOrder/orderType,V3.0.Length: 15

string 1..1

ProductOrderComprisedOf Access Seeker populates the Product Order with details of Appointment, Location and the Product to be Ordered

ProductOrderItem 1..1

AccessSeekerContact Access Seeker Contact Details. This contains the name and contact phone number of the contact person

AccessSeekerContact 0..1

/ManageServiceQualificationRequest/ProductOrder/AccessSeekerContact

contactName Access Seeker contact name string 0..1

contactPhone Access Seeker contact phone. string 0..1

/ManageServiceQualificationRequest/ProductOrder/AccessSeekerInteraction

ID Access Seeker Correlation ID.Length: 50

string 0..1

billingAccountID Access Seeker Billing Account Id.Length: 15

string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesLocation Contains the Location associated with this Product Order BusinessInteractionLocation 0..1

ItemInvolvesAppointment Contains the Appointment associated with this Product Order. Appointment 0..*

Page 9: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 9 of 44

ItemInvolvesProduct Contains Product Version and Product Specfication ID Product 1..1

ReferencesProductOrderItem An Instance of this contains details of the Product with its associated characteristics

ProductOrderItem 1..*

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment

activityNr A unique identifier for the Activity. Contains the appointment ID.

Length: 15

string 0..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocation

Place Specifies attributes associated with a location where the Product would be delivered

Place 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location ID. This only requires the NBN Location ID and not the complete location.Length: 15

string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Definition provided to Access Seeker by NBN Co during on-boarding.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedBy/Characteristic

ID Represents the name attribute in a name-value pair. string 1..1

type Represents the categorization of the name-value pair. string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy

ID Product Specification IDLength: 15

string 1..1

version Product Specification VersionLength: 6

string 1..1

type Product Specification Type string 1..1

category Product Specification Category string 1..1

Compare: Delete�
text
"Product"
Compare: Insert�
text
"Product"
Compare: Replace�
text
[Old text]: "/ManageServiceQualificationRequest/P" [New text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment"
Compare: Delete�
text
"roductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment"
Compare: Delete�
text
"/ManageServiceQualificationRequest/PPlace"
Compare: Replace�
text
[Old text]: "roductOrder/ProductOrderComprisedOf/ItemInvolvesLocation" [New text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocationPlace"
Compare: Insert�
text
"delivered"
Compare: Delete�
text
"delivered"
Compare: Delete�
text
"string"
Compare: Delete�
text
"1..1"
Compare: Insert�
text
"string"
Compare: Insert�
text
"1..1"
Compare: Delete�
text
"CharacteristicValue"
Compare: Delete�
text
"1..*"
Compare: Replace�
text
[Old text]: "Seekers" [New text]: "Seeker"
Compare: Insert�
text
"CharacteristicValue"
Compare: Insert�
text
"1..*"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedByvalueRepresents the value attribute in a name-value pair.CharacteristicThe associated quality or distinctive feature that defines an entity"
Compare: Replace�
text
[Old text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy" [New text]: "stringCharacteristic"The following text attributes were changed: size
Compare: Insert�
text
"1..11..1"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedBy/CharacteristicIDRepresents the name attribute in a name-value pair.stringtypeRepresents the categorization of the name-value pair.string"
Compare: Insert�
text
"1..11..1"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Insert�
text
"stringstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem"
Compare: Delete�
text
"actionAction being applied to the object."
Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..11..11..1"
Compare: Delete�
text
"Refer to the Appendix for a complete list of values for action,V3.0."
Compare: Delete�
text
"Length: 12"
Compare: Delete�
text
"ItemInvolvesProductContains characteristics associated with the Product. Please refer to"
Compare: Delete�
text
"Product"
Compare: Delete�
text
"Product Catalog for the compelete set of fields and structure that can be"
Compare: Delete�
text
"used here."
Compare: Delete�
text
"ReferencesProductOrderItemAn Instance of this contains an associated Sub-Product and its"
Compare: Delete�
text
"ProductOrderItem"
Compare: Delete�
text
"0..*"
Compare: Delete�
text
"characteristics."
Page 10: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 10 of 44

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesProduct Contains characteristics associated with the Product. Please refer to Product Catalog for the compelete set of fields and structure that can be used here.

Product 1..1

ReferencesProductOrderItem An Instance of this contains an associated Sub-Product and its characteristics.

ProductOrderItem 0..*

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Catalog.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy/Characteristic

ID Represents the name attribute in a name-value pair. string 1..1

type Represents the categorization of the name-value pair. string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedBy

ID Product Specification IDLength: 15

string 1..1

version Product Specification VersionLength: 6

string 1..1

type Product Specification Type string 1..1

Compare: Insert�
page
Matching page not found
Compare: Insert�
page
Matching page not found
Page 11: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 11 of 44

category Product Specification Category string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesProduct Contains characteristics associated with the Product. Please refer to Product Catalog for the compelete set of fields and structure that can be used here.

Product 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Definition provided to Access Seeker by NBN Co during on-boarding.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy/Characteristic

ID Represents the name attribute in a name-value pair. string 1..1

type Represents the categorization of the name-value pair. string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedBy

ID Product Specification IDLength: 15

string 1..1

version Product Specification VersionLength: 6

string 1..1

type Product Specification Type string 1..1

category Product Specification Category string 1..1

Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct"
Compare: Delete�
text
"DescribedByThis contains the name/value pairs which describe the Product. The valid CharacteristicValue"
Compare: Delete�
text
"1..*"
Compare: Delete�
text
"list and structure of name/value pairs are described in the Product Catalog."
Compare: Delete�
text
"SpecifiedByThis contains the Product Specification details.EntitySpecification"
Compare: Delete�
text
"1..1"
Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedBy"
Compare: Delete�
text
"IDProduct Specification IDstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"Length: 15"
Compare: Delete�
text
"versionProduct Specification Versionstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"Length: 6"
Compare: Delete�
text
"typeProduct Specification Typestring"
Compare: Delete�
text
"0..1"
Compare: Insert�
text
"1..1"
Compare: Delete�
text
"0..1"
Compare: Replace�
text
[Old text]: "Seekers" [New text]: "Seeker"
Compare: Insert�
text
"1..1/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedByvalueRepresents the value attribute in a name-value pair.string1..1CharacteristicCharacteristic1..1The associated quality or distinctive feature that defines an entity/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy/CharacteristicIDRepresents the name attribute in a name-value pair.string1..1typeRepresents the categorization of the name-value pair.string1..1/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedByIDProduct Specification IDstring1..1Length: 15versionProduct Specification Versionstring1..1Length: 6typeProduct Specification Typestring1..1categoryProduct Specification Categorystring"
Page 12: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 12 of 44

2.3. responseOrderFeasibilityCheck

Touchpoint DescriptionThis touchpoint will return details of the capability to deliver a Product to the specified location. It will include:• Service Qualification Status (Feasible; Feasible - Appointment Required; Feasible - Delayed; Rejected)• NTD Install Date (if it is known)• List of Shortfalls (if applicable)When the order is not feasible, the touchpoint will return a response with a qualification status of 'Rejected'. If the Access Seeker proceeds to submit the same order through the createOrder operation the order will be rejected again.Characteristics• Non-Repudiable: No

Page 13: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 13 of 44

Exception(Please refer to the Appendix for the exception codes and descriptions)

Description

invalidProductException Returned if an invalid Product has been specified in the request.

notAllowedException Returned if the Access Seeker is not allowed to perform the operation with the specified parameters.

technicalException Returned when a technical issue prevents the processing of the request. For example, the end application is unavailable.

validationException Returned when a validation issue prevents the processing of the request. For example, the message does not validate against the XSD and/or does not contain a mandatory field specified in the interface specification.

invalidAddressException Returned if an invalid Address has been specified in the request.

invalidOrderException Returned when the order being qualified is invalid.

accountHierarchyViolationException Returned when the optional Billing Account identifier is provided, but it does not belong to Access Seeker identifier.

accountNotActiveException Returned when an Access Seeker's account has a 'No-Sell flag' set (or) when billing account belonging to an Access Seeker is Inactive or Closed.

Page 14: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 14 of 44

This section describes in detail all attributes returned in the response message, including a description, type and any length/cardinality restrictions.Name Description Type Cardinality

/ManageServiceQualificationResponse

ServiceQualification Root element for Service Qualification detail response. ServiceQualification 1..1

/ManageServiceQualificationResponse/ServiceQualification

interactionStatus The resulting SQ status. One of:1. "Feasible": Order is feasible without Appointment OR Appointment specified is adequate.2. "Feasible - Appointment Required": Order is feasible however requires an Appointment to address Shortfalls.3. "Feasible - Delayed": Order is feasible however this is an NBN infrastructure shortfall.4. "Rejected": Order is not possible because either the Area is not Serviceable OR the Order is not valid (e.g. product not available, no capacity, invalid NTD/ CVC id's, specified attributes not correct for template. Essentially anything that could cause a rejection on order submission).

string 1..1

DescribedBy These name value pairs will be used to communicate the results of the order feasibility1. NTDInstallDate: Date in the future when an NTD will be installed. If NTD is already installed or there is no plan to install an NTD, no date will be returned. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ and the type field will be empty. It is not mandatory.2. NTD: The value will be either Yes OR No (indicating if there is a shortfall)and the type field will contain "Shortfall". It is not mandatory.3. LEADIN: The value will be either Yes OR No (indicating if there is a shortfall) and the type field will contain "Shortfall". It is not mandatory.4. NBNCOINFRASTRUCTURE: The value will be either Yes OR No (indicating if there is a shortfall) and the type field will contain "Shortfall". It is not mandatory.

CharacteristicValue 0..*

ServiceQualificationComprisedOf Contains further shortfall details ServiceQualificationItem 0..1

/ManageServiceQualificationResponse/ServiceQualification/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

Page 15: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 15 of 44

type This is used to classify the type of name-value pair. Valid Values are: Shortfall

string 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesAppointment Contains one or more Demand Types which are needed before an order can be fulfilled. This is returned if the interationStatus is "Feasible - Appointment Required"

Appointment 0..1

Note Contains the reason for rejection and Reason Code where required. Note 0..1

infrastructurePlannedDate Contains the date when NBN plans to overcome their infrastructure shortfall. This is returned if the interactionStatus is "Feasible - Delayed" and the infrastructure planned date is known.The format for date time is [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z (in UTC) e.g. 2011-06-23T12:00:00Z.Length: 20

dateTime 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment

ActivitySpec Contains one or more Demand Types ActivitySpec 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment/ActivitySpec

ActivitySpecificationReferences Contains demand type attribute ActivitySpec 1..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment/ActivitySpec/ActivitySpecificationReferences

type Demand Type, such as Standard Install.Refer to the Appendix for a complete list of values for ActivitySpecificationReferences/type,V3.0.

string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/Note

ID Reason CodeLength: 15

string 0..1

description Contains Reason for RejectionLength: 256

string 0..1

Page 16: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 16 of 44

2.4. requestSingleSiteQualification

Touchpoint DescriptionThis touchpoint is used to determine if a location is within the NBN Co service footprint (i.e. within an NBN serving area) and the type of access technology available at the location (i.e. Fibre, Wireless or Interim Satellite). It also provides infrastructure availability for the location (e.g. NTD Port/NNI availability) and Peak bandwidth availability. However, it does not validate if a specific product can be provisioned at a location - this function is provided by the requestOrderFeasibilityCheck touchpoint.This touchpoint accepts a location specified via one of the following:• NBN Location ID• NBN Physical Address details• Spatial Geocode (Latitude/Longitude)• GNAF IDIf the request does not result in the identification of a single NBN Location an exception will be returned.Validation RulesThis following validation rules apply to this touchpoint. Failure to satisfy these validation rules can cause an input message to be rejected and the service invocation to result in an error.• Provide a single valid NBN Location in the request.Characteristics• Non-Repudiable: No• Each request will be handled without regard to previous requests. If a duplicate request is received by the touchpoint, then this will be processed independently from the first

request. Each of the requests will result in a separate response.

Page 17: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 17 of 44

This section describes in detail all attributes required in the request message, including a description, type and any length/cardinality restrictions. The cardinality column reflects whether an attribute is mandatory in the request.

Name Description Type Cardinality

/ManageServiceQualificationRequest

serviceQualificationType This specifies the type of Service Qualification. Valid Values are: ProductOrder and ServiceQualification

string 1..1

ServiceQualification Root element for Service Qualification Request - this contains details of the location which will be used to determine the type of access technology available.

ServiceQualification 1..1

/ManageServiceQualificationRequest/ServiceQualification

ServiceQualificationComprisedOf Will have all detail used to perform the Site Qualification including the Location.

ServiceQualificationItem 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesLocation When using this operation, the Access Seeker must provide a valid Location details in form of one of the followingGNAF ID;Spatial Geocode (Latitude/Longitude);Full/Partial Australian Property Address;NBN Location ID;If the address details provided do not resolve to a unique NBN Location ID an exception will be returned.

BusinessInteractionLocation 1..1

type This specifies the type of the address provided. Valid values are: NBNPhysicalAddress, NBNLocationID, GNAFID, SpatialGeocode

string 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation

Place An Instance of Place to specifies Geocode and Physical Address associated with a location. If the Access Seeker wants to use GNAF ID, the Place object must be instantiated with the GNAF type (for example, Place@xsi:type=GNAF). The ID within Place is then used as the GNAF ID and it is mandatory

Place 0..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location ID.Length: 15

string 0..1

Geocode If Access Seeker needs to use Geocode details, this can be used Geocode 0..1

PhysicalAddress Physical address details of the location AustralianAddress 0..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/Geocode

Compare: Replace�
text
[Old text]: "species" [New text]: "specifies"
Page 18: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 18 of 44

latitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Latitudes south of the equator are expressed as a negative number, north of the equator as positive.Valid value range -8 to -45 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 1..1

longitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Longitudes east of Greenwich the equator are expressed as a positive number, west of Greenwich as negative.Valid value range 96 to 160 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/PhysicalAddress

secondaryComplexName Secondary Complex nameName associated with a building or area within a complex site.This data element may represent the name given to an entire building within an address site that has its own separate address.

Usage Examples:Biology Building B (Secondary Complex name - Building within a complex)20-24 Genetics Lane NorthBlamey Research Institute (Address site name - A complex)1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

Page 19: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 19 of 44

unitTypeCode Sub dwelling unit type code.Within a complex, an abbreviation used to distinguish the type of an address found within a building / sub-complex or marina.

Usage examples:Mrs Joyce CitizenApartment 7 (Sub-dwelling unit type code is APT)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

UnitTypeCode 0..1

unitNumber Sub-dwelling unit number.Within a complex, a number used to distinguish an address found within a building / sub-complex or marina.The data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7 (Sub dwelling unit number is 7)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

Page 20: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 20 of 44

levelTypeCode Level Type Code.Within a complex, an abbreviation used to distinguish the floor or level of a multi-storey building/sub-complex.

Usage Example:Apartment 7Level 3 (Level type code is L)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 20

LevelTypeCode 0..1

levelNumber Level Number.Within a complex, the number of the floor or level of a multi-storey building/sub-complexThe data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7Level 3 (Level number is 3)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

Page 21: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 21 of 44

complexRoadNumber1 Complex Road Number 1.Within a complex, identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 1 is 20)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

complexRoadNumber2 Complex Road Number 2.Within a complex, identifies the last number for a ranged address in the road or thoroughfare.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 2 is 24)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

Page 22: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 22 of 44

complexRoadName Complex Road Name.Within a complex, the name of the road /thoroughfare of the address.Within a Road name it is possible to find what appears to be a Road type (eg. The Boulevard).It is also possible to have a null Road type.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road name is Genetics)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

complexRoadTypeCode Complex road type codeWithin a complex, an abbreviation used to distinguish the type of road / thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane NorthBlamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

RoadTypeCode 0..1

Page 23: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 23 of 44

complexRoadSuffixCode Complex road suffix codeWithin a complex, an abbreviation representing the suffix of the road/thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road suffix code is N)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 20

RoadSuffixCode 0..1

addressSiteName Address Site NameSynonyms: Building property name, Primary Complex name

The official place name or culturally accepted common usage name for an address site, including the name of a building, homestead, building complex, agricultural property, park or unbounded address site.This data element represents the name given to an entire building or address site

Usage Examples:Parliament House (Name of the building)University of Melbourne (Site name of university campus - a complex)Happy Valley Retirement Village (Site name of gated property - a complex)Darwin Town Hall (Name of the building)Blue Hills Farm (Name of the property)

Length: 100

string 0..1

Page 24: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 24 of 44

lotNumber The Lot number is a reference number allocated to a property for subdivision administration purposes prior to road numbering.

Usage: Where an official Road number has not been assigned, this field may be used for postal purposes as well as the physical identification of an address site.

Length: 10

string 0..1

planNumber Plan NumberThe deposited plan number allocated to a property for subdivision administration purposes prior to road numbering in addition to the Lot number.

Length: 100

string 0..1

roadNumber1 Road Number 1.Identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.

Start of Range Number of the road e.g. 29 Archer Street, where roadNumber1 is 2921-25 Archer Street, where roadNumber1 is 2135A Archer Street, where roadNumber1 is 35A

Length: 10

string 0..1

Page 25: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 25 of 44

roadNumber2 Road Number 2.Identifies the last number for a ranged address in the road or thoroughfare.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.This data element is used for ranged street numbers otherwise it is left blank.End of Range Number of the street, e.g.21-25 Archer Street, where streetNumber2 is 2531-34A Archer Street, where roadNumber2 is 34A

Length: 10

string 0..1

roadName Road Name.The name of the road/thoroughfare applicable to the address site or complex.Only the road name should be stored in this data element.

Usage Examples:BROWNS ROAD WESTIn this case the Road name is BROWNS, the Road type is RD and the Road suffix is W

THE AVENUE WESTIn this case the Road name is THE AVENUE, the Road type is null and the Road suffix is W

COTSWOLD BRETTIn this case the Road Name is COTSWOLD BRETT and the Road type is null

HIGH STREET ROADIn this case the Road Name is HIGH STREET and the Road t type is RD.

Length: 100

string 1..1

Page 26: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 26 of 44

roadTypeCode Road Type Code.The abbreviation code used to distinguish the type of road/thoroughfare applicable to the address site/complex.

Usage example:23 Archer RD, where RD is the the Road Type code for Road

Length: 10

RoadTypeCode 0..1

roadSuffixCode Road Suffix CodeThe abbreviation code used to represent the suffix of road/thoroughfare applicable to the address site/complex.

20-24 Genetics Lane North, where North is the roadSuffix = N

Length: 20

RoadSuffixCode 0..1

localityName Locality Name.The name of the locality/suburb of the address.

Length: 50

string 1..1

postcode Postcode.The Australian numeric descriptor for a postal delivery area, aligned with locality, suburb or place

Length: 10

string 0..1

stateTerritoryCode State Territory Code.The State or Territory code of the address.

Length: 3

StateTerritoryCodeType 1..1

Page 27: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 27 of 44

2.5. responseSingleSiteQualification

Touchpoint DescriptionThis touchpoint will contain the results of a previously submitted Site Qualification request.If a single location was provided, the response can contain:• NBN Location ID;• Location Details (returned only if GNAF ID was not used to identify the location). These details include:• • GNAF ID;

• Spatial Geocode (Latitude/Longitude);• NBN Physical Address details

• Service Qualification Status (Servicable; Serviceable - Shortfall; Rejected)• Primary Access Technology (Fibre; Wireless; Interim Satellite)• Serviceability Class;• Serviceability Date; (if it is available)• CSA ID;• List of NTDs;Characteristics• Non-Repudiable: No

Exception(Please refer to the Appendix for the exception codes and descriptions)

Description

invalidAddressException Returned if an invalid Address has been specified in the request.

technicalException Returned when a technical issue prevents the processing of the request. For example, the end application is unavailable.

validationException Returned when a validation issue prevents the processing of the request. For example, the message does not validate against the XSD and/or does not contain a mandatory field specified in the interface specification.

Page 28: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 28 of 44

This section describes in detail all attributes returned in the response message, including a description, type and any length/cardinality restrictions.Name Description Type Cardinality

/ManageServiceQualificationResponse

ServiceQualification Root element for Service Qualification Response - this contains details of the location which will be used to determine the type of access technology available.

ServiceQualification 1..1

/ManageServiceQualificationResponse/ServiceQualification

interactionStatus The resulting SQ status. One of:"Serviceable": Location is serviceable now without shortfall."Serviceable - Shortfall": Location is serviceable now however there is a shortfall."Rejected": No services are currently available at the location.

string 1..1

ServiceQualificationComprisedOf Will have all detail such as location the Service Qualification test result ServiceQualificationItem 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesLocation One or more the following location details will be populated in this object :NBN Location ID;Location Type;Spatial Geocode (Latitude/Longitude);Australian Property Address;

BusinessInteractionLocation 1..1

ItemInvolvesProduct Represents attributes returned which are associated with the Product Product 1..1

ReferencesServiceQualificationItem An Instance of this represents attributes which are associated with the NTD and its specificationThis will be repeated for each NTD returned as part of the Site Qualification

ServiceQualificationItem 0..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation

Place Specifies attributes associated with a location Place 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location IDLength: 15

string 1..1

DescribedBy This contains name-value pairs used to hold Location related information.Following is the list of names and associated values:Region: Contains the Region which the address is located within. Valid values for this characteristic are: Urban, Major Rural, Minor Rural, Remote. It is not mandatory.

CharacteristicValue 0..1

Geocode Geocode details will be populated here. Geocode 0..1

PhysicalAddress Details of the Physical Address will be populated here. AustralianAddress 0..1

Page 29: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 29 of 44

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/Geocode

geographicDatum The geographicDatum is currently based on GDA94. This value "GDA94" will be returned.

Length: 10

string 0..1

latitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Latitudes south of the equator are expressed as a negative number, north of the equator as positive.Valid value range -8 to -45 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 0..1

longitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Longitudes east of Greenwich the equator are expressed as a positive number, west of Greenwich as negative.Valid value range 96 to 160 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/PhysicalAddress

Page 30: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 30 of 44

secondaryComplexName Secondary Complex nameName associated with a building or area within a complex site.This data element may represent the name given to an entire building within an address site that has its own separate address.

Usage Examples:Biology Building B (Secondary Complex name - Building within a complex)20-24 Genetics Lane NorthBlamey Research Institute (Address site name - A complex)1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

unitTypeCode Sub dwelling unit type code.Within a complex, an abbreviation used to distinguish the type of an address found within a building / sub-complex or marina.

Usage examples:Mrs Joyce CitizenApartment 7 (Sub-dwelling unit type code is APT)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

UnitTypeCode 0..1

Page 31: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 31 of 44

unitNumber Sub-dwelling unit number.Within a complex, a number used to distinguish an address found within a building / sub-complex or marina.The data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7 (Sub dwelling unit number is 7)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

levelTypeCode Level Type Code.Within a complex, an abbreviation used to distinguish the floor or level of a multi-storey building/sub-complex.

Usage Example:Apartment 7Level 3 (Level type code is L)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 20

LevelTypeCode 0..1

Page 32: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 32 of 44

levelNumber Level Number.Within a complex, the number of the floor or level of a multi-storey building/sub-complexThe data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7Level 3 (Level number is 3)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

complexRoadNumber1 Complex Road Number 1.Within a complex, identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 1 is 20)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

Page 33: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 33 of 44

complexRoadNumber2 Complex Road Number 2.Within a complex, identifies the last number for a ranged address in the road or thoroughfare.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 2 is 24)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

complexRoadName Complex Road Name.Within a complex, the name of the road /thoroughfare of the address.Within a Road name it is possible to find what appears to be a Road type (eg. The Boulevard).It is also possible to have a null Road type.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road name is Genetics)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

Page 34: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 34 of 44

complexRoadTypeCode Complex road type codeWithin a complex, an abbreviation used to distinguish the type of road / thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane NorthBlamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

RoadTypeCode 0..1

complexRoadSuffixCode Complex road suffix codeWithin a complex, an abbreviation representing the suffix of the road/thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road suffix code is N)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 20

RoadSuffixCode 0..1

Page 35: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 35 of 44

addressSiteName Address Site NameSynonyms: Building property name, Primary Complex name

The official place name or culturally accepted common usage name for an address site, including the name of a building, homestead, building complex, agricultural property, park or unbounded address site.This data element represents the name given to an entire building or address site

Usage Examples:Parliament House (Name of the building)University of Melbourne (Site name of university campus - a complex)Happy Valley Retirement Village (Site name of gated property - a complex)Darwin Town Hall (Name of the building)Blue Hills Farm (Name of the property)

Length: 100

string 0..1

lotNumber The Lot number is a reference number allocated to a property for subdivision administration purposes prior to road numbering.

Usage: Where an official Road number has not been assigned, this field may be used for postal purposes as well as the physical identification of an address site.

Length: 10

string 0..1

planNumber Plan NumberThe deposited plan number allocated to a property for subdivision administration purposes prior to road numbering in addition to the Lot number.

Length: 100

string 0..1

Page 36: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 36 of 44

roadNumber1 Road Number 1.Identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.

Start of Range Number of the road e.g. 29 Archer Street, where roadNumber1 is 2921-25 Archer Street, where roadNumber1 is 2135A Archer Street, where roadNumber1 is 35A

Length: 10

string 0..1

roadNumber2 Road Number 2.Identifies the last number for a ranged address in the road or thoroughfare.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.This data element is used for ranged street numbers otherwise it is left blank.End of Range Number of the street, e.g.21-25 Archer Street, where streetNumber2 is 2531-34A Archer Street, where roadNumber2 is 34A

Length: 10

string 0..1

Page 37: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 37 of 44

roadName Road Name.The name of the road/thoroughfare applicable to the address site or complex.Only the road name should be stored in this data element.

Usage Examples:BROWNS ROAD WESTIn this case the Road name is BROWNS, the Road type is RD and the Road suffix is W

THE AVENUE WESTIn this case the Road name is THE AVENUE, the Road type is null and the Road suffix is W

COTSWOLD BRETTIn this case the Road Name is COTSWOLD BRETT and the Road type is null

HIGH STREET ROADIn this case the Road Name is HIGH STREET and the Road t type is RD.

Length: 100

string 1..1

roadTypeCode Road Type Code.The abbreviation code used to distinguish the type of road/thoroughfare applicable to the address site/complex.

Usage example:23 Archer RD, where RD is the the Road Type code for Road

Length: 10

RoadTypeCode 0..1

Page 38: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 38 of 44

roadSuffixCode Road Suffix CodeThe abbreviation code used to represent the suffix of road/thoroughfare applicable to the address site/complex.

20-24 Genetics Lane North, where North is the roadSuffix = N

Length: 20

RoadSuffixCode 0..1

localityName Locality Name.The name of the locality/suburb of the address.

Length: 50

string 1..1

postcode Postcode.The Australian numeric descriptor for a postal delivery area, aligned with locality, suburb or place

Length: 10

string 0..1

stateTerritoryCode State Territory Code.The State or Territory code of the address.

Length: 3

StateTerritoryCodeType 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct

Page 39: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 39 of 44

DescribedBy These name value pairs will be used to communicate the results of the site qualification.Following is the list of names and associated values:1. PrimaryAccessTechnology: The value will contain either Fibre, Wireless or Interim Satellite. It is mandatory in the response to the Access Seeker.2. ServiceabilityClass: This value will contain one of the following numbers. It is mandatory in the response to the Access Seeker when PrimaryAccessTechnology is either Fibre or Wireless.0 - Planned to be serviced by Fibre in the future (boundary status isn't 'In Service' yet)1 - Serviceable by Fibre, no drop or NTD in place2 - Serviceable by Fibre, drop in place, no NTD in place3 - Serviceable by Fibre, drop and NTD in place4 - Planned to be serviced by Wireless5 - Serviceable by Wireless, CPE not installed6 - Serviceable by Wireless, CPE installed7 - Planned to be serviced by Satellite8 - Serviceable by Satellite, VSAT Terminal and CPE not installed9 - Serviceable by Satellite, VSAT Terminal and CPE installed3. ServiceabilityDate: Expected date when you can successfully submit an order. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ. It is not mandatory.4. CSAID: Customer Service Area ID. This value will be a string. It is mandatory in the response to the Access Seeker when PrimaryAccessTechnology is either Fibre or Wireless.

CharacteristicValue 0..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

Compare: Replace�
text
[Old text]: "contains" [New text]: "contain"
Compare: Insert�
text
"Wireless"
Compare: Delete�
text
"Wireless"
Compare: Insert�
text
"Seeker."
Compare: Delete�
text
"Seeker."
Compare: Move�
table cell
This table cell was moved from page 38 of old document to page 39 of this document
Compare: Move�
table cell
This table cell was moved from page 38 of old document
Compare: Move�
table cell
This table cell was moved from page 38 of old document to page 39 of this document
Compare: Move�
table cell
This table cell was moved from page 38 of old document
Compare: Insert�
text
"is mandatory in the response to the Access Seeker when"
Compare: Insert�
text
"PrimaryAccessTechnology"
Compare: Replace�
text
[Old text]: "not mandatory." [New text]: "either Fibre or Wireless."
Compare: Replace�
text
[Old text]: "isn’t ‘In" [New text]: "isn't 'In"
Compare: Replace�
text
[Old text]: "Service’" [New text]: "Service'"
Compare: Delete�
text
"not"
Compare: Replace�
text
[Old text]: "mandatory." [New text]: "mandatory in the response to the Access Seeker when"
Compare: Insert�
text
"PrimaryAccessTechnology is either Fibre or Wireless."
Compare: Move�
table cell
This table cell was moved from page 38 of old document to page 39 of this document
Compare: Move�
table cell
This table cell was moved from page 38 of old document
Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Page 40: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 40 of 44

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem

ItemInvolvesProduct Contains NTD ID and its characteristics Product 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct

ID NTD IDLength: 15

string 1..1

DescribedBy This contain a name-value pairs to further describe the attributes related to each NTDThe following is the list of names and their values associated with NTD.1. NTDInstallDate: Date in the future when an NTD will be installed. If NTD is already installed or there is no plan to install an NTD, no date will be returned. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ and the type field will be empty. It is not mandatory.2. NTDLocation: The value will be either INDOOR, OUTDOOR. It is not mandatory.3. NTDType: The value will be either INTERNAL, EXTERNAL. It is not mandatory.4. NTDPowerType: The value will be either AC,DC. It is not mandatory.5. BatteryPowerUnit: The value will be either Yes, No. It is not mandatory.6. BatteryPowerUnitMonitored: The value will be either ENABLED, DISABLED. It is not mandatory.7. UncommittedUpstreamBandwidth (This is the Capacity of the NTD in Megabits/second). It is not mandatory.8. UncommittedDownstreamBandwidth (This is the Capacity of the NTD in Megabits/second). It is not mandatory.9. UNI-D-1Status: The value will be either Used, Free. It is not mandatory.10. UNI-D-2Status: The value will be either Used, Free. It is not mandatory.11. UNI-D-3Status: The value will be either Used, Free. It is not mandatory.12. UNI-D-4Status: The value will be either Used, Free. It is not mandatory.13. UNI-V-1Status: The value will be either Used, Free. It is not mandatory.14. UNI-V-2Status: The value will be either Used, Free. It is not mandatory.

CharacteristicValue 0..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct/DescribedBy

Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Compare: Replace�
text
[Old text]: "1..*" [New text]: "0..*"
Page 41: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 41 of 44

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Page 42: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 42 of 44

Appendix A - List of Values

List of valuesProductOrder/orderType Version: V3.0

Connect Indicates the order is related to a Connect.

Disconnect Indicates the order is related to a Disconnect.

Modify Indicates the order is related to a Modify.

action Version: V3.0

ADD Indicates an Add action is being performed.

NO CHANGE Indicates No Change has occurred.

DELETE Indicates a Delete action is being performed.

MODIFY Indicates a Modify action is being performed.

ActivitySpecificationReferences/type Version: V3.0

Standard Install Indicates the appointment is for a Standard Install

ExceptionsThe code in the table below will be returned in the Exception\ID attribute. The description in the table will be returned in the Exception\description attribute.

InvalidProductException Version: V3.0

006000 The Product with the ID : %Product ID% specified in the request is invalid

NotAllowedException Version: V3.0

008000 The operation cannot be performed with the specified parameters: %parameter1%,%parameter2%, ....

TechnicalException Version: V3.0

000000 A technical error has occurred during the processing of the request.

ValidationException Version: V3.0

001000 The following mandatory field or fields are not provided: %field1%, %field2%, ....

001001 Field length of %fieldName% is invalid, the length provided is %providedLengthOfField% but it should be %acceptedLengthOfField%

001002 Data type mismatch on field %fieldName%

001003 Incorrect enumeration of %enumeration% provided for field %fieldName%

001004 Invalid parameter combination : %parameter1% cannot be provided with %parameter2%

001005 The following field or fields should not be provided for this operation: %field1%, %field2%,....

001006 The following technical issue or issues were found when validating the message: %technicalValidationReason1%. %technicalValidationReason2%. ...

001007 The specified %fieldName% is invalid due to the end date being before the start date

001008 The value specified in the field %fieldName% exceeds the maximum of %maximum allowed%

Page 43: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFS - 2012/09/28Document Version V2.4 © 2012 NBN Co Ltd 43 of 44

ExceptionsThe code in the table below will be returned in the Exception\ID attribute. The description in the table will be returned in the Exception\description attribute.

ValidationException Version: V3.0

001009 The value of %fieldName% is invalid as it is in the future.

001010 The number of occurrences for the following field %fieldName% exceeds the defined maximum occurrences of %maxOccurrences%

001011 At least one of the following fields must be provided: %field1%, %field2%

001012 The value for %field name% : %field value% is in an invalid format

InvalidAddressException Version: V3.0

012000 The NBN Location ID provided in the request : %NBN Location ID% does not result in a valid NBN Location Address match

012001 There are multiple matches for the address details provided in the request

012002 There are no matches for the address details provided in the request

InvalidOrderException Version: V3.0

005000 Order ID : %OrderID% is closed

005001 Order ID : %OrderID% is invalid or not found

005002 Order ID : %OrderID% is past the cancellation Point of No Return (cPoNR)

005003 Order ID : %OrderID% is past the amendment Point of No Return (aPoNR)

005004 Order ID : %OrderID% is already in progress of been amended

005005 Supplied NTD ID : %NTD ID% not found

005006 Attributes of the NTD in LNI do not match the attributes required by the order

005007 Order ID : %OrderID% is not PENDING waiting on information from the Access Seeker

AccountHierarchyViolationException Version: V3.0

002000 The Billing Account ID %Billing Account ID% does not belong to the Access Seeker

002001 The Product Instance ID : %ID% does not belong to the Access Seeker

AccountNotActiveException Version: V3.0

003000 The Billing Account with the ID : %Billing Account ID% is not active

003001 The Sell Flag is set to 'FALSE' for the Billing Account with the ID : %Billing Account ID%

Compare: Insert�
text
"005007"
Compare: Insert�
text
"Order ID : %OrderID% is not PENDING waiting on information from the Access Seeker"
Page 44: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy
Page 45: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

Interface Functional Specification ManageServiceQualificationIndustry InterfaceNBN CO OSS PROGRAM

This document forms part of NBN Co's Wholesale Broadband Agreement, which is a Standard Form of Access Agreement for the purposes of Part XIC of the Competition and Consumer Act 2010.

Page 46: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 2 of 43

Copyright

This document is subject to copyright and must not be used except as permitted below or under the Copyright Act 1968 (Cth). You must not reproduce or publish this document in whole or in part for commercial gain without the prior written consent of NBN Co. You may reproduce and publish this document in whole or in part for educational or non-commercial purposes as approved by NBN Co in writing.

Copyright © 2012 NBN Co Limited. All rights reserved.

Disclaimer

This document predominantly sets out technical information in relation to NBN Co's B2B Gateway. It also sets out some of terms and conditions that apply in relation to NBN Co's B2B Gateway. Other terms and conditions in relation to NBN Co's B2B Gateway are set out elsewhere in the Wholesale Broadband Agreement between NBN Co and Access Seeker, including in the Product Description for the NBN Co Platform Interfacing Service and the NBN Co Operations Manual. Access Seeker is advised to familiarise itself with all of the terms and conditions that apply in relation to NBN Co's B2B Gateway, not just those terms and conditions set out in this document. Where NBN Co has provided recommendations or examples in this document, Access Seeker must not assume that NBN Co's networks, platforms or systems will support Access Seeker's implementation of such recommendations or examples. Information that is identified as important in this document is brought to Access Seeker's attention for practical purposes of understanding all information in context and should not necessary be accorded more weight than other information for implementation purposes.

Environment

NBN Co asks that you consider the environment before printing this document.

Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 47: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 3 of 43

Document Control

Title Interface Functional Specification: ManageServiceQualification

Revision History

Detailed descriptions of changes can be found in the Service Design Change Log.

Version Date Details

V1.9 2012/04/06 First Release

Related DocumentsDocument Title Version

ManageServiceQualification Interface Technical Specification V1.9

Interface Common Objects Specification V1.4

Compare: Replace�
text
[Old text]: "Detailed" [New text]: "Version"The following text attributes were changed: font
Compare: Insert�
text
"Updated touchpoint"
Compare: Insert�
text
"2012/07/05"
Compare: Insert�
text
"V2.3"
Compare: Insert�
text
"Removed postcode from sample messages."
Compare: Insert�
text
"2012/06/11"
Compare: Insert�
text
"V2.2"
Compare: Insert�
text
"Updated sample messages with corrections."
Compare: Insert�
text
"2012/05/18"
Compare: Insert�
text
"V2.1"
Compare: Insert�
text
"Multicast and 2 UNI-Vs."
Compare: Insert�
text
"Updated sample messages with Service Restoration SLA,"
Compare: Insert�
text
"First draft for Industry Interface 3.0."
Compare: Insert�
text
"2012/05/09"
Compare: Insert�
text
"V2.0"
Compare: Insert�
text
"- remove postcode from responses."
Compare: Insert�
text
"- correct Transient IDs for NFAS/NWAS."
Compare: Insert�
text
"Updated sample messages to:"
Compare: Insert�
text
"touchpoint attributes 'ServiceabilityClass' and 'CSAID'."
Compare: Insert�
text
"- clarify the behaviour of responseSingleSiteQualification"
Compare: Insert�
text
"message."
Compare: Insert�
text
"- clarify the sequence of the specification blocks within a"
Compare: Insert�
text
"pairs."
Compare: Insert�
text
"- clarify the use of DescribedBy and SpecifiedBy name/value"
Compare: Insert�
text
"Updated touchpoint descriptions to:"
Compare: Insert�
text
"Updated under Industry Interface 2.1."
Compare: Insert�
text
"2012/08/29"
Compare: Insert�
text
"V1.91"
Compare: Insert�
text
"First Release"
Compare: Insert�
text
"2012/04/06"
Compare: Insert�
text
"V1.9"
Compare: Insert�
text
"Details"
Compare: Insert�
text
"Date"
Compare: Insert�
text
"to:"
Compare: Insert�
text
"- clarify the use of DescribedBy and SpecifiedBy name/value"
Compare: Insert�
text
"pairs"
Compare: Insert�
text
"- clarify the sequence"
Compare: Replace�
text
[Old text]: "changes can be found in" [New text]: "the specification blocks within a"
Compare: Insert�
text
"- clarify"
Compare: Insert�
text
"message"
Compare: Insert�
text
"behaviour of responseSingleSiteQualification"
Compare: Insert�
text
"touchpoint attributes 'ServiceabilityClass' and 'CSAID'"
Compare: Insert�
text
"V2.4"
Compare: Insert�
text
"2012/09/28"
Compare: Insert�
text
"Updated sample messages to:"
Compare: Insert�
text
"- add Multicast to existing sample messages."
Compare: Insert�
text
"- add Second UNI-V sample messages."
Compare: Insert�
text
"- add"
Compare: Replace�
text
[Old text]: "Design Change Log." [New text]: "Restoration SLA to existing sample messages."
Compare: Insert�
text
"- removed VLAN Mode from order feasibility sample messages."
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "- updated NTD Type and Location from External/Outdoor to"
Compare: Delete�
text
"Version"
Compare: Delete�
text
"Date2012/04/06"
Compare: Delete�
text
"First Release"
Compare: Replace�
text
[Old text]: "Details" [New text]: "Internal/Indoor."The following text attributes were changed: font
Compare: Insert�
text
"Version"
Compare: Insert�
text
"V2.4"
Compare: Insert�
text
"V1.6"
Compare: Delete�
text
"VersionV1.9V1.4"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 48: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 4 of 43

1. Introduction1.1 Purpose

The purpose of this document is to describe the service interface from a logical (functional) perspective.

1.2 ScopeThis document applies to: • The functional level interface description for the service• It details the service from a non-technical “black box” level to describe the service input and output

messages and concepts.

This document does NOT address: • Technical specifications, or physical design details of the service• Description of Functional and Non functional requirements

1.3 Target AudienceAudience Intended purpose

Business Stakeholder High-level understanding.Provide non-technical audience with a broad understanding of the service behaviour and constraints.

Project Team Project Planning.To support ongoing project planning.

Project Architects Project Architecture.To align other architectural views.

Nominated Reviewers Project Socialisation and Review.To understand service behaviour and constraints and to obtain objective feedback through the Peer Review & Ratification processes.

Integration Developers Input into detailed design.

Business Analysts Input into the Requirement Specification including service mapping documentation and schema designs.

Test Analysts High-level understanding & Next Phase.Provides a high level overview of the proposed service and used in conjunction with the System Requirement Specification, as input into their System Test documentation.

Service Consumer Stakeholders Input into detailed design and architecture for the systems consuming the service.

Service Provider Stakeholders Input into detailed design and architecture for the systems providing the service.

1.4 Document PrecedenceNBN Co’s Detailed B2B Specifications comprise a number of different documents. If there is any inconsistency between any of these documents, then that inconsistency will be resolved by giving precedence to the documents in the following order:1.The XSD, Product Definitions (XML), and the "NBN Co Product Attributes and Business Rules Matrix"2.The Interface Functional and Technical Specifications3.The Developer Guides and Message Examples

Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 49: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 5 of 43

2. Service DescriptionThe Manage Service Qualification interface includes mechanisms to determine serviceability of a location.Functions include:• Qualify whether or not a service can be ordered at a particular site (site qualification).• Determine if the product specified is serviceable at a particular site (order feasibility).

Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 50: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 6 of 43

2.1 Information ModelThis section describes the key entities and their relationships in the service schema represented as a class diagram.

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 51: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 7 of 43

2.2. requestOrderFeasibilityCheck

Touchpoint DescriptionThis touchpoint is used to perform a check to see if a given product offering can be delivered to a specific location.When using this touchpoint, the Access Seeker can provide a valid NBN Location ID and Product Offering. They can also specify certain resources or services which should be used in the delivery of the product offering at the location.Validation RulesThis following validation rules apply to this operation. Failure to satisfy these validation rules can cause an input message to be rejected and the service invocation to result in an error.• Valid NBN Product Specification ID and Version must be provided in the request.• Valid Billing Account ID must be provided in the request.The touchpoint can be used to asses the feasibility of 'Connect' orders only.Characteristics• Non-Repudiable: No• Each request will be handled without regard to previous requests. If a duplicate request is received by the touchpoint, then this will be processed independently from the first

request. Each of the requests will result in a separate response.

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 52: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 8 of 43

This section describes in detail all attributes required in the request message, including a description, type and any length/cardinality restrictions. The cardinality column reflects whether an attribute is mandatory in the request.

Name Description Type Cardinality

/ManageServiceQualificationRequest

serviceQualificationType This specifies the type of Service Qualification. Valid Values are: ProductOrder and ServiceQualification

string 1..1

ProductOrder Root element for Service Qualification Request - this contains details of the Location, Product and Appointment which will be used to determine the feasibility of the Order.

ProductOrder 1..1

/ManageServiceQualificationRequest/ProductOrder

AccessSeekerInteraction Contains the Access Seeker Order Correlation ID and/or Billing Account ID.

AccessSeekerInteraction 0..1

orderType The attribute contains the type of Product Order.Refer to the Appendix for a complete list of values for ProductOrder/orderType,V3.0.Length: 15

string 1..1

ProductOrderComprisedOf Access Seeker populates the Product Order with details of Appointment, Location and the Product to be Ordered

ProductOrderItem 1..1

AccessSeekerContact Access Seeker Contact Details. This contains the name and contact phone number of the contact person

AccessSeekerContact 0..1

/ManageServiceQualificationRequest/ProductOrder/AccessSeekerContact

contactName Access Seeker contact name string 0..1

contactPhone Access Seeker contact phone. string 0..1

/ManageServiceQualificationRequest/ProductOrder/AccessSeekerInteraction

ID Access Seeker Correlation ID.Length: 50

string 0..1

billingAccountID Access Seeker Billing Account Id.Length: 15

string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesLocation Contains the Location associated with this Product Order BusinessInteractionLocation 0..1

ItemInvolvesAppointment Contains the Appointment associated with this Product Order. Appointment 0..*

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 53: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 9 of 43

ItemInvolvesProduct Contains Product Version and Product Specfication ID Product 1..1

ReferencesProductOrderItem An Instance of this contains details of the Product with its associated characteristics

ProductOrderItem 1..*

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment

activityNr A unique identifier for the Activity. Contains the appointment ID.

Length: 15

string 0..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocation

Place Specifies attributes associated with a location where the Product would be delivered

Place 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location ID. This only requires the NBN Location ID and not the complete location.Length: 15

string 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Definition provided to Access Seekers by NBN Co during on-boarding.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy

ID Product Specification IDLength: 15

string 0..1

version Product Specification VersionLength: 6

string 0..1

type Product Specification Type string 0..1

category Product Specification Category string 0..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesProduct Contains characteristics associated with the Product. Please refer to Product Catalog for the compelete set of fields and structure that can be used here.

Product 1..1

ReferencesProductOrderItem An Instance of this contains an associated Sub-Product and its characteristics.

ProductOrderItem 0..*

Compare: Delete�
text
"Product"
Compare: Insert�
text
"Product"
Compare: Replace�
text
[Old text]: "/ManageServiceQualificationRequest/P" [New text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment"
Compare: Delete�
text
"roductOrder/ProductOrderComprisedOf/ItemInvolvesAppointment"
Compare: Delete�
text
"/ManageServiceQualificationRequest/PPlace"
Compare: Replace�
text
[Old text]: "roductOrder/ProductOrderComprisedOf/ItemInvolvesLocation" [New text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesLocationPlace"
Compare: Insert�
text
"delivered"
Compare: Delete�
text
"delivered"
Compare: Delete�
text
"string"
Compare: Delete�
text
"1..1"
Compare: Insert�
text
"string"
Compare: Insert�
text
"1..1"
Compare: Delete�
text
"CharacteristicValue"
Compare: Delete�
text
"1..*"
Compare: Replace�
text
[Old text]: "Seekers" [New text]: "Seeker"
Compare: Insert�
text
"CharacteristicValue"
Compare: Insert�
text
"1..*"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedByvalueRepresents the value attribute in a name-value pair.CharacteristicThe associated quality or distinctive feature that defines an entity"
Compare: Replace�
text
[Old text]: "/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy" [New text]: "stringCharacteristic"The following text attributes were changed: size
Compare: Insert�
text
"1..11..1"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/DescribedBy/CharacteristicIDRepresents the name attribute in a name-value pair.stringtypeRepresents the categorization of the name-value pair.string"
Compare: Insert�
text
"1..11..1"
Compare: Insert�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ItemInvolvesProduct/SpecifiedBy"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"string"
Compare: Delete�
text
"0..1"
Compare: Insert�
text
"stringstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem"
Compare: Delete�
text
"actionAction being applied to the object."
Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..11..11..1"
Compare: Delete�
text
"Refer to the Appendix for a complete list of values for action,V3.0."
Compare: Delete�
text
"Length: 12"
Compare: Delete�
text
"ItemInvolvesProductContains characteristics associated with the Product. Please refer to"
Compare: Delete�
text
"Product"
Compare: Delete�
text
"Product Catalog for the compelete set of fields and structure that can be"
Compare: Delete�
text
"used here."
Compare: Delete�
text
"ReferencesProductOrderItemAn Instance of this contains an associated Sub-Product and its"
Compare: Delete�
text
"ProductOrderItem"
Compare: Delete�
text
"0..*"
Compare: Delete�
text
"characteristics."
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 54: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 10 of 43

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Catalog.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedBy

ID Product Specification IDLength: 15

string 0..1

version Product Specification VersionLength: 6

string 0..1

type Product Specification Type string 0..1

category Product Specification Category string 0..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem

action Action being applied to the object.Refer to the Appendix for a complete list of values for action,V3.0.Length: 12

string 0..1

ItemInvolvesProduct Contains characteristics associated with the Product. Please refer to Product Catalog for the compelete set of fields and structure that can be used here.

Product 1..1

/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct

DescribedBy This contains the name/value pairs which describe the Product. The valid list and structure of name/value pairs are described in the Product Definition provided to Access Seekers by NBN Co during on-boarding.

CharacteristicValue 1..*

SpecifiedBy This contains the Product Specification details. EntitySpecification 1..1

Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct"
Compare: Delete�
text
"DescribedByThis contains the name/value pairs which describe the Product. The valid CharacteristicValue"
Compare: Delete�
text
"1..*"
Compare: Delete�
text
"list and structure of name/value pairs are described in the Product Catalog."
Compare: Delete�
text
"SpecifiedByThis contains the Product Specification details.EntitySpecification"
Compare: Delete�
text
"1..1"
Compare: Delete�
text
"/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedBy"
Compare: Delete�
text
"IDProduct Specification IDstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"Length: 15"
Compare: Delete�
text
"versionProduct Specification Versionstring"
Compare: Delete�
text
"0..1"
Compare: Delete�
text
"Length: 6"
Compare: Delete�
text
"typeProduct Specification Typestring"
Compare: Delete�
text
"0..1"
Compare: Insert�
text
"1..1"
Compare: Delete�
text
"0..1"
Compare: Replace�
text
[Old text]: "Seekers" [New text]: "Seeker"
Compare: Insert�
text
"1..1/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedByvalueRepresents the value attribute in a name-value pair.string1..1CharacteristicCharacteristic1..1The associated quality or distinctive feature that defines an entity/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/DescribedBy/CharacteristicIDRepresents the name attribute in a name-value pair.string1..1typeRepresents the categorization of the name-value pair.string1..1/ManageServiceQualificationRequest/ProductOrder/ProductOrderComprisedOf/ReferencesProductOrderItem/ReferencesProductOrderItem/ItemInvolvesProduct/SpecifiedByIDProduct Specification IDstring1..1Length: 15versionProduct Specification Versionstring1..1Length: 6typeProduct Specification Typestring1..1categoryProduct Specification Categorystring"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "10" [New text]: "11"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 55: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 11 of 43

2.3. responseOrderFeasibilityCheck

Touchpoint DescriptionThis touchpoint will return details of the capability to deliver a Product to the specified location. It will include:• Service Qualification Status (Feasible; Feasible - Appointment Required; Feasible - Delayed; Rejected)• NTD Install Date (if it is known)• List of Shortfalls (if applicable)When the order is not feasible, the touchpoint will return a response with a qualification status of 'Rejected'. If the Access Seeker proceeds to submit the same order through the createOrder operation the order will be rejected again.Characteristics• Non-Repudiable: No

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "11" [New text]: "12"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 56: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 12 of 43

Exception(Please refer to the Appendix for the exception codes and descriptions)

Description

invalidProductException Returned if an invalid Product has been specified in the request.

notAllowedException Returned if the Access Seeker is not allowed to perform the operation with the specified parameters.

technicalException Returned when a technical issue prevents the processing of the request. For example, the end application is unavailable.

validationException Returned when a validation issue prevents the processing of the request. For example, the message does not validate against the XSD and/or does not contain a mandatory field specified in the interface specification.

invalidAddressException Returned if an invalid Address has been specified in the request.

invalidOrderException Returned when the order being qualified is invalid.

accountHierarchyViolationException Returned when the optional Billing Account identifier is provided, but it does not belong to Access Seeker identifier.

accountNotActiveException Returned when an Access Seeker's account has a 'No-Sell flag' set (or) when billing account belonging to an Access Seeker is Inactive or Closed.

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "12" [New text]: "13"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 57: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 13 of 43

This section describes in detail all attributes returned in the response message, including a description, type and any length/cardinality restrictions.Name Description Type Cardinality

/ManageServiceQualificationResponse

ServiceQualification Root element for Service Qualification detail response. ServiceQualification 1..1

/ManageServiceQualificationResponse/ServiceQualification

interactionStatus The resulting SQ status. One of:1. "Feasible": Order is feasible without Appointment OR Appointment specified is adequate.2. "Feasible - Appointment Required": Order is feasible however requires an Appointment to address Shortfalls.3. "Feasible - Delayed": Order is feasible however this is an NBN infrastructure shortfall.4. "Rejected": Order is not possible because either the Area is not Serviceable OR the Order is not valid (e.g. product not available, no capacity, invalid NTD/ CVC id's, specified attributes not correct for template. Essentially anything that could cause a rejection on order submission).

string 1..1

DescribedBy These name value pairs will be used to communicate the results of the order feasibility1. NTDInstallDate: Date in the future when an NTD will be installed. If NTD is already installed or there is no plan to install an NTD, no date will be returned. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ and the type field will be empty. It is not mandatory.2. NTD: The value will be either Yes OR No (indicating if there is a shortfall)and the type field will contain "Shortfall". It is not mandatory.3. LEADIN: The value will be either Yes OR No (indicating if there is a shortfall) and the type field will contain "Shortfall". It is not mandatory.4. NBNCOINFRASTRUCTURE: The value will be either Yes OR No (indicating if there is a shortfall) and the type field will contain "Shortfall". It is not mandatory.

CharacteristicValue 0..*

ServiceQualificationComprisedOf Contains further shortfall details ServiceQualificationItem 0..1

/ManageServiceQualificationResponse/ServiceQualification/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "13" [New text]: "14"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 58: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 14 of 43

type This is used to classify the type of name-value pair. Valid Values are: Shortfall

string 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesAppointment Contains one or more Demand Types which are needed before an order can be fulfilled. This is returned if the interationStatus is "Feasible - Appointment Required"

Appointment 0..1

Note Contains the reason for rejection and Reason Code where required. Note 0..1

infrastructurePlannedDate Contains the date when NBN plans to overcome their infrastructure shortfall. This is returned if the interactionStatus is "Feasible - Delayed" and the infrastructure planned date is known.The format for date time is [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]Z (in UTC) e.g. 2011-06-23T12:00:00Z.Length: 20

dateTime 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment

ActivitySpec Contains one or more Demand Types ActivitySpec 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment/ActivitySpec

ActivitySpecificationReferences Contains demand type attribute ActivitySpec 1..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesAppointment/ActivitySpec/ActivitySpecificationReferences

type Demand Type, such as Standard Install.Refer to the Appendix for a complete list of values for ActivitySpecificationReferences/type,V3.0.

string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/Note

ID Reason CodeLength: 15

string 0..1

description Contains Reason for RejectionLength: 256

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "14" [New text]: "15"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 59: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 15 of 43

2.4. requestSingleSiteQualification

Touchpoint DescriptionThis touchpoint is used to determine if a location is within the NBN Co service footprint (i.e. within an NBN serving area) and the type of access technology available at the location (i.e. Fibre, Wireless or Interim Satellite). It also provides infrastructure availability for the location (e.g. NTD Port/NNI availability) and Peak bandwidth availability. However, it does not validate if a specific product can be provisioned at a location - this function is provided by the requestOrderFeasibilityCheck touchpoint.This touchpoint accepts a location specified via one of the following:• NBN Location ID• NBN Physical Address details• Spatial Geocode (Latitude/Longitude)• GNAF IDIf the request does not result in the identification of a single NBN Location an exception will be returned.Validation RulesThis following validation rules apply to this touchpoint. Failure to satisfy these validation rules can cause an input message to be rejected and the service invocation to result in an error.• Provide a single valid NBN Location in the request.Characteristics• Non-Repudiable: No• Each request will be handled without regard to previous requests. If a duplicate request is received by the touchpoint, then this will be processed independently from the first

request. Each of the requests will result in a separate response.

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "15" [New text]: "16"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 60: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 16 of 43

This section describes in detail all attributes required in the request message, including a description, type and any length/cardinality restrictions. The cardinality column reflects whether an attribute is mandatory in the request.

Name Description Type Cardinality

/ManageServiceQualificationRequest

serviceQualificationType This specifies the type of Service Qualification. Valid Values are: ProductOrder and ServiceQualification

string 1..1

ServiceQualification Root element for Service Qualification Request - this contains details of the location which will be used to determine the type of access technology available.

ServiceQualification 1..1

/ManageServiceQualificationRequest/ServiceQualification

ServiceQualificationComprisedOf Will have all detail used to perform the Site Qualification including the Location.

ServiceQualificationItem 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesLocation When using this operation, the Access Seeker must provide a valid Location details in form of one of the followingGNAF ID;Spatial Geocode (Latitude/Longitude);Full/Partial Australian Property Address;NBN Location ID;If the address details provided do not resolve to a unique NBN Location ID an exception will be returned.

BusinessInteractionLocation 1..1

type This species the type of the address provided. Valid values are: NBNPhysicalAddress, NBNLocationID, GNAFID, SpatialGeocode

string 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation

Place An Instance of Place to specifies Geocode and Physical Address associated with a location. If the Access Seeker wants to use GNAF ID, the Place object must be instantiated with the GNAF type (for example, Place@xsi:type=GNAF). The ID within Place is then used as the GNAF ID and it is mandatory

Place 0..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location ID.Length: 15

string 0..1

Geocode If Access Seeker needs to use Geocode details, this can be used Geocode 0..1

PhysicalAddress Physical address details of the location AustralianAddress 0..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/Geocode

Compare: Replace�
text
[Old text]: "species" [New text]: "specifies"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "16" [New text]: "17"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 61: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 17 of 43

latitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Latitudes south of the equator are expressed as a negative number, north of the equator as positive.Valid value range -8 to -45 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 1..1

longitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Longitudes east of Greenwich the equator are expressed as a positive number, west of Greenwich as negative.Valid value range 96 to 160 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 1..1

/ManageServiceQualificationRequest/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/PhysicalAddress

secondaryComplexName Secondary Complex nameName associated with a building or area within a complex site.This data element may represent the name given to an entire building within an address site that has its own separate address.

Usage Examples:Biology Building B (Secondary Complex name - Building within a complex)20-24 Genetics Lane NorthBlamey Research Institute (Address site name - A complex)1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "17" [New text]: "18"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 62: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 18 of 43

unitTypeCode Sub dwelling unit type code.Within a complex, an abbreviation used to distinguish the type of an address found within a building / sub-complex or marina.

Usage examples:Mrs Joyce CitizenApartment 7 (Sub-dwelling unit type code is APT)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

UnitTypeCode 0..1

unitNumber Sub-dwelling unit number.Within a complex, a number used to distinguish an address found within a building / sub-complex or marina.The data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7 (Sub dwelling unit number is 7)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "18" [New text]: "19"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 63: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 19 of 43

levelTypeCode Level Type Code.Within a complex, an abbreviation used to distinguish the floor or level of a multi-storey building/sub-complex.

Usage Example:Apartment 7Level 3 (Level type code is L)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 20

LevelTypeCode 0..1

levelNumber Level Number.Within a complex, the number of the floor or level of a multi-storey building/sub-complexThe data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7Level 3 (Level number is 3)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "19" [New text]: "20"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 64: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 20 of 43

complexRoadNumber1 Complex Road Number 1.Within a complex, identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 1 is 20)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

complexRoadNumber2 Complex Road Number 2.Within a complex, identifies the last number for a ranged address in the road or thoroughfare.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 2 is 24)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "20" [New text]: "21"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 65: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 21 of 43

complexRoadName Complex Road Name.Within a complex, the name of the road /thoroughfare of the address.Within a Road name it is possible to find what appears to be a Road type (eg. The Boulevard).It is also possible to have a null Road type.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road name is Genetics)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

complexRoadTypeCode Complex road type codeWithin a complex, an abbreviation used to distinguish the type of road / thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane NorthBlamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

RoadTypeCode 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "21" [New text]: "22"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 66: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 22 of 43

complexRoadSuffixCode Complex road suffix codeWithin a complex, an abbreviation representing the suffix of the road/thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road suffix code is N)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 20

RoadSuffixCode 0..1

addressSiteName Address Site NameSynonyms: Building property name, Primary Complex name

The official place name or culturally accepted common usage name for an address site, including the name of a building, homestead, building complex, agricultural property, park or unbounded address site.This data element represents the name given to an entire building or address site

Usage Examples:Parliament House (Name of the building)University of Melbourne (Site name of university campus - a complex)Happy Valley Retirement Village (Site name of gated property - a complex)Darwin Town Hall (Name of the building)Blue Hills Farm (Name of the property)

Length: 100

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "22" [New text]: "23"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 67: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 23 of 43

lotNumber The Lot number is a reference number allocated to a property for subdivision administration purposes prior to road numbering.

Usage: Where an official Road number has not been assigned, this field may be used for postal purposes as well as the physical identification of an address site.

Length: 10

string 0..1

planNumber Plan NumberThe deposited plan number allocated to a property for subdivision administration purposes prior to road numbering in addition to the Lot number.

Length: 100

string 0..1

roadNumber1 Road Number 1.Identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.

Start of Range Number of the road e.g. 29 Archer Street, where roadNumber1 is 2921-25 Archer Street, where roadNumber1 is 2135A Archer Street, where roadNumber1 is 35A

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "23" [New text]: "24"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 68: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 24 of 43

roadNumber2 Road Number 2.Identifies the last number for a ranged address in the road or thoroughfare.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.This data element is used for ranged street numbers otherwise it is left blank.End of Range Number of the street, e.g.21-25 Archer Street, where streetNumber2 is 2531-34A Archer Street, where roadNumber2 is 34A

Length: 10

string 0..1

roadName Road Name.The name of the road/thoroughfare applicable to the address site or complex.Only the road name should be stored in this data element.

Usage Examples:BROWNS ROAD WESTIn this case the Road name is BROWNS, the Road type is RD and the Road suffix is W

THE AVENUE WESTIn this case the Road name is THE AVENUE, the Road type is null and the Road suffix is W

COTSWOLD BRETTIn this case the Road Name is COTSWOLD BRETT and the Road type is null

HIGH STREET ROADIn this case the Road Name is HIGH STREET and the Road t type is RD.

Length: 100

string 1..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "24" [New text]: "25"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 69: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 25 of 43

roadTypeCode Road Type Code.The abbreviation code used to distinguish the type of road/thoroughfare applicable to the address site/complex.

Usage example:23 Archer RD, where RD is the the Road Type code for Road

Length: 10

RoadTypeCode 0..1

roadSuffixCode Road Suffix CodeThe abbreviation code used to represent the suffix of road/thoroughfare applicable to the address site/complex.

20-24 Genetics Lane North, where North is the roadSuffix = N

Length: 20

RoadSuffixCode 0..1

localityName Locality Name.The name of the locality/suburb of the address.

Length: 50

string 1..1

postcode Postcode.The Australian numeric descriptor for a postal delivery area, aligned with locality, suburb or place

Length: 10

string 0..1

stateTerritoryCode State Territory Code.The State or Territory code of the address.

Length: 3

StateTerritoryCodeType 1..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "25" [New text]: "26"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 70: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 26 of 43

2.5. responseSingleSiteQualification

Touchpoint DescriptionThis touchpoint will contain the results of a previously submitted Site Qualification request.If a single location was provided, the response can contain:• NBN Location ID;• Location Details (returned only if GNAF ID was not used to identify the location). These details include:• • GNAF ID;

• Spatial Geocode (Latitude/Longitude);• NBN Physical Address details

• Service Qualification Status (Servicable; Serviceable - Shortfall; Rejected)• Primary Access Technology (Fibre; Wireless; Interim Satellite)• Serviceability Class;• Serviceability Date; (if it is available)• CSA ID;• List of NTDs;Characteristics• Non-Repudiable: No

Exception(Please refer to the Appendix for the exception codes and descriptions)

Description

invalidAddressException Returned if an invalid Address has been specified in the request.

technicalException Returned when a technical issue prevents the processing of the request. For example, the end application is unavailable.

validationException Returned when a validation issue prevents the processing of the request. For example, the message does not validate against the XSD and/or does not contain a mandatory field specified in the interface specification.

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "26" [New text]: "27"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 71: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 27 of 43

This section describes in detail all attributes returned in the response message, including a description, type and any length/cardinality restrictions.Name Description Type Cardinality

/ManageServiceQualificationResponse

ServiceQualification Root element for Service Qualification Response - this contains details of the location which will be used to determine the type of access technology available.

ServiceQualification 1..1

/ManageServiceQualificationResponse/ServiceQualification

interactionStatus The resulting SQ status. One of:"Serviceable": Location is serviceable now without shortfall."Serviceable - Shortfall": Location is serviceable now however there is a shortfall."Rejected": No services are currently available at the location.

string 1..1

ServiceQualificationComprisedOf Will have all detail such as location the Service Qualification test result ServiceQualificationItem 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf

ItemInvolvesLocation One or more the following location details will be populated in this object :NBN Location ID;Location Type;Spatial Geocode (Latitude/Longitude);Australian Property Address;

BusinessInteractionLocation 1..1

ItemInvolvesProduct Represents attributes returned which are associated with the Product Product 1..1

ReferencesServiceQualificationItem An Instance of this represents attributes which are associated with the NTD and its specificationThis will be repeated for each NTD returned as part of the Site Qualification

ServiceQualificationItem 0..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation

Place Specifies attributes associated with a location Place 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation

ID Unique NBN Location IDLength: 15

string 1..1

DescribedBy This contains name-value pairs used to hold Location related information.Following is the list of names and associated values:Region: Contains the Region which the address is located within. Valid values for this characteristic are: Urban, Major Rural, Minor Rural, Remote. It is not mandatory.

CharacteristicValue 0..1

Geocode Geocode details will be populated here. Geocode 0..1

PhysicalAddress Details of the Physical Address will be populated here. AustralianAddress 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "27" [New text]: "28"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 72: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 28 of 43

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/DescribedBy

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/Geocode

geographicDatum The geographicDatum is currently based on GDA94. This value "GDA94" will be returned.

Length: 10

string 0..1

latitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Latitudes south of the equator are expressed as a negative number, north of the equator as positive.Valid value range -8 to -45 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 0..1

longitude This field is used by NBN Co to capture the co-ordinates of an NBN Location.Longitudes east of Greenwich the equator are expressed as a positive number, west of Greenwich as negative.Valid value range 96 to 160 based on GDA94.Format: [+/-]nnn.nnnnnnnn

Length: 13

double 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesLocation/Place@xsi:type=NBNLocation/PhysicalAddress

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "28" [New text]: "29"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 73: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 29 of 43

secondaryComplexName Secondary Complex nameName associated with a building or area within a complex site.This data element may represent the name given to an entire building within an address site that has its own separate address.

Usage Examples:Biology Building B (Secondary Complex name - Building within a complex)20-24 Genetics Lane NorthBlamey Research Institute (Address site name - A complex)1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

unitTypeCode Sub dwelling unit type code.Within a complex, an abbreviation used to distinguish the type of an address found within a building / sub-complex or marina.

Usage examples:Mrs Joyce CitizenApartment 7 (Sub-dwelling unit type code is APT)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

UnitTypeCode 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "29" [New text]: "30"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 74: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 30 of 43

unitNumber Sub-dwelling unit number.Within a complex, a number used to distinguish an address found within a building / sub-complex or marina.The data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7 (Sub dwelling unit number is 7)Level 3Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

levelTypeCode Level Type Code.Within a complex, an abbreviation used to distinguish the floor or level of a multi-storey building/sub-complex.

Usage Example:Apartment 7Level 3 (Level type code is L)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 20

LevelTypeCode 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "30" [New text]: "31"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 75: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 31 of 43

levelNumber Level Number.Within a complex, the number of the floor or level of a multi-storey building/sub-complexThe data element may include a leading alphabetic prefix.The data element may include a trailing alphabetic suffix.

Usage example:Apartment 7Level 3 (Level number is 3)Apex Building48 Johnson RdCLAYTON VIC 3168

Length: 10

string 0..1

complexRoadNumber1 Complex Road Number 1.Within a complex, identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 1 is 20)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "31" [New text]: "32"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 76: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 32 of 43

complexRoadNumber2 Complex Road Number 2.Within a complex, identifies the last number for a ranged address in the road or thoroughfare.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road number 2 is 24)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

string 0..1

complexRoadName Complex Road Name.Within a complex, the name of the road /thoroughfare of the address.Within a Road name it is possible to find what appears to be a Road type (eg. The Boulevard).It is also possible to have a null Road type.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road name is Genetics)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 100

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "32" [New text]: "33"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 77: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 33 of 43

complexRoadTypeCode Complex road type codeWithin a complex, an abbreviation used to distinguish the type of road / thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane NorthBlamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 10

RoadTypeCode 0..1

complexRoadSuffixCode Complex road suffix codeWithin a complex, an abbreviation representing the suffix of the road/thoroughfare of the address.

Usage Example:Biology Building B20-24 Genetics Lane North (Complex road suffix code is N)Blamey Research Institute1-131 Sunshine RdCAIRNS QLD 4870

Length: 20

RoadSuffixCode 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "33" [New text]: "34"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 78: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 34 of 43

addressSiteName Address Site NameSynonyms: Building property name, Primary Complex name

The official place name or culturally accepted common usage name for an address site, including the name of a building, homestead, building complex, agricultural property, park or unbounded address site.This data element represents the name given to an entire building or address site

Usage Examples:Parliament House (Name of the building)University of Melbourne (Site name of university campus - a complex)Happy Valley Retirement Village (Site name of gated property - a complex)Darwin Town Hall (Name of the building)Blue Hills Farm (Name of the property)

Length: 100

string 0..1

lotNumber The Lot number is a reference number allocated to a property for subdivision administration purposes prior to road numbering.

Usage: Where an official Road number has not been assigned, this field may be used for postal purposes as well as the physical identification of an address site.

Length: 10

string 0..1

planNumber Plan NumberThe deposited plan number allocated to a property for subdivision administration purposes prior to road numbering in addition to the Lot number.

Length: 100

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "34" [New text]: "35"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 79: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 35 of 43

roadNumber1 Road Number 1.Identifies the number of the address in the road or thoroughfare and for a ranged address is the start number.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.

Start of Range Number of the road e.g. 29 Archer Street, where roadNumber1 is 2921-25 Archer Street, where roadNumber1 is 2135A Archer Street, where roadNumber1 is 35A

Length: 10

string 0..1

roadNumber2 Road Number 2.Identifies the last number for a ranged address in the road or thoroughfare.The data element may include an alphabetic prefix.The data element may include an alphabetic suffix.This data element is used for ranged street numbers otherwise it is left blank.End of Range Number of the street, e.g.21-25 Archer Street, where streetNumber2 is 2531-34A Archer Street, where roadNumber2 is 34A

Length: 10

string 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "35" [New text]: "36"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 80: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 36 of 43

roadName Road Name.The name of the road/thoroughfare applicable to the address site or complex.Only the road name should be stored in this data element.

Usage Examples:BROWNS ROAD WESTIn this case the Road name is BROWNS, the Road type is RD and the Road suffix is W

THE AVENUE WESTIn this case the Road name is THE AVENUE, the Road type is null and the Road suffix is W

COTSWOLD BRETTIn this case the Road Name is COTSWOLD BRETT and the Road type is null

HIGH STREET ROADIn this case the Road Name is HIGH STREET and the Road t type is RD.

Length: 100

string 1..1

roadTypeCode Road Type Code.The abbreviation code used to distinguish the type of road/thoroughfare applicable to the address site/complex.

Usage example:23 Archer RD, where RD is the the Road Type code for Road

Length: 10

RoadTypeCode 0..1

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "36" [New text]: "37"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 81: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 37 of 43

roadSuffixCode Road Suffix CodeThe abbreviation code used to represent the suffix of road/thoroughfare applicable to the address site/complex.

20-24 Genetics Lane North, where North is the roadSuffix = N

Length: 20

RoadSuffixCode 0..1

localityName Locality Name.The name of the locality/suburb of the address.

Length: 50

string 1..1

postcode Postcode.The Australian numeric descriptor for a postal delivery area, aligned with locality, suburb or place

Length: 10

string 0..1

stateTerritoryCode State Territory Code.The State or Territory code of the address.

Length: 3

StateTerritoryCodeType 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct

Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "37" [New text]: "38"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 82: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 38 of 43

DescribedBy These name value pairs will be used to communicate the results of the site qualification.Following is the list of names and associated values:1. PrimaryAccessTechnology: The value will contains either Fibre, Wireless or Interim Satellite. It is mandatory in the response to the Access Seeker.2. ServiceabilityClass: This value will contain one of the following numbers. It is not mandatory.0 - Planned to be serviced by Fibre in the future (boundary status isn’t ‘In Service’ yet)1 - Serviceable by Fibre, no drop or NTD in place2 - Serviceable by Fibre, drop in place, no NTD in place3 - Serviceable by Fibre, drop and NTD in place4 - Planned to be serviced by Wireless5 - Serviceable by Wireless, CPE not installed6 - Serviceable by Wireless, CPE installed7 - Planned to be serviced by Satellite8 - Serviceable by Satellite, VSAT Terminal and CPE not installed9 - Serviceable by Satellite, VSAT Terminal and CPE installed3. ServiceabilityDate: Expected date when you can successfully submit an order. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ. It is not mandatory.4. CSAID: Customer Service Area ID. This value will be a string. It is not mandatory.

CharacteristicValue 0..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct/DescribedBy

value Represents the value attribute in a name-value pair. string 0..1

Compare: Replace�
text
[Old text]: "contains" [New text]: "contain"
Compare: Insert�
text
"Wireless"
Compare: Delete�
text
"Wireless"
Compare: Insert�
text
"Seeker."
Compare: Delete�
text
"Seeker."
Compare: Move�
table cell
This table cell was moved from page 38 of this document to page 39 of new document
Compare: Move�
table cell
This table cell was moved to page 39 of new document
Compare: Move�
table cell
This table cell was moved from page 38 of this document to page 39 of new document
Compare: Move�
table cell
This table cell was moved to page 39 of new document
Compare: Insert�
text
"is mandatory in the response to the Access Seeker when"
Compare: Insert�
text
"PrimaryAccessTechnology"
Compare: Replace�
text
[Old text]: "not mandatory." [New text]: "either Fibre or Wireless."
Compare: Replace�
text
[Old text]: "isn’t ‘In" [New text]: "isn't 'In"
Compare: Replace�
text
[Old text]: "Service’" [New text]: "Service'"
Compare: Delete�
text
"not"
Compare: Replace�
text
[Old text]: "mandatory." [New text]: "mandatory in the response to the Access Seeker when"
Compare: Insert�
text
"PrimaryAccessTechnology is either Fibre or Wireless."
Compare: Move�
table cell
This table cell was moved from page 38 of this document to page 39 of new document
Compare: Move�
table cell
This table cell was moved to page 39 of new document
Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "38" [New text]: "39"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 83: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 39 of 43

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ItemInvolvesProduct/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem

ItemInvolvesProduct Contains NTD ID and its characteristics Product 1..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct

ID NTD IDLength: 15

string 1..1

DescribedBy This contain a name-value pairs to further describe the attributes related to each NTDThe following is the list of names and their values associated with NTD.1. NTDInstallDate: Date in the future when an NTD will be installed. If NTD is already installed or there is no plan to install an NTD, no date will be returned. The value will be a DateTime stamp in UTC format e.g. yyyy-mm-ddThh:mm:ssZ and the type field will be empty. It is not mandatory.2. NTDLocation: The value will be either INDOOR, OUTDOOR. It is not mandatory.3. NTDType: The value will be either INTERNAL, EXTERNAL. It is not mandatory.4. NTDPowerType: The value will be either AC,DC. It is not mandatory.5. BatteryPowerUnit: The value will be either Yes, No. It is not mandatory.6. BatteryPowerUnitMonitored: The value will be either ENABLED, DISABLED. It is not mandatory.7. UncommittedUpstreamBandwidth (This is the Capacity of the NTD in Megabits/second). It is not mandatory.8. UncommittedDownstreamBandwidth (This is the Capacity of the NTD in Megabits/second). It is not mandatory.9. UNI-D-1Status: The value will be either Used, Free. It is not mandatory.10. UNI-D-2Status: The value will be either Used, Free. It is not mandatory.11. UNI-D-3Status: The value will be either Used, Free. It is not mandatory.12. UNI-D-4Status: The value will be either Used, Free. It is not mandatory.13. UNI-V-1Status: The value will be either Used, Free. It is not mandatory.14. UNI-V-2Status: The value will be either Used, Free. It is not mandatory.

CharacteristicValue 1..*

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct/DescribedBy

Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Compare: Replace�
text
[Old text]: "1..*" [New text]: "0..*"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "39" [New text]: "40"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 84: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 40 of 43

value Represents the value attribute in a name-value pair. string 1..1

CharacteristicThe associated quality or distinctive feature that defines an entity

Characteristic 0..1

/ManageServiceQualificationResponse/ServiceQualification/ServiceQualificationComprisedOf/ReferencesServiceQualificationItem/ItemInvolvesProduct/DescribedBy/Characteristic

name Represents the name attribute in a name-value pair. string 1..1

Compare: Replace�
text
[Old text]: "0..1" [New text]: "1..1"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "40" [New text]: "41"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 85: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 41 of 43

Appendix A - List of Values

List of valuesProductOrder/orderType Version: V3.0

Connect Indicates the order is related to a Connect.

Disconnect Indicates the order is related to a Disconnect.

Modify Indicates the order is related to a Modify.

action Version: V3.0

ADD Indicates an Add action is being performed.

NO CHANGE Indicates No Change has occurred.

DELETE Indicates a Delete action is being performed.

MODIFY Indicates a Modify action is being performed.

ActivitySpecificationReferences/type Version: V3.0

Standard Install Indicates the appointment is for a Standard Install

ExceptionsThe code in the table below will be returned in the Exception\ID attribute. The description in the table will be returned in the Exception\description attribute.

InvalidProductException Version: V3.0

006000 The Product with the ID : %Product ID% specified in the request is invalid

NotAllowedException Version: V3.0

008000 The operation cannot be performed with the specified parameters: %parameter1%,%parameter2%, ....

TechnicalException Version: V3.0

000000 A technical error has occurred during the processing of the request.

ValidationException Version: V3.0

001000 The following mandatory field or fields are not provided: %field1%, %field2%, ....

001001 Field length of %fieldName% is invalid, the length provided is %providedLengthOfField% but it should be %acceptedLengthOfField%

001002 Data type mismatch on field %fieldName%

001003 Incorrect enumeration of %enumeration% provided for field %fieldName%

001004 Invalid parameter combination : %parameter1% cannot be provided with %parameter2%

001005 The following field or fields should not be provided for this operation: %field1%, %field2%,....

001006 The following technical issue or issues were found when validating the message: %technicalValidationReason1%. %technicalValidationReason2%. ...

001007 The specified %fieldName% is invalid due to the end date being before the start date

001008 The value specified in the field %fieldName% exceeds the maximum of %maximum allowed%

Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "41" [New text]: "42"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 86: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy

NBN Co OSS Program

SFAA - WBA - NBN Co Platform Interfacing Service - ManageServiceQualification V1.0 IFSDocument Version V1.9 © 2012 NBN Co Ltd 42 of 43

ExceptionsThe code in the table below will be returned in the Exception\ID attribute. The description in the table will be returned in the Exception\description attribute.

ValidationException Version: V3.0

001009 The value of %fieldName% is invalid as it is in the future.

001010 The number of occurrences for the following field %fieldName% exceeds the defined maximum occurrences of %maxOccurrences%

001011 At least one of the following fields must be provided: %field1%, %field2%

001012 The value for %field name% : %field value% is in an invalid format

InvalidAddressException Version: V3.0

012000 The NBN Location ID provided in the request : %NBN Location ID% does not result in a valid NBN Location Address match

012001 There are multiple matches for the address details provided in the request

012002 There are no matches for the address details provided in the request

InvalidOrderException Version: V3.0

005000 Order ID : %OrderID% is closed

005001 Order ID : %OrderID% is invalid or not found

005002 Order ID : %OrderID% is past the cancellation Point of No Return (cPoNR)

005003 Order ID : %OrderID% is past the amendment Point of No Return (aPoNR)

005004 Order ID : %OrderID% is already in progress of been amended

005005 Supplied NTD ID : %NTD ID% not found

005006 Attributes of the NTD in LNI do not match the attributes required by the order

AccountHierarchyViolationException Version: V3.0

002000 The Billing Account ID %Billing Account ID% does not belong to the Access Seeker

002001 The Product Instance ID : %ID% does not belong to the Access Seeker

AccountNotActiveException Version: V3.0

003000 The Billing Account with the ID : %Billing Account ID% is not active

003001 The Sell Flag is set to 'FALSE' for the Billing Account with the ID : %Billing Account ID%

Compare: Insert�
text
"005007"
Compare: Insert�
text
"Order ID : %OrderID% is not PENDING waiting on information from the Access Seeker"
Compare: Insert�
text
"- 2012/09/28"
Compare: Replace�
text
[Old text]: "V1.9" [New text]: "V2.4"
Compare: Replace�
text
[Old text]: "42" [New text]: "43"
Compare: Replace�
text
[Old text]: "43" [New text]: "44"
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Compare: Replace�
image
This image was replaced (click to see the new and difference images)
Page 87: Interface Functional Specification ... · V2.2 2012/06/11 Removed postcode from sample messages. V2.3 2012/07/05 Updated touchpoint descriptions to: - clarify the use of DescribedBy