How to translate an electrical circuit diagram accurately requires more than knowing technical words in two languages. An electrical schematic communicates through component symbols, reference designators, wires, terminals, junctions, polarity marks, ratings, notes and document revisions. A diagram can appear neatly translated while describing the wrong connection, switch state or component rating. That is not a harmless language error.
If you need to translate a circuit diagram or electrical schematic into English or another language, keep electrical identifiers and network relationships stable while translating explanatory labels. First establish what kind of drawing you have and which symbol convention it uses. Then confirm component identities, connection points, units, warning language and the drawing’s issue status. A translated document should describe the same electrical design, not a plausible replacement.
This article focuses on electrical circuit-diagram translation and technical terminology. It does not teach a reader to build, repair, energize or certify a circuit, and a translation is not an engineering design approval. Electrical work can carry serious hazards. For equipment that affects safety or regulatory compliance, qualified professionals must verify the applicable drawings, instructions and local requirements before any practical work relies on the translated material.
Recognize the document before translating a label
A circuit schematic, wiring diagram, single-line diagram, block diagram, installation plan and printed-circuit-board layout do not communicate the same level of detail. A schematic emphasizes logical electrical connections and functional components. A wiring diagram may emphasize physical wire destinations, harnesses, connectors or terminal numbering. A single-line diagram can simplify a larger power system. Translation should preserve that distinction.
Begin with the title block, drawing number, revision, status and legend. An item marked “concept,” “for review,” “not for construction” or “superseded” must not emerge from translation sounding final and approved. The sheet may be part of a multi-page set, with wire or signal references leading to other drawings. If the translation separates it from those references, readers lose the context needed for safe interpretation.
Determine the intended audience. A trainee learning symbol names needs explanations different from a procurement reviewer checking component descriptions. A technical translator can preserve and clarify documentation, but should never assume that translation alone is sufficient for installation. The technical meaning of a line or symbol is established by the governing drawing convention and design documentation, not by the most familiar word in a dictionary.
Treat the drawing as a structured network of relationships
The electrical information in a schematic lives in relationships among components and connection points. Boxes and symbols may be moved on a page without changing the design, but changing which terminals are connected can change the design radically. Translation should therefore begin with a structural map: components, identifiers, terminal names, nets, references and notes.
A schematic may show a power source, a resistor, a switch and an indicator. Their visual proximity does not mean they are electrically connected. Only the drawing’s defined lines, connection dots, labels and connector rules establish that. Similarly, a long wire drawn across a page may simply clarify connection rather than represent physical wire length. Do not turn a schematic into an installation instruction unless the source actually provides one.
When creating a target-language version, compare the number of components and their designators. Trace connections using the original diagram or an authoritative netlist where available. If a line must be rerouted to make longer labels fit, its endpoints must remain unchanged. A translation that preserves every word but alters one junction is still unfaithful.
Read symbols with the legend and the applicable standard
Electrical drawing symbols are not arbitrary pictograms, but conventions differ by discipline, edition and regional practice. International sources such as the IEC 60617 database for graphical symbols can help qualified readers verify standardized symbol meanings. A project may also use legacy or company-specific symbols, so the actual drawing legend remains important.
Do not guess a component simply because its outline resembles a familiar symbol. A rectangle, circle, switch contact or triangle may represent different devices in different contexts. Read nearby component references, ratings, connection labels and notes. The current IEC resource is a maintained database, not a universal permission to overwrite the conventions of an older drawing.
Translating the explanatory name of a symbol is different from redrawing it. Unless authorized by an engineer and the project documentation, do not replace source symbols with a target region’s preferred alternatives. The reader needs a faithful representation of the issued design, followed by explanations where those symbols are unfamiliar.
Preserve reference designators and component identifiers
Circuit drawings often label components with reference designators such as R1, C2, U3, D4, J5 or K6. The specific prefixes and numbering conventions vary, but the identifiers link the schematic to a bill of materials, assembly drawing, test report or maintenance record. They are usually not ordinary words to translate.
A resistor labelled R12 should remain R12 even if the target language uses a different everyday word for resistor. Renaming it R21 because the numerals were transposed or because another item appears earlier on the page can break traceability. The same rule applies to connector identifiers, wire numbers, net labels, pin numbers and sheet references.
Maintain a separate glossary for the human-facing component description. For example, the identifier remains stable while “current-sense resistor” is translated into a clear approved term. If a manufacturer explicitly provides multilingual part names, use them with the exact part number. The role of translation is to make the description understandable without damaging the identifier that connects documents.
Separate component name, function and part number
A component may be called a relay, resistor, capacitor, fuse, diode, sensor, contactor or controller. These are category names. Its function in a circuit is another matter: protection, measurement, timing, isolation or switching may be described separately. A manufacturer part number identifies a specific product and should not be paraphrased as though it were a technical description.
For instance, a relay symbol does not automatically tell the translator whether the relay is used for safety shutdown, signalling or an ordinary switching function. That purpose requires supporting evidence. Likewise, a component called “filter capacitor” should not be relabelled “safety capacitor” merely because both terms contain capacitor.
Use the part list, notes and approved terminology to distinguish what a part is from what it does. Where a source phrase is ambiguous, preserve it and request confirmation. Technical fluency is not the freedom to infer functions from general electronics knowledge, especially when the diagram is used in troubleshooting or procurement.
Understand crossings, junctions and connection dots
One of the most consequential visual issues is whether intersecting lines are electrically connected. Different drafting conventions use dots, bridges, no-dot crossings or other symbols to distinguish connections. The translator must not assume that two lines crossing on the page form a junction.
Text expansion can tempt a designer to shift wires around labels. If two lines that previously crossed without connection now appear joined, the target diagram may communicate a different circuit. Conversely, removing a connection dot can make a genuine junction look unconnected. Preserve the source connectivity or have the redraw validated against an authoritative netlist.
An accessible written description should identify a connection using the actual component and terminal labels, not the mere visual crossing: “signal A is connected to terminal X of connector J2,” if the source supports it. Avoid descriptions such as “the upper wire touches the lower one” when the meaning depends on a formal junction convention.
Distinguish series, parallel and shared reference paths
Words such as series and parallel have precise technical meanings. Components in series share a path under the relevant network interpretation, while parallel branches connect across common nodes. A translated description that casually swaps the two can fundamentally change what readers believe the diagram shows.
However, diagrams can include complex networks where a quick visual statement about series or parallel is not straightforward. Do not label a group as “series” merely because symbols are drawn in a row. A branch, a test point or an internal device connection may change the interpretation. Use the source’s explicit notes or engineering verification.
The same caution applies to reference and return paths. A circuit ground symbol, chassis connection, protective earth and a local reference node are not interchangeable just because everyday speech calls each “ground.” The translator should preserve the exact label and symbol convention. Clarifying definitions belong with their verified source, not in improvised assumptions.
Keep polarity and terminal orientation exact
Some devices or circuits are sensitive to polarity. A schematic may mark positive and negative terminals, anode and cathode, or numbered connector pins. These distinctions must survive translation and any layout transformation. Swapping “+” and “−” or reversing a terminal description is not a stylistic error.
Technical writing also distinguishes input from output and source from load. These labels are context-dependent. An output of one device can connect to an input of another, and a bidirectional port may not fit a simple one-way explanation. Preserve the source label rather than imposing a universal direction on a terminal.
Right-to-left scripts create special layout challenges because symbols and numerals may display in mixed direction. Always inspect the rendered result for flipped signs, reversed ranges and displaced terminal labels. The underlying diagram must remain the same even if the accompanying text changes reading direction.
Understand switches and contact states in context
A diagram may use terms such as normally open, normally closed, energized, de-energized, actuated, reset, fault or trip. These terms describe states relative to a stated condition or convention. They are not casual synonyms for safe, on or off. Translating “normally closed” as “usually shut” without context may be insufficient or misleading.
The meaning of “normal” depends on the drawing convention and device description. A contact symbol may represent the device in a de-energized state, a process-normal state or another defined reference state. Read the legend or equipment documentation before describing a contact’s operation. Do not infer what will happen in a real machine from a cropped symbol alone.
For safety-related controls, uncertainty should trigger engineering review. If the source says “interlock contact” or “emergency-stop circuit,” preserve the terminology and warnings. A translator should not promise that a translated drawing proves a machine is safe or that a component will behave in a certain way under all conditions.
Translate units, magnitudes and electrical quantities carefully
Electrical schematics frequently contain units for voltage, current, resistance, capacitance, inductance, power, frequency and time. Their symbols and prefixes carry important magnitudes. Milliamperes, amperes, microfarads, nanofarads, kilohms and megohms are not interchangeable. A misplaced prefix can imply a thousand-fold or million-fold difference.
Keep values and unit symbols tied to their respective components or notes. Decimal separators may differ between languages, but electronic design identifiers and standardized units require careful treatment. Never translate a string like “4.7 kΩ” by dropping the k or altering the decimal meaning. Where a conversion is genuinely required, document it and verify against the authoritative design.
Tolerance and limits are also part of a rating. A value labelled “maximum,” “nominal,” “typical,” “minimum” or “not less than” carries different implications. The translator should not turn a nominal operating value into a required safety limit. The site-wide learning route on numbers, measurements and quantities in translation explains why small verbal changes around numbers can alter the underlying claim.
Distinguish alternating current and direct current labels
Labels such as AC and DC, input and output, line and neutral, phase and protective earth can be safety-relevant. Do not simplify them into a generic phrase for “electricity.” A symbol indicating a type of supply or measurement is not an optional decoration, and text direction should not swap the relationship between a supply label and its connection point.
In an educational description, it may help to explain that AC and DC name different electrical conditions. That explanation does not authorize readers to make assumptions about actual wiring, especially when the source drawing is incomplete. Equipment-specific instructions and professional verification remain necessary.
When a drawing includes test voltage, operating voltage, maximum rating and isolation rating, keep them separate. Their numbers may look similar but describe different conditions. A translated chart that collapses them into “voltage” hides the distinction a technical reviewer needs to understand.
Be precise with protective devices and safety warnings
Fuses, circuit breakers, protective relays and monitoring systems have different functions and requirements. The translation should not treat them as generic “safety switches.” If the source distinguishes overload protection from fault detection or isolation, preserve those terms rather than replacing them with a broad phrase.
Warnings such as “do not energize,” “isolate before service,” “for qualified personnel,” “hazardous voltage” and “refer to equipment instructions” express different instructions. Preserve negation, sequence, audience and condition. Do not soften a prohibition into advice or strengthen a conditional caution into an unsupported guarantee.
The existing eduKateSG article on safety pictograms and hazard symbols explores this issue for visual warnings. In electrical drawings, the same obligation extends to labels and technical conditions. A translation can be excellent linguistically yet unsuitable for safety-critical use until it has been checked by the right specialists.
Preserve connector pin numbers, wire IDs and net names
A connector symbol may show pin numbers, signal names and connector references. These are keys to other engineering records. The translator must not reorder pins to match the reading order of the target language. A left-to-right or right-to-left layout change does not justify changing pin 1 into pin 8 or swapping the names of signals.
Net labels can connect distant parts of a schematic without a drawn continuous wire. If two labels refer to the same net, changing one spelling may falsely separate a common connection. Case, punctuation and spacing may matter in electronic design files. Follow the project’s naming convention and protect tokens that are machine-matched.
If the source has an off-sheet connection reference such as a sheet number or coordinate, keep it accurate. A translated page that points to a non-existent cross-reference is hard to use and potentially misleading. Read a set of drawings as a connected document, not a pile of independent pictures.
Note the difference between schematics and physical layouts
A schematic describes electrical relationships; a physical layout shows where parts or connections are located. The same components can appear in very different positions. A translator should not describe a schematic line as the exact path of a real cable or infer physical proximity from the drawing alone.
Printed circuit board views introduce further terms: traces, pads, vias, layers, footprints and assembly references. These are not automatically equivalent to wires, terminals or parts. A translated maintenance instruction may need the physical board drawing as well as the schematic to identify a component safely.
If an image contains both logical and physical views, label the views separately and preserve their captions. Users may otherwise confuse a signal path with a cable route. That distinction belongs in the translation even when the source presents both views on the same page.
Handle industrial control and ladder-style diagrams without improvising
Some control diagrams use ladder-style representations, contact logic or function blocks. Their meaning depends on the relevant control-system notation and program conventions. A ladder diagram may be read differently from an ordinary picture of electrical wires. Translating the names of inputs and outputs does not provide proof of control-system behavior.
Keep instruction names, addresses, tag identifiers and state labels stable where they are technical tokens. A program tag may be referenced by automation software and equipment records. Changing its spelling because it resembles an English phrase could break that link or confuse a reader trying to compare two versions.
The appropriate target output may pair unchanged code or addresses with translated explanatory comments. Any reconfiguration, logic interpretation or validation belongs to qualified engineers using the correct project files. For readers interested in conditional structures as language, the separate guide on flowcharts and decision trees addresses if–then branches without treating them as electrical schematics.
Protect revision history and approval status
The title block may include a revision letter, date, author, checker and approval stage. These fields govern whether a drawing is current, preliminary or obsolete. A translation that omits them can make an outdated design appear usable, or make an unapproved draft look final.
Preserve the original drawing number and revision reference. If a translated edition receives its own document identifier, record the relationship to the source revision transparently. Do not substitute the day of translation for the engineering issue date as though the design had been updated that day.
When a corrected source drawing arrives, its content may differ from the earlier version. Do not silently merge revisions by translating labels from one version into symbols from another. Keep a clear source of truth and an audit trail of language changes. Translation should not conceal document-control events.
Work from a technical glossary with explicit evidence
Useful glossary entries include the source term, approved target term, component or document category, context note and reference. “Terminal,” “contact,” “lead,” “conductor,” “node,” “net,” “earth” and “ground” can have several senses. A simple word list without context will not resolve them reliably.
Check the manufacturer’s documentation and, where appropriate, recognized terminology sources. The International Electrotechnical Commission describes its Electropedia / International Electrotechnical Vocabulary as a technical terminology resource with multilingual equivalents. Terminology references help locate candidate meanings, but a specific drawing’s legend and design records decide which meaning applies there.
Keep source identifiers out of automatic substitution rules. A global search-and-replace may accidentally rewrite net names or device codes that happen to resemble common words. Test glossary changes on a copy, review unexpected matches and protect exact tokens before mass editing.
Translate diagram notes as instructions with scope
Many drawings contain notes applying to a whole sheet, a component group or one symbol only. A sentence such as “unless otherwise noted” changes how general rules apply. Do not delete it or move it away from the relevant text. Keep exceptions attached to the rules they modify.
Conditions expressed by if, only when, except, before, after, not and must carry operational meaning. An instruction to inspect a drawing before work is not equivalent to an instruction to inspect equipment after work. Translators should preserve the order and force of instructions without independently deciding what action is sensible.
Where notes refer to external specifications or standards, keep exact document identifiers and edition dates. A standard’s title can be translated for explanation, but a formal reference number should remain discoverable. The finished text should support a professional reviewer tracing the original requirement.
Accessibility does not excuse changing topology
A fully visual schematic may be difficult for readers who cannot inspect fine lines and symbols. A useful text description identifies the type of circuit, its major components, connection relationships and relevant notes at the level supported by the source. But translating the visible labels and writing a text alternative are distinct tasks with different quality checks.
The W3C guide to complex images recommends more than a short alt phrase for diagrams rich in information. A text-first description should describe key relationships and point to authoritative source materials, but should not claim to be a sufficient basis for working on equipment.
If an accessible explanation cannot represent every connection, say so. Do not replace a complete schematic with a simplified narrative and then present the narrative as equivalent engineering documentation. Accessibility requires meaningful access to information, including its limits, not the invention of an easier but technically different circuit.
Worked case: a crossing mistaken for a junction
Imagine two signal paths crossing at a right angle. The original drawing’s convention indicates that they do not connect. During text expansion, the new layout adds a dot at the crossing. The translated sheet now appears to join two signals that were separate in the source. Every component label might be correct, but the network is wrong.
A responsible reviewer compares connections against the source and, where available, the design netlist. The wrong junction is corrected before publication. The case illustrates why diagram translation needs structural checking in addition to bilingual proofreading. Electrical meaning can be carried by a single tiny graphic mark.
Worked case: a missing metric prefix
A source note specifies a 10 kΩ component. A target version displays “10 Ω” because the prefix was dropped in formatting. The component description remains grammatical but the stated resistance changes by a factor of one thousand. A translator cannot dismiss that as a minor typographical mistake.
Keep numerical tokens linked to their component identifiers and have the values reviewed independently. Where typographic characters such as Ω do not display reliably, use a verified equivalent notation instead of guessing. The values must remain readable at the intended display size.
Worked case: protective earth confused with circuit common
A diagram includes a protective-earth symbol and a separately labelled signal reference. The translation turns both labels into a single generic word for ground. That obscures a meaningful distinction, even if the document does not explain the full design details.
Check the symbol convention, legend and equipment documentation. Retain the original identifiers and translate each concept distinctly using approved technical terms. Do not conclude from visual similarity that two reference systems have the same protective function. A reader should be able to locate the exact original marks.
Worked case: normally open contact in an interlock
A drawing labels a contact “normally open.” An inexperienced translator treats “normal” as a promise that the equipment is safe in everyday operation. The result becomes a plain-language sentence about what happens when the machine is running, something the source may not establish.
Preserve the contact-state term and its reference condition where provided. If the operational meaning is needed, request engineering review. State labels are technical claims that depend on conventions and equipment behavior, not dictionary impressions. The translation should avoid adding a safety assurance that the source did not make.
Worked case: a connector appears mirrored
A wiring diagram shows an eight-pin connector with numbered positions. To accommodate a right-to-left layout, a designer mirrors the whole graphic. The connector now looks like a different physical view, and the pin numbers appear attached to opposite positions. The mistake can remain hidden until a professional compares the drawings.
Keep the verified connector orientation or explicitly identify the source view and revised presentation. Check the position of every pin label. A layout adjustment must never be allowed to imply a new connection. If the view needs to change, that is an engineering-drawing task requiring validation.
Worked case: a schematic copied from an obsolete revision
A manufacturer issues a corrected drawing after changing a component. A translation prepared from the older revision carries the prior part number and old warning notes, even though the words are translated accurately. It is inaccurate as current equipment documentation because the source edition is wrong.
Record revision numbers at intake and recheck them before release. Do not label an old translation as a current edition solely because it was translated recently. Where multiple versions coexist, make the status visible. Documentation provenance is part of technical meaning.
Worked case: an off-page reference disappears
A multi-sheet schematic sends a signal to another sheet through a labelled off-page connector. The translated picture keeps the signal name but drops the sheet reference because it looked like an unexplained code. A reviewer can no longer trace where that path continues.
Restore the exact cross-reference and verify its destination. External drawing references and document identifiers often look obscure precisely because they are compact machine-readable handles. They are not expendable language fragments. A faithful translated set must preserve its navigable connections between sheets.
Worked case: a relay name used as a device function
A box labelled “Relay K2” is translated as “Emergency Shutdown Relay K2” because it sits near a safety note. Nothing in the source says K2 has that function. The new label introduces a safety-critical claim. Even if the guess sounds plausible, it is not a translation of the issued drawing.
Translate the generic component name, preserve K2 and request an explicit function description if needed. Device purpose should come from the technical documentation. Proximity to a warning does not prove responsibility for the warned-against hazard.
Worked case: a bilingual educational circuit worksheet
An educational worksheet shows a simple symbolic circuit, asks students to identify components and includes questions about open and closed switches. Translation should preserve the labels, the problem’s given conditions and the distinction between a physical component and a symbolic representation.
A useful learning outcome is the ability to explain which information comes from the diagram and which conclusions require additional assumptions. Vocabulary becomes meaningful through diagrams and relationships. The exercise should stay within classroom explanation; it should not be rewritten as a practical wiring instruction or equipment maintenance guide.
Worked case: a sensor wiring legend with inconsistent abbreviations
A project uses a proprietary set of abbreviations for sensor inputs, supply references and shield connections. A translation system expands one abbreviation according to a general internet glossary and another according to a project note. The translated document then contains internally inconsistent names for related signals.
Use the project glossary and vendor documentation as the primary source. Preserve exact wire and net identifiers. If an acronym’s meaning is unresolved, do not invent a full phrase. The reviewer should be able to match every translated label to a unique source token and a documented definition.
Worked case: language length moves a caution note
A warning originally appears beside a particular power-supply block. In a longer target language, the note is moved to the bottom of the page without a clear callout. The words remain accurate but no longer visibly apply to that block; readers may interpret it as a general footnote.
Reflow notes while preserving their attachment to the relevant component or region. Use a stable note identifier or callout if the design supports one. Confirm with a professional reviewer that the final page does not create a new scope for the warning. Spatial association is part of technical documentation.
Worked case: an engineering report uses a simplified schematic
A research report contains a schematic simplified for conceptual explanation. The figure omits protection devices and physical wiring details and says “not an installation drawing.” If translation drops the qualifier, an inexperienced reader might regard the sketch as complete.
Preserve the scope statement clearly in the translated caption. Keep any note distinguishing conceptual arrangement from actual equipment documentation. Simplified educational diagrams are valuable, but their omissions must remain visible rather than being concealed behind a polished technical translation.
A practical verification sequence
Start by recording the drawing type, number, revision and purpose. Extract the title block, legend and notes. Catalogue identifiers and parts that must remain unchanged. Determine the symbol convention and obtain authoritative terminology from the project or manufacturer. Translate descriptions and warnings without changing codes or measurements.
Before publication, compare the target against the original for component count, reference designators, terminal numbers, polarity signs, units, wire/net labels, junctions, line connections, cross-sheet references, note scope and revision status. Use the underlying design data where available rather than relying on a visual impression.
Finally, submit the translated drawing to both a competent language reviewer and an appropriate technical reviewer. The translator checks clarity and linguistic equivalence; the technical reviewer verifies that the diagram still represents the issued design. Do not treat a clean bilingual proof as authorization to install, repair or energize equipment.
What learners can take from technical diagram translation
Technical English becomes easier when vocabulary is connected to a stable conceptual model. Component, connector, conductor, contact, terminal, node, reference, polarity, rating, tolerance and revision are not interchangeable words. Each points to a different kind of information in a technical document.
An effective learning task is to explain a source diagram in ordinary language, label which statements are direct observations and identify which require expert confirmation. This develops cross-linguistic transfer without encouraging unsupported inference. Students learn to carry precise concepts from one language into another while recognizing that some meanings are encoded visually.
For related eduKateSG explanations, see color-coded instructions and legends and tactile diagrams and spatial meaning. Those guides explore visual information. Electrical schematic translation adds the stronger requirement of preserving precise electrical connectivity and authoritative technical designations.
Frequently asked questions
Can a translation app read and translate a circuit diagram?
It may recognize visible text, but it cannot be trusted to preserve or validate every symbol, junction, reference and engineering meaning without review. Use it for candidate wording, not as a design approval. Qualified technical review is essential whenever a translated drawing affects equipment or safety.
Should I translate symbols in an electrical schematic?
Symbols are generally part of the drawing convention rather than ordinary text. Do not replace them with other symbols merely because the target language differs. Translate their explanatory labels where appropriate and check the legend and governing standard. Any symbol redrawing requires technical validation.
Can I translate R1, C1 and connector pin numbers?
Normally these are identifiers that must remain unchanged. They connect the diagram to parts lists, test records or wiring documents. Translate surrounding descriptions, not the reference codes, unless the engineering document owner explicitly authorizes a controlled renumbering.
What happens if lines cross in a schematic?
The connection meaning depends on the applicable drawing convention, junction dots and other marks. A visual crossing alone is not enough to conclude that two nets connect. Follow the source legend or seek technical review. Never add or remove a junction during a language-only edit.
Is “ground” always the same as protective earth?
No. Electrical reference, chassis and protective earthing concepts can differ. Preserve the exact source symbol and label, and use verified project terminology. Do not merge terms because colloquial language calls them all ground.
How should warning notes be translated?
Preserve the warning’s severity, negation, conditions, scope and ordering. Do not turn a prohibition into a suggestion. Keep the note attached to the correct drawing region and seek professional review when the wording concerns hazards or control-system behavior.
What if a circuit symbol is unfamiliar?
Check the legend, reference designator, nearby ratings, project documentation and applicable standards. Do not guess from shape alone. A translator should mark unresolved symbols for a technical reviewer rather than inventing a confident but unsupported component name.
Is a translated schematic safe to build from?
A translated schematic is not a substitute for approved drawings, equipment documentation, safety procedures, regulatory requirements or professional verification. Do not use a language-only translation as proof that an electrical installation or repair is safe. The responsible engineering process must determine whether the document is fit for practical use.
The central principle
A faithful electrical schematic translation carries the same technical relationships into another language: identical component identities, accurate connections, unchanged terminal references, exact quantities and equally forceful warnings. Words should become clearer, but the circuit must not become different. When uncertainty matters, preserve it and obtain the appropriate technical review rather than turning a guess into apparent engineering fact.