Create and configure a service

Steps to create and configure a service

To create and configure a service in the Dynamo Marketplace, you must complete a series of operational configuration steps.

The overall workflow includes:

1. creating a new service based on a Service Class;
2. configuring service information;
3. associating Service Centers and Data Centers;
4. configuring service attributes and parameters;
5. configuring service variants, pricing, and terms;
6. publishing the service in the Marketplace.

This guide describes the operational workflow for creating and configuring a service. To create or modify the technical model from which the service is derived, refer to the guide Create a Service class.

Create a new service

After creating or selecting a Service class, you can create the service that will represent the offering published in the Dynamo Marketplace.

To create a new service:

• Sign in to the Provider dashboard;
• From the side navigation menu, select Service management > All my services;
• Select Create service in the upper-right corner;
• In the Select a service class window, configure:
  • Service category – select the service category;
  • Sub category – select the service subcategory;
  • Service class – select the Service class to use as the technical model for the service.
• Select Confirm;
• The new service configuration page opens.

The new service inherits the attributes, configurations, and operational settings defined in the selected Service class and represents the service offering that can be published in the Marketplace.

A service can include multiple variants. Each variant represents a specific combination of price-relevant attribute values defined by the Service class.

Configure service information

After the service is created, the configuration page opens.

In the GENERAL section, configure the information used to present the service in the Storefront:

• Service name – the commercial name of the service displayed to Buyers;
• Description – a brief service description;
• Image – an image or logo associated with the service;
• Terms and conditions – a document or content containing the service terms and conditions;
• Service Description (HTML) – optional HTML content displayed on the service details page;
• Base URL – specifies the base path used to resolve relative paths contained in the Service Description (HTML). This allows existing HTML content, for example content reused from a website or one of its sections, to be used without replacing its relative paths.

The information configured in this section is common to all variants of the service.

In the ORGANIZE SERVICE section, verify the service classification and availability information:

• service category;
• service subcategory;
• associated Service class;
• Service Centers and Data Centers where the service is available.

Service Centers and Data Centers must already be configured before completing service creation.

Configure service attributes and parameters

The attributes defined in the Service class are used during service configuration and may be displayed to the Buyer during the ordering process.

Price-relevant technical attributes define the service variants and their pricing. Service-specific technical attributes do not affect the service price and are used to provide information required for provisioning.

A fixed value set by the Provider is displayed to the Buyer but cannot be changed and is passed in the provisioning request. If multiple values are available, the Buyer can select the required value during service configuration.

Depending on the selected Service class, the configuration page may require:

• service technical attributes;
• parameters related to configuration or provisioning;
• information required from the Buyer during the ordering process;
• service access, configuration, or delivery information;
• compliance or data processing information.

In the GDPR Disclosures section, configure the information related to personal data:

• Request type, Access type, and Format type – define how the Buyer can request and access the data collected by the service after purchase and during its use. Based on the selected values, in particular the Request type, provide the requested contact or access information, such as an email address, physical address, or API endpoint. This information is displayed to the Buyer on the service catalog page;
• Includes PII – indicates whether personal data is required to purchase the service. Select Yes if the purchase requires personal data; otherwise, select No.

If certificates or related documents are associated with the service, configure them so that they are available to the Buyer from the service details page in the Storefront.

Complete all required fields and verify that the entered values are consistent with the service you intend to publish.

Configure service pricing and terms

In the PRICING section, configure the commercial model for the service.

Depending on the selected model, you can configure:

• Price plan, such as Pay-Per-Use, Upfront, One-off, or Subscription;
• the currency used for charges;
• any service activation fee;
• initial, recurring, or usage-based charges;
• payment or billing frequency;
• service duration;
• renewal settings;
• Grace period – defines the tolerance period after the service expiration date, when applicable;
• Remedy period – defines the period allowed to remedy a failed payment before the service is deleted. It applies to recurring payments, such as subsequent payments for a Subscription, and to Pay-Per-Use services where charges are applied after usage.

The Price plan defines the common pricing terms of the service, such as duration and renewal settings. Prices are defined for each variant based on its specific combination of price-relevant attribute values.

For each variant, select the combination of price-relevant attribute values and configure the corresponding price.

You can configure only the combinations of attribute values that you want to make available as service variants.

Each combination of price-relevant attribute values uniquely identifies a variant. If the same combination already exists, the existing variant is updated rather than creating a new one.

Changing only variant prices does not create a new service version. Price changes are recorded in the service History. For services with a fixed term, a price change does not affect the current service period; the new price applies to new purchases and subsequent renewals.

Changes to the service configuration may create a new service version. The new version applies to new purchases, while existing provisioned services remain associated with the version under which they were purchased.

The service History allows you to review changes between published versions. It is available for consultation only and cannot be used to restore a previous version.

Publish the service

• Review all information configured for the service;
• Verify commercial information, Data Centers, attributes, and pricing;
• Select the available save or publish button on the page;
• Confirm service publication.

After publication, the service is available in the Provider dashboard.

Publishing the service does not make it immediately visible in the Buyer Storefront. The service becomes visible after Dynamo adds it to the catalog.