Prepare for the API SIRE exam by organizing study around the inspection decisions a source inspector makes on rotating equipment: classifying inspection and test plan points, verifying test setup and acceptance criteria, reading data trends before sign-off, reviewing traceability and nonconformance records, and exercising independent judgment. Practice each decision type with written scenarios and a vendor-style inspection and test plan rather than memorizing isolated facts.
Study SIRE as a Set of Inspection Decisions, Not a Parts Catalog
Source inspection of rotating equipment means verifying pumps, compressors, and related machinery at the manufacturer's facility before shipment. Structure your study around the decisions an inspector makes there: what to verify, witness, review, accept, or reject.
Source inspection differs from in-plant machinery maintenance inspection because you are working at the supplier's shop against a purchase order, a datasheet, and project specifications. Rotating equipment source inspection draws heavily on the API machinery publications, with API 610 for centrifugal pumps, API 617 for centrifugal compressors, API 682 for mechanical seals, and API 670 for machinery protection systems serving as natural study anchors. Read each standard with one question in mind: what would I personally have to see or record at the shop?
This reframing changes how you use your study time. Instead of drilling impeller terminology, ask what action corresponds to each fact: a hydrotest pressure implies a hold-point decision; an allowable vibration value implies a data-review decision; a material certificate implies a traceability decision. When you can state the inspector's action attached to each technical fact, recall becomes reliable and exam-style scenarios become manageable. Compare this with the fixed equipment and electrical source inspection credentials, SIFE and SIEE, which cover different equipment domains under the same source-inspection logic.
Choosing Between Hold Points, Witness Points, and Review Points
A hold point stops the manufacturer until you attend; a witness point lets work proceed if you do not attend; a review point is checked on paper afterward. Classifying each inspection and test plan activity correctly is a core skill to practice.
These three terms look interchangeable but carry different consequences, and confusing them is a real conceptual trap. At a hold point, the vendor must notify you in advance and cannot proceed past the activity without your attendance or documented release. At a witness point, the vendor notifies you, but if you miss the notification window the work may continue. A review point requires no shop presence; you verify records, certificates, and reports after the activity is complete. Practice reading an inspection and test plan and marking each line with the correct point type before you check the answer.
The distinction matters because your response changes with each type. For a hold point you must track notification dates and plan attendance; for a witness point you must know what happens if you decline or miss it; for a review point you must know which records constitute acceptable evidence. Build the habit of asking two questions for any activity: what is the point type, and what evidence will exist afterward? Run this drill against any vendor inspection and test plan you can draft or obtain, and compare your classification with the reasoning below.
| Point type | Inspector's action | If the inspector is absent | Typical evidence |
|---|---|---|---|
| Hold point | Attend and release in writing before work proceeds | Vendor must stop and await disposition | Signed hold-point release and test record |
| Witness point | Attend if available; vendor may proceed after notification | Work may continue without you | Notification record and any data you observed |
| Review point | Examine records after completion | Not applicable; no attendance required | Certificates, reports, and material test records |
Worked Scenario: Verifying a Pump Casing Hydrostatic Test
Before accepting a hydrostatic test, confirm the test setup, not just the reading: gauge calibration, test pressure calculation, medium, hold duration, and scope of the tested boundary. The scenario below shows why a correct-looking reading can still be unacceptable.
Scenario: you attend a hold point for the hydrostatic test of a centrifugal pump casing. The technician pressurizes the casing, the gauge reads the specified test pressure, and there is no visible leakage, so you are tempted to sign immediately. The plausible mistake is accepting on the reading alone. In this scenario, ask the technician for the gauge calibration record and check that the test pressure on the gauge matches the pressure derived from the datasheet and the applicable standard, including any temperature or medium requirements in the procedure.
Suppose the calibration certificate shows the gauge is out of calibration date, or the technician computed the test pressure from a bar rather than the datasheet's rated pressure. The better decision is to reject the test result as invalid evidence and require a retest with a calibrated, correctly ranged gauge, documenting the reason. This matters because a hydrostatic test you accept on a faulty gauge provides false assurance that the pressure boundary is sound, and your signature, not the vendor's, becomes the record of that assurance. Practice converting this habit into exam answers: whenever a scenario hands you a passing reading, list the setup evidence you would demand first.
Worked Scenario: Reading the Trend During a Mechanical Run Test
During a mechanical run test, final vibration and bearing temperature numbers within limits are not sufficient by themselves. Check that readings stabilized as the test procedure requires and review the full trend before sign-off.
Scenario: you witness a mechanical run test on a horizontal pump. At the end of the scheduled run, the final vibration readings fall within the acceptance values, and the technician asks you to sign. The plausible mistake is signing because the endpoint numbers pass. In this scenario, look at the trend first: bearing temperature that is still climbing when the run ends has not demonstrated thermal stability, and vibration that was trending upward may sit just under the limit only because the run stopped early. These are scenario-based observations for study purposes; actual acceptance depends on the governing test procedure.
The better decision is to hold your signature and compare the recorded readings at intervals against the procedure's stabilization requirements, then ask the vendor to either show compliance with those requirements or extend the run per the procedure. Why it matters: a signature on a run test asserts the machine was stable at acceptance conditions, and an unstable machine that passes on endpoint numbers can fail destructively after installation when no inspector is watching. When practicing, grade yourself on whether your answers reference the trend and the procedure, not just the final values.
Documentation Review: Traceability, Datasheet Conformance, and NCR Closure
A large share of source inspection work is documentary: matching material certificates to heat numbers, checking nameplate and as-built data against the datasheet, and confirming nonconformance reports are technically closed. Practice reading these records line by line.
Traceability review means following a chain: the material test report identifies a heat number, the heat number appears on the marked component, and the certificate's mechanical properties and chemistry meet the specified material grade. Train yourself to compare three documents at once — the datasheet, the certificate, and the physical marking — rather than trusting any single one. For nameplate review, check rated conditions, materials, and rotation against the datasheet, and note any deviation, however small, because a wrong rotation arrow or a missing material callout is exactly the kind of discrepancy a review point is designed to catch.
Nonconformance report handling is the second half of documentation skill. When you identify a discrepancy, record it factually: what requirement applies, what was observed, and what evidence exists. The vendor proposes a disposition — repair, rework, use-as-is, or reject — and your job is to evaluate whether the disposition restores conformance or is properly approved by the purchaser, not to redesign the part yourself. Practice writing one-line NCR statements from scenario descriptions and check that each states the requirement, the observation, and the objective evidence. Vague NCRs that say only 'rework as necessary' are a habit to avoid from the start.
Professional Standards: Independence, Objective Evidence, and Reporting Limits
A source inspector's authority rests on objectivity: base every acceptance on evidence you personally verified, keep your judgment independent of production pressure, and route disposition decisions through the purchaser rather than the manufacturer's schedule.
Ethics in this domain is procedural, not abstract. You accept work against stated requirements, and if the evidence is missing, stale, or contradicted, you do not accept — even when the shop is eager to ship. Conversely, you do not invent requirements: your leverage is the purchase order, the datasheet, the applicable standard revision, and the approved inspection and test plan. When a vendor proposes a deviation, your role is to document it accurately and escalate to the purchaser for disposition, not to negotiate acceptance on the shop floor. This mirrors the impartiality principle API states for its certification programs: decisions based on objective evidence and program requirements.
Practice this with decision drills. Give yourself short situations — the test lab certificate arrives unsigned, the supervisor urges shipment tonight, a procedure step conflicts with the datasheet — and write your action and the authority you cite. Check your answers against three tests: Is my action based on a stated requirement? Is my evidence objective and traceable? Have I kept the disposition with the party who owns it? An answer that passes all three is usually both the ethical and the technically defensible one, which is why these drills sharpen exam judgment and field conduct together.
A Four-Week Practice Sequence with Readiness Self-Checks
Spend two weeks on the rotating equipment standards and point-type logic, one week on documentation and NCR drills, and one week on mixed scenarios. Finish when you pass the self-check rubric below, which marks learning milestones, not a passing prediction.
Weeks one and two: read the pump, compressor, seal, and machinery protection standards on your shortlist, and after each reading, draft a one-page inspection and test plan listing the activities, point types, and acceptance evidence. Weeks three and four: shift to drills — classify 15 activities by point type, write five NCR statements, and complete two timed scenarios like the hydrostatic and run-test cases above. Exercise: take any vendor-style inspection and test plan and, for every line, write the point type, the notification requirement, and the evidence you would collect; then score yourself against the rubric in the bullets.
Readiness checks before scheduling: you can classify point types without hesitation; you can state the setup evidence required for a pressure test and a run test from memory; you can trace a material certificate from heat number to component; and you can write an NCR with requirement, observation, and evidence in two sentences. Administrative matters — application steps, exam windows, and fees — belong on API's Individual Certification Programs page rather than in study notes, since those details change. Use the free practice questions on this site to convert these skills into exam-item format, and revisit the main study guide index to balance this plan with your other preparation.
- Rubric item 1: every inspection and test plan line is classified as hold, witness, or review, with the notification consequence stated — target 15 of 15 correct.
- Rubric item 2: for each test activity, you list at least three pieces of setup evidence (calibration, procedure, datasheet derivation) before any reading is discussed.
- Rubric item 3: each NCR statement names the governing requirement, the observed condition, and the objective evidence, with no vague disposition language.
- Rubric item 4: in both worked scenarios, your written answer references the data trend and the governing procedure, not only the final reading.
- Milestone note: scoring yourself on this rubric measures study progress only; it is not a prediction of your exam result.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.