Architecture Harmonization team
Contact: John Reilly. jreilly@tmforum.org
Phone: +1 469-363-4546
This is an up and coming, action-oriented, leadership team that will shape key areas of architecture for the OSS/BSS industry. Initial focus is the development of a consistent approach for NGOSS Contract specification and application across TM Forum Technical Program in collaboration with NGOSS Contracts team and other teams using Contracts.
Work items (full list on team’s Collaboration Work Space) include:
- Contract Template: defining the contract meta data and other associated artifacts needed to populate the whole-lifecycle view of any DEFINITIVE Contract
- Define progression of Contract specification from Business View through Deployment View
- Contract granularity guidelines
- SID UML "adornments" for tool-based Contract generation
Seeking several levels of contributions:
- Active contributor to create/write contributions to the teams work on a regular basis;
- Sub-team lead to lead specific activities;
- Reviewers to active review and comment on the work of other members of the team.
Active contributor and sub-team lead implies travel to Team Action Weeks twice a year.
Skills:
Architecture, experience with NGOSS Contracts desirable, meta-modeling (for meta-modeling work items), UML (for UML related work items)
Catalyst Teams for Management World Americas 2007
Contact Debbie Burkett ( dfburkett@tmforum.org )
eTOM: Customer Interface Management
Contact: Kevin Scaggs. ks0567@att.com
This activity is building on the existing “Customer Interface Management” (CIM) Level 2 process element within eTOM, and seeking to develop this further with regard to emerging and anticipated customer interworking needs. In particular, this work is looking at the shifting balance on customer control with increased customer self-management, and the impact of web-based access. Hand-offs and linkages with other process areas within the enterprise are also being considered.
eTOM/SID L3 Mapping
Contact: John Reilly at jreilly@tmforum.org
eTOM/SID L3 mapping follows on the work done that mapped eTOM L2 processes to SID L1 ABEs. This new work involves mapping eTOM L3 processes to SID L2 and below ABEs, as well as SID entities and attributes were appropriate. A sample mapping has been completed for Service Configuration & Activation L3 processes. As a result of the work potential updates to the eTOM and SID will be identified. Members will benefit from the work by being able to employ mappings to further refine project scope in terms of the eTOM and SID, as well as perform detailed impact analysis from both process and entity perspectives.
eTOM: Location Management
Contact: Kevin Scaggs. ks0567@att.com
This activity is considering the way that “location” is handled within eTOM, and how to define the relationship between process elements and generic concepts of this kind. A particular issue is whether various kinds of location-related activity should be differentiated, or whether a single approach can be used in all cases. Links with other TM Forum work areas are important here, in particular SID for the modeling of location-related entities involved.
eTOM: Problem & Trouble Management
Contact: Mike Kelly (acting); mkelly@tmforum.org
This activity is building on existing work within eTOM on Assurance wrt faults etc, and related work in ITIL around Incident Management, to refine the use of terms like problem/ trouble/ incident that can cause misunderstanding and even conflict. Based on this, then to define improvements to the eTOM Model and process descriptions, and to develop process flows based on this, that clarify how problems/ troubles/ etc are handled. Links with other TM Forum work areas are actively being addressed, in particular SID for the terms and entities involved, and the NGOSS Contracts area where Contracts related to Assurance activities are being developed.
eTOM: Value Add Services
Contact: Kevin Scaggs. ks0567@att.com
This activity is looking at industry evolution and the impact on eTOM of issues such as new services, layered service provision, content provision, media convergence, etc. It is intended to develop modeling for significant scenarios within this, and to consider how eTOM can support these, or whether additional process development is required, and if so, how this should be represented for the enterprise.
eTOM: Workforce Management
Contact: Kevin Scaggs. ks0567@att.com
This activity is building on the existing “Manage Workforce” Level 3 process element within eTOM, and seeking to re-evaluate the level at which this process area should be positioned within eTOM, provide additional detail on the process definitions involved, and consider whether or not more than one such process area is needed due to fundamental differences in workforce management throughout the enterprise.
Industry Group Advisory Council (IGAC)
Contact: Tony Richardson; tonyr@tmforum.org Phone: +44 1394 386293
Membership of IGAC. Discuss / agree with other IGAC members positioning of TM Forum’s work in relation to that of other relevant Industry Groups. Carry details of TM Forum’s work items back into the activities of other Industry Groups. Give advice to TM Forum’s working teams, Board members etc – on other Industry Group developments. Help set Industry Group Liaisons strategy.
Integrated Customer-centric Management (ICcM) Project
Contact: ICcM Team leader - Gordon.Rawling@amdocs.com , TMF lead - Libbey Scheible at Ischeible@tmforum.org
Today’s heterogeneous Service provider BSS/OSS environments complicate the challenge of delivering excellent customer experiences and as a result many of today’s technology investments fall short or fail both the enterprise and the customer’s expectations of the service they should receive. The Integrated Customer centric Management (ICcM) initiative will explore the issues impeding effective customer management in information and communication service providers today. The ICcM project team would like to invite further participation from TMF members.
mTOP: Methodology
Contact: Francesco Caruso; Caruso@telcordia.com
The purpose of the Web Services Notification (WSN) TC is to define a set of specifications that standardize the way Web services interact using "Notifications" or "Events". They form the foundation for Event Driven Architectures built using Web services.
These specifications provide a standardized way for a Web service, or other entity, to disseminate information to a set of other Web services, without having to have prior knowledge of these other Web Services. They can be thought of as defining "Publish/Subscribe for Web services".
These specifications have many applications, for example in the arenas of system or device management, or in commercial applications such as electronic trading.
The current MTOSI notification service while based on WS-Notification, is not exactly WSN. The goal of this study is to identify what changes need to be made in the current mTOP specifications allow mTOP/MTOSI to fully leverage WSN specification to fulfill the notification and pub/sub needs.of the mTOP/MTOSI interface.
NGOSS Contracts Management
Contact: Dave Milham at dave.milham@bt.com / Libbey Scheible at lscheible@tmforum.org
Members are needed to respond to an upcoming RFI/RFP regarding NGOSS contracts. All OSS/BSS software and System Integrator members are encouraged to participate in this critical NGOSS program activity.
NGOSS Service Assurance project:
Contact: Stephen Fratini at sfratini@telcordia.com
- Business Agreement (BA) Editor for NGOSS Service Assurance Project
This job is for a Business Agreement editor concerning the NGOSS Service Assurance project. The BA contains requirements and use cases. The BA editor needs to have strong writing skills but also strong technical skills with regard to service assurance. The BA editor will need to collect agreed requirements and use cases from the team, and then integrate into a BA document.
This position needs to be filled as soon as the NGOSS Service Assurance project is approved (hopefully mid September). Most of the work will be during the first six months of the project but the BA editor will need to be involved for the entire duration of the project (tentative completion date is September 2008).
- Information Agreement (IA) Editor for NGOSS Service Assurance Project
This job is for an Information Agreement editor concerning the NGOSS Service Assurance project. The IA will be done mostly in UML (making use of the TM Forum selected tool, i.e., RSM). The IA editor needs to have strong model experience and ability to work with UML tools. As the model is to be SID based, the IA editor also needs to be familiar with the SID model.
This position needs can filled as soon as the NGOSS Service Assurance project is approved (hopefully mid September). However, much of the work will be done after the associated BA is in good shape (hopefully, by January 2008). The IA editor will need to be involved for the entire duration of the project (tentative completion date is September 2008).
- Interface Implementation Specification (IIS) Editor for NGOSS Service Assurance Project
This job is for an IIS editor concerning the NGOSS Service Assurance project. The IIS will be written in XML (XSDs and WSDL) and possibly other protocols, e.g., Java. However, the generation of the IIS may be automated via a tool such as Tigerstripe. The IIS editor will help with the methodology of mapping the IA to the IIS and in writing the IIS (in as much as manual editing is needed).
This position needs can filled as soon as the NGOSS Service Assurance project is approved (hopefully mid September). However, much of the work will be done after the associated BA and IA are in good shape (hopefully, by June 2008). The IA editor will need to be involved for the entire duration of the project (tentative completion date is September 2008).
OSS/J
Contact: Antonio Plutino at aplutino@tmforum.org
OSS/J is looking for new members on many teams! While OSS/J continues to function much like it did before formally joining forces with TMF, it is now much better positioned to fulfill the needs of the industry. Join the team to participate in the added value of further alignment with NGOSS and with Service Provider requirements. In addition, team members will also explore the business value that can be derived from OSS/J deliverables, such as our industry standard APIs and our Design Guidelines.
- OSS/J Common API: Non-normative Extensions
Contact: Vincent Perrot, vincent.perrot@sun.com
Specify and implement extensions of the OSS/J Common API to address specific customer’s environment needs or specific standard (like MTNM, 3GPP, mTOP, …)
- OSS/J Trouble Ticket API: Non-normative Extensions
Contact: Roman Schlegel, roman.schlegel@frox.com
Specify and implement extensions of the OSS/J Trouble Ticket API to address specific customer’s environment needs or specific standard (like ITU-T, …)
- OSS/J Billing Mediation API: Specification Leader
Contact: Antonio Plutino, aplutino@tmforum.org
Lead the team that maintains the OSS/J Billing Mediation API
- OSS/J Inventory API: Non-normative Extensions
Contact: Pierre Gauthier,pierre. gauthier@oracle.com
Specify and implement extensions of the OSS/J Inventory API to address specific customer’s environment needs or specific standard
- OSS/J Service Quality Management API: Non-normative Extensions
Contact: Thierry Supplisson, suppliss@ie.ibm.com
Specify and implement extensions of the OSS/J SQM API to address specific customer’s environment needs or specific standard
- OSS/J Pricing API: Java Reference Implementation Coding
Contact: John Wilmes, jwilmes@ceon.com
Implement the Java Reference Implementation of the OSS/J Pricing API
- OSS/J Pricing API: Java TCK Implementation
Contact: John Wilmes, jwilmes@ceon.com
Implement the Java TCK (test suites) for the OSS/J Pricing API
- OSS/J Pricing API: XML Reference Implementation Coding
Contact: John Wilmes, jwilmes@ceon.com
Implement the XML Reference Implementation of the OSS/J Pricing API
- OSS/J Pricing API: XML TCK Implementation
Contact: John Wilmes, jwilmes@ceon.com
Implement the XML TCK (test suites) for the OSS/J Pricing API
- OSS/J Pricing API: Non-normative Extensions
Contact: John Wilmes, jwilmes@ceon.com
Specify and implement extensions of the OSS/J Pricing API to address specific customer’s environment needs or specific standard
- OSS/J Discovery API: Non-normative Extensions
Contact: Sergio Pellizzari, sergiop@nakinasystems.com
Specify and implement extensions of the OSS/J Discovery API to address specific customer’s environment needs or specific standard
- OSS/J Fault Management API: Non-normative Extensions
Contact: Marc, Flauw, marc.flauw@hp.com
Specify and implement extensions of the OSS/J Fault Management API to address specific customer’s environment needs or specific standard (such as 3GPP, mTOP, …)
- OSS/J Order Management API: Non-normative Extensions
Contact: Andreas Ebbert Karroum, andreas.ebbert-karroum@nsn.com
Specify and implement extensions of the OSS/J Order Management API to address specific customer’s environment needs or specific standard
- OSS/Performance Management API: Specification Leader
Contact: Antonio Plutino, aplutino@tmforum.org
Lead the team that specifies and develops the OSS/J Performance Management API
- OSS/J Tooling: OSS/J RI and TCK stub generation with Tigerstripe Workbench
Contact: Eric Dillon, eric.dillon@tigerstripesoftware.com
Lead the work on the implementation of the Tigerstripe Workbench plugins for the generation of Reference Implementations and TCKs stubs of the OSS/J APIs
- OSS/J Tooling: OSS/J XML Plugin for Tigerstripe Workbench
Contact: Eric Dillon, eric.dillon@tigerstripesoftware.com
Lead the work on the implementation of the XML plugin of Tigerstripe Workbench for OSS/J
- OSS/J Tooling: OSS/J Web Services Plugin for Tigerstripe Workbench
Contact: Eric Dillon, eric.dillon@tigerstripesoftware.com
Lead the work on the implementation of the Web Services plugin of Tigerstripe Workbench for OSS/J
- Deployment of an OSS/J API and public disclosure (Prosspero candidate)
Contact: Antonio Plutino, aplutino@tmforum.org
Deploy an OSS/J API in a real Service Provider environment and publicly announce/ present it.
- Internal adoption project (a pilot project) for an OSS/J API and results published
Contact: Antonio Plutino, aplutino@tmforum.org
Work on an internal project on the adoption of an OSS/J API and publicly announce/ present it.
- Lab facilities for OSS/J business demonstrator (not as part of a pilot project)
Contact: Antonio Plutino, aplutino@tmforum.org
Set up a public local lab facility to demonstrate the result of OSS/J adoption.
- Public case study about actual implementation of an OSS/J API
Contact: Antonio Plutino, aplutino@tmforum.org
Publish a case study about the implementation of an OSS/J API
- Publication of financial data and ROI findings for an OSS/J adoption project
Contact: Antonio Plutino, aplutino@tmforum.org
Publish a financial data report and ROI analysis about an OSS/J based project
- Public OSS/J presentation at a major conference
Contact: Antonio Plutino, aplutino@tmforum.org
Present experience with OSS/J at a major public event
- Representation at standard organizations to increase OSS/J API adoption
Contact: Antonio Plutino, aplutino@tmforum.org
Active participation at major standard organizations to increase OSS/J adoption
- Technical support to OSS/J queries regarding a Service Provider’s own environment
Contact: Antonio Plutino, aplutino@tmforum.org
Provide technical support to answer queries about the OSS/J deployment in a Service Provider own environment
- Business support to OSS/J queries regarding OSS/J strategy and priorities
Contact: Antonio Plutino, aplutino@tmforum.org
Provide business support to answer queries about a Service Provider strategy and priorities about OSS/J
- Extensions of an OSS/J API to cover specific SP environment needs
Contact: Antonio Plutino, aplutino@tmforum.org
Develop an Official Extension of an OSS/J API to cover specific needs of a Service Provider’s environment
- Technical documentation or presentation on alignment of SP Environment data model with OSS/J Data Model
Contact: Antonio Plutino, aplutino@tmforum.org
Publish a technical document describing alignment of a Service Provider data model with the OSS/J data model
- Technical documentation or presentation on alignment of a SP architecture with the OSS/J Architecture
Contact: Antonio Plutino, aplutino@tmforum.org
Publish a technical document describing alignment of a Service Provider architecture with the OSS/J architecture
- Private OSS/J presentation at customer premises with support of the OSS/J team
Contact: Antonio Plutino, aplutino@tmforum.org
Non public presentation of the OSS/J adoption experience to a customer with the support of some OSS/J members
SID
Contact: John Reilly at jreilly@tmforum.org
Regulatory Compliance SID ABE Development – In collaboration with the Revenue Assurance and eTOM teams, this SID effort focuses on the development of ABEs to support and measure compliance with regulatory bodies such as SOX.
Telecom Applications Map
Contact: Piyush Sarwal at psarwal@us.ibm.com / Libbey Scheible at lscheible@tmforum.org
Telecom Application Map – release 3.0 will be launching in the next few weeks and needs additional team members to define applications.
Telecom Media Convergence
Contact: Bharat Mohan, Team Leader ( BharatM_Gupta@infosys.com )
The Telecom-Media Convergence Team, a new activity, is seeking participants who wish to contribute to the team's activities identifying and driving the resolution of issues related to operating and managing quad and triple play service and converged networks.
Telecom Media Convergence
Contact: Jakub Bielikowski ( Jakub.bielikowski@oracle.com )
The Telecom Media Convergence Interest Group is comprised of TM Forum members with IP / Media network operations and management expertise. Its main goal is to ensure rapid response to OSS issues and to provide expert guidance to TM Forum working teams in the Telecom and Media service sector. It may also spawn new teams to focus on fulfilling specific business requirements that may be identified that is not being addressed by an existing team. They have just completed the first stage of work by releasing TR136 to members for comment. In the next phase of work, the TMC is moving forward with a vision of “eMedia Service Provider” as mentioned in TR - 136 and plans to create detailed operational use cases for Converged Service Provider. Team will be developing five operational uses cases. Each use case will be led by an individual team member who is a part of core TMC team. The use cases currently under discussion include:
- Media Content Distribution Use Case
- Real Time Digital Rights Management Use Case
- Intellectual Property Rights Management Processes
- Mobile TV Use Case
- Broadcasting Operation Model Use Case – eTOM enhancements from Broadcasting perspective
- Shifters Use Case – Time, Place and Device
- Content Metadata Model