Page Comparison

Operation aliasing allows process engineers to group similar operations from one or more process flows for reporting purposes.

For example, several inspection operations such as AOI, manual inspection, and final inspection could all be assigned an Alias of Inspect. Once assigned, reports can be generated against the Inspect alias that takes all three operations into account instead of having to specify each operation manually in the report.

• Use the Alias drop-down to select a previously-defined alias, or select the Add Operation Alias  button to create a new alias.
  
  

  Note
  icon false title Note:
  Global operation aliases are used to define global operations accessible from Production. If you don't use global operations, you do not need to define any operation aliases as global. If you do use global operations, you need to define these aliases as global and also associate an appropriate Operator Interface template to make the global options available.  Use the Is Global column/option to specify an operation alias as global.

  
  

• No Tracking - Presents paperless work instructions only (no WIP tracking).
• Movement Tracking Only - Presents work instructions and tracking to indicate a product or assembly has passed through the operation. Start/Finish is immediate, so no actual processing time is recorded when you use this mode.
  • Allow Barcode Ranges lets operators enter a range of serial numbers to allow processing multiple units at once.

• Full Tracking - Forces operators on the shop floor to both start and finish a product or assembly as it moves through this operation, providing total touch time at this operation.
  
  

  Note
  icon false title Note:
  Touch time is the total time that a unit is started at an operation and not in a paused state.

  
  

  • Allow Multiple Units - Permits operators to scan more than one assembly into this operation at any one time for simultaneous processing.
    • Perform Activities by - Specifies whether activities for this operation will be performed By Activity or By Unit.
      
      Perform Activities By Unit allows you to start a WIP transaction for multiple units at the same time while forcing you to pass activities for each unit one at a time. For example, if you enable this option at an operation and start three barcodes there, instead of seeing all three barcodes in the WIP gadget, only a single barcode displays. You only pass activities for this barcode rather than for all three barcodes currently started. After passing all activities for the first barcode, you select the next unit from the WIP gadget and complete the same activities. You would complete activities for the final barcode, then the WIP transaction could be completed. 
      
      
  • Allow Barcode Ranges - Permits operators to enter a range of serial numbers allowing processing multiple units simultaneously.

  • Allow Next Operation Autostart - (This option is for operations with Full Tracking enabled in NPI.) Specifies that the operation following this operation will start automatically. When selected, an operator is able to press a button to complete all units in Production with a Passed status and those same units will be started at the next operation automatically. You configure the behavior of the Finish button in Production.

• Sampled Inspection - Sampled inspection is a technique to determine whether a lot should be accepted or rejected on the basis of the number of defective parts found in a random sample taken from the lot. The methodology used to sample depends on the type of analysis being done but may include simple random sampling or systematic sampling.
  • Sampling Plan - Specifies the sampled inspection plan to use for this operation.
    • MIL-STD-105E - ANSI/ASQ Z1.4 Sampling Plan - Refers to a United States defense standard that provides procedures and tables for sampling by attributes. 
    • MIL-STD-1916 - Accept-on-Zero (c=0) - MIL-STD-1916 is a United States defense standard that contains Accept On Zero (AOZ) plans for attributes, variables, and continuous sampling.
    • Squeglia Zero-Based Plan - Refers to a zero-defect sampling plan that is based on an acceptance threshold of c=0.  A lot or batch will only be accepted if no non-conforming items are found in the sampled inspection.
  • Sample whole batch, pass/fail whole batch - When a whole batch is sampled, if any units fail, the entire batch will fail.
  • Sample incrementally on intervals, pass/fail incrementally on individual interval lots - 
    • On Interval Lot Failure: If an interval lot fails, allows you to select what happens: Fail Sub-Lot Only or Fail Sub-Lot and All Subsequent Units.

    • On interval lot pass, unload carriers related to lot - When an interval lot passes sampled inspection, specifies that the carriers for that lot will be unloaded.
      
      

      Note
      icon false title Note:
      For more information about using sampling plans in FactoryLogix, see Add a new quality sampling plan.

      
      

• Allow Product Scrapping - Specifies whether shop floor operators can change a product or assembly status to Scrapped. 
• Allow Operation To Be Repeated - Affects WIP tracking operations and route enforcement.

  By default, a product or assembly may only pass through an operation one time—the next operation defined in the process flow is the only valid operation from a route validity perspective for the product or assembly to be scanned into. This option allows an assembly to be scanned into the specified operation more than once.
  
  

• Estimated Cycle Time - Specifies the expected/estimated time (in seconds) required to complete this operation.
  
  Reports and real-time dashboards can make use of this information to calculate and display information to operators indicating if they are performing as expected.
  
  

  Note
  icon false title Note:
  Cycle time is the complete time a unit has been at an operation. It begins when the unit is first scanned into an operation and stops when the unit is finished. Pausing the unit does not stop the cycle time count.

  
  

• Setup Time - Allows process engineers to specify the expected amount of time (in seconds) necessary to set up this operation for a new build.
• Resource Types - Allows process engineers to specify the type of resource this operation belongs to for resource planning purposes.
  
  You can add more resources by selecting the Edit Resource Types  button to the right of the Resource Types drop-down:
  
  
  
  
  
• Operation Locator Mode - Defines the side of the board to which an operation should be attributed: Top, Bottom, Auto. The side is determined based on the next logical side for which events aren't yet recorded. These options are used mostly for xLink machine data.
• ERP Route Point Name - Used with the xTend Integration FLX-XTD-WIP-01 (WIP Data Export) to tie FactoryLogix operation names to the corresponding ERP route point in your ERP system. Some ERP systems use a simple text name, some use a numeric or alphanumeric value, some use a combination of the two.
• ERP Route Point Value - Used with the xTend Integration FLX-XTD-WIP-01 (WIP Data Export) to tie FactoryLogix operation names to the corresponding ERP route point your ERP system. Some ERP systems use a simple text name, some use a numeric or alphanumeric value, some use a combination of the two.
• Enforce FIFO WIP Control - When selected, enforces First-In-First-Out WIP control of the operation.
• FIFO WIP Admin Override Mode - Controls override permissions for First-In-First-Out WIP control of an operation.
  

  None - Prevents any overrides from occurring.
  Single Transaction - Allows an override of a single transaction.
  Current Operation - Allows an override of the current operation only.
  
  

• Purpose - Allows you to create a new reason code or select an existing reason code for this operation. (See Add, delete, and manage reason codes for more information.)
• Finish Behavior - Specifies what happens when this operation is finished.
• Record Recipe parameters as Measurements - Saves recipe parameters in the FactoryLogix database. You can view these measurements in the Trace window in the Production client application or in the Test and Measurement data source in DataMiner.