3.1 · From MIL-L-85762A to MIL-STD-3009

Chapter 3 · Page 2 of 8

3.2 · Interface criteria and system design

The foreword to MIL-STD-3009 helps explain what changed. It says that the Class A and Class B technical criteria were retained, while lighting-system design requirements were removed from this interface standard. It also discusses Class C and exterior lighting. We’ll look more closely at those classifications in Chapter Four. For now, think about what this means when you’re developing a display.

A statement such as “meets MIL-STD-3009” needs more detail before we can use it to make an engineering decision. Which requirements apply? Under what operating conditions? With which receiver configuration? And what about everything else the display has to do? The equipment program still needs to define daylight readability, useful night brightness, dimming behavior, operating modes, controls, and what happens during transitions or faults.

Your organization may own only some of those requirements. The standard contains interface, performance, and integration requirements, but it doesn’t replace the complete requirements for the equipment and installation. So we use the applicable standard requirements together with the program’s tailored requirements, and identify the part of that work that belongs to us.

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 3 of 8

3.2a · Our role may cover only part of the system

Our role is often just one part of this work. We might produce the NVIS filter material or filtered backlight rails. We might supply a display module, or enhance an existing module with anti-reflection glass, EMI shielding and optical bonding. We may not know exactly where that product will be installed, every light source around it, or all the conditions it will encounter.

Sometimes we only receive a drawing, a component specification, or a set of performance targets. Even with that limited view, understanding the larger system helps us in our own product and process development. It helps us choose materials, decide what to measure, recognize potential leakage paths, and understand how a change in our part could affect the next assembly.

For example, when we’re developing an IR-cut filter, understanding the source spectrum and the receiver response helps us ask better questions about the transmission curve we need. If a customer invokes Type II, Class B, we need to establish how that requirement applies to our deliverable. A filter curve can support the design without proving that the complete display or installation meets the requirement.

That’s why we’re looking at the whole system in this course. We can use that understanding within our own scope, recognize what we don’t yet know, and provide useful information to the next person in the chain.

Apply this within your role

Record your deliverable, the requirement you own, the measurements you can provide, and any installation information you still need. Keep assumptions separate from confirmed customer inputs.

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 4 of 8

3.2b · NVIS and environmental qualification

For avionics and other aerospace equipment, NVIS compatibility is one part of the requirements picture. Two other documents you’re likely to encounter are MIL-STD-810 and RTCA DO-160. MIL-STD-810 deals with environmental engineering and laboratory test methods. It helps a program select and tailor tests to the conditions the equipment will encounter during its service life.

That may include temperature, humidity, shock and vibration. A statement such as “tested to MIL-STD-810” needs the revision, method, procedure, test levels, duration, configuration and acceptance criteria behind it. RTCA DO-160 addresses environmental conditions and test procedures for airborne equipment. Depending on the installation, applicable sections can include temperature and altitude, vibration, power input, radio-frequency susceptibility and emissions, and lightning-induced transients.

The revision, applicable sections and categories need to be identified for that equipment. We don’t assume every category applies to every installation. Neither document, by itself, demonstrates NVIS compatibility or completes aircraft certification. We need the applicable optical requirements and environmental requirements to work together. For our display, that means deciding what has to remain acceptable during and after the specified exposures.

We may need to check brightness, color, spectral leakage, dimming behavior and optical-bond condition. Which checks occur during a test, afterward, or both comes from the agreed test plan. And if we supply only a filter or a backlight rail, we need to understand which part of that evidence belongs to us. Component evidence supports the next assembly; it does not automatically qualify the finished display.

The linked FPD.DEV DO-160 course goes further into display qualification. Here, we’re establishing how these requirements fit together.

Qualification planning table

FPD.DEV DO-160 display qualification course · FPD.DEV aircraft display testing guide · DLA MIL-STD-810 record · RTCA DO-160 · FAA AC 21-16G

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 5 of 8

3.2c · Low brightness in a hot environment

NVIS operation usually means night use, with display luminance turned down to an appropriate level. But low brightness does not necessarily mean a cool operating environment. Think about a display in a hot ship’s cargo space or near an engine room. Even if we reduce the backlight’s electrical power, the surrounding air, nearby hot equipment and limited airflow can keep the display assembly hot.

Those are examples of demanding environments, not a claim that every cargo hold is hot. Dimming often reduces heat generated by the backlight. It does not remove heat coming from the environment, and the rest of the electronics may still dissipate power. The LED junction and optical stack can therefore operate well above the temperature of a comfortable laboratory. That matters to our optical design.

LED output and spectrum, filter transmission, LCD behavior and dimming stability can change with temperature. Coatings, adhesives and bonds also have operating limits. We need evidence for the actual materials and assembly, rather than assuming the room-temperature result carries over. For our test plan, separate the ambient environment from the equipment’s operating mode.

Identify the required temperature, cooling and mounting conditions, then identify the display settings and optical measurements needed under those conditions. Where required, check spectral leakage, usable luminance and dimming behavior at the hot operating condition and after the exposure. DO-160 is written for airborne equipment. A shipboard program needs its own invoked requirements; MIL-STD-810 may be part of that basis if the program calls for it.

Neither a shipboard location nor the word NVIS automatically selects the environmental test standard. The point for us is simple: a dim display can still be a hot display, and its optical performance must be evaluated in the conditions that matter to its intended use.

Exercise: separate environment from operating mode

For a dim display in a hot space, list ambient temperature, mounting and cooling conditions separately from luminance setting, electrical load and optical measurements. Identify which properties must be measured during exposure and which after exposure. Do not substitute the ambient temperature for LED junction temperature.

FPD.DEV DO-160 display qualification course · FPD.DEV aircraft display testing guide · DLA MIL-STD-810 record · RTCA DO-160 · FAA AC 21-16G

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 6 of 8

3.3 · Reading the complete requirement

Let’s look at how to read a requirement without losing its context. It’s tempting to find a table, pick out a number, and use that as the pass-or-fail limit. But that number belongs to a larger set of instructions. We need the classification, the applicable equipment paragraph, the table row, the measurement method, and any response data used in the calculation. Keep the footnotes with the table.

An exception or a specified test condition can change how a limit applies. The document history matters, too. Our retained reference set includes the base documents and later notices, including validation notices. A document’s catalog status, its supersession history, and the edition invoked by a project tell us different things. Before using a document for a real acceptance decision, check the applicable edition and notices against the project’s requirements.

Don’t assume that an older document number is automatically invalid—or that a newer document automatically replaces what the project has invoked. In the next chapter, we’ll work through the classification terms. Later, Chapter Nine develops the weighted-radiance calculation, and Chapter Twenty-One brings the measurement evidence together. For this chapter, the key is to keep the requirement and its supporting information connected.

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 7 of 8

3.4 · Translate a legacy drawing

Let’s work through a situation you might encounter. You’re reviewing an existing display. The drawing says MIL-L-85762A. The new purchase request says MIL-STD-3009. The supplier has provided a report against the earlier specification. What would you check before accepting that report? Pause here and make a short list. Start with the editions and notices identified by the drawing, purchase request, and report.

Then check the equipment category and the intended night vision receiver configuration. Next, compare the relevant requirements and measurement methods. Include the table footnotes and test conditions. Look for differences that could affect the result. Finally, record the agreed requirement basis and have any conflict resolved through the project’s approval process. The foreword explains the relationship between the documents.

It can help you understand the history, but it doesn’t resolve a conflict between your drawing and purchase specification. That resolution needs to be clear in the project records.

Original specification excerpts

Unaltered excerpts from MIL-L-85762A page 1 and MIL-STD-3009 cover and foreword page ii. Read them in the full source documents linked below.

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references

Chapter 3 · Page 8 of 8

3.5 · Build a requirement trace

Now let’s turn that into something useful for your own work. Choose one requirement within your scope and build a trace from the requirement to the evidence. For a display-level NVIS requirement, start with the intended classification and equipment category. Find the applicable paragraph and table row. Then identify the measurement method and any numerical response data needed to evaluate the result.

For a material or component requirement, start with the customer’s agreed specification and identify how your evidence supports the next assembly. Record any system-level assumptions that were supplied, and identify relevant information that is still unknown. Carry the test conditions with you: luminance where applicable, units, operating mode, and any exceptions or qualifications.

You can begin with a simple table: What is required? Where does it come from? How will we evaluate it? And where will we record the result? The goal is for another engineer to follow your reasoning without having to guess which limit you selected or why it applies. That trace also helps you see what’s missing before you spend time testing the wrong configuration.

Worked applications for this chapter

Translate a legacy drawing

A legacy drawing says MIL-L-85762A, while a new purchase request says MIL-STD-3009. Do not silently replace one citation with the other. Identify the invoked editions and notices, the equipment category and the receiver configuration. Map the relevant requirement and method references, including footnotes. Record what the program accepts as the applicable basis. The 3009 foreword helps explain the lineage, but it does not resolve a particular contractual inconsistency by itself.

Build a requirement trace

For a display requirement, trace classification to the applicable equipment paragraph and table row. Continue to the measurement method and numerical response data. Carry the luminance condition, units and exceptions through the whole chain. Then attach the program requirements for modes, controls, daylight readability and fault behavior. A report should allow another engineer to follow that chain without guessing which row supplied the limit. Chapter 4 works through the classifications and original tables.

Continue your learning: Chapter 4 — Types classes colors and the requirement boundary · Chapter 9 — Measuring NVIS weighted radiance · Chapter 21 — A practical measurement and verification program.

Check your trace

A useful row identifies the requirement source and revision, your exact deliverable and configuration, the agreed conditions and method, the acceptance criterion, and the report or record containing the result. A material transmission curve alone cannot establish complete-display or installation compatibility.

References: MIL-STD-3009 and MIL-L-85762A source documents · Course references