1 / 31

Universal Data Adapter

Universal Data Adapter. Ray Verhoeff. Agenda. Features and Benefits How does it work? Building UDA points Systems supported Deploying UDA Writing a COM Connector. Client Applications. PI Server. PI-UDA. COM. TCP / IP. PI Interfaces. DCS / PLC & Other Data Sources. UDA Architecture.

liam
Download Presentation

Universal Data Adapter

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Universal Data Adapter Ray Verhoeff

  2. Agenda • Features and Benefits • How does it work? • Building UDA points • Systems supported • Deploying UDA • Writing a COM Connector

  3. Client Applications PI Server PI-UDA COM TCP / IP PI Interfaces DCS / PLC & Other Data Sources UDA Architecture PIArchive COM Connectors Foreign Historians

  4. Supports all client software Any PI-API and PI-SDK application, including yours Client Applications

  5. Supports all interfaces as long as foreign data system can support insert of data Interfaces

  6. Base PI NetMgr Snapshot Archive How does it work? Client Connections

  7. Snapshot from PI Request PI NetMgr Response RPC Call Snapshot RPC Response Snapshot Array

  8. Snapshot from UDA Request PI NetMgr Response RPC Call Snapshot RPC Response COM call Return Data COMConnector Foreign Data System

  9. COM Connector IPIUDAPointConnector COM Object IPIUDASnapshotConnector IPIUDAHistoryConnector Foreign API Foreign Data System

  10. Three identifying point attributes uda_progid String Name of COM object uda_strmap String uda_lmap Integer Defining UDA Points

  11. Two point attributes insufficient? Developers are free to define additional attributes Use PI-SDK or PI-API to “call back” into PI COM Connector provided with “connect back” information name of system and TCP/IP port Defining UDA Points

  12. Currently, build points using available PI tools piconfig Tag Configurator Honeywell PHD “udaphdbuild” utility Point Building

  13. New product to synchronize PI and UDA databases with DCS database edit, delete, create Auto Point Sync

  14. Three Modules GUI to configure rules & settings Sync Engine to monitor DCS for changes APS Connector to get DCS database information (DCS specific) Communication between three modules is based on COM APS Runs on NT Auto Point Sync

  15. APS Connectors • APS Connectors implemented on NT • Vendor API on NT • Vendor API on VMS & UNIX • DCE RPC

  16. APS Connectors • Fisher-Rosemount CHIP • OSI PItoPI • Honeywell PHD • NT-based interfaces first

  17. APS Future • Initial release synchronizes existing interface points (edit, delete) • Second release provides point creation • APS development will be integrated with standard interface development

  18. APS can monitor Foreign System Create new UDA mapped points APS-defined interface could be exposed by COM Connector Point Building for UDA

  19. UDA can host “native” points Calculated points Batch points Alarm points Hybrid Systems

  20. Honeywell PHD Microsoft OLE DB Aspen Tech CIMIO IP/21, InfoPlus, InfoPlusX Aspen Tech CIM/21 ABB Enterprise Historian OSI-provided COM Connectors

  21. Foxboro Historian Westinghouse Historian Wonderware Westinghouse Enterprise Process Historian Possible COM Connectors

  22. Deployment - 1 UDA UDA PHD “PointX” PointX PHD sees 1 “client” Client connections

  23. Deployment - 2 UDAs UDA “PointX” Client connections PHD PointX UDA PHD sees 2 “clients” “PointX” Client connections

  24. Deployment - “n” UDAs UDA UDA UDA UDA PHD UDA PHD sees n “clients” UDA UDA

  25. Situation: Many clients call for a snapshot of a single point Does this mean many calls to the COM Connector? Multiple Snapshot Calls

  26. Snapshot subsystem signs up for exceptions in the Connector Exceptions received from the Connector are stored in PI’s snapshot The multiple client calls are resolved in the PI snapshot Multiple Snapshot Calls

  27. COM object written to OSI specifications Only software component coded to interact with foreign data system Spec will be published enable you to build COM Connectors to proprietary data systems Building a COM Connector

  28. You will be expected to implement: get snapshot put snapshot get archive values compressed interpolated timed plottable Building a COM Connector

  29. You will be expected to implement: Sign-up/unsign-up for exceptions get exceptions Building a COM Connector

  30. Buildable using C++, VB uses COM Variant data types PI coerces result into PI internal data type Exception: PI Digital Tags COM Connector responsible for translating foreign string to Digital code Building a COM Connector

  31. Questions?

More Related