3.6 Remote & Hybrid Work: Latency Controls

Manufacturing is a physical reality. We process atoms, not just bits. While we embrace the efficiency of asynchronous remote work for digital tasks, the factory floor dictates our rhythm. This policy defines the operational protocols required to maintain synchronization between distributed teams and the physical production line.

Remote work at Dannie.cc is not a benefit; it is an operational mode. It is granted only when the employee demonstrates they can bridge the "Latency Gap" without slowing down the line.

Role-Based Eligibility Logic

We categorize roles based on their proximity to physical risk. Eligibility is determined by physics, not seniority.

Tier 1: On-Site Essential (100% Presence)

Who: Production Operators, Maintenance, Warehouse, IQC/OQC, HR, Hardware Test Engineers (Bring-up).
Why: You cannot solder, inspect a solder joint, or interview a candidate effectively via Zoom.
Rule: 100% physical attendance required.

Tier 2: The Bridge (Hybrid Mandatory)

Who: Product Owners (PO), Hardware Design Engineers, Engineering Managers, Supply Chain Leads.
Why: These roles define what the factory builds. You must "walk the Gemba" (see the actual process) to make valid decisions. A CAD model is not reality; the physical prototype is.
Rule: Minimum 3 days/week on-site. Must be present for NPI (New Product Introduction) builds.

Tier 3: Remote Eligible (Digital Output)

Who: Software/Firmware Engineers, PCB Layout (Frozen Schematics), Data Analysts.
Why: The output is purely digital code or files.
Rule: Remote allowed if the "Factory Interface" protocols below are met.

The "Factory Interface" Protocols

Remote employees must compensate for their absence by increasing their signal fidelity. The following protocols are mandatory to prevent "out of sight, out of mind" delays.

Protocol A: The Anchor Timezone

The factory does not wait for your local sunrise.

The Rule: Remote staff must overlap a minimum of 4 continuous hours with the Production Time Zone (PTZ).
Impact: If the factory is in Vietnam (GMT+7) and you are in London, you must shift your schedule to be available when the line is running.
Violation: Missing a synchronous meeting with the factory team due to "timezone" is a performance strike.

Protocol B: Remote Debugging (The "Avatar" System)

"It works on my machine" is a banned phrase.

Hardware Ban: Do not take prototype hardware home. Home labs lack ESD protection and thermal chambers.
The Avatar: To debug remotely, you must pair with an on-site "Avatar" (Technician or Jr. Engineer) who acts as your hands.
Digital Twin: You must ensure your remote environment matches the factory test rig exactly (same firmware version, same scripts).
Visuals: When debugging a physical defect, use high-resolution live video. Do not guess based on text descriptions.

Protocol C: Documentation as Presence

In an office, you can tap someone on the shoulder. Remote, you cannot.

Availability Signal: You must update your status (Slack/Teams) to indicate availability.
The 15-Minute Rule: During the 4-hour overlap window, response time to direct pings must be < 15 minutes.
Output: "Work out loud." All decisions must be committed to Jira/Confluence immediately. If it isn't written, you didn't do it.

Environment & Security Standards

To work remotely, your infrastructure must meet professional standards. This is the employee's responsibility.

Bandwidth: Minimum 50 Mbps Down / 10 Mbps Up. Video calls must be artifact-free.
Acoustics: A quiet, door-closable room. Background noise (dogs, traffic) during client or strategy calls is unprofessional.
Security:
- VPN: Always On.
- Screen: No working in public cafes where code/schematics are visible to passersby.

Enforcement & Exceptions

Revocation of Privilege

Remote work is a revocable privilege. It will be rescinded immediately if:

Ghosting: The employee is unreachable during Core Hours.
Blocking: A production stop (Line Down) is prolonged because the remote employee was "offline."
Quality: Code/Design quality drops due to lack of collaboration.

Exceptions (The "Golden Handcuff")

Exceptions to the On-Site/Hybrid tiers (e.g., a full-remote Hardware Architect) require CEO Approval and are reserved for niche experts whose skill set is otherwise unobtainable in the local market. These exceptions require a signed Service Level Agreement (SLA) defining specific travel frequency (e.g., fly-in for 1 week per month).

Final Checklist

Control Point	Requirement	Why?
Overlap Window	4 Hours continuous overlap with Factory Timezone.	To resolve blockers before the shift ends.
Response Time	< 15 Minutes during Overlap Window.	To prevent line stoppages.
Hardware	Strictly Prohibited at home.	ESD safety and IP security.
Hybrid Rhythm	3 Days On-Site for Tier 2 roles.	To maintain physical context (Gemba).
Escalation	Must answer Red Button calls 24/7 if critical.	Line Down events ignore timezones.
Status	Calendar/Slack status must always be accurate.	To avoid "Ghosting."