Hexaware Technologies :Riding High! --nirmal bang,

Riding High!
Hexaware Technologies Limited (HTL) is a mid-sized IT company mainly catering to the capital markets (BFSI) and the airline (transportation) sector. It also focuses on enterprise software provided by PeopleSoft and Oracle. Recent large client wins has bought back the focus on this company which has good expertise in the niche areas. 


Investment Rationale

 Improved Revenue visibility due to large wins in the past 5 quarters

The deal wins of over $ 625 mn which HTL has gained in the past 5 quarters is commendable. HTL’s efforts of mining the existing clients in the gloomy days are paying off now reflecting in the incremental revenue streams it has earned. These long term deals give enough revenue visibility for CY12. In addition, HTL is negotiating almost 4 deals above $25mn which are in the pipeline.

 Margins moving northwards – room for further heights
EBIDTA margins have improved 812 basis points in the past 5 quarters led by drastic control in the operating costs. The company has in addition utilized its offshorablity lever in its advantage by moving almost 14% of work offshore during the same period. Currently, onsite: offshore mix stands at 53:47, utilization in early 70’s and plans to hire freshers would further aid the margins going forward. We expect HTL to report EBIDTA margins of 20% + in CY12E and CY13E.

 Proficiency in niche segments paying off
HTL earns 60% of its revenues from the Capital Markets and Travels industries and almost 30% of revenues come from enterprise solutions in terms of its service lines. In enterprise solutions, 60-65% of its revenues are from PeopleSoft where other software vendor’s focus is less.

 Guidance Revision of 20% on USD revenues for CY12E

On the back of good deals won recently, the company has revised the revenue guidance in USD terms to 20%. We feel this is a little conservative and the company can easily beat the guidance for CY12E.
Valuation & Recommendation

We expect HTL’s revenues to grow at a CAGR of 25% and adjusted profits to grow at a CAGR of 21% over CY11-CY13E. Margin improvement would remain under focus and we expect HTL’s EBIDTA margins improving by 313bps to 21.2% in CY13E from 18.03% in CY11. At CMP, the stock is trading at 10.4x and 8.6x for CY12E and CY13E respectively. On the back of improved financials and good revenue visibility, we recommend a BUY on the stock, assigning a target multiple of 11x for CY13E EPS with a price target of Rs. 147 which is a potential 28% upside.

Risks to our Rationale:

 Concentration in Discretion spending Revenues
Hexaware derives more than 50% of its revenues from Enterprise solutions and Business Intelligence and Analytics which could get affected in economic downturn. However, the recent deal wins re-affirms the revenue visibility for the company for CY12E.

 Industry Risks of wage pressures, rupee appreciation and competition
Rupee depreciation has acted in favor of the company and Industry per say. Any severe reversal of the rupee trend would affect the prospects of the firm.

 Exposure in the European Region
The company has 28.4% exposure in the European region and few of the major deals have been signed with clients in this region. Looking at the current economic scenario prevailing in the Euro zone, any delay in commencement of these deals or cancellation may impact the margins severely.

Valuation & Recommendation
We expect HTL’s revenues to grow at a CAGR of 25% and adjusted profits to grow at a CAGR of 21% over CY11-CY13E. Margin improvement would remain under focus and we expect HTL’s EBIDTA margins improving by 313bps to 21.2% in CY13E from 18.03% in CY11. At CMP, the stock is trading at 10.4x and 8.6x for CY12E and CY13E respectively. On the back of improved financials and good revenue visibility, we recommend a BUY on the stock, assigning a target multiple of 11x for CY13E EPS with a price target of Rs. 147 which is a potential 28% upside.

Hexaware Q2 net rises 48% on higher revenues

Software service provider hexaware technologies has reported a 48 per cent increase in net profit at Rs 89.03 crore for the second-quarter ended june 2012 against the same period last year.

Click here to read more…

Hexaware bets on UK, new verticals to lead mid-tier IT growth

Infosys, TCS and Wipro may be getting cautious in their outlook, but not hexaware technologies

.

After nine quarters of positive growth, the mid-tier leader is confident of a 20% year-on-year (yoy) growth in dollar revenues for fiscal 2013.

 

 

 

Multi-User Environment for Siebel Analytics/OBIEE by Alok Chowdhary on March 13, 2009 in Siebel Street

By default, only one user can edit the repository at a time, but a more efficient environment would allow developers to modify the repository simultaneously and then check in changes. Oracle BI allows multiple developers to work on objects from the same repository during group development of Oracle BI applications.

Steps for configuring Oracle BI multi-user development environment:

1)Create Project

In the Admin tool, open the Project Manager

Path:-Select Manage > Projects and then Action > New project for creating new project.

From the figure down below, you can notice two parts, in the left you can see objects that are available for the project and the right part consists of objects that can be added in projects. Select the objects from the left part that you want to add to the project and click the Add button. If you have selected the presentation catalog, all fact and dependent objects are selected in the project.

Besides the catalog, other objects such as USER, groups, Variables and initialization blocks can also be added in projects. Apart from this, you can also remove unwanted objects from project by clicking the Remove button.

