$Account.OrganizationName DAA Design-To-Order™ Newsletter
January 2006
News and tips about KBE, presented by DAA  

The most experienced provider of Knowledge Based Engineering and Web Based Design-To-Order™ Systems

John Lambert

John Lambert

President / CEO

DAA is Growing to Serve You Better.

2005 was a strong year for Knowledge Based Engineering technology. DAA has seen growth by all the KBE technology vendors and DAA’s services business has increased correspondingly. DAA has continued to increase and certify new Indian based service firms as well as hiring additional direct staff to meet our customer’s demands.

As part of our continuing expansion I would like to introduce you to Mr. Benny Federico, a new senior engineering resource available to support you. Most recently, Benny was the Director of Engineering for Accuride Corporation. His extensive experience and education is commensurate with the DAA philosophy of providing the most focused, senior talent to efficiently address customer needs. Benny will also be assisting in further developing DAA’s delivery model for consultative, KBE and engineering services.

Benny holds Bachelor and Master of Science Degrees in Mechanical Engineering from WPI, holds 39 credit hours in PhD level mechanical engineering mechanics courses from the University of South Carolina, Columbia, SC and Doctor of Management in Organizational Leadership from the University of Phoenix which is pending.

As we move into 2006, please do not hesitate to contact us to discuss your engineering, software and KBE needs. Our goal is to provide best-in-class support, efficiently and quickly solving your critical business and engineering problems.

