Supply Chain Framework 1.7.0

Feature Updates

The main feature released in 1.7.0 is the scenario analysis module (SAM). This module provide a consistant way for developers to implement scenario analysis using a set of SDKs, which allows developers to focus on their use case specific logic rather than the infrastructure required at runtime. SAM provides a mechanism to package use case specific artifacts into a template, which can then be tested, and exported from one SCO environment and imported into to another. SAM can be used for issue analysis, or simply just to check out different scenarios in supply chain.

This release provide the following capabilities related to scenario analysis:

• SDK/APIs for a developer to build a SAM template for a business use case.

• A set of APIs to import/export templates from one SCO instance to another.

• A set of APIs to run a scenario analysis, and interact with the SCO regarding the run status, and analysis output.

• Infrastructure and runtime support for running scenario analysis, including system and use case logging, snapshot cleanup, and so on.

• Update to issue analysis APIs, to integrate SAM into issue analysis, resolutions, and related call actions.

API Changes

This release provides the following new APIs for scenario analysis:

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/templates. This API supports the CRUD operations on SAM templates.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/transformations and HTTPS://{SERVER}/api/{$namespace}/scsam/v1/transformationrules. This API supports CRUD operations on the transformation component of a template. Transformation and related rules defines the change of state for a given scenario. Each trasnformation can have several transformation rules.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/validations and HTTPS://{SERVER}/api/{$namespace}/scsam/v1/validationrules. This API supports CRUD operations on the validation component of a template component. Validation and related rules defines the business logic to verify if an option for a given scenario is valid or not. Each validation can have more than one transformation rule.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/impacts and HTTPS://{SERVER}/api/{$namespace}/scsam/v1/impactrules. This API supports CRUD operations on the impact component of a template. Impact and related rules defines the business logic to calculate the business impact (such as time, cost, and so on) for a given scenario.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/scenarioanalysis. This API can be used to run a scenario analysis using a SAM template, or to retrieve the status/information about scenario analysis runs.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/scenarioanalysistrace. This API is used to retrieve the execution trace of a scenario analysis run.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/resolvescenarioanalysis. This API is used to resolve a scenario analysis by performing a set of call actions associated with a given scenario. This is typically used in case of issue resolution.

• HTTPS://{SERVER}/api/{$namespace}/scsam/v1/import and HTTPS://{SERVER}/api/{$namespace}/scsam/v1/export. These are APIs to import and export SAM templates with all template components.

This release also updates the following existing API:

HTTPS://{SERVER}/api/{namespace}/scbi/v1/runissueanalysis. This API is updated to support using SAM as part of the issue analysis logic. The change is backward compatible, i.e. analysis existing API implementation using the old way (not using SAM) will continue to work in this release without any changes to the original implementation.

See Introduction to the Scenario Analysis API.

Security Role Updates

A new supply chain role is introduced in this release: DevOps. Users with this role can manage SAM templates in the SCO instance, such as import or export.

Other roles are changed as follows:

• The role Developer now has the privilege to create SAM templates and to run SAM analyses.

• The roles Data Architect, Data Analyst, and Business Users now have the privileges needed to read SAM templates, and run SAM analyses.

See Supply Chain Security Roles.

Data Model Updates

There is no change in the canonical supply chain data model in this release. New internal data objects were added for SAM, and internal tables were updated with new attributes related to SAM.