Preview
HP’s Nov. 24 results call will follow a fall software roundup that puts device-management interfaces and access rules in view. The company’s Nov. 3 notice sets a webcast for 5 p.m. Eastern time to review the fourth quarter and fiscal year ended Oct. 31. Its replay will remain publicly available for about a year. The notice does not announce a discussion agenda for Workforce Experience Platform. The same announcement schedules Personal Systems President Ketan Patel for a Dec. 1 technology-and-AI conference fireside chat.
Labels and access
HP’s Nov. 20 notes rename Fleet Manager as WXP Navigator, Print Manager as WXP Print and WXP Starter as WXP Console. HP says that renaming does not change the suites’ features or functionality.
Asset and Alerts APIs feed device data into IT-service platforms. Access requires a Developer role and Navigator Pro or Elite. Workflow notifications require configured Teams or Slack connectors; the instructions place that workflow interface under Labs. The same roundup locates Smart Refresh under Labs, describes flexible refresh strategies, and restricts that tool to Navigator Pro and Elite plans.
A dated baseline
Quarterly figures provide a separate operating baseline. In its Aug. 26 release for the quarter ended July 31, HP reported $15.7 billion in net revenue, up 12.5% from a year earlier. Personal Systems revenue was $11.8 billion, up 18%, while total units fell 16%. Printing revenue was $3.9 billion, down 2%, and hardware units fell 7%. Consumer and commercial Personal Systems revenue rose 10% and 22%, respectively. Consumer and commercial printing revenue each fell, while supplies revenue declined 3%. Those are historical segment measures, not results for the quarter ended Oct. 31.
HP’s Nov. 10 commentary by CIO Niall Johnston frames employee technology as an experience spanning devices, applications, meeting rooms and AI, rather than separate products. He argues that local processing and cloud computing have different roles, and that employees should not need to navigate that architecture. His discussion emphasizes matching AI to particular roles and workflows rather than treating deployment itself as success. Johnston says employees differ in how quickly they want new AI capabilities, making role-specific understanding distinct from generic instruction.
Johnston also describes data, processes, infrastructure, security and governance as prerequisites for scaling AI. He says general training has limits and that employees need to understand how tools relate to their own tasks. These are the company’s stated design priorities, not independently established productivity gains. He calls cost and reliability fundamental considerations.
