Phase process diagram

This diagram is an example of a phase process:
Example of a phase process
FTB_PCD Programmers phase process diagram
  1. The command to START the phase is issued from the
    FactoryTalk Batch
     Server. The RUNNING program eventually begins.
  2. The phase logic sends a request to download the AMOUNT parameter from the
    FactoryTalk Batch
     Server.
  3. The
    FactoryTalk Batch
     Server requests a Promise ID from the Material Server. This establishes an accounting data entity for tracking the inventory used.
  4. The Material Server returns SUCCESS for the Promise ID to the
    FactoryTalk Batch
     Server. This is used by the
    FactoryTalk Batch
     Server during a non-Cold Restart to restore the state of a batch if the
    FactoryTalk Batch
     Server service stopped as the batch was running.
  5. The
    FactoryTalk Batch
     Server downloads the parameters to the phase logic. The PCD runs its program to perform a material addition or distribution.
  6. The FEED_COMPLETE and ACTUAL_AMOUNT parameters are uploaded to the
    FactoryTalk Batch
     Server.
  7. The phase logic transitions to a terminal state.
  8. The value returned in the FEED_COMPLETE report parameter, and the Hold on Split Feed configuration determine what recipe execution will do next:
    TIP:
    Set the
    Hold on Split Feed
     option in the
    FactoryTalk Administration Console Explorer
    . Right-click an application or area name to either add a server or edit an existing one. To add a server, select
    Add New Server FactoryTalk Batch Server
    . Set the
    Hold on Split Feed
     option by opening the
    FactoryTalk Batch Services Properties
     dialog
    General
     tab. In the
    Material policies
     area, view the
    Hold on Split Feed
     option.
    • If FEED_COMPLETE is TRUE, the batch continues running.
    • If FEED_COMPLETE is FALSE, and
      Hold on Split Feed
       is YES, the batch is held.
    • If FEED_COMPLETE is FALSE, and
      Hold on Split Feed
       is NO, the batch continues running.
  9. The amount of the material addition or distribution is sent to the Material Server. The inventory levels in the material database are updated, and for material additions, the sublot or sublots of inventory used are identified.
  10. Material, lot, and container data are returned to the
    FactoryTalk Batch
     Server and recorded in the
    FactoryTalk Batch
     Event Journal.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal