Product Map Overview

What is Product Map?

Product Map documents every manufactured product and how it runs in your factories, including where it’s built, the route it follows, and attributes that drive operations and KPIs. Think of it as the system of record for products, their routes, steps, and sub-steps, with the metadata needed to power real-time workflows and analytics.

Why we have it

• Create a single source of truth for product definitions across sites, lines, and processes
• Provide the context React and KPIs need for accurate takt, headcount, panel factors, and yield calculations
• Enable bulk onboarding, validation, and updates to product attributes so teams move faster with less friction

What it does

• Product inventory and structure
  • Define products, revisions, and how they run: routes → steps → sub-steps
  • Attach operational attributes by level, for example: unit cycle time, boards per panel, headcount, yield expectations, buildable flags
• Data sourcing and editing
  • Self-serve CSV import/export for bulk creation and updates using standard templates
  • APIs are available for auto-uploading and editing Products
• Operational enablement
  • Feeds React jobs with product and route context and provides panel and target logic
  • Powers KPI Sets with product-based KPIs and filters
  • Standardizes product semantics across sites for reporting and AI guidance

How Product Map ties to everything else

• Factory Map
  • Factory Map defines the physical structure: sites, areas, lines, machines
  • Product Map ties products and routes to those lines and stations so we know “what runs where and how”
• React
  • Uses Product Map for job context, item identification, target cycle time, and panels per board
  • The unit cycle time from Product Map's step attribute is multiplied by the boards per panel from Product Map's step attribute to get the target cycle time for React. 
  • Inherits defaults for target cycle time and headcount when product-level values are absent
• KPI Sets
  • Enables product-based KPIs and filters for UPH, yield, attrition, etc.
  • Standardization across instances improves consistency and comparability
• Action Manager
  • Product context drives better triggers and playbooks, including product-level yield and attrition modules and product-grouped views

Key capabilities

• Product, route, step, sub-step modeling with attributes
• All attributes available in bulk view: part number, cycle time, boards per panel, headcount, yield, buildable, descriptions
• Validated CSV import with clear error logs and notifications
• Bulk view with column-level filtering and sorting for faster validation

Data inputs and governance

• Sources
  • Standard CSV import template with required and optional columns
  • Optional integrations to MES/enterprise systems for product, routes, and attributes (for example FlexFlow)
  • Controlled web UI edits by the Routing Administrator role
• Validation and quality
  • Pre-checks for required columns and allowed values
  • Row-level error reporting without blocking the full import
  • Error CSVs for quick fixes and re-upload
• Roles
  • Routing Administrator manages Product Map edits
  • Product and Operations teams contribute source data and validate outputs

Glossary

• Product: Manufactured item, typically identified by part number and revision
• Route: The ordered path a product follows through the factory
• Step: Maps to one or multiple lines on the factory floor.
• Sub-step: Process stages that map to one or more machines within the lines mapped in Steps.
• Attributes: Operational fields used by React and KPIs, for example unit cycle time, boards per panel, headcount. They can be on the Step or Substep level.