OSIsoft has specific standards that ensure each lab is interesting and valuable to all participants. Your chances of acceptance improve when you meet the following requirements:
TECHNICAL LABS: Labs must be developed and delivered by an OSIsoft Partner and must present the value obtained from a PI System based solution. The content delivered in the lab must be development focused or a technical product overview. The content may be a PI System only based solutions or a PI System plus a third party or partner product solutions, but can’t be focused only on third party or partner product. The attendees generally expect to learn about new technical skills in such labs as opposed to commercial exposure. Partner lab content must showcase proven capabilities with at least one more customer references where Partner solution has been successfully deployed in production.""
PI SYSTEM-SPECIFIC BENEFITS: Tangible benefits (monetary, percentages, etc.) and intangible benefits from the PI System must be clearly specified. One popular approach, for example, is to show how you used data from the PI System for condition-based maintenance, making it possible to prevent costly downtime or dangerous events. Process optimization, productivity improvements, cost savings, improved asset lifecycle management, increased safety of operations, etc. are examples of benefits that show the value derived from the PI System. For deeper developer-oriented labs it is OK to spend the bulk of the lab on abstract development concepts; however, it’s recommended that such content is delivered in a way that serves a clear business purposes, as described above.
FOCUS: Subject and scope need to be clearly defined. Labs are 2 or 3 hours long. Leave some time for questions and answers with the audience. The content must be highly focused and right to the point.
Types of labs particularly valued are:
OSIsoft provides the course infrastructure including virtual development environment (VLE) as well as a technical point person inside OSIsoft. We consider content that’s useful to less skilled students as well as more advanced students. We encourage you to propose content that, in your judgment, would be difficult for OSIsoft alone to develop to increase your chances of approval. In your proposal please elaborate on the following items:
DETAILED WRITE-UP OF PRESENTATION:
Please submit additional information about your presentation in either Microsoft Word, Microsoft PowerPoint or PDF format.This information will help determine acceptance.Consider including:
Please note participation in a lab requires a significant amount of time and commitment from the partner. If you submission is approved OSIsoft will assign a point of contact to help guide you through the process and make sure you meet the milestones.
|15 November||Call for papers open|
|15 January||Call for papers close|
|31 January||Acceptance – Partner Lab packet sent to presenters, OSIsoft point of contact assigned|
- 12 April
|Periodic check‐ins regarding progress, information exchange, preliminary reviews, maintain engagement e.g. biweekly or other cadence of mutual agreement by partner and OSIsoft point of contact.|
|9 March||Draft Lab materials and VLE due (just prior to start of rehearsals)|
|12‐23 March||Full run‐through rehearsals of lab using combination of WebEx and VLE.|
|24 March||Final lab books due.|
|12 April||Final VLE due|
|24 April 2018||Start of conference|