Why So Many Modules?

HTS has over 40 modular software products.  Some people ask "why so many modules when others offer just one?"  Good question.

HTS uses an object oriented, three tier design approach that allows you to manage and use the functionality that you require. 

Modularity

When you break a huge problem up into manageable chunks -- you no longer are overwhelmed. 

Understanding

It is easier to understand a smaller chunk than one huge program. 

Facilitates Change

When you need to make a change, you know exactly where to go.  Instead of wading through hundreds of pages of code, you only have to deal with a couple of pages of code. 

"Black Box" / Encapsulation Approach

With a "Black Box" / Encapsulation Approach  -- you don't have to fully understand everything they do.  You simply look at what are their inputs, what do they output, and what functionality do they provide. 

Reuse

Clearly defined modules can be reused throughout your facility.  For example, many different groups have their own inventory.  Office supplies, raw materials, work in process, finished goods, cleaning supplies, operating supplies, maintenance parts, facilities, etc.  Now one module can be easily configured so each user group can benefit from their own inventory management system. 

Combine and Migrate Different Data Sources

Many companies started with "islands of automation" and wound up with data in many different database sources.  Our modules have separate data layers that allow you to easily change the type of data source.  For example, your employee database could be Oracle, your Bill Of Materials DB2, your inventory MySQL, etc.  By using ADO.NET and a separate data layer we make it easy to connect with data in different databases. 

It also makes it easy to slowly convert old, different datasources to one common format.  Each module can be changed over time.  For example, if you have company data in five different database formats, you can initially set-up the data component of our modules for each data source.  Then as you find time, start migrating your databases over to a common platform -- you simply copy the data component of our module to a new version and change the new version to support the new database.  In some case this is as simple as reconfiguring the connection. 

Different Presentations

Some users prefer Windows Forms, some Web Forms, some compact forms (PDA, smart phone, tablets, hand helds, etc.).  By having a separate presentation layer, it is easy to convert to other forms of data presentation. 

You Get What You Want

You don't have to purchase, maintain, and work around modules that you don't want.  Two of the most annoying problems are not having functionality you need and having functionality that is always in the way of what you are trying to accomplish (having to make changes to code you do not use or having to make changes to your code for some software you don't use).  With our source code, you get exactly what you need.  No more, no less.  You can change and evolve it over time. 

Replace Modules with your Existing Systems

Most companies have investments in existing systems that they don't want to replace.  Since you have the source code to our modules, you can use the modules you want and interface to all the other systems in your company.  You can use our modules for testing and then replace them with corporate databases over time.  Or use the corporate databases until you can migrate the database over to a standard platform.