20241022-IDEAS Access DB - details gathering session

Meeting Summary: Database Management and Integration

Key Goals of the Discussion

  • Understanding the data structure related to the ideas database.

  • Explanation of two main data types: Part Tracker Data and Action Tracker Data.

  • Discuss the process of onboarding new products and parts into the system.

Key Data Types and Tables

1. Part Tracker Data

  • Contains lists of parts approved for products.

  • Includes two main tables:

    • Service Parts Table: Lists parts eligible for field repairs.

    • Part to Problem Table: Connects parts to issues they can resolve.

2. Action Tracker Data

  • Manages information on actions taken regarding parts and problems.

Data Management Process

  • **Data Onboarding: **

    • New products get introduced with illustrative parts breakdown from engineering teams.

    • Evaluation by service engineers to decide which parts are hardware or non-hardware categories.

  • Entry Code:

    • Definition: A unique identifier for each product.

    • Example: Breakdown by digits indicating product and subcategories.

Functionality of Key Columns

  • Entry Code: Unique identifier for the specific product line.

  • PMCL Column: Specifies approval for specific systems or applications.

  • Part Number & Description: Essential for identifying parts used for repairs and linking them to problems.

Hardware vs. Non-Hardware Parts

  • Non-hardware parts are tracked for problem resolution; hardware parts do not require issue tracking.

  • Hardware components defined as items that can fix multiple issues (e.g., screws, bolts).

Tables Overview

Important Tables Discussed:

  • Problem Description Table: Contains master list of all possible problems.

  • Problems Available by Entry Code: Tags problems specific to products, used to filter down potential issues that can be resolved.

  • Oracle Items Table: Validates whether parts and problems already exist in Siebel.

  • ** Siebel Combinations Table:** Acts as an audit trail for parts added to the system.

Execution of Parts Approval Process

  1. Service engineers provide lists of parts and problems for a new product.

  2. Validate parts against previous entries and Oracle items.

  3. Generate service files once data is approved for inclusion.

  4. Output to Siebel for access by technicians.

Mechanism of Data Validation

  • Validation checks against the Oracle table and master lists ensure that no invalid entries are made.

  • The system is designed to prevent duplicates and maintain data integrity.

Next Steps and Future Improvements

  • Proposals for improved data extraction and tracking.

  • Sharing of additional reference documents to facilitate better understanding.

  • Exploration of creating a test user for Siebel to check data entries and relations.

  • Providing updates to existing documentation regarding how to navigate the current systems.

Closing Points

  • Emphasis on the need for clarity in the data structure and functioning for successful management moving forward.

  • Need for complete data dumps and possible access setup discussion.