• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Collaborative Enterprise Planning: Who Should Be Involved, And To What Extent?

October 4, 2018   SAP

Part 3 in the 10-part Collaborative Enterprise Planning series

Collaboration, by definition, involves people working together for a common aim. That aim is usually far bigger than could be accomplished by an individual working alone, mainly because of the unacceptable timescales that would otherwise be involved, the wide range of skills required, or a combination of both.

In the British Museum in London, there is a series of exhibits dedicated to the development of clocks and watches. Anyone who has taken off the back of an old windup watch can’t help but be amazed at the intricate nature of the mechanism. To work at all, the precision required is beyond most anyone’s comprehension, no matter what experience they have in working with metal. But to function with any degree of accuracy, the skills necessary are extraordinary. Yet back in the 1500s, clockmakers possessed those skills.

Or did they?

In the museum is a plaque entitled, “Who made watches?” The inscription reads:

Watches were not made by one craftsman working alone. Even in the 1500s, spring makers, gilders, and engravers worked alongside the watchmaker. By the 1700s, the making of watch mechanisms was becoming a specialist industry. Unfinished mechanisms were supplied to watch finishers. Dials and cases were then added ready for retail. The 1819 publication Ree’s Cyclopedia lists 34 separate trades involved in making a standard English watch.

The key to successful watch-making, as with business planning, is to carefully coordinate the skill and expertise of different people who work in different areas, but who are collectively working toward a common goal.

Because every department’s role in creating a business plan is different, managers are required to assess different data and respond in a way that makes the overall aim possible. This means that the traditional approach of using common templates, leaving users in the dark about the roles they play in attaining corporate objectives, just doesn’t work.

Planning to plan

The starting place for any plan is to decide on the overall aim of the plan. Plans come to fruition only when people take the right actions using the right resources at the right time. So it’s essential to define:

  • What is the overall goal?
  • What decisions need to be made?
  • What are the timescales for those decisions?
  • Who has to make those decisions?
  • What data do they need to review and analyze
  • What information do they need to supply and to whom?
  • Who will collect and approve any decisions proposed in the overall context of achieving organizational aims?

The above can be drawn out as a map of interactions, which ideally should be shared with all the managers involved. This, then, paves the way to developing an overall model in which the data can be held and, equally important, a process by which data is broadcast and collected.

The role of technology

The data model derived by addressing these questions might include internal and external data, historic and forecast results, as well as background information and textual notes on the objectives of the plan. There may be multiple models to handle the different levels of detail, but it is important that they the user can see them in a single aggregated view.

The only way to achieve this is with a modern intelligent finance solution that can cope with multiple, integrated models, where users are automatically restricted to the data they personally need. The solution must have an intelligent workflow capability that presents data and collects responses at the appropriate time.

Finally, the solution should possess a workflow “dashboard” by which senior management can see the progress of the plan and any areas where users are struggling to meet deliverables. This will allow interventions to assess any changes required to bring the process back on track.

The next blog in this series further explores technologies that support the collaborative enterprise planning process.

Follow SAP Finance online: @SAPFinance (Twitter)  | LinkedIn | Facebook | YouTube

CEP Blog CTA 1 Collaborative Enterprise Planning: Who Should Be Involved, And To What Extent?

Let’s block ads! (Why?)

Digitalist Magazine

Collaborative, Enterprise, Extent, Involved, Planning, Should
  • Recent Posts

    • Kevin Hart Joins John Hamburg For New Netflix Comedy Film Titled ‘Me Time’
    • Who is Monitoring your Microsoft Dynamics 365 Apps?
    • how to draw a circle using disks, the radii of the disks are 1, while the radius of the circle is √2 + √6
    • Tips on using Advanced Find in Microsoft Dynamics 365
    • You don’t tell me where to sit.
  • Categories

  • Archives

    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited