YetAnotherForum
Welcome Guest Search | Active Topics | Log In | Register

PI Points Relationship other than Time Options · View
blitzclipse
#1 Posted : Wednesday, September 15, 2010 5:36:30 PM
Rank: Member
Groups: Member

Joined: 1/15/2010
Posts: 13
Location: us
We have recently converted to the PI data historian and have utilized Rhys as well as other contractors for certain projects; however, we have hit a road block. We need to know what the best method would be for grouping data that is not time related. In example, we have raw materials that come in on a ship. For this ship, we need to relate the pi data. IE we need to relate the ship name, quantitly, various lab samples, and BOL information into a report. All information is stored in PI points; however, since we unload multiple ships at the same time and our lab points are generic to the type of raw material, we need a way to easily allow the data to be related other than time. The time that the information is entered might not be the same. IE: we get samples from the ship during the 3 days that it takes to unload it. Plus we get information about why the ship stoped unloading, when it started/ stopped, and how much material is in each hold of the ship. What is the best way to relate this data?
Sponsor  
 

OSIsoft vCampus is a subscription-based, online offering that consists of providing everything people need to develop applications on the PI System.
We invite you to take a "tour" of the OSIsoft Virtual Campus - also feel free to consult the FAQ  or contact OSIsoft vCampus for more details.
RJK Solutions
#2 Posted : Thursday, September 16, 2010 10:39:10 PM
Rank: Administration

Groups: Administration

Joined: 6/20/2008
Posts: 617
Location: Cheshire, United Kingdom.
Howdy...

Sounds like you need something like EventFrames, which is still only a CTP on vCampus.

How are you getting your data in to PI? Manual Entries, Automatic (e.g. samples from a LIMS to PI interface) or a combination of both?
One option would be to tag the data using Annotations (ValueAttributes) to store the "Ship Name/Number", to use another point attribute to store additional information (e.g. ExDesc, InstrumentTag) or have a clever method for creating PI tags (using AF for the structure and templates). As you know, AF would be the preferred approach unless there is something in the way you are collecting all the data that would prevent this.

The idea being you treat each ship as an Element (a Ship Element Template) and each time it docks with you the Ship element has a child Element (a Docked Element Template) that has attributes such as "Arrival Time", "Departure Time"...would need to analyse all the information you capture and how you capture it for a firmer plan of action.
Then your reports (Excel/Sharepoint) just look at AF, you see the list of ships, each ships docking events and the associated data for that particular event such as the status via digital states: Unloading, Halted...

Hope this helps.
Principal Consultant
Real-Time Data Management @ Wipro Technologies
blitzclipse
#3 Posted : Friday, September 17, 2010 2:46:01 PM
Rank: Member
Groups: Member

Joined: 1/15/2010
Posts: 13
Location: us
Rhys:

Thanks for the reply. I didn't think about writing values to the other point attributes. Can one view the point attributes in AF? I was thinking that it might best suit me to use a sql view for the pi data that is a linked table; however, the only way that I see showing it in AF would be to utilize the lot number that would be in one of the point attributes. That way the time on the AF query tool would be able to look ship name tag for that time and the lot number of that ship would be used to match the table. I am not sure how to see the pi point attributes in AF.

I don't think I could directly do it in AF because of the data. The ship names change; however, sometimes they are the same because the ship doesn't go far and returns back to us. Plus we have loading samples that occur during the loading / unloading of ships. Then we have a final composite sample that is ananlyzed.

I think one could use sql / pi oledb to make a view that looked at the lot number and displayed tag values based on the match of the lot number. What do you think?

Would PI batch possibly solve my problems?
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.