A.R.M.O.R. Administration

#623002

Effortless Administration defines the web-based software extensions of the A.R.M.O.R. suite. Your initial step is to establish your users, vehicles, drivers, groups, alerts, triggers, stop-arm, panic button and custom notifications. Then, you configure your options and reports for any connected vehicle and let the software save you time and money by executing the work for you.

Manage the following with Administration:

  • DVRs
  • Vehicles
  • Vehicle groups
  • Event notifications
  • Driver schedules
  • Email summaries
  • Activity reporting across entire software solution
  • DVR, vehicle and software information and maintenance
  • Automatic event download
  • Download scheduling by priority

A.R.M.O.R. software screen images subject to change due to constant evolution based on customer input and feedback.

Minimum System Requirements for ARMOR

Hardware

ARMOR Sentry server (main server which includes the ARMOR web app and SQL)*

  • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
  • Memory: 16 GB
  • Gigabit network adapter
  • 500GB system drive
  • Reference hardware example: Dell T110 (tower) or Dell R320. (rack mount)
    ARMOR Agent servers (additional server which allocates more resources for job processing, like downloads and conversions)

  • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
  • Memory: 6GB
  • Gigabit network adapter
  • 500GB system drive
  • ARMOR is supported on physical hardware as well as virtual (VMware or Hyper-V).
    *The Main server will support up to 100 buses. Depending on usage, it’s recommended to add 1 agent server per additional 100 buses.

  • Video Repository
  • 2TB of usable drive space. For fleets over 100 buses, 3TB or larger of network attached storage is recommended.

