Enquire
Menu

Syncops / Included capability

Syncops. The plant's memory, and the team that runs on it.

Every Silec retainer runs on Syncops: a private, per-site platform that reads your OT, MES and ERP data, files what your people know, answers in plain English with the source shown, runs the routine jobs overnight, and produces the monthly report from the work itself. It is included in the retainer, never sold separately.

The home screen.

Open items, today's due, last night's jobs and the documentation number — then the question someone asked at 06:40 and what needs a decision.

What it does.

Twelve things it does for your plant, every day, without being asked twice.

Ask your own data.

Plain-English questions answered from historian, SCADA, MES and ERP reads plus your documents, with the source cited. Says "not covered" instead of guessing.

A team of agents, not one bot.

Roles with their own instructions, tools and memory: a chief of staff that delegates, a planner, a desk clerk for the shared mailbox, a librarian that files nightly, a plant-ops specialist, a memo scribe. Add your own from a pack.

Meetings and site walks become records.

A wearable or a phone records; speech is transcribed and diarised, names and project applied, summarised, tasks captured, reviewed by a person, then filed.

The knowledge vault.

Plain markdown in an Obsidian-compatible folder on your NAS or server: entity notes for people, systems and organisations, decisions, procedures, per-project front pages, a nightly health report, full history under git. Sync it to your own laptop.

Documentation you can measure.

A system register with a named data owner, a document and a review date per system; coverage reported monthly — how many systems have a current, reviewed document.

The planner and your calendar.

One board for jobs and tasks, synced to Outlook, reminders on your phone, voice capture, per-item context notes filed to the vault when done.

Reports with an evidence trail.

A deterministic report engine: versioned methods, inputs captured with hashes, factors versioned, reproducible outputs, named sign-off before anything leaves. A model never computes a reported number.

Analysis, not just chat.

Read-only SQL with streaming to Parquet, a sandboxed Python workspace (pandas, DuckDB), forecasting, charts, Word/Excel/PDF exports on your templates, Excel workbooks read structurally (formulas, tables, VBA).

Routine work, overnight.

Cron schedules and heartbeats per agent: the morning briefing, compliance checks, the nightly filing run, deviation alerts by email, Teams-style channels, Slack or Telegram.

Approvals on your phone.

Anything that leaves the site — an email, a report, a data-map change — is an approval card first: one tap from a push notification.

Time, service report, invoice lines.

Hours logged where the work happens (page, planner, voice); the monthly service report and the invoice lines come from the same record.

Search everything.

Notes, documents, chats, planner, memos — one ranked search with dates and provenance; "since you last looked" on the home page.

Where it sits.

Beside the stack, not inside it. Reads from L2, L3, L4 and your people; writes only to people.

Where Syncops sits: beside the ISA-95 stack, reading from L2, L3, L4 and people, writing only to people, with MCP links to vendor context and to your tools. People Microsoft 365: mail, calendar, SharePoint;meetings; the wearable L4 ERP NetSuite, SAP, MYOB L3 historian, OT network, MES production, quality, traceability L2 PLC / HMI / SCADA Ignition, Citect, Wonderware L0–L1 field devices & instrumentation YOUR PLANT — THE ISA-95 STACK SYNCOPS private, per-site vault + search agents + approvals planner + reports read-only connectors M365 SSO, calendar, mailbox,SharePoint documents,the pendant read-only ERP viewsor exports read-only SQL to the MESand historian databases SCADA read API, historian OUT → answers, reports, cards, briefings, exports Flow / HighByte /Ignition MCP we consume contextualisationfrom the vendors that do itwell; we never build ahistorian or a namespace vendor context over MCP your tools dashboards, scripts,copilots read-only MCP endpoint,scoped tokens Where Syncops sits: beside the ISA-95 stack, reading from L2, L3, L4 and people, writing only to people, with MCP links to vendor context and to your tools. People Microsoft 365: mail, calendar,SharePoint; meetings; the wearable → M365 SSO, calendar, mailbox, SharePointdocuments, the pendant L4 ERP NetSuite, SAP, MYOB → read-only ERP views or exports L3 historian, OT network, MES production, quality, traceability → read-only SQL to the MES and historiandatabases L2 PLC / HMI / SCADA Ignition, Citect, Wonderware → SCADA read API, historian L0–L1 field devices & instrumentation YOUR PLANT — THE ISA-95 STACK SYNCOPS private, per-site vault + search agents + approvals planner + reports read-only connectors OUT → answers, reports, cards, briefings, exports Flow / HighByte /Ignition MCP we consume contextualisationfrom the vendors that do itwell; we never build ahistorian or a namespace vendor context over MCP your tools dashboards, scripts,copilots read-only MCP endpoint,scoped tokens
Reads L2–L4 through read-only accounts your IT controls. Writes nothing to a control system. Sits in your network or your own cloud account.

Integration points

LayerWhat Syncops connects toHow
SCADAIgnition (WebDev read API and Ignition’s MCP module), other SCADA via historian tablesread-only gateway user or API key; browse/read/history/alarms
Historian / MES / ERPPostgreSQL, MySQL, SQL Server-compatible, SQLite, DuckDB; Parquet and CSV on a file share or S3read-only roles, statement timeouts, streaming to Parquet — never raw rows into a model
DocumentsSharePoint folder (read-only, app permission scoped to one site), file uploads, the vaultindexed with headings and page numbers; cited by title and page
IdentityMicrosoft Entra ID single sign-on, MFA / passkeys, per-user device tokensyour tenant; roles operator / approver / admin
Mail & calendarMicrosoft 365 mailbox for the desk clerk, Outlook calendar sync, sending via your tenantGraph, per-user connections
NotificationsWeb push, Telegram, Slack, Discord, emailper person or per channel
VoiceOn-site speech-to-text and text-to-speech (GPU box) or AWS Transcribe / Polly in Sydneynever a browser vendor’s speech service
Vendor contextFlow, HighByte, Inductive Automation’s MCP serverconsumed over MCP with OAuth, scoped, results treated as untrusted data
Your toolsA read-only MCP endpoint on the instancescoped tokens, rate-limited, every call audited
AI modelsAnthropic Claude via AWS Bedrock in Sydney (default); local models on a GPU box for an air-gapped tiera locality policy in the product; anything outside AU needs a signed waiver

How it is deployed

On your own VM (default)In your own AWS accountAir-gapped
Computea Proxmox / VMware VM in your IT or DMZ VLANan EC2 instance in Sydney, in your accountyour VM plus a GPU box
AI and voiceyour own AWS account in Sydneysame accountlocal models only
Data at restyour hardwareyour account, encrypted, daily snapshotsyour hardware
Access from outsideyour VPNHTTPS with SSOyour VPN
Updatesa versioned image pulled over your VPNstaged rollout, rollback = previous versionmanual

Security controls

The long version, for your IT, is on the Security page.

Why it exists.

We built it because the same plant questions were being answered from memory, the same documentation was missing at every site, and the monthly report took an evening. Syncops is how our team runs a plant's OT, MES and integration work properly. It is not for sale on its own; it comes with the team.

Start with a conversation

Enquire — or request the security pack.

Enquire

Twenty minutes on the phone tells you whether a retainer fits. We will call you back.