This page will provide status updates on the Modern UI for Device Database Unification Project. 

The Modern UI for Device Database Unification project is a forward-looking initiative aimed at modernizing our legacy systems, specifically CATER and DEPOT. These outdated technologies are plagued by manual processes, redundancy, and inadequate integration. This project seeks to optimize our existing tools and workflows, ultimately enhancing user experience and minimizing duplicate data entry.

Project Initiation and Team

In late October 2023, Tiffany Tran and Claudio Bisegni were onboarded onto a team to launch this project, with Mike Zelazny serving as the project manager. Tiffany is responsible for frontend development using React.js, while Claudio focuses on backend development with MongoDB and Kubernetes. Together, they have been diligently working to establish a unified web application, or "portal," which will serve as a single point of access for users, integrating legacy systems such as CATER, DEPOT, and eLogs.

Timeline

  • October 2023 - April 2024: Completion of the proof of concept prototype.
  • May 2024: Deployment of the staging environment.
  • June 2024: Continued user research to gather feedback and make necessary adjustments. *Focus on CATER*


The Evolution of the Current CATER System

The current CATER system, originally designed for a specific problem-reporting purpose, has undergone significant changes over the years. As the needs of the organization evolved, new functionalities and fields were continuously added to the system. This gradual transformation has led to the system being used in ways that were not originally intended, such as task tracking and job planning. The original design has been modified to the point where it no longer efficiently serves its primary purpose, and the additional functionalities have created a cluttered and confusing user experience. 

The Need for a New Solution

Given the current state of the CATER system, it has become clear that a new solution is necessary. The primary reasons for creating a new system include:

  1. Streamlined Functionality: A new system can be designed with clear and focused functionalities, ensuring that it serves its intended purpose without unnecessary complexity. 
  2. Improved User Experience: By eliminating the clutter and confusion of the old system, the new system can offer a more intuitive and user-friendly interface, making it easier for users to track problems efficiently.
  3. Enhanced Efficiency: A purpose-built system can streamline workflows, reduce redundancy, and improve overall productivity by providing the right tools for the right tasks.
  4. Scalability and Flexibility: The new system can be designed with scalability in mind, allowing for future growth and the addition of new features without compromising its core functionality.
  5. Better Integration: Modern systems can offer improved integration with other tools and platforms, facilitating better data flow and communication across different parts of the organization.

Instead of forcing a single workflow to accommodate all the new functionalities and user needs, we have incorporated new workflows to adapt to each use case:

CATER Workflow

New Workflows

New Features

  • Progress Bar: show a visual status of the work ticket
  • Activity Log: log the actions done on that ticket
  • Threaded Comments: allow users to communicate and interact with one another
  • Work System Centralization: generalize the new system enough to include LCLS's and MFD's work systems

Proposed Changes

  • Maintenance and 8:15 meetings will be separated from the work management system.
  • Jobs can be standalone and doesn't require a CATER to be created first.
  • Software jobs needs to be able to add Safety Forms such as RSWCF 
  • Jobs will have 3 states (Active, Complete, Drop) and Rolled will become an action
  • Section to add persons associated with a job
  • Document who closes the cater
  • Improved reports feature that allows upper management to better analyze data

Current Stakeholders Involved

  • AOSD
  • EED
  • LCLS

Future Direction and Stakeholder Involvement

As the project progresses, the focus will remain on enhancing the application's functionalities and integrating feedback from users. Stakeholder involvement is crucial to ensure the development of a tool that meets the needs and expectations of its users.

Call for Proactiveness and Feedback

We invite all stakeholders to actively participate in the development process. Your feedback and suggestions are invaluable in shaping an application that not only improves functionality but also enhances the overall user experience. Please feel free to reach out with any insights or suggestions you may have as we continue to develop this important project.

  • No labels