GLOBAL KNOWLEDGE ARK

Engineering & Technology · Sketches, Models & Technical Communication

Schematics, flow diagrams and system boundaries

A small teaching tank receives water through a valve and sends water to a collecting vessel through an outlet. A layout drawing could show where those items sit on a table. For a different question—where can water travel?—their connections matter more than the lengths or bends of the pipes.

Use units and simple arithmetic from Measurement, Units & Engineering Evidence. This chapter introduces its own coordinates, projections and model vocabulary; multiplication and division are enough for the worked cases. The geometry, system, data and results are original teaching constructions. They are not observed experiments, build specifications or operating instructions. No conformance to a drafting, piping or NASA standard is claimed.

Back to the chapter

After reading, you can

Choose a diagram that makes connections, flow or sequence explicit, and state what crosses a chosen system boundary.

01

Choose the relationship before choosing the picture

A schematic uses symbols and connections to describe selected relationships. It may move components on the page to make those relationships easier to follow. In our water schematic, a line means a connected water path and an arrow marks the direction considered in the example. The line is not a measured pipe length. Bending it on the page does not add a physical bend to the design.

An electrical schematic similarly describes electrical relationships rather than the physical placement of every wire. A wiring layout, by contrast, may need to show terminals and routing. Read the legend and conventions of the actual diagram: identical-looking crossings or arrows can mean different things in different systems. Our water symbols are explained beside the figure and make no claim to a specialised piping standard.

02

Ask what belongs inside the question

The dashed boundary encloses the tank alone. Water enters from the valve and leaves through the outlet. A dotted arrow carries level information to a reader outside the boundary; it is not another water path. These different line styles separate material movement from information, even without colour.

If the question becomes how the valve setting affects filling, we might draw a larger boundary around valve and tank together. The valve then becomes internal, while the upstream supply becomes an input. Moving a boundary changes the bookkeeping and responsibilities being considered; it does not physically move a component. Inputs, outputs and stored contents will matter when we model filling.

Water connectivity and a paper calculation loopAn original water-path schematic shows supply, valve, tank and outlet, with the tank-only boundary and a dotted information path. A paper simulation loop advances time and recomputes volume before repeating its target comparison.Connections and sequence answer different questionsSchematic: connectivity, not physical layoutTank-only boundarySupplyValveTankwater outCollecting vessellevel information → readerPaper simulation: a repeated decisionStart VV ≥ target?yesStopnoAdvance timeUpdate volumeSolid blue: water ··· Dotted violet: information - - Boundary
Water path: supply → valve → tank → collecting vessel. A dashed rectangle encloses the tank only. A dotted information line goes from the tank to an external reader. The paper simulation starts with V and compares V with the target. If V is at least the target, stop. Otherwise advance one time interval, update V using the chosen filling rule, and repeat the comparison. The water schematic has no pipe-length scale, and the process is not a physical controller specification.
03

Use a process diagram for what happens next

The second panel is a process diagram for a paper simulation, not equipment operating instructions. Begin with a simulated volume, compare it with a target, and either stop or advance by one time interval, update the volume using the chosen filling rule, and compare again. The decision branches carry conditions. Without the volume update the loop would keep checking the old value; without its return arrow a reader could think the comparison occurs only once.

A diagram should also show the limits of the question. This simple loop omits overflow protection, instrument failure and real valve delays. It explains repeated calculation only. Another diagram would be required to analyse a physical controller’s possible states and faults. Completeness is always completeness for a stated purpose, not a promise that a few boxes describe everything.

Repair a misleading water diagram

A first sketch places the valve near the tank but does not connect them. A reader cannot tell whether it is part of the supply, part of the outlet or simply nearby. Add an explicit supply → valve → tank connection and a tank → collecting vessel outlet.

Next label the boundary “tank only”. Identify incoming water, outgoing water and the tank’s stored contents. Draw the level-reading connection with a dotted line and label it “information”. No pipe length can now be inferred from the spacing between the symbols.

For the paper calculation, label the two branches “volume at least target” and “volume below target”. The first leads to stop; the second advances time, recomputes the volume using the chosen filling rule, and returns to the comparison. This closes the logical gap without adding irrelevant physical detail.

Try the reasoning

  1. If two components are moved farther apart on a schematic, must the connecting pipe become longer?

    Show the answer and reasoning

    No. The schematic records the connection. A layout drawing and dimensions are needed to establish physical distance and routing.

  2. What crosses the tank-only boundary in this figure?

    Show the answer and reasoning

    Incoming water, outgoing water and the outward level information. The valve and reader are outside; the tank’s stored water is inside.

  3. Why label both branches of the process decision?

    Show the answer and reasoning

    The labels tell the reader which condition selects each path. An unlabelled fork does not define what the process should do next.

What to carry forward

A useful diagram states what its lines mean, which relationship it represents and where its question begins and ends.

References

Teaching resources and research supporting this lesson’s explanations and examples.

  1. Systems diagramming — sections 2.1–2.3 and 3.7–3.8The Open UniversityTeaching resourceopen.eduRead source