The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Technically, the CCC should probably have been pkfox ( @petepjksolutionscom ) ... but it's getting iffy as he didn't actually post the last one - which wasn't solved - and is probably nursing a HUGE hangover!
Assuming no objections, I'll take it back and do a reboot on Monday to get us squared away.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
One of my favorite (and criminally under appreciated) songwriters passed away a few days ago, a songwriter that could tell wonderfully vivid stories through song. Guy Clark[^].
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
When I stopped playing with the system, this server was archiving live process data from around 7500 plant parameters across 5 platforms and about 18 systems, all pumped down a 120 mile subsea fiber optic link, and then once archived, a secondary system pushed a sub-set out over a private vlan on the net to another company 18 miles away.
The headaches I had over the years were plentiful!
Oh, and a second parallel system connected to two of the end points archived event log data into another different SQL logger, which resulted in me having to dream up this; Developing Automated Data Purge Solution[^]
That was a pain to keep alive!
Started using the PI system in the early 90s; wrote custom interfaces (digital scales, bar code readers) on a VAX/VMS system.
Now, working for a utility company working 100% of the time in PI... I think we have about 85 PI Historians, 500+ interfaces, a few million tags....
Work mostly with renewables (wind, solar) spread across the continental U.S.... never a dull day! And absolutely enjoy my job!
Hope all is going well with you... enjoying the sun, sand and warm weather and all.
Your OSI license fees must be scary for a few million tags!
I had too much other stuff to do that never really got my hands deep and dirty with it (except the initial system installation and then the fist couple years of adding more 'stuff'), we had a team of controls guys looking after all the ESD/Control systems, so they took it over.
We have a PI Support Group of 11 people (including the manager) and that is all we work on.
However, 1 is retiring at the end of the month, 2 more may be retiring by year end, 1 is a contactor and he may or may not be back next year... we are about to get 'lean'.. in a hurting way.
And, the average age of the group is in the upper 50's... we struggle to get 'the younger crowd' to take an interest in it.
The OSISoft PI system has been around since the early/mid 80s. It was started by Pat Kennedy who had extensive experience in the oil/gas industry. The original name was "Oil Systems Incorporated". The system was designed to capture volumes of information from networked devices and stores the data in a proprietary format. The concept was always make data available to make informed decisions.
So, versus the IoT... OSISoft was around long before the IoT. As for '500+' interfaces, that is for the place where I work. We have 500+ interfaces, but that includes multiple instances of a particular type of interface such as: OPC, DNP, HabConnect, MODBUS, PI-to-PI (data transfer between systems) and, we have some custom written interfaces.
thanks for the info - shame you can't get younger people interested - if they cant program in node.js a lot of them dont seem interested - if I were in your neck of the woods I'd be asking what sort of experience I need to replace one of your retirees