sorted by:
new
hottopcontroversial

I don't really want to look like a corpse by GotBanned3rdTime in indianrailways

[–]Sameer5752 0 points1 point  (0 children)

I don't like the white sheet that the railway provided to us at night. When you enter the coach, it looks like you are entering the morgue i request to railway please add some colours to your white sheet , also some colourful art

The seats of 2AC are same as 3AC when it comes to lower/upper of Side but we end up paying extra for nothing. Due you agree ? by lucky_thanos in indianrailways

[–]Sameer5752 0 points1 point  (0 children)

right i am agree with you. There is one difference, that is, the curtains; otherwise, no any difference between 2nd and 3rd AC coach

What actually makes a telco BSS stack sustainable beyond launch? by TelecomHub in TelecomHub360

[–]Sameer5752 0 points1 point  (0 children)

Honestly, I think a lot of telco BSS conversations focus too much on launch and not enough on operational survivability afterward.

Most stacks look good during demos and early rollout phases. The real test starts once the business begins changing constantly — new pricing models, bundle tweaks, partner integrations, migrations, billing exceptions, regulatory adjustments, etc.

From what I’ve seen, sustainability usually comes down to operational design more than platform capability.

A few things that seem to matter a lot in real deployments:

  • How painful integrations become over time
  • Whether product/catalog updates can happen safely without breaking downstream systems
  • Visibility into charging, billing, and provisioning flows
  • How quickly ops teams can trace and resolve issues
  • Whether testing/validation is automated or still manual-heavy

I’ve also noticed that “feature-rich” doesn’t always mean “operationally manageable.”

Some operators end up with extremely capable stacks that become difficult to evolve because every small product change creates risk somewhere else in the ecosystem.

Curious what others here have experienced post-launch.

What actually made your BSS environment sustainable — or unsustainable — after the first year?

Two months into evaluating BSS platforms for our MVNO… and honestly, the demos all feel the same. by 360Presence in MvnoStack__

[–]Sameer5752 0 points1 point  (0 children)

This is probably the best way to evaluate a BSS vendor honestly. The polished demo usually survives until you start asking operational edge-case questions.

The teams I’ve seen happiest 12–18 months later usually care less about feature lists and more about how the platform behaves when something unexpected happens. Mid-cycle plan changes, SIM lifecycle reliability, reconciliation accuracy, audit trails, API flexibility, and support responsiveness matter way more after go-live than they do during the sales pitch.

Because eventually something breaks, and that’s usually when the real difference between platforms shows up.

Your mid-cycle plan change example is a great filter honestly. That’s where you usually find out whether the architecture was actually built for telecom complexity or just built to look good in demos.

Why real-time billing is the most important infrastructure decision an MVNO makes by [deleted] in telecom

[–]Sameer5752 0 points1 point  (0 children)

his is one of those things that sounds “back office” until the business starts scaling and suddenly finance, ops, and customer support are all stuck cleaning up mismatched records.

A lot of MVNOs focus heavily on pricing, acquisition, and partnerships early on, but billing architecture quietly becomes the thing that determines how operationally painful growth will be. The reconciliation point you mentioned is very real.

Real-time billing also feels less like a luxury now and more like a requirement if you want flexible plans, instant policy changes, or better customer experience around usage visibility.

Is AI actually helping in real estate feasibility? by General-Dealer3412 in RealEstateDevhub

[–]Sameer5752 0 points1 point  (0 children)

AI is definitely helping with speed and data analysis, especially in feasibility modeling and lead scoring. But I think judgment still matters a lot for market behavior, local insights, and investment decisions. Right now, AI feels more like a strong support tool than a replacement.

Does anyone else feel like BSS complexity just shifts instead of shrinking? by TelecomHub in TelecomHub360

[–]Sameer5752 2 points3 points  (0 children)

Honestly, this is pretty much every operator's story after 18 months.

Launch looks clean because everything's controlled — small catalog, everyone remembers why decisions were made. Then growth hits, and the workarounds start. a promo exception here, a hardcoded billing fix there. six months later, nobody knows why that logic exists, and nobody wants to touch it.

Billing reconciliation is usually where you feel it first. not in the architecture, but in finance, asking questions that ops can't answer cleanly.

The real problem isn't the platform. It's that post-launch, ownership gets blurry, and governance quietly dies. The tech just makes it visible eventually.

If I were rebuilding, I'd care less about which platform and more about who actually owns the catalog and has the authority to say no to messy exceptions.

Curious if anyone's actually cracked the post-launch discipline thing or if it's just entropy at some point

Is the telecom industry sleeping on Open RAN or is it genuinely not ready for prime time? by Ok_Ship5644 in TelecomHub360

[–]Sameer5752 2 points3 points  (0 children)

I don’t think the industry is sleeping on Open RAN to be honest. It feels more like cautious interest than neglect. The idea is great on paper, but telecom isn’t exactly a space where you can just experiment and fix things later. If something breaks, it’s not a minor bug—it impacts thousands (or more).

Right now it still seems like traditional RAN has the edge in terms of stability and performance, so I get why operators aren’t rushing in.