See this page for information on system requirements for the Shop Floor Insight communications app.

Before you proceed with this section you need:

• To have the Shop Floor Insight app in Business Central already installed.
• A service account setup in Business Central.
  • This must have an appropriate “Function Permission” entry.
  • This should have sufficient permission sets to access Business Central web services, as well as the “SFI-Service” permission set.
• Your web service address endpoint for SOAP services for Business Central.
• If you are using Shop Floor Insight 7.10 or newer and are on Business Central 14 or newer, you do not need to update the TCM_MES_License.txt file. If you are using Shop Floor Insight 7.9 or older or are on Business Central 13 or older, you must update the TCM_MES_License.txt file.

This component is intended to be run on-premise. This component will install a windows service that will provide an HTML-based barcoding interface optimized for Shop Floor Data collection.

Start Credential Manager on the server where Shop Floor Insight will be installed.

You need to be logged in as the service account user that will be used for the Shop Floor Insight windows service itself for this step. The credential configuration steps will not work if you are not logged in as the service user.

Choose “Windows Credentials”

Add a Generic Credential, and enter the appropriate Business Central username and password that will be used by Shop Floor Insight to connect to Business Central. For “Internet or network address” type “Shop Floor Insight”

When complete it should seem similar to the below.

As an administrative user, run the “setup.exe” provided to you by Insight Works.

Click “Next”.

If desired, choose a different install location for the initial service. The wizard will default to the recommended location. Choose “Next”.

Confirm the installation by choosing “Next”.

The on-premise component may take a few minutes to install.

After the install is complete find the Shop Floor Insight in the services list, and change the account to match the same service account used while performing the Credential Management step.

Enter the credentials for the Service Account itself. For On-Premise Business Central installations this is often a user in Business Central itself when configured with “Windows” authentication. For SaaS Business Central usages, this is a different distinct account than the Business Central user. Contact your IT Administrator to determine which account should be used for the windows service.

Replace the TCM_MES_License.txt file with the license file given you by your Microsoft Partner or Insight Works representative.

If you do not have a license file you can obtain a demonstration license file by contacting your Microsoft Partner or Insight Works representative. The on-premise component will not work without an updated license file.

Search for “Shop Floor Insight Service Controller” in Windows.

When asked if the system can make changes, choose “Yes”.

The available Shop Floor Insight services will be listed. The install wizard will install one by default. It is common to have multiple services for different time zones, different companies, and different environments.

Select the service, and choose the Choose the configure service button, which appears as a document with a gear in it.

In the following Screen Configure the SOAP URI section to your business central web service configuration endpoint.

Your Business Central web service endpoint can be determined with the advice given here:

https://docs.microsoft.com/en-ca/dynamics365/business-central/across-how-publish-web-service

For SaaS installs the pattern is typically:
https://api.businesscentral.dynamics.com/version/tenant/WS/CompanyName/

For On-Premise installs of Business Central the pattern is typically.
https://yourserverhere/1234/optionalTenant/WS/CompanyName/

Where 1234 is the port, “optionalTenant” is the optional tenant, and CompanyName is the URI encoded company name.

When uncertain, navigate to ‘Web Services’ in Business Central, and identify how it’s exposed by clicking on one of the SOAP links.

The “SOAP URL” will inform you what the server soap URL is, just remember to remove any specific object endpoint.

The below steps give an overview of a typical Business Central SaaS authentication, which provides “UserName” and “Basic” security. If your Business Central is On-Premise it is more typical to use Classic with Windows Client Credentials, and instead run the service as the windows account that has Business Central access to provide a higher level of security.

These are standard Windows Communication Foundation authentication settings and may need to be altered from this quick start guide to match the existing implementation of your Business Central configuration and the security policy of your company.

Authentication mode for Business Central SaaS is usually “UserName”. For On-Premise Business Central installs this is typically “Classic”.

Choose “Always Send Credentials” for Business Central SaaS installs. This is typically un-checked for on-premise installs configured to use windows authentication.

“Client Credential” mode for Business Central SaaS is usually “Basic”. For on-premise Business Central it is typically “Windows”.

Choose the Credential Vault Target created by the previous credential manager step.

Your configuration will look similar to the below:

If your Soap URI is HTTPS, then you need to change “HTTP Security Mode” to “Transport”.

All Business Central SaaS are HTTPS.

If your endpoint is HTTP, then it should probably be “Transport Credential Only”.

These are very simplistic guidelines, which can be affected by your Business Central configuration and your local security policies. All typical Windows Communication Foundation settings are available for configuration.

Start the Service by clicking the green arrow in “Shop Floor Insight Service Controller”

Alternatively, just start Shop Floor Insight from the services window itself.

If your Shop Floor Insight windows service started successfully, then you can move to the next step of testing it by printing barcodes and scanning them into the interface.