Apter Power · Mid-Autumn Festival 2026 Dice, Laughter and One Full Moon A joyful Bobing celebration of reunion, teamwork and shared success The Mid-Autumn Festival is a season of reunion, gratitude and shared happiness. On September 18, 2026, the Apter Power team gathered for a lively Bobing celebration, filling the office with the sound of rolling dice, cheerful applause and good-natured suspense. For one joyful afternoon, colleagues stepped away from their usual schedules to share a tradition that brings people together. The result was more than a festive activity—it was a vivid expression of the energy, trust and teamwork that shape our company every day. Prizes prepared with care—turning every roll into a moment of anticipation. A Table Full of Good Wishes Before the first roll, a colourful selection of prizes set the scene. Practical gifts, festive surprises and a golden trophy turned an ordinary office table into a celebration of appreciation. Every prize carried the same message: effort is seen, contribution matters and success is best when it is shared. What Is Bobing? Bobing is a lively Mid-Autumn tradition popular in Southern Fujian. Six dice are rolled into a red bowl, and different combinations correspond to different prize levels. The rules create suspense, but the real attraction is the shared experience—the anticipation before each roll, the cheers that follow and the memories created around the table. When the Dice Roll, Team Spirit Rises The most memorable part of the celebration was not a single winning roll. It was the atmosphere around the bowl: colleagues laughing together, watching closely, comparing results and cheering for one another. Every round brought a new surprise, and every smile made the team feel closer. The scene also reflected qualities that matter in our daily work: attention, quick response, clear communication and mutual support. Strong results begin with people who listen and move together. Laughter around the red bowl—the strongest prize was the joy shared by the team. Six dice, one red bowl and countless good wishes for the journey ahead. A Little Luck, A Lot of Heart A red bowl, six dice and a festive envelope captured the spirit of the day. Bobing may involve luck, but a strong team is built through consistent care, shared responsibility and the courage to meet challenges together. Every enquiry answered, part number checked, package prepared and customer deadline supported is one more roll toward a shared goal. From Celebration to Service Listen carefully Understand the exact model, configuration and application requirement. Respond quickly Support urgent maintenance needs and time-sensitive projects. Work as one team Coordinate sourcing, inspection, processing and worldwide delivery. Share success Help customers keep critical automation systems reliable and moving. Apter Power supplies automation and control equipment across DCS, PLC, CNC, HMI, drives, servo systems and power supplies, with particular experience in legacy, discontinued and hard-to-find spare parts. Behind that catalogue is a team that values both technical accuracy and human connection. Recommended Models Looking for one of these industrial components? Select a model to send the exact part number to our team for availability and product-detail confirmation. No. Brand Model Details 1 EVOGUARD H1CP 180/35 D130 FN100100 Request Details 2 Siemens 1PH8107-1DF02-0CE1 Request Details 3 Festo DGPL-63-1150PPVA-GFB Request Details 4 Siemens 2KJ3507-5EM23-4CS1-Z Request Details 5 ABB ACS600 ACN63401853 00000000902 Request Details 6 Siemens 1PH7133-2ND02-0BJ0 Request Details 7 Siemens 1PH7133-2ND02-0LJ0 Request Details 8 Biral EBZ 87V/4-225 Request Details 9 Becker SVw 190/1-485 Request Details 10 Nabtesco RV-320E-141 P65E021K00 Request Details 11 Siemens 2KJ3105-1GH22-9AN1-Z Request Details 12 Siemens 2KJ3990-0RU Request Details 13 — VK451011-ED621002/BU ED621002 Request Details 14 — PDRV2_R002K20 Request Details 15 S+S 960877/001 GTXB.118x90.DA.NP22D.F07/F10.100 Request Details 16 Siemens 1PH6137-4NZ00-Z Request Details 17 SEW R87 SDV112M8/2/BMG/HF Request Details 18 Lenze MCA19S35-SRMP5 Request Details 19 Lenze MCA 21X42-RS0P1-Z0H0-ST6S00N-R0SU Request Details 20 Yaskawa CIMR-AC4A0058AAA-0121 Request Details One Moon, Many Connections Mid-Autumn reminds us that people can remain connected even when they are far apart. That message is especially meaningful to a team serving customers and partners around the world. We are grateful to every colleague who brings care and energy to the workplace, and to every customer and partner who places trust in Apter Power. Your challenges inspire us to improve; your cooperation turns difficult requirements into practical solutions. Happy Mid-Autumn Festival As the full moon lights the way forward, may it bring harmony to every family, strength to every team and steady progress to every project. From all of us at Apter Power, we wish our customers, partners, friends and colleagues a joyful Mid-Autumn Festival. One moon connects us. One team moves us forward. Tel: +86 18030235313 Email: sales13@apterpower.com About Us Contact Privacy Policy Warranty Policy Payment Options Cookie Policy Our Team Services Part Conditions Case Studies Copyright Notice © 2026 ApterPower.com. All rights reserved. Apter Power is not an authorized distributor or representative of the manufacturers featured on this website. Brand names and trademarks featured are the property of their respective owners.

