Product Definition

The goal of the ICR team is to include as much functionality of the product(1) as possible into the Asic.  Typically reliability is better when all components are residing into the Asic and in general terms adding functionality inside the asic is more cost effective than having outside components. 
Some criteria to define if an architectural component should reside into the Asic or outside at the module (2) level are:

  • Feasibility:  are the specifications feasible with on-chip components or do we need components at the module level?
  • Risk mitigation: is there a higher product feasibility risk with the components off-chip than on-chip?
  • Optimizing the total module cost: is it
  • more cost-efficient to put the element inside the chip or outside?
  • Product Architecture

Based on the above criteria in combination with the target market/volumes/pricelevels ICR will define  with the customer the optimal chip/module architecture for the product.

Product Specification

  • Based on the architecture and nterface discussions, the product specification will be completed.

 ICR supports on

  • define the product architecture
  • assuring the Product architecture is complete and understood by all involved parties
  • defining the completeproduct specification
  • assuing the specification of the different elements (IC, Test, PAckage, Manuf.Process,....) are consistent with the product architecture

(1)Product: this is the element that fulfills the customer requirements. It generally contains a housing and a PCB with all electronic components.

(2)Module: in the ICR definition a module is a small PCB containing the asic plus all outside components as there are R,C, L external power transistors, external sensors etc. Besides the asic there may be other companion Asics or Standard products as well (FPGA, SOC, microcontrollers etc.)