The last decade of OSS software projects has seen a focus on implementing COTS products. There is of course lots of benefit in COTS but is there a space for custom solutions? I’m sure there is, but when is a custom OSS an option?
I’m not talking spreadsheets to manage transport rings or port allocation, or access databases knocked up in a week by an enthusiastic user. I am interested in the feasibility of designing a custom robust OSS that supports broader business operations, integrates to other solutions in the OSS, provides better customer value and lower delivery risk. Maybe kick start a new solution with an open source OSS, make use of standard data models like SID and go from there?
Maybe it’s another case of tactical deployments versus strategic ones (see a previous article on this) 'Strategy or Tatic'
So, what can be gained (or lost) from going down the custom route (in house or with a services partner) versus the risk mitigation and other benefits of a COTS product? Can the right team with the right customer focus get a reliable low cost maintainable custom solution together that offers real value to a telco.
Enough of my yabber - I look forward to exploring this topic with you in this thread. Please post your thoughts.