HSSE TRACKING SYSTEM USER REQUIREMENT DOCUMENT

HSSE TRACKING SYSTEM USER REQUIREMENT DOCUMENT Project Code: DHTN_PROJ_1 Document Code: DHTN_PROJ_1_URD_v1.0 HCM City, Mar-2012 DHNT_PROJ_1: User Requirement Document v1.0 2/39 Record of change Effective Date Changed Items Reason Source Old Version Change Description New Version DHNT_PROJ_1: User Requirement Document v1.0 3/39 SIGNATURE PAGE DHNT: ORIGINATOR: Member Project Leader REVIEWERS: PdQA APPROVAL: Project Director TNHD: APPROVAL: Power User System Owner Project Leader TNHD ICT Transition PM DHNT_PROJ_1: User Requirement Document v1.0 4/39 Table of contents 1 INTRODUCTION 6 1.1 Overview 6 1.2 Documents Referenced 6 1.3 Objectives 6 1.4 Scopes 6 1.5 Out of scope 6 1.6 The Structure of document 6 2 SYSTEM OVERVIEW 7 2.1 Business declare 7 2.2 System architecture 7 2.3 Technical solution 7 3 BUSINESS PROCESS 8 3.1 Organization map 8 3.2 Tracking processes 9 3.3 Actors definition 9 3.3.1 System Administrator 9 3.3.2 Approval user 10 3.3.3 General user 10 3.3.4 Restrict user 10 3.4 Event Status definition: 10 3.5 Action/Finding Status definition: to do only Event status = Approved 10 3.6 Levels definition: 10 3.7 Referent number: 10 3.8 The methods for reminding to send mail automatic: Admin only set schedule 10 4 USER REQUIREMENTS 11 4.1 AD - Administration 11 4.1.1 AD01 - Check admin user authentication (Admin Login) 11 4.1.2 AD02 - Module Management 11 4.1.3 AD03 - Account Management 11 4.1.4 AD04 - Company Information Management 11 4.1.5 AD05 - Category/Sub Category Management 11 4.1.6 AD06 - Notify to user by auto email 11 4.1.7 AD07 - Input target of each user in year 11 4.1.8 AD08 - Event Type 12 4.1.9 AD09 - Issue Related 12 4.1.10 AD10 - System Involved 12 4.1.11 AD11 - Equipment Involved 12 4.1.12 AD12 - Possible Immediate Cause 12 4.1.13 AD13 - System Cause 12 4.1.14 AD14 - Golden Rule 12 4.1.15 AD15 - Sub Golden Rule 12 4.1.16 AD16 - Severity Risk: for Potential & Actual 12 4.1.17 AD17 - Group Level Permission Management 12 4.2 EM - Event management 12 4.2.1 EM01 - My new event: for Inputter only 12 4.2.2 EM02 - My Task 13 4.3 NW - Create new / Upgrade request 14 4.3.1 NW01 - Raise a new SOC 14 4.3.2 NW02 - Raise a new Incident report 15 4.3.3 NW03 - Raise a new Audit report 17 4.3.4 NW04 - Raise a new Other Event 19 4.4 SE - Search 20 4.4.1 SE01 - SOC 20 4.4.2 SE02 - Incident report 21 DHNT_PROJ_1: User Requirement Document v1.0 5/39 4.4.3 SE03 - Audit report 22 4.4.4 SE04 - Other event 23 4.5 RE - Report 24 4.5.1 RE01 - SOC summary 24 4.5.2 RE02 - SOC performance 24 4.5.3 RE03 - Incident summary 26 4.5.4 RE04 - Audit summary 26 4.5.5 RE05 - Action summary 27 4.6 AN - Analysis 27 4.6.1 AN01 - SOC 27 4.6.2 AN02 - Incident report 29 4.6.3 AN03 - Immediate Cause 31 4.6.4 AN04 - System Cause 33 4.7 OT - Other 35 4.7.1 OT01 - Mail reminder 35 5 OTHER REQUIREMENTS 36 5.1 OR01-User interface 36 5.2 OR02-Interface with other systems, operating environment 36 5.3 OR03-Performance 37 5.4 OR04-Report 37 5.5 OR05-Security 37 5.6 OR06-Deployment Scope 37 5.7 OR07-System Expandability 38 5.8 OR08-Developing Tool 38 5.9 OR09-Derived handover to support 38 6 ACCEPTANCE & QUALITY 39 6.1 Assumption 39 6.2 Acceptance & Quality 39 DHNT_PROJ_1: User Requirement Document v1.0 6/39 1 INTRODUCTION 1.1 Overview This proposal has been prepared in order to present our suggested solution responding to your requirements on establishment of Local Tr@ction for TNHD. This document serves as a basis for your tender evaluation as well as for later contracting in case we are selected. DHNT commits to carry out all items and tasks indicated in this proposal. 1.2 Documents Referenced Reference Document information SoR Statement of Requirement – Supplied by TNHD ToR Term of Reference – Supplied by TNHD 1.3 Objectives • Provide a fast-access, user-friendly Local Traction online which allows TNHD staff to record their Events effectively. • Users in the head office or remote sites can access the system via Internet Explorer. • Provide a good report function to ensure HSE staff can produce weekly, monthly, quarterly… reports based on multi categories for TNHD. They will be able to compare reports of the same level and track whether actions are closed out. The reports can be converted to excel files. • The system should be simple to maintain and update. 1.4 Scopes • The system is limited to the TNHD staff, contractors and agencies. It will be only able to access to the TNHD intranet users. • TNHD Users can raise events and record them to the database. • TNHD ICT & HSSE staff’s site supervisors will provide the support 1.5 Out of scope • Existing system (MS Windows NT Domain Controller, ) • Networking, Infrastructure, 1.6 The Structure of document It has 6 functions of this, including: 1. Introduction 2. System overview 3. Business process 4. User requirement 5. Other requirement 6. Acceptance and Quality DHNT_PROJ_1: User Requirement Document v1.0 7/39 2 SYSTEM OVERVIEW 2.1 Business declare Tr@ction is terminated due to the cost for buying tr@ction copyright and maintenance of this system is too expensive. To record, file safety observation conversations, statistics, audits, HSSE events, Legal Reviews, Risk Review, Emergency Exercise… and monitoring actions from these sources, we need to build similar software to replace tr@ction. 2.2 System architecture 2.3 Technical solution The system consists of the following components, as below table: The technical solution uses Microsoft products to develop the system. Component Technical Solution Online Client Internet Explorer 6.0 or higher Web Application Server IIS 6.0 or higher Database server Oracle 10g Programming language ASP.NET DHNT_PROJ_1: User Requirement Document v1.0 8/39 3 BUSINESS PROCESS 3.1 Organization map Local Traction System Reports Analyze Reports Chart EVENT Management Administration Check admin user Account Management Company Management (Department,Location) Incident Report SOC Audit Edit mail template for auto send mail SOC Performed (Chart by Department) SOC Performed (Chart by Location) Chart by Category Incident summary SOC summary Module Management (Incident, Audit, SOC, Other events) Other Event Search (Incident report, Audit, SOC, Other events, Action) Tracking Approval Audit summary SOC performance Action summary Category/Sub Category Management Input/Set target 9 Master lists (AD08 to AD16) Grant user Role User Management Incident Report (Chart by Department) Incident Report (Chart by Location) Chart by Category Immediate Cause (Chart by Department) Immediate Cause (Chart by Location) Chart by Category System Cause (Chart by Department) System Cause (Chart by Location) Chart by Category DHNT_PROJ_1: User Requirement Document v1.0 9/39 3.2 Tracking processes Tracking System Inputter Approver Responsible person (Actionee) Tracking / Search New events Auto Mail No Comment Action Approve Event ? Yes Tracking / Search Event Status Open Complete for Approval Action Auto Mail Event Status Approved Complete for Approval Event Event Status Pending Action Status Open Auto Mail Action Status Completed Approve Action ? No Yes Report / Analysis Report / Analysis End Action Status Approved Mail Unapproved Auto Mail Receive mail Receive mail Auto Mail Mail Unapproved 3.3 Actors definition Below are the main system’s actors whose functions are fully described further down after this section: There are four roles in this application:  Administrator (Level 1)  Approval user (Level 2)  General user (Level 3)  Restrict user (Level 4) 3.3.1 System Administrator The Administrator is responsible for administration of this particular system. He manages system setting, master lists, and granting / revoking role to/from users. Besides that, he has full controls on the rest of system functionalities. Full access, possible Add / Edit / Remove for: Category, Department, Location, User account, DHNT_PROJ_1: User Requirement Document v1.0 10/39 Role, Set Active/Inactive user account 3.3.2 Approval user • Track, modify (status=pending) and close (click approve) for the Events/Actions ones. • Raise Events, Event’s actions. • Search, run, summary reports 3.3.3 General user • Raise Events, actions, allow modify the own input. • Search, run, summary reports 3.3.4 Restrict user • Raise SOC only and SOC’s actions • Search all SOC, view (owned ones). 3.4 Event Status definition: • 1 - Open: Inputter create new event, i.e. not be completed for approval • 2 - Pending: waiting for approval, i.e. not be approved • 3 - Approved: closed 3.5 Action/Finding Status definition: to do only Event status = Approved • 1 - Open: Inputter create new event, i.e. not be completed for approval o If Target Date is expired: Overdue • 2 - Completed: waiting for approval, i.e. not be approved • 0 - Overdue: appear only on status dropdown list for searching • 3 - Approved: closed 3.6 Levels definition: • Null if not be checked • 0 - No data, i.e. checked without level • 1 - Low • 2 - Med: Medium • 3 - High 3.7 Referent number: • Event number: <Event Code>-YYYY-xxxx • Action number: xx, start by “01” for each Event: <Event Code>-YYYY-xxxx-xx 3.8 The methods for reminding to send mail automatic: Admin only set schedule • Remain 30 days before Target date: send once to Actionee (status=Open) • Remain 7 days before Target date: send once to Actionee (status=Open) • Overdue: send daily to Actionee (status=Open) [...]...DHNT_PROJ_1: User Requirement Document 4 v1.0 USER REQUIREMENTS 4.1 AD - Administration 4.1.1 AD01 - Check admin user authentication (Admin Login) This function authorizes logged user when the user wants to use administration system 4.1.2 AD02 - Module Management  List of Modules  Modify Modules o o Email subject template... for updating template mail 35/39 DHNT_PROJ_1: User Requirement Document 5 5.1 v1.0 OTHER REQUIREMENTS OR01 -User interface  Easy to use We have had a good relationship with TNHD user User interface is designed for user easy to use with helping of mouse, keyboard and some hot keys, layout, color as the same with TNHD standard  Screen resolution All the user interface web pages are designed for 1024... approval authority to remind approving with the content as below  From The HSSE Tracking System  To Approver 18/39 DHNT_PROJ_1: User Requirement Document  Subject: get from template  v1.0 Main content o o Incident $title$ o Incident date $date$ o Status: $status$ o  Reference number $fullnumber$ URL: http://web.TNHD.com.vn/trackingsystem/Event.aspx?id=$id$ Footer: get from template and sender $sender$... from list o Show percentage of System Cause performed of each category 34/39 DHNT_PROJ_1: User Requirement Document v1.0 System Cause Analysis by Category Category 1 7% 19% 12% Category 2 Category 3 Category 4 14% 18% Category 6 14% 16% • Category 5 Category 7 Chart for Subcategory: select Category from list Show percentage of System Cause performed of each subcategory System Cause Analysis by SubCategory... Category 5 Sub Category 6 Sub Category 7 AN04 - System Cause 4.6.4.1 System Cause by Location • Filter form: filtering by 1 Year: select from list 2 From Month: select from list 3 To Month: select from list • Chart for Category: select Location from list Show percentage of System Cause performed of each category 33/39 DHNT_PROJ_1: User Requirement Document v1.0 System Cause Analysis by Category Category... do: [Target year] – [YTM Done] 24/39 DHNT_PROJ_1: User Requirement Document  o Seq v1.0 YTD performed (%): [YTM Done] / [Target year] Example for describing: 2007 Target Dept Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec YTM Done To do YTD performed % 48 Name 5 9 5 6 3 5 4 3 8 0 0 0 48 4 100 HSSE 1 Lam, NT HSSE 24 2 4 2 3 1 2 2 1 3 20 4 83 2 Thinh, TN HSSE 24 3 5 3 3 2 3 2 2 5 28 0 117 48 5 9 5 6 3... status = pending and send message to approver 16/39 DHNT_PROJ_1: User Requirement Document v1.0  After send: Not allow modify by Inputter, but Admin/Approver can edit (allow modify only all fields)  Send mail: an automatic message will be sent to approval authority to remind approving with the content as below  From The HSSE Tracking System  To Approver  Subject: get from template  Main content... OR02-Interface with other systems, operating environment  Windows OS: This system was web application run on Win 2003 Enterprise server  The Tracking System requires to be accessed using the TNHD standard IE browser that is installed on TNHD Passport machines  DHNT Contractor will carry out all installations with assistance from the HSSE & ICT resource on site at TNHD  Check user from Active Directory... message will be sent to approval authority to remind approving with the content as below  From The HSSE Tracking System  To Approver  Subject: get from template  Main content o o Incident $title$ o Incident date $date$ o Status: $status$ o  Reference number $fullnumber$ URL: http://web.TNHD.com.vn/trackingsystem/Event.aspx?id=$id$ Footer: get from template and sender $sender$ • Button “Approve”: appear... (List/Add/Delete/Update) AD06 - Notify to user by auto email The administrator uses this function to edit content and set parameters of automatically sending mail Purpose of this action is to notify Level 2 to CLOSE (approve) 4.1.7 AD07 - Input target of each user in year This function allows user (Level 1 only) to input target of each user in a year Only administrator or approval User has right to modify data . 12 4 .1. 11 AD 11 - Equipment Involved 12 4 .1. 12 AD12 - Possible Immediate Cause 12 4 .1. 13 AD13 - System Cause 12 4 .1. 14 AD14 - Golden Rule 12 4 .1. 15 AD15 - Sub Golden Rule 12 4 .1. 16 AD16 -. 11 4 .1. 6 AD06 - Notify to user by auto email 11 4 .1. 7 AD07 - Input target of each user in year 11 4 .1. 8 AD08 - Event Type 12 4 .1. 9 AD09 - Issue Related 12 4 .1. 10 AD 10 - System Involved 12 . 4 .1. 1 AD 01 - Check admin user authentication (Admin Login) 11 4 .1. 2 AD02 - Module Management 11 4 .1. 3 AD03 - Account Management 11 4 .1. 4 AD04 - Company Information Management 11 4 .1. 5 AD05