Web Content Display Web Content Display

Training Training



Name of the organization: Aon Hewitt

Address of organization: Aon center,Buliding 2,Unitech Info space,Tikri,Sector 48 Gurgaon 122001 Haryana.

Name of Manager:  Akshay Tyagi

Email id of Manager: akshay.tyagi@aonhewitt.com

Name of Project: Health and Welfare

My role in organization:

I joined Aon Hewitt as SCS(Setup Configration Specialist) in January 2015 .Aon Hewitt helps employees manage their employee benefits plans.It provides recordkeeping services to employees for their employee Defined Benefit ,Defined contribution and health and welfare plans.

SCS is the colleague responsible for configuring and testing Aon Hewitt's propiterary CBA(Core Benefit Administration) system to meet the needs of client requirements.

The SCS's uses the Test plan to perform calculations for clients to ensure that the results match what is expected.In order to do so this SCSs:


1.Execute a test plan,which they normally work with an SA to accomplish.

2.Document the results that are generated by the test plan.

3.Document any defects that occur.Typically SAs assist SCSs with this.

4.Execute regression testing,to find out what was inaccurate and discover how to repair it.

5.Updates the test needed.


If an issue requires futher resolution ,SCSs take the following steps:

1.Analyse and debug outstanding issues that have occurred.

2.Use problem-solving resources that corresponds to the concern in order to settle it.

3.Escalate to an SA or LSA when necessary.


Project Name: Health and Welfare


About the project:


Health and welfare plans are the employer sponsored palns that offer a group of employee benefits to ensure their health and well being.It also protects employee against catastrophic events.HW plans primarily provide employees access to important services during their working years and potentially in retirement.

HW plans encourages employees to have regular doctor visits to detect potential health related problems before they progress to a serious stage.Secondly employees are able to pay for their benefits on before tax basis.Benefits are more affordable when employer providedbecause a larger group of employees is covered ,each employee in the group receives a group-rate which is lower than if they receive coverage on their own.


With an HW plan:

1.Employees choose the type of coverage from an employer defined list as well as which individuals to cover(eg spouse or spouse and children).

2.Employers and employees pay for all or part of these benefits.Coverages cost values,depending on the type and extent of the coverage.

3.Employees cost are usually deducted from employees paychecks.


Technology used:


1.Core Benefit administration(CBA)


The CBA platform is used to provide health and welfare benefits to clients.Through CBA we configure the benefits to  clients.Our client's employees can enroll or check the status of their benefits.


The CBA platform uses different functions including:

1.The CBA system controls the setup of an employer's core benefits on benefit summary.

2.It is used to create,administer and publish client web content on the benefits Portal.

3.It allows employees to view current enrollment status and related messages and make updates allowed outside of annual enrollment.

4.It indicates changes that need to be made to employees records or plan/carrier information.


CBA mainly consist of the following:

  • Rapid Implementation(RI) which is used to configure client on the system.
  • Manager Self Service(MSS) which is used to create individual participants and also for testing purpose.

2.File Information Scheduling Tool(FIST)


FIST is web-based tool used to define,schedule and monitor inbound and outbound files between Aon Hewitt CBA and employer or carrier.FIST manages and maintains file interface giving support to clients.

This tool is primarily used by:

  • BeST colleagues dedicated to files implementations ,Files ongoing and Files Development Teams.
  • Files Development Team
  • System Assurance

By creating a file in FIST, a unique File ID is assigned to each of the files that will be transmitted between Aon Hewitt CBA and employer or carrier.


The files can securely transmitted through FTP account to secure connection CBA and employer/carrier.


Work Progress Details

Untill now, we have been provided training on:


1.Domain theory on various Health and welfare plans.

2.Configuring clients on Rapid Implementation(RI) which includes:

  • Creating up new clients
  • Setting their eligibility groups
  • Creating Medical and life plans
  • Benefits assignments.
  • Dependant Settings

3.Creating new participants on Manager self service(MSS) and also to perform various type of testing like unit testing and EOI testing in it .Participants are enrolled to various plans with the help of MSS.

4.An introduction to FIST(File information Scheduling Tool) and the various types of files used in CBA.


2 week Details:



4.1.1 Testing Definition


Testing is the process of evaluating an item with the intent of finding defects (differences between existing and required conditions). It is not one phase of the system development life-cycle; testing occurs in all phases. Testing is a quality control (QC) activity, and can be static (evaluation of a non-executable item, e.g. a document or code specification) or dynamic (evaluation of an executable item by executing it, e.g. a compiled software component).

4.1.2 Testing Context


The Quality Assurance context within which Testing is performed can be defined by the V-Model of Software Quality.

The V-Model provides a structured quality framework which integrates the application development and testing lifecycles throughout the development process, and ensures that both verification and validation are applied to all deliverables within a system.

It illustrates the development process, from defining benefits through converting the system into production, and helps focus on quality throughout the development process.