2) Set up a shared network directory

Administrator needs to identify or create a shared network directory that can be accessible to developers to keep the repository file at that location. This repository is the master repository which is accessible to multiple developers to check in or check out the changes done. Developer has to point to this directory path when they use Admin tool at their machine.

Making changes in the Admin tool at the local machine to use as a multi-user development environment:

1)Point to multi-user directory:

Set up for Admin tool to point multi-user  development directory.

Path:-Select Tools > Options and then select Multiuser tab.

From the figure,  it can be seen that it is a two field, one multi-user development directory in which you have to browse the path of the shared directory where the original repository has been kept for development purposes. The other field full name  is optional,  but if the user mentions name in that field, it helps in tracking the changes made by each user and stored in the HKEY_CURRENT_USER part of registry and is therefore unique for each login on computer.

2. Check out project:-

After pointing to the multi-user development , the directory developer can check out desired projects.

To check out projects, go to path File > Multiuser > Checkout which will be only available when the multi-user environment is setup. After this, the developer is presented with a dialog box to select the master repository if one has more than one repository. Select the repository , then enter user name and password, it will navigate to select the project or projects to be imported. After selecting the projects,  user must enter the name of the new repository which will be stored in user’s local directory.

3.Admin tool task during checkout:-

During checkout , the admin tool performs the following task:-

• Makes a temporary copy of the master repository on the local machine.
• Saves local copy of projects in the new repository on the local machine.
• Saves second local copy of project in the new repository on the l
  local machine with prefix as “original”.
• Deletes temporary copy of the master repository from the local machine.

4. Changes done in metadata:-

Changes can be performed on logical tables, table definitions and logical table sources. Developers can work on the same project but if one developer deletes objects,  it will be migrated without any warning. So developers should keep in mind that modifications can affect others too.

5. Tasks done during check-in:-

The Admin tool perform the process of locking the master repository to prevent other developers from attempting to merge at the same time and copies the master repository to a local directory so that the developer will be merging with the latest or recent repository.

6. Check in changes:-

After performing modifications on the repository, the developer needs to check in changes and merge with the master repository in the shared path. Only one developer at a time can merge it. After selecting File > Multi-user >Merge local changes, the developer is shown a  dialog box having full name and the option to write comments if any and after clicking ok , the admin tool performs the process of copying master from shared and keeps it on the local machine.

After developers lock the master repository,  the merge process take place. After the merge process,  developers have to publish to the network.  Go to path File >Multi-user >Publish to Network to publish changes done in the repository.  This will finally merge local repository changes to the master repository and at the same time a local copy of the repository has been removed from the local machine.

Advantages:

• History menu option:-This option gives the detail of all the changes performed during the merge process. We can have the version history that tracks all the changes performed in the repository during the merge process.
• It helps to track the Project history.

Disadvantage:

• Multiuser develop environment is purely for repository development. Dashboards/Reports can be developed/managed by any no of users in the browser once the presentation server is up.

Tp know more about OBIEE 

Avoid Several Restarts of Siebel (SWSE) Web Server After Each Build

When changes made to the browser scripts, customized images, style sheets, help files these files are copied to the respective folders under Siebel root/ Siebel Server/ Webmaster. To synchronize the changes to the web server, The Siebel web server usually restarted.


Restarting the Siebel web servers after each build is tedious task when you have several builds from development to testing or other environments.

Alternatively you can use UpdateWebImages!

UpdateWebImages! Interesting, I will explain step by step below.

Type the below URL in the browser and hit the enter key. That’s it.
http://host:port/application/start.swe?SWECmd=UpdateWebImages&SWEPassword=WebUpdateProtectionKey
Host = The name of the Web server machine.
Port = The Web server listen port (not required if using the default port, 80).
Application = Any Siebel application hosted by this Web server (such as callcenter_enu, sales_enu, and so on).
WebUpdateProtectionKey = The unencrypted version of the Web Update Protection Key, which is defined in the eapps.cfg file by the WebUpdatePassword parameter.

To know more about Siebel Web Server

Ask the Expert 01

Question :

Hi,

I have been following your site for quite sometime and its great.
Wanted to have a clear idea on the Siebel EMail Response module.

I did go through the bookshelf which gives a very good idea but still wanted to know if there are some practical implementation done.

Requirement is that a service request or an activity needs to be created from an email.

Response :

From what i understand of your requirement, please find the following reply to your query. Once the email is triggered using the Outbound Communication Manager BS, an activity gets generated as per the Siebel vanilla functionality. The activity of Type Email-Inbound or Email-Outbound will get created provided the Email templates, Email server, Outbound Communication Manager component is configured properly.

If one wants to generate customized activity / SR post the email is triggered, then e-scripts or VB scripts have to be used. For e.g The email has to be sent to the customer on updation of customer’s demographic info. The e-script written on appropriate event(s) can be called. This code will further invoke an email Workflow (WF). After the WF has been invoked, another chunk of code/Workflow has to be invoked for generating activity / SR by creating a new record in the custom BC.

To know more about Ask the Expert