Skip to main content

Activity Log

PROCESS NAME

Plant Activity Log (AM04)

FEATURE / USER STORY NAME

View and Filter Log Tab for Plant Activity History (AM04US01/High)

DESCRIPTION

The Log Tab feature provides a date-wise activity log for each plant, displaying essential information about the actions performed on the plant, such as asset creation, maintenance activities, inspections, and more. The log records high-level activities, focusing on action types like Asset Added, Asset Maintenance Completed, etc., along with the corresponding date. This log ensures users can track the most significant activities related to a specific plant, offering a clear view of key events without overwhelming them with detailed data.

Users can filter the log by date and search for specific action types, improving the ability to track plant-related activities for reporting and audit purposes.

ACTORS

Back-office user, Maintenance Manager, Auditor, Administrator

USER STORY

As a back-office user,
I want to see a simplified activity log for a specific plant,
so that I can quickly review high-level actions, like asset additions or maintenance completions.

As an auditor,
I want to filter and search for specific activities in the log,
so that I can track key events and ensure compliance.

STORYTELLING

John, a maintenance manager at River water Utilities, is reviewing the actions that have occurred in a particular plant. He navigates to the Log tab, where he sees a chronological list of high-level actions such as asset additions and maintenance completions. John filters the log by date to focus on the most recent actions. Later, John exports the log as an Excel file for further analysis during a monthly audit.

GOALS

  • Provide a concise, date-wise log of key actions related to a specific plant (e.g., asset creation, maintenance activities).

  • Allow users to filter the log by date and action type for easy tracking.

  • Enable export of the log in relevant formats for reporting and auditing purposes.

  • Maintain simplicity by recording high-level events without excessive detail, making the log easy to read and understand.

PROCESS FLOW DIAGRAM

 

MAJOR STEPS INVOLVED

  1. Back-office user logs into SMART360.

  2. Navigates to the Plant module and clicks view of a specific plant.

  3. Clicks on the Log tab to access the activity log.

  4. The activity log displays a list of high-level actions related to the plant, including:

    • Asset Added

    • Asset Maintenance Completed

    • Inspection Completed

    • Scheduling Completed

  5. Users can filter the log by date and action type (e.g., "AS01 Asset Added", "Maintenance Completed").

BUSINESS RULES

  • Only authorized users (e.g., back-office users, maintenance managers, auditors) can access the Log tab.

  • The activity log records high-level actions tied to the specific Plant ID.

  • The log must display the following columns:

    • Date (when the action was performed)

    • Action (e.g., "Asset Added", "Asset Maintenance Completed")

  • The log should display activities in chronological order by default.

  • The log must allow filtering by Date Range and Action Type (e.g., "Asset Added", "Maintenance Completed").

  • The log must reflect real-time updates when any action related to the plant is performed.

  • The log will contain a maximum of 1000 records to avoid performance issues.

SAMPLE DATA




Date

Action

2024-12-01

AS01 Asset Added

2024-12-02

MA01 Asset Maintenance Completed

2024-12-03

IS01 Inspection Completed

2024-12-04

SC01 Scheduling Completed

2024-12-05

AU01 Asset Audit Completed


ACCEPTANCE CRITERIA

  1. The activity log must display only high-level actions such as "Asset Added", "Maintenance Completed", "Inspection Completed", and "Scheduling Completed".

  2. The Date and Action columns should be displayed in the log.

  3. The activity log should be displayed in chronological order by default.

  4. Users must be able to filter the log by Date Range and Action Type.

  5. The log should reflect real-time updates whenever an action related to the plant is performed.

  6. The log must handle pagination for large sets of activities and display no more than 1000 records at once.

No Comments
Back to top