As planned, we released the TIA solution version 6.0 on March 31st 2009. The software and other deliverables are ready for download through www.tia.dk for customers and partners.
This represents a significant milestone for us at TIA Technology and a leap ahead in terms of the Service Oriented Architecture we are introducing with version 6.
With the new release and subsequent releases 6.1 and 6.2, customers will benefit from a modern service oriented architecture which fit into a service infrastructure in order to simplify integration and customization of the TIA solution.
This will in turn lead to reduced cost for customers who want to plug TIA into an existing IT infrastructure and at the same time significantly reduce the time to market for new P & C business initiatives and products.
At TIA we are continuing to evolve the solution with new planned features for version 6.1 and 6.2 as well as the delivery of the entire service catalog, which is documented and described in detail with release of version 6.0.
At our upcoming customer seminar in Copenhagen, May 28-29, we will be presenting version 6.0 together with key messages about the future roadmap and plans. Included in that is several keynotes with focus on our customers and how they can expand through increased effectiveness and how we at TIA are dedicated to continued predicatability in or market offerings whilst maintaining agility to deliver immediate value in the current market conditions.
See you at the International User Group meeting, Copenhagen May 2009.
Friday, April 24, 2009
Wednesday, February 11, 2009
Version 6.0 progress report
With my first blogpost in 2009 I would like to send greetings to all my readers from a currently snow covered Copenhagen, Denmark. It's been a while since my last post, which primarily is caused by the fact that we are busy with the final stages of the upcoming version 6.0 as well as exciting new customer opportunities.
Currently the development team at TIA is in the stabilization phase of version 6.0 which means we are system and integration testing the new features and the SOA arhitecture and completing the upcoming service catalog. We have completed the first test pass with succes and is currently fixing the remaining bugs found during this. Subsequently new test passes are planned before release currently slated for end of march.
Currently the development team at TIA is in the stabilization phase of version 6.0 which means we are system and integration testing the new features and the SOA arhitecture and completing the upcoming service catalog. We have completed the first test pass with succes and is currently fixing the remaining bugs found during this. Subsequently new test passes are planned before release currently slated for end of march.
Version 6.0 introduces a new Service Oriented Architecture as well as numerous application enhancements and features including a new module for complaints management. We are looking forward to presenting this and much more at our international user group conference - this time to be held in Copenhagen in May.
In parallel with finalizing the new release, we have begun the envisioning phase for what comes next. With that, we are encouraging our customers and partners to provide feedback and ideas for new features, modules, enhancements etc. Let us know what you belive it's important we focus on through www.tia.dk, comment to my blog, by phone or mail.
Thursday, December 4, 2008
TIA Newsletter
The December edition of the TIA customer newsletter was just sent out to subscribers. If you would like to receive the newsletter, please send an e-mail to support@tia.dk and we will add you to the distribution list.
The newsletter contains various information about the TIA product, company and community in general.
Thursday, November 6, 2008
Configuration management
I'd really like a bit more feedback from the TIA community on my blog postings. Sometimes I am wondering if anyone is actually out there :-). I did see some of you on our International Partner Symposium Thursday/Friday last week, but there has to be more of you with an opinion!
To stir things up a bit - let me introduce a pretty interesting topic - configuration management.
In TIA we have the Workbench. This is a tool designed for many things (maybe too many actually). Among other things we are currently using it internally to manage the source code and configuration management of our releases.
Now - my question is - who amongst our customers and partners cares about the workbench? if so - what are you using it for - managing source code, customization and deployment?
Right now we are having many discussions internally in TIA about the Workbench and configuration management in general. Partly because we are growing significantly in terms of people involved in development, and partly because new Java components (other than PL/SQL object) are being introduced (which not necessarily are closely related to the Workbench).
What are your thoughts and comments to this topic? Do you care about the Workbench? Please post your comments to this article...
To stir things up a bit - let me introduce a pretty interesting topic - configuration management.
In TIA we have the Workbench. This is a tool designed for many things (maybe too many actually). Among other things we are currently using it internally to manage the source code and configuration management of our releases.
Now - my question is - who amongst our customers and partners cares about the workbench? if so - what are you using it for - managing source code, customization and deployment?
Right now we are having many discussions internally in TIA about the Workbench and configuration management in general. Partly because we are growing significantly in terms of people involved in development, and partly because new Java components (other than PL/SQL object) are being introduced (which not necessarily are closely related to the Workbench).
What are your thoughts and comments to this topic? Do you care about the Workbench? Please post your comments to this article...
Friday, October 31, 2008
5.2 Service Pack 1 released
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.
The service pack contains a broad set of fixes as well as a significant update to the batch system.
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.
Subscribe to:
Posts (Atom)
