Lists Indexes and Databases Chapter 03 Lists Indexes

Lists, Indexes and Databases Chapter 03 – Lists, Indexes and Databases EMEC 125

Overview • Lists and indexes document the mechanical equipment and control system devices that make up a process plant. • Started as handwritten lists that organized data for the construction and operation of a plant. • The documents included, but were not limited to: • • • Equipment and instruments Piping Motors Cable and circuit schedules Etc.

Overview • Lists called out basic functions such as: • Defining component identifiers (make sure everything is referenced the same way on all documents). • ISA tag numbers or equipment numbers. • Instrument range. • Horse power. • Energy • Throughput or volume.

Overview • In the 1960’s, when the world started going digital, these lists became electronic and were now able to also be indexed. • Indexing allowed for sorting by using a reference designations such as: • Physical locations • Specifications • Instrument call outs (IDs)

Overview • No standard • Created to suite the users needs • Company practice • Company tradition • Included on a list • • • Pumps Compressors Vessels Tanks Air Handlers Loop list • Control system devices • Some data in addition to the equipment or instrument identifier, as required

Overview • List data sharing • Modern lists will be kept in a database so that information can be shared by other software • Maintenance departments can use the data in an asset management system • Calibration data can be accessed and instrument accuracy can be trended

Instrument Index • ANSI/ISA-5. 1 -2009 index should include, as a minimum, all instrument data by the owner and/or government regulator agency • • Loop ID number Service description Instrument ID number/Tag number P&ID drawing number Instrument data sheet number Location plan drawing numbers Installation detail drawing numbers

Database • Reusable data • Data (information) should be entered once • Data should be checked • Used in other documents and lists • Content of the database • • • Maintenance schedules Calibration records Instrument indexes Loop Diagrams P&ID text Process control computer configuration files • Relational database • Information should only be entered once to eliminate error • Relational database can be used to sort, cross reference and build various reports

Database • Relational database • Data can be used in many different ways • Users can create reports of only what they need • • • Calibration reports Component replacement information Control system configuration I/O assignment data Purchasing department – delivery status Construction staff – equipment installed vs. what needs to be installed

Control Systems Group Manages Device Docs • • • Appears on a P&ID Appears on a Loop Diagram Specification forms will reference the tag number Purchasing documents will reference the instrument Device log in Instrument Shop • • Calibration range Manufacture and model Tag number I/O loading (Defines termination points for signals) • A lot of information about one instrument • All this information can be in a database PT 100

To List or Not to List? • What really be on the list? • Rule of thumb states that if something has to be • • Purchased Mounted Wired Piped or tubed Maintained Calibrated Should also appear on the P&ID The device should appear on a list or in a database

To List or Not to List? • What should really be on the list? • Ask these questions: • Is the information needed? • Is value added by including the data? • Is it data that someone needs? • The additional data adds cost • • Data has to be found Data has to be entered and checked Data has to be updated and accurate Inaccurate data is WORSE than not having the data

Typical Instrument Data Fields

Data Flow Diagram Data. Flow. Diagram_Fig 3 -2_Pg 76. pdf

DB – Master Document • Consistency is key • All text fields should read the same everywhere they appear • Function description is sometimes the loop title • Function description should only be entered once no matter how many times it appears in a document or other documents • Two basic formats for loop title: • Loop function first, followed by a “for whom” or “for what” • Conventionally state what the loop does

DB – Master Document • Service identifier format example 1. Level – North Vessel 2. Flow – Chilled Water to Condenser • The hyphens are called delimiters and can make the identifier easier to read; however, • There needs to be consistency in how to enter the delimiter such as, a space on either side of the hyphen • Without the consistency, searching the DB becomes difficult if not impossible Do No t Mix Forma ts

DB – Master Document • Ensure there is agreement on the equipment titles • Calling a tank the Primary Mixing Tank might be the proper name; however, for the past 25 years everyone has been calling it the “Red Tank” • Call it the “Red Tank”. The maintenance technician being called in at 2: 00 AM will not appreciate the document calling out the Primary Mixing Tank and taking additional time to learn that it is the “Red Tank” Do No t Mix Forma ts

DB – Master Document • Ensure that the format used is supported by all control and monitoring software • Some software(s) describe a specific format for data such as: • Number of characters in a text field • Spaces or underscores • Punctuation or not • Data field format and structure could make software(s) not “talk” to each other

Linking Information • Instrument index is a core document that is prepared by the controls group • Computer Aided Design (CAD) software is commonly also linked to all documents • ANSI/ISA-5. 06. 01 -2007 provides examples of control software basic, I/O, interlock and operation data that all starts with the information drawn from an instrument database • Can ultimately populate a P&ID

Summary • Lists, indexes and databases are very important documents • Assists all departments with identifying, locating, purchasing, maintaining and calibrating equipment • Need to have data entered and checked in a consistent manner • Needs to be kept up-to-date • Needs to be properly linked to other documents

References Clark, J. (2013, May 14). Rule of Thumb. Retrieved September 29, 2016, from Everyday Idioms!!!: http: //idioms. languagesystems. edu/2013/05/rule-of-thumb. html: Image URL: http: //kinglawbankruptcy. com/wp-content/uploads/2012/12/Rot. gif Consistency: The Key to Success. (2016, December 7). Consistency Is The Key. Retrieved January 5, 2017, from Consistency: The Key to Success: http: //abundantrawlife. com/consistency-the-key-to-success/: Image URL: http: //abundantrawlife. com/wp-content/uploads/2016/12/Consistency-Key. jpg Greenbaum, K. (2012, April 23). Census Data: Babe's Father Earned $. Retrieved September 29, 2016, from Well, Happy and Safe An Everyman in World War II: http: //www. igreenbaum. com/2012/04/23/censusdata-babes-father-earned-810 -in-1939/: Image URL: http: //www. igreenbaum. com/wpcontent/uploads/2012/04/greenbaum_census. jpg Klazema, A. (2014, May 14). How to Write a Summary of an Article. Retrieved September 29, 2016, from udemy blog: https: //blog. udemy. com/how-to-write-a-summary-of-an-article/: Image URL: https: //blog. udemy. com/wp-content/uploads/2014/05/shutterstock_175331306 -300 x 200. jpg