To OASIS Members:
A draft TC charter has been submitted to establish the OASIS Field Force Management (FFM) Technical Committee (below). In accordance with the OASIS TC Process Policy section 2.2: (http://www.oasis-open.org/committees/process-2010-07-28.php#formation
) the proposed charter is hereby submitted for comment. The comment period shall remain open until 11:45 pm ET on 12 May 2011.
OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: mailto:email@example.com
. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/
. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/
. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail list.
A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar.
We encourage member comment and ask that you note the name of the proposed TC (FFM) in the subject line of your email message.
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information societyhttp://www.oasis-open.org
Primary: +1 973-378-3472
Mobile: +1 201-341-1393
Follow OASIS on:
OASIS Field Force Management (FFM) Technical Committee
Name of the TC:
OASIS Field Force Management (FFM) TC
Statement of Purpose:
Enterprises that deploy large field staffs to deliver services to their customers face a host of data use and integration challenges. As the on-site representatives of the enterprise, their field force serve as remote nodes for the entire organization, offering and delivering services, delivering information, committing the enterprise to future actions, and so on. Each of those "field work" operations may touch multiple central data stores, including:
-- the contact data in a CRM,
-- job ticketing (task tracking and completion) systems,
-- the enterprises's inventory and accounting systems, whether integrated into an ERP system or not,
-- records of completed installations, for purposes of product life cycle service and future customer relationship purposes,
-- sales, management and human resources systems tracking the field agents, and so on.
In addition to the challenge of connecting and coordinating multiple enterprise data systems, field force management also heavily depends on the ability to carry data across to the field staff, who often are at the other end of loosely-coupled, heterogeneous networks composed of many disparate nodes. The devices expected to work together and share meaningful data include mobile phones (enterprise and personal), smartphones, personal PIMs, laptops, company mainframes, and other special purpose devices, and are used in a highly mobile fashion requiring robust abilities to represent and reuse location data.
The term žField WorkÓ in this context refers to unit of work that is expected to be conducted by individual (or group of closely co-operating individuals) without need for strong supervisory guidance at each step.
Specification of such unit of work contains sufficient amount of information necessary for accomplishing expected activity in self-guided way, within expected time window and resulting into desired outcome.
Such a task may be completely independent of other activities, or be part of a larger project where number of activities are planned for and scheduled in relation to each other.
In the context of FFM TC effort, field work is not limited to particular industry segment or activity type. For example, field works in telecom, utility, facility maintenance, community services, construction, and others would be valid subject for FFM TC effort, as well as certain types of activities regardless of business segment (e.g. sales or field surveys).
The FFM TC will develop an integration interface that can be used between systems responsible for work planning and systems responsible for field request communication towards the addressable field force. In such scenario, a standardized, semantically rich and problem-domain-neutral interface is required. In order to enable fast delivery of fully integrated software solutions addressing the needs of both types of system.
Due to fast-changing business requirements typical for field service value chains that interface should be able to accommodate desired changes in content and interaction patterns without need for extensive customization of already deployed systems. The common data structures must be capable of rapid, flexible revision and extension, without disruption, to maintain the systems' ability to faithfully represent changes in business models, plans, and support structures.
Scope of Work of the TC:
The TC will specify a generic, extensible, vendor-neutral integration interface, based on open standards, for relaying field work requests between one or more work planning and one or more field communication systems. Principal use cases for the interface include:
-- field work request dispatching (including request updates and cancellations), and
-- collection of status and input data from the field in a reliable and scalable manner.
The TC may identify additional use cases for inclusion.
The FFM interface shall specify at least one protocol bindings. And the TC may specify bindings (or provide guidance) for use of multiple alternative protocols, such as a variety of messaging systems or formats, or different degrees of information security.
Out of Scope:
The FFM TC will not address implementation aspects of the systems generating field work requests, nor of the systems accepting and making those available to field personnel. FFM's projects is to provide an interface and data specifications permitting those two classes of black box to interoperate, generally without perturbing the behaviors inside those boxes. However, the protocol bindings, shared data models, and related interface requirements that the FFM Interface provides may impose some requirements on systems that employ it.
Testing materials are out of scope. This TC shall not develop FFMII conformance test suite materials (other than the conformance clauses as may be required within a specification), nor conformance certification methods for implementations of the issued specifications. For these and similar activities, a parallel Adoption Committee may be considered for creation at a later time, if deemed desirable.
List of Deliverables:
The FFM TC plans to produce several related deliverables within both the OASIS Standards Track and Non-Standards Track.
Standards Track Deliverables:
-- Field Force Management Integration Interface (FFMII) specification (primary base specification), which may be one or several related specifications as the TC deems desirable. The FFMMI may include one or more formal taxonomies or code lists for the compact and efficient re-use of recurring information. [ months from the first meeting.]
-- Such FFMII related technical artifacts (e.g., data models and machine-readable API) as the TC deems desirable.
Non-Standards Track Deliverables:
-- FFMII non-technical overview. [ months from the first meeting]
-- FFMII business drivers and design goals statements. [ months from the first meeting.]
-- Use case scenarios and exemplar models. [ months from the first meeting.]
The TC's deliverables shall re-use and leverage existing open data standards and architectures where possible.
IPR Mode Under Which the TC Will Operate:
RF on Limited Terms Mode.
The Anticipated Audience or Users of the Work:
The anticipated audience for TC deliverables produced within the OASIS Standards Track includes independent software vendors (ISVs) active in the area of work planning systems and in field communication systems. Similarly, systems integrators focusing on delivery of integrated and coherent model-driven solutions for respective customers will be candidates for using the standardized technology.
The anticipated audience for TC deliverables produced within the OASIS Non-Standards Track is business entities conducting field activities and seeking guarantees of interoperability between systems. Such businesses typically need to address different aspects of field operations and to support interaction between disparate systems.
Industry strategists, independent consultants, and device designers may benefit from the results of the FFM TC's work as well.
Language of the Technical Committee:
The TC will conduct its business in English.
Non-normative Information Regarding the Startup of the TC:
Similar or applicable work:
The proposers are unaware of any currently published work that fulfills the interface scope described here using open data standards. The following existing specifications and documents may be relevant or of interest:
- XML (W3C) as way of data serialization for exchange
- SOAP (W3C) as one of applicable protocol bindings
- xCal (IETF) for serialization of scheduling information
- OASIS WS-Calendar (in progress)
Date: Wednesday, 29 June 2011
Time: 9:00AM EDT
Location (in person or by telephone): Telephone
Sponsor: Nokia Siemens Networks
Meeting schedule and Sponsor:
Nokia Siemens Networks is the sponsor of these meetings. It is anticipated that the initial release of the FFMII interface shall be produced through regular [biweekly] teleconference meetings, together with [semiannual] physical sessions as the TC deems appropriate, until reaching a releasable state.
The meeting schedule for subsequent maintenance releases and interface extensions will be driven by identified need for enhancements, based on experience from existing deployments.
It is anticipated that deliverables produced on the Non-Standards Track will be developed through work in regular meetings and asynchronously on the TC's mailing list, with informal rounds of TC review comments and draft revisions, until deemed completed by the appropriate TC votes.
Names, Electronic Mail Addresses, and Membership Affiliations of at least Minimum Membership Who Support This Proposal:
Timo Perala, firstname.lastname@example.org, Nokia Siemens Networks
Pertti Lounamaa; email@example.com; Pajat Management.
Sami Vaskuu; firstname.lastname@example.org; Newelo Oy
Juha Tuominen; email@example.com; Rossum Oy
Juha Tiihonen; firstname.lastname@example.org; Aalto University
Primary Representative Statements of Support:
Timo Perala, Head of Services and Operations Standard, email@example.com, Nokia Siemens Networks. I approve the FFM TC charter.
Pertti Lounamaa, primary representative, firstname.lastname@example.org, Pajat Management. I approve the FFM TC Charter. Providing a standardized interface between workforce scheduling systems and mobile field data collection systems will help SMEs like Pajat Management to effectively address markets in collaboration with other vendors in ways that it could not do alone.
Sami Vaskuu, CTO, Newelo Oy, email@example.com, as the primary representative of Newelo, I approve the FFM TC Charter.
Johannes Lehtinen, Senior SW Architect, firstname.lastname@example.org, Rossum Oy. I approve the FFM TC Charter. Having supplied mobility related data transfer services since 2000, Rossum Oy warmly welcomes all standardization effort targeted at mobile work force management and field work reporting interfaces. We are confident that the FFM TC Charter will produce a high-quality outcome that will definitely boost the co-operation and cross-fertilization of various solutions and services in the field force management area.
Juha Tiihonen, Project Manager of Product Data Management Group, email@example.com, Aalto University, School of Science, Department of Computer Science and Engineering. I approve the FFM TC charter.
Thinh Nguyenphu; firstname.lastname@example.org; Nokia Siemens Networks
Contributions of Existing Technical Work:
Draft Frequently Asked Questions (FAQ) document:
Proposed Working Title and Acronym for the Specification(s):
The base specification shall be named the Field Force Management Integration Interface (FFMII) specification.