r12oic_oaug2009

Discover the Secret to R12 OIC

Lakshmi Sampath, Dell, Inc.

Presenter Qualifications• Global EBS Architect at Dell, Inc.• Expertise in implementing EBusiness Suite 11i

& R12 – including IStore, ISupplier, CRM – OIC, RM/TM, OM, PA, Financials & HRMS

• Presented several Papers and hosted several Panels at the OAUG, Oracle Open World, Austin Oracle Users Group etc.

• ENCORE Presenter @ COLLABORATE-2006• Board Member of the Oracle Business

Intelligence Special Interest Group (OBISIG) and Austin Oracle Users Group (AOUG)

Session Objectives• Learn about new Release 12 overview for

Oracle Incentive Compensation and Territory Manager along with Integration points

• Review the Steps to Implement OIC• Review some of the undocumented secrets

uncovered during our POC sessions.• Take away tips and techniques to use Oracle

Incentive Compensation (OIC) and Territory Manager (TM)

Target Audience for This Presentation • Oracle Customers currently evaluating Oracle

Incentive Compensation module• Oracle Customers who are planning to

upgrade to R12 from prior releases• Oracle Implementers who are planning or in

the process of implementing Oracle Incentive Compensation and Territory Manager modules.

Overview of Incentive Compensation• Eligible Transactions are determined• Eligible Credits are determined• Payments are calculated and processed• Territory Manager calculates the credits

based on sales reps assigned to Territories

Oracle Incentive Compensation Overview• Oracle Incentive Compensation (OIC) is a global variable

compensation application that automates the design, administration, and analysis of incentive-based compensation programs to successfully drive corporate goals.

• OIC enables "pay for performance" while maintaining necessary financial controls.

• OIC allows organizations to connect sales incentives to business objectives to motivate workers (sales reps).

• OIC automates the complex task of modeling and calculating incentive payments.

Oracle Incentive Compensation Overview

CollectionInterface Tables

• Configurable data mappings• Transformation & enrichment• Post collection actions / filters

Calculation Engine

• Multi-threaded/Grid processing• Retro active calculation• Incremental calculation

CompensationPlans

• Complex formulas• Flexible expression builder• Link to external logic• Linked objectives• Multiple rate dimensions

• Date effective components

• Reusable components• Currency conversion

Territory Manager Overview• Territory Manager enables organizations to align territories

accurately and efficiently.• Territory Manager is used in OIC to determine who the credit

receivers are for sales transactions• In OIC, Sales Credit Allocation is run to determine the how

much• TM has added new features that OIC has adopted in R12:

• Allows custom attributes to be created and used as territory qualifiers

• Provides effective dated territories for correct assignment by the Territory Engine

• Batch processing for assignments with new parameters• Additional seeded mapping

Territory Manager OverviewThe Benefits of the TM to OIC Integration Include:– Correct assignment using effective dated territory resources and

roles– Improved performance– Less setup for mapping and calls to the Territory Assignment

Engine (TAE) through Oracle Incentive Compensation for a more rapid implementation

Territory Rules

TransactionsCollection EngineCallsTAE

Credit Transactions

OIC Integration with Other Modules

Steps to Implement OIC

1. GL Setups2. Multi-Org Setups3. OIC Initial Setups4. Resource Manager Setups5. OIC Setups6. Compensation Plan Setup7. Pay Groups8. Pay run

GL Setups

• Base GL Setups (4C’s)– Currency, Calendar, Chart of Accounts,

Convention• Accounting Flexfield Setup• Ledger (COA)• GL Calendar to be opened

Multi-Org Setups

Hierarchy• Business groups• Primary ledgers • Legal entities• Operating units• Inventory Organizations

Multi-Org Setups

Organization Structure Example

Multi-Org Setups

• Create Security Profile• Attach the Security profile to responsibilities• Run Security List Maintenance

OIC Initial Setups

• Open the Compensation Periods• Navigate to Incentive Comp Administrator,

Configuration Workbench and define the following parameters• Application Parameters• Collection• Calculation• Payment• Credit Allocation

OIC Initial Setups

OIC Initial Setups

OSC: Default Conversion Type

OSC: Default Custom Flag

OSC: Reporting Hierarchy

Display Draw

Some of the 11i Profile Options are Configuration Workbench Parameters in R12

OSC: Collect on Acct Credits

OSC: Negate during Revenue Adjustments Collection

