Pharos: Enterprise Print Management System Upgrade


pharos.jpg
Quick View
Summary: 

Note:  Data issues resolved as of 08/16/09.  Data issues have been found which do not let some students print.  We are actively working on this for a resolution. 

================================================================================================================= 

At this time, Windows 2008 for servers has not been tested and certified for enterprise use by UTO.  Therefore the production servers for this project will be setup with Windows 2003. Pharos 8.0 is compatible with Windows 2003 but will need additional patches applied.

================================================================================================================= 

Note:  The project timeframe has been extended to May 31, 2009.  This was done due to an expected release of version 8.1 by the vendor.  IT Since the vendor will not be able to provide version 8.1 in time for this project, we are proceeding as originally planned with version 8.0.  

=====================================================================================================================

ASU will be upgrading to version 8.0 which includes support of SQL clustering., The part of the upgrade will be done over the Spring Break from March 8 - 15, 2009, the remainder will be completed by May 31, 2009.

Pharos Systems is the university print asset management system.  The system provides chargeback for use of the print resources available to the university community.  The current focus of the system is chargeback from public-facing printers in the labs, classrooms, and library.

The proposed project is twofold.  The first objective is the upgrade of the enterprise environment to the current version of the software, version 8.0.  Upgrading the system provides:

  • Secure Release Here - allowing multiple printer servers to communicate print job information so that a user can send from one location and printer to an unrelated location.  This allows greater flexibility for the end users.
  • Offline capability - users are able to continue to print even with a communication lose to the database server.  When the database or communications are re-established, the transactions are transmitted and processed.
  • Simplified installers.
  • Enhanced Canon MFD support

The second objective is the combination of the UTO managed Pharos environment into the enterprise environment.  This reduces the complexity and management time for two systems.  The desktop release that is currently available in the UTO managed labs and classrooms will be available for other labs and classrooms across the university as well as public end user computers.  Allowing true "print anytime anywhere".

Other advantages:

  • Address issues with the new Community Card
Start Date: 
October 1, 2008
Go Live: 
August 21, 2009
End Date: 
December 18, 2009
Current Milestone: 
11/30/2009 -- Addressing server load balancing and backend processing issues.
Stage: 
Critical
Lead Customer Comments: 
Meeting held on 10/8/2009 to resolve issues. (Laura Ploughe) This item is prioritized as priority #1 (High) by Ray due to the fact that the backend processing issues are impacting our business operations and customers and need to be immediately corrected and managed properly in the future.
People
Sponsor/Champion: 
Morgan Olsen, Executive Vice President and Chief Financial Officer
Project Manager: 
Sharan Johnson
Contact for more information: 
sharan.johnson@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Debi Carl
More Info
Source: 
Internal
Priority: 
Medium
Scope: 
  • Upgrade the current version of Pharos in the Enterprise system to version 8.0
  • Incorportate the desktop release functionality into the Enterprise Pharos system
  • Merge the UTO lab/classroom system with the Enterprise system
  • Configure the Pharos Enterprise system to the SQL DB standards in the data center

 

All Milestones and Schedule: 
  1. Project Kick-Off meeting -- Completed
  2. Meet with vendor -- Completed
  3. Conference call with Vendor - Completed
  4. Re-assess plan for upgrade to 8.0  --  Completed
  5. Determine project tasks and implementation schedule -- Completed
  6. Meeting with MSS - To discuss needs for hardware configuration -- Completed.
  7. Complete architectural design (As-Is) -- Completed
  8. Complete architectural design (To-Be) -- Completed
  9. Present design to the ARB (Architectual Review Board) -- Completed.
  10. Development of Implementation Schedule -- Completed
  11. Build production environment -- Completed
  12. Migration of 1st print queue to new system -- Completed
  13. User Documentation -- Milestone to be met by June 29, 2009.  (Erich van Safford) -- Pending confirmation
  14. Technical Documentation -- Milestone to be met by June 29, 2009.  (Erich van Safford) -- Pending confirmation
  15. Operations Plan -- Milestone to be met by June 29, 2009.  (David Bui) -- Pending confirmation
  16. Help Center Training -- Milestone to be met by July 31, 2009  (David Bui) -- Pending confirmation
  17. Implementation Across Campus -  Competed.
  18. Completion of all printer queue migrations -- Completed.
  19. Post Implementation Review meeting -- To be rescheduled after post implementation issues are resolved.
    • Desktop release for printing -- Completed
    • Data issues -- Sun Card Data
      • Preliminary plan to address data issues --September 30, 2009
Deliverables: 
  • Upgraded Pharos enterprise print asset system. 
  • Consolidation of Common Computing Pharos and the Enterprise Pharos into one environment.
  • Ability to provide desktop released print jobs to other labs/classrooms and end user systems.
Risk & Threats: 
  • Any new (as yet unknown) hardware/software requirements with the new version.
  • Issues related to the migration of the existing UTO lab/classroom data into the enterprise.

 

Syndicate content