|
|
article
page | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 |
and Web 2.0. These were considered to be better understood and spun off into other, less formal initiatives.
The SDF work program commenced in the summer of 2007. It still took another six months for this program to get started (Tony Richardson, TMF administrator of the SDF team, “[it]takes time to get common viewpoints in place”). During this time, much organizational work was accomplished; nevertheless, this delay may yet prove to be critical. Another TMF group, the NGN-M (Next Generation Network Management) team, after spinning off the NGOSS Harmonization team, was merged into the SDF activity. In this interim, a board sponsor stood up. TMF active contributors (notably Jenny Haung of AT&T, Johan Vandenberghe of Alcatel-Lucent, and Dave Milham of BT with Tony Richardson of the TMF) wrote an exceptional work charter with a clear six-month work plan – even if this seamed a retrenchment from the broad vision of the SDF. The larger TMF membership was informed of the program and solicited for interest and commitment of team member resources. Still, for something this important, this delay in starting is hard to understand. Perhaps the importance of this work and the critical time curve under which it must occur is not yet fully understood.
|
|
Stepping back, another possible reason for the slow ramp up emerges: neither SDP or SDF is a Business and Operations Support System (BOSS) application, so why is the TMF getting involved? |
|
struggled to complete its work plan. Vendors who were particularly active include Microsoft, Sun, IBM, and Oracle. Other members wandered in and out as the topics changed. With Tony Richardson involved (he has led the TMF’s liaison activities), lots of contact occurred with groups outside the TMF who were working in parallel areas or might contribute components or ideas. This diverse input needed to be assimilated and rationalized. All this has culminated in the TMF document TR139 Technical Report which should be finalized in time for the January 2008 TMF Team Week.
Officially, the TMF is pleased with progress. Tony Richardson:
“A lot has been achieved in the project to date – the creation of a first agreed version of the SDF Reference Model (which is presented in TR139 along with other related issues such as the main SDF business and technical drivers etc). Other items include
|
|
|
|
However, momentum is growing – since our review article on SDF last January, a whopping 237 members from more than 125 companies have signed on to follow the work and twenty or so companies have placed contributing members on the team. This contributing group expanded to significant members beyond the Landscape Team. Member Companies of the TMF SDF Team include Alcatel-Lucent, Amdocs, AT&T Inc., BT Group plc, Computer Associates, EDS Information Services L.L.C., IBM Corporation, IONA Technologies, Microsoft Corporation, Oracle Corporation, Pendragon Consulting, QinetiQ, Nokia Siemens Networks BV, Sun Microsystems, Telcordia Technologies, and Telstra Corporation.
For the second half of 2007, this team
|
|
evaluation / selection / initial usage of a tool for requirements capture, commencement of a BA development, forming of a set of Industry Groups collaborating in SDF development (via f2f workshops, conference calls etc.).”
But the contents of TR139 are essentially similar to the work of the Landscape Team. Six months is rather long for tooling up and as of this review, the document itself is unclear and muddy.
Stepping back, another possible reason for the slow ramp up emerges: neither SDP nor SDF is a Business and Operations Support System (BOSS) application, so why is the TMF getting involved? Is the learning curve for
article
page | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | |
|
|
