Skip navigation
All Places > PI Developers Club > Blog > Author: skwan

PI Developers Club

9 Posts authored by: skwan

Hi vCampus Members,

 

We are excited to announce the availability of our next milestone: PI Server 2015 Beta 2. This release includes PI Data Archive 2015 Beta 2 (3.4.395.15) and PI AF Client 2015 Beta (2.7.0.6298).

 

The files are available in the Download Center under Pre-Release.

 

For those of you that missed both our previous announcements, Beta 2 showcases two of the major features of PI Server 2015:  (1) the ability to store time series data with future time stamps and (2) the ability to migrate PI Batch data to PI Event Frames.  As with any pre-release software, please review the accompanying documentation for features and limitations before proceeding too far.  Please conduct your evaluation in a test environment, not a production environment.

 

Here’s a highlight of what’s new in Beta 2 since the first Beta:

 

Installation

 

-          The license machine signature file (MSF) is generated automatically.

 

-          Any license mismatches are detected and reported.

 

-          The services will be started after installation completes.

 

-          The PIHOME and PIHOME64 paths are configurable for new installations.

 

-          PI System Management Tools (SMT) 2015 Beta 2 (3.5.0.32) is distributed.

 

-          PI Collective Manager 2015 Beta 2 (1.3.0.5) is distributed.

 

Future Data

 

-          Future tags support annotations.

 

-          Trends – with released PI ProcessBook, PI Coresight, and PI System Explorer – with both a start time and end time in the future now display data if it exists.

 

-          With PI Collective Manager 2015 Beta 2 (1.3.0.5), collectives can now be created and re-initialized with future archives.

 

-          With PI Collective Manager 2015 Beta 2 (1.3.0.5), the path for future archives on a secondary can be configured independently at the time of collective creation or re-initialization.

 

Migration of PI Batch data to PI Event Frames

 

-          With PI SMT 2015 Beta 2 (3.5.0.32), PI AF Link initiates analysis of PI Batch Subsystem units and batches and displays the results, including any errors.

 

-          Once migration is initiated, any batches for PI Batch Subsystem units that are mapped to the PI Module Database are migrated to PI Event Frames.

 

-          The PI Batch Subsystem is disabled for write access once migration has been initiated, causing write attempts to fail with error “[-19600] PI Batch Database is read-only because migration to PI Event Frames is in progress.”

 

-          The PI Batch Subsystem is disabled for write access after migration completes, causing write attempts to fail with error “[-19601] PI Batch Database is read-only because migration to PI Event Frames has completed.”

 

PI System Management Tools

 

-          Fixes for bugs reported since the first Beta (3.5.0.12)

 

 

 

As a reminder, here’s a highlight of the changes in the first Beta since CTP1:

 

                Installation

 

-          Upgrades are supported from 64-bit versions of PI Data Archive PR1 SP1x (3.4.375.80) and later, including CTP1.

 

-          PI AF Client 2015 Beta (2.7.0.6298) is included.

 

-          PI System Management Tools (SMT) 2015 Beta (3.5.0.12) is included.

 

-          PI Collective Manager 2015 Beta (1.3.0.1) is included.

 

-          PI SDK 2014 (1.4.4.484) is included.

 

-          PI Buffer Subsystem 4.3.0.28 is included.

 

-          .NET Framework 4.5.2 is required and included.

 

-          The path for future archives can now be specified.

 

-          The limitation with 1-CPU machines has been removed, but 2+CPUs are recommended.

 

                Future Data

 

-          PI AF Client 2015 provides enhanced data access capabilities for future tags via AFDataPipe, AFDataCache, and new methods for specifically differentiating current value from end-of-stream value.

 

-          Automatically created future archives always start with an initial size of 1 MB and grow dynamically.

 

-          Automatically created future archives always have a duration of one calendar month: either 28, 29, 30, or 31 days.

 