In this issue

  • KBE Project Planning: Why is ROI so Important?


  • Can Knowledge Based Engineering help me reduce my back-end system maintenance costs and simplify my infrastructure?

  • Series: KBE on the web - Are there security issues involved with web-enabling a Knowledge Based Engineering System?


  • KBE Project Planning: Why is ROI so Important?
    ROI

    Over DAA’s decade of KBE planning and implementation, we’ve learned that project success is multi-faceted. Up-front identification and handling of these many facets determines whether a project will ultimately succeed. While proper handling of all factors is mission critical, there is a subset of up-front factors that must be resolved during the project selection phase. Resolution of these “up-front” factors during project selection is on the critical path to project success.

    This article will discuss the “up-front” factors and an efficient, well-tested approach ensuring these items don’t lie hidden only to derail a project during the development/programming cycle. DAA has even seen worst case scenarios when project derailment occurs at the last stage of the project cycle; post project deployment! Let’s take a look at how to prevent this.

    In order to avoid these issues, one must first pause and look carefully at personal motivation. In general, people become motivated when pain is present. In business, pain is generally caused when we are overloaded or when some aspect of our process is out of control. Out of control processes cause rework, margin erosion, confusion, headaches and after-the-fact scrambling.

    When issues regarding overloading and headaches are truly present there will be individuals within the organization who want to fix them; the self preservation instinct guarantees this. In addition, where overload and rework issues exist, quantification and documentation of these issues is straight forward. Conversely, when these issues are not quantifiable, the underlying “problems” are generally not present; even if purported to be.

    Over the years, DAA has learned the best way to assess a problems’ merit is by saying to the customer “if you have a problem in that area, then please help me justify spending resources to solve it.” Invariably, when problems are actually present, the justifications are generally straight forward and quantifiable.

    After the value of correcting a problem has been established, an assessment can be made regarding the cost of correction. If the one-year benefits are greater than the solution costs then most likely there will be compelling business justification to proceed.


    Can Knowledge Based Engineering help me reduce my back-end system maintenance costs and simplify my infrastructure?
    coins

    Parametric CAD systems have been the mainstay for geometric model development in engineering and drafting environments. They provide the ability to create solid models that can be driven by numerical parameters to produce multiple output variations. One of the central themes of KBE is changing the constructing of automated design systems from output based systems (traditional programming languages and parametric models) to those engineering logic and process based systems using non-procedural KBE tools. This change of focus provides benefits in many areas of business but also provides system maintenance benefits in two different ways.

    Programming Reductions: The first way KBE methodology assists in reducing system maintenance is to reduce the effort in rewriting source code used in applications. It is a well know fact that software applications need to be maintained as a company’s product and business processes change and evolve. A company must either maintain or contract out programming capabilities so applications can maintain their effectiveness over time. A primary component of the maintenance cost is the ease and simplicity by which code can be modified.

    KBE programming languages were developed with the concept in mind that engineers would be the primary caretakers of the code as opposed to programmers. One advantage of that philosophy is that domain experts would not have to take the extra step of transferring engineering and configuration knowledge to programmers to get programs written. Another advantage came when the original developers looked at the requirements of the tools needed to entice engineers to use those tools without discarding them as too difficult and time consuming to use. The result was non-procedural code with simple syntax that allowed rapid development of code.

    The combination of the ability of domain experts to program with the simplicity of a non-procedural code with simple syntax adds up to less time required for program maintenance.

    Reduction of Stored Template Models and Drawings: The second way that KBE methodology assists in reducing system maintenance is to reduce the effort in maintaining libraries of parametric parts used in the construction of models used in the configuration of physical systems.

    Parametric models provide a powerful and convenient means of representing physical objects with predictable (and stable) geometric relationships and are used in many engineering and configuration processes. Many configured and engineered to order products, however, require a much wider range of application of relationships than can be easily stored in a small number of parametric models. This leads many businesses to create large libraries of part configurations in the form of parametric models and assemblies that require extensive maintenance whenever the parts change or new configurations are offered as product options.

    Those who use KBE programming techniques have found that many relationships that require numerous parametric models can be represented by a set of process rules that can generate a much wider variety of product configurations. Also, changes in component parts that would require changes in the assemblies that use them don’t necessarily require changes in the rules that use those parts and therefore wouldn’t require any maintenance of the system over changing the component parts themselves.

    In summary, KBE systems can significantly reduce back end infrastructure and system maintenance. This is especially true in systems that make use of parametric models or significant amounts of traditional, procedural style coding.


    Series: KBE on the web - Are there security issues involved with web-enabling a Knowledge Based Engineering System?
    Computer

    One of the primary concerns when publishing KBE System on the internet is security of the rules. As these rules often times represent important intellectual company capital, security and theft prevention is paramount. In addition, there is also the concern that these rules may be compromised in some way thus causing the KBE system output to be compromised in some way. DAA has created a secure software solution called Knowledge Server™ that addresses and protects against these problems.

    Knowledge Server™ uses multiple tiers to secure data, applications, and engineering rules. Separating user interface code from business and engineering rules requires would-be attackers to navigate through multiple secure layers. The Knowledge Server™ layers have the added benefit of riding on top of your network’s existing security measures. Because your engineering rules are stored deep inside your internal network, the amount of work required to access these rules directly would be enormous.

    Your engineering rules can be further protected by storing them on a network that is segregated from your primary internal network. All communications with the server must first go through a secure gateway before they are even allowed to interact with your rules. With this scenario, even attackers who have gained access to your internal network either externally (from the Internet) or internally (while sitting at a computer inside your building) would be unable to access the server and the KBE rules directly.

    Allowing your customers or field engineers to interactively access your rules in a secure may sound impossible but DAA has solved that problem for you. By utilizing proper network security coupled with DAA’s multi-tiered Knowledge Server™ solution you can leverage your design rules over the internet and increase customer access to your custom products without handing over the keys to your business.


    Maintaining KBE (Knowledge Based Engineering) Systems – What’s the Best Approach?

    DAA’s core mission is assisting our customer’s successes in automating sales, engineering and manufacturing work order processes. The scope of automated functionality is dictated by customer business objectives. As these business objectives continually change, so must the supporting KBE systems.

    KBE systems have natural life cycle steps. Every automated business process (KBE system) that is expected to provide continued returns must go through the three steps of (1) Opportunity Identification & Qualification, (2) System Design and Implementation and (3) System Maintenance.

    As the scope of this discussion is step 3, let’s take a closer look at what this step involves and the two main approaches in which system maintenance can be approached.

    Specifically, system maintenance is the process of updating and changing a successfully implemented KBE system in order to sustain its associated business benefits. The need for system change is driven by the following factors:
    • Changes in the underlying business process that has been automated
    • Changes in the system’s user requirements
    • Changes in the consumer’s output requirements
    • Changes in the software products used to construct the system
    • Correction of various system problems and bugs.
    The requirement to address these items begins immediately after initial system implementation. Understanding and accepting this business reality and the need for maintenance is rarely disputed by KBE system users. The issue that can arise regards how the process of maintenance is approached. Over the years, DAA has seen two distinctly different approaches; the first generally leading to ongoing project success and the second generally leading to problems.

    Annual Application Maintenance

    Annual Application Maintenance involves an efficient, well planned process and approach to system maintenance. Annual Application Maintenance provides the following benefits:
    • Keeps the system continually at 100% usefulness and avoids user frustration.
    • Minimizes the effort in getting enhancements implemented.
    • Enables planning and implementation of changes in an efficient and forward looking way from both cost and resource availability perspectives,
    • Leverages the capabilities of the technologies used in the automated system to a maximum degree,
    • Minimizes overall system cost
    In addition to the Annual Application Maintenance providing these benefits, it avoids the negative issues associated with the Bundling approach as discussed below.

    Bundling

    The second, and least effective, method of system maintenance is referred to as “Bundling”. Bundling is the accumulation of multiple change requests over a period of time, sometimes years, followed by discrete upgrade events. The concept is that when the bundle is big enough, the changes can be implemented through a discrete upgrade event. This concept also presumes that these discrete upgrade events can be repeated each time a bundle of sufficient size accumulates. Although this approach may seem simple, attractive and effective, a decade of experience has shown that saving-up bundles of issues for periodic upgrade events most frequently leads to system failure with the KBE customer…
    • experiencing a continual erosion of application usefulness and increasing manual labor costs (“slow walk” back to the manual process which the system was initially created to replace.),
    • becoming frustrated by system limitations while waiting for the bundle to grow to an “appropriate” size for implementation,
    • finds they are unable to secure funding for their latest “bundle” as they find themselves at the mercy of ever changing spending constraints and justification criteria,
    The above list is a small sample of the very real frustrations that inevitably occur with the “bundling” approach. It has been DAA’s repeated experience that these frustrations eventually lead to applications reaching end-of-life within 3-5 years after initial implementation with corresponding loss of the initial investment.

    In summary, the Annual Application Maintenance approach is an integral part of DAA’s business model. The above items are a small sample of the very real benefits that all KBE users’ can enjoy. Please call DAA is you would like to get further information on this powerful and cost effective method of system maintenance.

    Learn more...
    Quick Links...

    Visit DAA on the web

    DAA's Solutions

    KBE Forum

    DAA Engineering

    DAA's Customers and Partners

    See live DTO™ demos

    More ways to contact DAA



    Join our mailing list!