Skip to Content

Next Scenario of the BPX Community Project starting

On January 25, I First Pilot of Community Project successfully concluded! the conclusion of the first scenario of the BPX Community project.

After giving everyone the chance to get rested, we are now ready to start the next scenario. We are using the same fictional context (BigMachines Corp) with its various employees (BPX, Jr. BPX, process owner, etc.) that we all come to love but we have decided to take a look at a different process from a new perspective.  This time around, we are looking at the GRC-related effects on an invoicing process (thanks to Fongyan Mak for her help here).  We thought invoicing was a good choice, because it is present in almost every company. GRC affects every company in some fashion and therefore combined with the invoicing process provides a good foundation for the possibility of broad community participation.   

The idea is that there is an existing invoicing process in BigMachines Corp (perhaps, based on best practices) that must be changed due to some new regulation. Thus, we don’t have to define the whole process in this new scenario but just change those parts of an existing process that are affected by the new regulations.  We haven’t decided yet whether this existing process will be based on Enterprise Services or not (but I’m assuming that this will be the case. One idea might be to use the Supplier Collaboration for the Supply Chain  ES Bundle as our foundation). The interesting aspect would then be to discuss the GRC impact on an E-SOA-based process vs. the impact on a process that is not ES-based.

We still haven’t identified exactly which regulation we are going to use as the foundation but the choice in itself is interesting inasmuch as it must reflect the fictional context (a multinational corporation based in Europe) in which we have placed the scenario. Currently, our choices are: International Financial Reporting Standards (IFRS) or EU Directive 2001/115/EC.

Other details about this new scenario:

  • This scenario will include a wiki. Yes, there will be a wiki in a wiki. The roles involved in the scripts will place the deliverables and meeting minutes into a wiki. This will allow us to explore in more detail and more accurately how Web 2.0 capabilities can influence process improvement projects.
  • Although SAP technology will still play an important role in the scenario, we’d like to spend more time examining the non-technical process-relevant issues. This is also reflected in the initial script ideas that we have created.

Here are some projected themes that may also be introduced (Thanks Ranjan Baghel for adding them)

  • The enterprise used for this use case is moving towards global expansion. Expansion introduces new requirements in terms of various categories of invoices.
  • There are typical communication gaps between business & IT throughout the project
  • A difference in opinion exists between business units, which either prefer to focus on GRCs or give priority to core invoicing processes.

If you are interested in working with us in this exciting new project that is based on community collaboration, then just contact me or start contributing to the wiki content.

You must be Logged on to comment or reply to a post.
  • Richard,
    This is an interesting approach to developing shared knowledge.  I have a collaboration project between my organization and several other local governments.  I’ve been surprised by some of the difficulty some people have had doing (what I consider, anyway) relatively simple tasks such as joining a group at Yahoo.  Have you faced similar challenges?  How do you bring people from e-mail-land to the world of wikis, and podcasts and blogs?
    • Hi Leo,

      It is a definite challenge to get people to use these new tools. What you usually have is a small core of individuals who participate actively using these tools and many who just consume. You have to move these “consumers” step-by-step towards greater involvement. You have to “mentor” them – sit down with them and show them how to correct a spelling mistake in a wiki. Once they see how easy it is, they usually feel more comfortable with this environment.