Posts

Posts

  • Kathleen Day
    Learn what's new for July 2019 (19.07)5.0
    Topic posted July 8, 2019 by Kathleen DayBlue Ribbon: 750+ Points, tagged Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, Profitability, Profitability Analysis, Profitability and Cost Management Cloud in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    Learn what's new for July 2019 (19.07)
    Summary:
    Read about new features for July 2019, 19.06
    Content:

    I’m sure you have already read the latest What’s New post but here are my thoughts on the new items in 19.07:

    1. Our User Assistance (UA) team (fancy new name for the Documentation folks )  continues to pump out new videos.  There is an new overview tour of EPM Cloud

    Given the interest in last month’s post about our new EPM Standard Cloud and EPM Enterprise Cloud products, I highly encourage you to watch this video.

    1. Our UA folks are pumping out cool stuff left and right.  There is a new EPM Cloud Features Tool that lets you quickly find and filter features released each month for your EPM Cloud Business Process.  You can search all Business Processes or filter on individual ones.  The data goes back to the beginning of EPM Cloud in 2014!  The filtering capability is awesome and you can download it to a .csv or .html file for further searching locally.  This feature should be added to your bookmarks ASAP!
    2. Better Support for Rule Development and Testing
    3. Changes to Provisioning Terminology
    4. Removal of Support for Transport Layer Security Protocol 1.0 and 1.1

    And check out Upcoming Changes.....

  • Akancha Sinha
    Inventory Valuation Account1
    Topic posted July 3, 2019 by Akancha SinhaGreen Ribbon: 100+ Points, tagged Cost Management, Costing, Profitability and Cost Management Cloud in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    Inventory Valuation Account
    Summary:
    Derive Inventory Valuation Account based on Deliver to Location
    Content:

    We have a requirement to derive the Inventory Valuation account for different events raised during Transfer Order shipment and receipt. 

    We are using 7 Segments in Chart of Account. The second segment that is 'Logical Entity Identifier' needs to be derived based on 'Deliver to Location'.  The Source for 'deliver to Location' is not present in Cost/Receipt Accounting Application while creating Mapping Set. Please provide any other solution to this.

    Version:
    Release 13, 19B
  • Alecsandra Mlynarzek
    PCMCS Out-of-the-Box (OOTB): 4.Traceability
    Topic posted June 3, 2019 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged ABC, Activity Based Costing, Activity Based Management, Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, IT Costing, Profitability, Profitability Analysis, Profitability and Cost Management Cloud, Tip in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    PCMCS Out-of-the-Box (OOTB): 4.Traceability
    Summary:
    Traceability and transparency within PCMCS - Out of the box features
    Content:

    Traceability is the buzz word in any regulated industry. Being able to prove the numbers is crucial to all businesses, but it can be very time consuming and complex for companies that operate across multiple and diverse lines of business with a large pool of Channels, Services, Customers or Products. 

    Where is this cost coming from?

    Why have I been charged so much more this month for the same service compared to last month ?

    These questions should be easy to answer. Unfortunately, not all profitability analysis technologies are able to support a quick turnaround for providing the required level of detail.

    PCMCS has more than one option to easily provide much-needed answers.

    The Rule Balancing report is one of numerous out-of-the-box (OOTB) features included with an Oracle Cloud Service subscription able to support data traceability and transparency. For more details about the type of information the report provides and to learn the ease with which it can be set up for your application, review this comprehensive blog post.

    Besides Rule Balancing reports, PCMCS OOTB features support transparency within allocations and/or profitability models with Traceability maps.

    The focus of the current post is how to access, build, and use Traceability maps.

    The order in which I am covering the PCMCS OOTB features is directly related to the Intelligence menu options available in PCMCS.  As a recap, the 6 menu options are listed below:

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 1  1.  Analysis Views (How to create them, customize them and use them here)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 2  2.  Scatter Analysis (Setup and configuration covered here)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 3  3.  Profit Curves (Usage and features covered here)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 4  4.  Traceability

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 5  5.  Queries

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 6  6.  Key Performance Indicators

    The contents of this blog are based on the standard Bikes (BkML30) demo application, so you can follow the step-by-step details without having to go through an app setup from scratch. You can load and deploy this application directly from your PCMCS Instance through a couple of clicks via the Application menu using the + / Create button.

    Traceability – Intro

    The traceability maps, whether for PCMCS or in on-premise HPCM, allow users to graphically visualize the allocation flow. A chosen business segment can be traced through the allocation steps, either backwards or forwards, starting from a predefined point. Images  make up the map of a data point either flowing into the selection of members chosen by an end user to troubleshoot or flowing out of that selection into subsequent allocation steps.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 1

    Alex Mlynarzek - Traceability - 5-21-19 - Image 2

    Traceability is a great tool for troubleshooting specific intersections of detailed data such as base level accounts against a specific department. However, when there is a need to identify patterns or troubleshoot allocation results at a higher level, the Standard Profitability (the first on-premise version of the Profitability module) Traceability maps are not geared to handle such requests. In order to perform a high-level analysis in Standard Profitability models, users would have to revert to Smart View or Financial Reports.

    Being able to trace data at a summarized level of detail is the key difference between traceability in Management Ledger applications and traceability in Standard Profitability. Management Ledger allows end users to select the level within the hierarchy where they desire to launch or generate traceability, whether base level or otherwise.

    Traceability – Setup

    The starting point of any traceability map in Management Ledger is Model Views.  If you are interested in learning how to build and use Model Views, spend a few minutes reviewing this prior post.

    List of steps necessary to launch a traceability report in Management Ledger applications:

    1. Select a valid Point Of View (POV). The POV must contain data in order to display any traceability results.
    2. Choose a prebuilt Model View – example: IT Support Activities.
    3. Select a tracing dimension which will represent the detail that is the focus of your analysis (Accounts, Departments, Entities, Business Units, Segments, etc). The selected tracing dimension determines the focus or scope of your analysis and will be the one dimension that is displayed at base level detail or any other generation within the hierarchy.
    4. Trace Forward and Use Generation Selection boxes are selected by default.  Not selecting “Trace Forward” allows users to perform a “Trace Backward” action; in other words, figure out how the model arrived at a data value for a selected intersection, rather than how a data value was allocated out from that intersection to other recipienAlex Mlynarzek - Traceability - 5-21-19 - Image 3

    A report with the “Use Generation Selection” filter disabled will display the data at the base level for the Trace Dimension (in this example, Entity).

    Note: If a message is received indicating the Flash Player version is not up-to-date, check that pop-ups are enabled on the page to allow the download of the required update.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 4

    Alex Mlynarzek - Traceability - 5-21-19 - Image 5

    If the traceability report does not generate any results, check that the allocation rules were successfully completed for the referenced POV. Alternatively, if the POV calculated is successful, but data is not displaying on the Trace Screen, check that the application variables are correctly setup for Current Year, Period, and Scenario. Also ensure the Account dimension maps are specified in the Dimension Settings screen.

    Traceability – Display Options and Filters

    Traceability screens have 5 display options:

    1. Vertical (Top Down)
    2. Horizontal (Left to Right)
    3. Tree
    4. Radial
    5. Circle

    Within the traceability analysis, users can focus on a single rule. The tracing dimension in the previous example is Entity. The tracing dimension is the focus of the traceability reports – following how data was allocated into or out of a base level Entity.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 6

    To isolate a specific rule and separate it in a standalone diagram, click Shift+Enter or select the graphical option on the top of the Rule ID box.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 7

    End users have the choice of displaying the aliases/descriptions of the Entities rather than the code member names. If aliases have not been uploaded in the metadata of the application, then the report will still reference the member name codes, regardless of this choice.

    The following traceability report will display how operating expenses are reallocated /redistributed from each support entity (like IT, Facilities, IT, etc.) to the production entities using predefined driver configurations referenced in the Rule box.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 8

    Select the “Trace Forward” filter and keep constant all other prior selections in the initial traceability screen to display IT Support Activity charge out.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 9

    The “forward tracing” of IT allocations represents how data is allocated out to consuming departments such as Finance, Marketing, Outside Sales, Assembly, etc.  Remember the focus of the trace screen depends on the “Tracing dimension” selected. In this example, Entity was the tracing dimension.

    The top box, R0009, shows us the Rule Name relevant for IT allocations, the ruleset reference, the Driver used to allocate data to Targets – in this case : Desktop Laptop Users, regardless of Activity performed (NoActivity reference) as well as the amount / dollar value of the allocation : Allocation Out 1.338.000.

    Users have the flexibility to allocate data partially (to allocate only a % of the total value instead of 100%). That is what the Contribution % reference in the R0009 box represents. In this rule, the administrator/rule designer decided to fully allocate the IT cost to the consuming department instead of allocating it partially. Therefore, the 100% reference is displayed.

    In the case of the Bikes ML (Management Ledger) application, the Entity dimension has 4 generations. When talking about generations, the larger number, in this case number 4, represents the lowest level of detail. Generation 0 represents the Dimension name; Generation 1 represents the first set of children; Generation 2 represents the Children of Children, etc.

    Below is a radial display of the contribution charge out at base Entity level when no generation selection was made prior to launching the traceability report:

    Alex Mlynarzek - Traceability - 5-21-19 - Image 10

    We can see in this diagram how much each Target Department was charged for their IT bill.  The contribution from the IT department to each target is displayed as a %.

    Change the generation reference from 4 to 3. The higher the number of the generation, the more summarized the detail. The change of Generation reference will result in a summarization of the members of the Entity dimension to one level higher than seen previously.

    Alex Mlynarzek - Traceability - 5-21-19 - Image 11

    Notice how there is no longer an Entity breakdown at base level as we had in the previous screen when Generation 4 was selected, and the contribution percentages have been summarized to display the contribution % at a node level.

    In situations where a dimension has many levels within the hierarchies or an increased volume of base level members, the generation selection proves useful as it allows users to group data sets and display them in the same diagram without compromising the level of detail.

    Traceability – Customization

    As mentioned at the beginning of this post, PCMCS comes with several features to support traceability and troubleshooting, one of these features being the Rule Balancing report. In situations where the traceability maps are insufficient to support a meaningful conversation regarding bill out values, and a deeper dive into an individual rule is necessary, the Rule Balancing report covers such a request.

    While the traceability report has evolved in comparison to the Standard Profitability model, its usage is limited to situations where there is a need to troubleshoot specific data points while also having a visual representation as support.

    The most common alternative to graphical traceability reports are ad hoc reports in Smart View, either built from scratch or launched via the Rule Balancing report (described in detail in a previous post).

  • Alecsandra Mlynarzek
    PCMCS Out-of-the-Box (OOTB): 3. Intelligence and...15.0
    Topic posted April 22, 2019 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged ABC, Activity Based Costing, Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, Profitability, Profitability and Cost Management Cloud, Tip in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    PCMCS Out-of-the-Box (OOTB): 3. Intelligence and Dashboarding: Profit Curves
    Summary:
    Out of the box features with PCMCS - Profit Curves
    Content:

    Over the past few months I have identified a need within the Oracle Cloud client community to discover what can be achieved with the tools provided when subscribing to one or more Oracle Cloud Services. A lack of awareness of the features included with your subscription is an unmeasured cost and a missed opportunity to gain much needed insight without further spend.

    PCMCS applications – whether built for Fully Allocated P&L Solutions, Transfer Pricing, Shared Services Allocations or Customer/Product Profitability – have OOTB reporting capabilities available via the Intelligence menu that offer insight into allocation models with reduced effort. Here, we’ll explore how to set up, configure, and use such features and fully leverage the functionality that is included in the Oracle Cloud subscription cost.

    The order in which I am covering the OOTB features is directly related to the Intelligence menu options available in PCMCS.  The 6 menu options are:

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 1  1.  Analysis Views (learn how to create, customize, and use them here)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 2  2.  Scatter Analysis (discover how to set up and configure them here)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 3  3.  Profit Curves (this post focuses on Profit Curves)

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 4  4.  Traceability

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 5  5.  Queries

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 6  6.  Key Performance Indicators

    The content of this post on the standard Bikes (BkML30) demo application, so you can follow the step-by-step information without having to go through an app setup from scratch. You can load and deploy this application directly from your PCMCS instance through a couple of clicks via the Application menu using the + / Create button.

    Profit Curves – What Are They?

    If you are looking for a graphical representation for the concentration of your profit by either Customer, Products, Channels, or Funds, look no further than the Profit Curves section in PCMCS. Profit Curves, also referred to as Whale Curves, are used to identify which cluster of Customers, Channels, or Products generate the most profit. Profit Curves display a graphical representation of the relationship between economic profit and the quantity of output sold.

    The details of the profit or net income split by unit/service/customer displayed in a Profit Curve identify issues with:

    • expansion of a production line
    • breadth of services that may have a negative impact on profit
    • onerous clients consuming numerous resources without justifying the cost for the profit gained from their engagement
    • potential costing issues of “over” or “under” costing products (for example, overburdening a product or product line inappropriately);  a cost study should be performed to determine the appropriate allocation
    • pricing

    Information illustrated with a Profit Curve can be enlightening and help to put the focus on specific customers, products, or channels where the greatest profit attention is needed, indicating situations where a few products, services, or clients create enough profit to maintain the rest of the company’s offering. Profit Curves are key to strategic decision making, especially when dealing with competing projects and limited resources.

    During one of my recent PCMCS implementations, a Profit Curve proved valuable when the client’s staple product, advocated as being its best and most profitable, was discovered to be the least profitable after the implementation of an accurate cost allocation methodology in PCM.

    The easy-to-follow Profit Curve provides the insight needed to rapidly shift gears across product lines, ensuring alignment of management decisions backed up by real information.

    Building a Profit Curve

    There are several Profit Curves available in the Demo application BksML30. In order to build a Profit Curve, there must be a corresponding Analysis View that can be leveraged as the basis for data selection. See a step-by-step guide on how to build an Analysis View here.

    Analysis Views can contain multiple references to Measures and/or Accounts; however, the Profit Curve using the Views analyzes and displays only one measure at a time.  Users can choose to define names for the X and Y axis to add clarity to the Profit Curve information consumers.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 1.png

    Here is an example of a Profit Curve:

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 2

    The curve displays a listing of Net Income generated by Customer.

    From a Quarter-to-Date perspective (the Period selected at the top of the View), this Profit Curve indicates that all customers are profitable.  That may raise questions about whether or not the overhead is allocated appropriately or an even spread is used, thus skewing the results.

    Note: Data in the BksML30 model at the time this Profit Curve was generated was calculated only for January, confirming the Profit Curve display, as the profit by customer distribution was evened out at Quarter-to-Date level.

    The details of each customer/product/channel/segment and how much net income each is generating can be reviewed in the Category Analysis section. From a cost management and process improvement point of view, the right side is the most important.  This side generally represents customers/products/channels with a negative profit or that cost the company money.  While these customers/products/channels can’t always be eliminated, they can be watched and reviewed for pricing changes.

    Using a PCMCS Profit Curve

    There are options to filter data by the POV dimension, Period, or by metrics tied to Customers. For example, we can exclude from the analysis any Customers with Operating Expenses that are considered marginal. After defining the required filters, we can refresh the Profit Curve and review the newly generated pie charts.  Filters can be added to all available metrics and can be stacked up to generate any custom report.

    Below is an example of the same “All Customers” Profit curve, limited to January and with a selection of all Customers who had a Net Income smaller than 1 positive unit (USD or the currency defined in the PCM model) thereby highlighting Customers creating losses.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 3

    In the Details section of the Profit Curve, there is a count of 886 customers with a Net Income smaller than 1.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 4100% of the customers analyzed based on the specified criteria are unprofitable. The “Actual Profit” in this Details section can be translated into “Actual Loss” as the total accumulated value across the 886 customers is US$ -1,148,670.

    If there are doubts regarding the data intersection for the remaining dimensions in the PCM model such as Product or Entity, we can analyze related information through the configuration icon located next to the “Add Filter” menu. These selections are predefined in the Analysis View that was used during the creation of the Profit Curve, and you will not be able to modify them unless you modify the underlying View.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 5

    If questions are raised during the analysis on the Profit Curve screen and a list of details by Customer is requested, we have the option to launch a report from the “Analysis Links” menu under the Category section.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 6

    A report in the following format will be generated to display the Customer detail records along with all the other settings defined in the Analysis View.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 7

    This report can be exported in .xls format (“Export to Excel” option), and it represents a base level data dump report, in column format, containing multiple generations and references to attribute dimensions.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 8

    Note: When launching this report, users must check that the parameters have transitioned correctly from the previous screen. The Period parameter, which is saved to be Quarter-to-Date on the original Analysis View used in the Profit Curve diagram, will override any other selection made during run time analysis. If there is a need to revert to a specific month before launching the Export to Excel, users will have to make this update on the Filter /POV area and perform a data Refresh.

    We can make changes to the Analysis View to add further details (for example, Cost of Goods).

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 9

    For the 886 customers that are not profitable, we can dive deeper into their Cost of Goods data, Operating Expenses, or analyze whether or not the products sold are so heavily discounted that they no longer generate a margin.

     

    Pie Charts Related to PCM Profit Curves

     

    We can further analyze the resulting Profit Curve data by using the available predefined categories tied to the Attribute dimensions available in the PCMCS application, in the underlying Analysis View displayed in the adjacent Pie Chart.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 10

    The available categories to display the Pie Chart data for the Profit Curve chosen are the following:

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 11

    When selecting the Region category/attribute, we learn that the Southeast area contains 26,07% of all the unprofitable customers.

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 12

    If we change the Focus of the Category to be on Top 10% most unprofitable customers by Amount vs. All Customers/Number of Customers, the following information is displayed:

    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 13
    Alex Mlynarzek - Profit Curves - 4-18-19 - Image 14

  • Mohammad Alhindawi
    Customization on the AP invoice14.0
    Topic posted March 11, 2019 by Mohammad AlhindawiRed Ribbon: 250+ Points, tagged Asset Tracking, BI Publisher, BI Publisher Reports, BICS, Business Intelligence, Configure to Order-CTO, Costing, Dashboards, DVCS, Geneology, Innovation Management, Installed Base, Inventory, Maintenance, Manufacturing, OBIEE Answers, Order Management, OTBI, Procurement, Product Development, Product Information Management-PIM, Public Sector, Quality – Inspections, Quality – Issues and Actions, Report Scheduling, Reporting and Analytics, Sample Reports, SCM, Setup/Administration, SQL in Reporting and Analytics for SCM Cloud public
    Title:
    Customization on the AP invoice
    Summary:
    Customization on the AP invoice
    Content:

    Is it possible to do a customization on the AP invoice to validate certain fields and making some fields required based on filling of other fields?

    Version:
    Oracle Fusion
  • Alecsandra Mlynarzek
    PCMCS Out-of-the-Box (OOTB) Features: 2....5.0
    Topic posted February 28, 2019 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged ABC, Activity Based Costing, Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, IT Costing, Profitability, Profitability Analysis, Profitability and Cost Management Cloud, Tip in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    PCMCS Out-of-the-Box (OOTB) Features: 2. Intelligence and Dashboarding – Analysis Views and Scatter Analysis
    Summary:
    Out of the box features with PCMCS - Analysis Views and Scatter Analysis
    Content:

    A few days ago, I shared a post regarding Rule Balancing reports usage and customization. This post builds on that basis and covers intelligence capabilities, some of which are only available in the Cloud version of the PCM software.

    There are 6 menu options when accessing the Intelligence menu within PCMCS.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 1  1.  Analysis Views

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 2  2.  Scatter Analysis

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 3  3.  Profit Curves

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 4  4.  Traceability

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 5  5.  Queries

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 6  6.  Key Performance Indicators

    This post covers the first two menu options to explain how to set up Analysis Views and how to use Scatter Analysis.

    Analysis Views

    Analysis Views are the first set of reports available to end users within the PCMCS user interface.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 7

    These views represent a way to predefine and save intersections of members for future review.  The selections within Analysis Views are open to all dimensions within the PCMCS application at various levels within the hierarchies. This is the first step you need to take towards building or defining a dashboard for your PCMCS application.

    If you cannot create or edit an analysis view, then you need to reach out to your PCMCS administrator in order to review and adjust your security settings.

    The example Analysis Views for this post are based on the “Demo Bikes” application that can be deployed with a few clicks in your PCMCS instance BksML30.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 8

    A data slice is a combination of rows and columns along with the page selection, which, in this case, is the Period dimension.

    Any dimension that is not specified in any of the 3 areas (row, column, page) will be read at top level and will be displayed in the settings menu.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 9

    The Add Filter section allows you to filter the columns based on specific numerical values. In this case, the columns are represented by the Product dimension selections.

    To create an analysis view, click on the plus (+) sign on the main menu. The three tabs displayed will allow you to define a name and description as well as the setup for row and column dimensions. You cannot select more than a dimension for either rows or columns.

    Within the Row dimension selection, you can leverage different formulas applicable to the hierarchies within PCM such as Children of member, Member and children, Level 0 descendants, etc.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 10

    Columns do not have options for member formulas beyond the usage of User preferences.

    The row dimension will allow you to display further information such as generation or level details. For example, for the Product dimension, we can display the generation 3 and 4 information alongside the level 0 members, allowing us to expand our analysis to different product categories, or types.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 11

    Selecting new members within the Analysis Views will not impact the original data definition. If you choose to display data for any month other than the one that was setup and saved in the Analysis view, you can do so because the Page parameter is open to end user modifications. If; however, you want to update and store a selection change within the analysis view, you must perform such update via the Edit menu instead of simply selecting a new parameter on the screen in view mode.

    You may need to utilize the concept of period ranges when using Analysis Views in order to dynamically reference specific members of your Period dimension.

    Defining a current period for the application is mandatory in order to be able to create formulas dependent on time. This action is available via the Application menu by selecting the Edit application option and navigating to the tab called Dimension settings. Here is where you can define the current Period and the Current Year for your PCMCS application.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 13

    These settings will be applied when using the “Single…” or “Current” selection options within Analysis Views. Single (-1) Level 0 selection represents, in this case, the month of May, since the current Period selection for the PCMCS application is June. The Single (-1) Level 1 selections return Q1, since June is in Q2.

    Scatter Analysis

    Scatter Analysis graphs will compare one member’s values against another member’s values. The two members selected must be within the same dimension. Your PCMCS Demo application may not have any sample Scatter Analysis graphs. However, you can create one by leveraging the Analysis Views at your disposal.

    You can launch Analysis Views from within Scatter graphs.

    Note that saved Scatter Analysis cannot be reused or referenced in dashboards. You should use this section to create graphs for ad-hoc use outside of the dashboarding capability.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 14

    If you need to include Scatter Analysis within your dashboards, you will have a corresponding menu item that allows you to create dashboards within the list of available items.

    You can select an existing Analysis view, but you must reselect your X-axis and Y-axis dimension references.

    Alex Mlynarzek - Analysis Views and Scatter Analysis - 2-28-19 - Image 15

    Conclusion:  PCMCS Intelligence – Analysis Views and Scatter Analysis

    While there are many alternative reporting solutions to use in conjunction with PCMCS applications, assuming that both time and money are of essence in any project implementation, it is safe to conclude that using the PCMCS OOTB reporting features would be cost effective as well as efficient. The Intelligence screens shared in this post are included in the PCMCS subscription cost, and any end user of a PCMCS application with the right level of access can take charge and build the desired reports, saving end users in a location accessible to their peers while spending no time in iterations of reporting requirements and data validations.

    The PCMCS OOTB reporting features support not only troubleshooting, but also detailed analysis and reporting within one screen.  Such capabilities should not be ignored as they will surely add meaningful insight into finance teams’ day-to-day use of PCMCS.

  • Alecsandra Mlynarzek
    PCMCS Out-of-the-Box (OOTB) Features: 1. Rule...5.0
    Topic posted February 14, 2019 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged ABC, Activity Based Costing, Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, IT Costing, Profitability, Profitability Analysis, Profitability and Cost Management Cloud, Tip in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    PCMCS Out-of-the-Box (OOTB) Features: 1. Rule Balancing Reports
    Summary:
    Out of the box features with PCMCS - Rule Balancing reports- how to launch them, create extensions of such reports to enhance the data analysis capabilities in PCMCS and support traceability.
    Content:

    The other day, I was thinking about the times I used to study Finance, and specifically about a course regarding Interest and how it represents the value of Time. What is the cost, or value, of one’s time? – is it high, resulting in a higher interest rate per period, or is it low, resulting in a low interest rate per period? How much time am I willing to spend working in order to get that new car? How much time do I have before that competitor will outrun me and snatch that market share from me?

    This was how I started thinking about various out-of-the-box features (OOTB). Such features are often key in deciding whether to acquire a software/service/product because the one resource that we constantly complain about not having enough of is “time.”

    You are now reading the first blog post on OOTB features in PCMCS covering one of the most used Reports for data analysis as well as troubleshooting profitability calculation results. At the end of this blog post, you should know what Balancing reports are, where to find them, how to use them, and also how to further expand them with minimal time and effort invested.

    What are Rule Balancing Reports?

    Rule Balancing reports provide quick insight into the validity of the application results. These reports are powerful OOTB artifacts that can be further configured to cater to any custom application requirements in order to support validation of calculation results as well as contribution analysis and traceability.

    The PCMCS OOTB Rule balancing report is initially based on a Default Model View with a standard selection of upper level members for each dimension. Starting from this Default Model View, the administrators or users of the PCMCS applications can perform a deep dive analysis on more granular intersections and configure detailed reports for a ruleset or a group of rulesets they choose to investigate.

    The Default Rule Balancing report is available as soon as the application has been deployed, and it can be accessed via the Main Navigator menu found under the Manage section.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 1

    I will be using the default BikesML30 application to demonstrate the capabilities of the Rule Balancing reports. If you have loaded your sample application and cannot see any results in the Rule Balancing reports, check that you ran your end-to-end calculations for any given POV from the Manage Calculation Menu. The POV I have chosen for this demonstration is FY16, January, Actual Scenario.

    As you open the Rule Balancing menu, the Default Model View is the only view available when you initially set up your application and your allocation rules. Any other Rule Validation reports that you see within the Demo application besides the Default Model View have been built and configured outside of the out-of-the-box list of features.

    What are PCMCS Model Views?

    A Model View represents a predefined data slice within the PCMCS application; consider the model views as a set of selections of members for each dimension that displays only the relevant data points for a required intersection.

    Rule Balancing Report Example

    After running the entire set of allocation rules within the Demo BksML30 application, the Rule Balancing report should look like this:

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 2

    The description of each rule selected will be displayed along with the rule number. The rules will be displayed in the order that they were launched following the user-defined sequencing, regardless of the actual Rule Number/Rule ID that has been assigned.

    • The “Input” column enables users to confirm that what was loaded into the application matches the expected values received from the source system.

    • The Allocation In and Allocation Out columns validate the allocations performed by the application from both a balance perspective (Allocation In should be equal and opposite to Allocation Out) and a numeric one.  The balance aspect is particularly of interest when allocations are executed with custom calculation rules.  In these cases, two separate rules are typically required, one for the “credit out” and one for the “debit in.”  As such, there is a greater risk that the formulas for the outbound and inbound values will not produce amounts equal and opposite in total, thereby causing an undesired imbalance.  In these situations, the Allocation In and Allocation Out values are shown on two separate rows, and they quickly illustrate to the user the success of their calculations.

    Rule Balancing and Smart View Ad Hoc Reports

    Any highlighted data point/data value in the Balancing screen will allow you to further investigate the allocation step through a Smart View ad hoc report. These hyperlinks represent pre-built/pre-defined queries that point directly to the Essbase database, allowing you to further expand the analysis of a selected data point.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 3

    When you click on the highlighted number, a Smart View link will be downloaded to your workstation.

    As an example, you can see how the detail for Net Change looks like for the Custom calculation rule R0001 – Utilities Expense Adjustment in a Linked report in Smart View.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 4

    The column headers for the Rule Balancing report will list the relevant Balance dimension members. If there are members that are not populated, these will be automatically filtered out of the view. You can choose to display them by selecting View -> Columns and tagging the members you would like to display on your report – whether they have data or not.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 5

    For further information on what each of these Balance dimension members represent, check out my blog post on Demystifying the Balance dimension in PCMCS.

    You can view and edit the model view definition in the collapsed area between the POV and the Balancing report.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 6

    The Input data on this customized Model View is pertinent only to Operating Expenses rather than the entire pool of data. This is the reason that the total USD value may be different from data displayed on the Default Model View report.

    You can perform ad hoc edits to the Model View as you are using it, but none of the newly made selections will be stored. If you want to apply permanent changes to a specific Model View selection, you will have to edit the Model View in the corresponding menu.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 7

    Your Model Views can be defined in the same order of operations as your allocations, or you can choose to create Model Views that are more detailed and dive deeper into a custom grouping of rules, regardless of the ruleset to which they might belong. The only dimensions displayed in your Model View selection are the Business dimensions. POV, Balance, Rule, and Attribute dimensions are not represented and therefore are not open for selection. The data points you define in the Model view will apply to all relevant rules IDs that generated the new cells.

    Enhancing and Customizing Your Rule Balancing Reports

    In the Demo BikesML30 application, there are several standard Rule Balancing reports that are split by Ruleset while others are named “Trace.” The Trace Model views are built in order to support point troubleshooting of allocation areas that are either complex or open to high variation during each run.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 8

    If you want to use the Rule Balancing report values outside of the ad hoc capacity, you can export the report into XLS, but remember that such an export will not represent a Smart View report – it will simply be a listing of the information presented on the Rule Balancing screen, as some members displayed here do not have a direct equivalent in the application (Running Remainder, Running Balance). This export option can be found in the Actions menu, export to Excel, or by selecting the button in the below screen capture.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 10

    A new workbook is downloaded called RuleBalance, and the entire set of data displayed on your screen will be available in XLS.

    Alex Mlynarzek - PCM Rule Balancing - 2-7-19 - Image 9

    PCMCS Rule Balancing Drawbacks

    Rule Balancing does not allow filtering based on Attributes, UDAs, or Names.

    Rule Balancing hyperlinks open SmartView tabs called Linked View, and any new selections of links within the Rule Balancing report will overwrite the contents of the existing tab. If you start developing a report by using Rule Balancing, remember to always rename the tab in case you want to kick off another report for a secondary data point within the same workbook.

    Common Issues When Using Rule Balancing Reports

    “Rule Balancing Report Links Don’t Work”

    Your workstation must have Smart View installed before using the hyperlink feature within PCMCS. The latest Smart View version is available for download through the Navigator main menu under the Installations section.  For more guidance on generic EPM product patching, read the blog post Patch Today! Don’t Delay!

    When selecting a hyperlink in the Rule Balancing report, you should be able to see that a download has started. As you click on the downloaded content, a new Excel tab will open, and you will be prompted to enter your Cloud credentials in order to have access to the requested data point intersections. If you do not have Excel open at the time you are accessing the downloaded content, the prompt to enter your Cloud credentials may not appear on the screen.

    “I Can’t See Any Data in the PCMCS Rule Balancing Report.”

    If data is not displayed on the screen, you are looking at one of the following situations:

    1. There is no data loaded and/or calculated for the POV at the intersections you have defined in the Rule Balancing report. Check your job console to see if such tasks have been triggered and completed successfully.

    2. Your security setup is restricting you from seeing any data values. Reach out to your administrator to adjust data grants or application access.

    3. (This used to happen occasionally during on-premise implementations) If your Business dimensions are tagged as Label Only, check that the first child contains values. You may be able to see data at base level intersections within your application, yet the Rule Balancing report shows no vales due to the Dimension Type, Member Storage, or Aggregation operators you have defined in the metadata.

    “I Can’t Create a PCMCS Model View.”

    This restriction is based on provisioning. Reach out to your PCMCS Administrator for assistance with your profile or settings.

    Rule Balancing Wrap Up

    Rule Balancing reports are easy to set up and use.  They retrieve data quickly, are accessible to all application users through the same menu, and they should be the first stop during a model run to quickly identify if there were any issues with data allocations.

    Because Rule Balancing is a fast reporting tool with a predefined template OOTB, it is one of the commonly used troubleshooting reports for PCMCS, which can be leveraged for quick balance checks. It is also a mechanism for quick report building at detailed Rule level, a faster alternative to reading the Rule definition and manually replicating the intersections in a Smart View report.   Because these reports are system generated and their hyperlinks are based on application and rules set-up, there is no room for manual errors when building validations.

    Save precious time by leveraging the PCMCS OOTB functionality. In subsequent posts I will cover Intelligence screens (Analysis Views, Scatter Analysis, Profit curves, Traceability, and the setup of KPIs). If you have further questions on the usage of Balancing Reports within PCMCS, please reach out to our team of PCMCS experts at infosolutions@alithya.com.

  • Edward Calderon
    Cannot find the logical for rule R0003 of demo PCMCS4
    Topic posted January 25, 2019 by Edward Calderon, tagged Allocation, Cost Management, Costing, Customer Profitability, EPM, Profitability, Profitability Analysis, Profitability and Cost Management Cloud in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    Cannot find the logical for rule R0003 of demo PCMCS
    Summary:
    Allocation for products in rule R0003 of PCMCS demo environment
    Content:

    I have checked the rule R0003 and I did not find the logical for the allocation of all products. Please see the following screenshoot of the analysis I did in smartview.

    I really appreciate your help. Thanks in advance.

    Version:
    18.12.74
    Image:
  • Alecsandra Mlynarzek
    Demystify the Balance Dimension in Profitability and Cost...5.0
    Topic posted January 14, 2019 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged ABC, Activity Based Costing, Allocation, Cost Management, Costing, Customer Profitability, Enterprise Performance Management, EPM, IT Costing, Profitability, Profitability Analysis, Profitability and Cost Management Cloud, Tip, Transfer Pricing in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    Demystify the Balance Dimension in Profitability and Cost Management
    Summary:
    Understand how the Balance Dimension works in Management Ledger (PCMCS or HPCM) by defining each member within the dimension, its purpose, and the way the allocations flow is using these members.
    Content:

    Management Ledger models, whether Hyperion Profitability and Cost Management (HPCM) or Profitability and Cost Management Cloud Service (PCMCS), have been around for a few years, but I still receive emails asking for help with figuring out where the results are coming from. This request is often related to a lack of understanding of the Balance dimension. Here are some key pieces of information regarding this system dimension, how it works, how it should be used when defining allocations and integration jobs, and how to leverage it to troubleshoot your allocations.

    Before we have a look at each member within this dimension, let’s go over some basic rules that govern the creation of an HPCM or PCMCS Management Ledger (ML) application:

    1. All HPCM or PCMCS ML applications must contain just one dimension named Balance
    2. Members and their properties cannot be edited or removed.
    3. You don’t need to import a file in order to load/setup the Balance dimension; members are created automatically when deploying an application for the first time.
    4. You can choose to rename the Balance dimension (translate it into another language, for example) when you first set up the application in PCMCS.

    For the most part, the Balance dimension members are quite easy to follow and understand, but familiarity with usage guidelines helps to avoid issues during development and supports troubleshooting.

    Demystifying the Balance Dimension in PCM - Image 1

    • Input — Used to store data input/pre-allocated data sets, whether these are pool or driver data sets. Data is generally loaded against this member in combination with the NoRule member. Input can be populated through custom calculations, but it is generally advised to keep it dedicated to valid data loads/input rather than for storing calculated or allocated results.
    • Adjustment In —Adjustment In can be used for manual adjustments to the Input data prior to running allocations. In this case, the Adjustment In data will be loaded against the NoRule member. Any manually submitted data on the Adjustment member against a Rule ID member may be eliminated during the subsequent data loads and calculations. Adjustment In can also be used during custom calculations to store intermediary values or calculated driver data.
    • Adjustment Out —Same usage as for Adjustment In, but with a negative data value.
    • Allocation In — This member will be populated against the Destination or Target intersection for the allocation rule.
    • Allocation Out —This member will be populated against the Source intersection of the allocation rule and the corresponding Rule ID member, or against a predefined “Offset” intersection that is custom defined for a given rule.
    • Allocation Offset Amount — Displays an amount that further reduces an Allocation In member, if one was used in addition to the Allocation Out. I have provided an example of how this member is populated and used in a lower section of this post.
    • Net Change — represents the total change for a given intersection, regardless of alternate offset actions.
    • Net Balance – sum of Input (initial data loaded) and any Net Changes made to the same intersection.
    • Remainder — Displays the difference between Allocation In and Allocation Out plus Allocation Offset Amount, if any.
    • Balance — The amount resulting when adjustments, allocations, and offsets are considered.

    Rules assign funds to destinations based on the way you have defined the allocation logic (member selections, sequencing, concurrency, etc.). “Allocations in” and “allocations out” are being generated upon executing the calculations of the Profitability model. Each pair of adjustments and allocations (the “in” and the “out”) should result in a zero sum in order to balance the transaction. The Input member is affected by each adjustment and allocation. The difference between what was taken from Input and what remains at the end of an allocation will be accounted for in the Remainder.

    The Remainder member is the source of your allocations, not the Net Balance member, as most would think.  Remainder takes into consideration alternate offsets and ensures we do not perform a double booking or a double allocation of the same data source, regardless of where the offset was applied.

    To further explain the Balance dimension usage, I have used an example from the Bikes default application BksML30, which can be deployed into PCMCS through a few clicks.

    The original application had only one adjustment Rule populating the Adjustment In member. I have copied that rule and reused it to demonstrate the same usage for the Adjustment Out member. Remember the adjustment out aggregation operator is still +, so if you want to offset data sets, you must use the appropriate signage for your data; in other words, negate the result either via a multiplication with -1 or by simply adding a – to the formula.

    The new ruleset contents will look like this:

    Demystifying the Balance Dimension in PCM - Image 2

    Our initial data set is loaded on the Input/No Rule combination for the two accounts – Rent and Utilities – on the intersection with Corporate Entity.

    The data adjustments are stored against Adjustment In and Adjustment Out.

    Demystifying the Balance Dimension in PCM - Image 3

    In order to further illustrate how to correctly follow the allocation process, I split the original Reassignment rule into 2 rules, each dedicated to its own account. I also updated the metadata by adding two new Account siblings to Rent and Utilities as offsets for each account.

    Alternate offsets are simply intersections of members where you would like to store the offset data point, if it should differ from the source of the allocation.

    The Remainder member demonstration is connected to the usage of alternate offsets, and before we go into the details of the numerical example, I would like to list out a few rules for setting up alternate offsets:

    • Alternate offsets are available for selection only in standard allocation rules. For Custom calculations, your Offset custom calc would have to be pointed to the appropriate “alternate” target.
    • All dimensions, including the ones predefined in the rule context, are repeated in the Offset screen as soon as you select “Alternate Offset Location.” You must select a single base level member for at least one dimension.
    • There is no “Same As Source” (SAS) option for offsets. The dimensions that must be offset on the Source intersections can be left blank in the Offset screen selections.
    • If each source member selection has its own offset, you will have to split the rule up into as many granular rules as needed in order to cover the individual offset selection. For example, if you have 6 accounts, each with its own offset account equivalent, you will have to create 6 standard allocation rules to create the individual offset selection for each account.

    Going back to the numerical example and the usage of the Offset tab, in the update rule I have selected the below member intersections:

    Demystifying the Balance Dimension in PCM - Image 4

    The Source account was Rent, target is “Same as Source” (SAS), and the alternate offset account is FACOffset_Rent.

    After the rules are executed, we will see the results below; focus on the Allocation Offset Amount member and the Allocation Out Member.

    Even though the offset was applied to an alternate account for both Rent and Utilities, the allocation engine correctly identifies the Remainder of these two accounts as being 0.

    1. The first step behind the scenes is for the allocation to correctly distribute the data to the target intersections.
    2. The second step is to perform the offset on the intersection specified by the user, if different from the source intersection.
    3. The third step is to copy the Allocation Out value onto the Source Intersection members, on allocation Offset Amount member. This final step is performed via a custom calculation embedded in the PCMCS generated scripts which ensures there will be no double counting of pool data.

    So even though we “moved” data from the Rent account, Corporate Entity, to other Entities, on the same target Account, the offset was performed on an alternate member. This allows us to create a report with Rent (Input), Rent (Allocation In) and FACOffset_Rent (Allocation out).

    This is not a typical example of how alternate offsets are used from a functional standpoint, but it helps explain the mechanics behind the scenes. This alternate offset option is mostly used in cases where a Bill Out account and a Chargeback account will differ and allows users to trace which portion of a chargeback account is coming from different source accounts.

    The final goal of an allocation is to generate a Remainder member with a value of 0. This ensures the total allocation of a pool data set, whether this was loaded or received from prior allocation steps. If the Remainder member has a positive value, then it is indicating that you have not fully utilized your pool data. If the Remainder member has a negative value, then you have overutilized your pool data which may be, in some cases, intentional.

    Demystifying the Balance Dimension in PCM - Image 5

    In situations where you will not give access to the PCMCS ML application to users who need to understand the various components of a data point flowing through the allocation steps, due to licensing costs or other considerations, the usage of alternate offsets throughout your allocation flow might be helpful.

    When talking about reporting out of PCMCS ML, our clients always emphasize simplicity, and we often get requests to remove the Rule and Balance dimensions from final reporting solutions, to cancel the noise and give finance users solely the core information. In such situations, the usage of alternate offsets has proved beneficial as these finance users can still follow the flow and components of a cost without having to deal with the rule by rule detail. If further investigation is necessary, this can be pursued within the PCMCS ML model itself rather than in the external reporting solution.

    If you need further help with figuring out the purpose and usage of the Balance dimension within PCMCS, email us at infosolutions@alithya.com. Our PCM Center of Excellence team is ready to share leading practices and industry-specific solutions that accelerate your ROI and expand the capabilities of your chosen profitability software.

  • Alecsandra Mlynarzek
    Cloud vs.On-Premise Comparison for Profitability: All You...5.0
    Topic posted December 18, 2018 by Alecsandra MlynarzekGold Medal: 3,500+ Points, tagged Allocation, Costing, Enterprise Performance Management, EPM, Profitability, Profitability and Cost Management Cloud in Enterprise Performance Mgmt > Profitability and Cost Management public
    Title:
    Cloud vs.On-Premise Comparison for Profitability: All You Need to Know
    Summary:
    A brief comparison of HPCM with PCMCS in table format: easy to reference, easy to follow and covering the most important aspects of the software
    Content:

    In a previous post, the history of Hyperion Profitability and Cost Management (HPCM) was discussed along with which modules made it to the Cloud. If you are after a more clear-cut comparison between Cloud and on-premise, the below table should fit the bill. Tables generally cannot provide all the needed context, yet they are, at times, the best starting point to understand the benefits and capabilities of one solution compared to another.  The below PCMCS vs. HPCM table is not exhaustive, and if you have questions on any of the items covered, email us and we will provide further details.

    PCMCS 12-11 Image 1

    Choosing between on-premise and Cloud depends on which factors are the most significant barring the overall licensing cost.

    Allocations and data assignments cannot have “If” statements attached to them in the on-premise version of the software – a feature fundamental to supporting Tax transfer pricing capabilities.

    The cross-dimension mapping is a functionality that is not available in HPCM. This mapping ensures the assignment of data sets to the same ID/name across multiple dimensions by using the “Same as Source but Different Dimension” option within PCMCS to support intercompany activities. This feature alone, or the lack of it, may significantly impact the design of an application and the overall complexity of allocation flows.

    Features available in the Cloud but not yet released in on-premise solutions could tip the scale to favor the Cloud option when all other aspects surrounding a Cloud implementation no longer appear to be as pressing. Out-of-the-box content such as overnight backups, full application, and data restores that are at the business users’ fingertips – not to mention the reporting and dashboarding included in the Cloud version – are all differentiators of a product that enables business users to control their allocation process and methodology from its inception.

    While there may be exceptions to the trend where on-premise solutions can have advantages (modules not available in the Cloud, for example) and, therefore, represent the best option at a given moment in time, the reality is that the future is being developed in the Cloud and for the Cloud, and at some point the shift will most likely no longer be an option, but a necessity.

    If you need help making a decision with an existing implementation or you would like more details about HPCM vs. PCMCS to make a better informed decision, email us at infosolutions@alithya.com. Our PCM Center of Excellence team is ready to share leading practices and industry-specific solutions that accelerate the ROI and expand the capabilities of your chosen software.