Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Frank Coluccio Technology Forum - ASAP -- Ignore unavailable to you. Want to Upgrade?

To: Lazarus Vekiarides who wrote (570)	12/1/1999 1:16:00 AM
From: Frank A. Coluccio	Read Replies (2) \| Respond to of 1782

re: autoprovisioning, autonomous service creation, customer-centric network management Hello Lazarus, From the "re" header above, it becomes obvious that this is not a single concept, but a broad set of considerations covering not only individuals and enterprises, but conceivably entire communities of interest who share a common network. When CNM, or customer network management, first became a "differentiating" feature for some carriers, they used a tremendous amount of restraint in just what they would and would not let the customers do and see. They were merely giving users a window into their own (the telco's) Operations Support Systems (OSSes) and their Operations, Adminstration, Management and Provisioning (OAM&P) platforms, and allowing users to read only the information relating to their own switch- or other forms of resource- "partitions." At one point, one of the RBOCs allowed certain customers to do auto "provisioning" on a small scale, activating links, time of day switching, etc., like customer controlled reconfiguration on DACS machines, and again through the OSSes/OAM&Ps. At one point they had to pull back considerably on these features because they could not pass some self-imposed audit criteria for security, as you mentioned. The rationale behind this had something to do with the level of trust that could be assigned to end users (i.e., customers) versus that which could be assigned to the carriers' own employees. And there is some merit to this, if the security safeguards and overall system designs which were put in place in those OSSes and OAM&Ps were based on different thresholds for threat avoidance than would have been put in place for customers. If for no other reason than the much higher level of scaling that would be required for the masses versus only a handful of technicians who worked "on the inside." In any event, these earlier forms of CNM and circuit provisioning features in the POTS and private line circuit-switched environment were relatively pedestrian, so to speak, compared to what a web user might enjoy at some point if given some feature capabilities and additional freedoms. Maybe you and/or someone else here might want to take a stab at this, and enumerate some of those features and service creation possibilities that an individual might find attractive in the future? I'd like to explore this topic further when I'm able to focus better. For now, tho, I'm going to have to say 'night, All. Regards, Frank Coluccio