> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-go/documentation/user-manuals/installation-and-operation-manual/planning-and-preparation.md).

# Planning and Preparation

The guidelines in the following sections are intended to help project planners and system administrators plan for the physical and logical requirements of deploying and using DynaFlex II Go products. The most effective way to ensure smooth deployment of a solution is to consider these factors before receiving the device.

## Logistical Planning <a href="#id-2.1_logistical_planning" id="id-2.1_logistical_planning"></a>

* Determine what type of host DynaFlex II Go will connect to. For a list of supported device types and operating systems, see Table - Available Models and Options. When planning, be sure to include any additional support or devices required by the host and DynaFlex II Go, such as physical locations, mounting, power connections, and charging cradles.
* Determine what connection the host will use to communicate with the device. The available connections are USB-C for power and control and Bluetooth® Low Energy (LE) for wireless connectivity (see Table - Available Models and Options).
* Determine what software will be installed on the host and how it will be configured. Software can include the operating system, transaction processing software, security software, and so on. If teams other than the software development team will be involved in preliminary device testing, MagTek recommends the solution development team provide a smoke test harness early in the development process to allow basic testing (for example, communication adapter testing). In addition, be sure to plan for any additional support required by the software, such as software licenses and network connections. Information about software is provided in section 4.2 About Host Software.
* Determine how the device will be physically presented to the cardholder. If the device is mounted, make sure there is adequate clearance for cardholders to swipe, insert, and tap. If the solution design includes metal objects anywhere near the device, including metal enclosures, make sure that at all points the metal is no closer than 15mm from the MSR swipe path or card insertion slot. Proximity to metal can adversely affect the device’s performance.
* Determine how the device should be configured and specify that configuration when ordering the device. A full list of configurable options is documented in *D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS)*.
* Select and configure a secure workstation that advanced operators will use to configure and/or update the device. The workstation must be configured as follows:
  * Available USB port.
  * A secure means of obtaining files, either via the network (such as SFTP) or via removable media, such as USB flash drives. This is required for installing software tools, copying firmware files, etc. If you are using Magensa Services, make sure the secure workstation has an internet connection and has all the required Magensa Remote Services software components installed.
  * *1000007406 DynaFlex, DynaProx Test Utility* installed, which advanced operators can use to configure and test the device.
* Determine the final set of tools advanced operators will use to configure, test, and update the device. This documentation uses the *1000007406 DynaFlex, DynaProx Test Utility* as an example for configuring the device; it can be used for initial pre-deployment testing and development, and as sample code showing how to communicate with the device, but the full solution may call for customized, solution-specific software for configuring the device and updating firmware.
* Determine how to inspect devices upon arrival, upon installation, and periodically during live usage, to ensure malicious individuals have not tampered with them. Details about inspection are provided in section 4.1 About Inspection.
* Develop procedures for maintaining the device(s). Detailed guidance is provided in section 8 Maintenance.
* Determine how to train operators. For example, training may include information extracted from section 5 Configuration, section 6 Operation, and section 8 Maintenance.
* Review the device’s PCI Security Policy, posted to the PCI web site [www.pcisecuritystandards.org](http://www.pcisecuritystandards.org/) under Approved PIN Transaction Security (PTS) Devices, for additional information about using the device securely.


---

# 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://developer.magtek.com/hardware/card-readers/mms-dyna-devices/dynaflex-ii-go/documentation/user-manuals/installation-and-operation-manual/planning-and-preparation.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.