# Infor Factory Track Scanner Device and Wireless Coverage Sizing Calculator

> Source: https://netray.co/tools/infor-factory-track-scanner-and-wireless-sizing-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Plan a Factory Track Warehouse Mobility and Time Track rollout: access points, devices with spares, peak transaction load and kiosks for shift change.

## Category

infor-cloudsuite

## Erp

Infor Factory Track

## Audience

- IT infrastructure lead
- Warehouse manager
- Factory Track project manager

## Tool

**Kind:** calculator

**Inputs:**

#### Warehouse and shop floor area to cover

**Key:** area

**Type:** number

**Default:** 8000

**Min:** 0

**Step:** 100

**Unit:** m2

#### Effective coverage per access point (after roaming overlap)

**Key:** ap_cov

**Type:** number

**Default:** 750

**Min:** 50

**Step:** 50

**Unit:** m2

**Help:** Rule of thumb for racked areas, already reduced for the overlap needed to roam; confirm with a site survey.

#### Peak concurrent scanner users per shift

**Key:** peak_users

**Type:** slider

**Default:** 25

**Min:** 1

**Max:** 150

**Step:** 1

**Unit:** users

#### Shifts per day

**Key:** shifts

**Type:** number

**Default:** 2

**Min:** 1

**Max:** 4

**Step:** 1

#### Devices shared across shifts

**Key:** shared

**Type:** select

**Default:** 1

**Options:**

##### Yes

**Value:** 1

##### No, one per user per shift

**Value:** 0

#### Spare devices (charging, repair)

**Key:** spare

**Type:** slider

**Default:** 15

**Min:** 0

**Max:** 50

**Step:** 5

**Unit:** %

#### Posted transactions per user per peak hour

**Key:** tx_user

**Type:** number

**Default:** 30

**Min:** 1

**Step:** 1

**Unit:** transactions

**Help:** Several scans usually make up one posted transaction.

#### Employees clocking at one shift change

**Key:** employees

**Type:** number

**Default:** 150

**Min:** 0

**Step:** 5

**Unit:** people

#### Shift-change window

**Key:** window

**Type:** number

**Default:** 10

**Min:** 1

**Step:** 1

**Unit:** minutes

#### Seconds per clock transaction

**Key:** sec_clock

**Type:** number

**Default:** 6

**Min:** 1

**Step:** 1

**Unit:** seconds

**Outputs:**

#### Access points

**Key:** aps

**Expr:** ceil(area / ap_cov)

**Format:** integer

**Primary:** true

**Description:** Area divided by effective coverage per access point.

#### Scanner devices to buy

**Key:** devices

**Expr:** ceil(peak_users * if(eq(shared, 1), 1, shifts) * (1 + spare / 100))

**Format:** integer

**Primary:** true

#### Peak posted transactions per hour

**Key:** tph

**Expr:** peak_users * tx_user

**Format:** number

#### Peak posted transactions per minute

**Key:** tpm

**Expr:** tph / 60

**Format:** decimal

#### Time Track kiosks for shift change

**Key:** kiosks

**Expr:** ceil(employees * sec_clock / (window * 60))

**Format:** integer

**Description:** Kiosks needed so everyone can clock within the window.

**Chart:**

#### Devices and peak transactions per hour vs peak users

**Type:** line

**X:** peak_users

**From:** 5

**To:** 100

**Steps:** 20

**Series:**

- devices
- tph

**Disclaimer:** All coverage and throughput figures are editable rules of thumb for planning, not Infor figures. A wireless site survey decides the real access point count and placement.

## Content

**Intro:** This calculator sizes the hardware side of an Infor Factory Track Warehouse Mobility and Time Track rollout: Wi-Fi access points, scanner devices with spares, peak transaction load and the number of Time Track kiosks needed at shift change. Every assumption is an input you can change.

**Sections:**

#### How to use it

**Body:** Enter the floor area that scanners must reach, including dock doors, mezzanines and yard areas if used. Set coverage per access point to what your wireless team expects for your racking; dense metal racking and tall pallet storage shrink coverage. Enter peak concurrent scanner users on the busiest shift, whether devices are shared across shifts, and a spare percentage for charging and repair. For Time Track, enter how many people clock in a single shift-change window and how long one clock transaction takes at the kiosk.

**Bullets:**

- Use the busiest hour, not the daily average, for transactions per user.
- Count mezzanines and cold rooms as separate areas; they often need their own access points.

#### The formulas

**Body:** Access points = ceiling(area / effective coverage per access point), where effective coverage already allows for the overlap needed to roam. Devices = ceiling(peak users x (1 if shared, otherwise shifts) x (1 + spare)). Peak posted transactions per hour = peak users x posted transactions per user per hour. Kiosks = ceiling(employees x seconds per clock / window seconds), which assumes clocking is spread evenly across the window; queues form if everyone arrives in the last two minutes. These are planning rules of thumb, not Infor sizing guidance; the server side of Factory Track should be sized from Infor's own requirements for your release.

#### Worked example

**Body:** With the defaults, 8,000 m2 at an effective 750 m2 per access point gives 11 access points. Twenty-five peak users with shared devices and 15 percent spares need 29 scanners. At 30 posted transactions per user per hour, the floor posts about 750 transactions per hour, roughly 12.5 per minute, at peak. For Time Track, 150 people at 6 seconds each over a 10 minute window need 2 kiosks; 300 people would need 3. The sweep chart shows devices and transaction load growing with peak users.

#### Why wireless problems look like application problems

**Body:** Most reports of Factory Track freezing or failed transactions on the floor are wireless issues: dead spots between racks, slow roaming between access points while a user walks an aisle, or devices clinging to a distant access point. A transaction sent during a roam can time out and leave the user unsure whether it posted, which leads to double scans. Survey with the actual scanner model, test roaming down every aisle, set sensible session timeouts, and keep spares charged. Factory Track is available on Android devices through the Factory Track app as well as through a browser, so check the Factory Track administrator guide for the Android app for supported setup before buying devices.

**Cta:** If you want to see Factory Track transaction volumes and failures explained in plain English from your own data, we can add a private AI layer on your servers.

**Faq:**

#### How many Wi-Fi access points does a warehouse need?

**Answer:** It depends on racking, ceiling height and building materials. Open areas may get well over 1,000 m2 per access point, dense high racking far less. Use this calculator for a budget figure, then let a site survey with your scanners decide the number and placement.

#### Is there an Infor Factory Track Android app?

**Answer:** Yes. Infor publishes Factory Track user and administrator guides for the Android app, for CSI and LN. Install and configure it as the administrator guide for your release describes, rather than side-loading an APK from an unofficial source.

#### Why do Factory Track transactions fail when users move around?

**Answer:** Usually because the device loses or changes its wireless connection mid-transaction. Roaming delays, coverage gaps and power-saving settings on the device are common causes. Check the access point logs at the time of the failure before looking at the application.

#### How many spare scanners should we keep?

**Answer:** Many sites keep 10 to 20 percent spares to cover charging, repairs and breakages. Shared devices across shifts need more spares, because there is no idle time for batteries to charge between users.

## Search terms

infor factory track wireless connectivity issues, infor factory track app, infor factory track android app, infor factory track apk, factory track scanner sizing, warehouse wifi access point calculator, time clock kiosk calculator

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json