COINS Integration Overview & Requirements
Tenna’s integration with COINS ensures that contractors have a more complete data picture for bids, project management, maximizing profits, and improving employee performance. Share real-time data about your assets and sites to your ERP for total visibility over operations and their associated costs. Your team can make informed decisions with accurate data and customize options to fit your business model.
💥Integrations is a premium product and requires a separate license. Please contact your Account Manager for more information on premium product licenses or reach out to Customer Support at help@tenna.com or call 888.836.6269.
In this article:
Data Flow
Enter Equipment Once
Enter a new piece of equipment in COINS and it will automatically show up in Tenna or allow the field to enter a pending piece of equipment in Tenna and it will show up in COINS. You choose the best process to work for your team.
Enter Jobs Once
Every job set up in COINS can automatically be added to Tenna. You can choose job status or utilize your own unique data field “Send to Tenna”. You choose the best solution for you.
View Utilization Updates Always
Capture hour and mileage readings for your assets and automatically update them from the machine into COINS from Tenna.
Benefits of Integration
- Field Productivity: Alert a project team when a piece of equipment arrives at a jobsite or when it is left behind.
- Accurate Job Costs: View up-to-date equipment listings to code equipment hours more easily and accurately.
- Visibility over Equipment Costs: Analyze and review equipment cost more accurately.
- Collaboration and Efficiency: Keep your office, shop and field teams connected sharing the same data. Eliminate static spreadsheets with efficient data sharing.
- Accountability: Increase accountability among field teams when using or handling assets to help control costs.
- Decision Making: Make educated decisions by taking appropriate action when assets are under (or over) utilized.
Integration Setup Instructions
The following setup/configuration must be done in the COINS environment prior to integration.
All work to be performed by the customer or the customer’s consultant.
Suggested COINS Resources
- COINS consultant or subject matter expert
- Consulting/support time from COINS corporate
- COINS System Administrator/IT Resource
Prerequisites Before Sending Data to Tenna
Important! At least one COINS designer license is required to implement on the COINS side. This may require an additional cost based on your COINS license and/or agreement.
- 1
- Apply a patch to COINS (SSL related, potentially).
- 2
- Install Tenna SSL certificate into COINS.
- 3
- Pick and define a UD field for Assets and Jobs to become "Send to Tenna" controllers.
NOTE: COINS may only provide a limited number of UD fields (e.g. 10) so the customer is responsible for allotting the required UD fields for "Send to Tenna".
- 4
- Set up data sets for Assets and Jobs.
- Include required fields per the information in this article.
- Include any optional fields.
- Include UD fields selected above named "Send to Tenna"
- 5
- Add the global database publish records for Assets and Jobs.
- 6
- Add a Tenna "send parameter".
- 7
- Configure email monitoring for processing errors.
- 8
- Add a background process to send data to Tenna.
- 9
- Configure the existing queues to ignore Tenna records (e.g. need to explicitly exclude Tenna messages from existing Main and Mobile queues and any other queues.).
Prerequisites to Receive Data from Tenna
Important! A webservices plan from COINS based on the number of assets is required. COINS will require an additional cost based on the number of calls and total data transfer size for new integrations. COINS service cost for ingesting data varies based on the customer's COINS license and/or agreement. Additional COINS licenses may be required based on the COINS license and/or agreement.
- 1
- Create the Hours, Miles, and Locations user-defined webservices.
- 2
- Set the PWDHASH system parameter to SHA-256.
- 3
- Verify that there are available licenses for users and concurrent users.
- 4
- Select the roles for the user making the webservice calls to allow the calls.
Field Mapping
IMPORTANT! Any information from COINS will overwrite the existing information in Tenna for the fields in the Field Mapping tables below.
Expected Implementation Timeline
The timeline is an average of 30-50 days beyond kickoff. The following example assumes the activity starts the first of January 2023 and extends for 48 days.
NOTE: For questions, reach out to the Tenna Integrations Department integrations@tenna.com.