Figure 4 Kanban Mechanism of Limiting wip.
图4限定在制品数量的看板机制。
The WIP contains information about past executions of each step.NO!
WIP包含了每个步骤以前执行的有关信息。错！
Then the WIP administrator defined 2 new schedules for that step: one recurring, and the other a one-time only.
然后，WIP管理员将为该步骤定义2个新的调度：一个重复发生，而另一个则只运行一次。
For each edition maintained in the WIP, its most current status is displayed.
对于维护在WIP中的每个版本，显示的是其最当前的状态。
The first mechanism only refers to the amount of WIP, but this second refers to the flow, its direction and speed.
第一个机制仅仅涉及到在制品的数量，而第二个则涉及到流程——流程的方向和速度。
I have seen some zealous WIP operators who purged successful editions from the WIP.
我曾看到一些热心的wip操作员将成功的版本从WIP中清除。
The information related to each execution of a step is uniquely identified in the WIP by an edition number, associated to a specific execution of a step.
WIP 中将通过版本号来惟一识别与每一步的执行相关的信息，因为版本号是与特定的执行步骤相关联的。
In this approach, the focus is on "Limits WIP", "Continuous Flow" and "Pull", at the same time, allowing the team (or manager) to use it for process improvement purposes.
在这种方法中，它的关注点是“限制在制品的数量”、“连续流通”和“拉动式”，同时允许团队(或者管理人员)借其改进工序。
Since these tables keep growing, the WIP operator needs to periodically remove from these tables the information that is obsolete.
由于这些表持续增长，所以wip操作员需要定期将已废弃的信息从这些表中删除。
The right-hand side of this graph explains how it minimizes WIP while sustaining continuous flow.
图表右侧说明了如何在维持连续流通的同时，最大限度地减少在制品。
The WIP window is a very dynamic environment; information about editions very frequently changes in the WIP, to reflect when the transformation steps are scheduled, and how the execution progresses.
WIP窗口是一个极其动态的环境；版本的有关信息在WIP中频繁变化，用以反映何时调度转换步骤以及执行进度如何。
If WIP in the store is too few, the downstream process has to wait for items not ready when needed, but at the same time WIP should be minimized to prevent overproduction.
如果仓库中的在制品太少的话，下游工序不得不等待所需的零部件准备就绪，但是在制品还应该保证最小化以防止生产过剩。
The maximum number of Kanbans (the "energy" in the system) is fixed and physically conserves the upper limit of WIP at any given time.
在任何时候，看板(相当于系统中的“能量”)的最大数量都与在制品的上限保持守恒。
"Limits WIP", "Continuous Flow" and "Pull" properties are not attained by the Agile Kanban example by itself, shown in Figure 5.
图5所示的敏捷看板例子本身并没有实现“限制在制品的数量”、“连续流通”和“拉动式”特性。
The WIP contains information about the last execution of each step.NO!
WIP包含了每个步骤最后执行的有关信息。错！
Failed editions may be purged safely from the WIP, since there is no data that was filled in the target table for a failed edition.
可以将失败的版本从WIP中安全地清除，因为一个失败版本没有向目标表填充任何数据。
It also may allow managers to reduce WIP buffers, which in turn reduces overall inventory and-most important these days-frees up cash on the balance sheet.
它还可以帮助管理人员削减在制品的临时库存，进而减少总的库存-当然今天最重要的是，增加增产负债表中的现金流。
The second mechanism, "Pull," also limits WIP by making the production velocity of the upstream process dependent on the downstream consumption velocity.
第二个机制——“拉动式”——通过依据下游消耗速度来确定上游工序的生产速度，这种机制也限制了在制品的数量。
The amount of information stored in the WIP can grow quite significantly, especially if the amount of steps run daily is large.
WIP中存储的信息量可能会极快地增长，特别是在每天运行很多步骤的情况下。
Information about transient steps is visible in the WIP only while the transient step is being executed; it disappears as soon as the step firing the execution of the transient step completes.
只有在执行暂态步骤的时候，才能在wip中看到其有关信息；而激活暂态步骤的那个步骤一旦完成，这些信息就会消失。
But at 14:20:26, the WIP administrator demoted the step out of production, and therefore the schedule became inactive.
但是在14：20：26,wip管理员会将该步骤从生产级别降级，该调度因而就变成非活动的了。
As you'll see here, there are roughly two different meanings of Kanban, one is "Limits WIP while sustaining Continuous Flow", and the other is "Kaizen".
你从中可以看到看板的两种含义，一是“在维持连续流通的同时限制在制品数量”，而另一种是“改善”。
A WIP of 1 was set for this lane, since we want to discourage the use of this category.
这个泳道的并行任务限制值设为1，因为我们希望少用这个类别。
Kanban's aim is to minimize WIP (Work-In-Process), or inventory, between processes by making sure that the upstream process produces parts only if its downstream process needs it.
看板试图通过确保上游阶段只生产下游阶段所需的零件，以达到在不同阶段之间最小化WIP(未完成任务)，或者存货清单的目的。
These records about scheduled editions already executed are deleted from the WIP after execution.
而这些关于已经执行的被调度版本的记录在其执行之后就已从WIP中删除。
Suppose that the WIP administrator decides to schedule the process for hourly execution; in this situation the WIP_ARCHIVE table only contains data which is at most one hour old.
假设WIP管理员决定每小时调度执行一次该过程；在这种情况下，wip_archive表最多只包含一小时之内的数据。
In order to make the process continuously flow as well as to limit WIP, "iteration meetings" are needed to communicate the information.
为了使工序连续流通并限制在制品的数量，需要召开“迭代会议”交流信息。
These temporary statuses are visible only for a short time in the WIP, until the edition is purged, canceled, or is being retried for population.
在清除、取消或为填充而重试该版本之前，只能在WIP中短时间内看到这些临时状态。
The WIP contains, for the last execution of each step, the intermediate statuses that the step went through.NO!
WIP包含了每个步骤最后一次执行中所经历的中间状态。 错！
In other words, the WIP does not maintain a full history of each edition, nor all the statuses that an edition went through.
换言之，WIP不会维护每个版本的全部历史记录和版本经过的所有状态。
应用推荐