00 — TECHS-S System Architecture

Reverse-engineering reference. Cites paths under /home/rmondo/repos/fab-forward-techs/analysis/decomp/ (_t1_* = client, _t2_* = small fragment of server-side modules shipped on the client install). Method bodies are sometimes blanked due to ilspycmd / [OptionText] obfuscation; class names, constants and c_clm* / c_TableNm* fields are the primary signal.

Subject system: TECHS-S (Technoa Corp., Japan) — Make-To-Order discrete manufacturing PMS. Version per Techs.ini: 0605.0002.0001.0000 → product line TECHS-S 6.05 / client build 6.05.0002.0001 with DB schema baseline 0.

---

1. High-level topology (3-tier + satellites)

Key facts cross-referenced from the decomp:

The build is essentially a Citrix-style fat WinForms client that makes synchronous SOAP calls into a colocated IIS server, plus a few operations that go directly against SQL Server (login validation, SymPassword updates, lock-table scans, history housekeeping). The server tier is layered:

ASMX (SI*)  →  BE* (business entity, transactions)
            →  CM* (common runtime: locks, query builder, masters)
            →  DA* (data access — typed SqlCommand builders)

This four-letter prefix convention is consistent across the dump:

Only ~16 of these *_S assemblies are present in the dump (lock, query builder, master CRUD, shared get-data, …). The rest (per-screen business logic for 0201001, 0501001, …) live on the IIS box at %TechsService6%\bin\ and are not in the dump.

---

2. Client startup sequence

Entry point is clsMain.Main() (_t1_Technoa.Techs.Menu/Technoa.Techs.Menu/clsMain.cs:62). High level:

1. Create a named mutex (Application.ProductName) — refuses to start twice on the same machine.
2. clsMain.StartSetUp() → clsSetUp.SetUpAsync() (async worker thread):
   • BaseSheet.CreateSheet() (UI scaffolding)
   • clsAuthorize.DBConnect() — opens SqlConnection(m_clsInfo.ConnectionString) and immediately SqlConnection.ClearPool to validate.
   • clsAuthorize.SIConnect() — calls m_clsInfo.SI.SIConnect() (SOAP SIMenu.SIConnect).
   • clsAuthorize.SIDBConnect() — server-side DB-connect probe via SOAP.
   • clsAuthorize.CheckVersion() — SI.GetVersion(serverVersion, clientVersion, dbVersion); client requires Asia/Tokyo timezone, Japanese 西暦 calendar, yyyy/MM/dd date format, HH:mm:ss time format.
3. Splash → frmLogin is shown.
4. User enters PersonCd / Password → frmLogin.StartLogin() → clsLogin.LoginAsync() → LoginWorker runs in steps:

Where exactly things come from

