An AI Model Training, Prediction, and Database Construction System Utilizing Machine Learning and SDCA Regression
This system is a Windows Forms application that constructs refined AI prediction models (AI models) from shipping data by combining EIQ analysis (Entry-Item-Quantity analysis) methods with advanced machine learning.
Taking the number of delivery destinations (E) and number of items (I) as inputs, it predicts approximately 160 items—including loose quantities, line counts, EIQ metrics, case counts, pallet counts, volume, and weight—using the SDCA regression (Microsoft.ML) machine learning algorithm.
| File | Class / Module | Role |
|---|---|---|
E0_メニュー画面.vb |
E0_MenuScreenF | Main menu. Navigation to processing screens and checking database status |
E1_データ前処理.vb |
EIQ_AIModelPreprocessingF | Import shipping data, classification conversion, create EIQ rankings, build T200 table |
E2_モデルデータ設定.vb |
ModelDataSettingsF | E/I ratio & pitch settings, manage T300_Progress table, navigate to E3 screen |
E3_モデルデータ作成.vb |
E3_ModelDataCreationF | Build T600_DataModel based on T300_Progress (batch processing) |
E4_機械学習.vb |
E4_MachineLearningF | Train AI models, execute predictions, and export using Microsoft.ML (SDCA regression) |
EIQ_AI実証及び検証Pro.vb |
EIQ_AIVerificationAndValidationPro | Verification and validation of AI prediction models (for future expansion) |
K1.vb |
Module K1 | Manage global variables, constants, and file paths |
AccessDbManager.vb |
AccessDbManager | Create new Access databases and import Excel data |
Access操作.vb |
— | SQL execution helpers and common database table processing |
テーブル構造確認.vb |
— | Database structure verification & diagnostic utility |
Because raw logistics field data often contains mixed units and errors, "automated classification conversion" standardizes shipping units (loose, case, etc.) to guarantee calculation accuracy. Additionally, automatically executing a "5-stage Pareto analysis (EIQ ranking)" enables the AI model to recognize which product groups drive center workloads as "features."
Built on VB.NET and Microsoft Access (database), this system is clearly modularized across processing phases. By adopting a design that completes entirely within the local environment (.accdb) without relying on external cloud services, it maintains strict confidentiality for sensitive shipping data while achieving high-speed batch processing in a desktop environment.
Rather than relying on a single past pattern, thousands of "virtual shipping scenarios" varying E/I ratios between 50% and 150% are generated to train the AI model.
By simulating numerical outcomes under extreme conditions—such as "What if delivery destinations increase by 1.5x?" or "What if items are halved?"—the AI prediction model gains an accurate understanding of the facility's "growth margin" and "processing limits."
E0_MenuScreenFEntry point when launching the application.
EIQ_AIModel.accdb, displays T200 table presence/type (linked or local) and record countEIQ_AIModelPreprocessingFHandles everything from shipping data import to creating the T200 table for EIQ analysis (storing into the database).
| Process | Content | Generated Tables |
|---|---|---|
| Create New Access DB | Create new EIQ_AIModel.accdb | — |
| Import to Access | Import ShippingData.xlsx into database | T000_ShippingData |
| T110 Classification Conversion | Create T100_Data, create conversion table, compute conversion calculations, shipping unit classifications | T100_Data, T110_ClassificationConversion |
| Create T200 (EIQ Data Processing) | Summarize EI for case/loose shipments, T180 EIQ rankings, integrate into T200 table | T150_*, T180_EIQRank, T200 |
| All-Shipment GPL Rankings | Create E/I rankings for all GPL shipments, add columns to T200 | T160_AllShipmentESummary, T160_AllShipmentISummary |
ModelDataSettingsFConfigures generation parameters for AI prediction model training data using machine learning.
| Parameter | Range | Description |
|---|---|---|
| E Min / Max Ratio | 50% to 150% | Range of destination count fluctuations (ratio relative to baseline) |
| I Min / Max Ratio | 50% to 150% | Range of item count fluctuations (ratio relative to baseline) |
| Record Pitch | 1 to 20 (Default: 5.9) | Interval between generated records (smaller pitch = higher data density) |
CreationChk flag per record → used in E3 to manage completed tasksE3_ModelDataCreationFSequentially processes uncompleted records in T300_Progress table and writes data into T600_DataModel in the database.
| Category | Fields | Count |
|---|---|---|
| Basic Info | Model Serial No., Destination Count, Item Count, Loose Quantity, Line Count | 5 |
| E Metrics | E1 to E5 | 5 |
| I Metrics | I1 to I5 | 5 |
| Line Count by Rank | LineCount01 to LineCount25 | 25 |
| Loose Quantity by Rank | LooseQty01 to LooseQty25 | 25 |
| Case Count by Rank | Case01 to Case25 | 25 |
| Pallet Count by Rank | PL01 to PL25 | 25 |
| Volume by Rank | Volume01 to Volume25 | 25 |
| Weight by Rank | Weight01 to Weight25 | 25 |
CreationChk flag in T300_Progress,
even if interrupted, execution can resume from uncompleted records.
Includes a keyboard interrupt feature via the GetAsyncKeyState API.
E4_MachineLearningFTrains and predicts AI prediction models via SDCA regression using Microsoft.ML.
| Function | Description |
|---|---|
| Data Import | Loads DataModel.csv via LoadFromTextFile and displays record counts |
| Execute Machine Learning | Trains an SDCA regression model for each output field, saving as .zip files in Models/ |
| Load Trained AI Models | Batch loads saved .zip models (enables predictions without retraining) |
| Execute Predictions | Input destination count & item count → Predict via all AI models → Display results in DataGridView |
| Export Results | Exports prediction output as PredictionResults.csv in UTF-8 format |
| Type | Items |
|---|---|
| Inputs (Explanatory Variables) | Destination Count, Item Count |
| Outputs (Target Variables) | Loose Qty, Line Count, E1-E5, I1-I5, Lines 01-25, Loose Qty 01-25, Cases 01-25, PL 01-25, Volume 01-25, Weight 01-25 (Total: ~160 items × 1 AI Model each) |
By simulating numerical outcomes under extreme conditions—such as "What if delivery destinations increase by 1.5x?" or "What if items are halved?"—the AI prediction model gains an accurate understanding of the facility's "growth margin" and "processing limits."
Database: TeraCalculationData\EIQAnalysisAI\EIQ_AIModel.accdb (Microsoft Access)
| Table | Created By | Purpose |
|---|---|---|
T000_ShippingData | E1 (Excel Import) | Raw shipping data source |
T100_Data | E1 | Basic shipping data (with row serial numbers) |
T110_ClassificationConversion | E1 | Conversion data based on shipping classifications |
T150_CBUnitShippingEISummary | E1 | EI summaries & ABC rankings for case/loose shipments |
T160_AllShipmentEISummary | E1 | All-shipment GPL rankings (by E/I) |
T180_EIQRank | E1 | Integrated EIQ ranking table (CE/CI/BE/BI) |
T200 | E1 | Processed EIQ analysis data (integrated ranks & metrics) |
T300_Progress | E2 | Progress management for AI model data creation (Serials, Settings, CreationChk) |
T600_DataModel | E3 | Data model for machine learning (165 fields) |
The proprietary database table progression (expanding from T200 to T600) embodies core logistics expertise. Raw historical data in T000 is transformed into structured EIQ metrics in T200, and ultimately elevated into a 165-field machine learning AI model (T600).
| Item | Requirement |
|---|---|
| Framework | .NET Framework 4.8 |
| Language | VB.NET (Windows Forms) |
| Primary Libraries | Microsoft.ML (Machine Learning with SDCA regression), ClosedXML, ADOX, Microsoft.Office.Interop.Access |
| Database | Microsoft Access (ACE OLEDB 12.0) |
| Data Storage Path | TeraCalculationData folder on any drive (Auto-scans drives A: through F:) |
| Required File | TeraCalculationData\EIQAnalysisAI\ShippingData.xlsx (when creating from shipping data) |
FileCheck() method in K1.vb scans drives A: to F: and automatically detects the
TeraCalculationData folder. An error is raised if the folder exists on multiple drives.
From the frontend UI to backend databases and machine learning AI prediction model integrations, the entire technology stack is unified under .NET Framework 4.8. This consistency minimizes library conflicts, ensures adaptability to OS updates, and delivers exceptional desktop responsiveness.
Raw Excel data evolves from "logistics data structuring" in T200 to "simulation space construction" in T600, culminating in an AI prediction model powered by machine learning. Through this sequence of database construction steps, unstructured shipment records become strategic assets supporting future facility engineering.
Traditional EIQ analysis was limited to static aggregations ("points") of historical data. In this system, by having machine learning AI models learn the fluctuations in destination counts (E) and item counts (I), EIQ analysis evolves into "AI prediction models" capable of dynamically simulating facility capacity and workload.
This system represents a next-generation simulation platform that algorithmizes 30 years of logistics consulting expertise. While conventional EIQ analysis merely aggregated past shipment results statically, this system acts as a "logistics digital twin" that dynamically forecasts capacity for new or consolidated facilities as the AI model learns fluctuations in delivery destinations (E) and item counts (I).