Signals Disposition Tool

Active Product Owner: Nathalie Campos Valverde
Priority Team Group VP Value Effort Notes
None Quality North American Manufacturing Global Quality Systems None None None
Key Requirements: (Non-device software)
 
  • Must be a validated software solution suitable for CBR review.
  • Connect to MES UDP tables to extract data related to NCs and Scrap.
  • It needs to follow a defined logic (use SQL code) to extract the required data that fulfills the status of “signal”
  • Monthly data refresh with storage in a secondary database to maintain historical records and dispositions.
    • Include logic for data retention policies and potential archival migration.
  • Historic and search review functionality.
  • Ability to filter and review Disposition IDs (open/closed) based on:
    • MES entity used to calculate signaling (may be different based on different sites, but can include product, Product Family, Workflow, or Scrap code)
    • Product Group/Family
    • Disposition ID creation/closure date
    • Submitter identity
  • Provide an API for external reporting tools (e.g., Power BI, Tableau, Excel).
  • Possibility to escalate to multiple sites (starting by North American region, but potentially a global solution)
    Proposed Features
  • Disposition module:
  • Visualization module: Idea here is leveraging a similar system as the GCIBs Search idea, but for Dispositions IDs and the input info of the signal
  • User Module: Idea here is leveraging a similar system as the GCIBs My Profile, but instead of having a Default Board, it will be a Default Grouping
  • Group Module: Idea here is leveraging a similar system as the GCIBs Boards, but instead of adding People to them, the Group Admin will be responsible for listing the MES entity used to calculate signaling, which can be imported by a monthly refresh that gets data from Snowflake, and creates new rows for them that are not currently in the system
  • Organization module: Idea here is leveraging a similar system as the GCIBs Organization, but to create a list of available BU/PUs and Value Streams for required sites (to start all NAMQ sites, potentially a global solution)

Kickoff

01 Jan 2030 to TBD

Design

01 Jan 2030 to TBD

Build

01 Jan 2030 to TBD

Iterate

01 Jan 2030 to TBD

Projected Go Live Date

1 month, 1 week
Sept. 16, 2025

Issues

# Issue Days Passed Status

Upcoming Milestones

Planned Date Phase Task Deadline Status

Comments

All Milestones

Phase Milestone Status Planned Date Actual Date
kickoff Kick-off Meeting - TBD TBD
kickoff User Requirements Document - TBD TBD
kickoff Infrastructure Set Up - TBD TBD
kickoff Process Map - TBD TBD
design User Flows - TBD TBD
design User Stories - TBD TBD
design Feature List - TBD TBD
design Sprint Plan - TBD TBD
design Tests Written (with Success Criteria) - TBD TBD
design Wireframe Review 1 - TBD TBD
design Wireframes Approved - TBD TBD
build Build Sprint 1 - TBD TBD
build Build Sprint 1 Complete - TBD TBD
build Test Link Delivered - TBD TBD
iterate Customer Feedback Review 1 - TBD TBD
iterate Iterate Sprint 1 - TBD TBD
iterate Iterate Sprint 1 Complete - TBD TBD
iterate UAT - TBD TBD
iterate Build Approved (Final Sign-Off) - TBD TBD
sustain Production Link Delivered - TBD TBD
sustain Go-Live - TBD TBD
sustain 1 Month Follow Up - TBD TBD
sustain 3 Month Follow Up - TBD TBD
sustain 6 Month Follow Up - TBD TBD
sustain Sustain Sprint 1 - TBD TBD
sustain Sustain Sprint 1 Complete - TBD TBD