Escolar Documentos
Profissional Documentos
Cultura Documentos
Licensing Model
The following license model applies to BI360 5x and previous versions.
An organization purchases BI360 using either a SaaS or perpetual license model. In either case,
organizations may use the same set of license keys in both a development and production environment
on the condition that there is only one of each type of environment.
An organization purchases BI360 for use within that organization. In cases where an organization is
acquiring another organization, if the organization being acquired is planning on using BI360 themselves,
they must purchase their own BI360 license unless they are just planning on being users in the parent
company’s BI360 installation. In this case, the parent company needs to purchase additional user
licenses for the subsidiary.
For organizations who are changing their name, please contact Solver Support
(support@solverglobal.com) to have your license keys updated to the new organization name.
SQL Server BI360 Databases such as the BI360 Data Warehouse will run on the SQL
Server.
Web Application Server This server will run the BI360 web application.
Microservices Server The Orchestrator is used for Report & Form Rendering and Data Warehouse
services, such as the Data Integrations run on this server(s). Note: If the BI360
deployment only utilizes live ERP reporting, the Microservices server(s) are
not needed.
SQL Server
The SQL Server will contain two or more BI360 databases, depending on the software purchased. The
specs below are the minimum requirements, however it is strongly recommended to build out a SQL
server that can be expanded as BI360 use grows within the organization.
SQL Server
1-50 Concurrent Users 50+ Users
CPU1,2 • 4 Core • 8 Core
RAM • 16GB or greater • 32gb or greater
Operating • Windows Server 2012/2012R2
System1,4 • Windows Server 2016
Database • SQL Server 2012 SP1/SP2+ • SQL Server 2016
Server* • SQL Server 2014 • SQL Server 2017
Storage Based on data integrated into Warehouse and/or transactional input within Budget
model (contact Partner)
• A highly available SSD setup
• A SAN that is optimized for online transaction processing (OLTP)
throughput.
• High-performance direct-attached storage (DAS)
Disk • Non-Raid configurations are supported, but redundancy will not be available.
Configuration • See notes for recommended RAID configurations5
* all items below.
Technical Information
1. The latest updates to the Operating System and Office are required. Please note that this may
require a reboot and therefore should be done during non-business hours if the installation is
being done on the Terminal Server
2. The Reporting application will install a small repository database on a designated SQL server
that can be the same server as the ERP and/or Warehouse.
3. BI360 typically supports service packs and cumulative updates of SQL. New versions of SQL
Server are tested and confirmed by Solver development team. Please contact Solver Support
(support@solverglobal.com) should you have any questions.
4. The BI360 Suite is not supported on systems that use FIPS or ADFS.
Ram 16GB+
CPU 2 Core
.NET Framework .NET 4.6
Server IIS 7+ with ASP.NET support
1. If installing Web Budgeting, the BI360 and/or ERP database must be set to SQL Compatibility mode
2008R2+. More information can be found here.
Ram 16GB
Drive Space A minimum of 40 of GB available disk space
CPU 4 core or greater CPU
Other • Service Fabric
• NET Framework 4.5.1 or higher, full install
• Windows PowerShell 3.0
• The RemoteRegistry service should be running on all the machines
BI360 Reporting
BI360 Reporting is compatible with many ERPs. The following chart displays all the ERP versions that
BI360 Reporting is compatible with. If the ERP system implemented at your company is not shown in the
chart below, please contact a Solver sales person at sales@solveursa.com.
In addition to live reporting off the ERP database, BI360 may also be integrated to many ERP systems
and other data sources through the use of the BI360 Data Warehouse. Certain systems like Intacct have
been integrated to BI360 using the source system’s Web Services and as such, is not dependent on a
specific version of the ERP.
AX 2009 Supported
Please see the BI360 Installation Guide for additional information on installing the BI360 Portal.