For Customers, it is mandatory to support the companies corporate language so users can chat with Marvin easily and based on daily business behavior.

Business Requirements:

• Marvin currently supports English and German by default

• Standard available languages of ESM should be supported

  • French

  • Italian

  • Spanish

  • -- not that urgent --

    • Polish

    • Dutch

    • Portuguese

All data providers used with SAM support Workers
(instead of deprecated Data Gateway).

Requirement:

Information about compliance in data warehouse - which is used for management reporting - must be updated in a consistent way. This means, the system is not updating the warehouse while background processing is active and numbers in the system are intermediate. Users should not be blocked from running actions (very much) by asynchronous processing.

Acceptance:

1. Warehouse is NOT updated if background processing is running

2. Background processing is NOT executing while warehouse is updated

Implementation:

Engine for data warehouse update is checking if there is background processing. If yes, it waits for x minutes (configured in engine; default: 119 minutes) before quitting. The default schedule of this engine will be set to daily.

Description:

Background processing sets license requirements into status 'invalid' if count expression returns an invalid status.

With this capability, license models may check scenarios that are not supported for licensing by licensing terms and react accordingly. Users must then either change the license model or the scenario.

Example: Licensing "SQL Server Standard" in an OSE that uses more than 20 hardware threads.

Acceptance:

1. License requirement is in status "invalid" if quantity of license requirement is less than zero (< 0)

Description:

When the user selects a software product opening the preview, he wants to have the option so see the status of compliance for the selected software product only, or for all software products that are included in reporting and share same publisher/product name.

The system remembers the user's preference and make last choice default for next occurrence of the use case.

Implementation proposal:

Acceptance:

1. Option is visible in preview of software product

2. System remembers last choice of user (even from previous session)

3. If option is enabled or disabled, chart updates showing the corresponding numbers

The customer is able to enable and configure the connection to the MAtrix42 infrastructure by entering security credentials (most likely a connection string) into the FireScope tenant. The result would be an SDDM UI!

TODO:

• Consider if multiple Matrix42 systems needs to be addressable

Description:

LIS Online Update is using new web-server

• Previous URI: https://support.update4u.de/LIS/LISUpdateService.svc

• New URI: https://lis.matrix42.com/LIS/LISUpdateService.svc

Also changing URL for License Library!

Acceptance:

1. LIS Update is using new webserver

2. LIS Library access is using new webserver

API extension to create tickets like it is currently in place for incidents (create.incident).

Minimum requirements need to be covered:

• User

• Subject

• Description

• Category (optional if not provided Ticket Default)

• Impact (optional if not provided Category default)

• Urgency (optional if not provided Category default)

• Role (optional if not provided Ticket Default)

• SLA (optional if not provided Ticket Default)

• Entry By (optional)

• Reported Asset (optional)

• Reported Service (optional)

• Classification (optional, if not provided -> Ticket)

Ideally, the extension is marked public.

Acceptance criteria

• API extension available and documented

• Tickets with direct classification to 'Incident' or 'Service Request' can be created

• If attribute values are not provided defaults will be used

• Extension supports

  • User

  • Subject

  • Description

  • Category (optional if not provided Ticket Default)

  • Impact (optional if not provided Category default)

  • Urgency (optional if not provided Category default)

  • Role (optional if not provided Ticket Default)

  • SLA (optional if not provided Ticket Default)

  • Entry By (optional)

  • Reported Asset (optional)

  • Reported Service (optional)

  • Classification (optional, if not provided -> Ticket)

A more intuitive dependency map is available for both assets and services and is based on the KeyLines map plugin.

Matrix42 ESM is able to consume ServiceBus events using the ServiceBus adapter (Nuget). Assets and Services will be created/updated based on ServiceBus messages.

Acceptance criteria

• Assets are created using the ServiceBus

• Assets are updated using the ServiceBus

• Services are created using the ServiceBus

• Services are updated using the ServiceBus

• Ticket (classified as Incident) is created using the ServiceBus

• Ticket (classified as Incident) is updated using the ServiceBus

• Dependencies are created using the ServiceBus

• Dependencies are updated using the ServiceBus

Mock-up

Doesn't apply

License entitlement (reconciliation between purchased licenses and license requirements) is performed significantly faster so that larger environments have their compliance status updated much faster.

SAM engines support new platform capability, to run engines in a serialized way, so that customers are able to improve execution of their overnight processing in a secure and efficient way.

Following SAM engines support serialized execution:

1. Empirum Connector

2. License Manager - Overnight processing

3. License Manager Recalculate Statistics

4. Business Intelligence Manager

5. License Manager Remote Usage Data Processing

6. Asset Manager - Overnight processing

7. Contract Manager - Overnight processing

The currently used design on ACS is no longer up to date.
Due to some design errors serious errors in the application can occur. In addition, it shows significant shortcomings in terms of performance and how intuitive and responsive the application is.
For these reasons a new, more modern design system must be developed.

Acceptance criteria

• A modern design is developed

• The design must be long-lasting and based on a framework

• In place functionality needs to stay functional

Mock-up

does not apply

Pre-calculated values used by Microsoft server license models are calculated based on existing license requirements and not on installations. This enables scenarios to calculate license requirements for virtualized servers from requirements rules or even with manually created license requirements.

Installation of older Extension versions will be enabled to allow following a release plan with unstable and stable releases at the same time.