Why did your company select SharePoint?
I knew that SharePoint works in lists and that was really the solution in my mind. Everyone is entering into one place, and they can all enter it at the same time. With Excel spreadsheets, if it’s open, someone else has it open it. You can’t collaborate, it can’t work together.
There were also some cascading lists that I needed to have created, which I knew were a little bit tricky in SharePoint and I knew Cabeus knew how to do that. We have product families, product types and brand names. If you pick a family, it will shorten the list into product type. And then you pick the type and that shortens the list even more for brand names. So all of that kind of intelligence built into it was attractive. However, I needed the expertise of Cabeus to assist me.
Was the filtering tool in SharePoint very effective for your organization?
Yes, we didn’t have a robust Microsoft Project plan, but at least it showed me Gantt chart views that we can edit. We put dates in, we can look at it through a Gantt chart view if we wanted to, which was also important.
Some of the dashboard views of things were really nice as well. That makes everything easier to view and quicker to work with.
Reporting to management is so much easier. Cabeus was able to show us. We showed the team that as well, and they were really thrilled.
What was your process for selecting Cabeus to work with?
I knew Bala, who is the president. We met while working on a project together for a previous organization.
We started discussing the information. He’s a regulatory person, so he totally understands and gets the problems and solutions. So it’s nice having someone from a regulatory background. It’s a strong background. And then his partner, Ravi, is the software person and the coder. He is also really easy to work with. It’s great.
Were they involved in planning, design, development and support?
Yes. They helped with the design. They helped with some of the documentation and some of the demoing of the systems and the support. They’ll help with some of the support as we roll it out. If we have problems, they’ll support us.
Were any other technologies used besides SharePoint?
Not for this project.
Can you give us a sense of the size of the initiative in dollar terms or personnel hours?
It’s not an expensive project. I would say it’s $75,000 at most. They spent a few months working on this or us. A lot of it is because we’ve even been making changes. For the initial first look at the prototype, it was probably one month. Then, we started showing it to the teams and they made comments. We were constantly going back and forth, tweaking the system to make it better. Now, we’re just doing iterations and things.