Introduction: After Delivery and Receipt, Why Do Parties Still Dispute Whether the Warranty Period Is Still in Effect?
The most common dispute after delivery of a 3D-printed part is not that the part cannot be manufactured, but that the service commitments are written too broadly. A contract statement such as “one-year warranty and lifetime service” can quickly degenerate into competing narratives in practice: the customer says the part cracked three months after installation and should therefore be replaced free of charge; the supplier says the customer supplied the model, the part was machined a second time before installation, and its load exceeded the technical agreement, placing the matter within an exclusion. Neither party can produce the fields needed for a determination: when the warranty period began, which version of the technical agreement applies, whether the failed part was retained, when the service ticket was created, or whether the response was late. The dispute can then only be resolved through commercial concessions. lantu3D treats delivery as one stage in managing the entire lifecycle from blueprint design to physical delivery, and service terms likewise need to be frozen, documented, and reviewed just like process parameters. This article presents an implementable engineering method for translating “good service” into verifiable commencement points, tiers, thresholds, and evidence chains.
1. Warranty Commencement Point and Freeze of Delivery Status
The warranty period should not begin on the manufacturing completion date or shipment date. Instead, it should be tied to an event that both parties can verify. It is recommended to define T0 as the point at which the part has passed inspection, has been packaged as agreed, has arrived at the designated location, and has been signed for. The receipt form should freeze eight fields at that point: contract number and line-item number; part serial number or batch number; technical agreement and version number; inspection report number and witness-coupon number; receipt time, including time zone; packaging condition and status of impact-indicator labels; delivered quantity; and the signatories for both parties. If the project uses first-article sealing or approval samples, the sample identifier and sealing date should also be recorded on the same form. This prevents later arguments over the same clause based on two different interpretations of the “approval sample” and the “production part.”
The warranty period should also be expressed as a dual limit rather than a single number of calendar months. For example: “12 months from T0, or 2,000 cumulative printing hours or service cycles, whichever occurs first.” The source of the hour count must also be specified, such as an exported equipment log, a reconciliation with the customer’s system, or a mutually confirmed ledger. The retention period for original records should be no shorter than the warranty period plus six months. The retention period for retained samples should match the warranty period, and the triggers for retesting should be defined: retesting is automatically initiated upon a third complaint involving the same type of issue or when the customer raises a written objection to an inspection conclusion. Without such provisions, it may be impossible to retrieve the relevant powder batch number, energy-density parameter package, or inspection records even one year later, and no matter how rigorous the wording, the supplier may be unable to substantiate compliance.
2. Tiered Criteria for Warranty Coverage and Exclusions
The greatest problem with exclusions is an unclear enumeration. The engineering approach is to divide the responsibility boundary into four categories and, for each category, identify the evidence fields and use a three-state determination: evidence supported, evidence insufficient, or excluded. A direct jump to a final conclusion is not permitted. The first category is input-model and design responsibility. This covers wall thickness, fillets, supports, and print orientation that were provided by the customer without the supplier’s DFM confirmation, as well as subsequent customer changes to the model version. The relevant evidence includes the model hash, part_revision, change-order number, and DFM confirmation record. The second category is secondary machining and post-processing. This covers third-party machining, welding, heat treatment, coating, adhesive bonding, or assembly torquing. The evidence includes the routing sheet, subcontractor report, assembly torque record, and surface topography photographs. The third category is operation beyond the specified conditions. This covers temperature, load amplitude, medium, or cycle count exceeding the windows declared in the technical agreement. The evidence includes the duty profile, load spectrum, medium analysis report, and operating log. The fourth category is normal wear and consumables. This covers the consumption of consumable items such as protective lenses, wiper blades, filters, and seals according to an established schedule. The evidence includes the replacement ledger and accumulated operating hours.
The purpose of the three-state determination is to prevent forced attribution. If the evidence from a fracture surface or failed part points only to “inclusions on the material side” but lacks review data for the same powder batch, the case should be recorded as “insufficient evidence,” and supplementary sampling should be initiated rather than assigning liability directly to either the customer or the supplier. The failed part itself should be retained using bilateral protection, prohibition of mating, six-sided photography, and serial-number binding. It should also be cross-referenced with the existing fracture-analysis, inspection-batch, and witness-coupon evidence chains. A warranty conclusion may be formed only after the three categories of evidence—process records, inspection records, and service records—are complete.
3. Service-Level Agreement Tiers and Response Timeliness
Service requests should be classified into three levels according to their impact on the customer’s production line, rather than through subjective labels such as “urgent” and “routine.” P1 applies to complete production-line shutdown, safety risks, or suspected common-origin defects in a batch. It requires a response within two hours, a remote disposition plan within 24 hours, and on-site support or dispatch of a replacement part within 72 hours. P2 applies to degraded performance where production can continue. It requires a response within eight hours and an analysis and corrective action within three business days. P3 covers document supplementation, parameter consultation, and non-functional questions. It requires a response within 24 hours and closure within five business days. Each level must define what constitutes a “response.” It should mean that the ticket has been accepted and assigned to a named owner, not merely that an automated email was sent; otherwise, timeliness statistics are meaningless.
The common commencement point for all timeliness calculations should be the ticket-creation timestamp, including the time zone. Two types of suspension conditions should be agreed: time spent waiting for the customer to provide fault logs, samples, or access to site conditions does not count toward the SLA. However, the start and end times of every suspension must be confirmed by both parties within the ticket; no party may suspend the clock unilaterally. Escalation should use two triggers: the ticket automatically advances one level and the owner at the next level is notified if it exceeds 1.5 times the target duration for its tier or if a second ticket of the same type occurs for the same serial number within 30 days. A default fallback action should also be established. If an owner does not accept the ticket within the specified threshold, it is automatically reassigned to a backup role, with an audit trail. These rules should use the same identity and timestamp system as account permissions and operational audit logs, preventing service records from becoming inconsistent with data-access records.
4. Spare-Parts Commitments and the Boundary for Consumable Parts
Spares provisions must be defined through an itemized list and quantities rather than through a promise to “supply promptly.” The first step is to list consumable and critical parts by component family: protective window lenses and galvo-related consumables on the optical side; wiper blades or powder-scraping strips, seals, and filters on the build side; timing belts and couplings on the motion side; and seals and filtration components associated with the powder path. Each item should specify its recommended replacement interval or MTBF basis, applicable machine model, unit of measure, and whether it is supplied free with the machine. Minimum spare-parts inventory should be back-calculated using “installed base × annual operating hours ÷ MTBF × service-coverage factor.” Replenishment trigger points and committed shipping times should also be defined—for example, dispatch of common items within 48 hours and dedicated items within ten business days—together with the ownership of replacement parts supplied through a trade-in arrangement and the deadline for returning the replaced items.
Another common source of dispute should also be addressed: whether replacing a spare part resets the warranty on the complete machine. Unless the contract provides otherwise, the default should be: “No reset; only the replaced part receives a separate guarantee of three months from the replacement date or the remaining warranty period, whichever is longer.” This prevents a single replacement from extending responsibility for the complete machine indefinitely, while also preventing the supplier from dismissing a newly installed part as “out of warranty.” The spare-part batch number, warehouse issue note, replacement work order, and returned-item identifier should all be mutually indexable, creating a verifiable closed loop.
5. Cost Allocation for On-Site Service and Repair Determinations
On-site service is expensive and susceptible to misuse, so dispatch thresholds should be established first. A field technician should be dispatched only where the issue cannot be reproduced remotely and specialized tooling or an installation datum must be checked; where multiple assembly interfaces are involved; or where the issue is P1 and a replacement part cannot be dispatched in advance. Each dispatch order must include estimated labor hours, a list of required tooling, an acceptance-signature template, and the travel-cost boundary, including which expenses are borne by each party and how time spent beyond the agreed mileage or waiting for customer-provided site conditions is charged. The output after arrival should not consist merely of the statement “it has been repaired.” It should be a structured record covering the fault symptoms, reproduction conditions, measured data, temporary measures, final conclusion, customer confirmation signature, and outstanding risks.
A repair determination should permit only three outcomes, each linked to a cost matrix: repair, in which labor and material costs are borne by the supplier when the supplier is responsible and charged according to the quotation when the customer is responsible; replacement, in which the old part is returned and retained and costs are allocated according to the responsible party; or concessionary use, in which the customer accepts the deviation in writing and it is expressly agreed that subsequent failures are not covered by the warranty. The cost matrix should be organized on two dimensions: responsible party by disposition method. Each cell should identify who bears the material, labor, logistics, and inspection costs, avoiding item-by-item disputes after the fact. Retesting of a repaired part must reference the original CTQ list and acceptance criteria and cannot rely on visual inspection alone.
6. Claim Timeliness, Service-Record Evidence Chain, and Performance Dashboard
Claim timeliness should preferably be calculated from the “date of discovery” rather than the “date of failure.” The customer should, however, be required to notify the supplier in writing within five business days of discovery. The minimum set of notification fields should include the serial number, contract number, discovery time, fault symptoms, emergency measures already taken, an index of site photographs or logs, and confirmation of whether the failed part has been retained. The discovery date is used because latent defects in additively manufactured parts—such as incomplete internal fusion or residual powder—often remain hidden until the part has been in service for some time. Prompt notification is required to ensure that evidence is not compromised by further machining or handling. The corresponding supplier obligation is to provide an acceptance number and evidence checklist in accordance with the SLA after receipt of the notice, with both parties jointly freezing the evidence status.
Service records should be organized in accordance with ALCOA+: attributable, legible, contemporaneous, original, and accurate, supplemented by complete, consistent, enduring, and available records. Four primary keys must run through every record: serial number, work-order number, fault code, and log timestamp. Every response, dispatch, replacement, and retest must be linked to these four keys. The monthly dashboard should track at least six metrics: on-time response rate, first-time resolution rate, spare-parts fulfillment rate, on-site dispatch rate, number of repeat incidents of the same type, and SLA attainment. It should report P95 response time rather than only the mean, since a large volume of P3 tickets can dilute the average. Recommended targets are an on-time response rate of at least 95%, a first-time resolution rate of at least 85%, and a P95 response time no greater than 1.2 times the applicable tier threshold. Two consecutive months below target should trigger a review of the contract terms and resource allocation rather than a temporary increase in staffing.
Summary and Minimum Verification Checklist
The professionalism of after-sales service does not depend on how attractive the commitments sound, but on whether, when a dispute arises, both parties can retrieve the same set of fields and reach the same conclusion using the same criteria. Eight matters should be written into the technical agreement appendix: warranty commencement, three-state determination of exclusions, P1, P2, and P3 timeliness, spare-parts lists and quantities, on-site dispatch thresholds, a cost matrix, claim timeliness, and the evidence chain. Doing so transforms service from an issue of attitude into a verifiable engineering problem. The minimum verification checklist is: 1) a T0 receipt form containing eight fields; 2) a dual-limit warranty period and record-retention period; 3) four categories of exclusions, each supported by evidence fields; 4) three-state determination and a prohibition on forced attribution; 5) three SLA tiers covering commencement, suspension, escalation, and fallback; 6) a consumable-parts list, minimum-inventory back-calculation, and a no-reset provision for the complete-machine warranty; 7) on-site dispatch thresholds and a responsible-party-by-disposition cost matrix; and 8) service records linked by four keys and a dashboard tracking six performance metrics. By satisfying these eight requirements, every post-delivery service interaction can be reviewed and improved, making the lifecycle commitment from blueprint to physical product genuinely enforceable.
Hantar model, lukisan, imej atau nota bertulis. Jurutera akan menyemak bahan, proses, penyempurnaan dan penghantaran berdasarkan penggunaan sebenar.