-
The HMS application will not contain individual records for the equipment owned by EAM.
-
Any activity in HMS or EAM that impacts the room (ROOM) will be synchronized between systems (i.e., new HMS rooms will be created in EAM and any room updates in HMS will be synchronized to EAM).
-
HMS will have the ability to create new rooms and to set them as active and inactive. Data will be transmitted from HMS to EAM; transmitted data includes the equipment ROOM, LOCATION, STATUS. EAM will create a new equipment record for the room. This record may require additional data elements be populated to fulfill the system requirements for a new equipment record.
-
EAM will not have the ability to create guest or event rooms
-
EAM will not have the ability to update room attributes that are configured in HMS.
-
Updates to room STATUS will be controlled by HMS. Room LOCATION information from HMS will be interfaced to read-only fields on the room record in EAM. These fields will be protected on the EAM work order.
-
Changes to room attributes will be transmitted from HMS to EAM. Guest information is also sent from HMS to EAM when there is a guest check-in or check-out.
-
No data will be transmitted from EAM to HMS for room updates (since information stored on the Room in EAM that is also stored for the Room in HMS is protected)
-
The transmission of room information from HMS to EAM will need to include all global codes. The code values included with the room record will be validated in EAM.
-
Guest rooms in EAM will be differentiated from Event rooms in EAM by the unit type field value. For Guest rooms, unit type is required in HMS and therefore will be populated in EAM. In HMS and EAM, Event rooms in EAM will not have a value populated for unit type.