MEETING AGENDA

The latest revision of the working text is: TMOC-AIP-2007-150R5 – see at: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-150R5.zip
(to be uploaded prior to the call)

A new index of all the TF documents is available at: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-152R5

1. Finalization of the High level Req. & Arch Spec – status update - The latest revision of the working text is: TMOC-AIP-2007-150R5 – see at: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-150R5.zip - The Initial Closure clock was re-started on August 15. The Issue was scheduled to go to Final Closure on September 5.

2. Action items from last call – see at: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-176.doc
• Amit to:
i. Find the needed definitions of the Industry Group Positioning Map (IGPM) see: TMOC-AIP-2007-174 – Appendix 2 – SDF / Industry Group positioning Map (initial version) – in the “Requirements” tab what are the Customer/Supplier/Partner Services definitions?

ii. Provide a draft of definitions of IPTV products and services

• Yvonne to reach out to Tony Richardson to discuss whether a new work register or liaison is necessary for providing the IPTV OSS FRA document (upon reaching a final closure) to the TMF SDF industry WG.
• Connie to:
i. Backtrack and see what documents are accessible – regarding CableLabs interface specifications for SP to CP (this is related to issue 93).

ii. Provide a draft of the “Scope” section of the new Ordering API WT

• Linda to submit a contribution for the diagram and the use cases.
• Dave and Ryan Gfeller (EMBARQ) to provide a contribution for ASR and LSR order processes

3. Review of what seems as an editorial oversight (typo) in the “lollipop” in Figures 22 and 23 of the IPTV OSS FRA document – here is a summary of email correspondence on that subject:
• Linda and Kam: “the network stratum offers the service of resource provisioning to the managing OSS plane. However the lollipop is in the opposite direction as if resource provisioning is being offered by a service resource or an application resource.”
• Connie: “figure 22 does have a mistake for showing the interface between transport stratum and OSS resource provisioning function. The OSS provides the provisioning commands, and the transport stratum consumes them, so the sickle should be on the left. The same interface is shown correctly in figure 23.”
• Linda: “the lollipop at the transport layer is correct and the others are wrong. Here is my reasoning. The NEL provides the service to the OSS (whether EMS or NMS or ...) to be provisioned. The OSS is the “client” and the network resource embedded management capabilities provide the service. The network element doesn’t ask the OSS to be provisioned; it is the OSS that asks the network resource to accept its provisioning request.”
• Connie: “there may be more than one way to look at these. I thought the component in a loosely coupled environment that offers an API is the provider (lollipop). I can’t find documents where the lollipop/sickle concept has been used down to a FCAPS function level. Our copy of the M.3060 diagram has the element function with both a lollipop and a sickle, so there was thought to be some element functions that are consumers. Perhaps we can’t say that provisioning is mostly one or the other for an element. In that case we should probably use “unqualified reference points”, e.g. plain lines… We will go along with whatever the team decides.”

4. Modeling methodologies
• TMN interface modeling – the new M.3020 spec
• Unified Modeling Approach (UMA):

i. Modeling process used by TMOC and OBF

ii. Requirements, Analysis, Design and Implementation

5. Review draft of liaison letter to ITU-T (SG-4 NGNMFG and SG-13 IPTV-FG) – by Yvonne

6. Cooperation with TMF:
• Work register status update:

i. TMOC-AIP-2007-029 – eTOM – GB921D Rel 6.0 ver. 6.1 – was updated to Release 7.0 – the document itself was uploaded as reference file (TMOC-AIP-2007-177) from the TM Forum – eTOM – The Business Process Framework – Addendum D: Process Decompositions and Descriptions – TMF GB921 D – see: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-177.pdf Please note: it was agreed that it is for use by the joint TMOC/OBF IPTV-OSS team, and only with respect to the work of the joint ATIS TMOC/OBF IPTV Operation Support System (OSS) Functional Requirements and Reference Architecture Document.

ii. The Work Register on IPTV Management and mTOP documentation (TMOC-2007-003.zip) – last discussed on the August 9th joint meeting:

1. The business justification as appears in the current Work Register:
- “Benefits to TeleManagement Forum: gain information and understanding concerning the ATIS TMOC work on IPTV Management
- Benefits to Liaison Partner(s): gain information and understanding concerning the mTOP-Service Management work. The document was not needed for the OSS doc”

2. We need to determine what our business need is to take next steps – the current WR either needs to be withdrawn, OR, needs to be updated to include the new business needs.

• SLAM – As part of the work register, ATIS have agreed to provide feedback/comment into the development of Release 2.0 of the application note:

i. A draft working copy of this effort is available on the TMF’s CWS, Laurent (who is also editor of this document) can indicate the exact location of the latest version.

ii. It is suggested that we join the end of the SLAM next conference call to answer any questions etc – no update.

• SDF Workshop

i. Feedback on Industry Group Positioning Map (IGPM) see: TMOC-AIP-2007-174 – Appendix 2 – SDF / Industry Group positioning Map (initial version). In particular comments on the “Requirements” and “Solutions” sections of the embedded workbook will be necessary

ii. Agree on document/s to be provided to the TMF’s SDF industry group by ATIS/TMOC and the mechanism to share these

• TMF’s new Service Assurance team (focus on fault management)

7. Work on issue 93 – Ordering API:
• IPTV Ordering Framework and API(s) - Working Text see: http://contributions.atis.org/UPLOAD/TMOC/AIP/TMOC-AIP-2007-175R2.doc (to be uploaded prior to the call)