This page (revision-19) was last changed on 26-Nov-2021 10:22 by mmcfarland

This page was created on 26-Nov-2021 10:22 by Administrator

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
19 26-Nov-2021 10:22 7 KB mmcfarland to previous
18 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
17 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
16 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
15 26-Nov-2021 10:22 7 KB mmcfarland to previous | to last
14 26-Nov-2021 10:22 6 KB jaiken to previous | to last
13 26-Nov-2021 10:22 6 KB JMyers to previous | to last
12 26-Nov-2021 10:22 9 KB JMyers to previous | to last
11 26-Nov-2021 10:22 9 KB JMyers to previous | to last
10 26-Nov-2021 10:22 9 KB Administrator to previous | to last
9 26-Nov-2021 10:22 9 KB Administrator to previous | to last
8 26-Nov-2021 10:22 9 KB Administrator to previous | to last
7 26-Nov-2021 10:22 9 KB Administrator to previous | to last
6 26-Nov-2021 10:22 9 KB Administrator to previous | to last
5 26-Nov-2021 10:22 9 KB Administrator to previous | to last
4 26-Nov-2021 10:22 9 KB Administrator to previous | to last
3 26-Nov-2021 10:22 9 KB Administrator to previous | to last
2 26-Nov-2021 10:22 9 KB Administrator to previous | to last
1 26-Nov-2021 10:22 7 KB Administrator to last

Page References

Incoming links Outgoing links
IHLS
IHLS

Version management

Difference between version and

