EN

03Scenarios

Menu
Back to Illustrative Deployment Scenarios

Scenario / Evaluation model

Illustrative deployment scenario

One-Way Data and File Release

An illustrative evaluation model in which approved reports, batch exports, and files are released one way from the Source Zone and made available as copies for subsequent workflows in the Destination Zone.

This content is only for identifying source, hardware-enforced one-way boundary, and destination conditions.

Buildings and treatment equipment at the Findlay, Ohio water treatment facility, illustrating a context for operational data and report sources.

Scenario context image; not a record of a product deployment.

Photo: Findlay, Ohio Water Treatment PlantAuthor: MbricknLicense: CC BY 4.0Source:Wikimedia Commons

Source → boundary → destination

Complete Data Path

  1. Source / Source Zone

    Source Zone systems and data

    Sources
    Report and batch-export jobs, Approved source file locations
    Data
    Operational reports and batch data, File content approved for release
  2. Hardware-enforced boundary

    Hardware-enforced one-way boundary

    Source Modulesource-to-destination one-way fiber data transferReceiving Module

    Within the listed hardware version, topology, and test scope, the Source Module receives files from approved source locations and sends them across the specified physical one-way link as source-to-destination one-way fiber data transfer; the Receiving Module then receives the files and provides file and destination-facing interfaces.

  3. Destination / Destination Zone

    Destination Zone systems and uses

    Destinations
    File-processing and analytics systems, Subsequent import workflows
    Use
    For the Destination Zone to obtain file copies created by the Receiving Module for analysis, retention, or approved subsequent import.

Evaluation inputs

Evaluation Considerations

  1. 01

    Define releasable source locations, file types, and approval workflows.

  2. 02

    Confirm file volume, update frequency, and acceptable loss conditions.

  3. 03

    Confirm destination naming, integrity-checking, retention, and import requirements.