VECTORIO
EN
EnglishDeutsch

“Subsidiaries send their staff lists as spreadsheets — by e-mail, every month”

One address list across many organisations.

Subsidiaries deliver CSV or XML by encrypted e-mail; Connectype picks it up, checks it and syncs it.

The problem
  • Every subsidiary sends a different spreadsheet, and someone types it into the directory.
  • Personal data travels unencrypted as e-mail attachments.
  • The group address list is out of date the day it is finished.
With PROTOR
  • Subsidiaries deliver CSV or XML by encrypted e-mail; Connectype picks it up, checks it and syncs it.
  • Only what changed is written — new, changed and removed entries alike.
  • One consistent address list across all organisations, with a signed record of every change.

From today to the first result.

What you do today

spreadsheets that someone types into the directory

Every subsidiary sends a different spreadsheet by e-mail, someone types it in, and the group address list is outdated the day it is finished.

With Connectype

Subsidiaries deliver CSV or XML by encrypted e-mail, and only what changed is written: 20 changes in 2.7 s.

Your first step

Let one subsidiary deliver its file by encrypted e-mail and preview the sync.

one subsidiary
How it runs

Directory contacts, synced as deltas. Step by step.

10,000 contacts are read with change tracking, checked, mapped to Active Directory attributes and written — rejected rows land in a dead-letter file for review.

PROTOR · Directory contacts, synced as deltasrunning
Contacts fileCSV SubscriberSchema ConformanceSchema ConformMap to AD schemaAD Schema MapperGAL attributesExpression MapperQuality GateSync.QualityGateDirectory exportCSV PublisherRejected contactsCSV Publisher
  1. Contacts fileCSV Subscriber
  2. Schema ConformanceSchema Conform
  3. Map to AD schemaAD Schema Mapper
  4. GAL attributesExpression Mapper
  5. Quality GateSync.QualityGate
  6. Directory export · Rejected contactsCSV Publisher · CSV Publisher
nodes
csv-source-contacts → CSV.Subscriber
schema-conform → ETL.SchemaConform
ad-schema-mapper → AD.SchemaMapper
expression-mapper → ExpressionMapper
quality-gate → Sync.QualityGate
csv-target-contacts → CSV.Publisher
csv-dlq-contacts → CSV.Publisher
10,000 contacts with change trackingmapped to Active Directory attributesdead-letter file for rejects
  1. Contacts fileReads rows from a CSV file in batches.
  2. Schema ConformanceEnforces required fields and safe types.
  3. Map to AD schemaMaps source fields to directory attributes.
  4. GAL attributesMaps and transforms fields with expressions.
  5. Quality GateChecks rows against rules and routes failures to a dead-letter table.
  6. Directory exportWrites rows to a CSV file.

A real workflow from our end-to-end test suite; the designer view is illustrated.

What you get. From the first pilot.

Subsidiaries deliver CSV or XML by encrypted e-mail; Connectype picks it up, checks it and syncs it.

Only what changed is written — new, changed and removed entries alike.

One consistent address list across all organisations, with a signed record of every change.

Why your tools fall short.

×

Directory sync tools expect a direct connection to every source directory.

×

Manual imports are slow and leave no trace of who changed what.

×

Shared spreadsheets carry personal data with no protection.

What drives it
  • Group structures with independent IT per subsidiary
  • Data protection for staff data in transit
  • Public-sector rules for on-premises processing

Your pilot. Three steps.

1

Your data shape

Tell us what data you have, where it lives and what the result must be.

2

A scoped pilot

On your data and your hardware, with the success measure written down first.

3

A clear decision

You see the result against that measure — and keep every workflow and record.

Beta · design partners wanted

Bring us your hardest data problem. Let's solve it together.

A short pilot on your data and your hardware. We agree on what success looks like before we start.