> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/readers-credentials-and-locks/nedap-access-reach-target-obsolescence-june-2024.md).

# Nedap Access Reach/Target obsolescence - June 2024

Review UPASS Access and Reach reader obsolescence, affected hardware, and UPASS Go availability.

#### **Immediate Obsolescence notification for All Regions**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Notification

**Effective immediately due to components issue**

Limited Stock is available on a per case basis. New Nedap **UPASS Go** to be announced once supported.

#### **Parts affected:**![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

* C862501 NEDAP UPASS REACH UHF READER (RGN 2 & 3)
* C862401 NEDAP UPASS ACCESS UHF READER RGN 2 & 3
* C862503 NEDAP UPASS RDR WEATHER PROTECTION HOOD
* C862504 NEDAP UPASS RDR POLE MOUNTING SET
* C862502 NEDAP UPASS RDR ADJUSTABLE MOUNTING SET

*Note: The **Nedap Target** devices are not affected by this discontinuation and are available to order.*

* C862411 NEDAP UPASS TARGET UHF READER (RGN 2 & 3)
* C862412 NEDAP UPASS TARGET PROTECTION HOOD

#### Questions![Edit section](https://resources.security.gallagher.com/skins/common/icons/icon-trans.gif)

Please direct questions to your local Gallagher representative.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/product-advisories/historical-notices/readers-credentials-and-locks/nedap-access-reach-target-obsolescence-june-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