-          The location of automatically created future archives is completely independent from the location of automatically created historical archives; this location is initially specified during installation and can be changed afterwards with the PI SMT 2015 Archives plug-in.

 

-          PI SMT 2015 Archives plug-in has been re-worked: there is a tab per server, there are separate tabs for historical and future archives, the automatic creation settings can be configured without using the PI SMT Tuning Parameters plug-in, disk free space and usage is displayed for the drives configured for automatic archive creation, etc.

 

-          PI SMT 2015 Point Builder plug-in can create future tags from the “General” tab by setting “Future Data” to “Allow.”

 

-          PI SMT 2015 CurrentValues plug-in returns the value at server’s current time for future tags instead of the SYSTEM digital state “Future Data Unsupported.”

 

-          Attempts to write annotations to future tags are rejected with error “[-11170] Annotation not supported for future tags.”  Support will be added before final release.

 

                Migration of PI Batch data to PI Event Frames

 

-          PI SMT MDB to AF Synchronization plug-in has been renamed to “PI SMT AF Link” to reflect the fact that it orchestrates both migration of the PI Module Database (MDB) to AF as well as the migration of PI Batch data to PI Event Frames.

 

-          PI SMT AF Link has been enhanced to configure the appropriate security in PI AF to handle the migration.

 

-          PI SMT AF Link has been enhanced to initiate analysis of the PI Batch Database before migration to PI Event Frames.  It displays the results of the analysis, including any errors (organized by category), archive gaps, and missing PI Identity Mappings.

 

-          PI SMT AF Link has been enhanced to initiate migration after analysis.  During migration, it provides status updates; after migration, it displays a final report, including whether any names were changed or errors were encountered.

 

-          PI Campaigns are migrated to PI Event Frames.

 

-          Empty procedure names and batch IDs are accounted for during migration.

 

-          The PI Unit index is forcefully synchronized with the MDB before analysis and migration.

 

-          Migration uses a set of derived PI Event Frame templates: PICampaignMigrated, PIBatchMigrated, PIUnitBatchMigrated, PISubBatchMigrated_L1, PISubBatchMigrated_L2, PISubBatchMigrated_L3, and PISubBatchMIgrated_L4.

 

-          The PI Batch Database is disabled for write access once migration has been initiated, causing write attempts to fail with error “[-19600] PI Batch Database is read-only because migration to PI Event Frames is in progress.”

 

-          The PI Batch Database remains disabled for write access after migration completes, causing write attempts to fail with error “[-19601] PI Batch Database is read-only because migration to PI Event Frames has completed.”

 

 

 

Just like before, if you have any questions or wish to provide feedback, please contact us at BetaPIServer@osisoft.com.

 

Thank you for your continued engagement.

Hi vCampus Members,

 

We are excited to announce the availability of our next milestone: PI Server 2015 Beta, which includes both PI Data Archive 2015 Beta (3.4.395.11) and PI AF Client 2015 Beta (2.7.0.6298).  Please note that since CTP1 back in May, the name of the release has changed from “PI Server 2014 R2” to “PI Server 2015” to more accurately reflect the release date of our final milestone.

 

For those of you that missed our CTP1 announcement, Beta showcases two of the major features of PI Server 2015:  (1) the ability to store time series data with future time stamps and (2) the ability to migrate PI Batch data to PI Event Frames.  As with any pre-release software, please review the accompanying documentation for features and limitations before proceeding too far.  Please conduct your evaluation in a test environment, not a production environment.

 

Here’s a highlight of what’s new in Beta since CTP1:

 

Installation

  • Upgrades are supported from 64-bit versions of PI Data Archive PR1 SP1x (3.4.375.80) and later, including CTP1.
  • PI AF Client 2015 Beta (2.7.0.6298) is included.
  • PI System Management Tools (SMT) 2015 Beta (3.5.0.12) is included.
  • PI Collective Manager 2015 Beta (1.3.0.1) is included.
  • PI SDK 2014 (1.4.4.484) is included.
  • PI Buffer Subsystem 4.3.0.28 is included.
  • .NET Framework 4.5.2 is required and included.
  • The path for future archives can now be specified.
  • The limitation with 1-CPU machines has been removed, but 2+CPUs are recommended

