{"id":1356,"date":"2020-03-06T00:52:31","date_gmt":"2020-03-06T00:52:31","guid":{"rendered":"https:\/\/support.mpsoftwarecmms.com\/?page_id=1356"},"modified":"2023-11-20T21:31:19","modified_gmt":"2023-11-21T03:31:19","slug":"tipo-de-equipo-y-tipo-de-falla","status":"publish","type":"page","link":"https:\/\/support.mpsoftwarecmms.com\/en_us\/tipo-de-equipo-y-tipo-de-falla\/","title":{"rendered":"Tipo de equipo y tipo de falla"},"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

Type of equipment and type of fault for the failure analysis and root cause<\/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

Cat\u00e1logo auxiliar de tipos de equipo y fallas<\/a>
\nCat\u00e1logo auxiliar de causas de falla<\/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<\/strong><\/h4>\n

\u25b8 What is a working non-routine?<\/a>
\n\u25b8 Process to register and attend a working non-routine<\/a>
\n\u25b8 Record and Edit a job is not routine<\/a>
\n\u25b8 Generate work order for non-routine work<\/a>
\n\u25b8 Historial de trabajos no rutinarios<\/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\r\n
\r\n\t
\r\n\t\t

El An\u00e1lisis de Fallas y Causa Ra\u00edz es un m\u00e9todo que permite al administrador del mantenimiento conocer los equipos que m\u00e1s fallan presentan, el tipo de falla m\u00e1s recurrente y las causas ra\u00edz de dichas fallas, ayud\u00e1ndolo a tomar acciones correctivas tendientes a atacar los problemas partiendo de los m\u00e1s recurrentes o de mayor impacto.<\/p>\n

En el m\u00f3dulo de An\u00e1lisis de Informaci\u00f3n, el MP agrupa y organiza la informaci\u00f3n hist\u00f3rica de tal forma que le ser\u00e1 sencillo identificar las fallas m\u00e1s recurrentes y su causa ra\u00edz, pero para ello es necesario que al momento de registrar una falla o indicar que la falla ha sido atendida, capture la informaci\u00f3n referente al tipo de equipo y tipo de falla.<\/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 <\/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 <\/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>\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

Cat\u00e1logo auxiliar de tipos de equipo y fallas<\/strong><\/h4>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n
<\/div><\/div>
<\/span><\/span>

El cat\u00e1logo auxiliar de Tipo de Falla se organiza formando grupos. Cada grupo corresponde a un Tipo de Equipo diferente.<\/h4><\/span><\/span>\n<\/div>
<\/div><\/div>\r\n
\r\n\t
\r\n\t\t

Cabe mencionar que no es necesario contar con un cat\u00e1logo de tipos de falla previo. Paulatinamente, conforme se van presentando las fallas, podr\u00e1 ir formando el cat\u00e1logo auxiliar de tipos de falla<\/p>\n\t<\/div>\r\n<\/div>\r\n\r\n\r\n\r\n

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

Si al momento que registramos la falla no contamos con informaci\u00f3n referente al tipo de falla, la causa ra\u00edz, da\u00f1o causado, etc., podemos complementar la informaci\u00f3n al momento de reportar que el trabajo ya se realiz\u00f3 (Actualizar la OT).<\/h4><\/span><\/span>\n<\/div>
<\/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
\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>\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

Cat\u00e1logo auxiliar de causas de falla<\/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

Por otro lado, tenemos tambi\u00e9n un Cat\u00e1logo auxiliar de causas de falla. Dicho cat\u00e1logo es general para todo tipo de fallas. Adicional al registro del tipo de falla, debe indicarse la causa de la falla seleccionada del siguiente cat\u00e1logo.<\/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\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
<\/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 Tipo de equipo y tipo de falla para el an\u00e1lisis...","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\/1356"}],"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=1356"}],"version-history":[{"count":16,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages\/1356\/revisions"}],"predecessor-version":[{"id":7249,"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/pages\/1356\/revisions\/7249"}],"wp:attachment":[{"href":"https:\/\/support.mpsoftwarecmms.com\/en_us\/wp-json\/wp\/v2\/media?parent=1356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}