Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Functionality

Description

Project Import

IImport Import all or selected projects from Vetro.

The project will be imported as an empty project, not having without any elements and with the same area settings as in Vetro.

Pole Import

Import all or selected poles from Vetro projects.

Box Import

Import all or selected boxes from Vetro projects.

Vertical Buildings Import

Import all or selected vertical buildings from Vetro projects.

Properties and Clients Import

Import all or selected properties and clients from Vetro projects.

POP Import

Import all or selected POPs from Vetro projects.

Cables Import

Import all or selected cables from Vetro projects.

Splitter Import

Import all or selected splitters from Vetro projects.

ODFs Import

Import all or selected ODFs from Vetro projects.

Technical Reserves (Spares) Import

Import all or selected technical reserves from Vetro projects.

Boxes Internal Connections Import

Import all or selected internal connections in boxes from Vetro projects.

...

  • Projects: All selected projects from Vetro are imported into OZmap, replicating their characteristics in OZmap.

    • The importation only covers the project element information. All items within a Vetro project are imported separately through other element imports.

    • The OZmap project name will be the same as in Vetro.

    • The latitude and longitude of the OZmap project will be the same as in Vetro.

    • The coordinate area of the OZmap project will be the same as in Vetro.

  • Poles: All poles from Vetro are imported into OZmap from the pole layer, replicating their characteristics in OZmap.

    • Poles do not have a project in OZmap, but they do in Vetro. If the client requests the importation of selected projects only, only the poles from the selected project will be imported.

    • The OZmap pole name will be the Vetro pole ID. If there are multiple poles with the same name in Vetro, a number will be added after the pole name in OZmap to avoid duplicate name errors

    • The OZmap pole coordinates will be the same as in Vetro.

    • The OZmap pole observation will be the Vetro note.

    • Includes mandatory importation of:

      • Pole Types

  • Boxes: All boxes from Vetro are imported into OZmap from the box layer, replicating their characteristics in OZmap.

    • The OZmap box name will be defined by the ID or existing name in Vetro. If there are multiple boxes with the same name in Vetro, a number will be added after the box name in OZmap to avoid duplicate name errors.

    • The OZmap box type will be the same as in Vetro.

    • The OZmap box coordinates will be the same as in Vetro.

    • If the box is in “build” in Vetro, it will be created as implanted in OZmap. Otherwise, it will be created as Not implanted in OZmap.

    • The OZmap box observation will be the Vetro note.

    • Includes mandatory importation of:

      • Box Types

  • Vertical Buildings: All condominiums from Vetro are imported into OZmap from the customer layer, identified by the building type, replicating their characteristics in OZmap.

    • The OZmap condominium name will be defined by the ID or company name in Vetro. If there are multiple buildings with the same name in Vetro, a number will be added after the name in OZmap to avoid duplicate name errors.

    • The OZmap condominium coordinates will be the same as in Vetro.

    • If the condominium is in “build” in Vetro, it will be created as implanted in OZmap. Otherwise, it will be created as Not implanted in OZmap.

    • The OZmap condominium observation will be the Vetro note.

  • Properties and Clients: All properties and clients from Vetro are imported into OZmap from the customer layer, replicating their characteristics in OZmap.

    • The OZmap client code will be the Vetro ID. If there are multiple clients with the same code in Vetro, a number will be added after the code in OZmap to avoid duplicate code errors.

    • The OZmap client name will be the company name of the property in Vetro.

    • If the property is in “build” in Vetro, it will be created as Implanted in OZmap. Otherwise, it will be created as Not implanted in OZmap.

    • The OZmap property coordinates will be the same as in Vetro.

    • The OZmap property observation will be the Vetro note.

  • POPs: All POPs from Vetro are imported into OZmap from the pops layer, replicating their characteristics in OZmap.

    • The OZmap POP name will be defined by the ID or POP name in Vetro. If there are multiple POPs with the same name in Vetro, a number will be added after the name in OZmap to avoid duplicate name errors.

    • If the POP is in “build” in Vetro, it will be created as Implanted in OZmap. Otherwise, it will be created as Not implanted in OZmap.

    • The OZmap POP coordinates will be the same as in Vetro.

    • The OZmap POP observation will be the Vetro note.

    • Includes mandatory importation of:

      • POP Types

  • Cables: All cables from Vetro are imported into OZmap from the cable layer, replicating the characteristics in OZmap.

    • The name of the OZmap cable will be the ID if it exists, or the cable name in Vetro.

    • The points of the OZmap cable will be the same as in Vetro.

    • If the cable is in “build” in Vetro, it will be created as Implanted in OZmap. Otherwise, the cable will be created as Not Implanted in OZmap.

    • The ends of the OZmap cables will be the same as the ends in Vetro.

    • Includes mandatory importation of:

      • Cable Types

    • May depend on the importation of:

      • Boxes, Condominiums, POPs, and Properties.

  • Splitters: All splitters from Vetro are imported into OZmap from the splitter layer, replicating the characteristics in OZmap.

    • The name of the OZmap splitter will be the ID from Vetro.

    • The box of the OZmap splitter will be the same as in Vetro.

    • The observation of the OZmap splitter will be the note from Vetro.

    • If the splitter is in “build” in Vetro, it will be created as Implanted in OZmap. Otherwise, the splitter will be created as Not Implanted in OZmap.

    • By default, splitters will be created in OZmap with the attribute “Allow Client Connection” set to false.

    • Includes mandatory importation of:

      • Splitter Types

    • May depend on the importation of:

      • Boxes, Condominiums and POPs.

  • ODFs: All DIOs ODFs from Vetro are imported into OZmap from the DIO layer, replicating the characteristics in OZmap.

    • The name of the OZmap ODF will be the ID from Vetro.

    • The box or the POP of the OZmap ODF will be the same as in Vetro.

    • The note of the OZmap ODF will be the note from Vetro.

    • If the ODF is in “build” in Vetro, it will be created as Implanted in OZmap. Otherwise, the ODF will be created as Not Implanted in OZmap.

    • Includes mandatory importation of:

      • ODF Types

    • May depend on the importation of:

      • Boxes

  • Internal Box Connections: All internal box connections from Vetro are imported into OZmap.

    • Internal box connections refer to connections between elements within a box, such as connections between cables, between splitters and cables, and between splitters and splitters.

    • May depend on the importation of:

      • Cables and Splitters

  • Technical Reserves (SPAREs): All technical reserves from Vetro are imported into OZmap from the technical reserves layer, replicating the characteristics in OZmap.

    • May depend on the importation of:

      • Cables

...