Frequently Asked Questions

The below represent the most common questions we hear about enCorps. If you have additional questions, please contact us.

We chose the word "issue" because it is less awkward than "logical unit of work" or "instance of something that needs to get done". enCorps certainly can be used for what would be considered traditional issue management - on steroids.

In enCorps, issues really serve as a collection point for all of the communications, documents, and other information surrounding something that needs to get done.

Regardless of what it is, the work that we do follows similar patterns and we deal with it in similar ways. We send emails, exchange documents, and spend time collaborating and creating.

In enCorps issues are configurable to represent any kind of work and to follow any kind of process. Whether you are dealing with a work order from a customer, a change request, or a risk that needs to be managed, each of these can be represented in enCorps.

What an issue means to you in the context of your own organization and processes is limited only by your imagination.

enCorps is hosted in our state-of-the-art hosting facility in Denver, CO. Our hosting partner consistently receives awards and recently won the contract for business continuity for the State of Colorado.

Our hosting partner provides highly scalable network connections across three national networks, is present on two power grids and guarantees 100% always on power and network connectivity.

We selected them because they are the best.

Yes. But not enCorps. To find out why, please see enCorps Performance.

Every enCorps instance is provisioned with its own database so your data is isolated from all other enCorps customers.

Customers own all of the user-entered/uploaded data that exists in their database. As part of our standard service level agreement, ServiceLogix will provide an extract with a data dictionary of all data to any customer for a nominal fee that covers our expenses.

As a standard, we perform a cold backup once per day during our nightly maintenance window and follow industry best practices for off-site storage and security.

For additional charges, we can offer other options such as hot backups multiple times per day all the way up to full database replication to a remote site - which can provide last-transaction recovery.

Network Security - Each of our servers resides on a private network and can only be accessed (physically and over the network) by authorized ServiceLogix personnel. Our entire hosting infrastructure resides behind a firewall and we implement industry best practice security procedures.

Physical Security - Our data center requires multi-factor authentication - including photo identification to gain physical access to the hosting facility - and maintains 24/7 video surveillance. This means that only authorized ServiceLogix personnel can gain physical access to the hosting facility and our servers.

Application Security - Our standard authentication is via email address and password. Passwords are encrypted on the server ensuring that nobody but a user can see a password in clear text. New one-time use passwords generated via password recovery can only be sent to the subscribed email address.

Additional measures - ServiceLogix offers additional measures of security including dedicated server, point-to-point VPN with private subnets, digital ID and multi-factor authentication.

With over four years of continuous operation, we have incurred less than two hours unscheduled server downtime and zero network downtime.

Our hosting partner is connected to three national fiber networks and gaurantees 100% network and power availability. This means that it is extremely unlikely that enCorps will become unavailable because of network connectivity issues (on our end - we cannot gaurantee your own or your downstream provider's connectivity).

Though we have an excellent track record, not all possible failures can be anticipated. If you require near 100% availability, we can offer options that include data replication and failover to a remote site.