> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/archive/use-busroot/oee/pt-vs-npt.md).

# PT vs NPT

Productive time versus nonproductive time 

Is the amount of time that the asset (machine) is adding value versus the time that it's not adding value.

In this case we are looking inside of the cycle time. PT vs NPT is looking at productive time versus nonproductive time, it is looking at the amount of time that your asset is actually in use.

So a CNC operation would be a good example. If you have a 10 minute CNC cycle time, which means the 10 minutes includes you loading the machine, running the programme and unloading the machine. That's what OEE would look at in its entirety. Is your entire cycle part to part.

Whereas PT versus NPT is now looking inside that cycle and it's looking at during your loading time, the machine wasn't in use, and during your unloading time the machine wasn't in use. So that's what's called nonproductive time. The only productive time was the part inside that cycle, and this is what our asset utilisation heat map is. It’s looking at the Andon light which tells us whether the machine is actually adding value. Which is very distinctly different from OEE.

The two get confused. But actually OEE and productive versus nonproductive time are two completely different concepts.

One is around making sure you achieve your nameplate or your documented cycle time.

This one is around making sure that your assets are being utilised as much as possible and are essentially looking to reduce your cycle time. OEE does not look to reduce your cycle time. It just looks to make sure that you achieve your cycle time.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.output.industries/archive/use-busroot/oee/pt-vs-npt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.