The scope of work

The scope of work is what the client asked to have examined: the lifting lugs by MT, the thick seams by PAUT and TOFD, the nozzles by UT or PAUT, the tubes by eddy current, before heat treatment, after it, or both. NDT Intact keeps it per asset, or for the whole project, and works out from the issued reports how far each inspection has got. Nobody types "done".

What a scope of work holds

A scope has two levels, because the welds belong to the thing examined and the method, the amount and the stage belong to each examination of it:

• An item is what is examined, in the client's words: "Lifting lugs", "Circumferential seams up to 38 mm", "Vessel", "Tubes". An item may list the welds or TMLs it is made of; then the scope follows each one, and a weld may sit in several items.
• An inspection (a requirement) is one examination of an item:
  • Method: one, or two where either will do ("PAUT or UT": the first named is preferred). A method that is needed as well, such as PAUT and TOFD, is another inspection.
  • How many and Of what: welds, TMLs, tubes, points, items, metres or square metres. Not needed where the item lists its welds.
  • Extent, %, and whether it is a percentage of Each item (10% of every seam's length) or of Their number (20% of the tubes, a sample). The page works out how many that is: "(248 to do)".
  • Stage: when in the fabrication: after welding, before PWHT, after PWHT, after the pressure test, before welding, root or back-gouge, after forming, or one of your own. One stage per inspection.
  • Procedure and Acceptance criteria, as the client names them, and a Note.

NDT Intact ships no scope, no extent and no sampling rule. What is entered is what the client asked for.

Where it lives

A scope belongs to an asset, or to the project itself for work asked for no asset in particular (piping by line class, for example). You see it in three places:

• An asset's page opens with its scope of work.
• The project's Scope of work tab is the overview: every asset side by side, each with how many inspections are still owed, and For the whole project beneath. It says at the top that the asset's page is where the work is done; click an asset to open it. What do these mean? beside its intro opens a legend of the seven states.
• A weld's page shows what the scope asks of that weld; see the tracker.

Owners, admins and technicians enter and change the scope. Everyone on staff reads it.

Entering it

On the asset's page or the Scope of work tab, choose Add an item:

1. What is examined, in the client's words.
2. It is made up of: Welds, TMLs, or Neither: a part, or the whole asset.
3. Which welds (or Which TMLs): one per line, or separated by commas. Optional. A number the tracker does not know is added to it, so the scope is also the quick way to enter a weld list.
4. Under Inspections it needs, fill in the first inspection: method, Or, where either will do, how many and of what, extent, when, procedure, acceptance criteria. Another inspection adds the next.

When depends on the asset. On an asset marked heat treated after welding, every inspection is asked Before PWHT, After PWHT or Before and after PWHT (two inspections): before and after are two inspections with two reports, so the form makes two lines in one go. An asset without PWHT is never asked. Set this on the asset with Heat treated after welding (PWHT); see assets.

Items and inspections are edited from their "⋯" menu. Take out of the scope removes an inspection or an item from the lists without deleting anything (the reports that answered it stay), and Put back restores it.

Other ways to start a scope

• Copy to other assets, for assets of the same design: the items and inspections are copied to the assets you tick, and each asset gets welds of the same numbers of its own. An item an asset already has is left as it is. Copy from another asset does the same the other way round.
• Add to the scope of work on a request's page, while nothing is entered for what the request is about: the scope's form opens filled in from the request, with its welds, one inspection per method, the stage and the procedure and acceptance criteria it names. One confirmation stays, because a request cannot say whether "C4" is a weld or a TML. The lines made this way read Requested at once.
• Read from a document, when AI is switched on for your company (see AI): upload the client's inspection and test plan, NDE table, purchase order, email or weld list, or paste its text. AI proposes the items and the inspections each needs; you check every item against the document, correct it, untick what does not belong and choose Enter the scope. Nothing is entered until you confirm, and the page records who confirmed and when.

How progress is worked out

Where an inspection stands is never stored; it is worked out from what stands today:

• By weld or TML, where the item lists them: from the results of every current report of the asset in one of the inspection's methods at its stage that covers one of those welds, and of any report linked to the line by hand. Each weld is outstanding, reported, accepted, rejected or repaired and awaiting re-inspection. The inspection is done when the welds it needs are accepted: all of them, or the number the extent asks for.
• By report, for the rest (a hardness test, the tubes): outstanding until a report linked to the line is issued. A link may say more reports are to come.

A sample that is met asks nothing more: once 20% of the tubes or clips are done, the welds outside the sample leave the tracker's count and read Not in the sample. A rejection opens the inspection again. A revision or a withdrawal of a report moves the answer by itself, because only current results are read. NDT Intact never closes an inspection by itself and never refuses a report.

What each state means

• Outstanding: nothing has answered it yet.
• Requested: an open inspection request calls it off.
• In progress: a report in draft or in review covers part of it, part of its welds are reported, or someone has marked work in the field.
• Awaiting report: everything it needs is met or marked inspected in the field; what is owed is the report. Only your company sees this step; the client still sees it as outstanding.
• Repair required: a current report rejected one of its welds.
• Done: the welds it needs are accepted, or the report that answers it is issued.
• Closed: a person closed it with a reason.

The same words are explained with the other statuses in what the statuses mean.

Marks from the field

The work happens before the report: six welds are examined today and the report is written tonight. So beside the record stands what the field says, marked by hand by owners, admins and technicians:

• Mark inspected on a line of the scope opens Mark what was inspected: tick the welds, say whether they are In progress, Inspected, Accepted or Rejected, and the day. Rejected asks for the Kind of defect, a Note and Photos; the photos become files of the weld. For an inspection without welds (the tubes, the hardness points) you enter Done so far.
• The same marks are made on a weld's page, on a request's items, and from the tracker's list by ticking welds and choosing Mark inspected; see the tracker. One mark per weld per method at a stage, whichever paper asked for it.

A mark is never a result. It makes the line In progress with a percentage worked out ("Inspected 5 of 5 (100%) · Reported 0 of 5"), and once everything is marked the line reads Awaiting report. Accepted and rejected on record come from the issued report alone, and the client never sees a mark. The report started from the line begins with exactly what was marked: the welds, the disposition the field gave each, a row of the indications table for each defect found, the day and the photos. When that report is issued, it takes the marks away. A weld rejected, repaired and examined again is simply marked again.

Starting a report from a line

Start report on a line opens the report dialog with the asset, the method's template (your default for the method first; both methods' templates for an either-or), the stage, and the procedure, acceptance criteria and extent filled in. Its weld results table starts with the welds marked inspected that no report in the works lists yet; where nothing is marked, with every weld still owed. The button says which: Start report (2 inspected). Where exactly one open request calls the line off, the report answers that request too. Every field stays editable.

