What IT things do you consider when looking at software?
-
Local storage only
-
Licensing terms / method
-
Per user or per computer (licensing)
-
How difficult is it to I implement / cut over to the new system.
-
Can the existing images be imported into the new system. (Without much trouble)
-
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
-
Support should be here as well, single point of support, or can you get support through multiple channels
-
@DustinB3403 said in What IT things do you consider when looking at software?:
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
Sadly, this is costly mostly in time and fees.
-
@DustinB3403 said in What IT things do you consider when looking at software?:
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
This is a good one. How it is stored is important.
-
@Dashrender said in What IT things do you consider when looking at software?:
@DustinB3403 said in What IT things do you consider when looking at software?:
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
Sadly, this is costly mostly in time and fees.
But less costly than being stuck and having no leverage.
-
I'd also consider things like:
- Operating System platform. If it requires MS, for example, that cost needs to be factored in to the TCO. Both the cost today and the ongoing maintenance costs. It adds up and can't be overlooked. (Same if you have to Bring Your Own DB.)
- Agents. Do you have to install and maintain agents? Do they only work on Windows? If agentless (HTML based) then great. If not, think about your support time and lockin for using the agents.
- Modernity. Hard to tell. But does the software appear to be using modern tooling and methods? Does it have bizarre archaic requirements and dependencies? This is an indicator of if the vendor is still maintaining the product. New products are more likely, but never guaranteed, to have development staff still employed. Products that have gone a decade without an actual update and barely limp along are more likely to have had their developers depart and the company may easily be selling something that they cannot actually support either.
-
@scottalanmiller said in What IT things do you consider when looking at software?:
@DustinB3403 said in What IT things do you consider when looking at software?:
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
This is a good one. How it is stored is important.
In this case, a closed black box. so I have no control/access to that data.
-
@Dashrender said in What IT things do you consider when looking at software?:
@scottalanmiller said in What IT things do you consider when looking at software?:
@DustinB3403 said in What IT things do you consider when looking at software?:
Non proprietary databases or other systems that make it difficult to move away from this product, would be another.
This is a good one. How it is stored is important.
In this case, a closed black box. so I have no control/access to that data.
Right. So that's a huge negative to consider. That's a worst case scenario.
-
@scottalanmiller said in What IT things do you consider when looking at software?:
I'd also consider things like:
- Operating System platform. If it requires MS, for example, that cost needs to be factored in to the TCO. Both the cost today and the ongoing maintenance costs. It adds up and can't be overlooked. (Same if you have to Bring Your Own DB.)
- Agents. Do you have to install and maintain agents? Do they only work on Windows? If agentless (HTML based) then great. If not, think about your support time and lockin for using the agents.
- Modernity. Hard to tell. But does the software appear to be using modern tooling and methods? Does it have bizarre archaic requirements and dependencies? This is an indicator of if the vendor is still maintaining the product. New products are more likely, but never guaranteed, to have development staff still employed. Products that have gone a decade without an actual update and barely limp along are more likely to have had their developers depart and the company may easily be selling something that they cannot actually support either.
For the OS, I assume you mean on the client side? I'm buying a SAAS, so it's pretty black box on the other side of things.
Good call on the agents, - but I did kinda cover that with my desire for HTML5.
Modernity - how do I test for this? Ask them what the platform is written? As for requirement, again, the server side is SAAS, so no clue, all I can see is the client side. There is an agent that can be run for more advanced features, but for mobility they are deploying it via Citrix - I don't believe the platform has an actual HMTL front end on it. -
@Dashrender said in What IT things do you consider when looking at software?:
For the OS, I assume you mean on the client side? I'm buying a SAAS, so it's pretty black box on the other side of things.
nd on it.Wait, SaaS? SaaS is buying a service, NOT buying software. It's specifically not buying software. So the whole discussion gets dramatically changed. The question should be what to look for when buying a service since you get no software.
-
Damn - you're right - I'll make a new thread.
