Vetro - en

Description

The importation between Vetro and OZmap is conducted via API calls; we execute API calls to import elements into OZmap.

This documentation only addresses an initial import model. Import using different formats or adding more elements may be requested, subject to evaluation by the responsible team.

Once the importation is completed, reports are sent to the client containing all imported elements, and the reasons for any errors during importation, for elements that weren't imported.

Functionalities Summary

Import Settings and Customization

Types Import

Elements Import

Functionalities

As follows, we’ll describe the functionalities of the import service between Vetro and OZmap, allowing a better understanding of the importation flow.

Settings and Customization Imports

Settings and customization imports from Vetro are performed to ensure that the data utilizing them (Cable and Box Types, Properties, Clients, Poles, etc.) can be created with identical customizations in OZmap. The imports occur as follows:

• System Settings: System settings including POP Levels, Box Levels, and Cable Levels, are imported.

  • For each layer concerning box, cable, and POP labels found in Vetro, a corresponding level is created in OZmap if one containing the same name does not already exist.

  • The imported levels in OZmap will be created following the already existing hierarchies in OZmap.

• Fiber profiles: All fiber profiles from Vetro are fully imported into OZmap, even if identical profiles (name and specificities) already exist.

• Box Templates: By default, all imported boxes from Vetro will receive an “Empty” template.

• Tags: Tags named “house” and “office” will be created in OZmap to replace the client type classification used by Vetro.

IMPORTANT: Even if the client selects specific projects for importation from Vetro to OZmap, ALL items described in this section will be imported to OZmap, regardless of their usage in the selected projects.

Types Import

Type imports from Vetro are performed to enable data that utilizes them (Cables, Boxes, Splitters, Poles, etc.) to be created in OZmap. The imports occur as follows:

• ODF Types: ODF types are imported during ODF importation, with the type name in OZmap defined by the number of ports the ODF has in Vetro.

  • For example, if a ODF has "12" ports in Vetro, a type named "12" will be created in OZmap.

• POP Types: All POP types from Vetro are fully imported into OZmap, with the type name defined by the Layer name used in Vetro.

  • Includes mandatory importation of:

    • System Settings, as each Vetro Layer has an equivalent POP level in OZmap.

• Splitter Types: Splitter types are imported during Splitter importation, with the type code in OZmap defined by the "placement" name and the number of ports in Vetro.

• Pole Types: All pole types from Vetro are fully imported into OZmap, with the type name defined by the Layer name used in Vetro.

• Box Types: All box types from Vetro are fully imported into OZmap, with the type name defined by the Layer name used in Vetro.

  • Includes mandatory importation of:

    • System Settings, as each Vetro Layer has an equivalent box level in OZmap.

• Cable Types: Cable types are imported during cable importation, with the type code in OZmap defined by the "placement" name, the "label" name, and the "loose" and "fiber" quantities in Vetro.

  • Includes mandatory importation of:

    • Fiber Profiles, as each Vetro Layer has an equivalent cable level in OZmap.

IMPORTANT: Even if the client selects specific projects for importation from Vetro to OZmap, ALL items described in this section will be imported to OZmap, regardless of their usage in the selected projects.

Elements Import

Element imports from Vetro aim to replicate documentation elements, either fully or partially. Element imports from Vetro occur as follows:

• 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

• Cabos: Todos os cabos do Vetro são importadas para o OZmap a partir da layer de cabos, replicando as características no OZmap.

  • O nome do cabo OZmap será o ID caso exista, ou o nome do cabo no Vetro.

  • Os pontos do cabo OZmap serão os mesmos do Vetro.

  • Se o cabo estiver em “build” no Vetro, ele será criado como implantado no OZmap. Caso contrário, o cabo será criado como não implantado no OZmap.

  • As pontas dos cabos OZmap serão as mesmas pontas do Vetro.

  • Inclui obrigatoriamente as importação de:

    • Tipos de Cabo

  • Pode depender da importação de:

    • Caixas, Condomínios, POPs e Imóveis

• Splitters: Todos os splitters do Vetro são importadas para o OZmap a partir da layer de splitters, replicando as características no OZmap.

  • O nome do splitter OZmap será o ID do Vetro.

  • A caixa do splitter OZmap sera a mesma do Vetro.

  • A observação do splitter OZmap será a nota do Vetro.

  • Se o splitter estiver em “build” no Vetro, ele será criado como implantado no OZmap. Caso contrário, o splitter será criado como não implantado no OZmap.

  • Por padrão, os splitters serão criados no OZmap com o atributo “Permitir Conexões de Clientes” sendo falso.

  • Inclui obrigatoriamente as importação de:

    • Tipos de Splitter

  • Pode depender da importação de:

    • Caixas, Condomínios e POPs

• DIOs: Todos os DIOs do Vetro são importadas para o OZmap a partir da layer de dios, replicando as características no OZmap.

  • O nome do DIO OZmap será o ID do Vetro.

  • A caixa ou a POP do DIO OZmap sera a mesma do Vetro.

  • A observação do DIO OZmap será a nota do Vetro.

  • Se o DIO estiver em “build” no Vetro, ele será criado como implantado no OZmap. Caso contrário, o DIO será criado como não implantado no OZmap.

  • Inclui obrigatoriamente as importação de:

    • Tipos de DIO

  • Pode depender da importação de:

    • Caixas

• Conexões Internas de Caixas: Todas as conexões internas de caixas do Vetro são importadas para o OZmap.

  • As conexões internas de caixas se referem as ligações entre elementos dentro de uma caixa, como conexões entre cabos, entre splitters e cabos, e entre splitters e splitters por exemplo.

  • Pode depender da importação de:

    • Cabos e Splitters

• Reservas Técnicas: Todos as reservas técnicas do Vetro são importadas para o OZmap a partir da layer de reservas tecnicas, replicando as características no OZmap.

  • Pode depender da importação de:

    • Cabos

LEGENDA:

“Inclui obrigatoriamente as importação de” - São outros elementos que também precisarão ser importados juntamente com o elemento selecionado pelo cliente no questionário.

“Pode depender da importação de” - São outros elementos que, caso não ser sejam importados, podem impedir a criação dos elementos em questão. Por exemplo: Na importação de caixas, caso uma caixa esteja alocada em um poste no Vetro, e esse poste não tiver sido importado previamente para o OZmap por algum motivo, a caixa não poderá ser criada no OZmap também.

Configurações Base

Elementos

Dados Acesso

https://forms.gle/dSzz7Mcyiy9uUDJt9

Dados de acesso necessários para buscar informações via API nos sistemas Vetro e OZmap. (Estes dados devem ser fornecidos no questionário inicial).

OZmap

Vetro

Dúvidas frequentes