Replacing a Bently Nevada 3500/53 133388-01 requires more than fitting a spare that powers up. Before return to service, the asset owner needs documented evidence that the correct front module and associated I/O are installed, the approved configuration is restored, voting and bypass states match the controlled design, and the required trip path passes the site's proof test. Turbine protection engineers, outage planners, and MRO buyers should define those records before requesting a quote. We can document the offered hardware and supplier-side checks, while installation and safety-function approval remain with the authorized site team. Where Does the 3500/53 Fit in an Overspeed Protection System? The 3500/53 is not a general-purpose speed display. Baker Hughes describes it as a fast-response, redundant tachometer system intended specifically for use in overspeed protection. Modules can be combined in two-out-of-two or two-out-of-three voting arrangements; the OEM application guide recommends two-out-of-three for the application it describes and states that the system requires a 3500 rack with redundant power supplies. It also distinguishes the overspeed detector as protection for the driver rather than the driven machine. See the OEM centrifugal compressor application guide . That context changes the replacement question. A matching front-module number is only one part of the protection chain: Speed sensors and their field wiring provide the input signals. The installed 3500/53 channels process those signals against the approved configuration. The site's voting arrangement determines how channel states contribute to a trip demand. Relay, shutdown, or emergency-shutdown interfaces pass the demand onward. Final elements act according to the plant's approved protection design. A spare can be genuine, functional on a bench, and still be unsuitable for a specific installation if its identity, revision, associated I/O, configuration basis, or approval requirements do not match the controlled design record. There is also an important lifecycle boundary. Baker Hughes states that the 3500/53 is included in its application guidance to support the existing installed base and is no longer available for new installations; it directs future Bently Nevada overspeed and emergency-shutdown applications toward the 3701/55 ADAPT ESD. The scope here is maintenance of an installed 3500/53 system, not specification of 133388-01 for a new protection architecture. What Must Be Captured Before Removing 133388-01? Build an as-found record before any component is disturbed. The record should let a second qualified engineer reconstruct what was installed, how it was configured, which protective paths were available or bypassed, and what evidence was used to approve the work. At minimum, capture the following: Evidence to capture What to record Why it matters Front module identity Full faceplate and side-label photos, part number, assembly/revision information, serial number, slot Connects the installed unit to the work order and replacement decision Associated I/O Full rear I/O label, termination style, connector positions, wiring identifiers Prevents a front-card-only comparison from hiding an I/O or termination mismatch Rack baseline Rack type, power-supply arrangement, relevant interface modules, adjacent protection modules Establishes the actual system environment rather than an assumed catalog configuration Configuration record Controlled backup/export, channel settings, alarm/trip setpoints, configuration checksum or revision record where available Provides the approved reference for restoration and comparison Protection state Voting arrangement, active bypasses, inhibits, channel defeat states, maintenance overrides Shows what protection remains available during the work External interfaces Relay or shutdown path references, ESD/DCS interface drawings, annunciation points Defines the downstream functions that the post-installation test must address Operating evidence Relevant alarms, system events, fault codes, and time-stamped as-found observations Helps distinguish a failed module from a sensor, wiring, configuration, or system-level problem Governance Approved work order, risk assessment, management-of-change record, responsible approvers Makes the change traceable and establishes stop-work authority The current 3500 System Datasheet explains that 3500 modules use associated I/O modules, store configuration in non-volatile memory, and record configuration changes in the system event list. Those capabilities are useful evidence sources, but they do not replace the site's controlled backup, drawings, or approval record. Document Voting, Bypass, and Trip Interfaces Do not reduce the as-found state to “two-of-three” or “two-of-two.” Record how the installed channels, bypasses, and outputs actually interact in the approved site design. The pre-removal package should answer these questions: Which modules and sensor channels participate in the overspeed vote? Is any channel already bypassed, inhibited, faulted, or under maintenance? What protection remains while one module is removed? Which contacts or downstream interfaces carry the trip demand? Which alarms indicate a channel fault, bypass, or loss of protection? Who has authority to apply and remove each bypass? What independent safeguards or operating restrictions are required during the impairment? What constitutes a failed restoration, and who can stop return to service? These are documentation and approval questions, not instructions to change the voting logic. If the current state does not agree with the approved cause-and-effect, logic narrative, or trip drawing, stop and resolve that discrepancy before using the maintenance window to introduce another change. Confirm the Module, I/O, and Firmware Revision Treat “3500/53 133388-01” as the beginning of identification, not the entire identity. The current Baker Hughes 3500 manuals index identifies document 134939 for the 3500/53 Overspeed Detection System. Use the revision of that manual applicable to the installed system, together with the site's approved records, to verify the required front module, associated I/O, firmware, software tools, approvals, and rack prerequisites. Use a two-sided comparison before releasing the spare: Installed side Proposed spare side Full part and assembly identifiers Full part and assembly identifiers Hardware revision Hardware revision Firmware version or controlled firmware requirement Installed firmware and evidence of version Rear I/O part number and termination arrangement Required I/O pairing and compatibility basis Agency or hazardous-area requirements Markings and documentation supplied for the quoted unit Approved configuration baseline Method and authority for loading or verifying that baseline Do not infer compatibility from a reseller title, a similar faceplate, or a shortened “3500/53 module” description. Preserve suffixes and revision details in the RFQ and purchase order. Where the OEM record and the physical labels do not agree, keep the item on engineering hold . Which Safety Reviews Are Required Before Replacement? A controlled replacement should pass four reviews before field work begins. The names of the reviews may differ by site, but the decisions should be explicit. Review gate Minimum decision Typical owner Release evidence Protection impairment review The plant can manage the period in which the channel or vote is unavailable Operations and turbine protection Approved impairment plan, bypass register, operating restrictions Change-control review The spare and planned configuration are within the approved design basis, or the change has been formally assessed Functional-safety or controls authority MOC/work-order approval and design references Work execution review Isolation, electrostatic-discharge controls, access, tools, and responsibilities are defined Maintenance supervisor Permit, job plan, toolbox review Restoration review Test scope, acceptance criteria, witnesses, records, and rollback action are agreed before installation Asset owner/authorized engineer Approved proof-test package and sign-off sheet The review must distinguish a like-for-like maintenance action from a design change. A new revision, different I/O arrangement, altered firmware, changed trip setpoint, or revised voting philosophy may trigger additional engineering and functional-safety review even if the front panel fits the same rack slot. Do not use a general certification claim as a shortcut. Baker Hughes' published TÜV notice says certification applies to specific 3500/53 configurations and that SIL determination depends on assessment of the system and application. It does not make every loose 133388-01 module, every rack configuration, or every field replacement automatically “SIL 3.” Review the Bently Nevada functional-safety notice and the safety documentation applicable to the installed configuration. How Should the Spare Be Bench-Checked? The bench check should answer a limited question: is the received unit correctly identified, physically acceptable, and capable of completing the supplier's or site's defined pre-installation checks? It cannot validate the complete field protection function. Use a serial-number-linked incoming inspection record: Compare the delivered label, assembly number, revision, and serial number with the purchase order and approved compatibility record. Photograph the actual unit from enough angles to show labels, connectors, card edges, extraction hardware, and visible condition. Inspect for contamination, corrosion, impact damage, bent or damaged connectors, broken fasteners, unauthorized markings, or evidence of poor handling. Verify the declared condition, such as new, surplus, or repaired, and record any packaging, preservation, or repair documentation supplied. Review the test report for the exact checks performed, equipment or fixture identification where provided, test date, result, and the serial number of the unit tested. If site-approved facilities and procedures allow a power-up or self-test, record the setup and observed status without extending the result beyond that test's scope. Quarantine the unit if the labels, physical condition, documentation, or test identity do not agree. The wording of the acceptance record matters. “Powered on” means only that the unit powered in the stated setup. “Self-test passed” means only that the documented self-test completed. Neither statement proves correct sensor response, approved trip setpoints, voting behavior, downstream relay operation, final-element action, or suitability for the installed safety function. This evidence boundary should also appear in the supplier's quotation. A vague “fully tested” claim is less useful than a traceable report that states exactly what was and was not tested. What Does a Valid Post-Installation Proof Test Include? A valid proof test is based on the asset owner's approved procedure and the installed system's safety requirements. The test stimulus, numerical values, expected time response, voting sequence, final-element scope, and acceptance criteria cannot be set by a generic blog or a parts supplier. For planning purposes, the proof-test package should show how each of the following layers will be verified: Test layer Question the approved procedure must answer Evidence to retain As-left hardware Is the approved module in the correct slot with the correct associated I/O and secure connections? Label photos, installation inspection, torque/connection records where required by site procedure Configuration Does the as-left configuration match the approved baseline, including channel parameters and setpoints? Configuration comparison, revision/checksum record, authorized sign-off Sensor input path Does each required channel receive and interpret the approved test stimulus correctly? Calibrated test-equipment record, channel results, observed values/status Channel diagnostics Are normal, fault, and applicable diagnostic states detected and annunciated as expected? Alarm/status record and exception log Voting and bypass behavior Does each approved test case produce the expected vote while bypasses and inhibits behave as documented? Step-by-step result sheet tied to the cause-and-effect or logic record Trip output path Do the designated relays or ESD interfaces change state as required? Contact/interface observations and time-stamped event evidence Final element, if in scope Does the shutdown device perform the required action under the approved test arrangement? Witnessed functional-test result or documented reason for a separately scheduled test Restoration Are all test forces, jumpers, bypasses, inhibits, and temporary wiring removed, with protection returned to its approved state? Independent check, bypass-register closure, final alarm/event review Plan the proof test before the outage, not after the replacement has been fitted. Predefine who applies the stimulus, who observes each interface, who can accept deviations, and what happens if one layer fails. A front-panel healthy indication should never be the sole return-to-service criterion. The final record should make failures visible. Do not convert an open issue into a pass by writing “functionally equivalent,” “as expected,” or “tested OK” without the underlying observations. Record actual results, deviations, corrective actions, retests, witnesses, date/time, and the approved as-left state. What Should Procurement Ask the Supplier to Prove? Procurement can reduce both schedule risk and technical ambiguity by asking for evidence that a supplier can reasonably control. It should not ask the supplier to certify site-specific compatibility or the completed safety function. Ask the supplier to document Keep with the asset owner Exact quoted part number and all visible suffixes Approval of the installed configuration Actual-unit label and condition photos Correct trip setpoints and voting philosophy Serial number and hardware/revision details available from the unit Compatibility with the site's exact rack, I/O, firmware, and design basis Declared condition and repair history if applicable Management of change and protection-impairment controls Test scope, result, date, and link between the report and serial number Field proof test of sensors, module processing, outputs, and final elements Included accessories or I/O, stated line by line SIL claim for the complete installed safety function Warranty and return terms in the quotation Authorization to return the turbine or driver to service Current availability, dispatch basis, shipping terms, and export documents Site acceptance and final sign-off For an efficient RFQ, send Apter Power: “ 3500/53 133388-01 ” exactly as shown on the requirement, without dropping the suffix. Clear photos of the installed front module, side label, and associated rear I/O label. Hardware and firmware details available from the site's controlled records. Rack and slot information, required approvals, quantity, preferred condition, destination country, and required-on-site date. The evidence package you require before shipment, such as actual-unit photos or a serial-linked test record. Apter Power can then prepare a documented quotation based on the identified requirement and current sourcing position. Availability, condition, lead time, warranty, and included documentation should be confirmed in that quotation rather than assumed from a catalog image or an undated web listing. Browse the Apter Power Bently Nevada catalog or send the complete requirement to our team . Return-to-Service Decision for 133388-01 A controlled 3500/53 133388-01 replacement has three separate acceptance decisions: Hardware acceptance : the received module, revision, associated I/O, condition, and documentation match the approved requirement. Configuration acceptance : the installed module is verified against the site's controlled baseline, with voting, bypasses, and interfaces correctly restored. Safety-function acceptance : the approved post-installation proof test demonstrates the required sensor-to-output behavior, or sensor-to-final-element behavior where specified, and leaves an auditable record. None of these decisions can substitute for the others. Supplier evidence can establish the identity and stated condition of a spare. It cannot prove the performance of the installed overspeed protection function. Keep procurement evidence, engineering approval, change control, and site proof testing connected, but assign each decision to the party qualified to make it.

