Just a quick note that service pack 1 for version 5.2 is now available for download at the TIA website.
The service pack contains a broad set of fixes as well as a significant update to the batch system.
Friday, October 31, 2008
Wednesday, October 15, 2008
Partnering for success
The TIA business model relies on strong partner alliances for implementing the TIA solution. One of the key reasons for the success of TIA can be contributed to this model, which provides the necessary scalability in terms of skills, resources and geographical spread.
In order for this model to work, we need our partners to be constantly up-to-date with our products, sales and services. We are seeking to achieve this in various ways, for instance by arranging specific events where we inform our partners about sales strategy, upcoming new product features and product development plans in general. Such an event is taking place this end of October in Copenhagen, where we expect a significant number of partners attending to learn about our plans in details.
If you are a TIA partner, please contact us if you would like to attend this event.
In order for this model to work, we need our partners to be constantly up-to-date with our products, sales and services. We are seeking to achieve this in various ways, for instance by arranging specific events where we inform our partners about sales strategy, upcoming new product features and product development plans in general. Such an event is taking place this end of October in Copenhagen, where we expect a significant number of partners attending to learn about our plans in details.
If you are a TIA partner, please contact us if you would like to attend this event.
Monday, July 7, 2008
Software localization and TIA
A key part of our strategy at TIA – and one of the things which I believe differentiates TIA from many competitors is the uniqueness of a standard solution which can be used across many geographies. The reason for this is of course the ability to customize TIA, but just as important the level of localization of the product to fit local requirements.
Localizing a product as TIA, which is targeted at business processes is much more than merely translating the software. In fact, this is just the beginning. For a vertical solution targeting the insurance business, it is a key requirement that it fits well with local standards. This includes support of common interfaces, legislation, practices etc.
In order for TIA to handle this, the solution has from the beginning been architected in such a way that it is possible to create and maintain what is called “country layers”. A country layer is a collection of features supporting the requirements in a certain country or region.
The creation and design of a country layer is not a trivial exercise. It requires deep knowledge about the local practices combined with a solid insight into TIA. We are currently expanding our work in terms of building and supporting a number of country layers. This work is being carried out by TIA and selected partners providing local knowledge and product development skills.
Another aspect is specifically how these local features are developed and implemented. There are different strategies you can apply when doing this. One strategy, which we see happening with many competitors, is the development of local features in a one-off exercise with individual customers as an integral part of the customer implementation. By doing this, the customer will typically end up with a legacy product where the implemented code is not generic. There are many concerns about this method like no re-use, no portability of the code and low upgrade possibility of the standard solution.The right approach is to build a country layer in a generic way to be used for all customers in a certain country/region. This key to this is local functionality being coordinated and built into the standard solution. This in effect means that the standard solution eventually will include local functionality for all supported countries/regions - and it will enable the use of different local features across several countries/regions within one implementation. Only by having this approach you ensure re-use and eventually a lower cost and upgradeability. This approach is what we apply at TIA.
Localizing a product as TIA, which is targeted at business processes is much more than merely translating the software. In fact, this is just the beginning. For a vertical solution targeting the insurance business, it is a key requirement that it fits well with local standards. This includes support of common interfaces, legislation, practices etc.
In order for TIA to handle this, the solution has from the beginning been architected in such a way that it is possible to create and maintain what is called “country layers”. A country layer is a collection of features supporting the requirements in a certain country or region.
The creation and design of a country layer is not a trivial exercise. It requires deep knowledge about the local practices combined with a solid insight into TIA. We are currently expanding our work in terms of building and supporting a number of country layers. This work is being carried out by TIA and selected partners providing local knowledge and product development skills.
Another aspect is specifically how these local features are developed and implemented. There are different strategies you can apply when doing this. One strategy, which we see happening with many competitors, is the development of local features in a one-off exercise with individual customers as an integral part of the customer implementation. By doing this, the customer will typically end up with a legacy product where the implemented code is not generic. There are many concerns about this method like no re-use, no portability of the code and low upgrade possibility of the standard solution.The right approach is to build a country layer in a generic way to be used for all customers in a certain country/region. This key to this is local functionality being coordinated and built into the standard solution. This in effect means that the standard solution eventually will include local functionality for all supported countries/regions - and it will enable the use of different local features across several countries/regions within one implementation. Only by having this approach you ensure re-use and eventually a lower cost and upgradeability. This approach is what we apply at TIA.
Thursday, June 12, 2008
IUG report #2
After spending two days in Riga with customers and partners I have a very good feeling about where TIA is going as a company as well as a product.
Delivering a conference with broad content focusing on the TIA solution was a deliberate choice from our side in TIA. Considering the feedback we have received so far it was a right one.
During the two days TIA employees delivered presentations describing new features relating to insurance specific processes as well as new technology advances for our Service Oriented Architecture. Based on the very positive reactions from the audience during the sessions, we definately believe we are moving in the right direction and doing the right things for partners and customers.
If you were in Riga, let me know your comments and thoughts as comments and stay tuned to my blog, which in a near future will have new topics around localization as well as insurance specific features.
Delivering a conference with broad content focusing on the TIA solution was a deliberate choice from our side in TIA. Considering the feedback we have received so far it was a right one.
During the two days TIA employees delivered presentations describing new features relating to insurance specific processes as well as new technology advances for our Service Oriented Architecture. Based on the very positive reactions from the audience during the sessions, we definately believe we are moving in the right direction and doing the right things for partners and customers.
If you were in Riga, let me know your comments and thoughts as comments and stay tuned to my blog, which in a near future will have new topics around localization as well as insurance specific features.
Thursday, May 29, 2008
IUG report #1
The 7th annual TIA International User Conference has kicked off in Riga with presentations by the chairman of the board, Lars Lysdahl, CIO Alm Brand, Evalds Trucksans /IT and Operations Director AAS Balta and finally Morten B Stener, CEo Tia Technology who is currently speaking.
With a record number of participants of 180 people the scene is set for two very interesting days.
Lars Lysdahl opened the conference commenting on the past year seen from a customer and user group perspective. Some of the things Lars mentioned was focused at making this a fresh start with increased interaction between the user group and TIA technology in terms of product feedback and new development. The coming year will be dedicated to an effort revitalizing the regional user groups and strenghtening the community.
Evalds trucksans gave a very good introduction to Balta, the leading insurance company in the area and a user of the TIA solution. Evalds also gave a good insight into Latvia demographics and the historic perspective of the 800 years old town in Riga.
Morten Steiner is currently speaking giving an overview of TIA Technology's strategy, perspectives on focus areas and a general welcome to the TIA customers and partner.
There is no doubt that people are ready for more information and two exciting days. Stay tuned for further updates from the conference as we move forward.
With a record number of participants of 180 people the scene is set for two very interesting days.
Lars Lysdahl opened the conference commenting on the past year seen from a customer and user group perspective. Some of the things Lars mentioned was focused at making this a fresh start with increased interaction between the user group and TIA technology in terms of product feedback and new development. The coming year will be dedicated to an effort revitalizing the regional user groups and strenghtening the community.
Evalds trucksans gave a very good introduction to Balta, the leading insurance company in the area and a user of the TIA solution. Evalds also gave a good insight into Latvia demographics and the historic perspective of the 800 years old town in Riga.
Morten Steiner is currently speaking giving an overview of TIA Technology's strategy, perspectives on focus areas and a general welcome to the TIA customers and partner.
There is no doubt that people are ready for more information and two exciting days. Stay tuned for further updates from the conference as we move forward.
Tuesday, May 27, 2008
User Group Conference in Riga this week
As this is written most people at TIA is putting the final touch on the preparation for the 2008 user group conference in Riga. Some of us have already departed for Riga and the rest will follow tomorrow wednesday. We are very much looking forward to two exciting days packed with content about past, present and future of the TIA solution and community.
I will take this opportunity to remind you of the newly established discussion forums at Goggle Groups (http://groups.google.com/group/tia-community) where we have prepared a forum for you to enter questions, comments, viewpoints etc. around the TIA solution and the conference in particular. TIA participants will monitor the discussions and reply as relevant.
In Riga we are announcing several new initiatives relating to the TIA solution - if you are participating you will definately get the opportunity to provide feedback and input for future development and enhancements to the solution.
Friday morning I will be presenting the keynote for TIA product strategy and throughout Thursday and Friday there will be lots of presentations detailing existing and future feature areas of TIA.
For those not present in Riga, stay tuned to this blog, I will certainly try to find time to report from the conference during the two days.
See you in Riga!
I will take this opportunity to remind you of the newly established discussion forums at Goggle Groups (http://groups.google.com/group/tia-community) where we have prepared a forum for you to enter questions, comments, viewpoints etc. around the TIA solution and the conference in particular. TIA participants will monitor the discussions and reply as relevant.
In Riga we are announcing several new initiatives relating to the TIA solution - if you are participating you will definately get the opportunity to provide feedback and input for future development and enhancements to the solution.
Friday morning I will be presenting the keynote for TIA product strategy and throughout Thursday and Friday there will be lots of presentations detailing existing and future feature areas of TIA.
For those not present in Riga, stay tuned to this blog, I will certainly try to find time to report from the conference during the two days.
See you in Riga!
Saturday, May 17, 2008
OFF-SHORING; would you do it?
This week I went to Bangalore, India, to better understand aspects of off-shoring maintenance, development and test work within a software development team.
Bangalore is, as you may know, a central hub for a large population of well-educated, well-trained and ambitious engineers within software development.
In TIA we are considering how to tap into this in relation to our development work and not at least maintenance of the released versions.
Arriving at Bangalore it is clear that India is nowhere near anything like the small country of Denmark, from where TIA origins. The Indian population is huge, the chaos (at least in traffic as I saw it) quite overwhelming, but you also get the impression, that these are people who wants to achieve a lot. Ignoring the occasional cow that disturbs the flow of traffic, the strategy of the Indians seems to be to always look for the best way of moving forward and then just go. Every inch of asphalt is being used. The infrastructure of Bangalore still is leaving something to be wished for, but I did not see any real serious jams through the intersections…
The visit for me was a confirmation, that if you select the right partner you will not just get access to a pool of resources; there is a good chance that you may even learn a thing or two. The operations we saw was certified at CMMi level 5, had several thousand engineers residing in the buildings and hired another thousand people across it’s locations in India each month.
The point of this is that when considering using off-shoring resources it may actually not be a question of whether they are up to the task, but whether you are.
Previously the word has been that Indian IT resources may be technically good, but did not know posess any domain knowledge. As far as I can tell even this is quickly changing. Partly because specific domain knowledge is fast being built up through on-the-job training working with domain issues – also within Insurance. And partly because it seems to be getting increasingly more interesting for Indian born people who have been living and working abroad for many years, to return to their native country; and with that – bringing back strong experience and domain skills.
Off-shoring any work requires that you start with realizing you have to be very structured with your requirements. You should know and describe exactly what you need. Over the last 20 years I don’t think this has been the most popular way of developing software for many programmers. What the heck – let’s talk to the customer and write the code – it’s way more fun than writing documents. Well - I certainly understand why programmers would prefer to spend time writing code as opposed to writing documents. I actually think we should work hard to let them do just this – writing code. Which again basically means that we should have someone else writing the requirements specifications! And those guys need to understand the business. Being more strict and structured in the requirements work is a good thing whether considering off-shoring or not. But if you want to send work abroad and work with people trained and working at a CMMi level 5 you better be good at it.
Another aspect I was interested in was the approach around testing. In India testing seems to be just a prestigious career path as programming, with several skill levels from junior test engineers to highly esteemed test architects. This is definitely hard to find in the Nordic region, where it seems that many people find testing a second rang discipline. From my experience, there is absolutely nothing second rang about testing highly complex business solutions – especially within the Insurance industry. This requires a solid technical background mixed with a passion for quality, building and using the right toolsets and finding those highly costly bugs in the products.
My conclusion from the short visit to India is that we should strive to be able to tap into this pool of resources. And we should use it as a way to improve our own internal processes and turn software development even more into a predictable process. One where creativity is applied at requirements and design time, but not to actually getting the things coded, tested and brought to life. The latter are disciplines where you do not need creativity but predictability. And in the end this is what I believe customers are looking from their vendor. Predictable features, at a predictable time, in a predictable quality. And so – it’s all about predictability.
At TIA we will be using off-shoring going forward – would you?
Bangalore is, as you may know, a central hub for a large population of well-educated, well-trained and ambitious engineers within software development.
In TIA we are considering how to tap into this in relation to our development work and not at least maintenance of the released versions.
Arriving at Bangalore it is clear that India is nowhere near anything like the small country of Denmark, from where TIA origins. The Indian population is huge, the chaos (at least in traffic as I saw it) quite overwhelming, but you also get the impression, that these are people who wants to achieve a lot. Ignoring the occasional cow that disturbs the flow of traffic, the strategy of the Indians seems to be to always look for the best way of moving forward and then just go. Every inch of asphalt is being used. The infrastructure of Bangalore still is leaving something to be wished for, but I did not see any real serious jams through the intersections…
The visit for me was a confirmation, that if you select the right partner you will not just get access to a pool of resources; there is a good chance that you may even learn a thing or two. The operations we saw was certified at CMMi level 5, had several thousand engineers residing in the buildings and hired another thousand people across it’s locations in India each month.
The point of this is that when considering using off-shoring resources it may actually not be a question of whether they are up to the task, but whether you are.
Previously the word has been that Indian IT resources may be technically good, but did not know posess any domain knowledge. As far as I can tell even this is quickly changing. Partly because specific domain knowledge is fast being built up through on-the-job training working with domain issues – also within Insurance. And partly because it seems to be getting increasingly more interesting for Indian born people who have been living and working abroad for many years, to return to their native country; and with that – bringing back strong experience and domain skills.
Off-shoring any work requires that you start with realizing you have to be very structured with your requirements. You should know and describe exactly what you need. Over the last 20 years I don’t think this has been the most popular way of developing software for many programmers. What the heck – let’s talk to the customer and write the code – it’s way more fun than writing documents. Well - I certainly understand why programmers would prefer to spend time writing code as opposed to writing documents. I actually think we should work hard to let them do just this – writing code. Which again basically means that we should have someone else writing the requirements specifications! And those guys need to understand the business. Being more strict and structured in the requirements work is a good thing whether considering off-shoring or not. But if you want to send work abroad and work with people trained and working at a CMMi level 5 you better be good at it.
Another aspect I was interested in was the approach around testing. In India testing seems to be just a prestigious career path as programming, with several skill levels from junior test engineers to highly esteemed test architects. This is definitely hard to find in the Nordic region, where it seems that many people find testing a second rang discipline. From my experience, there is absolutely nothing second rang about testing highly complex business solutions – especially within the Insurance industry. This requires a solid technical background mixed with a passion for quality, building and using the right toolsets and finding those highly costly bugs in the products.
My conclusion from the short visit to India is that we should strive to be able to tap into this pool of resources. And we should use it as a way to improve our own internal processes and turn software development even more into a predictable process. One where creativity is applied at requirements and design time, but not to actually getting the things coded, tested and brought to life. The latter are disciplines where you do not need creativity but predictability. And in the end this is what I believe customers are looking from their vendor. Predictable features, at a predictable time, in a predictable quality. And so – it’s all about predictability.
At TIA we will be using off-shoring going forward – would you?
Subscribe to:
Posts (Atom)
