{"id":1489,"date":"2020-03-06T23:11:12","date_gmt":"2020-03-06T23:11:12","guid":{"rendered":"https:\/\/support.mpsoftwarecmms.com\/?page_id=1489"},"modified":"2024-07-31T12:06:55","modified_gmt":"2024-07-31T18:06:55","slug":"ligar-planes-de-mantenimiento-a-equipos-y-localizaciones","status":"publish","type":"page","link":"https:\/\/support.mpsoftwarecmms.com\/en_us\/ligar-planes-de-mantenimiento-a-equipos-y-localizaciones\/","title":{"rendered":"Bind maintenance plans for equipment and locations"},"content":{"rendered":"
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\r\n
\r\n\t
\r\n\t\t

Home<\/a> \/ Maintenance management<\/a><\/p>\n

Bind maintenance plans for equipment and locations<\/strong><\/h2>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Index<\/strong>
\n<\/a><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Bind maintenance plans<\/a>
\nTo link a maintenance plan with activities with the regime of readings<\/a>
\nDesligar maintenance plans<\/a>
\nAlerts related to maintenance plans<\/a>
\nAlert computers without linked plan<\/a>
\nWarning of maintenance plans without assigning it to a computer or location<\/a><\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/span><\/span><\/span><\/span><\/span>
<\/div><\/div>\n\t\t\t
\n\t\t\t\t
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\r\n
\r\n\t
\r\n\t\t

Related topics<\/h4>\n

\u25b8 Introduction to maintenance plans<\/a>
\n\u25b8 Basic elements of a maintenance plan (Parties, activities, and frequency)<\/a>
\n\u25b8 Submenu of the catalog maintenance plans<\/a>
\n\u25b8 Add a maintenance plan<\/a>
\n\u25b8 Parts and activities of the plan<\/a>
\n\u25b8 Notes and attachments of the plan<\/a>
\n\u25b8 Add another maintenance plan as<\/a>
\n\u25b8 Edit a maintenance plan<\/a>
\n\u25b8 Delete a maintenance plan<\/a>
\n\u25b8 Add parts<\/a>
\n\u25b8 Edit parts<\/a>
\n\u25b8 Delete parts<\/a>
\n\u25b8 Copy and paste parts<\/a>
\n\u25b8 Insert a maintenance plan within another<\/a>
\n\u25b8 Add activities<\/a>
\n\u25b8 Edit activities<\/a>
\n\u25b8 Frequency of activities<\/a>
\n\u25b8 Priority of activities<\/a>
\n\u25b8 Duration of the activities<\/a>
\n\u25b8 Strike team<\/a>
\n\u25b8 Classification of activities<\/a>
\n\u25b8 Activities that involve the taking of a measurement (predictive Maintenance)<\/a>
\n\u25b8 Procedure to perform the activities<\/a>
\n\u25b8 Safety notes, images, and attachments of activities<\/a>
\n\u25b8 Requirements to close or include activities in OT<\/a>
\n\u25b8 Delete activities<\/a>
\n\u25b8 Copy-and-paste activities<\/a><\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t

<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t
<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n\t\t
<\/i><\/div>\r\n\t<\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n\t\t
<\/i><\/div>\r\n\t<\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n\t\t
<\/i><\/div>\r\n\t<\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n\t\t
<\/i><\/div>\r\n\t<\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\r\n
\r\n\t
\r\n\t\t

Bind maintenance plans<\/strong><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>
<\/span><\/span>

The scheduled maintenance of equipment or location, starts from the association of a computer with its own maintenance plan.<\/h4><\/span><\/span>\n<\/div>
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

To begin the programming of the routine maintenance of equipment or a location, they must bind first with the maintenance plan that corresponds to them.<\/p>\n

To handle routine maintenance, it is necessary to link each computer or location with a maintenance plan, as the plan of maintenance (teacher) is the one that contains the information about the routine activities that must be performed.<\/p>\n

A maintenance plan can be used to govern the routine maintenance of multiple computers or locations related to the plan. This avoids the need to capture the same plan multiple times for teams or locations related.<\/p>\n

Example of a league of teams and locations with maintenance plans.<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>
<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>
<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

To link a maintenance plan to computers or locations, choose in the catalog of plans, the plan that you want to link their computers or locations, and then click on the action\u00a0<\/a>Bind maintenance plan<\/strong> teams or locations from the submenu.<\/p>\n

Check the equipment or locations that you want to link to the plan previously selected, and then click\u00a0<\/a>Following<\/strong>. If you are ligand a maintenance plan that contains activities controlled by the readings, the system prompts you to type in the last read-known of the equipment and your average monthly usage for <\/a>finish\u00a0<\/strong>with the league.<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
\r\n\t\t
<\/i><\/div>\r\n\t<\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

In the same way it is possible to link maintenance plans, equipment, or locations from their respective modules. Select one or more computers or locations according to the module in which it is found, click the submenu Bind maintenance plan<\/strong> and follow the on-screen instructions.
\nIn the column Plan assigned<\/strong>the user can enter in each cell the name of the plan that you want to assign to the computer. You can also select multiple records from the list and assign them to the same plan with the button Assign plan to selected computers.<\/strong><\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\r\n
\r\n\t
\r\n\t\t

To link a maintenance plan with activities with the regime of readings<\/strong><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\r\n
\r\n\t
\r\n\t\t

We have seen that the frequency with which it must be an activity can be set by time or by readings (Example, kilometers, hours of use, parts produced etc).<\/p>\n

When a maintenance activity is controlled by the regime of readings or mixed, the control is more accurate since it is directly dependent on the use of the computer and not only on the elapsed time. However, the control reads and mixed it a little bit more complex, since it forces the user to register is periodically read of use that mark an odometer, clock, hour meter, etc the same way, to be able to predict a tentative date of completion of the activity, it is necessary to indicate in these cases a\u00a0average monthly usage estimate.<\/a><\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n
\r\n\t
\r\n\t\t

NEXT ROUTINE MAINTENANCE \u2013 READINGS<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>

<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n
\r\n\t
\r\n\t\t

NEXT ROUTINE MAINTENANCE \u2013 READINGS<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>

<\/div><\/div>
<\/span><\/span>

Therefore, when linking a maintenance plan controlled by the readings, the system prompts the user to type in the last read-known of the equipment and your average monthly usage. For more information concerning the control for readings click here.<\/h4><\/span><\/span>\n<\/div>
<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\r\n
\r\n\t
\r\n\t\t

Desligar maintenance plans<\/strong><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

At the time of decoupling a plan of maintenance of a computer or location, will be deleted from the measurement history, resources (labor, outside services and tools), and readings associated with them, and it will not be possible to register new values to flirt back with a plan.<\/p>\n

From the catalog maintenance plans, select the maintenance plan that you want to disassociate from the computer or location and then click action Desligar maintenance plan<\/strong> from the submenu.<\/p>\n

A list will appear with the equipment or locations that are linked to the plan that was previously selected. Check the computer or location that you want to unlink, and then click Desligar plan.<\/strong><\/p>\n

Note:<\/strong> To unlink a maintenance plan must ensure that none of the activities of the plan assigned to the computer or location is in an OT open. You will be able to continue recording the maintenance, non-routine equipment or locations that do not have plan assigned.<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t\r\n
\r\n\t
\r\n\t\t

Alerts related to maintenance plans
\n<\/strong><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

To link equipment and locations with their respective plans of maintenance is critical for the control of routine maintenance. Do not just add teams and structure maintenance plans in the system, it is very important to them to define the start of the maintenance work and the schedule of upcoming dates that will be performed each of the activities that we include in the plan. For this reason, the system has the following alerts:<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Alert computers without a plan assigned
\n<\/strong>Displays a list of all the computers that have not been associated with a maintenance plan.<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>
<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>
<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Warning of maintenance plans without assigning it to a computer or location
\n<\/strong>Displays a list of all the maintenance plans that have not been associated with equipment or locations.<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>
\r\n
\r\n
\r\n
\r\n \r\n \"\"\r\n <\/a>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>
<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\r\n
\r\n\t
\r\n\t\t

Can't find the answer to your doubts or questions?<\/h1>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t
<\/div><\/div>
<\/div><\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t\t
\n\t\t\t\t
<\/div> <\/div>
\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Additionally, we offer training courses<\/strong><\/h2>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

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.<\/span><\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

<\/div><\/div>\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n\n\t
\n\t\t
<\/div><\/div>\n\t\t
\n\t\t\t
<\/div><\/div>Contact us<\/span><\/a>\r\n
\r\n\t
\r\n\t\t


\n

\r\n \r\n
\u00d7<\/span>
\r\n \r\n

Consideration if you are going to use the engine for Firebird database<\/strong><\/h4>\r\n\t\t\t

\r\n

However, the excellent performance that this database engine provides, it is important to take into account that this database engine is only recommended for users that do NOT want to use the mobile applications MPsolicitudes or MPmobile, because these APPs ARE NOT COMPATIBLE WITH THE ENGINE FIREBIRD DATABASES.<\/p>\r\n \r\n <\/div>\r\n<\/div>
\n

\r\n \r\n
\u00d7<\/span>
\r\n \r\n

Name of the database and its location.<\/strong><\/h4>\r\n\t\t\t

\r\n

Regarding the name of the database: The name that you define can't wear white space, and the number of characters allowed maximum is 25, for example Maintenance Plant 1 instead use Hyphens or underscores this: Mantenimiento_Planta_1, in addition to it is not allowed that the name of your database-carry special characters such as these: \u00a1 " # , $ % & ( \u00bf ) ? } { The reason for this is that there are some rules or policies that the database engines prohibit the use of these characters.<\/p>\r\n\t\t\t\t\t\r\n\t\t\t

You'll have another field of up to 50 characters that will allow a broader description and complete database.<\/p>\r\n\t\t\t

Example:<\/p>\r\n\t\t\t\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Name of the database<\/strong><\/td>\r\nName of the access to the database<\/strong><\/td>\r\nLong description of the database<\/strong><\/td>\r\n<\/tr>\r\n
PLANTA_SPEREN_1<\/td>\r\nACCESS TO PLANTA_SPEREN_1<\/td>\r\nPLANT SPEREN PARQUE INDUSTRIAL EXPORTEC II<\/td>\r\n<\/tr>\r\n
PLANTA_SPEREN_2<\/td>\r\nACCESS TO PLANTA_SPEREN_2<\/td>\r\nPLANT SPEREN PARQUE INDUSTRIAL HUEHUETOCA<\/td>\r\n<\/tr>\r\n
PLANTA_SPEREN_3<\/td>\r\nACCESS TO PLANTA_SPEREN_3<\/td>\r\nPLANT SPEREN INDUSTRIAL PARK JILOTEPEC<\/td>\r\n<\/tr>\r\n
HOTEL_Mara_A<\/td>\r\nACCESS TO HOTEL_Mara_A<\/td>\r\nHotel All Inclusive Mara Place, Cancun, QR<\/td>\r\n<\/tr>\r\n
HOTEL_Mara_B<\/td>\r\nACCESS TO HOTEL_Mara_B<\/td>\r\nGran Executive Hotel Mara Place mexico City, Mexico<\/td>\r\n<\/tr>\r\n
HOSPITAL_TRAUMATOLOGIA<\/td>\r\nACCESS TO HOSPITAL_TRAUMATOLOGIA<\/td>\r\nHospital of Traumatology Loma Verdes, Naucalpan<\/td>\r\n<\/tr>\r\n
HOSPITAL_NEUROLOGIA<\/td>\r\nACCESS TO HOSPITAL_NEUROLOGIA<\/td>\r\nNational institute of Neurology and Neurosurgery, CDMX<\/td>\r\n<\/tr>\r\n
FLOTILLA_1<\/td>\r\nACCESS TO FLOTILLA_1<\/td>\r\nFleet Cars and trucks SPEREN EXPORTEC II<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n\t\t\t

After you've created your databases in the MP, these are hosted on the Database Server that you've chosen. For example, the databases created by the streamlined staying in your computer, the path in which you can find is C:\\Windows\\SysWow64 or C:\\Windows\\System32. Regularly are Files with the Extension.FDB<\/p>\r\n\t\t\t

The databases created in the following types of databases: MariaDB, MySQL, SQL-Server, MPcloud and Oracle does not generate Files. The information is stored in multiple tables of schema information, or in special environments of your server.<\/p>\r\n\t\t\t

Regardless of the type of database Server that you manage, we recommend to make backups of your information frequently so that you get a receipt of your information as a preventive measure in case of an emergency, see the section Backup and restore a database.<\/p>\r\n \r\n <\/div>\r\n<\/div>
\n

\r\n \r\n
\u00d7<\/span>
\r\n \r\n\t\t

Server IP, user name and password of the database engine<\/strong><\/h3>\r\n\t\t

\r\n\r\n

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.<\/p>\r\n\r\n

For example:<\/p>\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
DATABASE ENGINE<\/strong><\/td>\r\nADMINISTRATOR USER BY DEFAULT<\/strong><\/td>\r\nPASSWORD\r\n<\/strong>(Known only to the manager of IT)<\/strong><\/td>\r\n<\/tr>\r\n
MySQL<\/td>\r\nroot<\/td>\r\n******<\/td>\r\n<\/tr>\r\n
Microsoft SQL-Server<\/td>\r\nsa<\/td>\r\n******<\/td>\r\n<\/tr>\r\n
Oracle<\/td>\r\nSystem<\/td>\r\n******<\/td>\r\n<\/tr>\r\n
MariaDB<\/td>\r\nroot<\/td>\r\n******<\/td>\r\n<\/tr>\r\n
Firebird<\/td>\r\nSYSDBA<\/td>\r\n******<\/td>\r\n<\/tr>\r\n<\/table>\r\n

When you create a database, or a new connection on the MP, the program prompts you for the server name or IP where you will create or is the database to which you want to connect to, as well as a user name and password.<\/p>\r\n

The username and password that here we ask, are precisely those that allow access to the <\/em>database engine <\/em>permissions privileges to create the database. <\/em><\/h4>\r\n

\r\n\t\t\t\r\n

\r\n

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.<\/p>\r\n\r\n

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.<\/em><\/h4>\r\n

A single user account to the database engine is sufficient for the creation and connection of multiple databases.<\/p>\r\n\r\n

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.<\/p>\r\n\t\t \r\n <\/div>\r\n<\/div>
\n

\r\n \r\n
\u00d7<\/span>
\r\n \r\n\t\t

What is a access to the database?<\/strong><\/h3>\r\n\t\t

\r\n\r\n

When you create a database, it automatically creates an access to the database. Access is a file that contains encoded all information regarding the IP address or name of the server where the database resides. This information is also recorded in a QR code, which will facilitate the connection of mobile devices to the database.<\/p>\r\n\t\t \r\n <\/div>\r\n<\/div>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n\n\t\t<\/div> \n\t<\/div>\n\t<\/div> \n<\/div><\/div>\n\t\t\t<\/div> \n\t\t<\/div>\n\t<\/div> \n<\/div><\/div>","protected":false},"excerpt":{"rendered":"Inicio \/ Gesti\u00f3n de mantenimiento Ligar planes de mantenimiento a equipos y localizaciones \u00cdndice Ligar...","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages\/1489"}],"collection":[{"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/comments?post=1489"}],"version-history":[{"count":45,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages\/1489\/revisions"}],"predecessor-version":[{"id":7489,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages\/1489\/revisions\/7489"}],"wp:attachment":[{"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/media?parent=1489"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}