Before replacing a Bently Nevada 3500/32 125712-01, preserve the output behavior, not only the module number. The Alarm Drive Logic for each relay, its normal energized or de-energized state, the rear I/O terminal arrangement, and the receiving field circuit must remain aligned. A mismatch can operate the wrong annunciator, interlock, or shutdown input. Control engineers, electrical maintenance teams, commissioning personnel, and MRO buyers should prepare four records before approval: hardware identity, relay logic and states, point-to-point circuit mapping, and channel test results. Plant trip philosophy and setpoint changes remain outside this replacement scope. What Role Does the 3500/32 Relay Module Perform? The 3500/32 converts selected status information inside a 3500 rack into discrete relay-contact outputs for external systems. Depending on the approved site design, those contacts may feed an annunciator, DCS input, ESD input, interlock, or shutdown circuit. The current OEM documentation describes the 3500/32M as a four-output relay module. Each output has its own Alarm Drive Logic, which can combine Alert, Danger, Not OK, and individual PPL inputs from monitor channels using AND and OR expressions. The logic is configured in the 3500 Rack Configuration Software. See the current Bently Nevada 3500/32M datasheet . That function creates three distinct layers that must not be confused: Source condition : a monitor channel produces an Alert, Danger, Not OK, or PPL state. Alarm Drive Logic: the configured Boolean expression decides whether a relay command is true. Field result : the relay contacts change state and the connected external system interprets that change. A replacement check must follow the signal through all three layers. Seeing a relay LED change does not prove that the correct terminal changed state or that the intended DCS or ESD point received it. The Rack OK relay is a separate function. The 3500 System Datasheet locates that relay on the Transient Data Interface I/O module, describes it as normally energized, and limits it to general annunciation rather than automatic machinery shutdown. Do not treat Rack OK wiring as one of the four 3500/32 protection outputs, and do not use a Rack OK test as evidence that the configured 3500/32 relay paths work. Which Details Identify 125712-01 Correctly? Part number 125712-01 identifies a legacy 3500/32 four-channel relay module in the installed base. Identification should begin with the physical label, but it cannot end there. A complete replacement requirement must connect the front module to its rear I/O hardware, rack position, configuration record, and approval basis. Capture these fields from the installed equipment before issuing an RFQ: Identity field Evidence to capture Decision it supports Front module Full faceplate and side-label photos; 3500/32; 125712-01; serial and revision markings Confirms the exact legacy unit being replaced Rack position Rack identifier and slot number Links the module to the correct configuration and rear position Rear I/O module Complete label, part number, approval markings, connector and terminal arrangement Prevents a front-card-only match from hiding an I/O mismatch Installed configuration Controlled configuration export, file revision, and approval reference Establishes the actual relay logic to be preserved Field documentation Current wiring drawing, termination sheet, loop or cable schedule, and cause-and-effect reference Establishes where each contact goes and what it is intended to do Service requirements Hazardous-area, functional-safety, electrical-rating, and site engineering requirements Determines which documentation and hardware options require formal review The current OEM datasheet uses the model designation 3500/32M and lists 149986-02 as the spare four-channel relay control module. It separately lists 125720-01 as a spare four-channel relay output module available for repair only and 125720-02 as the output module for hazardous-area and functional-safety systems. Those current ordering entries do not, by themselves, prove that any one of those items is an unrestricted replacement for 125712-01 or for the rear I/O installed at a particular site. Use the manual revision applicable to the installed rack. The OEM 3500 manuals index identifies document 129771 for the 3500/32 and 3500/32M four-channel relay modules and document 130432 for 3500 field wiring diagrams. If the physical labels, controlled drawings, configuration records, and applicable OEM documents do not agree, place the replacement on engineering hold . Do not resolve the difference by dropping a suffix or by choosing the nearest current catalog number. How Is Alarm Drive Logic Documented Before a Swap? Export or capture the installed Alarm Drive Logic before removing the module. A useful record must show more than a screenshot of a relay name. It should allow another qualified engineer to reconstruct why each output changes state. Build one logic record per relay with the following fields: Logic field What to record Relay channel Relay 1, 2, 3, or 4, using the installed naming convention Logic expression Complete approved AND/OR expression, including grouping Source points Rack slot, monitor channel, measurement or state name Input type Alert, Danger, Not OK, or PPL, exactly as configured Voting or normal/true selection The configured behavior and its approved design reference Latching and reset behavior Whether the relay latches, how it is reset, and who is authorized to reset it Relay mode Normally energized or normally de-energized as found Configuration evidence Export file, screenshot identifier, revision, date, and reviewer Do not simplify (A AND B) OR C to a prose note such as “high vibration trip.” The shortened description removes the very structure that determines how the relay behaves. Also record any unused or forced input, active inhibit, maintenance override, or logic discrepancy as an exception. Do not silently correct it during a supposedly like-for-like replacement. Map Each Relay to Its Field Circuit After capturing the logic source, trace the output side. Use a point-to-point map that links the relay channel to the receiving system rather than a general note such as “goes to DCS.” Relay Rear terminal/contact pair Wire or cable ID External source Receiving system and point Field function Drawing revision 1 Record as found Record as found Identify AC/DC source or dry sensing circuit DCS/ESD/annunciator tag Approved function Controlled reference 2 Record as found Record as found Identify AC/DC source or dry sensing circuit DCS/ESD/annunciator tag Approved function Controlled reference 3 Record as found Record as found Identify AC/DC source or dry sensing circuit DCS/ESD/annunciator tag Approved function Controlled reference 4 Record as found Record as found Identify AC/DC source or dry sensing circuit DCS/ESD/annunciator tag Approved function Controlled reference The completed map exposes common replacement risks: wires landed on the correct terminal number but the wrong relay channel, an undocumented interposing relay, a shared external supply, a stale receiving-system tag, or a rear I/O module whose contact arrangement differs from the drawing. Record Energized and De-Energized States “Normally open” and “normally closed” are not enough to describe the intended field behavior. The contact drawing may show the de-energized hardware state, while the process design may keep a relay energized during healthy operation. Power loss, a false logic result, and a true alarm demand can therefore produce different field interpretations. Create a state-transition matrix before the swap. Fill it from the approved logic narrative, drawings, configuration, and controlled observations, not from assumptions. Test state Logic result expected Coil state expected Contact pair expected Receiving point expected Acceptance reference Rack powered, process normal Site-defined Site-defined Site-defined Normal/healthy indication Cause-and-effect or logic narrative Selected alarm input true Site-defined Site-defined Site-defined Alarm, interlock, or trip demand as designed Approved test case Input returns normal Site-defined Site-defined Site-defined Reset or remain latched as designed Reset philosophy Module or source Not OK Site-defined Site-defined Site-defined Fault response as designed Protection design record Rack or module power lost Not assumed De-energized Verify actual contact result Fail-safe or fault indication as designed Electrical and cause-and-effect drawings Bypass, inhibit, or test state Site-defined Site-defined Site-defined Controlled maintenance response Approved maintenance procedure This matrix answers the question that a wording-only comparison cannot: will the receiving circuit see the same state during normal operation, a commanded alarm, a reset, a detected fault, and loss of power? What Wiring and Isolation Checks Are Required? Relay output terminals can be connected to externally powered circuits even when the 3500 rack is de-energized. Before touching the rear I/O module or conductors, identify every source, obtain the required permit, apply the site's isolation and verification procedure, and prove the circuit state using approved test equipment. The work pack should address: The exact rear I/O part number and terminal designation. Common, normally open, and normally closed conductor identification for each relay. External AC or DC source, return path, fuse, and isolation point for every circuit. Interposing relays, barriers, suppression components, shared commons, and other devices between the 3500 output and the receiving input. Wire numbers, ferrules, cable cores, shields, grounds, and spare conductors against the controlled drawing. The receiving DCS, ESD, PLC, annunciator, or trip-system point and the person responsible for its isolation. Required hazardous-area or functional-safety approvals and the exact contact-rating basis used by the site. Temporary jumpers, test links, bypasses, and their independent removal check. Do not copy a voltage or contact-current value from a current 3500/32M datasheet into a legacy 125712-01 work order without confirming that the document, rear output module, approval option, load type, and installed application match. The current datasheet applies special restrictions to hazardous-area and functional-safety arrangements. The applicable manual and site engineering review must determine the permitted circuit values. The system datasheet also distinguishes front modules from their corresponding rear I/O modules and states that I/O modules are not hot-swappable. No removal sequence is provided here. Follow the applicable OEM manual, the site's electrical-safety procedure, and the approved job plan for the exact rack configuration. Stop the job if a wire identity is missing, two drawings disagree, an external source cannot be isolated, or the rear module label does not match the approved replacement basis. Photographs are helpful evidence, but they are not a substitute for verified wire and terminal identification. How Should the Relay Outputs Be Function-Tested? Test one relay path at a time under an approved commissioning procedure. The purpose is to demonstrate that the documented source condition produces the expected logic result, physical contact transition, and receiving-system indication. It is not necessary or appropriate for every maintenance test to operate a final shutdown device; that boundary must be defined by the asset owner before the test begins. A disciplined sequence is: Verify the as-left configuration. Compare the installed file or captured settings with the approved baseline. Record the file identifier, revision, and reviewer. Confirm the test boundary . Identify whether the test ends at the relay contact, the DCS/ESD input, an annunciator, an interposing relay, or a controlled final-element test. Obtain operations approval for any simulated condition. Establish the normal state. Record the relay indication, measured contact state, and receiving-system status before applying a stimulus. Apply one approved source condition. Use the site's authorized simulation or test method for the specified Alert, Danger, Not OK, or PPL input. Do not create a real process hazard to prove a logic path. Observe the complete path. Confirm the logic result, relay indication, terminal contact transition, wire identity, and receiving point. Time correlation is important when several systems record the event. Verify reset or latch behavior. Remove the stimulus and confirm whether the output returns automatically or requires the approved reset action. Test fault and loss-of-power behavior where required. Use only an approved method and acceptance criterion. Do not infer fail-safe performance from the relay mode label. Restore and independently check . Remove all test forces, jumpers, bypasses, and inhibits; return the circuit to the approved state; and have a second qualified person verify restoration where site rules require it. Record actual observations rather than “relay tested OK.” A useful channel record looks like this: Relay/test case Source condition applied Expected contact transition Measured contact result Receiving point result Reset/result Witness and time Status/exception 1 Approved case ID From state matrix Actual observation Actual tag/status Actual behavior Name/date/time Pass or documented exception 2 Approved case ID From state matrix Actual observation Actual tag/status Actual behavior Name/date/time Pass or documented exception 3 Approved case ID From state matrix Actual observation Actual tag/status Actual behavior Name/date/time Pass or documented exception 4 Approved case ID From state matrix Actual observation Actual tag/status Actual behavior Name/date/time Pass or documented exception If the contact changes but the receiving point does not, keep the result open and troubleshoot the field circuit, interposing devices, power source, and receiving input. If the wrong relay changes, stop and compare the logic assignment, rack slot, and terminal map. A partial success must not be converted into full acceptance. What Must Be Included in the Supplier Documentation? The supplier package should answer a relay-specific question: which four-channel unit is being supplied, which rear I/O hardware is included, and what contact behavior was actually observed before shipment? It must not imply that a loose-module test proves the site's Alarm Drive Logic or field circuit. Specify the required package as a set of linked deliverables: Deliverable Relay-specific content required How the plant uses it Offered-unit identity sheet 125712-01, all visible revision markings, serial number, and photographs of the exact front card and connectors Compares the received card with the approved earlier 3500/32 requirement Inclusion statement Front card only, or the exact rear I/O module and terminal hardware included; no implied accessories Prevents the buyer from assuming the field termination assembly is part of the offer Four-channel bench record Relay 1 through Relay 4 listed separately; test fixture or setup; observed contact state before and during actuation; result, date, and unit serial number Shows what was physically checked without extending the result to site logic Exception record Repair or refurbishment status and any label, connector, card-edge, relay-channel, or packaging exception Directs incoming inspection to the condition that could affect installation or acceptance Quotation release data Available quantity, commercial condition, warranty/return basis, dispatch basis, and the evidence supplied before shipment Aligns the purchase release with the actual offered unit rather than a catalog image The bench record should state its boundary plainly: observed contact operation is not proof of the installed Alarm Drive Logic, terminal wiring, external supply, receiving-system indication, or shutdown action. Those results belong in the site's channel test record. For a useful RFQ, send us clear images of the installed 125712-01 front label and the rear output-module label, plus the rack slot, required approvals, quantity, destination country, and required-on-site date. If engineering review is requested, also provide the relay mapping and non-confidential configuration identifiers needed to compare the requirement. Do not send passwords or uncontrolled plant-sensitive files through an ordinary sales channel. Use our 3500/32 125712-01 inquiry page to send the requirement. We will confirm the offered unit's availability, condition, included I/O, revision information, test scope, warranty, and shipping basis in the quotation. You can also browse our Bently Nevada parts catalog or contact our team . Relay-Path Acceptance Decision Use one end-to-end trace for each of the four outputs: source condition -> Alarm Drive Logic -> relay command -> energized/de-energized state -> rear contact -> field wire -> receiving-system point Every step needs an as-found reference and an as-left result. A matching 125712-01 label does not preserve the configured expression. A correct expression does not prove the contact is landed on the intended circuit. A bench contact test does not demonstrate the DCS, ESD, annunciator, interlock, or shutdown input. Approve the replacement only when the front and rear hardware identities agree with the engineering basis, each output follows the documented state matrix, and the observed receiving point matches the point-to-point map. Any broken link in that chain remains an open commissioning exception.