Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

Headcount Data Integrations

Details on Headcount integrations with a 3rd party systems.

Table of Contents



Summary

Headcount works to meet our clients' needs by providing a state of the art evacuation roster system with data that is as accurate as possible. 


To that end, we built a system to accept client data in a number of ways with flexibility and reliability in mind. We can receive or poll client systems and read data in a variety of formats. 


Headcount can integrate with any modern 3rd party system to automate the updates to your emergency roster within Headcount.


This can be achieved because Headcount, along with most modern 3rd party systems, has an Application Programming Interface, most commonly referred to as an API.


API’s allow two systems, even if they are built by separate vendors, to effectively communicate with each other without human intervention.


This enables us to fully automate tasks where data is needed to be shared between two different systems.

 

 

Benefits

If you have a large number of people at your facility or a very dynamic work schedule, including employees arriving on business travel from other sites, clients, visitors, contractors, vendors, etc., then it can be a lot of manual work to keep an accurate emergency roster.


In these situations, a data integration between Headcount and another system that already houses your employee/on-site/visitor/etc. information can fully automate the task of keeping your emergency roster up-to-date by automatically adding people to your emergency roster when they arrive and automatically removing people from your emergency roster when they leave your facility.


For example, integrations with:

  • A Human Resources Information System (HRIS) or Payroll System can automatically add new employees as they are hired and remove employees after they are terminated

  • A Time Management System can automatically add employees when they clock into work and remove employees when they clock out

  • A Visitor Management System can automatically add visitors when they sign-in and remove visitors when they sign-out

  • An Access Control System can automatically add employees when they badge-in to work and remove employees when they badge-out or reach a time-out period

  • Plus more

Integrations can sync data at a time interval that you define, including daily, hourly, and real-time.

The more accurate your roster is before an emergency, the faster and more accurate your headcount will be during one.  Keeping an up-to-date emergency roster can be critical to your emergency response procedures.

 

How It Works

Transferring Data

Our main way of transferring data is to use secure HTTP calls. We do not recommend or actively support non-encrypted communication of data. 


Security Concerns

We operate with a philosophy of least privilege access / risk and surface minimization


All client data is transferred in an encrypted format (TLS 1.2+), making it secure while “in motion”


All client data is encrypted in a database, making it secure “at rest”


Pushing Data

We support pushing data to Headcount. This can be done over secure HTTP calls. 


We support accepting JSON, XML, CSV (where applicable), or Excel data (where applicable)


We don't accept data over FTP, FTPS, or SFTP protocols. 


Polling Data

We support polling data as well. We communicate and can accept data in a number of formats, as with pushing data to Headcount. 


Typical Data 

Headcount data is not suited to a single CSV file, though parts of it are. There are several different parts of data that make a more structured data format such as JSON a better option


Site and Zone (Structure)

Site and Zone (Structure) information (can be constructed in a number of different ways)


Contacts
  • Name
  • Badge number
  • Phone number
  • Email address
  • Manager
  • Primary location (aka structure / zone)
  • Keywords
  • Photo URL
Groups and group memberships
Roles
  • Name and role combination

 

Process

Summary

Headcount offers Professional Services to support installations and integrations with our services. 


Workflow

Our general workflow looks like this: 

  1. Envision the solution our client wants
  2. Deliver the solution for our client
  3. Provide support for the client


 

Envisioning

Our main goal is to know what the client wants / what is of value to them - so we can codify it and deliver on it.  To do this, we need some basic questions answered to determine the scope, including:

  • What is being integrated? 
  • Where is it located? 
  • How do we interface with it?
  • What is being developed?
  • What is the schema of the data in question
  • What are the boundaries of the information we are going to use / collect?

Deliverables
  • Envisioning document
  • Estimate for the rest of the work

Delivery

This is very much an iterative process until the project is deemed operational for the client. 


The process includes cycles of:

  • Design
  • Develop
  • Test
  • Release

Deliverables
  • We deliver a working product that is online, to the best of our ability. That means, the product is operational, integrated with Headcount, properly configured, and the client is properly using it.

We  accomplish this by delivering the following:

  • Product
  • Defined operation responsibilities
  • Configuration
  • Documentation
  • Training
  • Maintenance

 

 

Support

Things change and bugs are found, so we provide support for our clients not on a transactional basis, but as a relationship.


Should bugs arise (hey, it happens), we will negotiate a contract that establishes our SLA, what everyone should expect, and who will pay for what.


Should features change or upgrades happen, we will work together to define how that looks.  

  • Do we start a new project?  
  • Do we devote a certain amount of hours for support per year?

Deliverables

  • A contract for maintenance
  • Includes terms of service
  • How to use your support (email, phone, hours, etc.)
  • SLA
  • Developer hours allocated for changes that are not functionality bugs

 

Common Integration Requests

  • Active Directory
  • Active Directory SSO
  • ADP
  • Alertus
  • Attendance On Demand
  • BambooHR
  • Custom People Data System
  • EIO Board
  • Envoy
  • Geo Tab
  • IPAWS
  • Kenexa (IBM)
  • Kronos
  • Lenel
  • Local Dispatch Alerts
  • Okta
  • PassagePoint
  • PeopleSoft (Oracle)
  • ProxyClick
  • SAP ERP HCM
  • SiPass
  • SQL server auto sync
  • SuccessFactors (SAP)
  • Taleo (Oracle)
  • Ultipro
  • work.com (Salesforce)
  • Workday




Pricing

In general, pricing is estimated on a case-by-case basis, but certain integrations will have a known price.


Your Headcount rep will be able to inform you on the price based on your specific situation.

 

Questions

If you have any further questions on integrations, please contact your Headcount rep directly.