Re: [Roll] [6tsch] comments on draft-phinney-roll-rpl-industrial-applicability

Tom Phinney <tom.phinney@cox.net> Fri, 01 March 2013 21:32 UTC

Return-Path: <tom.phinney@cox.net>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1071F0D10 for <roll@ietfa.amsl.com>; Fri, 1 Mar 2013 13:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level:
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZPD29e3zC9J for <roll@ietfa.amsl.com>; Fri, 1 Mar 2013 13:32:07 -0800 (PST)
Received: from fed1rmfepo202.cox.net (fed1rmfepo202.cox.net [68.230.241.147]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC4C21F8870 for <roll@ietf.org>; Fri, 1 Mar 2013 13:32:07 -0800 (PST)
Received: from fed1rmimpo210 ([68.230.241.161]) by fed1rmfepo202.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20130301213202.GZGC1243.fed1rmfepo202.cox.net@fed1rmimpo210> for <roll@ietf.org>; Fri, 1 Mar 2013 16:32:02 -0500
Received: from 192.168.1.250 ([68.106.19.170]) by fed1rmimpo210 with cox id 6MY01l00M3gAAro01MY2dl; Fri, 01 Mar 2013 16:32:02 -0500
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A020206.51311E52.008D,ss=1,re=0.000,fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.0 cv=Q80MFfKa c=1 sm=1 a=mbYREmtDDBfCLQwKCHNpxg==:17 a=YkMd_PYDa9IA:10 a=fUqkgGA-opkA:10 a=G8Uczd0VNMoA:10 a=Wajolswj7cQA:10 a=IkcTkHD0fZMA:10 a=kviXuzpPAAAA:8 a=kefdhCRHuhUA:10 a=48vgC7mUAAAA:8 a=7fnSsO-jmgmup-exoxwA:9 a=QEXdDO2ut3YA:10 a=_W_S_7VecoQA:10 a=4vB-4DCPJfMA:10 a=lZB815dzVvQA:10 a=2u8-7BD2COMLsqic:21 a=mbYREmtDDBfCLQwKCHNpxg==:117
X-CM-Score: 0.00
Authentication-Results: cox.net; none
Message-ID: <51311E50.7010604@cox.net>
Date: Fri, 01 Mar 2013 14:32:00 -0700
From: Tom Phinney <tom.phinney@cox.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: "roll@ietf.org" <roll@ietf.org>, "6tsch@ietf.org" <6tsch@ietf.org>
References: <20381.1362077015@sandelman.ca> <E045AECD98228444A58C61C200AE1BD835CD4B00@xmb-rcd-x01.cisco.com> <17207.1362162863@sandelman.ca> <5131049C.9020504@cox.net> <795.1362168205@sandelman.ca>
In-Reply-To: <795.1362168205@sandelman.ca>
X-Enigmail-Version: 1.1.1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 04 Mar 2013 09:50:39 -0800
Subject: Re: [Roll] [6tsch] comments on draft-phinney-roll-rpl-industrial-applicability
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Tom Phinney <tom.phinney@cox.net>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 21:32:08 -0000

The continuous and discrete manufacturing parts of hybrid manufacturing plants are ALWAYS connected; it would be pointless to build such a plant if that were not the case.

It is useful to consider the differences. Continuous processes use closed-loop control based on fixed-period process sampling and outputs to process actuators. The highest frequency of such control loops is usually 4 H, though a few compressor surge control loops that operate at a 9 Hz to 11 Hz rate may also be present. These process control systems are potential users of wireless communications because their fixed timing is compatible (in theory) with TSCH-like time schedules.

It is important to understand that the publish-subscribe messaging used for process automation does not require 100% delivery. The control algorithms traditionally are designed to tolerate the loss of three or fewer consecutive messages before receiving another message in the series. However, typically loss of four consecutive messages triggers the equipment to shift to a fallback control strategy. It is this statistic that leads to use of duocast (with its approximate squaring of message loss rates) for high-speed loops, since most plant managers will not tolerate more than one such shift to a fallback control strategy per year, per plant, and there can be thousands of 1 Hz and 4 Hz control loops operating in the plant.

Discrete processes use a different form of control that is cyclic but not periodic. This is usually implemented in PLCs (programmable logic controllers) that execute a variable-execution-duration program that repeats as soon as it finishes each iteration, leading to cyclic but aperiodic behavior. The duration of each execution cycle is usually a few ms, typically 3 ms to 10 ms, with a perhaps 50% maximum variance in cycle-to-cycle.
execution time. The messaging involved in such automation typically require higher data rates than those offered by IEEE 802.15.4, and any wireless messaging itself would typically be single-hop, from a router/local-controller that is part of the manufacturing device to multiple wireless backbone routers arranged high on opposite walls in a roofed factory. High-data-rate optical signaling would be a good match for this communication.

The variance in cycle-to-cycle times provides a significant challenge for comm technologies based on scheduled pairing of senders and receivers. That, coupled with the typically single-hop aspect of the communication, makes it likely that a non-TSCH approach will be optimal for such systems.

The communication between the continuous process controllers of a plant and the discrete automation controllers typically occurs on a 100 Mbit/s or faster backbone comm link. Wireless is not involved, and there is no reason to anticipate that it will be in the future. Since the physical systems that implement the continuous and discrete processes are interconnected (e.g., pipes with valves connected to bottle handling-and-filling apparatus in a soda bottling plant), wired interconnection between backbone controllers is typically not a significant issue.

I hope that the above discussion helps understand the differences in operating mode, timescales, comm needs and other high-level aspects of the continuous and discrete portions of a hybrid plant. There are others receiving this e-mail who are much more familiar with such plants and processes than I, so if I have erred substantially, I trust that they will post a correction to this list.

-Tom
=====

On 2013.03.01 13:03, Michael Richardson wrote:

      
"Tom" == Tom Phinney <tom.phinney@cox.net> writes:
    Tom>    Apologies to those who receive this e-mail on more than one
    Tom> list.  First, the traditional industry differentiation between
    Tom> "factory automation" and "process control" is that factory
    Tom> automation is focused on discrete manufacturing steps (and thus
    Tom> is often referred to as "discrete parts manufacturing") while
    Tom> process control involves continuous processing of fluids and
    Tom> quasi-fluids (e.g., sand, cereal and other materials whose flow
    Tom> rate can be measured by a mass flowmeter).  Many real-world
    Tom> plants use hybrids of these two manufacturing styles.  

So, given that many plants are hybrids, are you saying that this
document applies only to the process control parts of the plant?

Or that hybrid plants are also out of scope?

If there are scope constraints, what exactly are they? 

What happens in a hydrid plant might be significantly more complicated,
as it involves two kinds of networks; if there is a desire to have the
different pieces interconnected.

_______________________________________________ 6tsch mailing list 6tsch@ietf.org https://www.ietf.org/mailman/listinfo/6tsch" rel="nofollow">https://www.ietf.org/mailman/listinfo/6tsch