Paper Chart Upgrade Business Requirements



[pic]

Business Requirements

For the

Distribution System Pressure Recorder Upgrade

Table of Contents

1 Introduction 3

1.1 Purpose 3

1.2 Scope 3

1.3 Definitions, Acronyms, and Abbreviations 4

1.4 Document Conventions/Requirements Traceability 5

2 Overall Description 6

2.1 Project Perspective, Functionality and Benefits 6

2.2 Conceptual Diagram 6

2.3 User Roles and Functions 7

2.4 Constraints 7

2.5 Assumptions and Dependencies 8

3 Specific Requirements 9

3.1 Business Requirements 9

3.2 System Interface Requirements 10

3.3 Performance Requirements 11

3.4 Security Requirements 11

3.5 Support Requirements 11

3.6 Training 11

4 Deleted Requirements 12

Introduction

1 Purpose

The purpose of the Business Requirements document is to define requirements for the Distribution System Pressure Recorder Upgrade project in sufficient detail that, if those requirements are properly implemented, the critical needs identified in the Joint Application Development (JAD) sessions for this project will be met.

2 Scope

Due to advancements in technology, the method in which PGW monitors pressure throughout the distribution system has become antiquated. PGW currently uses paper recording charts at 283 locations (201 regulator stations and 82 standalone) to measure and record pressure within the distribution system at specific points. The need to pick up and replace these charts on a weekly basis causes PGW’s Pressure Force Department to dedicate one employee and one vehicle daily to the performance of this task. This places an employee on the road eight hours a day, driving an average of 53 miles per day, which creates a significant cost and safety risk to PGW. In the event of holidays or bad weather, Pressure Force is forced to place two employees and two vehicles on the road while juggling crew assignments and manpower to complete other necessary tasks.

In addition to the inefficient use of manpower and company vehicles, this method of monitoring the system inherently creates a potential delay in notification of abnormal or alarm conditions. A pressure problem or other anomaly could potentially remain unresolved for an entire week. This effectively renders this method of pressure monitoring to historical recordings as opposed to actively monitoring. This delay can contributebe attributed to added safety risks and the inability to resolve an issue prior to it being elevated into an alarm condition or accident.

Finally, the accuracy of paper chart recorders is significantly less than the modern instrumentation available on the market. The improved accuracy will help PGW’s Network Analysis group to model the system based on necessary settings for seasonal weather conditions.

3 Definitions, Acronyms, and Abbreviations

The table below defines all terms, acronyms, and abbreviations referenced in this document.

|Term |Definition |

|Digital Chart Recorder |Transducer connected to electronics that takes sample pressure readings at set intervals. |

| |The pressure readings are transmitted to a centralized location on a set schedule, |

| |typically once or twice a day. |

|DMZ |Demilitarized Zone is a computer host or small network inserted as a neutral zone between |

| |a company's private network and the outside public network. It prevents outside users from|

| |getting direct access to a server that has company data. |

|HMI |Human Machine Interface. (SCADA operations displays.) |

|MODBUS |Network communication protocol |

|Paper Chart Recorder |Pressure recording device, where the gas pressure moves a physical pen that traces the |

| |pressure reading onto a circular chart. |

|Real-time Transmitter |Pressure transducer, connected to electronics that transmits real time pressure data. |

|Regulator Station |Where gas is regulated down from a higher pressure system into a lower pressure system. |

| |These stations consist of 2 regulators: a worker regulator and a monitor regulator. |

|VPN |Virtual Private Network (Encrypted dedicated network connection not shared by anyone else)|

|In WC |Inches of Water column (Pressure Unit) |

4 Document Conventions/Requirements Traceability

1 Traceability

To facilitate forward and backward traceability, all requirements are given a unique identifier (e.g., 3.1.11.2) that will remain with the requirement throughout the life of this project (for this software release and all that follow). To maintain these unique identifiers, requirements are added and deleted as follows:

• Added Requirements: Any requirement added after the first approved version of this document is inserted at the end of the appropriate section. The version indicator, “[vX.X],” appears after the requirement to identify the document version in which the requirement was added.

• Deleted Requirements: For any requirement deleted after the first approved version of this document, the requirement text is replaced by the word “deleted” and the requirement text is moved to section 4 Deleted Requirements. The unique identifier remains attached to the deleted requirement in the document.

2 Prioritizing Requirements

Priority identifiers ([MH], [SH], or [NH]) appear at the end of each requirement. Requirements are prioritized based on the following definitions:

• Must Have [MH]: Essential to the project and must be implemented in an agreed manner before the system can be released. These requirements are non-negotiable.

• Should Have [SH]: Important to the project and should be implemented if at all possible. Implies that the system is not unacceptable if these requirements are absent.

• Nice to Have [NH]: Beneficial to the business/project, but not necessary for the project to succeed. These requirements are negotiable based on timeline, scope, risks, and availability of qualified resources.

Overall Description

1 Project Perspective, Functionality and Benefits

The Distribution System Pressure Recorder Upgrade Project directly supports several of the corporate goals and objectives established by PGW. The following table lists the business goals and objectives that the Distribution System Pressure Recorder Upgrade Project supports and how it supports them:

|Business Goal/Objective |Description |

|Timely and accurate reporting |Electronic pressure monitoring will allow real-time and accurate reporting of all system test points|

| |and regulator stations. |

|Improve staff efficiency |One less employee dedicated to chart collection. Reduced maintenance calls for replacing pens, |

