1. Identify the Phototransistor Variant
Identify the phototransistor optocoupler actually required by the released design. Keep its complete manufacturer code with the BOM reference and any documented CTR selection. Ask the owner to resolve an abbreviated family description before candidates are compared. A shared package description does not explain which transfer-ratio entry applies, and an undocumented grade should not be completed from an informal product cross-reference.
Vishay's document 83615 lists IL211AT, IL212AT and IL213AT separately within the CTR table. Preserve the row identity when carrying information into an enquiry. The table provides a concrete reason to retain the variant instead of reducing the request to a generic optocoupler name. It is the exact row, together with its conditions and column classification, that forms the source basis for this comparison.
Connect that identity to the intended receiving stage. Ask which circuit reference defines the LED-side drive requirement and which identifies the phototransistor-side receiver. Keep the two references distinguishable. This makes the CTR discussion specific to the signal-transfer question while leaving package, isolation or other component requirements available for their own reviews when the design owner requires them.
2. Read the CTR Row Conditions
The CTR table on printed page three of document 83615 states input-current and collector-emitter-voltage test conditions. Record those conditions alongside the named parameter. A detached percentage removes the bias basis that the engineer needs to interpret the source. The comparison should therefore show the required drive context and the published test context as separate, readable entries.
The same table separates minimum and typical columns and leaves the maximum entry unfilled. Preserve that structure in the review. A typical entry cannot silently fulfil a requirement written against a minimum, and a blank maximum does not become a newly inferred limit. Ask the design owner which classification the receiver decision requires before a candidate is ranked by its headline CTR.
If the intended bias differs from the table condition, identify the mismatch. Keep the exact source row and the engineering question attached to it, so the reviewer can request appropriate additional evidence. Avoid borrowing a condition from another optocoupler or choosing the nearest familiar bias. This step establishes a disciplined basis for comparison without calculating an output-current allowance for an unidentified stage.
3. Preserve Temperature and Lifetime Questions
Temperature remains an explicit question in the requirement. Ask the circuit owner which operating context the receiver must cover and locate the relevant exact-device evidence. The ambient caption associated with typical-characteristic illustrations should not be transferred automatically to a table whose applicable temperature basis has not been established. Keep the source scope and any unresolved temperature applicability visible in the CTR record.
A useful exception entry distinguishes missing component evidence from missing application information. For example, the customer may have defined its operating envelope while the review still lacks an applicable limit, or the document may be available while the installation conditions remain unsettled. Those are different next actions. Name the owner of each question rather than assigning a broad incomplete label to the entire component.
Lifetime questions also require their own basis. Record any accepted programme requirement and the evidence engineering intends to use for it. One static CTR row does not supply an ageing loss allowance or a lifetime result for the assembled circuit. Keep such questions separate from the initial variant and bias comparison, allowing the design owner to decide which additional assessment applies to the intended product.
4. Keep the Receiver Review Explicit
Ask the receiver owner to state the signal-transfer requirement under the relevant load and operating conditions. Retain its existing design reference with the CTR comparison rather than treating a favourable percentage as a complete receiver decision. The component table describes source data; the receiving stage supplies the application requirement. Both are needed before engineering can determine what the candidate evidence establishes.
Organise the review around variant identity, required input drive, output-bias context, specification classification and unresolved temperature or lifetime evidence. Keep the engineer's disposition on each material row. If a candidate changes the CTR selection, record that difference explicitly. This allows procurement to distinguish a permitted purchase item from a component proposal still awaiting a receiver-level decision.
For an ICULTRA sourcing discussion, provide the exact optocoupler code, quantity and destination, together with the accepted CTR requirement and shareable supporting references. List pending bias or receiver questions separately. After engineering accepts a different device or grade, retain that change in the controlled requirement. Subsequent supply comparisons can then use the same defined variant without assuming that CTR alone approves the complete circuit.
Sources and further reading
Manufacturer documents support the technical guidance above. They do not confirm our stock, authorisation or the condition of any offered lot.