NPT (Non Productive Time)

Non-Productive Time (NPT) refers to periods during operations when no productive work is being done due to delays or issues. In pdVISION, NPT events are categorized to help track and report downtime accurately. Here’s a guide to the different types of NPT:

Logging NPT in pdVISION

To log NPT during an operation:

Identify the Type of NPT: Determine whether the delay was related to wireline, non-wireline, operational issues, third parties, environmental factors, or a client hold.

1. Select Event:

• This option allows you to choose the type of downtime event you're logging. You can select between Non-Active Time, Non-Wireline (Non-WL) NPT, or Wireline (WL) NPT.

2. Event Types:

No NPT

• Definition: This option is selected when no non-productive time occurred during the stage. It indicates that the operation was carried out without any delays or interruptions.
• When to Use: Choose this when the operation proceeds smoothly and on schedule, with no downtime recorded.

Wireline NPT (WL NPT)

• Definition: This type of NPT is logged when delays or issues occur related to wireline operations. Wireline services are responsible for running tools and performing perforating jobs, so any problems such as tool failures, equipment malfunctions, or setup delays are categorized as Wireline NPT.
• Examples:

• Tool string failure.
• Wireline truck issues.
• Excessive time to rig up or rig down.

Non-Wireline NPT (Non-WL NPT)

• Definition: This NPT type covers delays caused by factors unrelated to wireline operations. These can include operational or logistical delays from other teams or equipment on site, or environmental conditions.
• Examples:

• Pump truck malfunction.
• Weather-related delays.
• Issues with other service providers (e.g., cementing, fracturing teams.

3. Event Start and End Times:

• Event Start: Enter the time when the downtime or non-active event began.
• Event End: Enter the time when the event ended, marking the duration of the downtime.

4. Notes Section:

• You can click on "CLICK TO EDIT" to enter additional details about the event. This can include a description of what caused the delay or downtime, the actions taken to resolve it, or any relevant notes for future reference.

5. Back and Finish Buttons:

• Back: Use this button to return to the previous screen without saving the event.
• Finish: After filling in all the details, press Finish to save the event and log it as part of the stage timeline.

This section is crucial for accurately capturing downtime during operations and helps ensure that any delays are documented and categorized for future analysis.