OSC: Apply Non Revenue Split to Quantity

OSC: Reset Error Transactions

OIC Initial Setups

OIC Initial Setups

OSC: Roll Summarized Transactions

OSC: Customized Summarization

OSC: Commission Rate Precision

OSC: Income Planner Disclaimer

OSC: Prior Adjustment

Resource Manager Setups

• Setup Resources and Salesreps or Import from HRMS

• Setup RolesSales Compensation Role types

• Setup Groups (Hierarchy)• Setup Teams

OIC Setups

• Collection– Transactions can be collected from AR– Oracle Order Management (Order Capture)– Custom data sources

OIC SetupsEligible Products (Formerly Revenue Classes)• OIC determines the corresponding eligible products for a transaction

to determine whether the credit receiver can receive compensation for that type of revenue.

• Eligible products serve two purposes:– They let you vary compensation by type of revenue.– They help determine whether a salesperson can be paid

compensation for the type of revenue represented on the compensation transaction.

Presenter

Presentation Notes

Instructor Note You can use the ATTRIBUTE1 through ATTRIBUTE100 descriptive flexfields in the CN_COMMISSION_HEADERS table to classify a transaction into a revenue class. In order to use the flexfield, Classification Value check box must be selected for the column using the Tables and Columns function. The Column Datatype must also be set to either numeric or alphanumeric (the default is alphanumeric). You can also specify a valueset name. The valueset should be table validated. The values in the specified valueset are used in the Value field instead of unvalidated data entry when you are defining a rule attribute.

OIC Setups

Transaction Factors for Eligible Products– Key transaction factors used to assign sales

credit:• Upon order• Upon invoice• Upon payment

– Other transaction factors include (default set):• Clawback• Credit Memo• Giveback• Manual Adjustment• Write-off

Presenter

Presentation Notes

Transaction Factors Key transaction factors define when during the revenue cycle OIC recognizes sales credit related to a transaction. For each revenue class assigned to a plan element you need to specify how much of the compensation you want OIC to award for each type of transaction you collect. The key transaction factors are: Order: When the order is received Invoice: When the invoice is processed Payment: When payment is received It is possible to select one or more of these key factors in combinations as long as they total to 100%. For example - 25% on Order date, 50% on invoice date and 25% on payment date. When calculating the compensation payment OIC multiplies the sales credit by the transaction factor you have defined. If you want to collect from additional transaction or other factors you would need to run the concurrent requests relating to these during the collections process in order to get all the data required into OIC. Other transaction factors that can be used include: Clawback: If customer doesn’t pay bill, the clawback of commission previously paid for the sale Credit Memo: If a credit memo is issued against an invoice or customer’s account Giveback: If a payment is received for a clawback Manual Adjustment: If a manual adjustment is made in OIC Write-off: A sale is reversed reducing a salesperson’s compensation Note: These do not have to total 100%.

OIC Setups

• Define Products/Product Hierarchy (upload available)

• Classification Rules– Rules that determine the nature of revenue class

for each transaction• Synchronize Classification Ruleset

Compensation Plan SetupPlan creation pre-R12“Bottom-Up”

R12 plan creation“Top-Down”

Presenter

Presentation Notes

In 11i, compensation plans were built bottom-up. Building blocks had to be defined before they could be included in larger building blocks. For example, the Plan Administrator had to first define a rate dimension in a separate flow, then create a rate table using the rate dimension. This approach makes the plan creation process somewhat complex, as the Plan Administrator would first have to map out which expressions were needed for every formula and create them all at once before creating formulas. In R12, the Plan Administrator can build compensation plans top-down. He can directly enter the compensation plan creation flow, and define plan components as necessary in order to complete the flow.

Compensation Plan Setup

Benefits of Top down creationSimplifies plan creation

Start with a blank plan and create plan components as necessary

No advanced planning for plan components

Reduces maintenance complexity

Dependencies between plan components are easier to track

Streamlines/simplifies demo flow

Presenter

Presentation Notes

In R12, the Plan Administrator can build compensation plans top-down. He can directly enter the compensation plan creation flow, and define plan components as necessary in order to complete the flow. This eliminates the need to map out and create all of the necessary plan components beforehand. When a compensation plan is created top-down, the Plan Administrator gains a greater understanding of the dependencies between the plan components in the plan.

Compensation Plan SetupBuilding Blocks of a Compensation Plan

RolesRolesSales GroupSales GroupResourceResource

Presenter

