I recently read an OSS Vendor market assessment by Gartner. I noticed in this report that no vendor scored Very Strong in Products and Services (aka Delivery). So why is that? As the report mentions, “Many of the vendors profiled...have been going through numerous merger and acquisitions activiti...
Telcos use inventories for all sorts of things, and there are different solutions for different purposes. One distinction often made is between a Physical Inventory system, typically geospatial in nature and for example used for physical planning, and a Logical Inventory System typically more abstr...
Requirement definition, in my experience at least, is the most difficult part of OSS Software projects. Requirements are often general, vague and lack clarity, and occasionally don’t even exist! The end result is typically a misunderstanding of scope across all the parties involved in the project de...
I’d like to start a discussion thread about ITIL and its interaction with OSS - How does / should ITIL integrate with or be part of OSS, and in particular OSS Inventory? - How does ITIL relate to other Telco standards such as eTOM? - Does anyone have any case studies to share? - Asset Management versus Network and Service Management I’d welcome your thoughts. Of course this is a broad topic so may spawn a series of threads or blogs.
- Lessons Learned / Best Practice / Dos and Don’ts?
- Product Offerings?
- How does / should ITIL integrate with or be part of OSS, and in particular OSS Inventory?
- How does ITIL relate to other Telco standards such as eTOM?
- Does anyone have any case studies to share?
- Asset Management versus Network and Service Management
I’d welcome your thoughts. Of course this is a broad topic so may spawn a series of threads or blogs.
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.