What's New with FICO Decision Modeler 2.1

Blog Post created by Makenna.Brei Advocate on Jun 20, 2017

What's new with FICO Decision Modeler 2.1

  • Generic scorecards and decision tables: Customers can now use decision tables and scorecards in Decision Modeler without the need to create templates. Business users no longer require any assistance from technical users, putting the power into the business user's hands and allowing for greater control, increased productivity and efficiency.
  • Analytic Integration:  Business users can now inject prescriptive analytics into decision processes by importing either PMML (Predictive Model Markup Language) for scorecards or FSML (FICO Strategy Markup Language) for decision trees. Once the prescriptive models are imported, they can be viewed and edited by business users and then executed to be part of the decision service. Business users can also easily map the variables used in the prescriptive models to their operational data structure.
  • Scorecard Enhancements:  Scorecard has been redesigned to have an automatic bin creation which will detect gaps in overlaps. This feature is essentially a way to check scorecard integrity.
  • SOAP/RESTful Deployment:  Decision Modeler now allows for multiple ways to support decision logic including SOAP, RESTful and Batch. This allows customers to have more options to choose their desired deployment method for different applications.
  • Java BOM Management: Java BOM (Business Object Model) Management enables business and technical users alike to quickly upload and refresh their operational data structure, reducing their dependency on IT. This will result in improved processes and increased speed in the ability to update and refresh data definitions and provide custom data providers with their decision logic.
  • Decision Testing: Users can conduct decision testing and validation at the same time, as well as upload validation data. If a user uploads their validation data and runs the test, the test will be validated and can easily inform the user if the test cases have passed or failed, ensuring the quality of the decision.
  • Reason Code Editor: In addition to returning a score, you can configure a scorecard to return a reason code for each bin that is fired. Reason codes provide users with reasons as to why a particular score was assigned during evaluation.