Presentation Notes

Compensation Plan Process It can be stated that compensation plans are built from the bottom up. First, the calculation expressions and rate tables are created, then a formula is defined that uses them. The formula becomes part of a plan element. A revenue class is added to the plan element so you can make a link with the revenue classes that have been assigned to the classified transactions. A completed compensation plan comprises of one or more plan elements. The plan is then assigned to a sales role, which is assigned to individual salespeople.

FormulasFormulas are composed of several components:

Input expressions: Transactional data that determines commission rates

Rate Tables: Designates commission rates based on input expressions values comparisons with rate dimensions

Output expressions: Determines the commissionable amount

Performance Measures: Accumulates expression to use in Year-to-Date Summary reporting

Forecast Expressions: Used to estimate commissions from Oracle Quoting

Compensation Plan Setup

Presenter

Presentation Notes

Formulas Inputs are evaluated first: The values of the inputs are then compared to the rate table tiers and a commission rate is determined. The output expression is then evaluated and a commissionable amount is determined. The following rules apply to the input expression: Apply Transactions Accumulative Interval to Date The following rules apply to the rate table commission rate: Split Any column from any table can be part of your formula, providing the Calculation Value check box for the column is selected in Columns and Tables. Calculation expressions must be defined before you assign them to your formulas. Rate tables must be created first if you want to include them in your formula. Calculation expressions can be repeated in your formula and can also be reused on other formulas as well. Formulas can be used in another formula definition (formula embedded into another expression) or in a plan element definition. Apply transactions individually if you want each transaction calculated separately to determine a rate. Group transactions if you want transactions aggregated to determine the rate. Grouped transactions require input expressions that utilize the Group SQL functions; only these type of expressions will appear in the input expressions. Do not split tiers if you want a rate from the rate table applied to the full amount. Split tiers if you want portions of the full amount paid at each rate up to the top qualifying rate. Select the Accumulative check box if transactions are required to be aggregated in total. The rate applied will be determined by the transaction total achieved to date within the interval. Bonus formulas calculate only against individual transaction options. You can save an incomplete formula and complete it later. Bonus Formula A bonus formula may not have links or references to transactions. Forecast Expressions The forecast expressions need to be simple in order for the Income Planner to work; no customized attributes in the expression. The input needs to include the calculation value Forecast Amount and the output must possess limited attributes. For more information on Income Planner please refer to the lesson titled “Compensation Tab and Income Planner.”

FORMULAFORMULA

InputExpressions

InputExpressions

Output Expressions

Output Expressions

Rate Table Results

Rate Table Results

Green = Provided to Incentive CompensationBlue = Calculated by Incentive Compensation

Compensation Plan SetupFormula Components

Formula Parameters

• Below are the valid combination of options available for formulas :– Transactions

— Group By Interval

— Cumulative— Individually

— Cumulative— Cumulative and Interval To Date

– Split— No Split— Non-Proportional— Proportional

Presenter

Presentation Notes

Instructor Notes: Selecting the Planning option has no bearing on how OIC will calculate or store transaction totals. This option is only used for the Sales Force Planning (SFP) module of OIC. Transactions: Assume the following rate table: 0-100 5% 100-30010% 300-9,99915% Sample Transactions: $75 in Jan-XX $125 in Feb-XX $110 in Mar-XX $50 in Apr-XX Group By Interval: Cannot be Interval to Date, must be used with Cumulative. Transactions are calculated in batch for the entire interval. For example, if the plan element has an interval of quarter, all transaction totals will be calculated and stored until the end of that interval. Using the above examples if a formula has been set up for a Group By Interval. This option instructs OIC to group the transactions for the entire interval as a batch and then apply this total into against the rate table. Using the above example, the payout for the transaction will be ($360 X 15%). Total payout $54. Individually Can be be used with Cumulative only. By using this option OIC will track the sum of each individual for the duration of the plan element. For example, if the plan element has an effective date of 01-Jan-XX to 31-Dec-XX, each qualifying transaction will be summed and stored for the plan element date range. Can be used with Cumulative and Interval to Date. By using this option OIC will track the sum of each individual for each interval for the duration of the plan element. For example, if the plan element has an effective date of 01-Jan-XX to 31-Dec-XX, each qualifying transaction will be summed and stored for each interval throughout the duration of the plan element date range. Option #1 instructs OIC to group and accumulate each transactions for the entire date range of the plan element and then apply the total into against the rate table. Using the above example, the payout for each transaction will be: Total CommissionAggregate Total $75 X 5% = $3.75$75 $125 X 10% = $12.50$200 $110 X 15% = $16.50$310 $50 X 15% = $7.50$360 Option #1 instructs OIC to group and accumulate each transactions for the entire interval and then apply the total into against the rate table. Using the above example, the payout for the transaction will be: Total CommissionAggregate Total $75 X 5% = $3.75$75 $125 X 10% = $12.50$200 $110 X 15% = $16.50$310 $50 X 5% = $2.50$50 Splits Each option is mutually exclusive and can be used with any options you choose to select for Transactions. The purpose of the splits options is to tell OIC who the evaluated transaction(s) will be used against the corresponding rate table and its tiers. Assume the following rate table: 0-100 5% 100-30010% 300-9,99915% Sample Transaction of $200 No Split. This option instructs OIC to use the tier that the transaction falls against. Following the above assumptions, using this option the appropriate payout would be 10%. Total payout $20. Non-Proportional. This option instructs OIC to split a transaction into the tiers they would fall into against the rate table. Using the above example, the payout for the transaction will be ($100 X 5%) + ($100 X 10%). Total payout $15. Proportional. This option instructs OIC to split a transaction into the tiers proportionally. Using the above example, the payout for the transaction will be (($100 X $100/$100) X 5%) + ($100 X ($100/300-100) X 10%). Total payout $10.

