DOCUMENT PURPOSE The purpose of this guidance document is to help licensees understand the IMan software license fee structure (License Fee Guide). The License Fee Guide is a guide only and does not form part of the End User License Agreement (EULA). Please refer to the EULA for all terms and conditions, including fees which will depend on your particular software configuration.
DETERMINING LICENSING FEES To determine the correct licence fee there needs to be some knowledge of the software integration requirements. IMan software is a backend system and therefore does not have a simple licensing fee metric such as user count. In calculating the licensing fee the key considerations are the number of integrations (or data-flows) and the connectors required to support the integration.
A Single Integration A single integration is data/work-flow where there is a start point and one or more endpoints.
Base/Core Product The base product contains all functionality for designing & scheduling integrations. It includes all the core data transformation functions and the support to extract and write to the following data formats: CSV/Text; OleDB/ODBC; Xml & Excel.
Licensing Consideration Every instance must have a Base IMan product.
Connectors Connectors provide the native connectivity to integrate with an application such as Sage300 ERP, Sage200, SageCRM, Magento, Amazon, etc via its API.
Licensing Consideration Every IMan instance can have 0 or more connectors.
Using the Realisable Software License Fee List After determining your required IMan software configuration, refer to the Realisable Software License Fee List. Starting with the cost of the core product, then add the cost of any required connectors.
Software Assurance Software assurance is 25% of total purchase price. Software assurance is mandatory the first year, and is due each year from the date of purchase.
Realisable License Fee Guide
Page 2 of 7
Realisable Software
Lapsed Software Assurance ·
IMan licenses are perpetual and IMan will continue to function.
·
Customers not renewing software assurance will not be entitled to upgrades, or bug/hotfixes.
·
Customer’s where IMan software assurance has lapsed will need to pay:
o
Software assurance from the point of lapse to the current day.
o
The full year’s software assurance.
o
A 25% surcharge.
Realisable License Fee Guide
Page 3 of 7
Realisable Software
LICENSING EXAMPLES The following screens are taken from the IMan designer to illustrate the key concepts described above. Figure 1 – A single integration with a single connector.
Figure 2 – An extension of single integration with single connector, where a CSV file is created following the connector.
Figure 3 – A single data source can import data into multiple parts within a company or into multiple companies. In the below example the upper connector first creates or updates a customer, and the second bottom connector creates a sales order.
Realisable License Fee Guide
Page 4 of 7
Realisable Software
IMAN LICENSE RESTRICTIONS The following table describes the restrictions on each version of IMan software. Feature
Unlimited
3 Integration
2 Integration
1 Integration
Number of Integrations
Unlimited
3
2
1
Connectors per Integration
Unlimited
4
4
2
Number of Start Points Per Integration
Unlimited
1
1
1
Integration Count The primary license restriction is based around the number of integrations allowed on a single installation of IMan software.
Licensing Consideration When deriving the IMan price the ‘integration count’ of the base/core product and any connectors cannot be mixed. E.g. An unlimited base product must use unlimited connectors; conversely a 1-Integration connector cannot use an unlimited base product. Remember to work ‘column wise’ when using the Realisable pricelist.
Pricing Rationale The primary reason for licensing IMan software by integration count is to reduce the cost of IMan for customers with lighter integration requirements; the more complex the requirement, the higher the cost.
Example The screenshot below shows two integrations. Additional integrations cannot be added unless the license is upgraded or an integration deleted.
Realisable License Fee Guide
Page 5 of 7
Realisable Software
Maximum Connectors per Integration The 1, 2 & 3 integration licenses place a limitation on the maximum number of connectors per any single integration, where the 1-Integration license permits a maximum of two connectors and the 2- & 3- integration license permit a maximum of four.
Licensing Consideration If five or more connectors are required in any single integration an unlimited license is required.
Example The screenshot below illustrates a job with seven connectors.
Realisable License Fee Guide
Page 6 of 7
Realisable Software
Number of Start Points per Integration Only the Unlimited license permits any single integration to have more than one start point.
Example The example below shows a single job with seven start points.