Future Data

  • PI AF Client 2015 provides enhanced data access capabilities for future tags via AFDataPipe, AFDataCache, and new methods for specifically differentiating current value from end-of-stream value.
  • Automatically created future archives always start with an initial size of 1 MB and grow dynamically.
  • Automatically created future archives always have a duration of one calendar month: either 28, 29, 30, or 31 days.
  • The location of automatically created future archives is completely independent from the location of automatically created historical archives; this location is initially specified during installation and can be changed afterwards with the PI SMT 2015 Archives plug-in.
  • PI SMT 2015 Archives plug-in has been re-worked: there is a tab per server, there are separate tabs for historical and future archives, the automatic creation settings can be configured without using the PI SMT Tuning Parameters plug-in, disk free space and usage is displayed for the drives configured for automatic archive creation, etc.
  • PI SMT 2015 Point Builder plug-in can create future tags from the “General” tab by setting “Future Data” to “Allow.”
  • PI SMT 2015 CurrentValues plug-in returns the value at server’s current time for future tags instead of the SYSTEM digital state “Future Data Unsupported.”
  • Attempts to write annotations to future tags are rejected with error “[-11170] Annotation not supported for future tags.”  Support will be added before final release.

Migration of PI Batch data to PI Event Frames

  • PI SMT MDB to AF Synchronization plug-in has been renamed to “PI SMT AF Link” to reflect the fact that it orchestrates both migration of the PI Module Database (MDB) to AF as well as the migration of PI Batch data to PI Event Frames.
  • PI SMT AF Link has been enhanced to configure the appropriate security in PI AF to handle the migration.
  • PI SMT AF Link has been enhanced to initiate analysis of the PI Batch Database before migration to PI Event Frames.  It displays the results of the analysis, including any errors (organized by category), archive gaps, and missing PI Identity Mappings.
  • PI SMT AF Link has been enhanced to initiate migration after analysis.  During migration, it provides status updates; after migration, it displays a final report, including whether any names were changed or errors were encountered.
  • PI Campaigns are migrated to PI Event Frames.
  • Empty procedure names and batch IDs are accounted for during migration.
  • The PI Unit index is forcefully synchronized with the MDB before analysis and migration.
  • Migration uses a set of derived PI Event Frame templates: PICampaignMigrated, PIBatchMigrated, PIUnitBatchMigrated, PISubBatchMigrated_L1, PISubBatchMigrated_L2, PISubBatchMigrated_L3, and PISubBatchMIgrated_L4.
  • The PI Batch Database is disabled for write access once migration has been initiated, causing write attempts to fail with error “[-19600] PI Batch Database is read-only because migration to PI Event Frames is in progress.”
  • The PI Batch Database remains disabled for write access after migration completes, causing write attempts to fail with error “[-19601] PI Batch Database is read-only because migration to PI Event Frames has completed.”

PI Server 2015 Beta is available for you to download under the Pre-Release category in the vCampus download page.  Just like before, if you have any questions or wish to provide feedback, please contact us at BetaPIServer@osisoft.com.

 

Thank you for your continued engagement.

 

Regards,

 

PI Server Team

skwan

PI Server 2014 R2 and Beyond

Posted by skwan Aug 29, 2014

As you may have already noticed, PI Server 2014 R2 has been released.  More specifically, PI AF, a component of the PI Server, has been updated to version 2.6.1.  This release corrects several issues with notification upgrades in PI AF 2014 (v2.6) which I know affected some of you.  My apologies for the issues that you may encountered.  This release also introduces steam functions to analyses.  Now you're able to calculate steam properties in your analyses using the latest IAPWS-IF97 (industrial formulation) standards.  There are many other fixes and enhancements in this release so please consult the relevant release notes and documentations for details.  There are many more enhancements on the way so if you have any specific features that you need, please let me know.

 