Formula Parameters – No SplitRate Table

Transaction Amount = $400,000

Calculation: $400,000 x 5% = $20,000

Transaction Amount Percent

$0-250,000 4%

$250,000-500,000 5%

$500,000-1,000,000 5.5%

$1,000,000 – Up 7%

Presenter

Presentation Notes


Formula Parameters – Non- ProportionalRate Table


Calculation: $250,000 x 4% = $10,000 $150,000 x 5% = $ 7,500

lTotal = $17,500


$0-250,000 4%

$250,000-500,000 5%

$500,000-1,000,000 5.5%

$1,000,000 – Up 7%

Presenter

Presentation Notes


Formula Parameters –ProportionalRate Table


Calculation: ($250,000 x ($250,000/$250,000) x 4%) = $10,000 ($150,000 x ($150,000/($500,000-$250,000)) x 5%) = $4,500

Total = $14,500


$0-250,000 4%

$250,000-500,000 5%

$500,000-1,000,000 5.5%

$1,000,000 – Up 7%

150,000250,000

= 0.6

Presenter

Presentation Notes


Percent of Target Commission %

0 - 0.25 * ITD Target 5

0.25 * ITD Target - 0.75 * ITD Target 10

0.75 * ITD Target - Target 15

Country Commission %

USA 5

Japan 4

Germany 7

Percent of Quota Commission %

0 - 25 0

25 - 75 1

75 - 100 3

Units Sold Commission %

1-250 2

250-500 4

500-99999999999 6

Amount: The rate dimension is defined in quantities.

Percent: The rate dimension is defined in percentages.

Expression: The rate dimension uses previously defined expressions.

String: The rate dimension uses alphanumeric data.

License Revenue Country Product Rate

0 – 250 USA Product X 1%

0 – 250 USA Service Y 5%

0 – 250 Japan Product X 1.5%

0 – 250 Japan Service Y 4.5%

0 – 250 Germany Product X 1.25%

0 – 250 Germany Service Y 6.25%

250 - 9,999 USA Product X 4%

250 - 9,999 USA Service Y 8%

250 - 9,999 Japan Product X 4.5%

250 - 9,999 Japan Service Y 7.5%

250 - 9,999 Germany Product X 4.25%

250 - 9,999 Germany Service Y 9.25%

Revenue Amount

0 – 250

250 - 9,999

Country

USA

Japan

Germany

Product

Product X

Service Y

Multidimensional Rate Table

Four types of Rate tablesRate Dimensions

OIC Calculation Process Sequence• Revert• Classification• Rollup• Population• Calculation

Pay Groups

• Can be assigned to a Role or a Resource• This needs to be assigned for the Calculation

process to run• Each pay group is based on frequency of

payment or business units.

Pay run

• Need Payment analyst role to create and maintain the payment batches (pay run)

• Create Payment Batches• Export the Payment batches

Multi-Org Access Control Setup and Process

For OIC Responsibilities, assign the following MOAC profile options:

