ERP Cost of Ownership Model

Infor SyteLine pricing and 5-year cost of ownership model

Infor does not publish SyteLine (CloudSuite Industrial) prices, so this model takes the numbers from your own order form or renewal quote. Enter users by license type, your multi-tenant subscription or on-premises perpetual license and maintenance, SQL Server and hosting, and an implementation scope built from SyteLine functional areas, sites, integrations and data migration objects. It returns a year-by-year table, an on-prem versus cloud comparison and the lines that drive the total.

Free. Runs in your browser. No login needed to use or export; save to your account if you want it back later.

Infor multi-tenant cloudOn-premises, perpetual license(verify with vendor)Private cloud or hosted single-tenant(verify with vendor)

Users by type

How many people and connections you license, by the user types that matter in Infor SyteLine.

People who work in SyteLine forms all day (Full Client session type, Windows or web client).

Web client in FormOnly mode, mobile logins and forms shown through Microsoft Office integration (Web Form Only session type).

Programmatic access to IDOs: REST web services, portals and the Microsoft add-in (IDO and IDO Custom User session types).

Starting counts are a sample company size so the effort model shows hours straight away. Replace them with yours.

5-year total cost

Implementation
1,820 h
Per user per year
$0

No amounts entered yet

The effort model already shows 1,820 hours. Add a quote in step 2, a blended rate in step 4 or staff cost in step 5 and the totals fill in as you type.

Vendor SaaS: year by year

All amounts in USD. Implementation and contingency are placed in year 1.

CategoryYear 1Year 2Year 3Year 4Year 55-year
License or subscription-----$0
Vendor maintenance-----$0
Infrastructure and hosting-----$0
Database-----$0
Implementation-----$0
Internal staff-----$0
Support (AMS)-----$0
Total$0$0$0$0$0$0
Cumulative$0$0$0$0$0

Cost drivers

Share of the vendor saas 5-year total.

Drivers appear once amounts are entered.

What to check in a Infor SyteLine quote

  • Concurrent versus named: concurrent tokens cover more people per token, so the count you license is peak logins per site and module, not head count. Measure peak logins before you negotiate.
  • Every module a form belongs to consumes a token, so a user who opens forms from several modules needs a token in each. Check Modules for Form before assuming a light user only needs one module.
  • Integrations: REST calls without the IDO Custom User header run as standard IDO sessions. Using the header lets parallel calls for one user share a token, which can change how many API sessions you need.
  • Multi-site: on-premises multi-site uses _MS license modules; the multi-tenant cloud does not need them.
  • Optional modules (Service, QCS, industry packs, Factory Track, APS) are usually separate lines. Price each one you scope.
  • Customizations: ask your partner how each existing on-premises customization will be delivered in the multi-tenant cloud, and price any rework as customization hours in this model.

Sensitivity

Move a driver and every number above updates. 100% is what you entered.

100%
100%
100%
100%

Effect of +/- 20% on the 5-year total

Enter amounts to see which driver moves the total most.

Infor SyteLine licensing explained

In words, from vendor documentation. Follow the source links before you rely on a point in a negotiation.

License modules and tokens

SyteLine licenses are sold as license modules. Each module carries a number of tokens, and a user consumes a token of every module that the form or IDO they open belongs to. The Modules for Form form shows which module a form belongs to.

Source
Named user licensing

A named license links one user login to one license through the User Modules form. The token is consumed when the user is assigned to the module and returns to the pool when the assignment is removed. With multiple sites per database, a named user can log in once per shared site.

Source
Concurrent login licensing

Users are assigned to modules, but the check happens at login: when the number of users logged in to a site with a module equals the module limit, the next login is refused. You can assign more users than tokens; tokens are released at logoff.

Source
Session types

Each module is tied to a session type: Full Client, Web Form Only, IDO or IDO Custom User. A named user can be logged in several times with different session types and only consumes the modules for each type. IDO Custom User applies to REST calls that send the X-infor-MongooseSessionType: CustomUser header, which lets parallel calls for one user share a token. $service sessions (for example TaskMan) consume no tokens.

Source
Multi-tenant cloud: usage tracking

