The Future of OSS is Play: Learning from My Journey of 85+ hour Weeks (in a State of Flow)
During my first forays into OSS, over a period of 6+ years, I averaged 85 hours a week whilst being paid for a 40 hour
During my first forays into OSS, over a period of 6+ years, I averaged 85 hours a week whilst being paid for a 40 hour
The call came in at 5:43am. “The routers are acting up again down at 1313 Packetloss Lane” the night supervisor whispered, as if afraid the
Telco appears to be an increasingly tough industry. Demand for connectivity continues to soar, yet profitability and differentiation are becoming ever more difficult to achieve.
I know a guy. One of my great friends actually. We’ve known each other since kindergarten – back when we were five years old. He
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
One Response
Q1
provide timely and accurate inventory count and status/attributes of NE and CAFAC including customer and network circuits
Q2:
accurate inventory and status serves as basis for the services we give to our customers. We need to know if NE port is free and can be assigned to a new customer order. We need to know if a particular NE is down so we can resolve the problem immediately and pro-actively inform our customers of the network problems