Is PI Manual Logger Still Being Developed? Understanding OSIsoft's Approach to Product Feedback
PI Manual Logger remains an active and fully supported OSIsoft product, with user feedback continuously evaluated against development priorities. Recent changes to feedback forums increase transparency around which suggestions will be acted upon, helping users understand PI Manual Logger's current and future development path.
Roshan Soni
Is PI Manual Logger Still Being Developed? Understanding OSIsoft's Approach to Product Feedback
PI Manual Logger is a longtime staple within the OSIsoft PI System ecosystem, designed to facilitate efficient, accurate manual data collection in environments where automation isn’t always feasible. Given its importance in many industrial applications—think field readings, routine inspections, or compliance data capture—it’s no wonder that users regularly check in on the product’s development and future.
So, is PI Manual Logger still actively developed and supported?
Current Product Status and Support
As of now, PI Manual Logger remains an active and fully supported OSIsoft (now part of AVEVA) product. Despite the last visible update in the public Live Library dating back to May 2019, OSIsoft continues to provide technical support, compatibility updates, and critical bug fixes as part of its ongoing product stewardship. This ensures customers reliant on Manual Logger for their data collection workflows are not left behind—especially given the criticality of accurate field data in process industries.
User Feedback and Development Priorities
A key part of OSIsoft’s product management strategy is its transparent approach to user feedback. Users are encouraged to submit feature requests, pain points, and enhancement suggestions through the official OSIsoft Feedback Portal. All OSIsoft products, including PI Manual Logger, are included within this system-wide feedback process.
Recently, users may have noticed more suggestions being marked as "Declined" on the feedback portal. This isn’t unique to PI Manual Logger; it’s part of a larger effort at OSIsoft to increase visibility, transparency, and communication about product development priorities. While every suggestion is reviewed and many are genuinely valuable, not all can be acted upon. By being clear about which ideas will not be pursued, OSIsoft aims to set clear expectations and build trust within its user community.
Why Don't All Ideas Make the Cut?
Product development, especially in complex ecosystems like the PI System, requires OSIsoft to make careful choices about where to invest engineering effort. Factors include:
- User impact and scale: How many customers will benefit?
- Technical feasibility and effort: Is the idea practical to implement?
- Alignment with long-term vision: Does it fit OSIsoft’s strategic direction?
- Resource allocation: Every new feature or change needs testing, documentation, support, and maintenance.
When a suggestion is marked "Declined," that decision reflects careful consideration of the above factors—including balancing ongoing support with adding new features.
Looking Forward: Manual Data Collection in the PI Ecosystem
Although major feature releases for PI Manual Logger may seem infrequent, rest assured that the product is not abandoned. Users can expect continued support and back-end updates to ensure security, compatibility, and reliability. If you're looking for additional capabilities (especially on the web client), submitting feedback through the official portal is still the best way to make your voice heard.
In the broader context, OSIsoft/AVEVA continues to innovate around manual data entry—across PI Manual Logger, PI Vision, and new cloud-based products. If mobile, web-based, or integrated manual data capture is critical to your workflow, keep an eye on the evolving PI System suite for future advancements.
In summary:
- PI Manual Logger is still a supported component within the OSIsoft PI System.
- Feature development is evaluated alongside user feedback and business priorities.
- "Declined" feedback statuses are part of OSIsoft’s broader effort to communicate more transparently about what is—and isn’t—on the roadmap.
For the latest information, monitor the official PI System forums, feedback site, and product documentation. And as always, keep sharing your insights to help shape the future of manual data collection in the PI ecosystem!
Tags
About Roshan Soni
Expert in PI System implementation, industrial automation, and data management. Passionate about helping organizations maximize the value of their process data through innovative solutions and best practices.
No comments yet
Be the first to share your thoughts on this article.
Related Articles
Enhancing PI ProcessBook Trends with Banding and Zones: User Needs, Workarounds, and the Road Ahead
A look at the user demand for trend banding/zoning in OSIsoft PI ProcessBook, current VBA workarounds, UI challenges, and how future PI Vision releases aim to address these visualization needs.
Roshan Soni
Migrating PIAdvCalcFilVal Uptime Calculations from PI DataLink to PI OLEDB
Learn how to translate PI DataLink's PIAdvCalcFilVal advanced calculations—like counting uptime based on conditions—into efficient PI OLEDB SQL queries. Explore three practical approaches using PIAVG, PIINTERP, and PICOunt tables, and get tips for validation and accuracy.
Roshan Soni
Understanding PI Web API WebID Encoding: Can You Generate WebIDs Client-Side?
Curious about how PI Web API generates WebIDs and whether you can encode them client-side using GUIDs or paths? This article explores the encoding mechanisms, current documentation, and best practices for handling WebIDs in your applications.
Roshan Soni