Make your enterprise data ready for AI.Verified for your AI, and kept that way.
Diagnose your data, prepare what the use case needs, and test the fit on your own model or agent under the same conditions. Recheck when conditions change.
Whether you can trace which steps produced this data.
Auto-managed metadataSteps recorded per versionRun history kept
Changes · as of v4 · 5 applied · 1 excluded
Review the fixes Data Ready proposed.
!Check 1 order with no customer infoWith no customer reference or contact, the amount alone cannot identify the customer.Not applied because it needs a manual check.ExcludedEvidence
✓Fill blanksFilled blanks by business rules so fewer rows are dropped from training.✓ Applied · v2Evidence
✓Remove duplicatesMerged rows where the same measurement was entered twice.✓ Applied · v2Evidence
✓Unify unitsUnified mixed units such as ℃ and °F.✓ Applied · v3Evidence
✓Unify time zone (UTC)Aligned measurement times to UTC so the order stays correct.✓ Applied · v3Evidence
✓De-identify personal dataReplaced inspector names and contacts so the data can be used with fewer original values exposed.✓ Applied · v4Evidence
Syntitan AgentExample
Persona survey
Survey virtual respondents similar to your customers to find answer distributions and improvements for each question.
Analysis report · PDF download
Customer success
15+ min
Download sample response CSV
Select data to analyze1/3
Demographic data is required. Survey data makes the results richer.
Customer behavior (cleaned)Ready for Raw Data
Campaign sends (cleaned)Ready for Raw Data
Demographics (organized)Ready for Raw Data
Churn training dataReady for Model
Sales history training dataReady for Model
customer_activity_2025.csvOriginal
crm_send_history.csvOriginal
institution_perception_survey_2025.xlsxOriginal
survey_2024.xlsxOriginal
Data needed for analysis
Demographic dataRequired for analysis
RequiredRespondent ageage, age_group
RequiredRespondent gendergender, sex
RecommendedPast survey responsesquestion, answer
Form types3–50 questions
Multiple choiceSingle or multiple answers
RankingPut options in order
RatingScore on a scale
MatrixRate several items on one scale
Open-endedAnswer in free text
Preview
Response distributionShows a chart and a short reading for each question type.
Standard dataUpload work files to generate test cases.
Personal or confidential dataHide sensitive fields, then generate test cases.
Sample dataSee the full flow without your data.
Recent projects
ProjectTypeDatasetsStatusOwnerUpdated
Permit renewal agent validationReady for Agentpermit_rules_2026 +1WaitingJamie Park4 days ago
Inspection assistant validationReady for Agentfacility_inspectionsCompletedAlex KimOct 30
Ready for Raw DataPrepare regional orders for shared useExample
1Goal & data
26-axis diagnosis
3Review proposal
4Validation
What do you need to accomplish?
Tell us the purpose, source and destination. Review the proposed handling next.
Your task
Prepare reusable order data while preserving currencies and customer relationships.
Source dataUse sample data
Data type
Permitted data / working copyPersonal / confidential data
Import method
Upload a fileCSV · XLSXUploaded datasetsDatasetsExternal sourceDatabases · cloud
data_example.csv10 rows · 8 fieldsChoose file
ⓘ DB & app connectionsⓘ File size or format issue?
Preview source
Syntitan proposesStart with the task, not a processing recipe.
Inspect the source and task conditions
Propose DTS processing and preservation constraints
Compare changes and task-specific results
You can stop at data preparation and continue with a model or agent when ready.
Product walkthrough sampleScores, transformations and evaluations illustrate the product experience; they are not customer measurements.
Ready for ModelAdapt transactions to a detection modelExample
1Goal & data
2Review related columns
3Baseline
4Result & validation
What do you need to accomplish?
Tell us the purpose, source and destination. Review the proposed handling next.
Your task
Align units and inputs, supplement scarce cases, and inspect both detection gains and false alerts.
Source dataUse sample data
Data type
Permitted data / working copyPersonal / confidential data
Import method
Upload a fileCSV · XLSXUploaded datasetsDatasetsExternal sourceDatabases · cloud
model_example.csv12 rows · 9 fieldsChoose file
ⓘ DB & app connectionsⓘ File size or format issue?
Preview source
Task type
Binary classificationSuggested
Compares before/after performance on how well the model separates two classes.2 classesMCC · Macro F1 · ROC-AUC
Anomaly detection
Measures a detection model that finds records outside the data's normal distribution.Normal / AnomalyPR-AUC · Recall · F1
Regression
Compares before/after performance on continuous predictions.ContinuousR² · RMSE · MAE
Multiclass
Measures per-class performance of a model that predicts one of three or more classes.3+ classesMacro F1 · accuracy, etc.
Based on what you wrote, we picked binary classification as a suggestion. You can change it.
Syntitan proposesStart with the task, not a processing recipe.
Inspect the source and task conditions
Propose DTS processing and preservation constraints
Compare changes and task-specific results
You can stop at data preparation and continue with a model or agent when ready.
Product walkthrough sampleScores, transformations and evaluations illustrate the product experience; they are not customer measurements.
Ready for AgentRefund exception checkExample
1Describe the task
2Review task scope
3Cases
4Run & compare
Set up the agent's task
Add the task the agent handles and the documents it works from.
Demo: after a failed analysis
Name *
Refund exception check
Main task *
I want the support agent to handle refund exceptions correctly.
How to provide task files *
Upload fileUpload a task manual or agent MD file and we analyze the decision rules.Connect via SDKConnect the agent to read its instructions and tool settings.
Upload file *
Standard fileContains personal data
Add documents
✓ Agent MD guide uploaded. You can combine uploaded files with existing data. (Up to 10)
Upload 2Existing dataExternal sources
Drag a file here or click to uploadUp to 20 MB per file · up to 10 filesEnter text instead
Selected documents 2/10Uploaded 2
CSVrefund_manual.csv×
MDrefund-agent-guide.md×
Summary
Agent
Refund exception check
Upload file
refund_manual.csv + 1 more
Personal data protection
Off
Work StudioHomeExample
Data that was hard to feed into AI, made ready to use.Start by seeing what is wrong with your data.
From preparation to results in one placeNo data expert? That’s fine.Syntitan proposes how to prepare your data first.
Examples by industryHere is what you can do with it.Pick a case close to your work and see right away how the data changes.
Prepare data for AII want to use customer order records for AI analysis, with personal details replaced.Names are hidden, but the same customer keeps the same value. Date and country formats are unified, and rare overseas orders are supplemented.
120 overseas order cases were supplemented. Names are hidden, but each customer's order flow stays intact.
Check how well AI predictsI want to know which customers will churn next month.Align fee formats and fill in missing plans, then compare how many more churning customers are found under the same conditions.
Before
CustomerPlanMonthly fee
C-01Premium55,000 KRW
C-0255000
C-03basic33000 KRW
▶
After
CustomerPlanMonthly fee
C-01Premium55,000
C-02Premium55,000
C-03Basic33,000
Check how well AI predicts
What to predict
Churn
Churning customers foundout of 200 actual
140›158
The prediction score rose from 0.710 to 0.780. You can reach out to customers likely to churn first.
Prepare data for AII want to prepare support records for an AI chatbot.Customers are grouped and masked even when contact formats differ. Duplicate records are merged so the same content is not learned twice.
85 duplicate support records were merged. Past inquiries are kept without being learned twice.
Check how well AI predictsI want to pick out products likely to be defective in advance.Unify temperature units and exclude sensor errors, then compare how many more defects are found under the same conditions.
Before
ProductTemperaturePressure
P-0785℃1.2 bar
P-0899991.3
P-09185°F
▶
After
ProductTemperature (℃)Pressure (bar)
P-0785.01.2
P-081.3
Sensor error excluded
P-0985.01.25 (avg)
Check how well AI predicts
What to predict
Defect
Defective products foundout of 60 actual
42›47
The prediction score rose from 0.510 to 0.580. You can inspect products likely to be defective first.
Prepare data for AII want to align scattered sales records before analyzing revenue.Date formats and currency units are unified so revenue can be combined on one basis. Missing amounts are flagged, not filled in arbitrarily.
Before
OrderDateAmount
O-112026.9.348,000 KRW
O-1209/03/26
O-132026-09-03$36
▶
After
OrderDateAmount
O-112026-09-0348,000 KRW
O-122026-09-03
Needs review
O-132026-09-0336 USD
Ready to use with AI
What was preparedThe original stays as is
Date alignmentCurrency alignment
Readiness
61 pts›84 pts
312 date and amount entries were aligned. Revenue can be combined on one basis, and missing amounts are flagged separately.
Check how well AI predictsI want to know which loans are likely to become delinquent.Unify income and amount units in KRW and fill in blanks, then compare how many more delinquent loans are found under the same conditions.
Before
LoanMonthly incomeLoan amount
L-113M30,000,000 KRW
L-12300000025M
L-1318000000
▶
After
LoanMonthly incomeLoan amount
L-113,000,00030,000,000
L-123,000,00025,000,000
L-132,800,000 (avg)18,000,000
Check how well AI predicts
What to predict
Delinquency
Delinquent loans foundout of 120 actual
84›95
The prediction score rose from 0.640 to 0.710. You can review loans likely to become delinquent first.
Handling · applied 4 · excluded 0Recommended steps are applied by default. Excluded steps are recorded as ‘Excluded’
Replace names, emails and phone numbers with stand-insThe same customer gets the same value (e.g., ‘Customer_0193’), so order history stays linked
Unify order date formatMixed formats like 2026/10/01 · 2026-10-01 into one
Supplement scarce overseas ordersOverseas orders are only 2%, so country analysis skews domestic. We add cases similar to real overseas orders and flag the added rows
Unify country labelsMixed labels like US · USA · United States into one
This stepWe’ll prepare it with 3 cleanups and 4 supplements
The original stays as is; a cleaned new version is created separately.
Syntitan prepares firstNo need to know how to read the results
Train the same AI on both versions
We compare how much better it predicts under the same conditions
We explain what changed in plain words
If it falls short, you can keep refining
Review data impactCreate projectExample
Select data
2Question
3Baseline
4Compare
What do you want to predict?
Choose what to predict, and we compare before and after under the same conditions.
This stepChoose what to predict, and we compare under the same conditions
For your goal, we compare data before and after preparation under the same conditions. If no goal fits, write your own.
Review data impactCreate projectExample
Select data
Question
3Baseline
4Compare
We predicted with the data before refining first
Results measured on your current data. We’ll refine the items below and compare with the same AI
Prediction score57%Below the threshold (75%)
Share of actual cases found52%Found 196 of 374 actual cases
Share of AI picks that were correct62%196 of 314 picks were correct
Scope
21 columns · 7,043 rows · 1,409 rows used for scoring
Column to predict: ‘Churn’
Positive side ‘Yes’ 26.5% · rest 73.5%
AI model
1 representative AI · scores for all 4 are in Expert mode
Gaps and handling to try
Handling to tryWhat we found
Drop confusing training rowsSimilar rows, different outcomes · training only
Fill blank ‘TotalCharges’ cells11 rows are blank · fill with the column median
Turn text values into numbersText values like ‘Contract’ · converted by frequency
Next stepAfter refining the data, we compare again with the same AI
Review data impactFind rows where ‘Churn’ is ‘Yes’Example
Find rows where ‘Churn’ is ‘Yes’21 columns · 7,043 rowsv2
Type
Review data impact
Question
Know who will cancel next month
Column to predict
Churn (find Yes)
Datasets
telco_churn.csv
Before/after comparison complete
Saved to recent projects. Your uploaded file stays unchanged.
ReportCompare before/after performance.
Proof KitGet before/after metrics at once
Connect a destinationConnect via MCP or API.
Predictions before/after refining
Correctly found cases rose from 196 to 288
Correctly found196▸ 288Of 374 actual cases
Newly found92Missed before refining, found after
No longer found0No cases were found before but missed after refining
What made the difference?We refined the data by dropping confusing training rows. Rows with similar values but different outcomes confuse the AI, so only the majority-side rows were removed from training. Evaluation rows used for scoring are unchanged.
Newly found row IDs1,6406,1267513,3635,9691,4733,9763,5171,9886,389+82 more
AI accuracy changeThe score rose but is still below the threshold (75%)
Recall–precision balanceA score combining the two rates on the right56.98% → 62.61%+5.63pp
Support ticket triage agent4 filesAgentv1DoneAAlex KimOct 15
Order lookup agent2 filesAgentv1DoneAAlex KimOct 1
Summary
Agent
Refund support agent
Connection
Upload files
File
3
Switch to sample?
Switching removes your 3 uploaded files. You can upload them again anytime.
ConnectionsExample
Connections
Connect refined data so your AI tools can read it directly. Connections are set up in Expert mode.
What you can do in Expert mode
Bring in data via DB · app connectionsConnect to DBs, analytics tools and cloud storage to bring in allowed data directly.No need to download and re-upload files
Combine dataCombine multiple datasets by stacking rows or joining columns into new data.Refine split data like customer info and order records at once
Send refined dataChoose a version to send to MCP tools like Claude, data platforms or storage.Creating a new version keeps existing connections as they are
See destinations and applied status at a glanceSee where each version is used and whether it’s applied, on one screen.If results change, find which version was in use right away
What is combining data?
UnionStack data of the same shape to add rows.
DateNameTier
5/3Amin KimStandard
5/18Seokwon HanVIP
6/10Hyuna JungStandard
6/20Minsu KimVIP
I want to merge monthly data into oneMay new members + June new members
JoinJoin side by side on a shared key (e.g., customer ID) to add columns.
Customer IDPurchasesSupport ticketsPoint balance
user_001120K24,200 pts
user_002340K38,900 pts
user_003520K0900 pts
user_004-1-
I want to link data and analyze it togetherCustomer ID · purchases · points + customer ID · tickets
Where you can connect in Expert mode
ImportSome of 16 DB · Analytics · Cloud Platform sources
Claude MCPMCPDatabricksData PlatformSnowflakeData WarehouseAmazon S3Cloud StorageAzure Blob StorageCloud Storage
Run HistoryExample
Run History
See which project versions Ready for Raw Data and Ready for Model produced each time the source dataset was updated.
Source datasetga4_web_events · Google BigQueryD
P1GA4 web event cleanupReady for Raw Data
P2Churn prediction training dataReady for Model
03.31#c9d9e52
Import March events1,284,500 events · 1,180 customers
04.01v1
Create project · 4 preprocessing stepsStrip symbols and commas from amounts · Standardize date formats · Link country spellings · Fill blanks with representative values
#c9d9e52basis
04.03v2
Remove constant columnsApplied one more preprocessing step · 3 columns removed
#c9d9e52basis
04.03v1
Create project · fill missing churn casesTask: churn prediction (classification) · Label: churned · F1 0.62 → 0.71 after filling churn cases
Refined for the model#c9d9e52basis
04.30#b9d9cbf
April events added automatically+412,300 events · +220 customers
05.01v3
Same preprocessing applied to the April updateReapplied the 5 steps used through v2 to the April update in one go
Update applied#b9d9cbfbasis
05.02v2
Same refinement applied to the April updateReapplied the v1 refinement to the April update and compared before and after under the same conditions · F1 0.71 → 0.72
Update applied#b9d9cbfbasis
05.31#a9d9b2c
May events added automatically+398,700 events · +185 customers
06.01v4
Same preprocessing applied to the May updateReapplied the 5 steps used in v3 to the May update in one go
Update applied#a9d9b2cbasis
06.12v5
Drop “Fill blanks with representative values”Left the blanks as they are and reapplied the other 4 steps
#a9d9b2cbasis
06.30#99d9999
June events added automatically+421,000 events · +198 customers
07.01v6
Same preprocessing applied to the June updateReapplied the 4 steps used in v5 to the June update in one go
Update applied#99d9999basis
Not applied yet
All pending · 2
Space + drag to pan · ⌘ + scroll to zoom−100%+Fit
ConnectorsExample
Connections
Connect the tools you already use to bring data into Syntitan and send it out.
MCP 5
Claude MCPAnthropic's AI assistant
ChatGPT MCPOpenAI's AI assistant
Cursor MCPAI code editor
Gemini MCPGoogle's AI assistant
Microsoft Copilot MCPMicrosoft's AI assistant
Databases 10
PostgreSQLOpen-source relational database
MySQLRelational database widely used for web services
MariaDBMySQL-compatible open-source database
Microsoft SQL ServerMicrosoft's enterprise relational database
Oracle DatabaseRelational database for large business systems
MongoDBDatabase that stores JSON documents
SnowflakeCloud data warehouse
Google BigQueryGoogle Cloud's data warehouse
Amazon RedshiftAWS data warehouse
DatabricksLakehouse platform for analytics and AI
Analytics 4
GA4Web and app visits and conversions
AmplitudeProduct usage events
MixpanelUser behavior flows
Adobe AnalyticsEnterprise web marketing analytics
Cloud storage 3
AWSAmazon S3 file storage
Microsoft AzureAzure Blob file storage
Google CloudGoogle Cloud Storage file storage
Application StatusExample
Connections & usage
See what data each connector brought in and sent out, and when it was updated.
Hand over the data and the goal. Get it back checked against your criteria.
Prepare the data, fit it to your use case, and check the result yourself. Your criteria carry over to the next file (reuse after changes is coming soon).
ExampleCustomer churn prediction
01You hand over
customers.csvCRM
customer_id
plan
last_login
C-1042
Pro
09-28
c1042_
Pro
null
C-2210
Basic
10-02
C-3307
null
10-11
C-4415
Pro
10-09
4415
Pro
10-09
Use caseChurn prediction
Model and criteriaXGBoost v1.3Recall ≥ 0.82
02Syntitan does
Six-axis assessment
Usability
Integrity
Context
Consistency
Reproducibility
Traceability
Prepare what the use case needs
c1042_→C-1042Customer IDs linked
Same model, same evaluation set
Your criterion
Before
After
03You get back
Version 2New version
Criteria met
for churn prediction with XGBoost v1.3
Criterion
Recall ≥ 0.82 met
Evidence
Before and after under the same conditions
Changed
Customer IDs linked, gaps filled
v1 startv2 new
Saved for next timeUse case profile for the next file
What you stop redoingAsking the data team to clean files and waiting. Revalidating from scratch every time the data changes.
Position in the stack
Between your data
and models,Syntitan fills
the missing layer.
Works with the storage, models, and tools you already use. Syntitan prepares and checks the data for your AI, and records the data state each run used.
Every run should be able to say which data state it ran on.
Fraud detection
Customer analytics
Enterprise copilots
AI agents
Risk simulation
Document search & summary
Each run is bound to a specific data state and recorded, so any result can be traced back.
SyntitanAI-Ready Data Platform
Three paths. Start with the question you need answered now.
Ready for Raw Data
Ready for Model
Ready for Agent
LLM Capsule
Core capability · standalone
Context-Preserving Data Layer for AI
Substitute
Execute
Recover results
DTS
Core capability · standalone
Core technology that prepares the data your AI task needs
Supplement
Data Enablement for AI
Standalone
Organized for management, not yet verified as ready for AI.
DatabasesSQL · NoSQL
DocumentsContracts · Internal
CRM & ERPSalesforce · SAP
Object StorageS3 · Data Lake
Logs & IoTSensors · Streams
APIs & LegacyREST · SOAP
Every source is here and clean. That still does not make it AI-Ready.
Three ways to start
Start from
the question
you need to answer now.
Syntitan is CUBIG's AI-ready data platform.
Every path keeps the original dataset and saves each result as a version.
AI: Fraud and AML decision modelData: Transaction and account logs
DiagnoseProblemWhere the data stands today
Rare fraud and AML patterns barely appear in training data, so the model misses them. Later, no one can find the data behind a decision.
Prepare and compareWhat we applyPrepared and validated for the use case
DTS fills the gap with the rare scenarios the task needs. Syntitan records that data as one version, exactly as it was validated.
Check the resultVerdictUsable for this use case, or not
Criteria met forfraud detectionThe model decides on data that includes rare patterns, and each decision traces back to the data it ran on.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Syntitan saves the version that met the criteria and records which version each run used. When transaction patterns change, review the change and revalidate the affected data.
ExampleHealthcare
Clinical decision support
AI: Clinical decision-support LLMData: Patient records (PHI) · rare-disease cohorts
DiagnoseProblemWhere the data stands today
Patient data cannot go into an LLM as it is, and rare-disease cohorts are too small to train on.
Prepare and compareWhat we applyPrepared and validated for the use case
LLM Capsule substitutes patient identifiers, keeps clinical context and structure, and runs the clinical LLM on that working version. DTS fills out rare-disease data to a trainable size.
Check the resultVerdictUsable for this use case, or not
Criteria met forclinical decision supportThe original patient records stay in the hospital. Clinical work uses the substituted working version, and research uses the prepared cohort.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Syntitan keeps the working version and the prepared cohort as one data version, records it on every run, and revalidates it when records change.
ExamplePublic sector
Policy sentiment & citizen services
AI: Policy sentiment analysis · citizen-service LLMData: Agency citizen records
DiagnoseProblemWhere the data stands today
Citizen records sit in separate agencies under privacy law, so LLM services cannot use those records directly.
Prepare and compareWhat we applyPrepared and validated for the use case
DTS reconstructs agency citizen records into a form that is not restored to individual records, and LLM Capsule substitutes identifiers in the records the citizen-service LLM uses while keeping their context.
Check the resultVerdictUsable for this use case, or not
Criteria met forpolicy sentiment analysisLLM services analyze shifts in policy sentiment and answer citizen requests. The agency can see which records each answer used and how Capsule substituted them.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Every run records the data version it used. When agency records change, review the change and revalidate.
ExampleTelecom
Real-time inference & network operations
AI: Real-time inference service · network operations modelData: Pipeline versions · topology change records
DiagnoseProblemWhere the data stands today
When inference results change, no one can tell which input data version or network configuration change caused it.
Prepare and compareWhat we applyPrepared and validated for the use case
Syntitan records the data and pipeline state as versions and logs the difference when a change comes in.
Check the resultVerdictUsable for this use case, or not
Criteria met forreal-time inferenceCompare the changed run with the last run that met the criteria, under the same evaluation conditions. See what changed in the data and reuse the version that met the criteria.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Syntitan records which version each run used. When the topology changes, review the change and revalidate the affected data.
Rare defect classes are underrepresented in training data, so the model misses uncommon defects in production.
Prepare and compareWhat we applyPrepared and validated for the use case
DTS fills in inspection data for the rare defect types, and Syntitan verifies the data before and after under the same conditions.
Check the resultVerdictUsable for this use case, or not
Criteria met fordefect detectionThe inspection model trains on data that includes rare defects, with a record of which data it trained on.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
When line settings or product specs change, you review the change and revalidate the inspection data.
ExampleInsurance
Claims processing
AI: Claims-processing LLMData: Claim documents · policyholder records
DiagnoseProblemWhere the data stands today
Claim documents carry policyholder identifiers as they are, so they cannot go into LLM processing.
Prepare and compareWhat we applyPrepared and validated for the use case
LLM Capsule substitutes policyholder identifiers, keeps the claim context, and runs the LLM on that working version. It then restores the original values inside the company.
Check the resultVerdictUsable for this use case, or not
Criteria met forclaims processingClaim summaries and rationale come back matched to the real case and flow straight into review.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Each run records which fields Capsule substituted and which data version it used. When document formats change, Syntitan revalidates the data.
When recommendation quality drops, it takes days to find what changed in the data or the runtime.
Prepare and compareWhat we applyPrepared and validated for the use case
Syntitan records the data state and the runtime details of that moment as one version, and logs which version every run used.
Check the resultVerdictUsable for this use case, or not
Criteria met forproduct recommendationYou compare the degraded run with a run that met the criteria on the same basis and see what changed in the data.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
When the catalog or log schema changes, you review the change and revalidate the recommendation data.
ExampleDefense
LLM support in isolated networks
AI: Document analysis and Q&A LLMData: Documents and operating records inside the isolated network
DiagnoseProblemWhere the data stands today
Documents cannot leave the isolated network, and stripping context makes LLM answers useless.
Prepare and compareWhat we applyPrepared and validated for the use case
LLM Capsule substitutes identifying details inside the isolated network to make a working version. Only that working version, with structure and context intact, goes to the LLM on the approved path.
Check the resultVerdictUsable for this use case, or not
Criteria met fordocument analysisThe originals stay inside the network while analysis and Q&A results come back in the original terms.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
Capsule keeps the substitution set as a version and records it per run. When document formats or classification rules change, Syntitan revalidates it.
ExampleIndustrial · OT/ICS
OT network data analysis
AI: Anomaly detection modelData: OT network logs · equipment telemetry
DiagnoseProblemWhere the data stands today
Raw OT data reveals plant configuration and cannot leave the site for analysis, and anomaly cases are rare.
Prepare and compareWhat we applyPrepared and validated for the use case
DTS reconstructs the data without plant configuration, keeps the patterns anomaly detection needs, and fills in the rare anomaly cases.
Check the resultVerdictUsable for this use case, or not
Criteria met foranomaly detectionThe team trains the anomaly model on reconstructed data and verifies it under the same conditions as the site data. The original telemetry stays on site.
Track and reuseOperate and recordRecorded per run · recheck after changes coming soon
When equipment joins or protocols change, you review the change and revalidate the data.