Software

  • Windows Server Standard Edition* 2012 R2, to include installation of IIS
  • SQL Server Standard Edition* 2014
  • Silverlight
  • PowerShell version 4.0 or later
  • TeamViewer version 9 (preferred) or other remote access software mutually agreed upon by the customer and REI. NOTE: Customer licensing of TeamViewer is not required. Remote access will be obtained using REI TeamViewer licenses.
  • *NOTE on Client Access Licenses (CALs):

  • Windows: The customer must have a number of CALs to cover the number of end users. This may already be covered by per-seat licensing within their environment.
  • SQL: If the customer opts for the Server/CAL licensing model, the customer is responsible for obtaining sufficient number of CALs for each anticipated end user AND for each DVR (bus).
  • Wireless Infrastructure

    If the customer requires lot-based Wi-Fi capability, the wireless infrastructure should be designed and installed to:

  • Support 802.11g or 802.11n in the 2.4 GHz range
  • Support WPA2 encryption
  • Must have a minimum of -65 dBm coverage for all points on the lot
  • Print

    Description

    Effortless Administration defines the web-based software extensions of the A.R.M.O.R. suite. Your initial step is to establish your users, vehicles, drivers, groups, alerts, triggers, stop-arm, panic button and custom notifications. Then, you configure your options and reports for any connected vehicle and let the software save you time and money by executing the work for you.

    Manage the following with Administration:

    • DVRs
    • Vehicles
    • Vehicle groups
    • Event notifications
    • Driver schedules
    • Email summaries
    • Activity reporting across entire software solution
    • DVR, vehicle and software information and maintenance
    • Automatic event download
    • Download scheduling by priority

    A.R.M.O.R. software screen images subject to change due to constant evolution based on customer input and feedback.

    Specs

    Minimum System Requirements for ARMOR

    Hardware

    ARMOR Sentry server (main server which includes the ARMOR web app and SQL)*

    • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
    • Memory: 16 GB
    • Gigabit network adapter
    • 500GB system drive
    • Reference hardware example: Dell T110 (tower) or Dell R320. (rack mount)
      ARMOR Agent servers (additional server which allocates more resources for job processing, like downloads and conversions)

    • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
    • Memory: 6GB
    • Gigabit network adapter
    • 500GB system drive
    • ARMOR is supported on physical hardware as well as virtual (VMware or Hyper-V).
      *The Main server will support up to 100 buses. Depending on usage, it’s recommended to add 1 agent server per additional 100 buses.

    • Video Repository
    • 2TB of usable drive space. For fleets over 100 buses, 3TB or larger of network attached storage is recommended.

    Software

  • Windows Server Standard Edition* 2012 R2, to include installation of IIS
  • SQL Server Standard Edition* 2014
  • Silverlight
  • PowerShell version 4.0 or later
  • TeamViewer version 9 (preferred) or other remote access software mutually agreed upon by the customer and REI. NOTE: Customer licensing of TeamViewer is not required. Remote access will be obtained using REI TeamViewer licenses.
  • *NOTE on Client Access Licenses (CALs):

  • Windows: The customer must have a number of CALs to cover the number of end users. This may already be covered by per-seat licensing within their environment.
  • SQL: If the customer opts for the Server/CAL licensing model, the customer is responsible for obtaining sufficient number of CALs for each anticipated end user AND for each DVR (bus).
  • Wireless Infrastructure

    If the customer requires lot-based Wi-Fi capability, the wireless infrastructure should be designed and installed to:

  • Support 802.11g or 802.11n in the 2.4 GHz range
  • Support WPA2 encryption
  • Must have a minimum of -65 dBm coverage for all points on the lot
  • A.R.M.O.R. Administration

    #623002

    Description

    Effortless Administration defines the web-based software extensions of the A.R.M.O.R. suite. Your initial step is to establish your users, vehicles, drivers, groups, alerts, triggers, stop-arm, panic button and custom notifications. Then, you configure your options and reports for any connected vehicle and let the software save you time and money by executing the work for you.

    Manage the following with Administration:

    • DVRs
    • Vehicles
    • Vehicle groups
    • Event notifications
    • Driver schedules
    • Email summaries
    • Activity reporting across entire software solution
    • DVR, vehicle and software information and maintenance
    • Automatic event download
    • Download scheduling by priority

    A.R.M.O.R. software screen images subject to change due to constant evolution based on customer input and feedback.

    Specs

    Minimum System Requirements for ARMOR

    Hardware

    ARMOR Sentry server (main server which includes the ARMOR web app and SQL)*

    • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
    • Memory: 16 GB
    • Gigabit network adapter
    • 500GB system drive
    • Reference hardware example: Dell T110 (tower) or Dell R320. (rack mount)
      ARMOR Agent servers (additional server which allocates more resources for job processing, like downloads and conversions)

    • CPU: Quad Core Intel Xeon @ 3.0GHz or equivalent
    • Memory: 6GB
    • Gigabit network adapter
    • 500GB system drive
    • ARMOR is supported on physical hardware as well as virtual (VMware or Hyper-V).
      *The Main server will support up to 100 buses. Depending on usage, it’s recommended to add 1 agent server per additional 100 buses.

    • Video Repository
    • 2TB of usable drive space. For fleets over 100 buses, 3TB or larger of network attached storage is recommended.

    Software

  • Windows Server Standard Edition* 2012 R2, to include installation of IIS
  • SQL Server Standard Edition* 2014
  • Silverlight
  • PowerShell version 4.0 or later
  • TeamViewer version 9 (preferred) or other remote access software mutually agreed upon by the customer and REI. NOTE: Customer licensing of TeamViewer is not required. Remote access will be obtained using REI TeamViewer licenses.
  • *NOTE on Client Access Licenses (CALs):

  • Windows: The customer must have a number of CALs to cover the number of end users. This may already be covered by per-seat licensing within their environment.
  • SQL: If the customer opts for the Server/CAL licensing model, the customer is responsible for obtaining sufficient number of CALs for each anticipated end user AND for each DVR (bus).
  • Wireless Infrastructure

    If the customer requires lot-based Wi-Fi capability, the wireless infrastructure should be designed and installed to:

  • Support 802.11g or 802.11n in the 2.4 GHz range
  • Support WPA2 encryption
  • Must have a minimum of -65 dBm coverage for all points on the lot