ffm message

Subject: FFM 1st Meeting, June 20, Meeting Minutes

From: "Nguyenphu, Thinh (NSN - US/Irving)" <thinh.nguyenphu@nsn.com>
To: "FFM TC List" <ffm@lists.oasis-open.org>
Date: Mon, 20 Jun 2011 12:10:03 -0500

Title: FFM 1st Meeting, June 20, Meeting Minutes

Hi All,

Enclosed email is FFM TC 1^st Meeting, June 20, 2011 Meeting Minutes. Thanks to Robin, Israel, Juha for sending me your notes.

Thinh

=================

FFM TC 1^st Meeting, June 20, 2011 Meeting Minutes.

1. Call to Order/Welcome + Volunteer for Note Taking

An informal, short talk, limited to housekeeping issues such

as conference bridge or F2F location issues; handle any

initial procedural matters if necessary.

Designate someone to take meeting notes for the first meeting

minutes; Convenor may call for volunteer(s). Text logged in

a community chat window may be used to supplement the

minutes taken by the designated scribe.

[meeting notes] Israel Beniaminy is the secretary.

2. Roll Call.

The list of Voting Members must be determined [2], as well as the

number of votes required for majority. All meeting attendees

(Members, Observers, Staff) are noted and minuted [3].

[meeting notes]

Robin's initial attendance record notes for

FFM TC meeting #1:

Present*

Israel Beniaminy *

Jiri Hlusi *

Johannes Lehtinen *

Juha Tihonen *

Ilkka Salminen [absent]

Peeter Pruuden [absent]

Sami Vaskuu *

Thinh Nguyenphu *

Timo Perala [absent]

Robin Cover* (OASIS Staff)

The list above was constructed by Chet Ensign as a list

of Eligible Voting Member for the FFM TC

http://lists.oasis-open.org/archives/ffm/201106/msg00004.html

Current TC roster:

TC: http://www.oasis-open.org/committees/ffm/

Members: http://www.oasis-open.org/committees/membership.php?wg_abbrev=ffm

(OR): http://www.oasis-open.org/apps/org/workgroup/ffm/members/roster.php

(TC Member view)

3. Nominations for Chair/Co-Chairs.

Any nominations posted to the TC's mailing list [4] are acknowledged,

and the floor is opened for additional nominations. The TC may

choose to elect a single Chair, or two Co-Chairs [5].

[meeting notes] Thinh Nguyenphu was nominated as TC chair.

4. Election of Chair or Co-Chairs

A Chair may be elected [6] by unanimous consent or by voice ballot.

A candidate must receive a Full Majority in order to be elected.

If the Convener is one of the candidates for Chair, an OASIS

Staff member runs the election. Once the TC has a Chair or

Co-Chair(s), the Convenor steps down and the meeting is handed

over to the new Chair(s).

[meeting notes] There was no other nomination. The decision passed unanimously: Thinh is elected as TC chair.

5. Welcome from OASIS Staff

Includes a short overview of the OASIS Technical Committee

Process [7], the OASIS IPR Policy [8], the TC Charter [9], and

the online help and tools [10] available to the Technical

Committee Members.

The FFM TC has been set up to use the RF on Limited Terms

Mode for IPR:

http://www.oasis-open.org/policies-guidelines/ipr#s10.2.3

[meeting notes] Robin Cover welcomed everyone on behalf of OASIS and reviewed some of the information TC members will need to know. Robin pointed out that much more information is available in the e-mail he sent prior to the meeting and especially in the references at the end of that e-mail.

6. (Optional) Review of the TC Charter

This is for informational purposes only; by joining the TC, the

members accept the Charter as proposed [9] and no further ratification

is required. It is sometimes useful, however, to provide an

overview of the plans and deliverables. Note that a Technical

Committee may clarify its Charter [11] at any time.

[meeting notes] Thinh reviewed the deliverables and their division into two tracks. Thinh reviewed the timeline for the TC's work.

