Ryan Gilbert Email & Phone Number

Phoenix, Az, Us

Cambridge, Gb

Cambridge, Gb

AVEVA acquired OSIsoft on March 19th 2021I am continuing my role as a Staff Software Developer on Community / Data Sharing in Aveva Data Hub.

San Leandro, Ca, Us

Technical lead on OSIsoft Cloud Services.

San Leandro, Ca, Us

Responsible for leading a team of software engineers tasked with building the Calculation Engine for the OSIsoft Cloud Services Distributed Data Store. The engine is a high-scale fault-tolerant SaaS solution built on Service Fabric and the ChakraCore JavaScript Engine.

San Leandro, Ca, Us

OSIsoft, LLC is a worldwide manufacturer of Application software for real-time data infrastructure solutions, called the PI System. Founded in 1980, OSIsoft, LLC is privately held and headquartered in San Leandro, CA.I have worked on data acquisition interfaces and PI AF.Data Acquisition Interfaces:Modbus (Serial)Modbus (TCP/IP)XML (OPC XML-DA)Data acquisition interfaces are fault tolerant and highly available services that run 24/7 in customer facilities reading data from sensors, programmable logic controllers, SCADA systems, other distributed control systems, etc. They collect data at high rates of speed and bulk load the values into the PI Data Archive (Time-series database). SDKs:AF SDK (Rich Data Access)I worked on the Rich Data Access portion of the AF Software Development Kit: the OSIsoft.AF.PI and OSIsoft.AF.Data namespaces. As .NET became the standard, the AF SDK took on functionality found in our legacy COM / ActiveX based PI SDK. Our goal was to expose the well-known data access calls in the PI SDK in the AF SDK without incurring a COM Interop peformance penalty, and then carry those over to the AFAttribute class. This allows developers to make rich data access calls against attributes without needing to know the underlying data source, as the plug-in based architecture would route the calls accordingly. The attributes could reference PI points, they could reference rows in a relational database retrieved via parameterized SQL queries, or they could access some other data source via a custom Data Reference plug-in. From the user's perspective, they were all the same.I also worked on adding bulk Rich Data Access calls. These allowed developers to reduce the number of remote procedure calls (RPCs) by batching data access calls. In environments with any significant latency, the bulk calls greatly improved performance.Servers:AF ServerI worked on the T-SQL stored procedures and WCF-based Windows Service that make up the AF Server.

Scottsdale, Az, Us

Following in the footsteps of my mentor, I teach C# Programming Level I and Level II at SCC.

Sequencia was a leading provider of Batch Automation and Product Lifecycle Management Software. The Batch Automation division was sold to Rockwell Automation. Sequencia was acquired by OSIsoft.I worked on ActiveX controls that allowed customers to build custom user interfaces. I also worked on a thin-client collaboration portal and our PLM product suite.Open Batch (now FactoryTalk Batch) ActiveX Controls:Procedure ViewBatch ListEquipment ViewI was responsible for adding features and maintaining several ActiveX controls for Open Batch. The ActiveX controls allowed customers to easily create their own graphical user interfaces for Open Batch without having to create custom controls from scratch. Many of the controls relied on no other built-in OS controls and rendered themselves manually with support for resizing and zoom. They communicated with the server using DCOM.ProcessPoint:Collaboration PortalDisplay EditorBulk UtilityI worked on a thin-client collaboration portal that used the Microsoft XMLHTTP ActiveX objects to reduce the number of server post-backs before the term "Ajax" was coined three years later.I worked on a WYSIWIG (What-you-see-is-what-you-get) display template generator known as the Display Editor. It provided an experience similar to Microsoft FrontPage, and it allowed users to build display templates that could then be rendered in the ProcessPoint PDM Editor. The Display Editor saved the templates as XSLT (eXtensible Stylesheet Language Transformations) which were used to transform the XML data objects into HTML displays. The templates supported control flow structures such as loops and "if-then-else" to repeat or conditionally render portions of the display. Commonly used segments of a display such as headers and footers could be saved and re-used.