DTC (ASX) Kronos Platform

Originally posted by RustyAs: ↑

I don't usually post on here, I usually don't have anything to contribute that would be relevant.
However, in this case, I think I might.
Having worked for, in a Management role, and having worked with the System, as a User in a large construction company, I have a bit of knowledge about how it all works.

The real strength of the system, probably not promoted enough by Damstra, is that the base program was developed in house, by an original employee, and all ongoing development was completed in house. Any acquired systems were all integrated into the core system.

In relation to the the KRONOS situation, Damstra were the only company that could integrate directly with KRONOS, that is KRONOS data, time sheet data etc could be integrated with Damstra hardware like onsite login terminals in a way that no other company could do.

I don't believe they are a front end for KRONOS (this may have changed) it is just that clients who use KRONOS are able to continue too, and not have have "another" program on their system to use Damstra .

Based on what I know, there is no way the KRONOS issue will impact Damstra, actually it may help Damstra clients as the data may be able to be retrieved (just a guess, in no way am I able to verify)

Yes, I'm significantly invested, Yes, I'm taking a bath on this, but I'm comfortable that the long term will be great.

Expand

Full disclosure up front: I'm an employee at this company. I don't speak for, or on behalf to the company in any way.

So Kronos is a product we use in the back-end for time and attendance processing in our core original product. Everything else (way before any acquisitions) is built in-house by our development team over the last 17+ years as the product has grown and evolved.

Kronos largely does one thing very well, which is time management. Turning "swipe" "swipe" "swipe" into In/out, in/out, etc., handling things like missed events, network losses/outages meaning in/out don't always come in sequence., cross-site operations and so forth. It's actually a very complex system, but they've been doing it as their bread and butter from day 1.

In the original days, we used their hardware, but a long time ago we moved on to using our own terminals to increase flexibility and capability, and these days, Kronos is < 5% of our systems operations. It's a background processor for us, and that's about all. So we have it, we use it, but it's not in any way that we're just "putting a skin on it".

FWIW, while there have been a lot of acquisitions lately, the company and core product have been around for a LOT longer (pre-Skilled days, and then during the Skilled/Programmed ownership), and the systems are robustly developed throughout that time and remain at the core.

So again, I don't speak for or on behalf of the company, and I hope I haven't said too much, I just felt I had to comment here and put a few mis-truths to rest.