ONE20 Inc. is going out of business

By | Blog

June 18 of 2018, ONE20 inc. is going out of business.

As of this date, ONE20 apps will no longer work but we can help your business stay ahead of the loss. TeMeDa is able to provide immediate support for your ELD needs using your existing hardware. Our team is standing by ready to assist you in providing continuous ELD support.

Contact us via email at customer.support@temeda.com or call us at 855-289-7821.

TeMeDa App 2.12.0

By | Release Notes

Table of Contents

  1. Account Hierarchy – 5 Levels (part 2 of 3)
  2. Asset Detail – added ability to edit Hierarchy
  3. New Alert: Time Limit Exceeded and No Movement outside Location(s)
  4. Locations, Zones, Projects – set Active or Inactive
  5. Locations on History Trail View
  6. Manage Account Notifications via Admin Menu
  7. International Language support for Assets and Alerts
  8. Quick Groups added to Grid
  9. New User Role – Restricted Admin

Account Hierarchy 2

In TeMeDa app v2.12 we have added support for customers to create their own Account Hierarchies up to 5 levels deep. This feature allows a TeMeDa ‘parent’ account to create ‘child’ customer accounts, and those child customer accounts can also have their own child accounts, and so on. Admins can create any number of child accounts within 5 levels. Users can then be created and assigned to individual child accounts. Assets assigned to the parent account can be re-assigned down to child accounts. Account Hierarchy allows for clear separation of Assets, Users, Groups, Projects, Locations, Zones, Alerts, and Maintenance amongst the various business units, regions and departments within an organization. Account Hierarchy can be accessed by account Admins using the Admin, Account, Account Hierarchy menu.

Example 1: A large corporation with multiple Regions and Departments:

Parent Company ACME Logistics has 2 regions: Midwest and East. The Midwest region has 2 Departments: Operations and Logistics. The East region also has 2 Departments: Sales and Marketing. ACME parent company can assign Assets to each child Region, and each Region can re-assign those assets down to individual Departments. In this scenario, the Midwest Region has no visibility to the Assets in the East Region and vice versa. Also, the Midwest Operations Department has no visibility to Assets in the Midwest Logistics Department or any other Department.

Example 2: An OEM Manufacturer with multiple Dealerships and Customers:

Parent Company ACME Equipment has 50 dealerships with each dealership selling products to many customers: ACME Equipment can create child accounts for each dealership. Each dealership can have its own Assets, Users, Groups, Alerts, etc. that are separate from the parent account. Each dealership is isolated for others dealerships information. ACME Equipment can provide each of its dealerships with a secure and separate telematics solution. In turn, each dealership can offer this same service to its own customers. Each customer is isolated from all other customers.

Example 3: A mid-size company with many customers:

Parent Company ACME Rentals has 100 customers: ACME Rentals can create child accounts for each customer. Each customer can have its own Assets, Users, Groups, Alerts, etc that are separate from the parent account. Each customer is isolated from other customer accounts. ACME Rentals can provide each of its customers with a secure and separate telematics solution.

Account Hierarchy Examples:

Account Hierarchy Setup:

Asset Detail – Added the ability to configure Asset within Hierarchy

Customers now have the ability to set the Account Hierarchy of an Asset directly in the Asset Detail page. Prior to this release, customers needed to make Hierarchy updates in the Hierarchy List pages. Now, when adding or editing an Asset, navigate to the new “Hierarchy” tab to configure the asset within a particular account within your corporate hierarchy.

Asset Detail:

New Alert: Time Limit Exceeded and No Movement outside Location(s)

The new “Time Limit Exceeded and No Movement outside Location(s)” Alert will trigger when one or more assets is located outside one or more known geo-fence Locations, has not moved, and has been in that state for greater than the configured time period in hours.  This alert can be used to detect vehicles/operators that have stopped outside of your known work locations for an extended period of time.

Locations on History Trail

The History Trail Map view now displays an overlay of any geo-fence Locations that an Asset stopped in during the time frame selected. Locations can be toggled on/off by clicking the Show/Hide Locations button.

Location on History Trail:

Active or Inactive Locations, Zones, and Projects

Customers now have the ability to set Locations, Zones, or Projects as Active on Inactive. Only active items will show in the Accordion and Alerts. Inactive items will still show up on the Admin Menu so that they can be re-activated or deleted. This allows customers to keep all Locations, Zones, and Projects in the system but to activate only those items in use to keep the user interface clean and un-cluttered.

Location on History Trail:

Manage Account Notifications via Admin Menu

Customer Admins now have the ability to manage all alert Notifications in one central location. Admins can go to the new Admin | Account | Notifications menu to add/edit/delete alert notification email addresses and sms text message phone numbers.

Menu Button:

Notifications Window:

International Language support for Assets and Alerts

The app now has support for international characters on Asset Name, Descriptions, and Alert messages.

Quick Groups added to Grid

Admins can now quickly create Groups by using the Grid to sort/filter assets, then clicking the Add Group.

