<objective> Create a front-end prototype for a root cause analysis system tailored to the Houston Metro, accommodating the variety of observed operational scenarios and reflecting the reality of a regulated and requirement-heavy American transportation sector. </objective> <role> Act as a root cause analysis expert with deep knowledge of the U.S. rail and transit industry, as well as experience in software development. </role>
<target_user>
The target audience for this prototype includes engineers, technicians, operators, managers, planners, and field supervisors working in the operation of buses, light rail systems, and paratransit services for people with disabilities.
</target_user>

<main_content>
The prototype must include the following sections or components:

General Dashboard

Executive overview with key KPIs: number of open/closed/critical RCA cases, occurrence heatmap by location, recurrence rate.

Login and Investigation Selection

Initial screen (Investigation Editor): After login, users view a list of investigations/audits. They can create a new one by filling in required fields (title, date, location, classification).

Case selection: Opening a case brings up an overview with current status and access to each process step.

Case Overview (Dashboard / 7-Step Process Flow)

Displays the 7-step RCA workflow, where each step groups a set of tools: SnapCharT, Root Cause Tree, Corrective Actions, Reports, etc.

Shows which steps are complete or pending and serves as the central hub for progress and navigation.

SnapCharT – Interactive Timeline

Accessed by clicking within the process flow.

Users drag and connect elements (events, conditions) logically, from left to right, top to bottom.

Upon saving a version (e.g., "Autumn version"), causal factors are identified, automatically linking to corresponding Root Cause Trees.

SnapCharT allows marking safeguards (barriers), highlighting failures, and defining focal points for analysis.

Safeguard Analysis (integrated with Root Cause Tree)

After identifying a causal factor in SnapCharT, users conduct safeguard analysis.

The system shows failed or missing barriers in the diagram, which trigger the Root Cause Tree analysis.

This step serves as input to the root cause identification.

Root Cause Tree + Dictionary

Each causal factor opens a decision tree with guiding questions.

Users mark or unmark branches intuitively.

Right-clicking a node opens the dictionary with detailed definitions.

Notes or report descriptions can be added per node.

The tree promotes logical reasoning and avoids vague conclusions like “human error.”

Equifactor – Equipment Failure Analysis

Specialized in technical failure investigations using predefined or custom tables (FMEA/PSM).

Based on the Heinz Bloch Troubleshooting Method.

Teams can import or create custom troubleshooting tables.

Within Equifactor, users enter failure parameters (e.g., wear, lubrication, configuration), generating likely physical causes.

Outputs are linked back into the Root Cause Tree for further analysis.

Event Logging & Corrective Action Helper

Once root causes are defined, the Corrective Action Helper supports action planning.

Users assign actions to each cause, aided by best-practice suggestions.

Each action has three structured phases:

Implementation – responsible party, department, deadline

Verification – short-term check

Validation – long-term review of effectiveness

SMARTER criteria support action design (Specific, Measurable, Accountable, Reasonable, Timely, Effective, Reviewed).

Files (photos, docs) can be attached, with timestamps and responsible users recorded.

Reports, Export, and Knowledge Base

The final process step auto-generates comprehensive reports: SnapCharT, causes, actions, statuses, metrics.

Reports are viewable, exportable (PDF, Word, Excel), and integrable via API with ERPs, EHS, or BI tools.

A built-in lessons-learned database allows case comparisons, filtering by type, date, and severity for organizational insights.

AI Assistant

AI-generated summaries per RCA, displaying case status, risks, pending items, user interaction logs, suggested actions, and connections to institutional learning.

</main_content>

<expected_features>
Include the following visual or interactive features:

Hierarchical sidebar menu with categories: Dashboard, SnapCharT, Equifactor, Events/Actions, Reports, Settings

Visual indicator of active case (code, title, status) visible in the menu

Progress tracker displaying completed RCA steps

Contextual filters (e.g., by case type, date, responsible person)

Audit controls: change log, timestamps, responsible user records

Integrated attachments: upload of photos, documents, videos

Role-based access control: Investigator, Reviewer, Manager

Export and API integration: PDF reports, BI dashboards, third-party systems

Knowledge base for cross-case learning and failure pattern recognition

Scroll-free layout for components like SnapCharT; optimized for full HD displays
</expected_features>

<visual_style>
The visual style should be:

Modern, corporate, and responsive

Color palette:

Deep Purple #7C47CB (primary highlights: headers, buttons)

Medium Purple #A675E2 (hover states, icons, interactive charts)

Vivid Green #8BC53F (positive indicators, confirmation tags)

Pure White #FFFFFF (main background for lightness and contrast)

Light Gray #F4F4F4 (secondary backgrounds, card containers)

Dark Gray #2A2A2A (main text for readability)

Status Colors:

Green (Completed), Yellow (Incomplete), Red (Critical Status)

Typography:

Montserrat for titles

Open Sans for body text

Clear layout with strong visual hierarchy and generous spacing
</visual_style>

<responsive_behavior>
The system must perform well on:

Desktop (minimum 1280px) – primary usage scenario

Tablet – for fieldwork and meetings

Mobile – for quick follow-ups, reviews, and updates
</responsive_behavior>

<optional_inspiration>
Inspiration sources:

Material Design (Google)

Power BI and Grafana dashboards

Platforms like Notion, Monday.com, and Figma
</optional_inspiration>

<additional_notes>

Avoid visual clutter; prioritize clarity and traceability

Highlight critical KPIs and alerts

Use icons only when functionally meaningful (e.g., status, attachments, comments)
</additional_notes>

<deliverable> Generate the HTML/CSS/JS code or rapid prototyping structure for the interface based on this scope. </deliverable>