TSG-S OMA (Open Mobile Alliance) Ad-Hoc Report Richard Robinson Chair - 3GPP2 TSG-S SC-20030519-008B_Eshwar Pittampalli’s (Lucent) comments/concerns embedded.

Slides:



Advertisements
Similar presentations
OMT RETREAT (WORK PLANNING). The UNDG Operational Guidelines for the Implementation of Common Services were developed in 2000 by an inter-agency.
Advertisements

Participation Requirements for a Guideline Panel Member.
Table of contents 1 Manual of Operational Procedures (MOP) 2
DEVELOPING A TECHNOLOGY PROJECT IN STUDENT AFFAIRS A Guide to the Process Paul Schantz November, 2010.
Global Business Blueprint Summary Presenters: Laurie Dempsey, CBP Lois McCluskey, eCP January 28, 2004.
Chesapeake Bay Program Goal Development, Governance, and Alignment Carin Bisland, GIT6 Vice Chair.
Chesapeake Bay Program Goal Development, Governance, and Alignment Carin Bisland, GIT6 Vice Chair.
- 0 /9- TTA Views on Criteria for Successful M2M Consolidation August 17~18, 2011 (Washington DC, ATIS Building) TTA M2MCons02_15 (Agenda 4.1)
Doc.: IEEE /324r0 Submission May 2001 Bruce Kraemer, IntersilSlide 1 PARTNERSHIP PROJECT DESCRIPTION During the meeting held in Copenhagen, 2.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
The Proposal. Project Proposals Genesis of Proposals: They can result for formal requests (e.g. Request For Proposal, RFP) They can be unsolicited (e.g.
An Introduction to the Hennepin County Hennepin County GIS Technical Advisory Group (eGTAG) 10/20/2009.
EVALUATION AND QUALITY ASSURANCE STRATEGY PRESENTED BY DR SHYAM PATIAR.
Runway Safety Teams (RSTs) Description and Processes Session 5 Presentation 1.
RST processes Session 6 Presentation 3. A framework for RST processes Establishing an RST Membership Terms of reference Work programme (schedule, agenda,
Doc.: IEEE /1454r7 Submission March 2013 IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process 20 March 2013 Haasz et al, IEEESlide.
NESCC Meeting March 28, Topics Accomplishments Since Last Meeting Program Management for NESCC Support to the NESCC Sponsor Committee Review and.
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
EARTO – working group on quality issues – 2 nd session Anneli Karttunen, Quality Manager VTT Technical Research Centre of Finland This presentation.
Slide: 1 27 th CEOS Plenary |Montréal | November 2013 Agenda item: 29 Adrian Simmons, Chair of the GCOS Steering Committee Update from the Global.
Space Technology for Emergency Response and Risk Reduction European Conference - GEO Welcomes FP7 Constanta, Romania 15 September 2006 United Nations platform.
Getting Involved in the Research Data Alliance Stefanie Kethers
ESMO Clinical Practice Guidelines: Consensus Conference (CC) SOP Edited by EDC-SC September 2013.
SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed draft.
SCFAH r1 Title: Working Draft “Ad-Hoc Recommendation to SC on 3GPP2 Future” Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.
TSG-S OMA AD-HOC RECOMMENDATIONS TSG-S OMA AdHoc.
Partnership Analysis & Enhancement Tool Kit Cindy S. Soloe Research Triangle Institute (RTI) April Y. Vance Centers for Disease Control and Prevention.
1 Status of PSC recommendations (January December 2007) Portfolio Committee on Public Service and Administration 14 March 2008.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
© GEO Secretariat Work Plan Guidance document 2 nd Capacity Building Committee Meeting, Brussels September 2006.
CJK9, Zhangjiajie, China 1/14 Discussion: [Drafted] 3GPPs works in CJK Cooperation CJK 9, Zhangjiajie, China April 8-10,2009 Changho RYOO
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Management Methodology
Committee on Earth Observation Satellites Ivan Petiteville, ESA Plenary Agenda Item # th CEOS Plenary Kyoto International Conference Center Kyoto,
3GPP2 Publication Process Training TSG-S PMT. December Presentation Overview Background OP Input and Intent Publication Process Overview The Revised.
TSG-S Project Coordination Recommendations Nick Yamasaki TSG-S Chair ABSTRACT: This document presents TSG-S recommendations for improved coordination of.
Application procedure From theory to practice Dieter H. Henzler, Steinbeis-Transfercenter Cultural Resources Management, Berlin.
TSG-S OMA AD-HOC RECOMMENDATIONS TSG-S OMA AdHoc.
SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future ver2 Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed.
An adoption phase for RDA WGs?. Background WGs end after 18 months WGs (and some IGs) produce outputs, but adoption of these outputs often only takes.
State of Georgia Release Management Training
1 Item 2.1.b of the agenda IT Governance in the ESS and related issues Renewal of mandates STNE Adam WROŃSKI Eurostat, Unit B5.
Advanced Project Management Project Planning Phase Ghazala Amin.
Subject:Proposed Liaison from TSG-X to BBF Date: 21 August 2009 Source: Chair, FMOAHG Airvana Contact: Doug Knisely cdma2000® is the.
Doc.: IEEE /0241r0 AgendaRich Kennedy, MediaTek IEEE /15 Regulatory SC Macau DRAFT Meeting Plan and Agenda Date: Authors: March.
Program Management Team Framework Strawman Vancouver June 2001 Sprint PCS ®
SCFAH r2 Title: “Ad-Hoc Recommendation to SC on 3GPP2 Future” – Working Draft Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.
© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
TSG-S Comments to TSG Chairs Regarding Proposed 3GPP2 Restructure Nick Yamasaki Chair, 3GPP2 TSG-S
REDD+ FOR THE GUIANA SHIELD Technical Cooperation Project Session 5 – Conclusion session Marie Calmel, ONF International December 11 th, nd Steering.
1 Source:Bob Plunkett TSG Coordination Ad Hoc Chair Copyright Statement The contributor grants a free, irrevocable license to 3GPP2 and its Organizational.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Implementing Program Management Standards at Duke Energy.
TSG-S OMA (Open Mobile Alliance) Ad-Hoc Report Richard Robinson Chair - 3GPP2 TSG-S SC D.
Commission Staff Working Document Free Movement of Workers in the Public Sector 18 January 2011 Ursula Scheuer European Commission DG Employment, Social.
June 24, 2016 UNAIDS Partnerships- Strategies, structures and social relationships Sally Smith Partnership Adviser.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
EIAScreening6(Gajaseni, 2007)1 II. Scoping. EIAScreening6(Gajaseni, 2007)2 Scoping Definition: is a process of interaction between the interested public,
TSG-S OMA (Open Mobile Alliance) Ad-Hoc Report Richard Robinson Chair - 3GPP2 TSG-S SC B.
European Regional Aviation Safety Group (RASG EUR)
31 January Table of Contents (1) 3- Draft Partnership Project Description22- The Partnership Project Agreement (1)3- Draft Partnership Project Description22-
1 30 November GPP2 SC Subject:Recommendations for 3GPP2-BBF Working Relationship Date: 30 November 2009 Source: Doug Knisely TSG-X FMOAHG.
Bow Basin Watershed Management Plan Revised Terms of Reference
Alignment of Part 4B with ISAE 3000
AANI SC Teleconference Agenda
IEEE 802 2nd Vice Chair last name at ieee dot org
Adult Education Survey Anonymisation Point 6
(Project) SIGN OFF PROCESS MONTH DAY, YEAR
Presentation transcript:

TSG-S OMA (Open Mobile Alliance) Ad-Hoc Report Richard Robinson Chair - 3GPP2 TSG-S SC B_Eshwar Pittampalli’s (Lucent) comments/concerns embedded. Also please look at contribution -008D of Shenzhen SC meeting for prior report of OMA AdHoc.

Page 1 SC B Contents Background & Assignment from SC in January 2003 Communication with OMA Technical Plenary Centralized Management via PMT Measures of Success

Page 2 SC B Background and SC Assignment Ref. SC R1, Section 13.1 – It was concluded that:  3GPP2 is still lacking in information regarding the current and proposed activities of the OMA (so is OMA about 3GPP2– How is this void being filled?),  3GPP2 might wish to engage in informal discussions (What would be informal?) with OMA representatives in an effort to gain awareness (Has there been any progress during the past 6 months??).  All TSGs should feel free to communicate with the OMA regarding gathering required information (This would result in a multiple sources/letters/individuals trying to gain access to the information from 3GPP2 and vice versa )  TSG-S will serve as a focal point for gathering OMA-related information and developing 3GPP2 needs (Why TSG-S, why not TSG-X? Network expertise is in TSG- X not in TSG-S..).  All efforts aimed at developing a potential relationship (Is this formal or informal?) between 3GPP2 and the OMA are to be undertaken either by the Steering Committee or by the Organizational Partners, as appropriate. OMA Proposed Framework 3GPP2 SC OP OMA BoD Liaison Committee TSG-S PMT (??) OMA Tech. Plenary 3GPP2 Needs

Page 3 SC B Background – OMA Ad-Hoc Conclusions April meeting with all TSG representatives and May meeting: u Prefer to operate within and establish plain language, non-binding working guidelines (Is this work in progress? Should we wait till this document is finalized and agreed to by the 3GPP2 community?) –  Within the spirit of the SC assignment  Establishment of guidelines is not a decision for specific work items but the establishment of procedures only  3GPP2 will need to establish document reference procedure similar to that existing with 3GPP today (Does this include IPR and Copyright issues?) u Consensus that the formal Framework proposal from OMA is inappropriate for the current working relationship (Why is consensus not required? ) TSG-S PMT (????) OMA Tech. Plenary 3GPP2 Needs

Page 4 SC B SC Action Recommendations Based on OMA Ad-Hoc review to date, TSG-S asks the SC to direct TSG-S to develop the following (as detailed on the following slides): u Develop procedures to establish open communications between 3GPP2 and OMA (Is this informal or formal? SC should do this directly without involving TSG-S) u Develop procedures for centralized management of the process internally within 3GPP2 (SC should do this directly.) Additionally, TSG-S asks the SC for approval to implement these processes on a single item (Are these processes or guidelines going to be approved by the SC or OP?), to be selected by the TSG-S PMT, for the specific purpose of the review ing and fine tuning these processes and internal procedures and to gauge OMA response to 3GPP2 requirements (i.e., test case) (How long is this test case going to be running?).

Page 5 SC B Goal of Relationship = Open, 2-Way Communication Process (Is this going to be correspondence or physical presence communication?) Purpose/Objective (Strategy) (Is this after we go through a test case?) u Periodic exchange of information concerning workplans to obtain a better understanding of the other’s (Who?) activities u On a case-by-case basis:  Identify potential items of shared, overlapped or duplicate work ( Are we assuming that OMA is going to decide on their own without getting any feedback from 3GPP/3GPP2/IETF/..,  Identify potential level of work coordination for, and  Define conditions and procedures in a potential agreement on use of other’s work (IPR, Copyright??) u Manage coordination activities including joint meetings (OMA, 3GPP2, and sometimes 3GPP) (Are we going to be taking the responsibility for these meetings?) u Confirmation of deliverables and scope of use of other’s work (????) (Are we going to be waiting for OMA deliverable to start our work in some cases?) Levels of Communication u JEMs/Workshops meetings with applicable OMA groups as needed (Should be both ways). u TSG-S and TSG-S PMT (Why both?) have direct liaison with OMA Technical Plenary and OMA subgroups for the purpose of implementing a centralized process management function (What is this process??) on behalf of 3GPP2. (TSGs will get it directly from OMA and will adjust their respective schedules.) u All other TSGs have authorization for liaison communications with OMA groups for the purpose of resolution of technical issues in the definition, development, and confirmation phases of the shared/owned work efforts (If all TSGs start communicating with OMA, where is the need for TSG-S to centralize this activity?) u Guests and observers at the other’s meetings (???) Potential Shared, Overlapped or Duplicate Work Items u Definition of work item that 3GPP2 should do itself or that can be entrusted to OMA ( Who is going to decide what can be entrusted?) u Definition of application/service requirements (What if they don’t have definitions and requirements from their end?) u Development of application/service (same as above comment)

Page 6 SC B Centralized Management – TSG-S PMT Responsibilities: u Assessment of current work items and identification of possibility and necessity of cooperation with OMA associated with each work item (Who is going got be deciding this?). u Assessment of possibility for future use of work items already in process in OMA (same comment as above). u Definition of work projects that can be entrusted to OMA. Actual definition of scope of work must be done in conjunction with 3GPP2 technical experts. and TSGs.(delete this) u Monitor and report status of work projects done by 3GPP2 (to OMA?) and by OMA (to 3GPP2?) including identification of critical path activities (of OMA work?) and projection of schedule for final deliverables Process: u Joint meetings with 3GPP2 internal groups (Who/When/Expenses?). u Monthly status reports to all TSGs, SC Chair, and 3GPP2 Secretariat (Is this different from the Meeting Minutes of OMA?). u Direct correspondence for project alarms (direct action required, e.g., schedule slippage, requirement issues) (Are we doing OMA work in letting us know their schedule slips?).

Page 7 SC B Factors for Success Pending approval by SC/OP, S-PMT would develop the rules/guidelines (only after clarifying all the issues raised in this and other correspondences from other members of 3GPP2; SC should develop any rules/guidelines itself – not the PMT.> Relationship is based on a “plain language” working agreement (What is “plain language” agreement?), not a binding contract. Active participation of 3GPP2 membership in OMA (Is 3GPP2 going to bear expenses to send a liaison to OMA meetings?) and in 3GPP2/OMA Liaison roles is crucial. Promote 3GPP2 member activity in OMA and determining WI’s, reviewing work being done and providing inputs (3GPP2 membership is already active in OMA. What additional activity is being referred to by this?) Start slow: (Is this only a after test case???) u Pick a few work items ( single test case or multiple??) that  can be fully defined,  distinguished between 3GPP2 and OMA (What does this mean?),  Agree (What??) on case-by-case basis, ( At the TSG level – not PMT)  Monitored closely during the development effort by OMA,  fully validated after completion (How do you validate? Is there going to be determining process?), and then  considered as a working model for future work entrusted to OMA. PMT must provide formal review of status and impact of relationship to the SC: (: Such formal review should be done by each concerned TSG, not the PMT.) u After 6 months u After one (1) year.