At line 4 changed one line
Users can define an entity’s Safety Policies to develop safety rules for specific locations. Safety rules are established on the Define Location Safety Rules [IHLS] form. The definition data for the IHLS form is stored in the [P2K_SH_LOCATION_SAFETY_RULES] table.
You may apply the entity’s safety policies to develop safety rules for specific locations. Safety rules are established in the Define Location Safety Rules form. The definition data for the Define Location Safety Rules screen is stored in the [P2K_SH_LOCATION_SAFETY_RULES] table.
At line 6 added 2 lines
;Location: This field identifies the location associated with the safety rules. Location from [IDLN] ([P2K_CM_LOCATIONS]) is a mandatory field you must fill through the LOV.
;[Start Date|POLICY_START_DATE] / [End Date|POLICY_END_DATE]: These fields define the time frame that the safety rules are applied to the location. Policy_Start_Date and Policy_End_Date are mandatory date fields you must enter either manually or using the calendar icon (F9).
At line 7 removed 5 lines
!!IHLS Safety Policy Fields
||Field||Desciption
|Location|This field defines the location associated with the safety rules.
|[Start Date|POLICY_START_DATE] / [End Date|POLICY_END_DATE]|These fields define the time frame that the safety rules are applied to the location.
At line 13 changed 10 lines
!!Details Tab
||Field||Desciption
|[Safety Program in Place|SAFETY_PROGRAM_IN_PLACE]|When this toggle is set to ON, there is a safety program for this location.
|[Active Safety Committee|ACTIVE_SAFETY_COMMITTEE]|When this toggle is set to ON, there is an safety committee for this location.
|[Prevention Serv. Requested|PREVENTION_SERVICES_REQUESTED]|When this toggle is set to ON, there has been preventative services required of this location. Example: regular fire equipment testing.
|[Prevention Serv. Used|PREVENTION_SERVICES_USED]|When this toggle is set to ON, the location is using the requested preventative service.
|[Safety Policy|LOCATION_SAFETY_POLICY]|This field provides details on the safety policy specific to this location.
|[Medical Policy|LOCATION_MEDICAL_POLICY]|This field provides details on any medical treatment policy specific to this location.
|[Nearest Treatment|NEAREST_TREATMENT]|This field indicates where the nearest medical treatment center, such as a hospital or clinic, is located.
|[Transportation Avail.|TRANSPORTATION_AVAILABLE]|Users can enter quick emergency information on the best transportation and route to a medical center.
!!Details tab
At line 12 added 9 lines
;[Safety Program in Place|SAFETY_PROGRAM_IN_PLACE]: If this toggle is on, there is a safety program for this location. Safety_Program_In_Place is an optional toggle field.
;[Active Safety Committee|ACTIVE_SAFETY_COMMITTEE]: If this toggle is on, there is an safety committee for this location. Active_Safety_Committee is an optional toggle field.
;[Prevention Serv. Requested|PREVENTION_SERVICES_REQUESTED]: If this toggle is on, there has been preventative services required of this location. For example, regular fire equipment testing. Prevention_Services_Requested is an optional toggle field.
;[Prevention Serv. Used|PREVENTION_SERVICES_USED]: If this toggle is on, the location is using the requested preventative service. Prevention_Services_Used is an optional toggle field.
;[Safety Policy|LOCATION_SAFETY_POLICY]: This field provides details on the safety policy specific to this location. Location_Safety_Policy is an optional 4000 alphanumeric field
;[Medical Policy|LOCATION_MEDICAL_POLICY]:This field provides detail on any medical treatment policy specific to this location. Location_Medical_Policy is an optional 4000 alphanumeric field.
;[Nearest Treatment|NEAREST_TREATMENT]: This field indicates where the nearest medical treatment center (e.g. hospital or client) is located. Nearest_Treatment is an optional 4000 alphanumeric field.
;[Transportation Avail.|TRANSPORTATION_AVAILABLE]: This field allows you to provide quick emergency information on the best transportation and route to an medical center. Transportation_Available is an optional 4000 alphanumeric field.
At line 29 changed 5 lines
||Field||Desciption
|[Date Reviewed|DATE_REVIEWED]|This field defines the last review date of the safety rules, based on the specific needs of the location.
|Reviewed By Employee/Or By Contact|These fields define the name of the individual who conducted the review. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID]. \\* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].\\ \\
|[Next Review Date|NEXT_REVIEW_DATE]|This field identifies the next safety review date.
|[Safety Review Text|SAFETY_REVIEW_TEXT]|Users can enter detailed information about the safety review.
;[Date Reviewed|DATE_REVIEWED]: This field displays the last review date of the safety rules, based on the specific needs of the location. Date_Reviewed is an optional field you may fill either manually or using the calendar icon (F9).
;Reviewed By Employee Or By Contact: These fields display the identify who conducted the review.
;:%%information You may only complete one of these fields.%%
;:This is a optional field you may fill manually or retrieve from the LOV provided.
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;[Next Review Date|NEXT_REVIEW_DATE]: This field identifies when the next safety review will take place. Next_Review_Date is an optional field you may fill either manually or using the calendar icon (F9).
;[Safety Review Text|SAFETY_REVIEW_TEXT]: This field allows you to provide detailed information about the safety review. Safety_Review_Text is an optional 4000 alphanumeric field.
At line 40 changed 4 lines
||Field||Desciption
|Employee/Or By Contact|These fields defines safety member information. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID]. \\* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].\\ \\
|[Safety Member Role|SAFETY_MEMBER_ROLE]|This field defines any safety role the member may have. Example: Safety Chief, Volunteer or Drill Leader.
|[Description]|Users can enter further information about the safety member role.
;Employee Or By Contact: These fields display the safety members.
;:%% information You may only complete one of these fields.%%
;:This is a optional field you may fill manually or retrieve from the LOV provided.
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;[Safety Member Role|SAFETY_MEMBER_ROLE]: This field allows you specify any safety role the member may have. For example Safety Chief, Volunteer or Drill Leader. Safety_Member_Role is a mandatory field you must fill with a selection from the fixed lexicon [X_SAFETY_MEMBER_ROLE].
;[Description]: This field allows you to provide further information about the safety member role. Description is an optional 50 alphanumeric field.
At line 48 changed 8 lines
Information on the Safety Equipment tab is stored on the [P2K_SH_SAFETY_EQUIPMENT] table.
||Field||Desciption
|[Equipment|RESOURCE_REFERENCE]| This field identifies the safety equipment.
|[Type|RESOURCE_TYPE]|This field categorizes the equipment into a specific type.
|[Status|RESOURCE_STATUS]|This field defines the status of the equipment.
|[Description]|This field allows users to provide further information about the equipment.
|[How to Use|HOW_TO_USE]|Users can enter instructions on how to operate the safety equipment.
|[How to Inspect|HOW_TO_INSPECT]|Users can enter instructions on how correctly inspect the safety equipment.
Information on the Safety Reviews tab is stored on the [P2K_SH_SAFETY_EQUIPMENT] table.
At line 53 added 7 lines
;[Equipment|RESOURCE_REFERENCE]: This field identifies the safety equipment. Resource_Reference is an optional 50 alphanumeric field.
;[Type|RESOURCE_TYPE]: This field categorizes the equipment into a specific type. Resource_Type is a mandatory field you must fill with a selection from the fixed lexicon [X_RESOURCE_TYPE].
;[Status|RESOURCE_STATUS]:This field displays the status of the equipment. Resource_Status is a mandatory field you must fill with a selection from the fixed lexicon [X_RESOURCE_STATUS].
;[Description]: This field allows you to provide further information about the equipment. Description is an optional 50 alphanumeric field.
;[How to Use|HOW_TO_USE]: This field provides instructions on how to operate the safety equipment. How_To_Use is an optional 4000 alphanumeric field.
;[How to Inspect|HOW_TO_INSPECT]: This field provides instructions on how correctly inspect the safety equipment. How_To_Inspect is an optional 4000 alphanumeric field.
At line 61 removed 11 lines
||Field||Desciption
|[Type|SAFETY_ACTIVITY_TYPE]|This field categorizes the safety activity to a specific type.
|[Description]|Users can enter further information about the safety activity.
|Safety Equip.|This field identifies any equipment associated with the safety activity.
|[Status|SAFETY_ACTIVITY_STATUS]|This field defines the status of the safety activity.
|Assigned to EE/Or To Contact|These fields define the who the safety activity is assigned to. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID]. \\* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].\\ \\
|[Initial Date|SAFETY_ACTIVITY_DATE]|This field defines the first time this safety activity took place.
|[Interval|REPEAT_INTERVAL]|If the activity repeats, this field will display the repeat interval.
|[Basis|REPEAT_BASIS]| This field defines the time basis for the repeat interval, such as month, year.
|[Process|SAFETY_ACTIVITY_PROCESS]|Users can enter a detailed description of the safety activity.
|[Results|SAFETY_ACTIVITY_RESULTS]|Users can enter any results achieved through the safety activity.
At line 65 added 15 lines
;[Type|SAFETY_ACTIVITY_TYPE]: This field categorizes the safety activity to a specific type. Safety_Activity_Type is a mandatory field you must fill with a selection from the fixed lexicon [X_SAFETY_ACTIVITY_TYPE].
;[Description]: This field allows you to provide further information about the activity. Description is an optional l50 alphanumeric field.
;Safety Equip.: This field identifies any equipment associated with the activity. Safety_Equipment from ([P2K_SH_SAFETY_EQUIPMENT]) is a mandatory field you must fill through the LOV.
;[Status|SAFETY_ACTIVITY_STATUS]: This field identifies the status of the safety activity. Safety_Activity_Status is a mandatory field you must fill with a selection from the fixed lexicon [X_SAFETY_ACTIVITY_STATUS].
;Assigned to EE / Or To Contact: These fields identify whom the activity is assigned.
;:%%information You may only complete one of these fields.%%
;:This is a optional field you may fill manually or retrieve from the LOV provided.
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;[Initial Date|SAFETY_ACTIVITY_DATE]: This field indicates the first time this safe activity took place. Safety_Activity_Date is an optional field you may fill either manually or using the calendar icon (F9).
;[Interval|REPEAT_INTERVAL]: If the activity repeats, this field will display the repeat interval. Repeat_Interval is an optional 10 digit numeric field.
;[Basis|REPEAT_BASIS]: This field displays the time basis for the repeat interval. e.g. month, year. Repeat_Basis is a mandatory field you must fill with a selection from the fixed lexicon [X_PERIOD_BASIS].
;[Process|SAFETY_ACTIVITY_PROCESS]: This field allows you to describe the activity in depth. Safety_Activity_Process is an optional 4000 alphanumeric character field.
;[Results|SAFETY_ACTIVITY_RESULTS]: This field allows you to post any results that achieved through the activity. Safety_Activity_Results is an optional 4000 alphanumeric character field.
At line 74 changed 7 lines
||Field||Desciption
|[Date|SAFETY_LOG_DATE]|This field defines the date the equipment was inspected.
|[Time|SAFETY_LOG_TIME]|This field defines the time the equipment was inspected.
|[Status|SAFETY_LOG_STATUS]|This field defines the status of the event.
|Done By Employee/Or By Contact|These fields identify who created the logs. This is an optional field users can enter manually or retrieve from the LOV provided. \\ \\__NOTE:__ Users can select either one or the other one of these fields, but not both. \\* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID]. \\* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].\\ \\
|[Description]|Users can enter further information about the activity log.
|[Next Activity Date|NEXT_ACTIVITY_DATE]|This field identifies the next scheduled time for the activity. This date will calculated based on the Interval and Basis of the Safety Activity if left blank by the entry person.
;[Date|SAFETY_LOG_DATE]: This field displays the date the equipment was inspected. Safety_Log_Date is an mandatory field you must fill either manually or using the calendar icon (F9).
;[Time|SAFETY_LOG_TIME]: This field displays the date the equipment was inspected. Safety_Log_Time is a mandatory 5 character numeric field.
;[Status|SAFETY_LOG_STATUS]: This field displays the status of the event. Safety_Log_Status is a mandatory field you must fill with a selection from the fixed lexicon [X_SAFETY_LOG_STATUS].
;Done By Employee / Or By Contact: These fields identify who created the logs.
;:%%information You may only complete one of these fields.%% This is a optional field you may fill manually or retrieve from the LOV provided.
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;[Description]: This field allows you to provide further information about the activity log. Description is an optional 50 alphanumeric field.
;[Next Activity Date|NEXT_ACTIVITY_DATE]: This field identifies the next scheduled time for the activity. Next_Activity_Date is an mandatory field you must fill either manually or using the calendar icon (F9).
At line 92 added 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 84 changed 2 lines
![Notes|Edit:Internal.IHLS]
[{InsertPage page='Internal.IHLS' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.IHLS]
[{InsertPage page='Internal.IHLS' default='Click to create a new discussion page'}]
}]
This page (revision-19) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop