1. Identify Which Side Handles the Power
Locate the requested power function in the product architecture. Ask the system owner whether the item receives power as a powered device, or controls power delivery on the sourcing-equipment side. Record that decision with the released controller code and board reference. An Ethernet connector or networking description is insufficient to identify which side of the power relationship the purchase line must serve.
Use the role names consistently in the enquiry. A powered-device requirement and a power-sourcing-equipment requirement should occupy separate lines when both occur in one programme. Keep their respective owners and design references visible. This prevents a supplier's broad PoE-controller response from being compared with an application role that it has not actually identified, particularly when a purchasing list combines several networking assemblies.
If the architecture includes several ports or boards, identify the specific function associated with this component. The owner should supply that relationship from released documentation rather than allowing procurement to infer it from a headline port description. A clear role record creates a useful first filter for candidates while leaving the detailed system requirement attached to the engineering team that maintains it.
2. Keep PD and PSE Examples Separate
TI identifies TPS2372 as a powered-device-side example. Its product description refers to a remote PSE, preserving the distinction between the receiving device and the equipment supplying power. Keep that role description with the named family. The sourcing use of this example is to identify which side is being discussed, rather than to assign every feature or historical standards statement to a customer's design.
TI describes TPS23881 as a PSE controller that inserts power onto Ethernet cables and detects powered devices. This is a different role from the TPS2372 example. Retain the separate family and role references in a candidate comparison. A shared PoE heading does not make the devices interchangeable purchase items, and an abbreviated controller description should be clarified before any technical ranking begins.
For a different proposed controller, locate its own manufacturer role description. Record it beside the required role and full ordering identity. Where a source names only a broad power-management category, mark the role unresolved and request the applicable document. This avoids importing a receiving or sourcing description from another family simply because a supplier has grouped the products under the same networking heading.
3. Separate Ethernet Data from PoE Power
Keep Ethernet data-interface selection on its own technical record. The PHY or MAC-side requirements describe the data connection, while this purchase decision identifies the PoE power function. A board may need both records, with different component codes and review evidence. The data-interface description should remain available without being used as a shortcut to the receiving or sourcing role required for the power controller.
When a BOM line says Ethernet IC, ask the component owner to resolve what item it actually refers to. It may need a more precise data or power description before suppliers can respond consistently. Preserve the existing internal material reference while the manufacturer identity is clarified. This is an item-definition task; it does not require guessing a network interface from an assembly's connector style.
Link the separate records through the board revision when that relationship matters. The system owner can then see whether a proposed power component belongs to the same released application as the data device. Maintaining that connection helps purchasing coordinate the enquiry without combining unrelated checks. An accepted MAC-interface record answers its own question and leaves the PoE role assessment with the appropriate power-system evidence.
4. Request the Exact Role and Pending Reviews
Prepare the role-specific enquiry with the full controller code, receiving or sourcing role, design reference and engineering disposition. List a proposed candidate under its own identity with any unresolved role questions. This gives the supplier a defined component to discuss and gives the system owner a focused exception to assess. Keep the confirmed purchase item visible while alternative roles or architectures are under consideration.
Detailed power requirements, applicable standards and finished-system assessment need their own accepted references. Retain them where the owner supplies them, without converting a historical product paragraph into a present certification result. A component role description can support the initial selection question while port behaviour and system interoperability remain separate matters for the responsible team. Each conclusion should retain the evidence appropriate to its scope.
For an ICULTRA sourcing request, send the permitted PoE controller code, quantity and destination, with the required role clearly stated. Add shareable manufacturer links and the owner's pending power questions as distinct entries. Keep data-interface enquiries separately identified. When engineering accepts a changed controller or application requirement, retain that decision before comparing the new device as the programme's confirmed component.
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.