I have received some questions and comments on our current naming convention.  I want to take this opportunity to remind everyone that back in 2010, we made a strategic move to redefine what "PI Server" means.  Today, the PI Server is not a single product, but rather it consists of several components.  These components include the PI Data Archive, PI Asset Framework, PI Notifications, PI ACE and a few interfaces for monitoring the health of the servers.  Therefore, although this release consists of an upgrade to PI AF, it is considered an upgrade to the PI Server and hence the PI Server 2014 R2 label.

 

Lastly, for those of you that may be testing the PI Data Archive CTP which provides for native support for data with future time stamps, you may have noticed that the estimated release date is now Q2 2015.  As such, we're tentatively labeling it "PI Data Archive 2015", which is a change from past communications.  I wanted to bring this up in this blog post to minimize confusion.

 

Feel free to consult the PI System Roadmap for the latest information on product releases.  Hope to see you all at the Lisbon User's Conference in a few weeks.

 

--

 

Steve Kwan

skwan

Back to the Future

Posted by skwan May 14, 2014

Hi vCampus Members,

 

We are excited to announce the availability of our first Community Technology Preview (CTP) of the next major version of the PI Data Archive, code-named “DeLorean” and tentatively labeled “PI Data Archive 2014 R2”.  This release introduces two major features:  (1) the ability to store time series data with future time stamps and (2) the ability to migrate PI Batch data to PI Event Frames.  As with any CTP, please review the limitations detailed in the accompanying documentation before proceeding too far, and please conduct your evaluation in a test environment.  You can download the files from the Download Center in the Pre-Release category.

 

Prior to DeLorean, the PI Data Archive rejected data with timestamps that were greater than 10 minutes into the future relative to the server’s clock.  Because of this limitation, users that still needed future data have been forced to deploy complex and costly workarounds that offer a limited user experience at best.  CTP1 finally removes this limitation and allows you to store data with timestamps throughout the entire UTC time range:  January 1970 to January 2038.  In order to support this new storage capability, the PI Data Archive is introducing the concept of “future PI Points” or “future tags” allowing separation from all the data for traditional “historical PI Points” or “historical tags”.  While the PI Data Archive is critical to unlocking the value of future data in the PI System, many more components – particularly our PI System Access (e.g., PI AF SDK) and PI Visualization (e.g., PI Coresight and PI ProcessBook) products – are also getting updated in order to deliver a superior user experience.  New versions of these other products are not available with CTP1, but we are providing detailed documentation on limitations and workarounds based on released versions so that you can start your evaluation of future data right away.

 

PI Event Frames were introduced several years ago, and rollout of their implementation throughout the PI System has occurred in different waves.   As we near the completion of “Wave 2”, we are focusing our efforts on providing PI Event Frames support for standard PI Batch users.  CTP1 provides the ability to perform a complete, one-way migration of your PI Batch data to PI Event Frames in order to establish a new system of record.  During and after migration, the entire PI Batch database remains in a read-only state for reference purposes.  Just like with future data storage, CTP1 has several limitations, so please consult the accompanying documentation for details.

 

Even though CTP1 is not feature complete and has significant limitations, soliciting early feedback from our technical and forward-thinking vCampus community will only make our upcoming release that much more reliable and valuable.  We build the OSIsoft ecosystem together, and we hope that you share our enthusiasm for DeLorean’s features and their potential for the PI System.  If you have any questions or wish to provide feedback, please contact us at BetaPIServer@osisoft.com.

 

Thank you for your time and vibrant engagement.

 

Regards,

 

Doc Brown and the PI Data Archive Team

