App Catalog Submission Guidelines

CAT APPLICATION CATALOG - Application Submission Guidelines

Copyright Notice

This Documentation is the property of Caterpillar. All ideas and information contained in this document are the intellectual property of Caterpillar.  This document is not for general distribution and is meant for use only by employees and people to whom it is distributed.  This document will not be loaned to anyone, within or outside Caterpillar, without prior approval.  Copying or unauthorized distribution of this document in any form or means, including electronic, mechanical, photocopying or otherwise, is illegal.

Last Updated: 2018-10-16

 

1. Introduction

This document is targeted for Caterpillar and Dealer Application Publishers.
The Cat Application Catalog is a single catalog for Application Users to search for mobile apps, web apps, and tools.  After reviewing the application information, the application user can select to be redirected to the application location URL.  This document is intended to provide guidelines for Application Publishers to submit apps for listing in the Cat Application Catalog https://digital.cat.com/applications.

 

2. Application Submission Process Flow Diagram

This flow chart explains the Application Publisher Submission Process to list an application on the Cat Application Catalog.

App Submission Flow

 

 

3. Application Submission Form Fields

Application Basics

  1. Application Image - Provide the Application image and up to 4 screen shots of the app.  The Application Publisher is responsible for securing the legal rights to all development & visual materials in the app.  Do not include PII, metadata with trademarked terms, popular application names, or irrelevant phrases to influence search results.

  2. Application Name - A unique application name limited to 30 characters.

  3. Price - Enter the prices of the application along with the appropriate currency. If no price, enter the word ‘Free’.

  4. Company Name - The Company that is presenting the Application.

  5. Language - Select the language(s) offered for the application. All selected languages must be tested rigorously.

  6. Category - List the category(s) that best fits the application - to aid in user search results.  
    Selects: Back Office Tools, HR, Machine / Engine Sales, Parts Sales, Productivity, Quality, Rental, Safety, Service, Technology, and Work Tools

  7. Application Description - Clearly define what the problem is solving and how it can benefit the user. The description is limited to 4000 characters, and should not include any prices or terms. The description cannot make any unverifiable product claims, or include content that is offensive, insensitive, or otherwise in poor taste.

Application Location

  1. Application Location - For redirecting to the app. Select from Android, iTunes, Web URL, Android China, QR Code, or Text-To.
  2. Application Size & Minimum Version - The Application install footprint / size should be kept minimal for efficient resource usage and user retention. List the minimum platforms supported by the app.
  3. Application Visibility - Visibility to the application will be restricted via CWS to the selected group: 1) Caterpillar, 2) Caterpillar & Dealers, 3) Caterpillar, Dealers, & Customers, or 4) Public

Application Support Information

  1. Offered By / Seller - List the company name that is offering/selling the app.
  2. Application Support Information - Website, Email, and/or Phone.
  3. List the Application Developer Support Information - Website, Email, Phone, and/or Address.

 

4. Additional Application Guidelines

  1. Distribution - Based on the location where the application is distributed, you may need to comply with additional restrictions or procedures where required by law.
  2. Content Rating - Icons, screenshots, and previews must adhere to the appropriate content standards as dictated by the International Age Rating Coalition (https://www.globalratings.com).
  3. Usage Pattern - Expected customer usage across different geolocations may be used for maintenance planning (expected volume, peak time, regular usage, off-peak time, etc.). Performance and stress testing is recommended.
  4. Application Lifecycle Maintenance - The application lifecycle plan should be based on the current capabilities and proposed capabilities, releases, and enhancements. Consider any upcoming major platform upgrades and review their potential impacts to the app. If retiring an app, ensure to distribute timely and effective communication to application users.
  5. Application User Reviews & Ratings - Application Publishers must not manipulate reviews or inflate through fake, paid, or incentivized feedback.
  6. Research & Reference - Include the citation for any research and reference used within the application to avoid legal issues. Caterpillar is not responsible for any legal, trademark, or copycat related claims.
  7. Application Rejection & Removal - Caterpillar retains the right to reject or remove any application that Caterpillar believes in its sole discretion is violating any of these application guidelines. The Application Publisher can request their application be removed from the Cat Application Catalog using the Contact Admin feature of the Cat Application Catalog ([email protected]).

 

5. Security

  1. Registration - Application Publishers and Application users should register using the Caterpillar CWS registration process.
  2. Authentication - Restricted by CWS and/or Federated Identity Management.
  3. Authorization - Restricted by CWS token characteristics, collected as part of CWS Registration. To determine the appropriate authority level, use the OAuth token characteristics such as Org, geolocation, affiliated user groups, etc. Application user identities are validated in a back-end web service through a security token. Application users must only be able to affect information in the system that they are authorized. Apps must not contain "back doors" for circumventing the normal security mechanisms.
  4. Data Collection, Sharing, and Usage policy - If the application is collecting information provided by a user, collected about a user or their use of the application or device, (including but not limited to PII, user location, or financial information), then the application must include a privacy policy, a disclosure of what data will be collected and how the data will be handled, and must obtain user consent to the collection and use of the data. The application must collect and limit use of the data to the description in the disclosure.
  5. Data Storage and Security - If the application is collecting or accessing data, do not use local storage for confidential information. Apps storing Caterpillar confidential information must follow applicable Caterpillar data handling & communication policies. Apps must not send personal or confidential information to console logs or application logs.
  6. Data Retention and Deletion - Retention and deletion periods must be limited to that required to support app functionality and legal obligations.
  7. Revocation of Consent - Have a process for removing user data if consent is withdrawn, and describe this process to users when they withdraw consent.

 

6. Legal

  1. Brand UX Requirements - Apps must not use a third party's intellectual property protected by patent, trade secret, trademark or copyright unless the Application Publisher per has obtained written permission.  Apps may not include Caterpillar's name or trademark(s) without Caterpillar's prior written approval.  Apps may not use the same or similar look and feel as Caterpillar's apps and Application Publisher’s may be required to modify their apps look and feel.  The Application Publisher shall indemnify, defend and hold Caterpillar harmless for third party claims arising from the app's infringement on a third party's intellectual property.
  2. Third-Party Software; Open Source Software - Application Publishers must maintain a catalog of all open source software used to build an app; ensure all open source software used in their apps meet all technical, legal and licensing requirements; and, if attribution or disclaimers are required, include in apps an "About" or "Legal Notices" section providing users with the required open source and application specific legal information claims, or include content that is offensive, insensitive, or otherwise in poor taste.
  3. Compliance with Laws - Application Publishers are responsible to keep updated on current laws and where or how an application may be used, to ensure it conforms to all applicable laws, including, but not limited to, antitrust and competition, data privacy, anti-corruption and international trade laws.  Application Publishers should consider situations where their apps can facilitate the sharing of information between competitors, transfer of information across borders, or collect personally identifiable information.  The application must contain a clear notice to application users regarding their responsibility for using the application within the parameters of all applicable laws that apply to the nature and location of their activities.  The Application Publisher shall be solely liable for any third-party claims arising from failure to comply with applicable laws.  The Application Publisher shall indemnify, defend, and hold Caterpillar harmless for third party claims arising from the failure of an application to comply with applicable laws.
  4. Individual Terms of Use - Application Publishers must provide terms of use to users that should address issues including application use, compliance with laws, privacy, data use and security.
  5. Functional Restrictions - Apps are restricted from including functionality that combines 3D data with machine location.

 

7. Contact Information

 

 

 

End

ISO 15143-3 (AEMP 2.0) API
/apis/products/prod/iso-15143-3-aemp-20-api