The foundation of the V-Model is Phase Containment - finding and fixing errors within the stage of origin - by focusing on:

  • Testing throughout the development life-cycle.
  • Early development of test requirements - concurrent with the development of application requirements.
  • Utilizing Verification and Validation techniques on key and high risk deliverables/work products to facilitate early detection of errors.

Because testing of completed applications usually results in identification of only 30-50% of application errors, these early checkpoints are key to delivering high quality applications.

4.1.3 Testing Phases


There are three primary phases of testing for HR BPO, with four secondary or sub-phases:

  1. Unit Test
  2. Integration Test
  3. Component Integration Testing (CIT)
  4. System Integration Testing (SIT)
  5. Acceptance Test
  6. Internal User Acceptance Testing (UAT)
  7. External User Acceptance Testing (UAT)

Regression testing must occur in all testing activities/phases.

All phases of testing apply both to implementation/project teams and ongoing/BAU teams.

4.1.4 Testing Activities

There are four main activities in the Testing Discipline (Plan, Design, Execute and Evaluate). The four activities apply to the overall implementation as well as to each phase of testing: Unit, CIT, SIT, and UAT. There are specific modules for each process at a unit test level, as well as a module for CIT, SIT, and UAT. Each testing activity applies to both implementation and ongoing teams.

Client Acceptance Testing


  • Specify client involvement/ activities
  • Develop UAT Test plan, including client sign off
  • Determine scope of testing effort
  • Tools: UAT Checklist; Hewitt Test Plan Template; Test Execution Work plan; Defect and Issues Log
  • Identify environments
  • Identify databases
  • Identify Access requirements


2. Design

  • Draft test cases
  • Determine Logistics (location, test environment requirements, tester ids, etc.)
  • Confirm change control process


3. Execute

  • Ensure completion of SIT, including client sign off if necessary
  • Migrate all objects to UAT environment
  • Complete client testing
  • Identify open issues and defects
  • Regression test


4. Evaluate

  • Issue tracking/reporting
  • All application changes are documented and detailed
  • Perform CM audit
  • No open Severity 1 or 2 Incidents; target closure dates for Severity 3 and 4 Incidents identified
  • Issue resolution
  • Retest/Regression testing needs
  • Develop plan to address any deferred defects, including client sign off



Testing Phases

The five phases of testing include:

  1. Unit Test
  2. Integration Test
  • Once The Client's provisions have been set up in Rapid Implementation, BeST Colleagues need to test the newly implemented provisions as a flow.
  • It evaluates all of the functionality together, including how they interface with each other. All channels should be incorporated into this test.
  • The Integration test cases originate from the client's business requirements and CBA Requirement Documents, and become the source of any future planned acceptance
  1. Regression Test

Performed to uncover new errors, or regression, in existing functionality after changes have been mad, such as functional enhancements, patches or configuration changes.

      It is done to ensure that a change such as a bug fix, did not introduce new bugs.

  1. Client  Acceptance Test
  • Conducted by BeST Colleagues and the client to accept the final system configuration and to ensure that the CBA Manager Self Service and Portal tools work as expected.
  • It provides an opportunity for clients (including both internal and external) to review the system prior to changes going live in production.
  • Alteast CAT testing should include validation of the following –

          General and Dependent Settings

          Annual Enrollment Flow and Plan availability

          Web Content Overview


          Work / life Events


All phases of testing apply to implementation and ongoing teams.

  • E. File Testing

Performed to test eligibility files, pre-load files, employer payroll files and carrier files.  Conducted by CBA System Analysts. It occurs in parallel with Integration testing.


 Testing Activities

There are five main activities in the Testing Discipline. The five activities apply to each phase of testing: unit, integration, regression, and acceptance. There are specific modules for each process at a unit test level, as well as a module for integration, regression, and acceptance testing. Each testing activity applies to both implementation and ongoing teams.

There are five main activities in the Testing Discipline. The five activities apply to each phase of testing: unit, integration, regression, and acceptance. There are specific modules for each process at a unit test level, as well as a module for integration, regression, and acceptance testing.


 3 Week details


File Implementation and      Scheduling Tool (FIST)

FIST Used to setup and schedule several different types of files, including payroll / HRIS files, depending and eligible files and carrier files.

  • Used to create, Maintain and schedule client and third party files (both inbound and outbound).
  • Files may include :

                                    Payroll/ HRIS files

                                         Dependent and Eligibility files  

                                         Carrier Files

  • Use FIST to create and edit inbound files, outbound files, custom values, expectations, and FTP accounts.
  • FIST has 2 main parts

        > Extraction

        > Customization

  1. Extraction has custom values.
  1. Customization has specification, lookup table and mapping.
  2. Layout


  • There are 2 types of environment :
  1. Production Environment
  2. Test Environment


