Write a KB article that shows the succession of products
OSIsoft has made many products over the years, and many of those products have been deprecated and/or succeeded. The deprecation/succession documentation is currently scattered.
Based on personal experience, this is extremely confusing for someone new to the PI system. Some newbies might set up a PI system using older products, only to learn later that they should have never used those products and that they should migrate to a newer product. The more cautious newbies will be confused as to why so many products overlap in function, and each one will need to do their own research to find out which program is recommended. This is absurd.
Please write a KB article showing the succession of products. I suggest a table with 3 columns: Predecessor, Successor, and Initial Release Date Of Successor. The Successor column should only ever have 1 product. All predecessors can be stuffed into the same cell in the Predecessor column, ordered by initial release date. A separate KB article might be needed for PI Interfaces, since there are many that are deprecated.
I will share the succession list that I have compiled over the years. It will be in the comments so that I can delete it and repost it if I need to add any programs or make corrections.
Kenneth Barber commented
This list is not guaranteed to be correct. Here it goes:
PI Prerequisites Kit → built into install kits
PI Server = PI Data Archive → PI Server = PI Data Archive + PI Asset Framework
Float16 → Float32 & Float64
PI Users & PI Groups → PI Identities
PI Trusts → PI Mappings
PI Firewall → other firewalls
PI Module Database (MDB) → PI Asset Framework (AF)
PI Batch Subsystem → PI Batch Database → event frames (PI AF)
Zero, span, typical value → limit traits (PI AF)
PI AF Collectives → SQL Server AlwaysOn Availability Groups
PI AF models, layers, ports, & connections → (none)
Sigmafine → (none)
PI Advanced Calculation Engine (ACE) → PI Analysis Service
PI Performance Equations → PI Analysis Service
PI Alarm & PI AlarmView → PI Notifications → notification rules
PI Statistical Quality Control (SQC) → notification rules
PIPC logs → PI Message Subsystem (PI SDK message logs) → Event Viewer → log files
PI API → PI SDK → PI AF SDK
About PI-SDK → PI SDK Utility
API Buffer Server (BufServ) → PI Buffer Subsystem (pibufss) → built into PI Connectors and the PI Connector Relay
Phase 1 UniInt failover → Phase 2 UniInt failover
PI Interface Status Utility & watchdog points → UniInt health points
PI OPC Tool → PI OPC Client Tool
MCN Health Monitor (PI Performance Monitor interface + PI SNMP interface + PI Ping interface + PI TCP Response interface) → PI Connector for PI System Health? → ???
PI Interface for HTML → PI Interface for UFL → PI Connector for UFL → PI Adapter for Structured Data Files
PI Interface for UFL → PI Connector for UFL → PI Adapter for Structured Data Files
PI Interface for BACnet → PI Connector for BACnet → PI Adapter for BACnet
PI Interface for Ping → PI Connector for Ping
PI To PI Interface and its APS Connector → PI System Connector?
PI Interface for DNP 3.0 → PI Adapter for DNP 3
PI Interface for Modbus → PI Adapter for Modbus TCP
PI Interface for RDBMS → PI Adapter for RDBMS
PI Connector for OPC UA → PI Adapter for OPC UA
PI Interfaces → PI Connectors → PI Adapters
PI AF Builder & PI Tag Configurator & PI Module Database Builder → PI Builder
PI OLEDB Provider → PI OLEDB Enterprise → PI SQL Client
PI Web Services → PI Web API
PI BatchView & PI ProcessBook → PI Coresight & PI Coresight for iOS → PI Vision
PI ActiveView → PI WebParts (formerly RtWebParts) → PI Vision
PI Manual Logger Mobile → PI Manual Logger Web → PI Vision (future?)
Qi → OSIsoft Cloud Services
Any OpenVMS PI program (includes PINet) → (none)
PI DataSheet Control → ???
PI ProcessPoint → ???
PI ProfileView → ???
RtBaseline Services → PI Data Services
vCampus → PI Developers Club
PIoneer program → PI Champions