| |batteries, stuck pen, clocks, etc. |

|Reduced safety risks |Safety risks associated with operating a vehicle will be reduced by removing 2080 hours of a vehicle|

| |on the road. |

|Reduce overhead costs |PGW will no longer need to stock paper charts, pens, clocks, and batteries associated with paper |

| |chart monitoring. Also, Pressure Force supervisors will no longer be required to review charts |

| |daily. |

|Local and Federal Codes |With this project, PGW will continue to meet and exceed all local and federal codes regarding |

| |Distribution system pressure monitoring (e.g., CFR §192.741). |

2 Conceptual Diagram

[pic]

3 User Roles and Functions

• Manager, Pipeline Integrity & Press Control - Shall oversee the entire system process.

• Instrumentation Analyst (System Administrator) - Will oversee the entire system from a functional aspect. Will be responsible for system changes and addition/subtraction of points. Will also receive system alerts/alarms.

• Supervisor, Pressure Force - System user and will receive alerts and alarms.

• Instrumentation Technician - Responsible to maintain end points including calibrations.

• Pressure Foreman - Needs to be able to access current and recent pressure recordings.

• Senior Pressure Mechanic - Needs to be able to access current and recent pressure recordings.

• Pressure Mechanic - Needs to be able to access current and recent pressure recordings.

• Report writer - Responsible for creating new reports and updating existing reports and data extraction.

• Data viewer - View-only access to data and reports.

4 Constraints

• There are limited Pressure Force resources available to install the electronic pressure recorders.

• There are limited Information Services resources available to support the Distribution System Pressure Recorder Upgrade Project and other, ongoing, IS initiatives.

• There are installation temperature restrictions.

5 Assumptions and Dependencies

1 Assumptions

• All staff and employees will be trained accordingly in their respective responsibilities pertaining to the distribution pressure monitoring system.

• Funding will be available for training.

• Funding will be available for purchasing the hardware and software required for receiving, interpreting, and monitoring pressure data.

• All involved departments will provide necessary support for successful project completion.

• Project has executive-level support and backing.

2 Dependencies - None

Specific Requirements

This section contains all software requirements in sufficient detail to enable developers to design a system to satisfy those requirements and testers to verify that the system satisfies those requirements.

1 Business Requirements

1 Field

1 Test Points (38)

1 1 pressure input, pressure recorder 0 – 15in WC or 0 – 10psig [MH]

2 0.5% span accuracy. [MH]

3 Recorder shall be battery powered. [MH]

4 Recorder shall communicate over a secure, reliable, and wireless network. [MH]

2 Regulator Stations (196)

1 2 pressure input, pressure recorder 0 – 1in WC or 0 – 10psig and 0-30psig. [MH]

2 0.5% span accuracy. [MH]

3 Recorder shall be battery powered. [MH]

4 Recorder shall communicate over a secure, reliable, and wireless network. [MH]

3 Field Users

1 Need to have access to see live readings. [MH]

2 Instrument technician shall be trained on the calibration procedure. [MH]

3 Shall be able to recall 24 hours of recent history [MH]

4 Local system configuration (See 3.2.1.2 Local Access) [MH]

2 Office

1 Hardware (Handle and secure the signals from the field)

1 Open to vendor hosting

2 Router to receive the field signals. [MH]

3 Server preferably compatible with Windows Server 2012 and VMware. [NH]

4 Network equipment (Dependent on hosting decision)

5 If vendor hosted, provide ability to store the data internally for minimum of 5 years. [MH]

6 Handheld device [NH]

2 Software

1 Connections made to touch points (see 3.2.2) [NH]

2 Remote system configuration (See 3.2.1.1) [MH]

3 Local system configuration (See 3.2.1.2) [MH]

4 Compatible with Windows 7 [MH]

5 Preferred compatibility with VMware [NH]

6 Database SQL or Oracle [MH]

3 Reports and Forms

1 Stock reports shall be included with the initial system build. [MH]

2 A reporting tool shall be available to create ad-hoc and standard reports as required. [NH]

4 Alarms

1 Alerts shall be sent via electronic communication to identified employees based on user roles. [MH]

2 Alerts need to be clearly visible on local monitoring software. [MH]

2 System Interface Requirements

1 User Interfaces

1 Remote access from PGW office 24/7/365 [MH]

2 Local access in field [MH]

2 Software Interfaces

1 ArcGis (ESRI) [NH]

2 SynerGEE Network Analysis Software (“Stoner”) [NH]

3 Reporting [MH]

3 Communications Interfaces

1 Shall be a secure, reliable, and wireless network [MH]

2 Network shall be able to communicate with backup to alternate site [MH]

3 Must support security protocols necessary to ensure data integrity and confidentiality [MH]

3 Performance Requirements

1 System must be available 24/7. [MH]

2 Archives must be kept for 5 years. [MH]

3 Must support data and configuration backups [MH]

4 Security Requirements

1 User Authentication for remote access [MH]

2 User Authentication for local access [NH]

3 Encrypted transmissions [NH]

4 Access and Activity Logs [NH]

5 Support Requirements

1 Software updates and patches [MH]

2 Technical support during business hours [MH]

6 Training

1 Field End Users [NH]

2 Office End Users [NH]

3 Core Team [MH]

4 Manuals and documentation [MH]

Deleted Requirements

|Date |Approved By |Requirement |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

| | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download