TetherPoint Sync

TetherPoint Sync is kitting workflow software built for SAP-connected production floors. It runs on rugged Android tablets at the kitting station, replaces paper travelers with enforced digital workflows, and produces an auditable component-level record of every kit your floor builds — automatically, at the point of scan.

What It Does

A kitting operator opens a production order on the tablet. The order — pulled live from SAP — lists each component, the required quantity, and the lot rules that apply. The operator scans each component's GS1 barcode as it's added to the kit. The system verifies the component matches the bill of materials, the quantity is correct, and the lot satisfies any FEFO or expiration rules. Mismatches block at the scan. When the kit closes, a signed manifest with components, lot numbers, quantities, timestamps, and operator ID is generated automatically and archived to your SMB network share.

That is the entire scope. We do not manage inventory, run MRP, or replace your ERP. TetherPoint Sync is the layer between your operators and your SAP system — the part that paper currently does badly.

SAP Integration

TetherPoint Sync connects to SAP through a lightweight middleware proxy that exposes a REST API to the tablet. The proxy authenticates against SAP using your existing service-user credentials and translates the tablet's requests into standard SAP function modules and BAPIs. No core SAP modifications are required.

Data Flow

• Production order pull — Tablets request the active production order list and component bill of materials.
• Lot & batch lookup — Each scanned component is validated against SAP's batch master for expiration date, status, and storage location.
• Goods movement posting — On kit close, the system can post goods issues against the production order automatically.
• Audit retrieval — Completed kit manifests remain queryable on the tablet and on the SMB archive without re-hitting SAP.

Barcode & Scanning Standards

TetherPoint Sync reads GS1 standards: GS1-128, GS1 DataMatrix, and GS1 QR Code. It parses Application Identifiers (AIs) for GTIN (01), batch/lot (10), expiration date (17), serial number (21), and quantity (37). The system can be configured to read SSCC pallet labels (00) when shipping kits as palletized loads.

Non-GS1 barcodes — internal item-master codes, supplier-specific labels, custom Code 128 — are also supported. The barcode parser is configurable per item-master segment, so your existing labeling does not need to change before deployment.

Hardware & System Requirements

TetherPoint Sync runs on commercial-grade Android tablets with integrated 1D/2D imagers. We recommend devices in the Zebra ET40, Honeywell EDA52, or Samsung Galaxy Tab Active class — devices rated for shop-floor temperature, drop, and ingress conditions. The application also runs on consumer Android tablets paired with a Bluetooth-class scanner for lower-volume deployments.

iOS support is available for select deployments. Tablet count scales linearly — one tablet per kitting station is the typical configuration.

Deployment Process

Deployment is intentionally short. We do not run multi-month implementation projects. The standard sequence:

• Day 0 (pre-arrival) — Provide your SAP service-user credentials, target production orders, and SMB share path. We pre-configure the middleware against a test SAP instance.
• Day 1, AM — Install the middleware on your VM. Connect to your SAP environment. Verify production order pull and bill-of-materials retrieval against a test work order.
• Day 1, PM — Provision tablets. Train the first operator. Run the first live kit on the floor.
• Day 2+ — Scale to remaining stations as you're ready.

If you cannot be running on the same day, something is wrong with the software — not the implementation plan. That is a design constraint, not a marketing claim.

Data Architecture & Security

TetherPoint Sync is a fully on-premise system. There is no SaaS backend, no cloud sync, and no requirement that any data leave your network. The tablet talks to the middleware proxy, the proxy talks to SAP, and the manifest archive lives on your SMB share. We have no production data, no telemetry pipeline, and no reason to.

What Stays Where

• Production orders & bills of materials — In SAP, queried by the middleware on demand. Never persisted off-host.
• Active kitting session state — On the tablet, encrypted at rest.
• Completed kit manifests — On your SMB share, in a structured directory layout with one file per kit.
• Operator credentials — In your existing identity system (LDAP, Active Directory, or SAP user master).

Operator authentication uses your existing badge or credential system. Every scan, hard-block override, and kit-close event is signed with the operator's identity and a millisecond timestamp. The system does not allow anonymous events.

Compliance & Records

Kit Manifests

TP-0001247-001.pdf

The kit manifest is designed to satisfy traceability requirements without manual transcription. A typical manifest contains the production order number, the kit serial, every scanned component (GTIN, lot, expiration, quantity), every override (operator, supervisor, reason), and start/close timestamps. This is the record auditors ask for.

TetherPoint Sync supports the data-capture requirements of:

• GMP / cGMP — lot trace, operator identification, timestamped events
• ISO 22000 / FSSC 22000 — full forward and backward traceability per kit
• ISO 9001 — auditable digital records, version-controlled procedures
• 21 CFR Part 11 — electronic record integrity, signature capture (where deployed in regulated contexts)

We do not certify your facility — that is between you and your auditor. We make sure the underlying data exists, is signed, and is retrievable.

Frequently Asked Questions