The report carries an Inspection stage, printed on it and frozen at issue. The step needs the Technician role; someone without it is told so, with the way to the Team page.

Closing, reopening and linking by hand

• Close as not needed closes an inspection the client waived or that does not apply after all, with a reason kept with your name and the date. Open again reopens it.
• Link a report attaches a report that already exists and answers the inspection; tick More reports are to come for this inspection where it is only part. Take ... off this inspection undoes the link. A linked report of a weld item counts its welds; a linked report of any other item answers the line once it is issued.
• Every change to the scope is written to the activity log.

What the client sees

With the project's tracker released to the client (see the tracker), the portal shows the scope of work of each asset and how far it has got, counting issued reports only: never a draft, never a report in review and never a mark from the field. On an outstanding line the client chooses Request inspection to call the work off; the request fills in the methods and the welds still owed, and the line reads Requested while it is open. Staff raise a request from the scope the same way, under From the scope of work on the request form.

The checks before issue, and the Operations module

Two warnings, never a refusal: a report of an asset that has a scope and answers no line of it, and a report whose stage is not the stage of the line it was started from. The examiner reads them and goes on; see issuing a report.

With the Operations module, From the scope of work on a job lists the inspections the project's scope still owes; each one ticked becomes a work item with its method and how much is still to do, so demand and estimates follow from the scope, and a report started from the item answers the line. Extra scope the client approves in the portal joins the asset's scope as well as the job. See operations.

Why "accepted after MT" is not "done"

The tracker knows the method and the stage of every result. A weld that needs MT, PAUT and TOFD is not accepted after the MT alone: each inspection of the scope reads from the reports in its own method at its own stage, and a rejection under one method stands until that method inspects the weld again. MT after heat treatment following an accepted MT before it is a new inspection, not a repeat. See what the statuses mean.