Tag Archives: timesheet integration

timecontrol

API – the Ultimate in integration

TimeControl has long been known as one of the most flexible and integrate-able timesheet systems in the industry.

In virtually every TimeControl deployment we are called upon to weave the timesheet data into a much larger business process.  At one time we focused more on doing this from database to database but as more and more systems (including TimeControl) became available as in-the-cloud subscription services, we had to broaden our approach. In 2017 we released a full service RESTful API included with all TimeControl versions.

The ultimate in TimeControl integration is almost certainly the Application Programming Interface (API) which is included with both TimeControl Online and TimeControl on-premise.  This module allows data and processes to be access both for pulling information out of TimeControl and for putting information into TimeControl.  Within the API we have defined numerous end-points for accessing data and processes allowing literally hundreds of functions and objects to be accessed.

Using the TimeControl API lets you create a blended corporate environment where data from one system can be updated into another completely in the background without user intervention.

What can you do?

The API has a remarkable range of possible methods to access.  Data from all the tables holding your TImeControl data can be pushed or pulled at any time and the API will ensure that all of TimeControl’s data control rules are followed.  The API has extensive messaging and we provide numerous examples and startup code to get you started quickly.

Is it secure?

The API carries all the same security measures that TimeControl is famous for.  The API can be turned on and off for the entire instance in the System Preferences and then access is controlled through a TimeControl User Profile.  Typically a single user profile is created for API interactions and the data that is made available to the API or data which can be updated by the API can be controlled right in that User Profile definition.  That’s quite an advanced structure as it allows as much API access as you define regardless of what the programmer writes in code that access the API.

For an on-premise deployment you can even elect not to install the API at all though this means that not only the API but also the free TimeControl Mobile App will be disabled.

How is it accessed?

We provide dynamic API documentation that is actually generated by the API itself whenever you ask for it in the help menu.

The result is an always up-to-date exactly for the version you are in with information on each method as well as example code on how to connect to TimeControl and guidance on how to get your project started.

We’ve not eliminated any of the other methods of integrating TimeControl with your corporate systems but the TimeControl API represents the ultimate in blended system integration.

For more information on how the TimeControl API can help you create an integrated business environment, contact HMS at: TimeControl.com/contact.

timecontrol

Timesheet Data can be the center of your data universe

When you publish a multi-functional timesheet like TimeControl, it should be no surprise to see a conceptual data diagram that includes all the places timesheet data might be used or which might integrate with other corporate systems.  We see such diagrams virtually every week. TimeControl at the Center

For many organizations, becoming more effective requires integrating systems from many sources.  Big ERP vendors will promote doing everything under their umbrella but that’s not always practical for operational systems.  As soon as you must consider a project or estimating or cost control or government compliance system, you have to think about the timesheets that will drive the actuals.

The worst-case scenario is finding an organization that is trying to support more than one timesheet system at a time.  It’s hard enough to get people to fill in one timesheet in a week, imagine having to fill out two or three or more.  We encounter this worst-case nightmare all the time.  The challenge that TimeControl answers is having a single source of auditable timesheet data that can be used for multiple purposes and multiple systems at once.

That’s why the integration and interface abilities of TimeControl are such an important aspect of its functionality.  TimeControl is known for having pre-built integration to more project and cost control systems than any other timesheet in the industry but the integration doesn’t stop there.  Here are some of the tools that you can consider when building TimeControl into the center of your data universe.

Import and Export Transaction Files
Transaction File Interfaces are the most popular method of linking to or from a Finance or ERP system as CFOs can be reluctant to direct connect their Finance system with direct input or output.  TimeControl can create a transaction file in many formats and then place that file in a place where the Finance, Payroll or ERP system can consume it and ensure that any data coming in is going through their systems business rules.

TimeControl can consume transaction files in just the same way.  So, new employees can be added directly from the HR system by bringing in a transaction file.  There are many file formats supported including CSV, XML and Excel formats among others.  Not only can transaction files be consumed or generated on demand but TimeControl can schedule these links to occur at any time or as often as you require in the background.  Files can be transferred to or from a network location, a laptop or to and from an FTP site to which you and your external corporate systems have access.  This makes Transaction File integration as efficient on our subscription service, TimeControl Online as with TimeControl on premise.  With this integration occurring in the background, the effect on users is to make the integration completely transparent.

Programmable Integration
The ultimate in integration is often considered to be through an Application Programming Interface (API) and TimeControl includes an API with bi-directional abilities to both send information out to or receive information from external systems.  The RESTful API is extensive and highly secure.  The API works in both the Online and on premise versions of TimeControl and TimeControl Industrial.  Programming integration to the API takes more work but the level of integration is complete.  Clients can weave TimeControl into as many other systems as are required to make an overall control environment.

Database to database direct connection
For clients who have TimeControl installed on premise, connections can even be made directly to and from the TimeControl database.  TimeControl on premise can be installed on MySQL, SQL Server and Oracle databases and HMS provides the schema to allow for a direct SQL link to or from the database.  There are rules, of course, when pushing data into TimeControl but our technical services can help with that.

Project Management and other Systems

TimeControl include direct pre-configured links to Project Management systems either on demand or on a schedule. With Microsoft Project Online, BrightWork and Primavera EPPM you can even have the link into TimeControl notice when a new project appears in the project system and import it automatically. Pre-configured links to other systems include:

TimeControl supports all of these connections simultaneously. You can have multiple project links, multiple corporate system links and using multiple techniques. This is why TimeControl is often the center of data flow diagrams in an organization as links may be used for any combination of bidirectional updates with project management, payroll, HR, billing, R&D reporting, job costing, presence management systems, contractor management and more.

To find our more about specific links, go to.

For more information on how TimeControl integrates with other systems, go to TimeControl.com/use-cases or contact us at TimeControl.com/Contact for help on integrating many requirements into a timesheet single system.