TM Forum Community

 View Only

  • 1.  Business process architecture

    Posted Jul 18, 2017 10:39
    How will the business process architecture of IoE/IoT be designed?

    ------------------------------
    Wang Jianmei
    Detecon International
    ------------------------------


  • 2.  RE: Business process architecture

    Posted Jul 19, 2017 00:51
    Wang, good question. In the IoE monetisation management and trust workstream we are beginning to look at that. We started looking at business scenarios and monetisation models. The next will be to look at management and the business processes for the different ecosystems. Our approach will be to do a gap analysis relative to eTOM, SID and TAM. We are expecting some changes here - but not wholesale changes. There will be impacts on the APIs to support the partnership and trust models which will be impacted.

    we will be covering these and other overlaps with the other workstream at Vancouver Action Week 25-29th September, join us to take part in the discussions. Baljit

    ------------------------------
    Baljit Sarpal
    Sarpal Consultancy
    ------------------------------

    Original Message


  • 3.  RE: Business process architecture

    Posted Jul 19, 2017 08:12
    Edited by System Oct 30, 2018 15:01

    The use of IoE can be in different application domains and at different scales (thousands to millions of connected systems / devices), and I am not very certain of the extent of maturity of BP's and if any notations have evolved. Probably in course of being defined. The process automation in a plant for instance classically depended on a P&I, which has the positioning of the connected devices and must thus dfine the control of such devices (example actuators and feedback sensors). The business is realized when we start to monetize the installation using the massive data or the potential of massive savings.

    A trend is to decouple the IoE systems from the comms network via use of a dedicated IP network on SIGTRAN or NBIoT etc. The SP processes will be O/BSS centric but partner processes will still be governed by a central controller like CISCO JASPER, and a gateway to O/BSS which enable an IoE environment to be seamlessly integrated with the O/BSS systems (for example to have proactive parent level tickets created on the controller).

    All major telco domains can thus be used transparently as in a conventional communication system, along with models for usage to bill. So the treatment of BP needs to be done in 2 stages. One in which a platform like JASPER will cater to the direct customers of the partner (entire inlife experience), and two, the SP to partner relationship. Whitelabelling can still be a possibility, where SP BSS takes the responsibility of the needs of the direct customers of partners.

    A link consisting of a useful 'cousin' in this respect: Enriching Business Processes through the Internet of Everything

    Cisco remove preview
    Enriching Business Processes through the Internet of Everything
    Connecting more people, data, and things to the Internet will help automated processes do more for an enterprise, its suppliers, and its customers.
    View this on Cisco >







    ------------------------------
    surojit mukerji

    ------------------------------

    Original Message


Related Content