Industry 4.0 - An Introduction

This post is meant to give you an introduction to Industry 4.0. This is a topic that generates many questions and opinions and the purpose of this post is to give a brief overview with future posts going a little more in depth.

What is it?

Industry 4.0, you’ve heard of it, but what does it really entail and what will it do for your organization? That’s not an easy question to answer because it can and likely does mean something very different for each and every organization.

Industry 4.0, or Industrie 4.0 as it’s also known, was originally defined as the computerization of manufacturing. The term derives from the fourth industrial revolution. Its goal is to leverage computing and information technology in manufacturing environments -- increasing productivity, flexibility, and quality, all while decreasing costs. It accomplishes this by defining four key concepts to help guide manufactures and stakeholders in their Industry 4.0 implementations.

What is it not?

It’s not a set standard. While we are used to industry standards like ISA 88 and ISA 95 guiding the implementation of control systems and technology in manufacturing organizations, Industry 4.0 is not a standard. It encompasses principles for driving your organization forward.

The advantage comes with the flexibility to implement in the most appropriate way for your organization. Industry 4.0 implementations are not one size fits all. The benefit of this is that it allows you to choose a scope that’s appropriate for your organization.

Who is it for?

Manufacturing organizations with a strategic look forward for progressing both their Greenfield and Brownfield operations.

The Four Principles

These principles are in place to guide your strategic directions and implementations. The principles will mean something different for every organization.

  1. Interoperability - Communications between people, machines, devices, and sensors allowing unencumbered flow of information.
  2. Information Transparency - Embedding data collection and aggregation systems from low level sensors all the way up and through advanced Manufacturing Execution Systems (MES) and Enterprise Resource Planning (ERP) systems. This allows for the culmination of limitless data collection and advanced record keeping.
  3. Technical Assistance - Provides services, support, and aid to people. This increases the tools available to all manufacturing stakeholders.
  4. Decentralized decisions - Automating decisions and reducing human interaction as much as practically possible.

What concepts and technologies can Industry 4.0 include?

  • Internet of Things (IoT) and Industrial Internet of Things (IIoT)
  • Operational Technology (OT) and Information Technology (IT) convergence
  • Smart Manufacturing
  • Digitalization and Digitization
  • Cloud Computing
  • Machine Learning (ML) and Artificial Intelligence (AI)
  • Digital Twin
  • Supervisory Control and Data Acquisition (SCADA), Manufacturing Execution Systems (MES), and Enterprise Resource Planning (ERP) systems

Wow, that’s a mouthful, and not even an exhaustive list. What’s important to keep in mind is the four principles and to adopt the technologies and concepts above. This will allow your organization to achieve your goals.

What's next?

This post was meant to give you an introduction to Industry 4.0. Future posts will include various topics like example applications, benefits, and implementation strategies. Let me know if you'd like to see anything specific!

SQL Server 2016 Upgrade Hung at sqlrsconfigaction_upgrade_configrc_cpu64

When performing an upgrade of Microsoft SQL Server 2014 to SQL Server 2016 the install/upgrade seemed to hang at the very end.

The following status was displayed:
sqlrsconfigaction_upgrade_configrc_cpu64

I found that the only SQL Server service still running was:
SQL Full-text Filter Daemon Launcher

Manually stopping this service allowed the upgrade/installation to continue and complete successfully!

Installing FactoryTalk Historian SE (Site Edition) 4.01 on Windows Server 2012 R2

The following procedure outlines the process of setting up and configuring Rockwell FactoryTalk Historian SE on Windows Server 2012 R2.

  1. Install the FactoryTalk Services Platform. If you need assistance, follow the link Installing Rockwell FactoryTalk Services Platform (FTSP).
  2. Launch Setup.exe from the install directory
  3. Select Install FactoryTalk Historian Site Edition
    Install FactoryTalk Historian Site Edition
  4. Select Install FactoryTalk Historian Site Edition
    Install FactoryTalk Historian Site Edition
  5. Select Install FactoryTalk Historian Asset Framework
  6. Select Install Microsoft SQL Server 2012 Express
  7. Select New SQL Server stand-alone installation or add features to an existing installation
  8. Select the first radio button, Perform a new installation of SQL Server 2012 and then Select Next
  9. Read the End User License Agreement, if you accept it Select Next
  10. Select all three check boxes and Select Next
  11. Select Next
  12. Select Startup Type to Automatic for both services and Select Next
  13. Select Next
  14. Select Next
  15. Select Close
  16. Close the SQL Server Setup window
  17. Select FactoryTalk Historian AF Server
  18. Select Next
  19. If you accept the license agreement Select Next
  20. Select Next
  21. Select Next
  22. Select AF Application Service and AF SQL Database and Select Next
  23. Select Install
  24. Select Finish
  25. Select Back
  26. Select Install FactoryTalk Historian Site Edition
  27. Select Next
  28. Select Next
  29. Enter User Name, Organziation, Serial Number, and Select Next
  30. Select Next
  31. Select Next
  32. Select Install
  33. You may be warned that the server will need to be restarted after installation, if this is acceptable Select Yes
  34. Wait for the install to complete
  35. Select OK to stay in the existing FactoryTalk Directory
  36. Select Finish
  37. You may be prompted to restart the server, if this is acceptable Select Yes

Installing Rockwell FactoryTalk Services Platform (FTSP)

The following procedure outlines how to install the Rockwell FactoryTalk Services Platform on Windows Server 2012 R2.

  1. Ensure you have the .Net Framework installed. If not, you may receive the following error:
    Microsoft .NET Framework 3.5 SP1 is not installed.
    To install the Microsoft .NET Framework 3.5 SP1, open an elevated Powershell prompt and enter the following command:
    PS C:\Windows\System32> Install-WindowsFeature -Name Net-Framework-Core -IncludeAllSubFeature

  2. Install FactoryTalk Services Platform

  3. Launch the installer and select Install FactoryTalk Historian Site Edition

  4. Select Install FactoryTalk Historian Site Edition

  5. Select Install FactoryTalk Services

  6. Select Install FactoryTalk Services

  7. Select Next

  8. Select Next

  9. Read the Software License Agrement, if you agree to it, Select Accept all

  10. Select Install

  11. Select Finish

  12. Select Yes to reboot server

HP HPDM Master Repository Controller Configuration

When configuring a Repository with HP Device Manager you may receive either of the following messages:

Remote access is not configured with the same folder path as the Master Repository Controller on repository Master Repository with protocol FTP.

Remote access is not configured with the same folder path as the Master Repository Controller on repository Master Repository with protocol Shared Folder.

Remote access is not configured with the same folder path as the Master Repository Controller on repository Master Repository with protocol FTP.  Remote access is not configured with the same folder path as the Master Repository Controller on repository Master Repository with protocol Shared Folder.

This is caused by using a directory that is different from the default. The default directory is: C:\Inetpub\Ftproot\HPDM.

To change the default directory, modify the the following configuration file: C:\Program Files (x86)\HP\HP Device Manager\MasterRepositoryController\Controller.conf. Change the ReposPath variable to the path you'll be using for your repository. After making this change, you'll need to reboot server or VM running HPDM.

After the restart completes, the repository can successfully be tested.
HPDM_Test_Repository_Result