MO: Security ProfileMO: Default Operating Unit(MO: Operating Unit is not

required since Security Profile is defined)

Multi-Org Access Control Setup and Process

• Compensation Plan

360 Degree View

Top-Down Plan Creation

Checklists & Wizards• Plan Component Library • Multi-Level Marketing Enhancements• Export for Plan Assignment• Terminology Changes

R12 OIC New Functionality

Presenter

Presentation Notes

This TOI describes the Plan Administrator role and the new or changed features for it. This section provides a high level functional description and flow of how to set up and use the Plan Administrator role. For more detailed or technical information regarding the Plan Administrator role, or any other role please refer to the product documentation for this release. Several feature introductions and enhancements have been introduced as part of R12. The Plan Component Library provides a common starting point from which to create and maintain plan components. Creation and maintenance of compensation plans is facilitated by a 360-degree view of the plan, and a new top-down creation flow. Notes capabilities has been augmented with a hierarchical structure to allow easier tracking of changes. Search results can be personalized. Tabular information, such as plan assignments, can be exported to a comma-separated file and opened with Microsoft Excel Multi-org access control supports global compensation practices for shared service centers. Finally, terminology changes introduced in R12 will be discussed.

• New Features

Configuration Workbench

Multi-Org Access Control (MOAC)

• Changed Features

Notes

Improved Territory Integration leveraging R12 Territory Manager Capabilities

Redesigned reports

R12 OIC New Functionality

Presenter

Presentation Notes

This TOI describes the Incentive Compensation Administrator role and the new or changed features for it. This section provides a high level functional description and flow of how to set up and use the Incentive Compensation Administrator role. For more detailed or technical information regarding the Incentive Compensation Administrator role, or any other role please refer to the product documentation for this release.

Plan Element Checklists

Checklists enhance:Data Completeness UsabilityAccuracy

System validation at end of each step

Roadmap for Plan Element creation

Track progress

Presenter

Presentation Notes

Compensation plans are comprised of plan elements. In R12, a plan element checklist is provided as a roadmap for creating plan elements. The Plan Element Checklist identifies all steps required for creating the plan element and provides easy navigation to each step. Status indicators for each of the tasks help the Plan Administrator to track progress. Using the plan element checklist to create plan elements, the Plan Administrator will avoid leaving out important information. Errors with data entry are easily isolated, as the system performs validation at the end of each step.

Plan Element Checklists– The ‘Required’ field column lets the user know which steps need to

be completed– The ‘Status’ column tells the user where they are in the process– Each Area has a ‘Go To Task’ drill down with its own check-list– The ‘Checklist Key’ explains the status icons

Presenter

Presentation Notes

Compensation plans are comprised of plan elements. In R12, a plan element checklist is provided as a roadmap for creating plan elements. The Plan Element Checklist identifies all steps required for creating the plan element and provides easy navigation to each step. Status indicators for each of the tasks help the Plan Administrator to track progress. Using the plan element checklist to create plan elements, the Plan Administrator will avoid leaving out important information. Errors with data entry are easily isolated, as the system performs validation at the end of each step.

Multi-Level Marketing EnhancementsPer customer requests, Multi-level Marketing (MLM)

features have been added:

Rollup Level

A column has been added to the OIC transaction to track the level of the roll up for each transaction

Direct vs. Indirect Credit Receiver

Users can more easily distinguish if a credit is earned due to a roll up or if it was directly assigned to the resource

Plan Element processing option to calculate transactions rolled up through the Sales Comp Hierarchy

Now if users Rollup across the Sales Comp Hierarchy they have the option, at the PE Level, to calculate commission for those rolled up transactions

Presenter

Presentation Notes

In a legitimate MLM company, commissions are earned only on sales to the end-user, who is often also a distributor. Below are a couple of Incentive Plan Component descriptions and how typically MLM Rollups might occur: Baseshop overrides are overrides of managers from their subordinate non-managers, collectively called a baseshop. This is the same as any other sales organisation. Generational overrides are overrides of managers from the baseshop of managers who were previously their subordinate. Most plans compensate at least three generations of such managers. Rollup level is a field on the OIC transaction. The level number is tracked if the credit is received through the rollup function in OIC. For example, a direct credit receiver's Managers roll up level would be = 1; The Manager’s manager roll up level would be = 2, and so on. The rollup level can be used in calculating commission. Users have the Resource and the Direct Credit Receiver columns that can be displayed in Transaction based queries and reports. These two column help the user to more easily tell the difference in who the original resource (direct seller) and who received credit for the transaction via a rollup using the Sales Compensation Hierarchy. The ‘Indirect Credit’ calculation option for the Plan Element gives the user more flexibility in configuring the plan components. The user can choose to Calculate commission for rolled up transactions for all resource, for Manager type resources, or for no-one for any plan element.

