Saturday, June 27, 2009
Mobile Field Service Applications are coming into increasing demand. The practice of Field Service Management (FSM) (or Field Force Automation (FFA) or Field Force Management (FFM) as it is sometimes called) involves optimizing business processes that provide on-site repair, installation, replacement and other services. Building custom field service applications rather than using off-the shelf solutions may be necessary for some businesses where proprietary processes and organizational structure make other solutions unfeasible. Mobile Field Service applications are typically deployed on Windows Mobile devices, however, iPhone, Blackberry and other devices are sometimes used as well. Programming of Custom Field Service Management software is often developed by enterprise IT departments or outsourced to system integrators and custom software houses.
As Gartner suggests, "Accelerated business demand to improve field service execution will favor two types of software suppliers: those with multiple application components and an underlying process design tool, and best-of-breed vendors with strong functionality, whose software is service-oriented architecture (SOA)-compliant or delivered using a software-as-a-service (SaaS) model. These capabilities enable the best-of-breed vendors to fit logically into (and more readily integrate with) a service management suite." The reason Gartner emphasizes service-oriented architecture so heavily here, in my view, relates to the nature of FSM software and not just Gartner's penchant for SOA programming. Because of the wide range of program requirements and unique proprietary dimensions of FSM software needs within an enterprise, Gartner correctly sees a need for extensive customization.
When building custom field service applications, it is important to consider the basic functionality and architecture of field service applications as well as the optimal development methodologies for establishing proprietary advantage through custom software development and service-oriented architectures.FSM requires development tools capable of creating Rich Internet Applications (RIA) for PCs and mobile devices.
Field Service Management: Functional Requirements Overview
FSM systems optimize business processes and manage information connected with on-site service. From a process viewpoint, the basic FSM process usually begins with a Service Request. The incoming service requests are matched against the available service staff and equipment in the Routing/ Dispatch process. Once deployed to the field, the On-Site Service itself occurs, in many use cases, field-based access to knowledge resources are involved. Inventory Processes involve management of products, replacement parts and supplies and may also incorporate cross-selling or up-selling methods. The Close Work Order process is a key milestone and trigger in FSM. Time Accounting, Billing and Collections typically follow the close of the work order. Sometimes, Scheduled Service Calls, additional on-site selling or appointments for follow-up visits are made at the conclusion of a job as well. The existence of warranty requirements or Service Level Agreements may affect process requirements as well.
Looking at the business benefit / functionality matrix as a functional tree, one can see the major branches as a) Build Customer Loyalty, b) Increase Revenues, and c) Reduce Costs.
FSM will Build Customer Loyalty by improving response times, standardizing service procedures, normalizing customer service policies, increasing first-call issue resolution, and enhancing availability of product, service and customer knowledge in the field. Service calls often begin with an initial sense of dissatisfaction on the part of the customer. Goof FSM can create a customer recovery culture wear the focus is on creating a positive customer experience that wins-back customers, building loyalty and a "customer-for-life" brand loyalty.
FSM will Increase Revenues by improving the efficiency of field service processes to capture overlooked service revenues; facilitating cross-selling of services and related products; and leveraging service excellence as a strategic differentiator and business driver. Customer loyalty lays the groundwork for enhanced revenues but it is not tantamount to the same thing. A good FSM system will guide service personnel through a business process that incorporates selling, winning of new appointments, full completion of prior purchase and service commitments, and procurement of profitable service-level agreements.
FSM will Reduce Costs by creating more efficient business processes, increasing productivity of field personnel, improving control of assets, and reducing duplicated effort. Components of efficiency come through elimination of duplicated effort, tightest possible coordination of resources, and improved availability of information. It is often said that you can't expect what you don't inspect. A key component of process efficiency can often come through the application of geo-spatial information management. Geo-spatial information makes possible more efficient routing, tighter scheduling, and better deployment of human resources.
A detailed functional specification for FSM will include functionality related to: centralized administrative and management functions; geo-spatial functional requirements; service management dashboard and business intelligence requirements; and mobile field service functional requirements. Each business will have uniqueness in its products, service procedures and organizational structure that drive needs and requirements for unique internal and customer facing processes and capabilities of the FSM system.
For Additional Information
Magic Software Enterprises and our business partners are experienced in developing custom field service business applications and extensions for customers seeking best-in-class service capabilities and business efficiencies. For additional information on how services based on the uniPaaS application platform can facilitate the development of FSM systems, please contact us at firstname.lastname@example.org.
Tuesday, June 23, 2009
The need for a workforce skilled in RIA development is creating demand for Rich Internet Application training in a variety of RIA development languages and platforms. With something like 360,000 application programmers in the United States alone and with RIA one of the hottest job growth areas in the IT industry, you can be sure that tens of thousands of jobs -- new highly-paid jobs -- will open up that require RIA programming skills over the next few years. Within a decade, 100,000 programmers with RIA development skills will be needed. The problem as I see it, is that with the most mainstream approaches, the toolsets and skillsets required for RIA are needlessly complex and fractured.
So I think many developers will consider it very good news that free RIA developers training for uniPaaS is now available online at the Magic Software Enterprises "Magic University" Computer-Based Training center. Smart IT departments will get there teams trained as uniPaaS developers and avoid the inevitable shortages of programmers, system architects and programmers with the multiple skillsets needed to produce coherent RIA applications.
According to the course description: The Getting Started with uniPaaS Rich Internet Application course is intended to teach the basics of programming with uniPaaS and Rich Client. The primary goal of the self-paced training is for the student to build a basic Rich Internet Business Application. When the course is completed, the student will have finished a course project which is a training application that was developed specifically for the course. By working toward the completion of the course project in a hands-on manner, the student learns the fundamentals of how uniPaaS operates and how to program in uniPaaS.
This is no lightweight online training session, however. The course contains 24 chapters presented in logical order, progressing from simple tasks to advanced concepts. To be successful you should really concentrate on the hands-on activities within the course. By working through the sample and practice exercises, you will discover uniPaaS from A to Z as it relates to Rich Internet Applications.
With this self-paced training course, you will be preparing yourself with the skills needed for RIA development of business applications. Unlike other approaches, you can be productive more quickly and develop applications in a self-sufficient manner. here is what you can expect:
1. Learn the fundamentals of uniPaaS and how to get the best out of uniPaaS.
2. Become familiar with the uniPaaS Studio interface.
3. Get to know the uniPaaS wizards and utilities.
4. Understand the uniPaaS concepts.
5. Understand the uniPaaS standards.
6. Create a basic uniPaaS business application that:
- Has a full GUI interface.
- Works with an SQL database.
- Exhibits one-to-one and one-to-many data source relationships.
- Produces reports.
2. uniPaaS Studio Interface
3. Your first program
4. Data Manipulation
5. Data Validation
6. Setting Initial Values
7. Controlling the Form's Appearance
8. Viewing Data Source Content
9. Object Data Centralization
10. Application Engine Concept
13. Conditioning Block of Operations
14. Repository Manipulation Tools
15. Find Reference Utility
16. One to One Data Relationship
17. Selecting Data from a list
18. One to Many Data Relationship
19. More about the Deployment Engine
21. Complex Reports
22. Processing Data in Groups
24. Application Deployment
One of the clear differences with uniPaaS is its metadata driven approach to development. I think this is one of the reasons why uniPaaS does not require an additional scripting tool. When everything is based on metadata originally, in the core of the application platform, engine and design, then there is no need to recreate the alphabet to adjust to new requirements such as RIA deployment. Both the architecture and the development paradigm of uniPaaS are metadata centered and so this allows for tremendous forward migration of business logic and appropriate simplification of the development task.
Monday, June 22, 2009
- The ubiquity of broadband Internet access.
- The fact that time spent on the Internet exceeds time watching TV in the highly coveted younger demographic, and is nearly equal in the population as a whole.
- Explosive increase in Web 2.0 sites and usage.
Yativ says that with the current "Web 2.0 frenzy", surfing the web has been replaced by Googling, Twittering and Facebooking. Regardless of why the use of the Web is changing, it is impacting how new entrants into the workforce think and react to business software and is therefore creating a huge need for Rich Internet Applications in business.
Clearly, business users are driving the demand for RIA in business. Properly implemented, RIA can help IT departments as well. RIA allows access to enterprise application data and functionality via alternative interfaces and reduces the number of technologies needed in the organization not to mention the required skill-sets needed.
Yativ showed how RIA replaces outdated technologies and reduces project and budget risks as it extends Enterprise Applications to business users. He also mentioned the benefit of Business Process Automation (BPA) via RIA interfaces as a way to automate business processes. Presenting information in the context of relevant business processes and in accordance with users' roles was also mentioned. Yativ sees all of this as part of a more Service Oriented IT Delivery focused on business needs.
A key concept introduced by Yativ was "Time to Cloud." Reducing the time needed to create Rich Internet Business Applications will result in greater "ROEI" or "return on existing investment" a notion that Yativ says is far more important in today's economy than ROI. Clearly, Yativ's presence at the AJAXWorld RIA Conference landed like a tidal wave at the event with a business oriented message for RIA development that was well received. uniPaaS has arrived.
Tuesday, June 16, 2009
With uniPaaS 1.8, you can expand your IT offering by supporting Windows Mobile devices alongside stationary desktops. Smartphones have become enterprise-class, making this a top 2009 priority for many IT departments and a key part of their IT strategy. With the metadata-centered productivity principles of uniPaaS, you can now easily produce highly interactive mobile applications. Existing Magic applications can be upgraded to uniPaaS and deployed as Windows Mobile applications. Most of the changes required to your application will obviously be in the graphical user interface. New applications destined for Windows Mobile can be quickly generated from the data table structure you design for your application.
As Michael Singer and I have pointed out in many previous webinars, developing mobile applications with uniPaaS is very similar to developing RIA for desktop display. Obviously, the main difference between desktop RIA and Mobile RIA is the consideration of the mobile devices’ viewing area and the expected user experience, such as touch screens and styles, and the deployment methodology. The new documentation for uniPaaS 1.8 highlights a number of important considerations.
First, there are a few prerequisites you should take into consideration. RIA applications require that you install the .NET Compact Framework and the Smart Device Framework on the mobile device. The Rich Client Deployment Builder generates an HTML that contains links to these framework files for easier installation. This means that you can simply browse the mobile device to the HTML file and install everything needed from there. Once the installation completes, the browser is no longer needed. Direct installation to the mobile device is also possible by following instructions that came with the device.
The RIA development paradigm for Windows Mobile is similar to the RIA development paradigm for other Windows versions; with these caveats: mobile devices have smaller screen sizes. Consequently, navigation is more complicated. Applications screens need to be designed to account for the much smaller "real estate" of the mobile device. Because mobile devices have unique screen resolutions, use of placement is recommended.
For the popular QVGA screen format, it is recommended to use Microsoft Sans Serif 8 font in the form properties. In addition, a width of 49 and height of 20.5 is ideal.
You should also keep in mind that mobile devices perform more slowly than desktop PCs. Good application design will find the right balance between client side operations (where the performance is slower) and server side operations (whose results require communication time and consume bandwidth). Try to avoid approaches that push large amounts of data to the client or call on the mobile client to perform extensive calculations. The good news is that bandwidth is improving all the time, with megabit throughput levels reliably available through networks such as WiMAX, EV-DO Rev A, and HSPA.
Keep in mind that the .NET Compact Framework does not include all of the functionality of the .NET framework. You will see that Mobile applications work differently. For example, the main menu opens from the bottom of the screen up in a mobile application. If only two options are possible in a menu, the items are displayed in smartphone style with the first item on the left and the second on the right side, both selectable by the corresponding smartphone key. I won't get into all the differences between .NET and .NET compact here, but you should look carefully at the uniPaaS Mobile Deployment – Supported Properties page in the uniPaaS documentation contained in the help file.
A new uniPaaS function called IsMobileClient allows you to see whether or not the client is a mobile device or not. In this manner, you can optimize your application to perform differently for mobile devices and desktop devices. Since you will have designed all of your underlying business functions using components, this really only effects the user interface layer of your application. You can use this function, for example, if you need to dynamically select a form suitable for a mobile device, or to process some logic differently based on the fact that the user is known to be mobile.
There are many, many more improvements in uniPaaS 1.8, including of course support for the use of any .NET control or assembly within your uniPaaS application. You can upgrade the look and feel of your Rich Internet Application by directly placing new .NET controls into your RIA user interface. You can also enhance the functionality of your RIA by integrating any .NET assembly. We will take a much closer look at this and other features of uniPaaS 1.8 in a future article.
Friday, June 12, 2009
I use the CEO's method of picking software development tools. I pick one that gets you to the end quickest. I don't care what everyone else uses, or whatever Microsoft is selling, or even what your IT guys want. There is only one criterion: the largest amount of software created in the shortest amount of time. Period.
That tool is [uniPaaS] by Magic Software Enterprises. It is, by far, the most productive software development tool available. I can almost guarantee that your IT department will not like this tool. But for minimizing risk and cost, it is the best choice on the market today.
I have solutions using this tool running in life insurance companies across the country, managing over $50 billion in assets.
-- Art Pennington, the Predator, Profit Research Institute, 2008.
It is never easy to put into words why uniPaaS leaves other approaches to application development so far behind. You simply have to spend a few days learning what it can really do to truly understand the "Power of Choice" as Magic's marketing team calls it.
Some of the keys to uniPaaS productivity principles derive from the fact that it is:
- Repository Based
- Task Oriented
- Event Driven
- Reusability Optimized
- Inheritance Principled
- Technology Agnostic
- Internally Debugged
- Team Ready
When I talk to IT analysts about uniPaaS, they focus in on its metadata-driven approach to application development. I am certain that those of you who program with uniPaaS on a daily basis could find even better ways to describe the essence of uniPaaS productivity. But as I have been told so many times when I ask real developers why uniPaaS is the most productive application platform on the market today, "it just is."
The results, at least, are hard to argue. As Pennington states:
Or in other words, it just is.
Just by eliminating inefficiency you can:
- Double pre-tax earnings
- Achieve a 33% increase in ROE
- Achieve a 50% increase in ROA
Thursday, June 11, 2009
As younger workers used to social media and other Web 2.0 dynamics enter the workforce, pressure will increase on mainframe IT organizations to enhance and extend their applications in a manner that makes them look and act like Web 2.0 applications. Not to mention the demand for mobile access to the same core business functions.
While uniPaaS is an ideal RIA development tool for Windows, Linux, UNIX and IBM i operating systems, the uniPaaS server itself does not run on the mainframe. In a post on my JD Edwards integration blog, I discussed Mainframe Integration Patterns that can be used with iBOLT. I represent the same discussion here, but in the context of creating uniPaaS RIA extensions for mainframe applications:
When using the uniPaaS application platform to meet the needs of RIA and Windows Mobile users, it will be necessary to find the right point of access to the mainframe. Challenges to be considered in mainframe integration include fundamental differences between systems such as EBCDIC versus ASCII text character set encoding. Finding metadata information about file structures is also fundamentally different between mainframe and other systems. On the mainframe, most of the programming is performed in COBOL and data is defined and contained in the COBOL copybook. Often, the copybook is the only source of metadata as well. In addition, consideration must be given to whether processing on the mainframe occurs in online processes, batch processes or some combination.
Extending a mainframe application by adding new RIA clients will cause the application architect to consider whether the application requires synchronous real-time, semi-synchronous near real-time or asynchronous batch methods.
Mainframe database adapters. A database adapter connects directly to the mainframe database and polls for changes in the database or responds to database triggers. These adapters can normally read, write, erase and update data in the mainframe database as well as deliver the mainframe data via certain protocols. Database adapters are very powerful and low-level solutions but have the fairly significant disadvantage of requiring the integration architect to have extensive knowledge of the database structures used and the application processes. While reading from a database is less problematic, writing directly to a database is problematic and could even void vendor support obligations for off-the-shelf software.
Mainframe ODBC adapters. Another approach is to use an ODBC driver, such as the one built-in to the SNA server or one of many available from third-party software vendors. The ODBC driver has the advantage of being more widely accessible by third-party software vendors, but in the end has the same fundamental limitations or risks associated with direct database adapters or access.
FTP. File Transfer Protocol (FTP) uses TCP/IP and provides a way to transmit files between diverse systems including mainframes, Linux systems, IBM i, UNIX systems and Windows servers. On IBM mainframes, the z/OS operating system includes capabilities for both get and put commands to transfer files. Serious limitations exist for FTP based integration, however: 1) The amount of parsing required to get to the relevant data is often extensive. 2) Security exposures are not trivial and require painstaking attention. 3) FTP is resource inefficient by requiring a separate data connection for each file transferred. 4) Parsing of the FTP directories is also complex. 5) For high volume integration requirements, managing all of the FTP files can become problematic.
Proprietary APIs. Proprietary APIs may at first seem attractive based on the specificity of their integration to a specific application. This may also be a point of weakness, however, as a great deal can be invested in terms of licensing and labor to make these APIs work and they are essentially single purpose. If you later find that you need to extend a different RIA application, you are back to the drawing boards in you search for the right integration pattern. A better approach would seem to involve a generalized integration solution on both the mainframe side and the non-mainframe side of the integration scenario.
3270 Emulation. Another option for mainframe integration is 3270 emulation. Clearly this is a strong candidate for RIA extension as it provides entry to the user interface itself. Adapters are available that will publish a secure Web service that enables bi-directional communication with mainframe systems and applications via the user interface stream known as 3270. The advantages to this approach are the relatively small amount of integration work required on the mainframe side. An expert user can spend a few hours training the emulator to find the right workflow to reveal the data or conduct the transactions and other I/O needed. However, the integration possibilities will be limited to those provided by the application to the user. If there is a need to go outside of these limitations, then this might not be the best integration pattern. In addition, the risk of inappropriate integration design needs to be carefully considered. Even expert users may be completely unaware of the ramifications of a particular interaction. Nevertheless, this will be a method chosen in many instances. The trick is to avoid the trap of just stuffing the mainframe application into the browser using one of these screen scraping type tools. Security concerns and usability issues are not trivial.
Messaging Queues (MQ). With JMS or WebSphere MQ on the mainframe, a messaging protocol can be observed that includes message brokering capabilities and greatly enhances the integration system. In many respects, messaging is the best gateway to application-to-application integration. But it should not be mistaken as a great solution for RIA extensions. Not all mainframe systems are equipped to handle MQ and certainly yhe investment required off the mainframe would be considerable. Unless you alrady have MQ present in both mainframe and non-mainframe servers, I would skip this approach. Other protocols such as CICS may be preferable not only for their relatively greater presence, but also because of the strong knowledge base in the mainframe IT community regarding their use.
CICS. Customer Information Control System (CICS) is a mainframe transaction server designed for mostly interactive rapid, high-volume online processing and can also perform background processes. With a CICS Adapter, the uniPaaS application platform can be made to appear like another CICS server (including its clients) to a mainframe system. CICS support for multi-region operation (MRO) provides a simple and secure entry-point into the mainframe application environment without the need for extensive programming. Some CICS integration solutions utilize Web Services to interface CICS on the mainframe to the outside world. So with CICS we have another excellent pattern for mainframe RIA extension to utilize the CICS adapter to connect to the uniPaaS application platform, thereby eliminating the need for multiple interface development and simplifying the deployment of the refactored mainframe applications as RIA applications.
To manage RIA development and RIA mobile development of Rich Internet Business Applications, the uniPaaS application platform is an excellent solution. More information on the uniPaaS Application Platform is available from Magic Software Enterprises.
Tuesday, June 9, 2009
Business Trends Quarterly targets 35,000 "senior level business and technology executives with in-depth analysis of, and key insight into market trends and innovative technologies."
Daniel made a great observation about uniPaaS when he wrote: "That is, if you're an ISV, you create your app as one code base, rather than separate versions for full client, web-based, on-premise/on-demand, RIA, SaaS, localized, globalized...much simpler!" You can read the entire article on the Business Trends Quarterly site or get more information. For more information on uniPaaS Rich Internet Applications development or SaaS Development see the Magic Website.
Wednesday, June 3, 2009
uniPaaS and Green IT Initiatives
We all have to do our part to reduce our carbon footprints and help the environment. It not only makes business sense, it’s just the right thing to do. The question for those who manage enterprise application portfolios and IT departments is: how can they do their part to reduce energy consumption and harm to the environment? While many organizations may be looking at SaaS as a means to reduce their carbon footprint, as well they should, they may not realize that cloud computing strategies such as Platform-as-a-Service or PaaS can also help the environment.
At Magic Software we’ve long been known for making a highly productive application platform. In the 1990s, developers utilizing our development tools earned Magic Software’s application platform a stellar reputation for efficiency by winning the Droege International Developers Competition five years in a row. Since then, Magic has continued to thrive, as more and more large and midsize enterprises decided to deploy mission-critical business applications based on the application platform from Magic Software. Today, the uniPaaS application platform provides state-of-the-art capabilities for Rich Internet Applications, Mobile Computing, Software-as-a-Service and traditional full client, batch and web applications. Over the years, much attention has been focused on the productivity advantages of uniPaaS, but little has been written about the energy impact of this application platform. uniPaaS actually has a number of characteristics that make it greener than its Java and .NET siblings. With uniPaaS, the PaaS may indeed be greener on the other side. This article highlights how uniPaaS can become a core efficiency driver in your green IT initiatives.
Energy Reduction Has Become an Economic and Environmental Imperative. While computer technology properly implemented has the potential to reduce paperwork, there is no question that it also consumes enormous amounts of power. It is suggested that 15 personal computers have the same carbon footprint as one automobile. According to a 2007 research report by the Lawrence Berkeley National Laboratory:
“Aggregate electricity use for servers doubled over the period 2000 to 2005 both
in the U.S. and worldwide. Almost all of this growth was the result of growth in
the number of the least expensive servers, with only a small part of that growth
being attributable to growth in the power use per unit.
Total power used by servers represented about 0.6% of total U.S. electricity consumption in 2005. When cooling and auxiliary infrastructure are included, that number grows to 1.2%, an amount comparable to that for color televisions. The total power demand in 2005 (including associated infrastructure) is equivalent (in capacity terms) to about five 1000 MW power plants for the U.S. and 14 such plants for the world. The total electricity bill for operating those servers and associated infrastructure in 2005 was about $2.7 B and $7.2 B for the U.S. and the world, respectively.”
Much of the attention in green IT initiatives is therefore understandably focused on reduced energy consumption. This is definitely not a strictly hardware oriented issue. A recent Uptime Institute study found that 10% to 30% of servers in the typical data center consume energy without serving any business function. The uniPaaS application platform has unique characteristics during both application development and deployment that contribute to reduced energy consumption.
1. uniPaaS enhances Elasticity through Multi-threaded Architecture. The uniPaaS application platform’s enterprise server delivers a multi-threaded application architecture. Economies of scale are enhanced by the increased elasticity possible through multi-threaded architecture. How does this work in uniPaaS? Each application task is broken up into manageable pieces called threads that are processed by any of the cores, CPUs or physical servers available to it. uniPaaS’ dynamic application partitioning also allows it to apply multiple physical servers to a single application. Instead of having lots of excess CPU capacity dedicated to a single user or application module, highly efficient usage is made of all the available processing power in order to reduce overall capacity requirements by as much as 95%.
2. Data-deduplication. uniPaaS is a cross-platform and cross-database application platform. It can be deployed on IBM i, AIX, Linux, Windows and other operating systems and it can access mainframe data as well. It also works with data from any database – DB2 UDB, DB2/400, Oracle, MS-SQL, MySQL, etc. You can easily use uniPaaS with the data types already in use in your IT environment. There is no need to resort to elaborate ETL procedures that duplicate data. Duplicate data not only increases storage capacity requirements, it also requires processing power dedicated to synchronization procedures and all of this consumes still more energy. uniPaaS also delivers all of the record locking and other database programming features needed to accommodate transactions in an efficient, data-lean manner.
3. Rich Internet Applications. To access a Rich Internet Application, all that is needed on the client computer is the URL. The full application doesn’t actually get installed on my system, as most of the logic is being executed on the server. When I access the URL, the application loads into memory on my computer and of course, it is already running on the server. Notice I said “most” of the logic is executed server-side, but not all. uniPaaS is truly unique in the way it allows both the server and the client to execute and process logic. It is not truly a thin client or a thick client application. We call it a “fit” client. Much of the focus in the IT industry has understandably been placed on reducing power consumption in the data center. One of the best means for doing so may be to make better use of the computing power available on the client machine.
From an energy consumption standpoint, the client machine is already running while the user is interacting with the server. With uniPaaS, developers can optimize applications to use the both the server and the client’s available processing power. While many approaches attempt to centralize computing with the use of thin clients, in reality most of these thin clients are run on extremely powerful personal computers whose CPUs are vastly underutilized. uniPaas enables true optimization resulting in the greatest efficiency in both performance and energy usage.
4. The unitary nature of uniPaaS. The uniPaaS name is no accident. Not only does uniPaaS provide the application platform infrastructure needed to deliver “Platform-as-a-Service” or PaaS, it is also unitary in terms of its development orientation. What does this mean and how does it save energy? It’s quite simple. If you can use one programming tool to create both your server application and your client application – you have successfully reduced the number of development computers and the number of programmers. This is an extremely unique and fundamental characteristic of uniPaaS that is catching many veteran IT architects by surprise. While they have all known that it is theoretically possible to develop and deploy in a unitary fashion, they thought the evolution of increasingly complex environments made it impossible to use one tool for both the RIA client and the background server. There had been one or two mildly viable projects bouncing around in the open source community, but no mature, stable commercially available application platform could deliver this capability. uniPaaS is an enterprise-proven application platform that has been deployed in the market for over twenty years – and it is suddenly being looked at extremely closely by major IT organizations because of this fundamental advantage – a paradigm shift really – that means you can create a rich Internet business application (not just a game or an entertaining website, but an application with transactions, complex data structures, and logic) with one development tool and not two (or three or more). Instead of having to master Java or C# and Flex or Silverlight and hire a small army of energy consuming programmers, you can hire one or two uniPaaS developers who develop in a unitary way.
But this concept is not limited to development; it is really more about deployment. The application deploys in a unitary fashion, and this means no complex programming is required to manage the brokering of communications and other technical matters between the client and the server. If project time is therefore also reduced, energy savings in the development phase becomes dramatic. And of great interest to many software producing organizations, those energy savings are also mirrored by reductions in research and development costs that reduce the need for initial investment and increase the health of the business.
5. Paperwork Reduction. All software has the potential to add to paperwork reduction. Unfortunately, that is rarely the case. With the personal computing revolution has come the personal printing revolution as well. uniPaaS is well positioned however to support culture shifts in the way software is used that enhance paperwork reduction and the greening of the IT environment. Paperwork reduction saves trees, the energy required in producing paper, shipping paper and the rather significant energy costs involved in storing paper-based records. The average office employee consumes over 10,000 pages per year. This costs companies an average of $15,000 per employee. Cutting paper usage not only reduces expenses, it also helps the environment. The average printer consumes 49 KWh (kilowatt hours) of electricity each month. For every, 500 printers decommissioned, a company can save $3000 or more in direct printer device related energy costs alone – this doesn’t even begin to factor in paper storage or costs of paper and printing supplies or the equipment itself.
How does uniPaaS reduce paperwork and printing, thereby reducing energy costs and other harmful environmental impacts? Rich Internet applications reduce printing requirements. Electronic reports, electronic documents, electronic books, and electronic catalogs can all substitute for their paper equivalents. In addition, electronic transactions can replace traditional paper-based invoices, POs, RMAs, etc. adidas Canada reports that they achieved an immediate 400% ROI with their implementation of uniPaaS attributable to the reduced demand for hard copy printed product catalogs by retailers when their new online catalog was implemented. Detailed information on uniPaaS and paper work reduction is contained in the White Paper: uniPaaS and the Paperless Office: Your Choice of Application Platform Can Make A Difference in Paperwork Reduction.
6. Cloud Computing and SaaS: Server Consolidation 2.0. Leading IT and energy efficiency analysts have discussed the energy saving effects of Cloud Computing and SaaS. These approaches take the savings possible within a single company through server consolidation to a higher level by spreading the consolidation concept across multiple enterprises.
The uniPaaS SaaS Management and Monitoring Module allows developers to provision and deploy true “multi-tenant” Software-as-a-Service (SaaS) applications. A multi-tenant application employs a single application and database for multiple completely separate client organizations. To illustrate this, consider that in the past 123 SOFTWARE COMPANY sold its software to ACME SUPPLY, ABC MANUFACTURING and XYZ TRANSPORTATION all of whom purchased their own hardware to run it in their data centers with individual employees accessing those applications from networked personal computers. These client server applications are the mainstay of business today.
With SaaS, a single cloud-based data center exists. Since the personal computer workstations at ACME SUPPLY, ABC MANUFACTURING and XYZ TRANSPORTATION all have access to the Internet, these companies can close their data centers or at least eliminate and reduce many of the power-hungry servers in their data centers. Instead, all three companies utilize the centralized SaaS application hosted in the cloud. None of them can see the others’ data as they all have visibility and access to only their slice of the application and data. uniPaaS has all of the difficult-to-develop application platform pieces necessary to make this possible: an enterprise-class server, a broker-engine, rich Internet client and web browser client support. Alongside this, the Management and Monitoring module allow the SaaS company to do all the provisioning of new companies and users, as well as the metering and monitoring needed for billing purposes.
The beneficial effects for the environment, when multiplied across tens of thousands or millions of businesses are enormous. Most data centers are designed to perform well at times of peak demand. As a result, they have significant unused capacity typically ranging from 92-98% of the time that they are in operation. By pooling use of data center resources through the use of Cloud and SaaS infrastructure, centralized data center power usage can be reduced by 90-99.9% depending on the application type. The typical IT server consumes 450 watts of power. Even when one factors in the continued use of personal computers and handheld devices to access the SaaS applications, overall power usage is reduced by amounts ranging from 55-95%.
The SaaS model fuels green savings in other ways too. Not the least of which is data deduplication. By reducing the amount of storage required, energy consumption is reduced. And the metering options possible in uniPaaS allow a software company to charge per, per month, per data throughput, per transaction, etc. When people have to pay to use software, the demand is self-regulating and therefore less energy is consumed. Finally, most SaaS and cloud infrastructure facilities are run by world-class IT organizations that know how to architect and manage their facilities far more optimally than individual IT organizations. But SaaS is not the only way uniPaaS reduces power consumption.
Measuring the benefit. So how can uniPaaS fit into the green initiatives for your company? We recommend using the services of an IT consulting organization who can help you quantify the verifiable energy savings possible with uniPaaS across all dimensions of your business. The Server Side Savings Worksheet enables analysis that can be used to show server side energy savings. For a copy, send me an email request. Additional factors to be evaluated include network and storage energy savings, cooling and power supply energy savings, and client side energy savings.
We are not suggesting that you rewrite all enterprise applications from scratch, but rather that you take an incremental approach to adopting uniPaaS as your enterprise standard application platform. Evaluate how RIA, SaaS and Cloud Computing with uniPaaS as your application platform can reduce energy requirements. Thousands of major enterprises use the uniPaaS platform for mission critical business applications today because it is more productive and straightforward than available alternatives. Now they have a third reason: verifiable green IT savings that reduce the enterprise carbon footprint.
Glenn Johnson is Senior Vice President at Magic Software Enterprises, Inc. in Laguna Hills, Calif., an Advanced IBM Business Partner and winner of SAP Global Innovation and Quality awards. He may be contacted at email@example.com or (800) 345-6244.