Quick Groups:

New User Role – Restricted Admin

We’ve added a new User Role named “Restricted Administrator”. A Restricted Admin has read-only visibility to all Assets in his/her organization on the Map, Accordion, Alerts, Maintenance and Reports, however, the Restricted Admin can be configured with limited Add/Edit/Delete capabilities for all system entities. System entities include Account Hierarchy, Account Notifications, Assets, Cameras, Drivers, Groups, Locations, Projects, Sensors, Unassigned Devices, and Zones. For example, an Admin can create a Restricted Admin that can only Add/Edit/Delete Account Notifications and Groups. This user cannot Add/Edit/Delete other entities such as Assets, Drivers, etc.

Smartphone App 1.1.3

By | Blog

Maintenance Logs

You can now Log Maintenance from within the app and view the Tasks associated with each service interval. We’ve added a view to see the Service History for each Asset, and you can view the Total Cost of Maintenance for your fleet or for individual Assets.

Maintenance Status and Tasks:

Maintenance Logs:

Asset Search using Barcode scanner

We’ve added the ability to find Assets using the barcode scanner on the Asset Search screen. Customers can affix any type of barcode (line, QR code, DataMatrix, etc) to their Assets and easily find those Assets using the built-in scanner in the app.

Locations with Assets on map

From the Locations menu, you can now see the Assets that are currently within the selected Location, and focus on any Asset using the Asset slider for that Location.

TeMeDa App 2.11.0

By | Release Notes

Table of Contents

  1. Account Hierarchy 1
  2. User Impersonation
  3. Primary Asset
  4. New Alert: “Location Time-Limit Exceeded”
  5. New Alert: “Location In/Out”
  6. TeMeDa API Portal – Production Release
  7. Barcode Scanner in smartphone apps

Account Hierarchy 1

In TeMeDa app v2.11 we have added support for customers to create their own Account Hierarchies. This feature allows a TeMeDa ‘parent’ account to create ‘child’ customer accounts, and those child customer accounts can also have their own child accounts. Admins can create any number of child accounts within 3 levels. Users can then be created and assigned to individual child accounts. Assets assigned to the parent account can be re-assigned down to child accounts. Account Hierarchy allows for clear separation of Assets, Users, Groups, Projects, Locations, Zones, Alerts, and Maintenance amongst the various business units, regions and departments within an organization. Account Hierarchy can be accessed by account Admins using the Admin, Account, Account Hierarchy menu.

   Example 1: A large corporation with multiple Regions and Departments

Parent Company ACME Logistics has 2 regions: Midwest and East. The Midwest region has 2 Departments: Operations and Logistics. The East region also has 2 Departments: Sales and Marketing. ACME parent company can assign Assets to each child Region, and each Region can re-assign those assets down to individual Departments. In this scenario, the Midwest Region has no visibility to the Assets in the East Region and vice versa. Also, the Midwest Operations Department has no visibility to Assets in the Midwest Logistics Department or any other Department.

   Example 2: An OEM Manufacturer with multiple Dealerships and Customers

Parent Company ACME Equipment has 50 dealerships with each dealership selling products to many customers: ACME Equipment can create child accounts for each dealership. Each dealership can have its own Assets, Users, Groups, Alerts, etc that are separate from the parent account. Each dealership is isolated for others dealerships information. ACME Equipment can provide each of its dealerships with a secure and separate telematics solution. In turn, each dealership can offer this same service to its own customers. Each customer is isolated from all other customers.

   Example 3: A mid-size company with many customers:

Parent Company ACME Rentals has 100 customers: ACME Rentals can create child accounts for each customer. Each customer can have its own Assets, Users, Groups, Alerts, etc that are separate from the parent account. Each customer is isolated from other customer accounts. ACME Rentals can provide each of its customers with a secure and separate telematics solution.

Account Hierarchy Examples:

Account Hierarchy Setup:

Account Hierarchy – New Accordion blade:

Account Hierarchy – New Filter on Admin, Users List page:

User Impersonation

Admins can now impersonate any Non-Admin users, and can impersonate both Admins and Non-Admins in child account hierarchies. This way, an Admin can replicate the experience of a user within his organization, without asking that user for his/her credentials. This allows Admins the ability to verify the accessibility of Assets, Groups, Locations, etc for any User. User impersonation is especially useful for simulating the experience of users within child account hierarchies.

Primary Asset

Assets can now have a “Primary Asset”. Only Primary Assets are displayed on the Map. This is useful for Assets that have multiple telematics devices installed on a single vehicle or piece of equipment. When multiple assets in the system are associated to a single Primary Asset, the Map will only display the Primary Assets so as to not clutter up the Map.

New Alert: Location Time-Limit Exceeded

The new “Location Time-Limit Exceeded” Alert will trigger when one or more assets is located within a geo-fence Location greater than the configured time period in hours.

New Alert: Location In/Out

