1. Background of Data Analysis

1-3. When to Conduct Data Analysis

Difference in Progress Processes Between "Business Negotiations" and "Customers"

A logistics center construction project proceeds as two distinct timelines run in parallel: the receiving side (business negotiation) and the ordering side (customer).

• Progress of Business Negotiations (Left Axis):
  This is the internal process of the receiving side (manufacturers or system vendors). It proceeds as a relay race with role division between "Sales Initiative" and "Engineering Initiative." Sales organizes inquiries and requests, while Engineering conducts data analysis (current status analysis & future prediction) to solidify preconditions and propose multiple options. Afterwards, through adjustments, Sales again compiles the final estimate and secures the order.
• Progress of Customers (Top Axis):
  This is the decision-making process of the ordering side. Starting from the "Initial Inquiry," it moves through "Current Status Understanding," "System Proposal," "System Reconstruction," "Final Estimate," and "Order Placement." Importantly, between each phase exist gates such as "Precondition Confirmation," "System Exploration," "Unified Specification Sheet," and "Internal Approval," creating a structure where the project cannot proceed to the next stage unless these gates are cleared.

How Project Operation (Progress Content) Intertwines

Connecting the above two axes (negotiations and customers) at an operational level is the "Progress Content (Project Operation)" drawn in the lower right of the diagram. The core anchor here is data analysis.

• Taking the data analysis (inbound/outbound characteristics and future predictions) performed by Engineering as a core, it multiplies commodity characteristics to derive "shipping characteristic predictions for the new center."
• Against these derived characteristics, realistic elements such as "location/site constraints," "investment budget," and "internal/external factors (utilization of 3PL/4PL, etc.)" are confronted, aligning the optimal system and building specifications.

【Supplementary Explanation】Operational Process Premised on Rework (Loops)

At the bottom of the diagram, it states: "DATA must be reviewed every time the proposal content changes."

In actual project operations, initial proposals rarely pass as-is. Projects invariably hit walls, such as "system reconstructions" due to customer budget overruns or pushbacks during internal approval processes. At such times, instead of simply removing equipment to offer discounts, one must return to "Data Analysis (Preconditions)."

Questions like "If we change this condition, will we be able to handle future peak shipments?" are posed, redefining requirements based on DATA as evidence, and repeating loops (agile-like alignments) to readjust information systems and operational methods. Only when these three wheels (negotiation, customer, and actual data) mesh together is an unwavering "Unified Specification Sheet" completed.