360 likes | 489 Views
PI Module Database. Ken Coates, Jon Peterson OSI Software, Inc. Introduction. PI Server Databases Programmatic Interfaces ActiveX. OSI and ActiveX based interfaces. Tools for applications OSI Products. Controls, applications ISV and system integrators User’s applications.
E N D
PI Module Database Ken Coates, Jon Peterson OSI Software, Inc.
Introduction • PI Server Databases • Programmatic Interfaces • ActiveX. • OSI and ActiveX based interfaces. • Tools for applications • OSI Products. Controls, applications • ISV and system integrators • User’s applications
Introduction, continued • PI Module Database • Add structure to the PI Data Archive • “Display Time” data source resolution • PI Batch Database • Model and store batch data • Map batch data to PI Data Archive • Support ISA S88 and beyond
Purpose • Batch Industry • Demands on equipment modeling • Numerous, similar equipment entities • Produce a wide range of products • Moveable, configurable equipment
Purpose • All industries can benefit • Add Structure to the PI Data Archive • Add organization through PI Point grouping • Controllers • Arrays. For example profile points • Complete hierarchical model
OSI Brewing • Demonstrate the Module Database • Pre-beta PI 3.3 • Top-down design approach • Start with the big picture • Drill down into the details
Enterprise: OSI Brewing, Inc. Site: Cleveland Area: Production Line: Phil’s Pilsner Line: Mark’s Stout
PI SDK Object Model Server PIModuleDB PIHeadings PIHeading PIModules PIModule PIHeading PIAliases PIAlias PIProperties PIProperty
PIHeadings • Used to implement consistent naming convention • Does not enforce a particular hierarchy • Does enforce order
PIModules • PIModule is the fundamental equipment element • Comprised of: • Name • PIHeading: Module's hierarchy • PIAliases: Collection of Data sources • PIProperties: User/Application specific configuration data • PIModules: More equipment collections
FCML101 F9CCFA79-B356-11d3-BA4B-F0C04F428C95ControllerFlow controller, ML-101 Version 24PIAdmin 22-Sep-19993-Oct-1999 PIAliases PIProperties PIModule
PIAliases • PIAlias maps a common name to a PI Point • Used to associate data with modules or equipment • All PIModules have a collection of PIAliases
FCML101 PIAliases PIAliases Alias Data Source Value LCMS101.pv Setpoint LCMS101.sp Output LCMS101.out
PIProperties • Set of Name-Value pairs • Stored in a VARIANT; therefore can hold nearly anything • User or application definable properties • Non-time series data associated with module
FCML101 PIProperties PIProperties Name Value Instrument Engineer John Doe Last Tuned 22-Nov-1996 Type PID
Demonstration • Configuration Tool • Microsoft Management Console Based • Consistent configuration interface
MMC Snap-in MMCProgramming Interface PI-SDK basedControls Snap-in Snap-In Toolkit PIModuleDb Snap-in Active Directory WMI WMI PIModuleDb SQL Server IIS
Enterprise: OSI Brewing, Inc. Site: Cleveland Area: Production Line: Phil’s Pilsner Line: Mark’s Stout Unit: Brew Kettle Unit: Brew Kettle
Brew Kettle “Sub-Modules” • The PIModules used to add collections of modules. • PIModule: “Controllers” • Temperature Controller • Level Controller
Brew Kettle Demonstration • Add the brew kettle to hierarchy • Add the controllers to the brew kettle
Brew Kettle, Phil’s Stout Line • Nearly identical to Brew Kettle on Mark’s Stout Line • References different data sources • Demonstration: Display time resolution of data sources
Historize Equipment Changes • Just like Process Data • Time stamp and Value • Keep track of modifications • New Instruments and New Units • Changing Product Information • Updated Specifications • New Products / Raw Materials • Database Driven Applications
Adding a New Instrument Time (values) Brew KettleEffectiveDate: 01-Jan-00 Brew Kettle EffectiveDate: 01-Mar-00 Aliases Aliases Thermocouple 1 Thermocouple 1 Thermocouple 2 Thermocouple 2 Thermocouple 3 Thermocouple 4
Demonstration • Excel spreadsheet report • Correctly resolving equipment in place for report period
PIModuleDB Summary • Easier access to PI Data Archive • Model to fit users requirements • For example, production requirements vs. maintenance requirements • Model supports changes through time • Module definable attributes • PIProperties collection
Features For Release 2 • Module Templates • Re-use of common module configurations • Also hierarchical • Inheritance • Changes to Module template propagated through derived modules • PI Alias Definitions • Template of alias definition with default point attributes
Release Schedule • Leveraging foundation of PI SDK 1 • Harry Smith • Bill Vaughan • Leveraging foundation of PI 3.x • Richard Beeson • Rulik Perla • Four Developers (4 fold increase!) • Configuration tools and controls • Richard May • Prabal Acharyya • ActiveX and Server Components • Ken Coates • Jon Peterson
Release Schedule • Beta Second Quarter 2000 • General beta with beta controls and configuration tools • Release Third Quarter 2000 • PI 3.3 • PI SDK 1.1
PI Module Database Server PIModuleDB PIBatchDB PIHeadings PIHeading PITransferRecordDB PIModules PIModule PITransferRecordList PITransferRecord PIHeading PISubBatchDefs PISubBatchDefinition PIAliases PIAlias PIBatchList PIBatch PIModule Templates PIProperties PIProperty PIProperties PIProperty PIProduct Templates PIProperties Hierarchy PIProperties PIModules Hierarchy PIUnitBatches Hierarchy PIPeople Templates Unit PIUnitBatchRules PIUnitBatch SubBatchLinkage PIUnitBatch PIUnitBatchList PISubBatches PISubBatch PISubBatchDefinition PISubBatches PIProducts PIProduct Same as PIModule except for Unit Hierarchy PIPeople PIPerson