TECHS 全体像 (ビジュアル中心)
個別受注生産業向け生産管理システム「TECHS-S v6.05」（株式会社テクノア）の中身を、ビジュアル中心で解説します。 注：Mermaid図は日本語、ASCIIアートはレイアウト整合のため英語で記載しています。
+-------------------------------------------------------------------------+
| TECHS-S = "Customer Order"-driven Manufacturing Operations Platform |
+-------------------------------------------------------------------------+
| |
| INDUSTRIES : Machinery / Electronics / Parts processing |
| COVERAGE : Quote -> Order -> BOM -> Procure -> Make -> Ship |
| -> Bill -> Receive -> Cost -> Journal |
| SCALE : 509 screens / 225 reports / ~110 entities |
| CADENCE : Closes monthly (AR / AP / Cost / GL hand-off) |
| VINTAGE : v6.05 (2020) - .NET WinForms + SOAP + SQL Server |
| |
+-------------------------------------------------------------------------+
一言で言うと：受注（製番）を起点に、部品表展開・調達・製造・出荷・売上・請求・原価集計・仕訳出力までを一気通貫で管理するシステムです。
CUSTOMER SUPPLIER
| ^
| order | PO
v |
+-------------+ BOM expand +------------+ +--------+
| Sales Order | ----------------> | Production | -- alloc ---> | Buying |
| (Juchu) | | Lot=Seiban | | (PO) |
+-------------+ +------------+ +--------+
| | ^ |
| v | v
| +--------------+ +------------+
| | Work Orders | <- supply -- | Receipt & |
| | + Daily Rep. | | Inspection |
| +--------------+ +------------+
| | |
| v |
| +-----------------+ |
| | Finished Goods | <-----------------+
| | Inventory |
| +-----------------+
| |
| ship |
+--------------------------+ |
v v
+---------------------+
| Shipment & Sale |
+---------------------+
|
+---------+ bill | pay +----------+
| CASH | <----------- | ---------> | CASH |
+---------+ v +----------+
+---------------+
| Accounting |
| AR / AP / GL |
+---------------+
ポイント：受注を起点にして、(a) 製造を発注すべきか、(b) 部品を仕入れるべきか、(c) いつ出荷するか、をシステムが**製番(Seiban)**という単位で繋ぎます。
所要時間の目安：受注 → 製造 → 出荷で数週〜数か月、出荷 → 売上 → 入金 → 仕訳で 1〜2 か月。
+------------------------------------------------------------------------+
| [LAYER 1] USER WORKSTATION (Windows) |
| +-------------+ +---------------------------+ +-----------------+ |
| | Menu.exe | | UI DLLs x563 | | Local helpers | |
| | (MDI host) |--| (one per business screen) | | (Login, Set, | |
| +-------------+ +---------------------------+ | License chk) | |
| | | +-----------------+ |
+---------|-----------------------|--------------------------------------+
| SOAP / HTTP |
v v
+------------------------------------------------------------------------+
| [LAYER 2] APPLICATION SERVER (IIS + ASMX) |
| |
| /TechsService6/ |
| TSS000001100.asmx (common SI) |
| TSS000002100.asmx (menu SI) |
| TSS<NNN>NNN100.asmx x N (per-screen SI) |
| |
| each SI -> CM -> BE -> DA (4-layer per-module) |
| (Server-side common libraries: |
| lock framework, audit, code generators) |
+------------------------------------------------------------------------+
| ADO.NET | HTTP
v v
+--------------------------------+ +-------------------------+
| [LAYER 3] SQL Server | | SSRS Reporting |
| +---------+ +-------------+ | | /TechsReports |
| | TECHS6 | | EUCTOOL | | | 225 RDLC reports |
| | (Mst / | | (ad-hoc EUC)| | | via Viw* / Udf* |
| | Trn / | | | | +-------------------------+
| | Wrk / | +-------------+ |
| | Sys) | |
| +---------+ |
+--------------------------------+
External integrations:
+ Seiryu (scheduling Gantt) + BtoB EDI platform
+ Plasurm (planning tool, OEM) + Outlook / Thunderbird
+ Excel templates (quote, label) + POP shop-floor terminals
+------------------------------+
| 12 Master Data |
| (35 entities, 178 screens) |
+------------------------------+
| references
v
+-----------------+ +-----------+ +----------------+ +-----------------+
| 02 Sales | | 03 Sched. | | 04 BOM/Process | | 05 Procurement |
| O2C 69 scr | | 10 scr | | 13 scr | | 93 scr |
+-----------------+ +-----------+ +----------------+ +-----------------+
|
v
+-----------------+ +-----------+ +----------------+ +-----------------+
| 07 Operations | | 08 Invent.| | 09 Costing | | 06 Payable |
| 31 scr | | 45 scr | | 28 scr | | 16 scr |
+-----------------+ +-----------+ +----------------+ +-----------------+
|
v
+-----------+ +------------+
| 10 Journal| | 11 Budget |
| 4 scr | | 7 scr |
+-----------+ +------------+
Cross-cutting: Auth | Lock | Audit | i18n(JA) | Mail | BtoB | EUC | SSRS
エンティティ全体像（小さいダイヤ＋大きい群の地図）：
+-------------------------- MASTER DATA (Mst*) ---------------------------+
| Party Item / Drawing Process / Routing Org / Person |
| Deal ItemNo+Rev Process+Ope Person |
| Customer PictureNo ProcessCompose Sec / Dept |
| Supplier PartsCompose ProcessPtrn Base |
| Claim Maker / Quality WorkSystemCompose House (倉庫) |
| Pay ItemNoGroup Machine Subject (科目)|
+-------------------------------------------------------------------------+
| references
v
+-------------------- TRANSACTIONAL (Trn*) -----------------------------+
| Order -> Seiban -> Bom / Ps -> OpeInd / Day / Allocate / Accept |
| \ / |
| `--- Ship --> Sale --> Tar --> Claim --> ReceiptIn -------' |
| `--- Tap (AP) <-- Pay <-- Receipt(検収) <----------------+ |
| | |
| Cost / Journal <----------------+ |
+------------------------------------------------------------------------+
| snapshots / staging
v
+-------- WORK (Wrk*) -------+--- HISTORY (His*) ---+--- AUDIT (Sys*) ---+
| WrkLock, WrkInvCount, ... | HisTar, HisTap, ... | SysUpdRec ... |
+----------------------------+----------------------+--------------------+
Seiban = "1 customer-line -> 1 manufacturing job lot"
^ ^
| |
ORDER COST
| |
+--- BOM snapshot (parts at order time) -----+ |
+--- Process snapshot (routing at order) ----+ |
+--- Allocations (stock + PO) ---------------+ |
+--- Work orders (per process step) --------+ |
+--- Daily reports (qty + labor hrs) -------+ |
+--- Receipts of purchased / outsourced ----+ |
+--- Shipments / Sales ---------------------+ |
+-----------------------------------------------------+
製番がなぜ重要か：個別受注生産では、同じ品番でも、受注ごとに仕様・納期・原価が違います。製番でくくることで「この受注の儲けはいくらか？」を製番別原価で把握できます。
Day -3 / -2 / -1 Day 0 (cut-off) Day +1 .. +5
+---------------+ +-------------+ +-----------------+ +-------------------+
| Daily report | | Receive | | AR cut-off | | Cost cut-off |
| / shipment | | inspections | | (sales->Tar) | | (job lot lock) |
| entries | | finalised | | -> invoices print| | |
+---------------+ +-------------+ +-----------------+ +-------------------+
| |
v v
+-----------------+ +-----------------+
| AP cut-off | | Monthly cost |
| (买掛 -> Tap) | | rollup |
+-----------------+ +-----------------+
| |
v v
+-----------------+ +-----------------+
| Monthly carry | | Journal export |
| -> History | | (-> GL system) |
+-----------------+ +-----------------+
Rule: "Once closed, prior period writes are forbidden;
changes flow through red-slip (赤伝) reversal in the next period."
PRODUCT EDITION (industry vertical)
+-----------------+-------------------+
| A: Machinery | B: Electronics |
| C: Parts proc. | |
+-----------------+-------------------+
+
OPTIONAL MODULES
+----+-----------------------------+---------------------------+
| # | Name | # screens unlocked |
+----+-----------------------------+---------------------------+
| 1 | Production (basic) | 301 |
| 2 | Inventory | 52 |
| 3 | Sales | 33 |
| 4 | Quote | 8 |
| 5 | Scheduling | 2 |
| 6 | FAX | -- |
| 7 | MISUMI integration | 3 |
| 8 | BtoB Platform integration | 6 |
+----+-----------------------------+---------------------------+
示唆：オプション 1（生産基本）が中核で、それ単体で 8 割の機能を提供します。販売・在庫・見積は段階的アップセルの形。
+----+-----------------------+----------+
| M | Module | Reports |
+----+-----------------------+----------+
| 02 | Sales (O2C) | 49 |
| 03 | Progress | 4 |
| 04 | BOM / Process | 7 |
| 05 | Procurement | 45 |
| 06 | Payable | 8 |
| 07 | Operations | 10 |
| 08 | Inventory | 25 |
| 09 | Costing | 30 |
| 10 | Journal | 2 |
| 12 | Master prints | 45 |
+----+-----------------------+----------+
TOTAL 225
User A opens "受注入力" for Order #123 User B opens same Order
| |
v v
BEGIN TRAN BEGIN TRAN
SELECT WrkLock WITH(TABLOCKX,HOLDLOCK) SELECT WrkLock WITH(...)
INSERT CtmCompLock ----> WAITS on lock
|
COMMIT v
edit, edit, edit ... (User A finishes)
UPDATE TrnOrderH... |
INSERT SysUpdRec (audit) |
DELETE CtmCompLock v
COMMIT Lock released
INSERT CtmCompLock
continue ...
Result: No two users overwrite each other. Audit trail in SysUpdRec.
Conflict shown to user as message ES99120004 = "他ユーザが編集中"
[STRENGTHS] [WEAKNESSES]
+---------------------------------------+ +---------------------------------------+
| - 個別受注生産業界の "業務知識" の蓄積 | | - 技術が古い (.NET FW + WinForms) |
| - 製番中心の整合性 | | - クラウド/SaaS 化されていない |
| - 締次・赤伝など日本会計実務に適合 | | - 日本語前提 (i18n なし) |
| - 535画面/225帳票の機能網羅 | | - SOAP通信 (REST/GraphQL ではない) |
| - 排他制御フレームワークが堅牢 | | - 帳票が SSRS 依存 |
| - Seiryu/Plasurm/BtoB と統合済み | | - 拡張は予備項目に限定 |
+---------------------------------------+ +---------------------------------------+
段階的移行ステップ：
PHASE 1 : Master CRUD (35 entities) ##.... 2-4 wks
PHASE 2 : BOM + Routing ###... 2-3 wks
PHASE 3 : Order -> Seiban -> Production ####.. 3-5 wks
PHASE 4 : Allocate -> PO -> Receipt -> Inspect #####. 4-6 wks
PHASE 5 : Work order -> Daily -> Cost rollup ###### 4-5 wks
PHASE 6 : Ship -> Sale -> Bill -> Receive (O2C) ###### 4-5 wks
PHASE 7 : Closing cycles + Journal #####. 3-4 wks
PHASE 8 : Reports (225 -> rationalize to ~80) ...... ongoing
TOTAL : approx 6 - 8 months for feature parity (with 2-3 engineers)
ARTIFACT COUNT NOTES
--------------------------- -------------- ------------------------
Help PDFs 509 1 pdf per screen
UI DLLs 545 1 dll per screen
SSRS reports (RDLC) 225 queries via Viw*/Udf*
Common libraries ~80 domain libs + infra
Master entities 35+ 30+ Mst* tables
Transaction entities ~40 Trn* / Wrk* / His*
Distinct DB columns 1,557 (extracted constants)
Distinct enums (Kbn) 303 S0/S1/S2 encoded
SOAP service classes 378 x 256 distinct ops
UI form controls 20,812 txt/cmb/chk/grd/btn
Distinct Japanese labels 1,669 form captions/buttons
Error codes (ES99xxxxxx) 35 linked to MstMsg
FEATURE COVERAGE (screens per module)
--------------------------------------
12 Master ################## 178
05 Procurement ########## 93
02 Sales ####### 69
08 Inventory #### 45
07 Operations ### 31
09 Cost ### 28
06 Payable ## 16
04 BOM/Proc. # 13
03 Schedule # 10
15 Quote . 7
10 Journal . 4
+-- LEGAL / COMPLIANCE -------------------------------------------+
| - 赤伝 (red-slip reversal) は日本の税務監査要件を満たすため |
| 必須。新システムでも DELETE 禁止、Insert-only 設計を堅持。 |
| - ロケール (JST + 西暦 + yyyy/MM/dd) は新システムで i18n 化。 |
+-----------------------------------------------------------------+
+-- VENDOR / IP -------------------------------------------------+
| - TECHS は Technoa の知財。再実装は仕様の再構築であり、 |
| コードのコピーはしない。本ドキュメントは仕様の発見。 |
| - Plasurm / Seiryu / Infragistics / GrapeCity は別ライセンス。 |
+----------------------------------------------------------------+
+-- DATA / MIGRATION --------------------------------------------+
| - 旧 TECHS6 DB のデータ移行は、製番 ID / 取引先 Cd / |
| 過去仕訳の整合を保つ必要あり。 |
| - EUCTOOL (分析DB) は別システム化を検討。 |
+----------------------------------------------------------------+
+-- ORGANISATION ------------------------------------------------+
| - 製番文化、締次運用、赤伝処理は "業務担当者" の知識依存度 |
| が高い。新システムでも "製番" 概念を残す方が混乱が少ない。 |
+----------------------------------------------------------------+
+================================================================+
| |
| TECHS-S = "個別受注生産の 業務OS" |
| |
| - 受注 (Seiban) を起点に O2C / P2P / Make を一気通貫で管理 |
| - 締次/月次サイクルで会計まで自動連携 |
| - 排他制御 + 監査ログで業務の整合性を保証 |
| |
| - 535画面、225帳票、110+ エンティティ |
| - 8 オプション × 3 業種で SKU 構成 |
| |
| 再実装方針: |
| - 業務知識は再利用 (製番/締次/赤伝を踏襲) |
| - 技術スタックはクラウド/Web/REST に刷新 |
| - i18n + マルチテナント を最初から組み込む |
| |
| 工数見積: 約 6-8 ヶ月 (エンジニア 2-3 名) |
| |
+================================================================+
| Q | A |
|---|---|
| なぜ製番が中心？ | 個別受注生産では同一品番でも受注ごとに仕様が違うため、「この受注の利益」を製番単位で把握する必要がある |
| クラウド化の効果は？ | 現地サーバ運用コスト削減、複数拠点での同時利用、災害時の事業継続、UI のモダン化 |
| データ移行の難所は？ | 締次済みの過去仕訳と製番の整合、外部GLとの仕訳連携、過去のCtm*Lock/SysUpdRec 監査履歴 |
| 工数 6-8 か月の根拠は？ | 1モジュールあたり 3-5 週、8 モジュール、並行 2-3 名想定。詳細は analysis/docs/09-requirements.md 参照 |
| 業務上のリスクは？ | 赤伝/締次の運用差異が顕在化した場合の財務影響、現場の習熟期間、移行直後の二重運用 |
| ライセンス形態は？ | TECHS は業種edition + 8 オプションで販売されてきた。新システムも段階的アップセルが可能 |
| 競合との差別化は？ | (1) クラウド／SaaS化、(2) i18n対応、(3) 拡張API/Webhook、(4) モダンUI、(5) BIネイティブ統合 |
仕様の詳細は同フォルダの以下を参照：
| Doc | 内容 |
|---|---|
00-architecture.md | 3階層構成・ログイン・排他制御 |
01-features-catalog.md | 509画面の機能一覧 |
02-user-stories.md | 200+ ユーザーストーリー |
03-use-cases.md | 20の主要ユースケース |
04-erd.md | データモデル (Mermaid ERD) |
05-sequence-diagrams.md | 14業務フローの時系列図 |
09-requirements.md | 機能・非機能要件80+ |
13-license-sku-map.md | SKU/オプション構成 |
COMPLETENESS.md | 抽出網羅性監査 |