Related topics
▸ Introduction to the catalogue of locations/real estate
▸ Submenu of the catalog of locations/real estate
▸ Add a location/building
▸ Add another location/property equal
▸ Edit a location/building
▸ Additional information locations/real estate
▸ Cost center locations/real estate
▸ Images, attachments, and notes of locations/real estate
▸ Delete a location/building
Introduction to the tree of locations and equipment
El árbol de localizaciones y equipos es un diagrama de árbol que representa de forma sencilla la ubicación de cada uno de los equipos e inmuebles dados de alta en SVISION. Incluso es posible identificar cuáles son los equipos padre e hijo, al igual que aquellos que no cuentan con una localización fija. Dentro del árbol de localizaciones y equipos es posible consultar la distribución de equipos en su planta, así como editar la ubicación de los equipos y localizaciones a voluntad.
Relate teams up with his physical location
In the Submenu of Locations/real Estate and in the submenu of equipment you will find an action called Tree of locations and equipment it provides an overview of his plant and the location of their computers in different areas. From there you will be able to relocate their equipment and move locations with a lot of ease.
Because a computer can be a part of a larger team establishing a dependency between team dad and team child, where the child automatically adopts the location of your team, father, this dependence is also displayed in the module mentioned, and from it we will be able to relocate the equipment and locations easily.
Note: When you edit a team in the assets module, we can relate that to the team with your location corresponding, leaving this documented the location of each of the teams.
Teams without a fixed location
Sometimes there are equipment that by its nature cannot be assigned a fixed location, for example cars.
For this purpose it is possible to assign the status of “No fixed location” and it will not be necessary to assign a location within the company.
A history of locations
La localización forma parte de la información de un equipo y está sujeta a modificación o edición cuando movemos o pasamos un equipo físicamente a una localización diferente. Cuando esto sucede, se guarda un historial que nos permite consultar en forma cronológica las diferentes localizaciones en las que ha estado ubicado un equipo.
Select a team in the Module Equipment and under the action of the submenu History select History of Locations.
Selecciona los Equipos
Ingresa al Submenú
Visualiza los registros
Can't find the answer to your doubts or questions?
Additionally, we offer training courses
Our flexible options of online training and face-to-face will provide you with all the knowledge necessary to understand and implement your software maintenance.
Contact us
×
Server IP, user name and password of the database engine
Today, virtually all companies have at least one IT professional who is responsible for, among many other functions to manage the data and servers of the company. Among their functions include the administration of a database engine, which, for security reasons, has access by means of a user name and a password. If not, any person could enter the network, and provide high-databases, query, modify and even delete confidential information of the company.
For example:
| DATABASE ENGINE | ADMINISTRATOR USER BY DEFAULT | PASSWORD (Known only to the manager of IT) |
| MySQL | root | ****** |
| Microsoft SQL-Server | sa | ****** |
| Oracle | System | ****** |
| MariaDB | root | ****** |
| Firebird | SYSDBA | ****** |
Al momento de crear una base de datos o una conexión nueva en SVISION, el programa solicita el nombre del servidor o IP en donde se creará o se encuentra la base de datos a la cual deseas conectarte, así como un nombre de usuario y su contraseña.
The username and password that here we ask, are precisely those that allow access to the database engine permissions privileges to create the database.
Now, the administrator of the database can also create different user accounts to allow access to more people by giving them privileges and permissions custom.
With the aim of not to use the administrator user of IT and its respective password each time that the department of maintenance required to create a database or a connection to an existing database, it is recommended that the IT administrator create a user account specifically for the maintenance department.
A single user account to the database engine is sufficient for the creation and connection of multiple databases.
The username and password that here is requested, you do not have any relationship with the licenses of use are acquired or the amount of users that can access the database, so that a single user account can be enough, because in this case it refers specifically to the user and password of the database engine.
EN_US 
ES_MX