In the multi-tenant cloud, licensing is handled by Infor's Cloud Enablement Team and uses a usage-tracking model: SyteLine does not block access by license count, and Infor can run snapshot audits of which forms and IDOs are used and whether concurrent users exceed the licensed count. Restrict access to unlicensed modules with roles. The multi-site (_MS) license modules are not needed in the cloud.

Source
Free, optional. Reopen it on any device.
Download the model:

Using this for a budget, a renewal or a cloud decision? An engineer can check the license metric, user mix and effort assumptions against how you run Infor SyteLine.

How to use the Infor SyteLine cost model

  1. 1

    Count users by license type

    Split users into full users, light or mobile users and integration sessions. If you are on-premises, check the License Management form for how many tokens each module has today.

  2. 2

    Enter the quotes you have

    Type the subscription per user per month for the multi-tenant cloud, and the perpetual license and annual maintenance percent if you are pricing or keeping on-premises. Leave a deployment empty if you have no quote for it.

  3. 3

    Add infrastructure for self-managed options

    For on-premises or private cloud, enter servers, Microsoft SQL Server licensing, hosting and backup costs from your own invoices or provider quotes.

  4. 4

    Scope the implementation

    Pick the SyteLine areas in scope and set sites, integrations, customizations and data migration objects. Adjust the hours per unit and the blended rate to match your partner's estimate.

  5. 5

    Read the drivers and test the range

    Use the sensitivity sliders to see how much the 5-year total moves with license, effort and rate, then export the model or save it to your account.

Infor SyteLine pricing and licensing questions

How much does Infor SyteLine cost?

Infor does not publish SyteLine list prices. The price depends on license type (named or concurrent), the license modules you buy, user counts, deployment (multi-tenant cloud subscription or on-premises perpetual license plus maintenance) and your negotiation. This model does not guess a price: enter the figures from your quote and it builds the 5-year total around them.

What types of SyteLine licenses are there?

SyteLine documentation describes two licensing methods, named user and concurrent login, applied per license module. Modules are also tied to session types: Full Client, Web Form Only, IDO and IDO Custom User. A named user can log in several times with different session types and only consumes the modules for each type.

What is the difference between named and concurrent SyteLine users?

A named license is consumed as soon as a user is assigned to a module on the User Modules form. A concurrent license is checked at login: if the number of users logged in to a site with that module has reached the limit, the next login is refused, and the token is released at logoff. You can assign more users than you have concurrent tokens.

How is SyteLine licensing enforced in the multi-tenant cloud?

In the multi-tenant cloud, Infor uses a usage-tracking model. SyteLine does not block access by license count; access is controlled by roles and permissions, and Infor can run snapshot audits to check that the forms and IDOs used belong to purchased modules and that concurrent users stay within the licensed count.

Do integrations and REST API calls consume SyteLine licenses?

Programmatic access uses the IDO session type, so it consumes IDO-type license modules. REST calls that send the header X-infor-MongooseSessionType: CustomUser use the IDO Custom User session type, which lets several simultaneous calls for one user share a token. Framework utilities such as TaskMan run as $service sessions and consume no tokens.

What is included in SyteLine total cost of ownership beyond licenses?

Implementation (configuration, data migration, integrations, testing, training, project management), infrastructure and SQL Server licensing for self-managed installs, internal staff time for administration and support, outside application support (AMS), and upgrades. Implementation and internal staff can be larger than the license line, which is why the model shows each separately.

Is SyteLine still available on-premises?

Infor still publishes on-premises installation and administration guides for current SyteLine releases, but its product page presents the multi-tenant cloud on AWS as the offering and on-premises as the setup customers migrate from. Ask Infor directly whether new on-premises licenses are available for your situation; existing on-premises customers continue on maintenance.

How accurate is this model?

The arithmetic is exact for the numbers you enter. The default effort hours are planning assumptions, not benchmarks, so replace them with your partner's estimate when you have one. Ask an engineer to review the result if you are using it for a budget or a cloud versus on-premises decision.

Sources

Netray is an independent ERP consultancy. Product and licensing names belong to their owners; confirm terms against your own contract.