Packages and products

What’s in an order

When placing an order, it is important to know about the order packages and products in the packages.

A package basically an aggregation of a set of products. Each package has a code and defining either administrative products or products technical of nature which influence the delivered service for an end user.

For example, when you’re ordering a VDSL2 line you may want to request an IPv4 subnet of size 8 and an EVC allowing 50 Mbit/s downstream. In that case the order will contain:

• A product for the line itself (technical)

• A product for the EVC (technical)

• A product with quantity 8 for the IP subnet (technical and administrative)

• A product for line setup costs (depending on the product package, technical)

For most cases, the A2B order system will determine which products to add to the order. In most cases, only a product defining the SLA and a product defining the EVC parameters will need to be specified.

Determining what to order

When you’d like to place an order for a DSL line of sorts (this may obviously well include FttH lines or other types of connections), you need to determine in advance which package and (EVC/SLA) products you need to order. To do that, you first need to perform an availability check with the Availability checker. The availability checker API will return either a list of packages and corresponding information, or it’ll return an empty list, meaning A2B can either deliver no products at the requested location, or requires a manual process including a quotation trajectory.

See the Availability checker documentation for more information.