What evidence can you share that demonstrates the impact of the engagement?
Timereaction has a lot of benefits for different processes that we want to track. We had a couple of reasons for it, but the year we went with Timereaction we were on time with everything. It definitely had great benefits for the team to know at every step whether or not we were on time. If a critical step is being late, then we can send emails and notifications, so that we don’t fall behind.
It was an adaptation, but the benefit was definitely demonstrated. The software actually helped me understand the production process a lot better. I knew it superficially before, but I and the rest of the IT group know it well now. We’re able to do reporting for that team, and it helped us understand a lot of concepts around fabric, trim, and fit approvals. It was super beneficial.
On the first day, we pushed 2,400 purchase orders (POs) in seven seconds. Their API was solid. They were surprised that it went so fast, but the way we do it here is really tied to the database. The API was able to withstand a big load in one swoop. I was pleasantly surprised by that part of Timereaction.
How did Timereaction perform from a project management standpoint?
Our main contact is a very nice guy. He calls me every day, and we get along well. He was always super committed to this project. There is a way to submit tickets from the application, which is super easy to use and also takes a lot of information about the browser. We get support via email a lot of the time.
What did you find most impressive about them?
Timereaction shows all the transactions we want to track, and it can highlight urgent items in whichever color we choose. The dashboard is very useful in helping coordinators make sure they’re on time.
Any time something goes to red, they’ll know there’s an issue. That’s really the benefit of Timereaction. If we set up our workflows, we’ll know right away what we have to take care of. Once it’s resolved, it goes back to green, and we know we’ve corrected all the fires for that day or that week.
Are there any areas they could improve?
We were really hoping to have pictures, so we suggested that to Timereaction and they’re implementing it on the next release. They promised it, and they’re going to deliver. I’ve seen the demo, and they’ve done a few things that we requested. Working on just a style number can be hard, so we wanted to have the whole collection showing with images.
The thing they could improve on is reporting. Having reports like vendor performance could help us make decisions on whether or not to keep a vendor. We have to build our own reporting now. There aren’t sufficient BI elements, but we’re giving them suggestions.
Do you have any advice for future clients of theirs?
It's important to perform the development in phases. We did everything at once, and it was too much. We sent 2,400 orders in one day, which sent 2,400 emails to different people involved in the process. Not only that, the system sent one email for each workflow. We had a message for the PO being sent, one for the fabric approval for each style, one for the trim approval, and one for the fit. In one day, 10,000 messages left the building.
That’s just the way we organize our workflow, and we didn’t know. We made it super complex and actually complicated our lives. We’re reorganizing our workflows to not have 2,400 fabric approvals. It’s important to understand the processes and make sure to work with Timereaction advice. We wanted to do it in a certain way and didn’t listen to their recommendations, so we really made it complicated for ourselves. It’s a matter of understanding what the system can do for us, and using it wisely.