Over the last few weeks, many of my colleagues in engineering have been busy building and testing software so that I can make this announcement.  With that I'm happy to announce that we're making a beta available for you.  This beta consists of:

  • AF Server 2014
  • AF Client 2014 which includes the Asset Based Analytics Client (aka Abacus client) and the Analysis Management Plugin to PSE
  • PI Analysis Service (aka Abacus scheduler)
  • The next generation PIBufSS
  • Kitchen sink

Whew, what a mouthful!  (Ok, not really the kitchen sink, but  you get the idea - there's a lot of stuff in this beta.)   It goes without saying that I'm extremely proud of the work that the engineering teams have done and I encourage all of you to give them a pat on the back during vCampus Live! 2013 while you get the chance to play with many released and unreleased software.  You are coming to this event, aren't you?  If you haven't decided, please do check out the agenda here.

 

There are so many enhancements I don't think I can cover them all in a blog post.  So here are a few personal favorites just to wet your appetite.  In no particular order:

  • Support for Buffered writes via PIBufSS
  • Parameterized AF Tables.  Optional separation of AF Table Connections from AF Tables.
  • Faster Searches, in particular, bulk path lookup and template-based attribute searches
  • PI System Explorer (PSE)
    • Lightweight trend in PI System Explorer
    • Improved Search UI in PI System Explorer
    • Both 32 and 64 bit PSE
  • Event Frame enhancements, including new searches, locked event frames, duration displayed in PSE
  • Data Access
    • Support for the Bulk RPCs in PI Data Archive 2012
    • DataPipe on AFAttributes
    • DataCache
    • Digital State Set editing
    • PI Identity and Mapping exposure
    • Find PIPoint Metadata changes
    • Tracing
    • Ability to pass windows credentials for off-domain windows connection
  • New String Builder Data Reference
  • PI Builder support of Tag Configuration and Analytics.  Support for 64-bit Excel.
  • Audit Trail and Audit Trail Viewer (must be enabled via command line, requires SQL Server Enterprise or higher)

In all we completed several hundred work items including enhancements and fixes.  I would suggest you read the release notes to get all the details.

 

Before you run off and download the beta, I want to describe to you something we added to Abacus in this beta.

 

The Asset Based Analytics functionalities are new to the PI System.  It’s critical that we fully understand the typical usage pattern of the users and how the system reacts to these use cases.  As such, this beta incorporates the ability to collect and provide back to OSIsoft ANONYMOUS usage statistics from the use of the analytics features (only).  The statistics that is collected has no identifiable information which can be used to trace back to the user or any particular computer.  In addition, no business logic or actual data is collected.  Below are examples of some of the statistics that are collected:

  • # of Analysis Processors
  • Fractional CPU
  • Computer memory profile
  • # of Performance Equation functions used (but not the business logic)
  • PE functions used (but not the business logic)
  • # of different types of analyses
  • # of analyses in various states (running, in error, etc.)
  • Latency
  • Analyses queue statistics
  • Evaluation count
  • Error count
  • Statistics on backfilling
  • Statistics on Rollups
  • Statistics on User Interface (UI) actions

The current plan is for user to be able to voluntarily opt-in to providing anonymous statistics to OSIsoft in the release product.

 

So if you're interested in trying out this beta, please go to the download center and select the Pre-Release category.  If  you have any question or comments, feel free to start a discussion thread or email me directly at: skwan@osisoft.com.  Feedback and support related questions to the beta can be sent to any one of the following dedicated mailboxes: BetaAF@osisoft.com, BetaAnalytics@osisoft.com and BetaBufSS@osisoft.com.

 

 

 

See you at vCampus Live! 2013

 

 

 

--

 

Steve Kwan

 

Product Manager

 

 

skwan

PI AF 2012 - where art thou?

Posted by skwan Oct 2, 2012

 

 

So here I am eating my breakfast and reading my emails.  Among them are a couple of emails from users asking about the release date of PI AF 2012.  As some of you may know, we had originally planned on releasing it at the end of 3Q, which passed 2 days ago.  As the product manager, it goes without saying that I’m very excited that users are waiting for this release (similar to an iPhone release?  ).  So I want to give everyone a status update on PI AF 2012.  We built release candidate 1 and made it available to select external users for testing on 9/22.  We have received a handful of bug reports from both internal and external users some of which we’re fixing.  We’re hoping to build release candidate 2 later this week and if all goes well, it will be generally available later this month.

 

For those who are impacted by this slippage of the release date, please accept my sincere apologies.  This release has significant changes and enhancements to the AFSDK requiring very significant testing efforts.  Rest assured the development team is working their tails off to get this out the door as soon as possible.  Feel free to contact me directly at skwan@osisoft.com if you have additional questions or comments.

 

 

 

 

skwan

PI AF 2012 Beta 3

Posted by skwan Aug 3, 2012

A funny thing happened to me on my way to work this morning.  My good friend and fellow Product Manager, Mr. Steve Pilon, the esteen PM for our data access products, wanted me to eat my last post.

 

http://vcampus.osisoft.com/discussion_hall/development_with_osisoft_sdks/f/28/t/3221.aspx

 

in which I mentioned the PI AF 2012 Beta 2 was going to be the last beta released to vCampus prior to the release.  Well, ignore that post, because PI AF 2012 Beta 3 is here and available for you to download at the download center under pre-release.  This beta 3 provides support for PI OLEDB Enterpise (beta) to access PI Event Frames.  Please see this blog post on PI OLEDB Enterprise

 

http://vcampus.osisoft.com/bloggers_place/b/pm/archive/2012/08/03/pi-oledb-enterprise-2012-beta-now-available.aspx

 

You will of course need to install the Beta 3 PI AF Server with event frames support.  The PI AF 2012 Beta 3 also provides additional bug fixes since beta 2 in the PI AF Client so you should find it fairly stable.  The release is coming up real soon

 

If you find any problems with this Beta 3, you can contact me at skwan@osisoft.com, post on the forum.

 

Thanks, Steve

 

 

skwan

PI AF SDK - Rich Data Access

Posted by skwan Feb 10, 2012

Hi folks,

 

For those of you who attended the last vCampus Live! in November, you may have overheard or even participated in conversations with us on the work that we've been doing with rich data access (RDA) and the PI  AF SDK.  For the benefit of those who do not know what this is, in a nutshell, we have been busy enhancing the AF SDK so that it would allow you to directly access PI Server data directly in AF Attributes using the AF SDK.  Some of you may have been developing .NET-based multi-threaded applications using a combination of the AF SDK and the PI SDK in order to access PI AF and PI Server data respectively.  In this case, you may have run into STA/MTA threading issues, as well as performance issues with COM Interop.  The AF SDK with RDA functions will allow you to use a single .NET 4 based SDK to access data from the PI System, i.e. PI AF objects and PI Server data, thereby avoiding those issues.  In addition, the AF SDK with RDA functions may provide performance improvements depending on the architecture and implementation of your application.

 

The PI AF Client 2012 CTP setup kit is now available in the vCampus Download Center.  This kit consists of two versions of the AF SDK; a .NET 3.5 version that retains backwards compatibility with your existing applications and a .NET 4 version that implements RDA, and includes PI System Explorer and PI AF Builder.  Along with the PI AF Client setup kit, there is also an updated PI AF Developer Tools setup kit and a README that describes the improvements and changes.  We will continue to ship both the .NET 3.5 and .NET 4 versions of the AF SDK so if you do not have the need for the new RDA functions, you do not have to do anything and your applications will continue to work.  If you wish to use the new RDA functions, you will need to implement the methods provided to you in the two new namespaces that have been added to the AF SDK: OSIsoft.AF.Data and OSIsoft.AF.PI.

 

Of course the PI SDK continues to be fully supported.  It’s important to note that if your application is based on the PI SDK and you are not using the AF SDK or if you have no need for the RDA functions in the AF SDK, then you do not have to do anything.  Rest assured that your applications will continue to work and be supported going forward.

 

This CTP is just that, a preview, so it is not intended nor recommended to be used in a production environment.  There are some features and functions that are not yet finalized at this time and much refinement is to be done in many areas.  This SDK is evolving and will continue to do so over the next few releases.  The initial release will happen later this year along with PI DataLink.  Keep your eyes on the PI System Roadmap for updates.  It is worthwhile to remind everyone that this is one element of our PI Data Access product suite and as such its usage is governed similarly, i.e. vCampus license for Development use and PSA license for Runtime use.

 

I urge you to spend some time evaluating this CTP.  In addition to any bug reports, we are extremely interested in any performance comparisons of the RDA functions in your applications that you are willing to share.  You may of course post to the vCampus forums or you can send them to us via email.  Any data you send directly to us will be kept strictly confidential.  Please use the BetaAF@osisoft.com mailbox to report back any comments, questions or problems that you may have with this CTP.  The BetaAF mailbox is monitored by myself, the PI AF product specialists and the PI AF development team.  Please do not contact our regular Tech Support as they are not prepared to answer your questions regarding this CTP.  Lastly, keep your eyes out for an upcoming vCampus webinar on this CTP later this month.

 

And oh, one more thing, check out the enhancement to AF Tables

 

--

 

Steve Kwan, PI AF Product Manager

skwan

AF, AF 2010, AF 2010 R2, ...

Posted by skwan Nov 24, 2010

So, this is my first blog at vCampus.  Actually this is my first blog ever, anywhere .  First a quick introduction, my name is Steve Kwan and I'm the Product Manager for AF.  I joined OSIsoft back in June this year (2010) and I have to say I'm very fortunate to work with a smart and talented group of people at OSIsoft.  I was met some of you vCampus members at the vCampus Live! event a few months ago and I've been trying to get smarter by following the vCampus community via forums and such.  I have to say I'm amazed by the experience and expertise of the vCampus community.

 

As you may already learned by my post on vCampus last week, AF 2010 R2 was posted as a Community Technology Preview (CTP) for the vCampus community.  AF 2010 R2 would be the first AF release that I'm involved with at OSIsoft as product manager.  I am fortunate enough to have a great bunch of very smarts people developing what I feel is an extremely important piece of software as we move the PI System from a tag centric world to an asset centric world.  I have already seen some great work produced by OSIsoft's partners, system integrators, etc. that leverage the features and functions of AF.  I'm proud to be part of this evolution.

 

AF 2010 R2 will provide to you a very important piece of software, the AF Builder.  For many people, it will be the primary way to interact with AF.  Our work is not complete, there are many features and functions of AF that aren't yet supported by the AF Builder.  We will continue to improve on it, hopefully with your feedback and encouragement.  AF 2010 R2 also includes a whole slew of fixed and enhancements that are spelled out in the released notes.  Please consult these release notes for additional details.  As of this time, we're looking at releasing AF 2010 R2 some time towards the latter part of December.

 

We release CTP to the vCampus community for several reasons.  First off, you deserve the opportunity to be the first to try out the latest and greatest.  More importantly, I know you won't be bashful in providing useful feedback to us to improve the software.  So don't be shy, give it a try and by all means, provide to us any feedback that you may have via forum postings or emails.  You are welcome to email BetaAF@osisoft.com and myself at skwan@osisoft.com

 

Looking ahead past AF 2010 R2 into 2011, we have plans to add a bunch of features and enhancements to AF.  Many other OSIsoft products will be released based on the infrastructure AF provides.  Stay tuned, myself and the other product managers will keep you updated.  For a sneak peak, please visit our PI Product Roadmap webpage at: http://techsupport.osisoft.com/TechSupport/NonTemplates/roadmap.aspx

 

Best regards,

 

Steve Kwan

Filter Blog

By date: By tag: