PLM Customer Stories: AttributeState

Teleflex

Teleflex is a global provider of medical technologies designed to improve the health and quality of people’s lives. They apply purpose driven innovation – a relentless pursuit of identifying unmet clinical needs – to benefit patients and healthcare providers. Their portfolio is diverse, with solutions in the fields of vascular and interventional access, surgical, anesthesia, cardiac care, urology, emergency medicine and respiratory care. Teleflex is the home of Arrow®, Deknatel®, Hudson RCI®, LMA®, Pilling®, Rusch®  and Weck®

Problem-icon-transparent.png
The Challenge

Teleflex has several plants and the BOMs (Bill of Materials) are plant specific. These BOMs need to be maintained manually, which is error-prone and time consuming.

 

Solution-icon-transparent.png
The Solution

Zero Wait-State installed AttributeState, which automatically extrapolates the plant information for items and BOMs. This provides necessary data to visualize and update the BOM specific to the plant.

 

benefits.pngThe Benefits

Through automation of setting item and BOM plant variations, Teleflex now has the ability to automate, streamline and prevent errors, thanks to AttributeState. Now Teleflex reaps the benefits of increased productivity due to elimination of a time consuming, error prone manual process. They have also decreased the amount of manpower necessary to update these BOMs. Teleflex now owns a customization platform for Agile PLM which they can leverage internally for future needs.

  

Stanley

Stanley Black & Decker is a world-leading provider of tools and storage, commercial electronic security and engineered fastening systems, with unique growth platforms and a track record of sustained profitable growth. STANLEY Healthcare is a recognized leader in visibility and analytics solutions that transform safety, security and operational efficiency for senior living organizations, hospitals and health systems

Problem-icon-transparent.png
The Challenge

Stanley required custom CAPA and NCR workflow notifications not possible with out-of-the-box Agile PLM configuration. They desired the ability to quickly and easily modify these notifications to support future business requirements.

Solution-icon-transparent.png
The Solution

Zero Wait-State implemented AttributeState, which now ties into workflow status change events for CAPAs and NCRs. AttributeState uses templates to determine and set observers which can be easily updated by Stanley without assistance from ZWS.

 

benefits.png
The Benefits

Stanley can now be more responsive to CAPA and NCR issues due to notifications going to the correct person. They can also update the automation around CAPA and NCR notifications as needed by simply changing a template. Thanks to AttributeState, Stanley owns a customization platform for Agile PLM which they can leverage internally.

 

Enovation Controls

Enovation Controls is a leading global provider of electronic control, display and instrumentation solutions for recreational and off-highway vehicles, stationary equipment and power generation applications. Enovation Controls serves these markets and more with a portfolio of products under the Murphy, Zero Off and High Country Tek brands. 

Problem-icon-transparent.png
The Challenge

Enovation Controls had many requirements around automation and data consistency within their Agile PLM environment which would typically require a large number of independent process extensions.

 

Solution-icon-transparent.png
The Solution

Zero Wait-State installed AttributeState to enable Enovation to centralize all of their automations under the umbrella of a single customization framework.  This allowed Enovation to centralize all of their customizations within a single AttributeState configuration spreadsheet which is versioned controlled within Agile to provide visibility into and quick turnaround for changes to their customizations.  

benefits.pngThe Benefits

  • • Smart Selection of Secondary Fields such
       as Populating the Commodity based on
       the Component Subtype selection
  • • Propagation of primary Branch Plant to All
  • • Automation of Workflow Selection based
       on ECO Conditions
  • • Automating Subtype Selection for specific 
       Subclasses or other conditions

 

  
  • • Clearing and/or Defaulting Specific Fields
       using SaveAs
  • • Using Template BOMs – Quickly Create New
       Part Numbers including select BOM
       children, while Referencing other BOM
       Items
  • • Auto Assignment of Item Group(s) based on
       other selections
  • • Enforce standard practices and general
       data consistency

MKS Instruments

MKS Instruments, Inc. is a global provider of instruments, subsystems and process control solutions that measure, control, power, monitor, and analyze critical parameters of advanced manufacturing processes to improve process performance and productivity. Our products are derived from our core competencies in pressure measurement and control, flow measurement and control, gas and vapor delivery, gas composition analysis, residual gas analysis, leak detection, control technology, ozone generation and delivery, RF & DC power, reactive gas generation, vacuum technology, lasers, photonics, sub-micron positioning, vibration isolation, and optics. Our primary served markets include semiconductor capital equipment, general industrial, life sciences, and research. 

Problem-icon-transparent.png
The Challenge

MKS Instruments had requirements around cost rollup, automation, and data consistency within their Agile PLM environment which would typically require a large number of independent process extensions. 

 

Solution-icon-transparent.png
The Solution

Zero Wait-State installed AttributeState.

 

 

benefits.pngThe Benefits

  • • Recursive cost rollup or items onto a new
       item subclass called “Quote Item”. A set of
       attributes and rules govern how the rollup
       is performed and allow overriding of cost   
       and 
    cost multipliers at the individual item
       level
  • • Setting a page two attribute named “Item
       Type” 
    based on the values of several other
       attributes. 
    The attributes used in
       determining the value 
    for “Item Type”
       include simple text, numeric, 
    and list
       values as well as relationship to
       other 
    objects (dynamic list values).
  •  • Set item attributes ”Design Center” and    
       “Primary Org” by locating a type of user
       group named “Design Center” associated
       with the logged in User and extracting
       those values from that user group
  • • Setting of the ”Commodity” attribute on
       items based on the “Item Subtype” during
       new item creation
  • • Business unit specific semi-intelligent part
       numbering
  •  


Contact Us Today to Learn More About AttributeState
Contact Us Today