CONTROLLING SMART INSTRUMENTATION DATA

Size: px

Start display at page:

Download "CONTROLLING SMART INSTRUMENTATION DATA"

Moris Watson
5 years ago
Views:

2 Controlling Smart Instrumentation Data Garbage Data Plant Hierarchy Data Naming Conventions Tag Properties Tables Process Function Data Instrument Type Data Properties Spec Sheet Forms Custom Defined Fields Data Validation

3 Smart Instrument Garbage Data "Garbage In, Garbage Out" - used to express the idea that in a relational database, incorrect or poor quality input will always produce faulty output. In a Smart Instrument data dictionary, every Table and Trigger has a specific purpose and is intended to contain data that is relevant to that purpose Incorrect data (Garbage) can also effect the performance of the database Examples of Garbage in a Smart Instrumentation database: Unstructured or Duplicate Key values in primary tables or fields Data that does not fit the a purpose of a field (e.g. a numeric value in a character field such as Name ) Data that violates the purpose of a Null value in a table Key Field Use of a User Defined Fields to duplicate a field already defined in the Smart Instrumentation data dictionary Narratives or Notes used in place of valid data fields

Smart Instrument Garbage Data "Unstructured or Duplicate Key values" Key values maintain the integrity of a relational database and must be structured and never duplicated Smart Instrumentation has

4 Smart Instrument Garbage Data "Unstructured or Duplicate Key values" Key values maintain the integrity of a relational database and must be structured and never duplicated Smart Instrumentation has naming conventions to assist in maintaining the structure of Key Fields Smart Instrumentation has constraint rules that prohibit the creation of Duplicate Key Field Data into the database A Relational Database creates a unique record_id number for each record in a table that Identifies Key Fields Tables in Smart Instrumentation have indexes of Primary and Foreign Keys All of these constraints can be bypassed by importing or introducing new records directly into the database

Smart Instrument Garbage Data Data fit the Purpose every data field column and table in Smart Instrumentation has a purpose as defined by the Table or Field name Common errors in data placed in the

5 Smart Instrument Garbage Data Data fit the Purpose every data field column and table in Smart Instrumentation has a purpose as defined by the Table or Field name Common errors in data placed in the wrong Table or Column are: Mixing Tag Class, I/O Types and Signal Types Difference between Manufacture Model and Catalog numbers Assigning Soft Tag numbers to Control System Tags Assigning wiring tables (e.g. cable, I/O) to Soft Tags Assigning both a Line Number and Equipment number to a Tag Not filling in Key Field Data like P&ID Number or Loop Number

6 Smart Instrument Garbage Data Purpose of a NULL value A field with a NULL value is a field with no value. It is very important to understand that a NULL value is different than a zero value or a field that contains blank spaces A NULL value stops a query from engaging additional Foreign Keys Any other value including space or or NA continues the Query

7 Smart Instrument Garbage Data Purpose of a NULL value A field with a NULL value is a field with no value. It is very important to understand that a NULL value is different than a zero value or a field that contains blank spaces A NULL value stops a query from engaging additional Foreign Keys Any other value including space or or NA returns a positive value

8 Smart Instrument Garbage Data Misused User Defined Fields custom fields created to track information specific to certain subject areas not already provided in the data dictionary or on a Instrument Specification

9 Smart Instrument Garbage Data Narratives and Notes are not Data while Smart Instrumentation provides Notes and Remarks fields in the data dictionary, they should be used sparingly, as they do not contain defined data

Smart Instrument Plant Hierarchy Data The Plant Hierarchy can become very complex and should be established early on in the project to prevent rework The Basis of the Hierarchy may be Process Unit,

10 Smart Instrument Plant Hierarchy Data The Plant Hierarchy can become very complex and should be established early on in the project to prevent rework The Basis of the Hierarchy may be Process Unit, Operating System, Physical Unit or Construction Areas but needs to be kept simple The Plant Hierarchy must be consistent across all applications for integration to function when data is published and retrieved

11 Smart Instrument Naming Conventions Naming Conventions the most important function of the naming conventions is the definition of the structure of Instrument Master Tags Additional Naming Conventions may also be assigned for documents, cabinets, cables and equipment

12 Smart Instrument Naming Conventions Some things to consider when developing the Instrument naming conventions: The naming conventions should be based on a standard (e.g. ISA ) The naming convention need to be consistent across all applications There are 39 definable naming conventions with different behaviors There are several Instrument Tag Naming Conventions and behaviors: Instrument (Conventional) most universal Instrument (Foundation Fieldbus) allows VFD and Function Block assignments Instrument (HART) Limits I/O to HART AI and HART AO Instrument (Profibus DP) allows VFD and Function Block assignments Instrument (Profibus PA) allows VFD and Function Block assignments Instrument (Telecom) limits Instrument Types to Telecom Soft Tags should not be used for wired devices Analyzer Components allows analyzer stream data assignments

13 Smart Instrument Naming Conventions At times it is necessary to have different Instrument Naming conventions for separate systems or groups of instruments: Systems like Machinery Protection can have unique naming conventions: Unit-Equipment Number-Function-sequence-suffix Example: 27-C-100-VSH where the equipment number is part of the Tag Safety Systems where other groups are responsible for purchase or maintenance of devices (e.g. Relief Valves have unique naming convention) Example: POSRV Pilot-Operated Safety Relief Valve Packaged equipment where the vendor has a unique naming convention Example: CV-100 non ISA naming convention Instruments that are purchased as coded items rather than tagged Example: PSG43005R1 (ASME bottom connected 300 psi pressure gauge)

Smart Instrument Naming Conventions The best way to create unique naming conventions without compromising the BPCS Key Tags is to create unique Units for them: Example: Inserting a

14 Smart Instrument Naming Conventions The best way to create unique naming conventions without compromising the BPCS Key Tags is to create unique Units for them: Example: Inserting a 2 digit equipment number in a Tag in Unit 21 by creating a new Unit number 210 with a Unit Number length of 2 BPCS Tag in Unit 21 21TSH Equipment Tag in Unit TSH

15 Smart Instrument Tag Properties Tables Tag Class: Pick List defined by the Naming Conventions - Used to select the naming convention used for the Master Tag Numbers Service: String describing the service description of a tag May be inherited from the Loop service Description Instrument Type: Pick List used to define the Automation Profile Composed of Instrument Function, Description and Process Function Status: Pick List defining the status of an instrument e.g. New, Furnished, Relocated, Deleted etc.. Location: Pick list defining the physical location of an Instrument May be general such as Field or more exact such as Inline I/O Type: Pick list used to define the type of connection to a DCS or PLC Should not be modified if you are using a DCS Vendor Interface If required System or Signal Type can be defined else ware

16 Smart Instrument Tag Properties Tables Certification: Pick List used to define any standard certifications required for procurement or installation of the instrument Signal Type: Pick List used to define the signal or protocol used by an instrument May be used to define Soft Tags or special Protocols Linear Type: Pick List used to define the instrument calibration of an analog control signal Usually defined as Linear, Non-Linear, Logarithmic or Exponential Equipment: Pick List selection of the Equipment Number that an instrument is mounted on or in Not associated to Line: Pick List selection of the Line Number that an instrument is mounted on or in Line Size and Material Spec are important P&ID: Pick list used to select the source Piping and Instrument Diagram showing the Instrument May be other source documents

17 Smart Instrument Tag Properties Tables Manufacturer: Pick List used to select the Manufactures name of an instrument Different spellings and case causes issues in this table Model: Pick List used to select me model number based on a parent relationship to the manufacture catalog numbers may be used Intrinsically safe circuit type: Pick List used to select the method of making an instrument incapable of igniting an explosive atmosphere On and Off signal state: a description of what state an instrument will be in when the signal is on and off Requires power supply: a check box that turns on a Power Supply tab enabling the user to define the power requirements

Smart Instrument Process Function Data The Process Function defines Tables containing the variables associated to each Instruments sizing and selection requirements General Flow Level Pressure

18 Smart Instrument Process Function Data The Process Function defines Tables containing the variables associated to each Instruments sizing and selection requirements General Flow Level Pressure Temperature Analyzer Control Valve Relief Valve Instruments that do not Measure or Control are considered General instruments Process Data needs to be defined by a process engineer and populated in the process module for Sizing and Selection

19 Smart Instrument Type Profile Data The Instrument Type Profile defines the automation functions and how data is distributed in the Smart Instrument database When an instrument is added to the database or the Profiles are launched the following actions will happen if the Profile Data is populated: An Instrument Spec sheet is created and populated from a Spec Sheet Template A Process Datasheet is created in the proper Process Function assigned to the Instrument Type The I/O Type and Location are assigned The Wiring Device Panel and Terminals are created The Wiring Instrument cable is created and connected to the Device Panel Other associations including: Custom Tables, Hookups, Dimensional Data for Piping and Loop Symbols are initialized

Smart Instrument Spec Sheet Forms The Instrument Specification Form (Data Sheet) Form for each Engineered Instrument Data from Index and Line table Data from the Process Function The majority of the

20 Smart Instrument Spec Sheet Forms The Instrument Specification Form (Data Sheet) Form for each Engineered Instrument Data from Index and Line table Data from the Process Function The majority of the Form are UDFs Spec Forma are one place where garbage data seems to gravitate Without a structured data dictionary it is easy to place irrelevant or incorrect data on a Spec Form There is a tendency to overuse notes on a Spec Form instead of structuring the form to provide data fields for needed information 20

Smart Instrument Custom Defined Fields The Custom Defined Fields are Provided for almost all primary Tables Some Custom Fields that are normal in most project database are: System lists the different

21 Smart Instrument Custom Defined Fields The Custom Defined Fields are Provided for almost all primary Tables Some Custom Fields that are normal in most project database are: System lists the different Control Systems documented in the database Plan Drawing while the use of Plan drawings are being phased out because of Smart 3D, they are still being used for construction There are other Project specific Fields not included in the data dictionary Care should be taken not to repeat data fields already in the Data Dictionary The EDE will eliminate the need to duplicate data for Custom Reports 21

22 Smart Instrument Data Validation SPI has several External Validation Software choices SmartPlant Engineering Integrity Rule based auditor for P&ID, SPI and SPEL Beaconsuite Data Control for SPI monitors and reports all nonconforming deliverables PAS Integrity/DOC4000 for SPI offers a consolidated view the control infrastructure SPInspector examines the SPI database for specific data attribute discrepancies CAXperts Report Adapter for SPI exports Data for data attribute analysis WiseTools INAudit interrogates SPI and generates reports highlighting discrepancies 22

23 Controlling Smart Instrumentation Data Those who rule data will rule the entire world ~ Masayoshi Son 23

and Emerging Instrument Technologies

FLUOR and Emerging Instrument Technologies SmartPlant Implementation Team By John Dressel The Challenge of Emerging Technologies New and emerging technologies bring new challenges to the Instrumentation