MS SharePoint / SQL refers to Microsoft Sharepoint, a web-based collaborative platform, being used in tandem with Microsoft SQL Server to provide business intelligence analytics and reporting. They can provide BI content such as data connections, reports, scorecards, dashboards, and more.
N/A
Workday Adaptive Planning
Score 7.7 out of 10
Mid-Size Companies (51-1,000 employees)
Workday Adaptive Planning streamlines planning workflows, using AI and real-time data integration to improve collaboration and provide predictive forecasts for better strategic analysis.
As I mentioned in my previous answers, MS SharePoint is very useful as a shared drive for the organization and is very easy to manage. It also helps us import data from SharePoint directly into PowerBI for creating reports. According to my understanding, only share link features should be improved.
We're a mid-size organization working with a shoestring budget and an IT skeleton crew...not much room to dedicate resources to a platform like this fully. Having it SaaS based is helpful for system management through their Helpdesk system, and a single platform also helps streamline the knowledge needed by our developers when integrating other business aspects to Workday.
It helps create dynamic plans for finances, operations and various functional units in an organization all under one platform
It helps in scenario modeling to help analyze various business events and report by any number of business dimensions including channel, customer or product
It can be integrated with any system including ERP, BI or CRM
Dashboards are not the best for graphs/charts. However, I have heard of companies using the dashboards for forecasting/budgeting. I would like to see Workday Adaptive Planning demonstrate this part of the feature.
Better security or locks to prevent deleting Actuals data - you are literally one click away from doing this.
On the web-based reports, better functionality when needing to reverse the sign in calculations - right now it is only available for revenue vs. expenses.
This was a long-term buy-in from a corporate perspective, to remain in the SharePoint space. Migration is certainly possible, which is good for planning and having options further out. At this point, the only planned migration is to eventually move the architecture up to SharePoint/SQL 2013. At that point, we will be able to leverage some greater efficiencies, some enhanced content design and management features, and some more current social features. It is well worth a full consideration in any shop looking at a new implementation of or migration to SharePoint (although you will probably be considering 2013 versions or beyond in those discussions), but the platform should be a strong competitor to any alternatives. Realizing the capability of a fully-branded and customized website was not part of the original choice for the architecture at Lincoln, but seeing it implemented and functioning now with this capacity far beyond original expectations has certainly cemented plans to continue using it.
For one we're in way too deep to not move forward with Adaptive. We're integrated with Workday, we do a ton of reporting with Adaptive, and it's working very well for planning and forecasting. No reason to look back or change course.
I gave this rating due to MS SharePoint being a big help with our userbase. We have a lot of users that are just old enough to not have much technical skills or they have been in this industry long enough to where they haven't really needed to utilize much technology. MS SharePoint helped us move beyond that barrier without too many bumps and bruises.
It is overwhelming at first, but once you really get to know it, you realize it is fairly simple and customizable, and then it has a lot more limitations than you first thought. Realizing those limitations and finding workarounds is when you know you've mastered the software.
There haven't been any lately. The only one issue I can think of is when there was an update in Adaptive that altered our reports. Before I realized there was an issue, Adaptive reached out to let me know, so that it could be fixed.
All aspects of Adaptive Insights perform well. One area that I wish was quicker was integration. When importing data from Intacct our accounting ERP platform, it can sometimes take 4 hours for the import to process. The earlier imports are done, the quicker they complete. My estimate for a quick upload is about two hours.
I've only had to call in to support on one occasion but they were able to work though our issue and find a solution that did fully resolve the issue in a timely manner. I can't always say the same about support from other companies so it was a refreshing change to have support that did help.
Whenever we have had any questions, issues, or concerns, the support has been quick and thorough. [This] allow[s] us to be able to fully resolve any issues, or be connected with the right group quickly to attain the result we were after; be it from simple formatting to adding new detailed reporting.
This was extremely helpful so that they could walk you through the model and teach you more about the complexity of various areas. It is most helpful when it is specific to your organization's model. The larger in-person trainings were helpful but they tended to be more generic and entry level. The trainings that are more tailored to your specific needs are the most helpful.
They often times tended to be way too generic or entry level. They would also become sales pitches to upgrade or get new Adaptive Planning products. The questions in the training would be very niche and specific to other organizations. They were rarely helpful to the group at large.
Trust the expertise of very strong 3rd party implementers. Having deployed Adaptive at a separate company before, I thought I knew it all (hubris, I know). Fortunately, I began to (very quickly) trust the judgment of our Carlson implementation team, and they provided invaluable insights and best-in-class processes that have benefitted me and my team greatly.
At the time of the two large projects, SharePoint was the enterprise solution so we were required to use that. We have since lobbied the enterprise teams to review and consider Atlassian Confluence and were successful. Confluence is cheaper than Sharepoint which is why we wanted to bring that in. The enterprise has now made Confluence an enterprise solution as an alternative to SharePoint. After using both I think SharePoint has many more add-ins than Confluence. It has much more customization ability than Confluence. SharePoint is not good for mobile readiness. Confluence is so there is a difference that might lead you to Confluence over SharePoint. I would also say that SharePoint is very document-centric and that Confluence has better KM than SharePoint does. even with the use of SQL Server. We were told that we could not use Google Drive even though it had features we liked.
Workday became our choice because it is fully web-based and easily integrates with other systems. The learning curve for Workday was shorter than that of Dynamics. The reporting tools in Workday are more user-friendly than that of Dynamics. However Workday did not have Check Printing tools which are available in Dynamics. The organization started a project to digitize all financial transactions so it was not a priority feature. When it comes to scaling up the functionalities of Workday it was much easier than Dynamics.
We went from 2 users to 70+ users over a 2 year period of time. The application scaled wonderfully. 65 of those users were non-finance users so they were able to quickly learn the software and prepare budgets quickly and efficiently. That is the power of Adaptive and its ability to scale
It's facilitated a better financial literacy and management by the non-financial managers in the company, giving them a much better ability to see what they're spending, control it, and plan better in the future.
It's hard to quantify the ease of model and version management, but we could never do what we're doing now with our current staff. It would take a small army to replicate anything close to what Adaptive pulls off using Excel, if it's even possible.
