My latest status is that the release date has been postponed to early October 2012.
Thanks for asking. We know there is lot of interest in PI Server 2012 and apologize for the delay. The core PI Server components (PI Data Archive and PI AF) will be generally available in October. However, it is likely the PI Data Archive bits will be ready in September. Therefore we can provide early access to that component once it is complete through our User Acceptance Test (UAT), upon request. Just send an email to BetaPIServer@osisoft.com or contact Tech Support regarding UAT.
From PI Server 2012 onwards will the development efforts of both servers (PI & AF) influence the release dates of new major versions of each other? Will they be released together from now on, or is it just because of the performance improvements that we see them influence each other for 2012?
Since PI Server 2010, we have expanded the definition of PI Server to include PI Data Archive, PI AF, PI Event Frames, PI Notifications, PI Analytics, AND MCN Health Monitor. In addition, the runtime license for current PI Data Access products is available with PI Server. Therefore, we have adopted a release "train" where these products are released together. You may have noticed this with PI Server 2010 R3 in Dec 2011. Here is the release announcement for the full PI Server 2010 R3:
Note that initially we released the core PI Server 2010 R3 components that were ready (PI Data Archive, PI AF, PI Event Frames, PI Notifications) then followed up with the PI Data Access components when they were available a few weeks later. We plan to do the same for PI Server 2012.
There are several reasons for this approach:
1. Provide higher value to customers with a complete infrastructure. The PI Server components are becoming more dependent on each other. This started with PI Server 2010 where PI AF (and SQL Server) are now required. With PI Server 2012, there are performance/scalability improvements in PI Data Archive and PI AF SDK, so this is a better together story. Similarly, enhancements in the server components are exposed through PI Data Access. Expect this trend to continue as we go forward.
2. Related to #1, customers are assured the PI Server components have been tested together and verified to be compatible.
3. Help customers plan their PI Server upgrades. We recognize that upgrades must be scheduled to avoid downtime (although this is mitigated when using PI HA), and we expect it is easier for folks to upgrade the full PI Server at one time (which reduces the churn of upgrading individual components). At the same time, we are working to improve how we project release dates on the PI System Roadmap to enable you to schedule an appropriate window to perform an upgrade in your environment.
These are some of the reasons and benefits of going to the train model. Of course high priority patches or security fixes will continue to be released independently as needed. Like Microsoft does with Windows, SQL Server, or Office/SharePoint, we want to deliver the highest impact to our customers with each release so you can get more value from the PI System...