Project: POWRA Document Integration

Overview

This document outlines the requirements for integrating the POWRA (Permit to Work Risk Assessment) document into the system. The feature will ensure that technicians sign the required safety documents before starting their tasks, enhancing compliance and workplace safety.

Roles & Responsibilities

• Site Manager (Web App): Creates and manages POWRA templates, attaches templates to tasks, and oversees signed documents.
• Technician (Mobile App): Signs the POWRA document upon clock-in before starting a task.
• System: Enforces signing requirements, manages alerts, and prevents timesheet submission if the document is not signed.

Feature Flow

1. Site Manager Creates a POWRA Template

   • The template includes safety hazards, PPE requirements, and specific task conditions.

   • CRUD operations are available (Create, Read, Update, Delete).

   • Editing a template with existing signatures will invalidate all signatures and require re-signing.

   • If a template is modified, an alert appears:

     "Are you sure you want to modify this template? All collected signatures will be invalidated, and users must re-sign due to updated safety requirements."

     

2. Attaching a Template to a Task

   • A template can be attached to tasks under milestones and towers.
   • Hierarchy: Tower → Milestones → Tasks
   • Once attached, the template cannot be edited without invalidating collected signatures.

   

3. Technician Clock-In & POWRA Signing (Mobile App)

   • Upon clock-in, the system checks if the technician has signed the POWRA document for the assigned task.
   • If not signed, the technician is directed to the signing form.
   • If the technician does not have a saved signature, they must create one in their profile before proceeding.
   • Technicians cannot create a timesheet without signing the POWRA document.

   

1. Notification & Alert System

   • If a technician does not sign the POWRA document or submit a timesheet, a push notification alert is sent.
   • Alerts are triggered similarly to unsubmitted timesheets, initially set for a **one-week interval (subject to change).

   Zendit notifications scope :** https://docs.google.com/spreadsheets/d/1ZEWY0KmfcQAgsRMz3duTdpshg8n9CRVVzKOJOKnyFKw/edit?usp=sharing

   ---

   

   

2. Accessing Signed Documents

   • Signed POWRA documents are stored and accessible in the web app under the POWRA pages.
   • Site managers can view signed documents, including the personnel who accepted the hazard conditions.

   

3. Safety Hazard Dynamic Collection

   • Site managers can create new Safety Hazard list.

Platform-Specific Features

Web App

• Site Manager Capabilities:
  • CRUD POWRA templates.
  • Attach templates to tasks.
  • CRUD Safety Hazards dynamically.
  • View signed POWRA documents.
  • Prevent editing of templates once attached, unless users re-sign.