Recently active
Feature Description: In SPP, SKU Margins are always based on Standard Price and Standard Cost. However, depending on the customers’ requirements, they might want to calculate it using any price or cost bucket. So, we need to provide the flexibility for them to be able to use any bucket to calculate the margin. Benefits: Flexibility and accuracy in margin calculation and reporting.
Ability to see a holistic view of the financials for all the regions in a single screen, including Revenues, Profits, and Margin. Also identify top 10 part groups that are performing best in the market. Compare previous year (YTD) revenues and profits.
I just looked in SPP 11.4 and found that we are still not able to figure the SKU - Needs New Price flag on the General tab of the Pricing Worksheet. This field should be something that I can display. Can we get this added in the next release?
Currently when any user logs in, he is always taken to pricing home page. But it could be cases that user would want to always start his day from a different page, say, pricnig actions, or pricing worksheet. In this case, user would then need to navigate to that page, increasing the number of clicks. So, we should provide the ability to allow users to set their specific home page such that when user logs in, he is directly taken to the specified page.
Incorporate Machine Learning in SPP for our system to recommend actions and guide user to better price parts and increase revenue and profits. Some of the Machine Learning use cases: Cluster SKUs by demand. Attribute vs profitability. Analyze similar parts and compare their profits and get a relation as to how a part attribute impacts the profit. Price/Pricing Rule Recommendation Analyze the financial history and recommend a business rule or even the final price that will give maximum profit. Approval Recommendation On the basis of approval history, automatically recommend approval actions if, say, a part's new margin is greater than or equal to the margin for the same part and was approved in the past. Elasticity Looking at the history, determine if the part is elastic or not and then recommend a new price for such parts.
In addition to the pricing at normal pricing locations, sometimes customers need to price parts at dealer locations, making them different from normal SKUs as interpreted by the system. Also the prices are not calculated in a complex manner, but are simply the offsets of a price at a reference location. We would like to add a feature where customer can generate new price for any part in the system at any number dealer locations, without increasing the SKU count stored into the system. Users would also be able define simple offset rule, probably using pricing offset management feature, and rounding rules and generate prices and upload them to price book. In addition to this, users would able to see the dealer location price history as well.
The Promotions module that existed in 9.6.4 and earlier versions doesn't exist in 11.x. This is needed for Komatsu and other customers. Some requirements from Komatsu: Promotions need to have a unique identifier for reference and reporting purposes. The promotion price will be applied to the Dnet price (standard price). When creating a promotion in SPP, the UI should have the option of choosing affected P/Ns by part attributes, individual P/N, or other attributes (Strategy Code, Segment, Division, etc). Promotions can be applied for all locations and/or single/multiple regions. Promotions will need effective dates and termination dates. Promotions should have specific qualification thresholds (Weight, Order Qty, etc.) that can be shared with the host system. Ability to report on sales and profitability of promotions. Please add any other ideas as feedback.
Feature Description: Data manager is a master data management tool, where user can see the tables data, export them, or import new data into the tables. For SPP, only Part, Location, Demand, and SKU tables are currently available and we would like to add other important entities such as Price, Cost, Competitive Data. In addition to it, we would be enhancing it to have inline editing, bulk editing too. Benefits: Make it easier for implementation teams and customers themselves to view and import/export data in and out of the SPP tables, especially where this data drives pricing rules.
Feature Description: Expose SPM full forecast functionality to be able to predict the future volume based on the history and other input parameters and then use it for new financial calculations. Benefit: More accurate projections of sales and other forward looking pricing related metrics. This is particularly useful for specific use cases, such as new part introduction and end-of-life scenarios.
It would be beneficial to have GPA be able to classify parts using all of the segments within a segment group, rather than just by the part attributes: Type, Class, Family and Line. We could develop a configuration table that let us list the segment groups that should be applied to GPA. Then in the Group Price Analysis main page, in addition to the drop down for the four part attributes, the drop down would expand to include the segment groups. When a segment group is selected, users would expect that the parts would be grouped by segment name within the segment group.
Create a global setting that enables/disables the entire suite of Elasticity features, including hiding all references to Elasticity in the UI. Customers who aren't using Elasticity don't want to see the Elasticity tab on the Pricing Worksheet or the Max Profit Price reference points in pricing policies.
Use the price offset management not just to create/edit price records, but to apply the offset codes across the application. 1. Be able to define the offset code as policy rules and use them in pricing policy simulations, so that user do not have to define the adjustments again and again in the policy, but simple create an offset code for the same and use it in the policy. It'll help user to create multiple offset codes and use them in a single policy with a single rule, use predefined offsets, rather creating multiple policies with different assignment rule. 2. Use them in other pricing areas such as dealer location policies, promotion policies, etc. 3. Be able to link them to loc-to-loc pricing rule such that user doesn't need to define the loc-to-loc adjustments separately in the policy, but define them at the offset code level and use them directly in the policy any number of times. 4. Be able to use the future offsets defined in the price offset management and use them when doing
Functional Overview: An accelerator will be provided with the installer, that will load the sample data into the system. Application: With the sample data, users would be able to access the SPP modules, navigate through UI and run processes on the demo data, before actual data is loaded into the system for them to understand the app better. Benefits: Would help users with on-hands training. Would help users understand the funtionalities better before actually using and implementing them. Users could access SPP features which might have been unused till now.
One thing that would be incredibly useful as an enhancement would be to have photos "attached" to part numbers. Photos bring a new level of credibility to pricing, especially when comparing parts that you sell to your competitors. Often times when we find new photos online or elsewhere, we have nowhere to store it for reference later. Or if we have it stored somewhere, we do not have the time to drop everything and go gather to photos when we are looking at the pricing analysis.This would be useful in all areas of the tool when the part number (or survey part number) is displayed. I imagine the data could be stored in the part master and the survey part tables, then used throughout the tool.How it should look...I imagine it would look like many nice websites you see out there...Small thumbnail hover over it with your mouse, it would display a pop up with all available photos of the part and click on it to open a large photoMedium photo with same functionality that the small thumb
It would be beneficial to expand curve pricing functionality. It currently works by deriving margins using the price of competitive parts and the cost of associated service parts. 1. Rather than using competitive data, it should be possible to generate curves just by looking at groups of service parts. Right now, the only way to build curves from existing serivce parts is to model the service part prices and competitive part prices. This adds a lot of unnecessary data and effort. 2. Right now, Curve Pricing calculates margins using Standard Price and Standard Cost. It should be possible to select the source of the Cost and the Target Price Stream when calculating the Curve Price margins and applying these margins in policy rules. I can provide more details if this idea gains traction.
Currently in our system, users can create part lists either through import or by adding them one-by-one. However. we cannot define a criterion, say, Part Type is "Axle" and automatically create part lists out of it. So, similar to segments page, we should be able to define criteria to create part lists
Feature Description: Currently, users can perform action events such as approve/reject/upload from price actions page only. However, if user wants to work on pair-by-pair basis through pricing worksheet, these actions cannot be performed from there. So, add the ability to perform these action events from pricing worksheet only. Benefits: Improved usability and efficiency of analysts working on price action approvals.
Feature Description: Provide OOTB new standard reports and dashboards that are used by most of the customers so that they do not have to be implemented separately, but can be deployed with product installation. Benefits: Best Practices incorporated in the area of out of the box reports.
Feature Description: Price Book Management functionality only considers data of that policy that have been marked as completed. However, there are other policies too in other statuses such as Pending, On Hold, etc. So, we would need to enhance it so that all the data can be made available to the price book to do a better what-if analysis as to how much revenue/profit are still to be added and if target is met or not. In addition to this, once a price book is uploaded to the price book, it doesn’t appear in SPP till it comes back from host system as a price record. So, we need to allow users to also see the uploaded prices data so that they are aware of the state of the SKU price record once the record is uploaded. Benefits: Improve visibility and "What-if" capabilities in Price Book Management making it more applicable to customer use cases.
Feature Description: Multi-attribute group or value-based pricing right now has two separate modules where, on the basis of part attributes, a user can either apply adjustments or can apply weights to part attributes. In addition to this, the adjustments can be either applied sequentially or in independently. These restrictions limit the flexibility of the feature. We need to enhance it and combine all the features such that it is flexible enough for users to be able to use any combination they want to do value-based pricing. Benefit: Increase feature flexibility for the utilization of attributes for pricing to help increase the adoption of value based pricing.
Feature Description: Often, pricing at dealer or buyer locations is done by applying an offset at a reference location. The current pricing policy system is too complex to handle it and doesn’t allow to apply a pre-defined offset. In addition to this, the number of dealer locations could be large as compared to normal pricing locations, which could lead to a high number of SKUs into the system that will also impact the performance. To handle it, we plan to introduce dealer-location pricing module which will separately handle the dealer pricing and hence users can manage the main SKU prices and dealer prices separately. The pricing here would be simple with offset rule, threshold rule, and rounding rule. Benefit: Removes complexity for location types, such as dealers or importers, that require simplified logic vs. the full suite of rules SPP handles at pricing locations. Performance improvement.
Functional Overview: Customers would be able to associate each SKU to an Offset code, which will store different adjustments per pricing streams. Prices can be fed for only one pricing stream and then a process will calculate all other pricing stream prices for all SKUs, with respect to the reference stream. An offset code could have multiple adjustments/offsets for the same pricing stream, with different effective dates. Application: All customers using SPP could leverage this feature. Usually, customers calculate prices of one pricing stream and then apply discounts or offsets to calculate prices of other pricing streams. However, as per the current system, customers need to feed the prices for all the price stream into the system. Existing price records would be updated automatically and new price records would be created automatically for new/updated adjustment percentages. Benefits: Customization would be reduced. Prices of all the stream pri
Functional Overview:Attributes of competitors are used to calculate their tier group prices.Competitor prices can be compared with OEM part recommended prices.OEM data can be overridden, if needed, so that OEM part prices can be set according to competitors.Application:Customers who want to set attribute-based prices, as per the market.Benefits:Competitive advantage.Multiple competitors can be assigned. and customers can then set prices to be at a premium level or a more competitive level, as needed.This feature is in implementation and scheduled for SPP 11.3 release.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.