Select the radio option for ‘CN_COMMISSION_ LINES’

Navigate to the Rollup Level column, then click the ‘Usage’ box then Apply

Calculation Configure Tables & Columns task

Presenter

Presentation Notes

To use the Rollup Level in an Expression for Commission calculation do the following: Go to the Configuration Workbench Calculation ‘Task’ Configure Tables and Column sub-task Search for table name like CN_Comm; select the radio option in the top table for ‘CN_COMMISSION_LINES’. In the bottom table navigate to the ‘Rollup_Level’ column attribute then check the ‘Usage’ check-box; click the Apply button This column will now be available in the expression builder.

Create a 2-D Rate table. One of the dimensions will be for the Rollup Level.

Select the Rollup Level attribute from the Commission Lines object to use in your formula as an input parameter.

Presenter

Presentation Notes

Setup a Two Dimensional Rate table to use the Rollup Level and what ever other parameter you need like attainment level. Then in the Formula, pass in the Attainment level and the Rollup Level to calculate the commission based upon these two factors. You’ll need to create two input expressions; one for the attainment percent the other for rollup level. (See the Plan Administrator presentation for Plan and plan component creation details.)

Both inputs (Attainment Percent and Rollup Level) are passed to the Rate Table.

Add both input expressions to the formula

Presenter

Presentation Notes

Now in the Formula for the Plan Element select both Input expressions (MLM Attain Rates and MLM Rollup Level) to be used for the rate 2-dimensional rate table ‘MLM Rollup Rates’‘, The rate based upon the intersection of the attainment level and rollup level is then used in the output expression to calculate the commission. (See the Plan Administrator presentation for Plan and plan component creation details.)

Data Export for Plan Assignment

Table data can be exported as .CSV

Data to export

Plan eligibility

Plan search results

Plan element search results

Payment plan search results

Presenter

Presentation Notes

Most tabular data can now be exported as a comma-separated file which can be viewed using Microsoft Excel. Compensation plan eligibility information can be exported to CSV. In addition, search results for compensation plan, plan element, and payment plan can be exported to CSV.

Tips and Tricks 1Instance Status active only after periods are open and only if the Instance status is active, comp plans can be saved.

Tips and Tricks 2No. of expressions is limited to 200 expressions unless you change the profile option FND: View Object Max Fetch Size

Tips and Tricks 3

FND: View Object Max Fetch SizeFND: View Object Max Fetch Size

You can add any custom function to OIC Lookups and It will show up in the expression builder while creating comp plans

Tips and Tricks 3 (Continued)Here is an example. Adding the CN_API.GET_SALESREP_NAME

function to the OTHER_FUNCTIONS lookup.

Tips and Tricks 3 (Continued)It shows up under Other functions in expression builder. Any packaged function can be called from the form.

Tips and Tricks 4Using Other Hierarchy, you can customize the Product Hierarchy out of box and use your custom table

Tips and Tricks 4

Tips and Tricks 5

• Commission type Plan Elements – uses transactions for calculation

• Bonus type Plan Elements – non transaction base for calculation

• Creating Dummy PE and referencing it in the next PE will make it as Commission type Plan Element.

Tips and Tricks

• Use External tables or views and map them in OIC and they can be used to create expressions.

AcknowledgementsSpecial thanks to the following people at Dell

who made this presentation possible• Steve Rivers, IT Director• Michael Clark Sr. Manager

And the following sponsors for the POC Team• Will Cornish, Sr. Manager• Sue Patti, Sr. Manager• Ken Allen, Sr. Manager• Bill Uhlenhop, Director

AcknowledgementsAnd thanks to all the members of our POC Team• Shanker Karpe• Brent Perlinger• Kalyana Elangovan• Michael Mintskovsky• Jim Cullis• R Kirubakaran• Phillip Woodruff• Dave Ackron• Sridhar Potluri

Acknowledgements

• A very special thanks to my husband Ram Ganapathy for his full support and encouragement in writing this paper

Thank you all for attending!

r12oic_oaug2009

Documents