The System Settings module is a collection of customizable settings that affect all aspects of the Powerfleet system. The settings are broken down into categories separated by green bars. Please note that some of the features covered in this article may not be available to you. Availability is based on your specific site license. Accessibility may be based on role restrictions set by the System Administrator.

• Expand All displays all the details for each section.
• Collapse All hides all the details for each section.
• Click ˅ and ˄to toggle between displaying and hiding section details.
• Search: Expand all sections and use Control+F (or your browser's standard search function) to search for the topic you are interested in.

---

NOTE: If you are a new customer preparing Warehouse IoT to go live for the first time, please review our implementation quick start guide Before You Go Live - Warehouse IoT System Settings* attached below.*

---

Checklists
Items in this section pertain to safety and operator job selection (job codes) checklists 

Enforce checklist compliance rules for
When checked, operators with Master and Maintenance authorization are held to the same compliance rules as Standard operators

Countdown for completing compliance requirement for safety and job selection checklists
Determines the amount of minutes an operator has to complete a safety or job checklist before becoming non-compliant

Override non-compliance behavior profile assignments, log the operator off and reset the countdown instead
When enabled, the VAC automatically logs the operator off and reset the countdown when the countdown expires, thus preventing non-compliance events from happening.

Job selection compliance type
Determines the rules for a vehicle to be compliant for job checklists

• No Compliance Required = Operators do not have to complete checklists, will not be presented a countdown and will not be subject to non-compliance events
• Once per period = Any operator needs to complete the job checklist within N hours of the last time it was completed
• Oper/Vcl Pair Per Period = Each unique operator that uses the vehicle needs to complete the job checklist within N hours of the last time that operator completed it
• Consecutive Oper Use Per Period = The job checklist needs to be completed every time a different operator accesses the vehicle.  When the same operator uses the vehicle consecutively, they only need to complete the checklist if they haven’t completed it within N hours.
• Once per shift = Any operator needs to complete the job checklist the first time the vehicle is accessed for each configured shift (see shift section for configuring shifts)
• N = Job selection compliance period

​Job selection compliance period   
Number of hours the vehicle is compliant after a job checklist is completed (subject to compliance type rule)

Safety compliance type
Determines the rules for a vehicle to be compliant for safety checklists.

• No Compliance Required = Operators do not have to complete checklists, will not be presented a countdown and will not be subject to non-compliance events
• Once per period = Any operator needs to complete the safety checklist within N hours of the last time it was completed
• Oper/Vcl Pair Per Period = Each unique operator that uses the vehicle needs to complete the safety checklist within N hours of the last time that operator completed it
• Consecutive Oper Use Per Period = The safety checklist needs to be completed every time a different operator accesses the vehicle.  When the same operator uses the vehicle consecutively, they only need to complete the checklist if they haven’t completed it within N hours.
• Once per shift = Any operator needs to complete the safety checklist the first time the vehicle is accessed for each configured shift (see shift section for configuring shifts)
• N = Safety selection compliance period

Safety compliance period
Number of hours the vehicle is compliant after a safety checklist is completed (subject to compliance type rule)

Randomize the location of the safety checklist answers  

• Yes = Pre-selected answers to checklist questions are randomly determined
• No = The #1 checklist answer is pre-selected for each question

System Settings – Impact Management

Items in this section pertains to the impact sensor data 
Profile

• AAA Impact = Standard automated impact calibration process
• Legacy = Custom manual impact calibration process for obsolete hardware

Severity Range Definitions
Slider bar that determines how the VAC will categorize impacts based on the ratio of the impact to the minimum impact level

• Low = Minimum impact ratio and this slider cannot be moved
• Moderate = Slider should be moved to the lowest desired ratio that will result in an impact categorized as Moderate; any impacts below this slider will be categorized as Low
• Medium = Slider should be moved to the lowest desired ratio that will result in an impact categorized as Medium; any impacts below this slider will be categorized as Moderate
• High = Slider should be moved to the lowest desired ratio that will result in an impact categorized as High; any impacts below this slider will be categorized as Medium
• Severe = Slider should be moved to the lowest desired ratio that will result in an impact categorized as Severe; any impacts below this slider will be categorized as High
• Max = Maximum impact ratio and this slider cannot be moved

Sigma Factor
Customer factor used for adjusting the impact algorithm base calculations.  Standard entry is zero 

System Settings – License

Items in this section pertain to the licensed features applied to the site 

Software License ID
Alphanumeric string that defines the license key applied to the site.  License keys can be acquired from the I.D. Systems’ Support team.  Paste or type a new license into this field in order to change the license key.  The “Analyze” button allows you to see what the pending changes will be to a newly entered license key prior to saving the change

VAC license ID
These two license keys are what appear in a VAC synchronized with the software.  They are not editable but will change if a new software license key is entered.  When configuring a new VAC, these keys should be entered at the license key entry step.  The left box is the top license, the right box is the bottom license

Customer Type
Read-only field based on the license key applied

System Type
Read-only field based on the license key applied

System Settings - Licensing
Read-only representation of what features are enabled (check boxes) and disabled (empty boxes) based on the license key entered

Pending Licensing Configuration
When applying a new license key and pressing the “Analyze” button, this section displays pending changes (these changes are also highlighted in green text in the licensing section)

Electronic ID Profile

• ID Pattern = Pattern the VAC uses to decode the ID presented
• Login Length = Not used (should always be 3)
• Option = Not used (should always be 1)
• Digits to skip = number of digits to skip from the start of the ID read
• Digits to use = number of digits to read from the ID

System Settings – Maintenance

Items in this section pertain to the planned maintenance feature. 

Minutes prior to scheduled maintenance to display message to operator
The number of minutes before a planned maintenance event is due that a message will be displayed to a vehicle operator

System Settings – Messaging

Items in this section pertain to the messaging feature. 

Seconds between sending text messages
Number of seconds the software waits between sending test message to a VAC

Time until a message is removed from the 'send' queue and WAMs; it is then queued again if it is not expired
Minutes a pending message is made available for a VAC before it is re-evaluated for its expiration date.  If expired, the message is no longer available.

System Settings – Operators

Items in this section pertain to operators in the system 

ID authorization level evaluation while in Any ID mode
For systems that use iButton VACs, this feature determines how to interpret an unknown ID when it is read and the system is in Any ID mode.  Set the values desired to automatically associated different iButtons as Standard, Master and Maintenance operators

Maintenance Operators Automatic log-off when inactive
Amount of consecutive inactivity that results in a Maintenance operators being logged off automatically

• Use VAC setting = Use the time setting for idle timeout of the behavior profile assigned to the vehicle
• N mins = Operator is logged out after N minutes of inactivity

Master Operators Global Profiles

• All Vehicles = Master operators can log into any vehicle in the fleet, regardless of the groups the Master operator is assigned to.
• Assigned Groups = Master operators can only log into vehicles that the operator has a valid group assignment for

Master Operators Output alerts for configured events

• Yes = Output alert (alarm, strobe, etc.) will function for configured events for Standard and Master operators (for applicable vehicles)
• No = Output alert (alarm, strobe, etc.) will function for configured events only for Standard operators (for applicable vehicles)

Skill level vehicle control
For iPort vehicles, these setting control the maximum performance of the vehicle based on the skill level assigned to the operator in their group assignments.  Soft, Medium and Hard settings are as determined by the vehicle manufacturer

Temporary Operators Authorization Hours
Number of hours a temporary ID is enabled for when assigned at a VAC.  See VAC user guide for how to assign temporary IDs

Temporary Operators Authorized When
Determines whether or not a temporary ID can be used based on the VAC synchronization status

• VAC partially syncd = Allows temporary IDs to be used before the VAC synchronizes
• VAC fully syncd = Disabled temporary IDs until the VAC synchronizes

Allow login using keypad entry for IDSY hardcoded IDs

• Yes = Allows operators to log in with one of the default IDSY user IDs
• No = Prevents operators from logging in with one of the default IDSY user IDs

Evaluate operator authentication in while logged in

• Checked = If an operator ID becomes suspended or unlicensed while the operator is logged in, the VAC will log them off at the next idle period and prevent them from logging in again until they are licensed
• Unchecked = If an operator ID becomes suspended or unlicensed while the operator is logged in, the VAC allows them to stay logged in until they log off for a standard reason (idle timeout, event lockout, logoff button, etc.)

Break mode countdown
Minutes the vehicle is in break mode from the point of activating break mode

• Disabled = Break mode is not available on the VACs
• N mins = number of minutes break mode is active for

Deactivate Operator when MVAV detected

• Checked = Operator is set to ‘suspended’ when a multiple vehicle access violation occurs
• Unchecked = Operator stays licensed even after a multiple vehicle access violation occurs

System Settings – Sensors

Items in this section pertain to sensors connected to vehicles in the system 

Fork Load

• Lift Drop Filter =  Seconds the forks need to be lowered before a ‘drop’ is recorded for a trip record
• Minutes after lowering forks before trip gap records starts = Minutes after the load is dropped before the VAC starts a new record recording time between loaded trips

Output Alert

• Available 

• Always = Alarm will trigger if an event happens even if no one is logged in

• Only When Operator Logged In = Alarm will not trigger if an event happens and no one is logged in

• Activation Pattern – when alarm is triggered (until event is cleared)

• Cycle on/off every ½ second = Alarm will turn on and off 2 times per second

• Cycle on/off every 1 second = Alarm will turn on and off once per second
• Cycle on/off every 2 second = Alarm will turn on and off once every 2 seconds
• Constantly On = Alarm will be on constantly until the event is cleared (typically used for ‘creeper mode’)
• Disabled = Alarm will not trigger

Tow

• Minimum tow presence to create an event = Minimum amount of consecutive time the tow sensor must sense a load before a tow record is recorded
• Minimum tow presence percentage = After a tow is registered, minimum amount of time the load must be sensed for a tow record to continue.  For example, if the tow disappears for 1 second out of a 10 second sample, it remains in tow but if the load is not sensed for 3 seconds of a 10 second period, the tow record stops
• Tow full stop filter = Amount of time the vehicle must be stopped during a tow record to count of a tow stop, followed by a tow start

System Settings – Server

Items in this section pertain to server configuration for the system 

Client alias

• Client code = IDSY internal code to identify the customer name. Shows up on VAC when VAC is synchronized with software
• Site code = IDSY internal code to identify the customer’s site name. Shows up on VAC when VAC is synchronized with software
• Facility ID and CheckSum = IDSY unique internal codes associated with each site. Must be consistent with the ‘Facility ID’ in the VAC Access Control menu

Data Archive 
Amount of time the referenced data type is stored in the Warehouse IoT database (and available in the Warehouse IoT report tool) prior to being archived. Once archived, the data cannot be viewed through the Warehouse IoT database without being restored by an I.D. Systems’ Support resource

Outbound Messages   

• No = Normal mode
• Yes = Writes all data communication between VAC and Warehouse IoT to log files

Services – WiFi debug

• Checked = Writes all Wi-Fi diagnostic data to log files
• Unchecked = Normal mode

Schedule Events
Frequency that each item automatically happens

• Enforce people and vehicle expirations = reviews assigned license, medical, certification and group expiration dates and suspends access for dates prior to the date/time the event runs
• ForceFull Vehicle Synchronization = All vehicles complete a full synchronization of each category
• Retries for failed events = number of times each of the scheduled events in this category will retry should the initial attempt fail
• Distribute Batched Subscriptions = Sends emails and/or SMS messages for all events that are defined for batch distribution rather than immediate notification
• Reset WAM Date and Time = Synchronizes the date and time of the WAM with the date and time of Warehouse IoT
• Daily event timer = Minimum time between executing scheduled events (default 5 seconds)
• Update WAM Configuration = Synchronizes the assigned Warehouse IoT WAM settings to the WAM
• Send System Health statistics = Sends health statistics from the Warehouse IoT site to the central IDSY data repository for system health verification
• Send System Health Performance Statistics = Sends performance statistics from the Warehouse IoT site to the central IDSY data repository for system performance  verification
• Automated People feed from external source = Synchronizes people loaded in Warehouse IoT from external people management software (when configured)
• Force Incremental Vehicle Synchronization = All vehicles complete a synchronization updates based on changes since the last incremental or full synchronization

Time Settings for data presentation

• Time Zone: Determines the data and time data is presented in.
• Session Timeout: The timeframe of Warehouse IoT software inactivity prior to an automatic software logoff.  Options: 5, 15, 30, 60, 120, or 180 minutes.

System Settings – Shift

Shifts are used for multiple purposes in Warehouse IoT. They can be used for:  

• Separating data collection
• Analysis of data in the reporting tool
• ​Determining checklist compliance of vehicles and operators

​Any number of shifts can be configured per day. Regardless of shifts configured, the system automatically creates and end-of-shift record at the site local midnight time daily to allow for daily data comparisons when operators logins span multiple calendar days.

Default shifts are configured in Warehouse IoT as follows:

• First Shift = Sunday Through Saturday, 6 am to 2 pm
• Second Shift = Monday Through Friday, 2 pm to 10 pm; Saturday and Sunday, 2 pm to 6 am
• Third Shift = Monday Through Friday, 10 pm to 6 am

Adding a new shift

1. Click the Clear button in the top section of the configuration view
2. Enter new details for name and shift parameters
3. Click the Add button (note you still need to click “Save” at the bottom of the screen to save the changes to the system)

Editing an existing shift

1. Click on the shift you want to change in the ‘calendar view’
2. The details of that shift will appear in the top section of the configuration view
3. Change the required fields:

• Shift Name – for reference in the UI and report filters
• Shift Description – notation for UI only
• Days of the week – Picks which days of the week the shift will be applied to (All button selects all 7 days)
• Shift Start Time – the time the shift will begin.  Note you do not specify a shift end time as the shift will end at the next shift’s start time
• Update – applies the changes made in the top section to the calendar view (note you still need to click “save” at the bottom of the screen to save the changes to the system)
• Clear – Clears all settings for the shift

Deleting an existing shift

Click the red ‘x’ to the left of the “Sunday” column in the in the shift summary section (note you still need to click “save” at the bottom of the screen to save the changes to the system)

System Settings – Vehicles

Items in this section pertain to vehicle settings in the system ​

Data upload characteristics

• Auto-scan interval = Number of hours or days of no iRF communication before the VAC begins scanning other frequencies.  (0 = disable auto-scan)
• Auto-scan interval type = Hours or Days setting for auto-scan (see above entry)
• Message retry = Consecutive times a VAC will try and resend data without hearing a confirmation from Warehouse IoT
• Transceiver timer (milli seconds) = How long the VAC will wait for Warehouse IoT to respond to a message
• Maximum message inbound interval = Maximum number of messages a VAC will try and send in a 5 second period
• Portal record interval (seconds) = Not used (default 255)

Device data generation

• Frequency = Rate the VAC generates data records (Reduced, Standard or Escalated)
• Create detection data while in motion (seconds) = Seconds of motion time registered before creating a detection record (Read-only field, changes with ‘Frequency’)
• Create detection data while idle (minutes) = Minutes of stationary or idling time before creating a detection record (Read-only field, changes with ‘Frequency’)
• Number of data records collected (without log-off, log-on, or event) before sending detection packet = Number of consecutive records created before sending them to the software (Read-only field)
• VAC creates location records when out of communication range
• Checked = will continue to create location records when out of range and the records will be send when the VAC returns to range
• Unchecked = does not create location records when out of range (location is not known during historical search for periods out of range)
• Minutes after changing states between idle and motion before changing data generation profile = Minutes the VAC waits before changing data record creation interval

VAC Firmware Upgrade

• New Wireless Upgrade Available – “Get New Firmware” button is enabled when new firmware is available for the site; once button is pressed the firmware is saved for distribution to VACs

• Wireless upgrade method – Determines how the firmware is distributed and installed on VACs

• Turned off = Firmware will not be sent to VACs for download

• Distribute firmware, automatically install = Firmware is sent to all VACs.  Each device installs the firmware as soon as it receives the complete file and the vehicle is not in use
• Distribute firmware, Request install by any user = Firmware is sent to all VACs.  Each device prompts anyone who logs in to install the update as soon as it receives the complete file
• Distribute firmware, Request install by Master user = Firmware is sent to all VACs.  Each device prompts any Master operator who logs in to install the update as soon as it receives the complete file
• Distribute firmware, Request install by Maintenance user = Firmware is sent to all VACs.  Each device prompts any Maintenance who logs in to install the update as soon as it receives the complete file
• Distribute firmware, Request install by Admin user = Firmware is sent to all VACs.  Each device prompts an IDSY user who logs in to install the update as soon as it receives the complete file
• Pending Firmware Version – Displays the version of firmware saved for distribution to VACs
• Pending Firmware – This section shows the last known status of each VAC type by firmware type when the screen was last refreshed. Example: “0/3” means zero of three VACs needing the update have completed the update
• VAC Jack upgrade - The ‘download files’ button allows the software user to download firmware upgrade files to a computer.  These files can be copied to a USB drive and VACs can be upgraded at the device using a VAC Jack (this is an alternative to wireless upgrade)

Languages

Each language checked is made available for operators to choose on the VAC.  Once chosen, the VAC will display content in that language.  You do not need to check the language chosen as the ‘Primary Language’.  Only 3 languages can be chosen in addition to the primary language

Login Options

• Allow login using keypad entry of operator ID

• Yes = allows operators to use keypad entry of login IDs

• No = Operators must us electronic IDs to access vehicles

• Log off when an operator ID is presented while already logged in

• Yes = Logs the operator off when an ID is read by the card reader (the same ID or another ID)

• No = operators are only logged off by pressing the logoff button, an even lockout, or idle timeout

• Access control mode

• Any ID = Allows anyone with a compatible ID to log into a VAC, and the VAC will not enforce event shutdowns

• Registered ID = Requires IDs to be synchronized and authorized to log into a VAC and access a vehicle; event shutdowns are enforced
• Days a VAC is powered and out of communication range before it automatically transitions to Any ID mode = safety feature to allow someone to log into a VAC and use a vehicle after the selected amount of days out of range
• After last button press back light stays on for = Amount of time the VAC backlight stays on after a button press

• Turn off the VAC screen while the VAC senses motion

• Checked = VAC screens is blank when the VAC senses motion

• Unchecked = VAC display remains on when the VAC senses motion

• Disable green LED when logged in

• No = when someone is logged in, the green LED is on

• Yes = when someone is logged in, the green LED is off

• Display current login usage statistics on VAC

• No = VAC uses standard screens while logged in

• Yes = enables a ‘Stats’ option in the menu. When selected, the operator can see accumulated activity metrics for the current login period
• Amount of consecutive inactivity (idle time) before an operator is automatically logged off
• Amount of consecutive logged off time before the vehicle hardware enters sleep mode

• Login technology – Setting for the VAC to choose ID reader

• Local = Standard configuration that allows the VAC to decide what ID reader to use based on the VAC configuration

• Others = Forces the VAC to the configuration setting in the software regardless of how it was set up during vehicle configuration

• System compatible with incremental synchronization

• No = VAC will only complete full synchronization (see Server Settings)

• Yes = standard configuration that allows incremental changes to be sent to the VAC
• Vehicle lockout warning countdown = Number of seconds the VAC will display a countdown before locking out due to an event

System Settings – Visibility

Items in this section pertain to location tracking and mapping of vehicles in the system 

Stationary maximum change
Not used, do not change.

Time decay alpha
Not used, do not change.

Time slot count to calculate
Not used, do not change.

Use new stationary algorithm
Do not uncheck.

Automatic asset relocation
Not used, do not change.

Display events alert icons for events that occurred within the last
Select the number of events to display icon for.  Events are displayed from newest to oldest

Display time stamp for every record during playback mode  

• Yes = During breadcrumb playback, each point in the playback will show the date/time the event occurred at the point it occurred.
• No = Points of a breadcrumb trail do not display timestamps; however, the information is available by hovering over the point.

Display WAM communication range

• Checked = When WAMs are displayed, approximate coverage area is displayed as well.
• Unchecked = WAM coverage range is not displayed.

Frequency to retrieve system status
Not used, do not change

Item image
Determines the relative size of each icon displayed on the map (vehicles, people, WAMs, etc.)

Minutes since last detection before map indicates a vehicle is out of range
Minutes of data (not real-time minutes) not being reported by the VAC before the vehicle displays as out of range on the map.

Zone violation audible alert on computer

• Yes = Provides an audible alert on the user’s computer when a zone violation occurs.
• No = Zone violations do not make audible alerts on the users computer.

System Settings – WAM

Items in this section pertain to Wireless Asset Managers (WAMs) 

Transmission Frequency

• Data = RF frequency in MHz that data (usage, events, etc.) is transmitted between WAMs and VACs
• Location = RF frequency in MHz that location records are transmitted between WAMs or Beacons and VACs
• Data Rate = RF data rate that information is transferred at

Transmission Profile

• Seconds WAMs wait between wireless settings messages = Determines how frequently WAMs send messages
• Number of attempts WAMs wait before a request message times out = How many reties a WAM goes through before expiring a message attempt
• Number of messages WAMs skip if a failure occurs = When message attempt expires, WAMs wait this many more messages before trying to send messages again
• Interval between WAM and Beacon location identification messages broadcast to devices = Time between sending location messages for VACs to triangulate with when using WAM/Beacon-based location
• Minutes between Beacon check-ins to validate configuration = How frequently Beacons check in with WAMs to validate if they have the correct configuration
• Region = Region used to determine RF range applicable to WAMs, Beacons and VACs

System Settings – WiFi

Items in this section pertain to Wi-Fi communication between VACs and Warehouse IoT. Security profiles entered in this section are synchronized to VACs when they connect to the software.  This can be used to send new credentials to VACs when transitioning between profiles. VACs can synchronize up to 9 ‘personal’ profiles or 1 ‘enterprise’ profile. To enter security profiles, press the “Add security profile” button and follow the onscreen prompts for information.

Power down Wi-Fi radio between connection attempts

• Yes = VAC Wi-Fi radio shuts down between attempts to connect to the software via the Wi-Fi network
• No = Wi-Fi radio remains powered as long as the VAC is in normal power mode (Radio shuts down when VAC is in Hibernate mode)

Module Boot Commands (Hit Enter key for next line)
Various commands that tell the Wi-Fi radio what to do when powering up (either after a shutdown period or when the VAC wakes from power loss or Hibernate). Default commands are inserted as required

VAC attempts to Connect to the Server  
Determine when the VAC attempts to connect to the software through the Wi-Fi infrastructure  

• Always when in range = VAC will try to connect whenever it is in range of an Access Point using the security credentials the VAC is programmed with
• Once every N = VAC only tries to connect to the software through the available Wi-Fi infrastructure one time per period chosen.  If the connection fails, it waits the same period to try again

System software host server identification

• Type = Server security type, Private or Public
• DNS Name = DNS name identification of server hosting the Warehouse IoT software.  Alternatively, you can use the server IP Address.
• IP Address = IP Address of server hosting the Warehouse IoT software.  Alternatively, you can use the DNS name.
• Port = Port associated with the DNS named or IP Address of the Warehouse IoT host server

Profile details
Options vary by profile type.

• Profile Name = User defined name of choice
• Profile Description = User description of choice
• SSID = SSID Access Points and VAC will use to access the network
• Security Type = Security type Access Points and VAC will use to access the network
• Encryption Type = Encryption type Access Points and VAC will use to access the network

Security Credentials
Credential information available for selection and entry vary based on the profile details entered.

Attachments

• VP-Before You Go Live.pdf