Cal-E-Force General Information

Cal-E-Force is the name for ETP’s newest application  for contract management and is based on the SalesForce platform.  Cal-E-Force will provide functionality for both ETP internal users and external stakeholders. Users can find training materials, copies of past presentations and references guides below. Please continue to check back here for more materials as the system is deployed over the next 6 months.


For any questions please contact the Cal-E-Force help desk

Open: Monday-Friday 9:00am – 12:00pm & 1:00pm – 4:00pm

Phone: 844-729-2070


Cal-E-Force Video Guides

Stakeholder Presentations & Data

Stakeholder Input Report
ETP thanks all of our external stakeholders for their inputs on design and features for the ETP Cal-E-Force system that will start supporting ETMS in June 2019.  More than 65 people participated in these initial External Stakeholder Needs Assessments.  More than 300 inputs were provided and are summarized in the report below along with FAQs collected from the sessions.

Cal-E-Force Reference Guides


Cal-E-Force FAQs

What is Cal-E-Force?

Cal-E-Force is the name for the specific ETP application that will be deployed over the next 6 months.  Cal-E-Force will provide the functionality for both ETP internal users and external stakeholders.  Cal-E-Force is based on the Salesforce platform.  This platform was selected because (1) it was the most dynamic cloud platform on which to design and deploy the Cal-E-Force System over time; and (2) it allowed for an initial implementation to migrate ETMS contracts in June 2019. 

A platform that could be initially deployed and then modified overtime was a must.  At this writing, much of the functionality for Cal-E-Force is not designed or built.  This will be the focus between now and December 2019.

Why Migrate ETMS Contracts to Cal-E-Force?

As discussed at the February 2019 ETP Committee and Panel Meetings, ETP has embarked on migrating Employment Training Management System (ETMS) contracts and deploying the Cal-E-Force System.

The functionality to support the ETMS contracts is driven by the need to move data that already exists and has been used to generate contract payments.

Additional upgrades can be made as part of the overall project effort.

What Internet Browser should be used with Cal-E-Force?

SalesForce can provide the most up to date information on which browsers should be used on your device. We have found multiple issues while using Internet Explorer (IE) and we recommend using the most recent updated version of Chrome with Cal-E-Force instead. 

SalesForce’s Browser Troubleshoot Guide

SalesForce’s New Google Chrome Extension (optional)

What is the Time Frame for Cal-E-Force?

It is the intent of ETP to deploy Cal-E-Force over three (3) phases, with full implementation by December 2019.  Following that implementation, we will hold bi-yearly updates to the systems that can incorporate ongoing business enhancements and stakeholder needs.

These phases will build on (1) key features of Salesforce; (2) inputs and needs of the Stakeholders that will use Cal-E-Force; and (3) automated support for internal ETP management of Training Contracts. Each phase will include refined ETP business rules that are set by executives and the Panel. 

Is Cal-E-Force Changing the ETP Business Model?

ETP business reengineering is not part of this automated project.  ETP has a procedure established to review and streamline business processes.  This is done through the ETP Committee Meeting process.  More information on those meetings and outputs are posted on the ETP Website and part of the Panel Meeting agendas.

What is Needed to Migrate ETMS Contracts?

Within ETMS, there was a population of 307 single employer contracts. Each contract is in various stages of execution. Some employers were in the final stages of execution having completed their training and awaiting ETP Fiscal Close Out processing. Most are still completing their approved training program. For this reason, features for the Cal-E-Force focused on the processes needed to support contract executions, including: enrolling trainees, tracking trainee hours, invoicing, and fiscal processing. It also included maintaining the needed data to complete the monitoring of contracts. Lastly, contract performance data was also needed by employers and their representatives.

For the contracts that were closed in ETMS, a view-only access will be provided to these contract owners. Until July 30, 2019 they can also view-only their contract in ETMS. If you have questions on viewing your closed contract, please contact the Cal-E-Force Help Desk at

How will External Stakeholders be Involved in Initial Deployment?

Having external stakeholders involved in each phase of Cal-E-Force deployment is part of the ETP project. This was true for the initial deployment of Cal-E-Force to support ETMS migrating contracts. Numerous communications on the migration have been emailed and posted on the ETP website. External Stakeholders will also be involved in Phases 2 and 3 of Cal-E-Force deployment. These sessions will be planned and started in August 2019 include:

  • Initial recommendation sessions on functionality
  • Demonstration sessions of prototypes for contract management features.
  • Guided video tour and prototype review sessions.
  • Modifications of features as needed based on prototype sessions.
  • Availability of updated Cal-E-Force functionality in a sandbox environment so that users can be comfortable with system features.
Does External Stakeholder Involvement End in June/July 2019?

The commitment with the deployment of Cal-E-Force System is to ensure the initial and ongoing consideration for external stakeholder needs for conducting business with ETP.  This builds on business changes that have already been made as part of the ETP Committee process.

When will new ETP Contracts be in Cal-E-Force?

Until Cal-E-Force deployment efforts (Phases 2 and 3) are completed, the legacy system and processes will remain the method, to develop an ETP application and manage a resulting contract. ETP is currently working with some of the large legacy contract owners to determine applicability for these complex contract types. This will be done in a controlled test environment and will not be part of the production environment until a full deployment and migration is developed for ETP legacy contracts.

What External Stakeholder Inputs were received for the Cal-E-Force to Support ETMS Migration?

Provided in the next table is a summary of inputs. ETP will also be posting on the website and on the login page new features that are being added over time.

At this writing many features that were requested have been implemented. For example, a vast majority asked that the system be easy to use.  They also asked for a straightforward navigation and a simple landing page.

Participants were in agreement on some of the specifics data elements for trainee enrollment or trainee hours tracking.  Some wanted more trainee data and some less.

Where possible, the go forward data requirements mirror those of the ETP legacy system.  The prototype reflects this going forward. For example, this means a key issue for ETMS user will be addressed by reducing the amount of information on the trainee hours tracking.