Skip to content
English
  • There are no suggestions because the search field is empty.

Analyze project status with PROEVER AI

Serving as a strategic partner for PMs and PMOs, PROEVER AI combines quantitative metrics with qualitative insights to provide reports that empower rapid decision-making.

This feature is available as a widget that can be added to your Dashboard or Project Reports.

While you can review your analysis history on the PROEVER AI screen, the analysis itself must be initiated from the Dashboard or Project Report screens.

  1. Open the Dashboard template editor or the Project Report creation screen.
  2. Select [AI Ticket Analysis] from Custom Graphs.
  3. Configure the analysis settings:

    1. Item Name: Enter the name for the analysis area as it will appear on the report.

    2. Template: Specify the ticket category to be analyzed.

    3. Ticket Filter: Set the status of the tickets you wish to include in the analysis.

    4. Language Settings: Select the output language.

    5. Maximum Items to retrieve at once: Set the maximum number of tickets to analyze (up to 200).

  4. Click [Save].
  5. Click [Detailed Analysis] to start the AI analysis and generate results. 
    Note: You must save the template once before the [Detailed Analysis] button becomes available.

 

The results are generated in the following format:

Section Overview
1.Exective Summary
  • Key Metrics: Presents "Basic Metrics" (e.g., total count, completed count) and "Progress Metrics" (e.g., overall progress rate, delayed rate) in a table format to visualize quantitative status. 
  • Status Overview: Provides a summary of the project's health based on the metrics—incorporating perspectives such as EVM, SQC, and TOC analysis—along with the current severity level.
2.Key Achivements and Positive Signs Beyond identifying issues, the AI highlights positive elements, such as areas progressing according to plan or emerging signs of improvement.
3.Analysis and Root Cause Hypothesis The AI delves into the underlying factors behind issues like delays or stagnation, providing logical hypotheses to explain why these situations occurred.
4.Strategic Recommendations and Trade-offs The AI suggests three specific action plans to overcome the current situation. Each proposal clearly outlines the "Action," "Expected Outcome," and "Trade-off (Potential Side Effects)."
5.Supplementary Notes

This section outlines data constraints (such as missing or incomplete fields) and specific disclaimers regarding AI analysis—emphasizing that all final decisions must be made by a human user.

 

If the number of target tickets exceeds the set limit, the system will prioritize "critical tickets closest to the current date," based on the following logic.

フィルター設定 Target Data Definition Priority(Sort Order) Notes(Behabair when date is not set)
Completed Status is “Completed” Sorted by Due date closest to today  If missing, use Created Date
Completion on schedule Due date is on or before today  No substitution (date required) 
Completion delayed Due date is on or before today and Status is not “Completed”
Not started  Status is “Not Started” If missing, use Created Date
In progress Status is any value other than “Completed” 
Start on schedule Start Date is on or before today
Started Start Date is on or before today and Status is not “Not Started”  Sorted by Start Date closest to today
Start delayed Start Date is on or before today and Status is “Not Started”