Background

AutoPlant P&ID and other Plant products store information that is related to the electrical component that will be used in the Promis.e project. The Plant Exchange function will read the data for any electrical devices in the Plant project database and place the devices in the Promis.e BOM Explorer. Part numbers can be assigned in Plant or in the BOM Explorer. Once part numbers are assigned, the Insert Symbol By ID tool can be used to place the symbols for the components onto the Promis.e drawings. Attribute information can be edited on the drawings, the Promis.e Data Manager, or the BOM Explorer, and then be transferred back to the Plant database. The exchange of attribute information with Plant is bidirectional through the Exchange module and the user has the ability to specify which data should be the master.

Create a direct link between the Promis.e parts database and the Plant database.

To place symbols in Promis.e from Plant data, it is required to assign a part number that exists as a record in the Promis.e parts database with a valid symbol assigned. The assignment can be done in the Plant application or in the Promis.e BOM explorer. It is convenient to read the Promis.e parts database directly from Plant in order to avoid having to have duplicate entries in two separate databases.

Linking Promis.e Part Number Catalogs to Project Database (prefered method) ¹

Linking Promis.e Part Number Catalogs to Project Database (method 2)¹

Create a linked server in SQL 2005/2008 or Oracle (different code required from shown below). This allows you to pull in data from an access database located anywhere on personal computer drive. You can also locate an Access DB, Oracle DB, SQL DB, Excel Spreadsheet, on a server/ network somewhere else.

Code to create Link Server to MDB file:

EXEC sp_addlinkedserver
@server = 'PromiseLinkServer', @provider = 'Microsoft.Jet.OLEDB.4.0',
@srvproduct = 'OLE DB Provider for Jet',
@datasrc = 'C:\promis-e Data\Databases\ANSI-IEEE_parts_database.mdb'
GO

Code to pull in fields from Ansi catalog via linked server 'PromiseLinkServer' via a view:

CREATE VIEW dbo.promise_partnumber as
SELECT [Part_Number], [Category], [Manufacturer]
FROM [PromiseLinkServer]...[parts_database]
GO

• Now you need to add this to show up in the ProjDb ( Data Manager, I&W ).
• Go to [Project Name][schema][RebisTable] and add 'promise_partnumber'.
• Under the REGAPP field put "DMGR,I&W"
• Launch DM or I&W and now it should be displayed under the tables column.
• Go into Motor List view, and edit the view. Create a pick list for "MODEL NO" field with query: "select distinct Part_Number, Category, Manufacturer from promise_partnumber "
• This will pull in those three fields. The part_number can now be assigned to a motor for example.
• Now when that motor tag is imported into Promise. It is ready to be placed upon the part_number configuration
• Now you can create views, pick lists whatever you want on that catalog data. Data Manager or I&W can also report on or create views off any data in Promise database this way.

Using the link

Go into Promise. Add a part number M987654 Give it a schematic symbol, Single Line Symbol etc.
(Symbols allocated to Part Number)

In Data Manager under the Motor List for example. The MODEL NO field now has a drop down list. Listing all the part numbers in the Promise Part Number catalog. Here I am showing the new part number M987654 created in Promise, now displaying in DM. When this Motor “M-001” is imported into Promise database. It will bring along the part number M987654, in which Promise will recognize. It will know how to place the tag (with it’s rightful Schematic, Single Line symbols ( depending on what mode you are in ). Also the user could change the part number for that motor in Promise, and push that data change back into Project Database. There is two work flows we can promote.
Note: We could even possibly link ProjDb with a DCS system. Some DCS systems link to Oracle or SQL or Excel. We could also pull in data from the DCS system if we had a way to link the DCS tags to the ProjDb tags. Part Numbers could be allocated to Cables, Instruments, Motors, Equipment in Project Database.

foot note: 1. Code provided by Derek Kyryliuk