The new “Location In/Out” Alert will trigger when one or more assets goes in or out of a geo-fence Location. This alert allows a simpler approach to the process of setting up both a “Location Entry” and a “Location Exit” alert for customers who want to know when an Asset enters and leaves a location.

TeMeDa API Portal – Production Release

The TeMeDa API is a set of application programming interfaces (APIs) developed by TeMeDa which allow communication with TeMeDa Services and their integration to other services. Examples of these include Asset information such as odometer and engine hours, Locations, Reports, Maintenance, History Trails, and Alerts. TeMeDa customers can use these APIs to take advantage of or extend the functionality of their existing services and internal applications.

The TeMeDa API portal provides a comprehensive list of RESTful JSON-based APIs that allow TeMeDa customers the ability to securely view, analyze and manage their telemetry devices and data. Developers can use this portal to discover and learn about the TeMeDa APIs, and can try out the various API calls right within the portal to view real-time production data in their customer account.

Barcode Scanner

The TeMeDa smartphone app and the TeMeDa Installer app now allow you to scan the telematics device serial number barcode when adding or editing Assets. This will allow Admins and Installers with the ability to quickly select devices without having to scroll through long lists of serial numbers and will help prevent the wrong device from getting entered into the app.

TeMeDa API Portal

By | Blog

TeMeDa API Portal URL

The TeMeDa API is a set of application programming interfaces (APIs) developed by TeMeDa which allow communication with TeMeDa Services and their integration to other services. Examples of these include Asset information such as odometer and engine hours, Locations, Reports, Maintenance, History Trails, and Alerts. TeMeDa customers can use these APIs to take advantage of or extend the functionality of their existing services and internal applications.

The TeMeDa API portal provides a comprehensive list of RESTful JSON-based APIs that allow TeMeDa customers the ability to securely view, analyze and manage their telemetry devices and data. Developers can use this portal to discover and learn about the TeMeDa APIs, and can try out the various API calls right within the portal to view real-time production data in their customer account.

APIs

Currently there are main 4 APIs offered on the TeMeDa API Portal:

AEMP API

The AEMP (Association of Equipment Management Professionals) API for use with the TeMeDa telematics solution. The AEMP OEM Integration Service will pull specified engine and location information from an OEM provider into your TeMeDa account. The OEM Assets will appear on the map, and can be included on Alerts, History Trail, Reports, Maintenance, etc. The data is formatted according to the AEMP (Association of Equipment Management Professionals) standard version 1.0 in xml. Includes Lat, Long, Cumulative Operating Hours, Idle Hours, and Distance (Odometer). http://www.aemp.org/ Customers who wish to setup the AEMP OEM Integration service will need to provide TeMeDa with valid credentials and url to their OEM AEMP feed. Please contact TeMeDa customer support for more information.

Telemetry API

A collection of RESTful JSON-based operations for use with the TeMeDa telematics solution. The Telemetry API provides Asset information, Locations, Reports, Maintenance, History Trails, Alerts, and more.

TeMeDa Admin API

A collection of RESTful JSON-based operations for use with the TeMeDa telematics solution that allows administrative functions such as Add, Edit and Delete operations to your TeMeDa account data.

TeMeDa PUSH Service API

The TeMeDa Push Service API is a real-time data interface based on industry standard JSON and HTTP web operations. This interface is being offered to customers and service providers who intend to integrate their systems with TeMeDa and wish to receive real-time telemetry data updates as they occur within the TeMeDa telematics system. Customers are required to create a HTTP/JSON listener in order to receive data.

Getting Started:

Usage of the TeMeDa APIs requires authentication and authorization. To start, it is necessary to sign-up on the TeMeDa API Portal (https://temeda.portal.azure-api.net) and subscribe to one or more API Products. Once your subscription is approved, you will be given an Authorization token, Environment Code, and a Subscription Key. You must use these credentials to execute API calls to the TeMeDa API.

API Documentation:

The TeMeDa API Portal documents each API call, including every operation available, the request url, required input fields and/or body, and sample Response JSON data. There is also a Code Sample generator that will generate the each API call in Curl, C#, Java, Javascript, ObjC, PHP, Python, and Ruby.

API Documentation – Sample JSON Response and Code Samples:

API Documentation – Units of Measure:

The TeMeDa APIs use standard units of measure for either US/Imperial or Metric. The API can also be configured for a specific TimeZone:

Miscellaneous API Usage Notes:

  1. To get the current actual Odometer and Engine hours for an Asset, use the following fields from the Device object contained within an Asset object:
  • “Estimated_GPS_Odometer”:
  • “Estimated_Engine_Hours”:

Note: The Estimated fields above are calculated by adding the odometer or engine hours to the User entered offset from the Asset Detail page (Basic and Source Setting Tabs). The Estimated values are sourced according to the corresponding “OdometerSource” or “EngineHoursFromEngineBus” fields.

  1. “Total” fields are cumulative/lifetime values.
  2. Maintenance Plans – “TimeInterval” unit of measure is in days.
  3. Report Summary section – duration units of measure are in seconds.