Uploaded image for project: 'Technical Committee Administration'
  1. Technical Committee Administration
  2. TCADMIN-929

30-Day Committee Specification Draft Public Review Request for Field Force Management Integration Interface Specification

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: First public review
    • Labels:
      None

      Description

      Submitted on Wednesday, May 9, 2012 - 15:24
      Submitted by user:
      Submitted values are:

      Submitter's Name: Thinh Nguyenphu
      TC Name: Field Force Management (FFM) TC
      TC Email Address: ffm@lists.oasis-open.org
      Work Product Title: Field Force Management Integration Interface
      Specification
      Committee Specification Draft ##: CSD01
      CSD URI: TBD
      Additional Resources :
      http://www.oasis-open.org/apps/org/workgroup/ffm/download.php/45965/latest/FFMII_V1_0_WSDL_Schemas_WD01.zip
      Approval Link:
      http://www.oasis-open.org/apps/org/workgroup/ffm/email/archives/201205/msg00018.html
      Abstract: This document describes the Field Force Management Integration
      Interface (FFMII). FFMII provides a flexible interface between Enterprise
      Resource Management System (ERMS) and Field Force Management System (FFMS).
      The
      role of ERMS is to take a holistic view at work scheduling and resource
      allocation from the corporate point of view. For this purpose it needs to
      manage
      individual units of work performed without strong supervisory guidance (Field
      Work) in a way aligned with the business objectives of the company. The role
      of
      FFMS is to communicate with available set of workers (Field Force) and to
      provide individual workers (Assignees) performing Field Work with technical
      means of accessing information about and sending feedback on work assigned to
      them. While ERMS defines the structure, content and resource allocation of
      dispatched work, FFMS is responsible for communicating that information to
      the
      field and enforcing any specified constraints on user provided feedback. For
      facilitating structured communication between ERMS and FFMS in heterogeneous
      scenarios, FFMII defines flexible mechanisms that enable Work Request
      modeling
      (data content, workflow), exchange, work history collection, and collection
      of
      data from the field. Information carried with work requests, work request
      structure (work-flow, schedule) and data to be collected can all be defined
      dynamically 'as data'. This data driven architecture makes FFMII very
      flexible and adaptable to numerous industries. Additional FFMII capabilities
      include Field-Initiated Requests that facilitate structured requests and
      reporting information outside the usual work flow, such as reporting absence,
      requesting additional work, or providing a sales lead. Reference Data
      Management
      provides means to establish custom data repositories with arbitrary content.
      This enables e.g. input value selection, content validation, or delivery of
      documents to Field Force. Furthermore, flexible Integration Topologies are
      supported. Further flexibility is provided by scalability of FFMII itself:
      Basic
      features of FFMII are mandatory, and some features are optional. This allows
      both simple basic implementations and a range of more complete
      implementations.
      TC Description: FFM-TC approved the FFMII Specification and all supporting
      files
      (WSDL and Schemas) version 1.0 for 30 Days Public Reivew.
      Notification List:
      Notes: For 30 Days PR, the package should include FFMII spec, WSDL and
      Schemas
      zipped files.

      The results of this submission may be viewed at:
      http://tools.oasis-open.org/issues/browse/TCADMIN

        Attachments

          Activity

            People

            • Assignee:
              chet-oasis Chet Ensign
              Reporter:
              thinhnguyenphu Thinh Nguyenphu (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: