Search This Blog

Showing posts with label optimization. Show all posts
Showing posts with label optimization. Show all posts

Friday, January 30, 2015

Analytics for Manufacturing - MTConnect Insights.

Have been looking around for analytics applied to manufacturing processes. View to how to optimize business value of the manufacturing process (aka ROI, efficiency, etc.). [And optimization can be about consumables, parts, energy - usually uptime and reliability are key concerns.]
Found an approach with the following components:
Protocol or language: MTConnect. Wrote about MTConnect before.
Tools: Systems Insights VIMANA and their partners like Autodesk and Yamazaki Mazak.
Then apply model based analytics ala Analytika.

Sunday, November 30, 2014

MassTLC IoT at PTC - Smart Connected Products Transforming Competition - HBR.

IoT has had much discussion lately. Went to a great MassTLC sponsored seminar at PTC on November 4. How Smart, Connected Products are Transforming Competition. Went hand in hand with article in Harvard Business Review. Lay of land for Smart Connected Products. Ten questions businesses should ask themselves. Very appropriate.  Looking at steps
  1. 1. Monitoring.
  2. 2. Control.
  3. 3. Optimization.
  4. 4. Autonomy.
Could not help but think about the roots of IoT in tracking/viewing things. The order should perhaps still be
  1. 1. Monitoring.
  2. 2. Optimization (based purely on what is monitored and outside of any actual IoT programme).
  3. 3. Autonomy.
  4. 4. Control - Control is last because one should understand the situation before taking action.
And in many cases there are limits (safety, regulatory, privacy, moral, etc.) on what can be controlled. Most of the value is in monitoring and optimization. Some situations never get to control.
 
There were questions during discussions about..
When will industries standardize? What are we waiting for?
  1. Leadership from Apple, Amazon, Google and so forth were cited for consumer.
  2. Leadership by the main players are often cited in commercial industry. But there is a commercial incentive for non-standard approaches (differentiators) in many situations.
  3. Cooperation and collaborative openness. There are examples of collaborative standardization. There are ecosystems which makes it easy to exchange, normalize, coordinate, aggregate and analyze data.
Examples of collaborative standardization:
  • BACnet in buildings.
  • Sunspec in renewables.
  • MTConnect in factory systems.
  • OPC (XML DA) in automation.
And the following too - if an ONLY if the mapping/schema is well known... the universally accepted schema is the heart of the matter
  • Modbus in industrial. The depth and of Modbus (all the way to sensors), and the breadth of its install base, should not be ignored.
  • SNMP in IT.
  • RESTful exchange in commerce.
  • Any XML in any domain.
  • MQ (message queuing) in any domain.
SQL is often hauled out as an exchange method. There is no universal public schema for any database system. Such a schema would be orthogonal to the performance needs of a database.
 
And as a final word. Smart connected things without goals and analytics are fruitless. And goals need not be set in stone, as they are generally informed by analytics. Tactical drives the strategic and vice versa. They are two sides of the same coin. Planning is essential but plans are useless.
 

Monday, March 24, 2014

Continuous Monitoring Based Commissioning.

Article regarding Continuous Monitoring Based Commissioning.
http://w3.usa.siemens.com/buildingtechnologies/us/en/Smart_Buildings/Documents/the-12-things-you-need-to-know-about-monitor-based-commissioning-a-siemens-white-paper-final.pdf

Most everyone knows about commissioning. For most systems the concept is straightforward, and the goal is universal - optimization - chiefly for reliability (be it economic or functional.. and this is not really an "or" at transcendence).

It is more nuanced what happens with re-commissioning a system... Is it a snapshot? Does one stop the process? etc.

Then after one gets the before/after understood... one is faced with understanding ongoing versus batch/jump. The real winners (sometimes better termed "non-losers") are the ones who can harness the power of continous improvement.

Here is Contiuous Improvement with a large "C". 
http://en.wikipedia.org/wiki/Continual_improvement_process