Setting Up DNV-ST-E271 Lifting Set Certificates

How to configure Core for DNV-ST-E271 (DNV 2.7-1) and DNV-ST-E273 work: the equipment type with component traceability attributes, the Certificate of Test and Certificate of Inspection templates, the traceability block and proof loads on the certificate, numbering and revision control.

Last updated

Content

How the DNV workflow fits together

1. The equipment type

2. Two inspection templates, plus NDT

3. The certificate templates

4. Certificate numbering

5. Amending an issued certificate

6. The container owner's portal


How the DNV workflow fits together

A lifting set certified to DNV-ST-E271 needs two kinds of certificate over its life: a Certificate of Test & Examination when it is manufactured or re-certified, and a Certificate of Inspection at each periodic visit (visual at 12 months, NDT or load test of components at 48). Both certificates describe the same components, so in Core the component data lives on the equipment record and the certificates read from it. The same pattern works for portable offshore units under DNV-ST-E273.

The traceability block and the proof load calculation described in steps 3 and 4 are configured by Core support against your certificate template. Send us a recent certificate and we will set them up with you during onboarding or on request.

1. The equipment type

Create an equipment type for the standard (for example DNV-ST-E271 lifting set) under Configuration > Equipment Types, and give it an attribute for every value that appears on the certificate. A working set looks like this:

  • Sling: WLL (t), MBL (t), angle, effective length (m), number of legs, size (mm), construction, core, lay, finish, grade, splicing method, termination, date of manufacture, ID number, manufacturer serial number
  • Wire rope: manufacturer, batch number
  • Master link: manufacturer, size, grade, batch number, type approval (TA) number
  • Ferrules and thimbles: manufacturer, size, material, batch number
  • Shackles: manufacturer, WLL (t), grade, type, TA number, and a batch number for each shackle (shackle 1 to shackle 4)
  • Top leg or forerunner, where fitted: length and size, construction, core, lay, finish, grade, master link details, termination
  • DNV-ST-E273 only: operational class

Use list attributes for the values that repeat (grade, construction, ferrule material, master link grade) so technicians pick rather than type, and add an "Other" free-text attribute beside each list for the exceptions. See Configuring Equipment Types for the mechanics.

The point of putting the components on the equipment record rather than the inspection is reuse: the values are entered once when the set is built and appear on every certificate for its life, including re-certifications after a shackle is replaced.

2. Two inspection templates, plus NDT

Link these inspection templates to the equipment type under Configuration > Inspection Templates:

  1. Certificate of Test & Examination: the manufacture or re-certification test. Fields for the test specification (for example DNV-ST-E271 & AS 1666.1), the load cell used, the proof load applied, the compliance statement (pass and fail versions, shown by the result) and comments.
  2. Certificate of Inspection: the periodic examination. A checklist of the items the standard asks for (tag, component marking, master link assembly, legs, terminations, shackles, couplings, geometry, overall condition), the schedule applied this time (12-month visual, 48-month NDT or load test), the result and the suffix marked on the tag (V, VN or T).
  3. NDT certificates for magnetic particle, liquid penetrant and eddy current testing, linked to the same type so the 48-month evidence sits on the same asset.
  4. An anomaly report for defects that take a set out of service.

Give each template its own default interval so the next due date follows the certificate that was issued: 12 months after a Certificate of Inspection, and the 48-month items tracked as a separate interval or a custom field. See Configuring Inspection Templates.

3. The certificate templates

Each inspection template is formatted by a Word document with <<tags>>, as described in Configuring Certificate Templates. Equipment attributes are available as <<equipment.Attribute Name>>, so the master link's type approval number is <<equipment.Master Link TA No.>> and the first shackle's batch is <<equipment.Shackle #1 - Batch Number>>.

Two parts of a DNV certificate need more than a single tag:

  • The component traceability block, one line per component in the form "Manufacturer, size, grade, component, batch number, TA number", with each shackle on its own line. Core support configures a stored-procedure tag for your template that composes these lines from the equipment attributes and drops any segment whose value is empty, so a sling without thimbles does not print an empty thimble line.
  • Proof loads per leg, in kN for the master link, each leg and each shackle. These are calculated from the WLL, angle and number of legs in a calculation template, and the technician records the load cell reading against each expected value. Core support sets the calculation up from your test procedure.

Both certificates can also show the conditional text the standard expects: a compliance statement that changes with the result, and the line "Designed, manufactured and tested in accordance with DNV-ST-E271" on the test certificate.

4. Certificate numbering

The certificate number on a DNV lifting set is stamped on the ferrules and the DNV tag, usually before the certificate is issued, so it has to exist as soon as the inspection is opened. Set a certificate number series on the inspection template so the number is allocated when the inspection is created, not when it is approved. If you run more than one laboratory, give each branch a branch code under Configuration > Branches and use the {branchcode} placeholder in the series prefix so each lab's certificates are distinguishable at a glance.

When several sets are tested on one job, multi-inspect honours the series so each certificate gets the next number in order.

5. Amending an issued certificate

Laboratories accredited to ISO/IEC 17025 have to control amendments to issued reports (clause 7.8.8). In Core, changing an inspection after its certificate has been issued requires a reason for the change, the certificate template can print the revision and the reason for amendment using the certificate revision tags, and the audit log keeps the before and after values. Point your assessor at the audit entry and the revised certificate together.

6. The container owner's portal

Container owners are responsible under the standard for keeping certification current and for the records. Give each owner a portal login so they can see their own lifting sets and containers, the certificates and NDT reports attached to each, and the next due dates. See Customer Portal: Equipment Register. Logins are unlimited, so the owner's logistics team and their HSE team can each have their own.