• Connection string — clsMenuInfo.Reset() (_t1_Technoa.Techs.Menu/Technoa.Techs.Menu/clsMenuInfo.cs:476-479) copies CommonConfiguration.ConnectionString into m_cnString. CommonConfiguration is a per-install XML maintained by frmConnection.cs (the connection-edit dialog) and is referenced via CommonConfiguration.WebServiceServer / .WebServiceFolder / .SIPort.
• WebService URL — same Reset() call:

  m_SI.Url = ApplicationInfo.GetWebServiceUrl(
      m_SI.Url,
      CommonConfiguration.WebServiceServer,
      CommonConfiguration.WebServiceFolder,
      CommonConfiguration.SIPort);
  

  The original SIMenu.Url is templated from app.config (http://localhost/TechsService/TSS000002100.asmx) and only the host:port/folder part is rewritten — the asmx filename is preserved (last path segment, array[^1], ApplicationInfo.cs:1270).
• License & validity — SymSystemCtrl is decrypted with Cryptogram.DecryptString using TechSerial as key and a hard-coded salt "Technoa.Techs" (clsAuthorize.cs:24-26, 230-256). Trial vs Product is determined here: validityTerm == "none" → Product, else Trial with expiry compared against server time from SELECT GetDate().
• Password storage — SymPassword, encrypted by EncryptPassword = Cryptogram.EncryptString(personCd + password, SerialKey, personCd) (clsAuthorize.cs:1100-1104). Update path goes through SI.RegistPassword (server-side; clsAuthorize.cs:1077-1098); first registration of an empty password is recognised by InsDt == UpdDt.
• Person data + UI item / message / kbn caches — fetched via ApplicationInfo.GetPersonInfo / GetUImItemInfo / GetMessageInfo / GetKbnInfo; rows go into the MstPersonInfo / UImItem / SymMessage / SymKbn DataTables (clsAuthorize.cs:584-700). MessageInfo.SetMessage / SetKbnData / SetItemData populate the global runtime caches the rest of the client uses for label / dropdown / error-message lookup.
• Menu data — seven calls in clsAuthorize.GetMenuData() (:921-950) populate one DataSet (m_clsInfo.MenuData):
  1. GetMenuAPList — full list of authorised AP codes (the launchable screens) → drives clsApListBusiness.
  2. GetMenuMyMenuList → clsMyMenuBusiness.
  3. GetMenuStartRecList (table SysStartRec) → clsStartRecBusiness (recent-launch panel).
  4. GetMyWorkData → "MyWork" tile.
  5. GetTransitAPInfoAll → drill-through links registry (the TransitListBusiness that lets a screen launch another with parameters).
  6. GetReportInfoAll → SSRS report registry per AP.
  7. GetPersonSchedule → calendar pane.

License / lock seat enforcement

clsAuthorize.ConnectingSetting (:468-533) calls SI.ConnectingSetting(personCd, cnString, license) (or ConnectingSettingForce when app.config DuplicatedLogin=yes). Return codes:

Server-side this stamps a row keyed by the MachineName from MachineInfo.GetMachineName() (clsMenuInfo.cs:495). At graceful shutdown clsAuthorize.ConnectingRemove (:985) calls SI.ConnectingRemove(personCd); for crash recovery, ApplicationInfo.ForceEndLockAll(apInfo, personCd) is called as part of GetLoginInfo (clsAuthorize.cs:575).

---

3. Client → server call shape (per-module SI / BE / CM / DA stack)

Wire payload is a DataSet (or array of DataSets) plus an ArrayList of UIParam records (key/value/type triples). Example seen on every reference op:

SIMenu.SoapHttpClientProtocol  (Namespace = http://technoa.techs.co.jp/SI)
  ConnectingSetting(personCd, cnString, license)       -> int
  GetVersion(ref serverVer, ref clientVer, ref dbVer)  -> int
  GetConnectionInfo(APInfo, ref DataSet)               -> int
  GetLockInfo(APInfo, ref DataSet)                     -> int
  RemoveLockInfo(APInfo, connectPersonCd)              -> int
  GetPasswordList / GetPassword / RegistPassword / ClearPassword
  GetLoginInfo / GetPersonInfo / GetItemInfo / GetMessage / ...
  ReloadSendMailBox / SendMail / DeleteSendMail (mailbox panel)

Source: enumerated OperationCompleted callbacks in _t1_Technoa.Techs.Menu/Technoa.Techs.Menu.WebRef/SIMenu.cs:25-130 plus the public method list at :283-705.

SICommon.GetCommonSharedData (_t2_Technoa.Techs.SI.TSS000001100_S/Technoa.Techs.SI_S/SICommon.cs:15) is the canonical pattern for a per-module SI:

public int GetCommonSharedData(ArrayList apInfoArray, ArrayList uiParameter,
                               ref DataSet data, bool countOnly)
{
    Dictionary<object, UIHashParam> uiParamDictionary = null;
    int rc = RefillParameter.RefillUIParam(uiParameter, ref uiParamDictionary);   // CM_S
    if (rc != 0) return rc;
    BESharedGetData be = BESharedGetData.GetInstance();
    int dataCount = 0;
    return be.Reference(apInfoArray, uiParamDictionary, ref data, countOnly, ref dataCount);
}

BESharedGetData.Reference (_t2_Technoa.Techs.BE.TES000006100_S/Technoa.Techs.BE_S/BESharedGetData.cs:35-60) loops the apInfoArray, refills each entry into a strongly-typed APInfo (RefillParameter.ReFillApParam), then delegates to DASharedGetData.Reference(apParamStrt, refParameter, ref data, …). Empty result is normalised to return-code -10 so the UI can show "該当なし".

DA layer extends DABusinessBase (_t2_Technoa.Techs.CM.TCS000006100_S/Technoa.Techs.DA_S/DABusinessBase.cs:16), with virtuals each concrete DA must override:

Convention: rows have a DelFlg column (constant c_DelFlg = "DelFlg", value S0 = active — DABusinessBase.cs:22-24); soft-delete is the default.

---

4. Lock model (排他制御 / "exclusion control")

Three concrete lock kinds, all extending DACtlLock (_t2_Technoa.Techs.CM.TCS000020100_S/Technoa.Techs.DA_S/DACtlLock.cs):

All three insert their lock row using the same shape (BuildSqlBeginLock):

IF NOT EXISTS (<query that finds existing matching lock>)
BEGIN
  INSERT INTO <BTableName> (
      ApCd, PersonCd[, KeyFieldNms, KeyValues],
      UserAuthorityKbn, TerminalNm, LockKbn,
      InsUserCd, InsApCd, UpdUserCd, UpdApCd
  ) VALUES (@ApCd, @PersonCd[, @KeyFieldNms, @KeyValues],
            @UserAuthority, @MachineName, @LockType,
            @PersonCd, @ApCd, @PersonCd, @ApCd)
END

The EndLock / ForceEndLock shapes are the symmetric DELETE (DACtlLock.BuildSqlEndLock / BuildSqlForceEndLock, DACtlLock.cs:29-54). PartEndLock (CompLock only — DACtlCompLock.cs:129-145) deletes one specific key tuple.

Lock master schema for CompLock (rich case):

Cited from _t2_Technoa.Techs.CM.TCS000020100_S/Technoa.Techs.DA_S/DACtlCompLock.cs:13-200 (constants c_MasterName, c_MasterKeyName, …) plus GetMasterData (:147-181) which loads the five master tables in order to discover (a) the keys to lock on, (b) the FROM/WHERE template, (c) the LockTargetKbn for the requested operation. GetPhraseLockTarget (DACtlLock.cs:106-115) maps the runtime intent to that target column:

LockType.AddNew -> "M.lockTargetKbn='S0'"
LockType.Edit   -> "(M.lockTargetKbn='S0' OR M.lockTargetKbn='S1')"
LockType.AddUp  -> "M.lockTargetKbn='S2'"

So the "what to lock" is data-driven, sourced from the master tables. This is the single most important insight to migrate: the business layer doesn't hard-code which tables/keys to take locks on — it asks the lock master, which returns a SQL fragment ("FROM TblHd JOIN TblDt … WHERE TblHd.SeibanCd=@SeibanCd"), the lock layer pastes the fragment into the IF NOT EXISTS (…) template, and a row goes into CtlCompLock with the resolved key values.

Pessimistic table-level fallback also exists for "stop-the-world" journaling-style operations (period close): Technoa.CMN.BaseCommon.LockInfo.DBLockTreat (_t1_Technoa.TechsCommonClass/Technoa.CMN.BaseCommon/LockInfo.cs:13-53):

IF NOT EXISTS (
   SELECT * FROM VIEW_LOCK
   WHERE TableName='WrkLock' AND LockMode LIKE '%排他%')
   SELECT * FROM WrkLock WITH (TABLOCKX, HOLDLOCK)
ELSE
   SELECT * FROM WrkLockCtrl WHERE [Dmy] IS NULL

It loops with a MessageBox prompt ("他の端末でデータの登録中…再度 登録処理を行って下さい") until the table-level X lock is granted. WrkLock is a sentinel/empty table; WrkLockCtrl records waiters.

Summary of locking strategy

• Optimistic (default): row-level via SysUpdRec / SysUpdKeyRec audit (cleaned every login by clsAuthorize.DeleteUpdRec / DeleteUpdKeyRec), enforcing last-write-wins detection at update time.
• Pessimistic logical (per-screen, per-key): CtlApLock + CtlCompLock + CtlSameStartLock, configured by master tables — gives "while user A is editing Seiban 2025-001, user B sees ES99120004 (排他) and is blocked".
• Pessimistic physical (per-batch process): WrkLock / WrkLockCtrl TABLOCKX HOLDLOCK for journal-style ops.
• Crash recovery: ApplicationInfo.ForceEndLockAll(apInfo, personCd) is called on every login (clsAuthorize.cs:575) so a client that died last time clears its abandoned locks at next login.

Error code constant c_errExclusion = "ES99120004" appears in every lock DA — this is the wire-level signal for "lock conflict" surfaced to the UI.

---

5. Plug-ins / external integrations

5.1 Seiryu — production scheduler (help screen 0301011 "Seiryu連携処理")

Source: _t1_Technoa.Techs.ClientCommonLibrary/Technoa.Techs.Common/ApplicationStartingPLS.cs.

• The Seiryu scheduler is shipped as a sibling Windows app at Seiryu\Bin{V|E|S}\Pls.exe (:160, :164, :166, :190, :195), selected by plsKbn config:
  • plsKbn=0 → BinV\Pls.exe (standard / 製番大日程, Viewer)
  • plsKbn=1 → BinE\Pls.exe (Express / Engineering)
  • plsKbn=2 → BinS\Pls.exe (Setup / Simulator)
• Hand-off is via ExecProcedure calls to two stored procedures:
  • SIPls_UpdSchedule — pushes the current TECHS schedule keys (with @VchrUpUserCd, @ChrApCd) to a hand-off table (:127-131).
  • PrcAddApStartRecord — inserts a launch record (:223-231) so SysStartRec shows the Seiryu invocation.
• Then Process.Start(Pls.exe) is fired (Path.Combine(text, "Seiryu") is the install root).

The pair of help PDFs 0301011.txt (大日程 / 部品小日程連携) confirms both directions of data flow: TECHS → Seiryu (schedule push) and Seiryu → TECHS (read back computed dates).

5.2 EUC tool (ad-hoc query)

Source: ApplicationStartingEUC.cs and frmMenu.cs:2733-2740:

if (Operators.CompareString("E", Strings.Mid(info.ApCd, 1, 1), true) == 0)
    CallEucEXE(GetApInfo(info));
else if (Operators.CompareString("1201073", info.ApCd, true) == 0)
    ShowEucConnection();

So AP codes starting with E… are routed to the EUC executable (separate Euc.exe), and the system management screen 1201073 ("EUC接続情報設定") configures the connection — typically pointing at a separate EUCTOOL database for free-form SQL by power users.

5.3 Excel report controller / EUC export

ApplicationInfo.cs and BuyLinkInfo.cs reference Excel automation (grep hit, full source not in dump — likely ships in Technoa.Techs.XlController / XlControllerEUC, also referenced by the help corpus). Each report DLL drops to Excel via late-bound COM or via SSRS export.

5.4 Mail (MailBox / NewMail panes)

Sources: clsMailBox.cs, MailBoxPanelControl.cs, NewMailPanelControl.cs plus the SOAP methods ReloadSendMailBox / SendMail / DeleteSendMail / ReloadReceiveMailBox (SIMenu.cs callbacks). The client-side panel renders an in-app mailbox, while the server stores messages internally — there is also Outlook / Thunderbird launch logic (referenced from clsShedule.cs) to hand a composed mail to the local client. So "mail" is dual-mode: in-app mail (server-stored) + hand-off to OS mail client.

5.5 BtoB / EDI

_t1_Technoa.Techs.BtoBCommonLibrary is a separate assembly grouping the EDI inbound/outbound handlers. The order side has an OrderInfo.EDIFlg enum (OrderCommonLibrary/.../OrderInfo.cs:82-86) distinguishing manual vs EDI rows. Help screens prefixed 0202xxx, 0501xxx reference EDI dispatch / receive.

5.6 PlasurmStart (PS prefix)

In frmMenu.StartAp (frmMenu.cs:2741-2744):

else if (Operators.CompareString("PS", Strings.Mid(info.ApCd, 1, 2), true) == 0)
    CallPlasurmStart(info);

AP codes starting with PS are dispatched to the Plasurm (another Technoa companion product, possibly process-simulation) launcher.

5.7 SSRS reports

GetReportServerUrl(... oldReportFolder = "TechsReports", oldReportServer = "ReportServer", ...) (ApplicationInfo.cs:1287) confirms reports are an SSRS-hosted ReportServer folder named TechsReports by default. The per-AP report registry comes from GetReportInfoAll (clsAuthorize.GetMenuData, :933-934); each report row carries PrintTypeKbn so a single screen can have multiple printout layouts.

---

6. Persistence / utility patterns

6.1 Direct ADO.NET (client-side)

Used only for: login validation, password update, history cleanup (SysStartRec, SysUpdRec, SysUpdKeyRec), WrkLock/WrkLockCtrl TABLOCKX. All other reads/writes are routed through SOAP. Pattern seen in clsAuthorize.cs:258-321:

SqlConnection cn = new SqlConnection(m_clsInfo.ConnectionString);
cn.Open();
SqlCommand cmd = new SqlCommand(sb.ToString(), cn);
cmd.Parameters.Add("@PersonCd", SqlDbType.VarChar, 10);
cmd.Parameters["@PersonCd"].Value = personCd;
SqlDataReader r = cmd.ExecuteReader();

i.e. parameterised SqlCommand + StringBuilder SQL + named typed parameters (always @CamelCase).

6.2 Server-side query builder (SqlCombination / MakeSelect /

MakeInsert / MakeUpdate / MakeDelete / ExecProcedure)

In _t2_Technoa.Techs.CM.TCS000005100_S/Technoa.Techs.DA_S/SqlCombination.cs

• MakeSelect.cs (and the similar files for INSERT/UPDATE/DELETE in TCS000006100_S). These take:

• a DTableName / BTableName
• a QueryCtrlId (lookup into SymQueryCtrl / MstSql)
• a UIHashParam dict
• SettingInsertColumns / SettingUpdateColumns

…and emit dynamic SQL with positional / named parameters. Concrete DAs (MstHouseInfo, MstSupplierInfo, MstPersonInfo, MstItemNoInfo, MstCustomerInfo, CostPersonInfo) supply only the overrides above and inherit the entire CRUD machinery — strong template-method pattern.

6.3 Audit / journal (SysUpdRec / SysUpdKeyRec)

UpdRecInfo.cs (_t2_Technoa.Techs.CM.TCS000006100_S/Technoa.Techs.DA_S/UpdRecInfo.cs) is the row-history infrastructure. Every business write produces:

• one SysUpdRec row (header: UpdSeq, PersonCd, ApCd, UpdRecDt)
• N SysUpdKeyRec rows (one per affected key tuple)

Cleanup is in clsAuthorize.DeleteUpdRec / DeleteUpdKeyRec (clsAuthorize.cs:788-890): on every login, drop history older than 60 days for the current user, plus orphaned SysUpdKeyRec rows (UpdSeq no longer in SysUpdRec).

6.4 Stored-procedure helper

Technoa.Techs.DA_S.ExecProcedure (in TCS000006100_S and used by ApplicationStartingPLS.cs) wraps SqlCommand {CommandType=StoredProcedure} with named-parameter setters (SqlDataType.Char/Varchar, ParameterDirection.Input). All stored procedures use the prefix Prc… (PrcAddApStartRecord) or SI… (SIPls_UpdSchedule) — visible from the few we see.

6.5 Common runtime helpers (server)

_t1_Technoa.Techs.ServerCommonLibrary_S/Technoa.Techs.Common_S/ holds the cross-cutting helpers reused by all BE/CM:

• SystemInfo — system-config getters (incl. GetProhibitChar)
• CompanyInfo / ApCtrlInfo / PersonInfo / GpFileInfo
• ParameterSetting — UI-param refill
• MoneyCalculate, TaxCalculate — money/tax math
• ConvertUnit, ConvertRate, ConvertTime
• OperateDate — date utilities
• RefillParameter — converts wire UIParam → typed UIHashParam dict; this is the universal entry shape for every BE/SI call.

---

7. Cross-cutting reference tables (sourced via login or per-AP)

Inferred from c_TableNm* / SQL strings across the dump.

Database name: TECHS6 (per task brief; the connection string is built externally and fed via CommonConfiguration.ConnectionString). The EUC tool talks to a separate EUCTOOL DB via the connection configured by AP 1201073.

---

8. Versioning & deployment

• Techs.ini version = 0605.0002.0001.0000 → product line TECHS-S 6.05, build 0002.0001 (assembly), DB schema baseline 0000.

• Three-way version check at every startup (clsAuthorize.CheckVersion, :172-219):

  • clientVersion (assembly) must equal what the server reports → otherwise NeedDownloadError ("クライアント側のファイルの バージョンが異なります"). This is the trigger for the auto-download / sync mechanism (likely ClickOnce-style or a custom updater not in the dump).
  • dbVersion (server) must equal what SymSystemCtrl.Version contains → otherwise fatal "TECHSデータベースのバージョンが異なります".
  • Trial mode: SymSystemCtrl.ValidityTerm != "none" → expiry checked against the SQL Server's GetDate().

• Locale enforcement (also CheckVersion):

  • CultureInfo.DateTimeFormat.NativeCalendarName must start with 西暦 (Japanese Gregorian).
  • ShortDatePattern must be yyyy/MM/dd.
  • LongTimePattern must be HH:mm:ss.
  • TimeZone.StandardName must start with 東京 (i.e. JST).

Re-platforming notes: this is a hard couple to Japan / Asia-Tokyo operationally — any rewrite must consider how to relax these checks without breaking the date math elsewhere (OperateDate, MoneyCalculate, TaxCalculate all assume Japanese fiscal conventions).

---

9. Module map (top-level assemblies in dump)

Client common libraries (_t1_*)

Server fragments present in dump (_t2_*)

The bulk of business logic (per-screen DLLs Technoa.Techs.BE.TES000NNNNNN_S for every 0201001, 0501001, …) is not in the dump.

---

10. What flows over the wire (canonical UIParam shape)

UIParam[] = [
  { Key = "PersonCd",  Value = "U001",       SqlDataType = Varchar, Size = 10, ConvertType = ... },
  { Key = "SeibanCd",  Value = "2025-001",   SqlDataType = Varchar, Size = 20, ... },
  ...
]
APInfo = {
  ApCd          = "0201001",
  ApMode        = (Master|Reporting|Query|Input|Output|Tool|PickUp|Search|AddUp|Entry|EUC|Common)
  ApName, ApID, AutoRefMode, ExecLevel,
  MachineName, PersonCd,
  QueryCtrlId   = "C001"                    // selects which SymQueryCtrl row
  QueryID, TableName, UserAuthority,
  WebServer, WebFolder
}

Server side RefillParameter.RefillUIParam turns UIParam[] into Dictionary<object, UIHashParam> keyed by KeyFieldNm; the BE/DA stack uses that dict to fill @PersonCd / @SeibanCd / … parameters positionally on the generated SQL.

---

11. Open items / gaps (server-side guesswork)

• WebConfiguration.cs (_t1_Technoa.Techs.ServerCommonLibrary_S/Technoa.Techs.Common_S/WebConfiguration.cs) is here but the actual ASMX web.config is not — we only see the client's view of which URL templates exist (TSS000002100.asmx for SIMenu; numbers run sequentially per module). A live server install will list a TSS000xxxxxx.asmx per business module under TechsService\bin.
• The mapping screen-id (0201001) ↔ TSSnnnnnnn.asmx is not exhaustive in this dump. We can confirm:
  • TSS000002100.asmx ↔ SIMenu (login / menu / mail).
  • TSS000001100.asmx ↔ SICommon (shared-data refresh).
  • The other TSS000nnnn100 IDs follow the BE/CM/DA numbering (TES…, TDS…, TCS… share the trailing module number).
  • Per-screen SI numbering (one ASMX per business AP code) is inferred from the matching CM/BE numbering convention rather than observed in the dump.
• The on-disk hand-off table for Seiryu (the rows SIPls_UpdSchedule writes) is not directly enumerated here but appears in help PDF 0301011 as the 製番大日程 / 部品小日程連携 bridge.
• No source for the auto-update / patch installer (the NeedDownloadError branch in CheckVersion) is in the dump; this is presumably a separate Technoa.Techs.UserHPStartUp job (the assembly is in _t1_* but only contains version metadata in the obfuscated view).

For a fresh build, the takeaways are:

1. Treat the lock model as a first-class data-driven feature, not an afterthought — CtmCompLock* is genuine business config and migrating it requires reading those master tables, not the client code.
2. The "screen → SI → BE → CM/DA → SQL" stack is mechanical and shape-preserving: porting one screen tells you exactly how the next 562 work.
3. The DataSet / DataTable wire format is the entire integration contract — every column name in every table is identified by its c_clm* constant somewhere in *CommonLibrary and reused server side. A modern rewrite that keeps the column names verbatim can re-use the help-PDF documentation 1:1.