General Reference

Data Model

The following diagram shows how the families used in eLog are related to one another.

Note: In the diagram, boxes represent entity families and lines represent relationship families that are configured in the baseline database. You can determine the direction of the each relationship definition from the direction of the arrow head: the box from which the arrow originates is the predecessor, and the box to which the arrow head points is the successor.

Security Groups

Note: To create a Primary Event in eLog, you must be a member of the MI GAA Analyst Security Group. For more information about this Security Group, refer to the Security Groups section of the Generation Availability Analysis documentation.

The following table lists the baseline Security Groups available for users within this module, as well as the baseline Roles to which those Security Groups are assigned.

Important: Assigning a Security User to a Role grants that user the privileges associated with all of the Security Groups that are assigned to that Role. To avoid granting a Security User unintended privileges, before assigning a Security User to a Role, be sure to review all of the privileges associated with the Security Groups assigned to that Role. Also, be aware that additional Roles, as well as Security Groups assigned to existing Roles, can be added via Security Manager.


Security Group	Roles
MI eLog Viewer	Log Viewer MI APM Viewer MI Foundation Admin MI Foundation Power MI Foundation User
MI eLog Contributor	Log Contributor MI Foundation Admin MI Foundation Power MI Foundation User
MI eLog Administrator	Log Administrator MI Foundation Admin

The baseline family-level privileges that exist for these Security Groups are summarized in the following table.


Family	MI eLog Viewer	MI eLog Contributor	MI eLog Administrator
Entity Families
Log Entry and all its subfamilies	View	View, Create, Update, Delete	View, Create, Update, Delete
Shift	View	View, Create, Update, Delete	View, Create, Update, Delete
Reference Document	View	View, Create, Update, Delete	View, Create, Update, Delete
General Recommendation	View	View, Create, Update, Delete	View, Create, Update, Delete
Relationship Families
Action Is Assigned To	View	View, Create, Update, Delete	View, Create, Update, Delete
Asset Is Risk Increased	View	View, Create, Update, Delete	View, Create, Update, Delete
Asset Is Safety Bypassed	View	View, Create, Update, Delete	View, Create, Update, Delete
Asset Has Log Entries	View	View, Create, Update, Delete	View, Create, Update, Delete
Asset Has Shifts	View	View, Create, Update, Delete	View, Create, Update, Delete
Has Recommendations	View	View, Create, Update, Delete	View, Create, Update, Delete
Has Reference Documents	View	View, Create, Update, Delete	View, Create, Update, Delete
Has Shift Transition Arriving	View	View, Create, Update, Delete	View, Create, Update, Delete
Has Shift Transition Departing	View	View, Create, Update, Delete	View, Create, Update, Delete
Log Entry Has Human Resources	View	View, Create, Update, Delete	View, Create, Update, Delete
Log Has Events	View	View, Create, Update, Delete	View, Create, Update, Delete
Shift Has Log Entries	View	View, Create, Update, Delete	View, Create, Update, Delete

URLs

There is one URL route associated with eLog: eLog. The following table describes the various paths that build on the route, and the elements that you can specify for each.

Tip: For more information, refer to the URLs section of the documentation.


Element	Description	Accepted Value(s)	Notes
elog/dashboard/0: Displays the eLog Overview page.
elog/logentry/<Log Entry Key>/summary: Displays the log entry datasheet.
<Log Entry Key>	Specifies the key for the log entry that you want to open.	Any numeric Entity Key that corresponds to an existing log entry.	N/A
eLog/newlogentry/<Log Entry Sub Family Key>: Creates a new log entry for the given log entry subfamily key.
<Log Entry Sub Family Key>	Specifies the key for the type of log entry that you want to create.	Any numeric Entity Key that corresponds to a log entry subfamily.	N/A

URLs


Example URL	Destination
elog/dashboard/0	eLog Overview page
elog/logentry/1234567/summary	Log entry datasheet for the existing log entry with the Log Entry Key 1234567
elog/newlogentry/64260049699	New log entry datasheet for the log entry type with the Log Entry Sub Family Key 64260049699

System Code Tables

The following table lists the System Code Tables that are used by eLog.


Table ID	Table Description	Function
MI_LOG_CAUSE	Log Entry Cause Types	Populates the Cause list for all of the Log Entry datasheets.
MI_LOG_UTILITY_TYPE	Log Entry Utility Type	Populates the Utility Type list for the Log Entry, Utility datasheet.
MI_LOG_MITIGATINGS	Log Entry Mitigatings	Populates the Mitigatings While Safety Bypassed list on the Log Entry, Safety Bypass datasheet, and the Mitigatings While Repairing list on the Log Entry, Temporary Repair datasheet.
MI_LOG_INJURY_SEVERITY	Log Entry Injury Severity	Populates the Severity of Injuries list on the Log Entry, Safety datasheet.
MI_LOG_IMPACTS	Log Entry Impacts	Populates the Impact list on the Log Entry, Utility datasheet.
MI_LOG_DURATION_UNITS	Log Entry Duration Units	Populates the Duration UOM list on the Log Entry, Safety Bypass datasheet and Log Entry, Temporary Repair datasheet.

State Management

The eLog module uses standard State Management functionality to manage the Log Entry records.

The following baseline record states are configured for the Log Entry family:

In Progress: This is the default state for any new log entry. The Log Entry can be modified by any member of the eLog Administrator or eLog Contributor Security Groups.
Complete: Log Entries are in a view-only state for all eLog users. Log Entries cannot be modified unless they are returned to the In Progress state.

Note: Only members of the eLog Administrator Security Group and Super Users can modify the state of a Log Entry.