There are mainly 3 types of files :

  1. Core – T : The basic method to extract data for outbound files. Data is extracted based on transactions or changes to those transactions. If  a transaction occurs within a certain date range, then the Core Transaction file will pull that transaction data into the file to be sent.


  1. Core – D : This type is for outbound payroll files, and pulls current election data association with payroll deductions. Core Deductions  will not pull election information if that election is elected in the future; it will only extract data that should have a payroll deduction enforced currently.


  1. Core – P : A specialty process for CBA that is used when an employee record needs to be direct billed for benefit deduction or have the deductions taken out via the pension account. This type will scan a record and determine whether or not the participant needs to have their information sent to Pension and Direct Bill. Essentially, this file is sent to evaluate whether the plan participant has enough money in their pension to cover election amounts. If so, it is sent to the pension system for processing. If not, then notification is sent to Direct Billing and Payment so they can bill the retiree.


Note : Each of these file have in turn full file and Change file.

  • PGP and FTP logs capture messages for the success or failure of the data encryption or transmission step of the automated file process.

File Life Cycle

  • Step 1 : Extracting Files from CBA database is determined by custom values.
  • Step 2 : If successfully extracted Xml document is created.
  • Step 3 : Specification document is checked for conditions to be applied.
  • Step 4 : Mapping is done using look-up tables.
  • Step 5 : Layout is made and txt document is created.
  • Step 6 : EDI Notepad is used to validate.
  • Step 7 : txt document is send to carrier through Any Client.
  • Expectations
  • Expectations are set up in FIST in order to schedule when we should extract data for an outbound file or when we should receive an inbound file.



The Plan Test is a step-by-step methodology to walk the user through the testing of the functionality (or event process flow) in question. It contains:

  • Background information on the functionality or the event flow being tested.
  • The scope of testing, which includes each task in the event flow that requires testing.
  • Requirements, used to determine what will need to be tested (test cases and test conditions)
  • A step-by-step test strategy for executing the testing process.

During the Plan Test, you are gathering information and determining your strategy for the test. You use the Test Case Creation artifact to map out the possible scenarios (test cases or populations) that will be used in your test conditions.

As an outcome of the Plan Test, you will understand the scope and strategy for the test.





Review the begin and end dates assigned to the test planning and testing sub-tasks in HRO Maestro.


Review the input artifacts (e.g., requirements, gap tracker, impact assessment, SDLC analysis and testing guides) applicable to the unit (or process).


Identify any specific challenges or exceptions (i.e., critical testing considerations) associated with the test. Document these and any client-specific considerations and exceptions in the Design Test Spreadsheet (i.e., test plan or DTS). Ensure any associated gaps have been documented in the Gap Tracker and any impacted areas have been documented in the Impact Assessment.


Determine the scope and strategy for your test. Document the testing strategy in the Design Test Spreadsheet (i.e., test plan).


Review client use cases. Make sure they are represented in the overall testing strategy during each phase of testing: unitintegrationregression, and acceptance.


If not already available, create the Test Case Creation Template



Review any assumptions included in the base test plan and evaluate whether your client deviates from those assumptions. Updates to the base DTSs will be needed if your client team deviates from the base activity process flows or if there are client-specific challenges, considerations, or exceptions that need to be adjusted for the test. Examples include:

  • Client does not offer IVR.
  • Client only has cash balance DB plans and not a FAP plan.
  • Client has multiple sources of incoming HR data which requires the testing of transfers across sources.


  • The Analysis Gap Tracker includes any tailoring or customizations required by the client team around:
  • Each unit of work in the event flow that requires testing.
  • Any assumptions, risks, or contingencies which may affect or impact the test effort.
  • All testing tools needed to execute or evaluate the test have been clearly outlined as part of the test strategy.
  • All requirements inputs used in test planning have been checked off.

Input Artifacts

  • Gap Tracker
  • Plan Provisions
  • Ongoing Interface Requirements
  • Ongoing Reporting Requirements
  • Base PCSs
  • Flagship PCS Sample (if applicable)
  • Base PCS Requirements
  • PCS Custom/Client Requirements Artifact
  • Kit Management Requirements
  • PORTAL DESIGN/Internet Requirements
  • CS Pro Requirements
  • IVR Requirements
  • Benefits Payment Document (DB only)
  • Shared Service Requirements:
  • Access Direct
  • Benefits Manual
  • Direct Billings & Payments (HM only)
  • Connections (HM only)
  • Financial Manager (HM only)
  • Provider Direct (HM only)
  • Health Plan Comparison Charts (HM only)
  • Systems Analysis—Note that systems analysis can be used as a supplemental testing input if and only if the documentation has been reviewed and formally approved by the LSA and BSM.
  • Overall Project Plan (saved to the client file on the Shared Drive)

Output Artifacts

  • Updated Design Test Spreadsheet denoting Testing Strategy (and critical testing considerations)


  • The Systems Analyst (SA), or Programmer Analyst Advanced (PAA) for batch intensive tasks such as interfaces and reporting, is responsible for all test planning.
  • The SA or PAA should reach out to the Lead Systems Analyst (LSA) and Benefits Operations Manager (BOM) with any test planning questions.