7. (Optional) Discussion of Contributed Work

[meeting notes] see agenda #6.

8. (Optional) Adoption of Standing Rules

Some typical standing rules [12] are to allow motions to be made

via e-mail, or to allow chairs to use web-based ballots.

Standing Rules can be adopted at any time.

[meeting note] The TC adopted a standing rule stating that electronic ballots will have the same status as ballots performed during meetings.

9. (Optional) Assignment of Responsibilities

The TC may, at its choosing, elect or appoint the following:

secretary, editor, webmaster, and TC liaisons.

[meeting notes]

a. Thinh will be editor of both "Field Force Management Overview" and "FFMII Specification" until end of August. Following that, the TC may need to re-assign these roles.

b. Taking meeting minutes for the next meetings:

Johannes - meeting of June 27

Jiri - meeting of July 11

Sami - meeting of July 25

10. (Optional) Creation of Subcommittees

[meeting note] None at the moment.

11. Confirmation of Meeting Schedule

Along with determining the frequency, date and time of meetings [13],

it is helpful to determine who will be providing call-in numbers

and whether any video-conferencing tools will also be used. All

Members must be taken into consideration in the selection of

mutually-convenient meeting times and tools. Some Technical

Committees rotate calling times in an effort to foster global

participation and ensure that no one group is more inconvenienced

than another.

[meeting notes] Bi-monthly meeting conference call: June 27, July 11, July 25

Face to face meeting (@ Espoo, Finland) when the specifications are about 30% completion.

12. Any other business

[meeting notes]

Input contribution via email: FFMIIBusinessUseCasesFeatures20110620-D.docx, by Aalto University, Nokia Siemens Networks and Rossum

Jiri reviewed the document "Field Force Management Integration Interface - Business Driver, Use Cases, and Feature Requirements" contributed by NSN, Rossum and Aalto University, concentrating on part 4 (FFMII Business Drivers) and 5 (FFMII Business Use Cases). These parts were also discussed briefly. It was agreed that some of the raised comments should be followed up by proposing additional business use cases. Israel will contribute one or more such business use cases as soon as possible in order to enable TC members to review before the next meeting on June 27. Regardless, the next meeting should continue the review of this document by concentrating on part 6 (FFMII features).

Additional notes from Juha Tiihonen

Comments to architecture:

Israel: Can identify a lot from the Figure. Sometimes team leader would like e.g. change scheduling from Field. Interaction (with customer) is typical, and actual customer requirements cause blurring of what has been identified. (Jiri: May have tactical needs. ) Summary & point: Use cases may require that FFMII must be richer than originally planned. Click Software will provide corresponding use cases.

Comments to use cases:

Israel: certainly give good (ideas) for many real-life situations. Use case 4: maybe not sure about that one. This use case drives a much simplified interface. Might be more logical to include it in other use cases?

Some hints on forthcoming use cases: Situation: asset management. Need to access information about assets. Maybe e.g. switchboard, another asset is also relevant, need information on that. It may become necessary to create a new task on-the-fly; assign maybe to yourself. Sketching functionality into mobile. Jiri: Assignee could be a creator. Israel. Happens quite a lot. Quite a few assets are usually close.

Israel volunteers to write a use case for asset management. Provides it by next meeting.

13. Adjourn

======== References:

[1] 2.3 First Meeting of a TC

http://www.oasis-open.org/committees/process-2010-07-28.php#firstMeeting

[2] Requirements for TC first meeting attendance

http://www.oasis-open.org/committees/process-2010-07-28.php#firstMeeting-minMembership

http://www.oasis-open.org/committees/process-2010-07-28.php#dMinMembership

- five Eligible Persons, at least two of which represent OASIS Organizational Members

[3] Meeting attendees and recording attendance

http://www.oasis-open.org/committees/process-2010-07-28.php#membership

http://www.oasis-open.org/committees/process-2010-07-28.php#meetings