Enterprise System Integration.com

Contact Us
Wide System Fundamentals | No Bugs in Our Future |
Zero Latency Enterprise (ZLE) | ESI ZLE Benefits | Scalable Growth Strategy | OMG Meta Object Facility | ESI Business Cases | ESI ZLE Proof Of Concept |
Large Enterprise Business Objects | Dynamic Subset or Composite-Object VIEWS |
Where are We Today /a> |
subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link | subglobal5 link
subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link | subglobal6 link
subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link | subglobal7 link
subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link | subglobal8 link

Enterprise System Integration for Business Process Management

Launch Your Business

Enterprise Acceleration

Cost-Effective, State-Of-The-Art, Enterprise Architecture - Rapid Implementation Methodology to Integrate, Consolidate, Simplify and Accelerate Agile Business Processes and Distributed Enterprise Computing Systems.

The Fastest, Lowest-Cost, Reliable Way to Build Architecture and Implementation Infrastructure for Enterprise-Wide System Integration – A Proven Approach With Impressive Large-Scale Multi-National Enterprise-Wide Success History.

Document and Eliminate Unnecessary Redundancy, Duplication Of Effort, Reinventing The Wheel, and Incompatible Enterprise Elements Across Isolated, Compartmentalized Departments That Lack Coordination of Processes or Systems, with Autonomous Development and Maintenance Budgets.

Implement Lower-Cost, Higher-Performance, Standardized, Reusable Enterprise-Wide Solutions.

Enterprise System Integration (ESI)

(ESI) is the natural continuing evolution, amalgamation and assimilation of many advanced Enterprise-Wide Management, Computing Science, and Networking Concepts, including: Electronic Business Process Management, Lean Enterprise (Jidoka plus Just-In-Time), Enterprise Application Integration, Model-Driven Development, Enterprise-Wide-Glossary-Based Consolidated Metadata (Information Sharing and Disambiguation), Self-Defining Meta-Metadata Repository (Heterogeneous-Environment and Technology-Independent Information Transportability - within the Enterprise and among Business Partners), Enterprise Architecture, Object-Based Service-Oriented Architecture, Enterprise Service Bus, Zero-Latency Enterprise, Push / Pull, Publish-and-Subscribe Message Oriented Middleware, Semantic-Network and Object-Oriented Class-Based Data Structures, United Nations and World-Wide-Web-Consortium (W3C) Based “Intelligent Agent” Semantic Web using Industry-Specific Uniform-Data-Tag Standards (XML, etc.). The webpages on this site will introduce the role that each of these play in ESI. (Work In Progress)

ESI documents and helps eliminate: Unnecessary Redundancy, Duplication Of Effort, Reinventing The Wheel, and Incompatible Enterprise Elements across isolated, compartmentalized departments that lack coordination of processes or systems, with autonomous development and maintenance budgets.

Lower-Cost, Higher-Performance, Standardized, Reusable Enterprise-Wide Solutions

Enterprise System Integration (ESI) does NOT require homogeneous hardware-or-software products. Evolving protocol-specific heterogeneous business process interfaces are accommodated and implemented by universal, distributed, Publish-and-Subscribe Middleware, which is “Metadata-Driven” by a comprehensive, hardware-and-software-environment-independent, Enterprise Architecture Integration Model.

Synchronize worldwide networked computer systems. Allow authorized need-to-know systems and people to be notified around the world in near-real-time (about 2 elapsed seconds) about important business events that initiate and influence multiple interdependent, collaborative business unit processes. (Eliminate the latency that is inherent in cumbersome, expensive paperwork, AND with aging legacy distributed relational databases with “multi-phase commit.”)

Eliminate Unnecessary Paperwork by automating information flow. EVERY PIECE OF NEW OR MODIFIED INFORMATION IS ENTERED ONLY ONCE, and then it is automatically propagated to every authorized person and system that needs it, without manual human intervention.

The smooth transition to ESI does NOT have to be “all or nothing.” The transition to ESI is both incremental and controlled. Generic, standardized, reusable ESI Publish-and-Subscribe Message-Oriented Middleware (MOM) Infrastructure is installed first, and then it smoothly handles heterogeneous-evolving-version software release interface protocol transitions (and possible fall-backs) over the distributed system server network, over time

Eliminate Unnecessary Paperwork by automating information flow. EVERY PIECE OF NEW OR MODIFIED INFORMATION IS ENTERED ONLY ONCE, and then it is automatically propagated to every authorized person and system that needs it, without manual human intervention.

Phase out application-specific hard-coded special-purpose inflexible, difficult-to-maintain, legacy-system databases and intercommunication protocols. Incrementally replace them (as time and resources permit) at minimal cost (when system enhancements are made) with general-purpose, agile, adaptable, standardized, reusable, Publish-and-Subscribe, Message-Oriented Middleware, Object Request Brokers, Zero-Latency Enterprise Application Integration, Service-Oriented Architecture, Enterprise Service Bus, and other ENTERPRISE ARCHITECTURE Infrastructure innovations, as they become available in the future.

The smooth transition to ESI does NOT have to be “all or nothing.” The transition to ESI is both incremental and controlled. Generic, standardized, reusable ESI Publish-and-Subscribe Message-Oriented Middleware (MOM) Infrastructure is installed first, and then it smoothly handles heterogeneous-evolving-version software release interface protocol transitions (and possible fall-backs) over the distributed system server network, over time.

Message-Oriented Middleware (MOM) Each software release includes Publish-and-Subscribe interface “adapters.” This allows multiple dissimilar versions of ESI application components (providers and consumers) to be concurrently active on your worldwide network.

These “push” and “pull” ESI message adapters translate interface protocols forward or backward across evolving software releases.

The future evolutionary enterprise expansion process is driven by the agility and integration opportunity insights provided by the Enterprise Architecture Model “blueprint.” It is also the SUPERIOR SOLUTION for Rapid Consolidation when profitable Mergers and Acquisitions occur.

Back to Top

Eliminate Unnecessary Paperwork by automating information flow. EVERY PIECE OF NEW OR MODIFIED INFORMATION IS ENTERED ONLY ONCE, and then it is automatically propagated to every authorized person and system that needs it, without manual human intervention.

Phase out application-specific hard-coded special-purpose inflexible, difficult-to-maintain, legacy-system databases and intercommunication protocols. Incrementally replace them (as time and resources permit) at minimal cost (when system enhancements are made) with general-purpose, agile, adaptable, standardized, reusable, Publish-and-Subscribe, Message-Oriented Middleware, Object Request Brokers, Zero-Latency Enterprise Application Integration, Service-Oriented Architecture, Enterprise Service Bus, and other ENTERPRISE ARCHITECTURE Infrastructure innovations, as they become available in the future.

The Inviolate Enterprise Acceleration RULE That The CEO Must Mandate Is:  
“No Piece Of New Or Changed Information Should Ever Be Entered More Than Once.”
In a widely-distributed enterprise, information can be replicated and widely distributed, (to maximize parallelism and worldwide sub-second access time), but the Distributed (not centralized) Publish / Subscribe system will coordinate message-oriented data distribution to ensure information consistency, availability and fail-safe reliability.

.

Start Simple To Demonstrate Benefits and Build Consensus Let’s assume that we can find a CEO (or senior operations executive) who wants to aggressively slash unproductive, unnecessary costs, accelerate the enterprise, and rapidly grow profitable business operations. (There don’t seem to be enough of them in America these days.) What can we do quickly and inexpensively to demonstrate some of the above potential benefits, WITHOUT the kind of capital and time investment that was required by the very-successful Sabre and FedEx GOCC systems.

Low Fruit for Enterprise Architecture In essence, we want to rapidly find some low-hanging tasty fruit, and offer it to the CEO. We’ve discovered a cute name for this effort – We call it the ESI Watermelon Project. It can work like this:

We ask the CEO for one young aggressive self-starter. The person does not need a lot of business-as-usual experience (in fact it would get in the way). The personal needs to be friendly, outgoing, observant, communicate well (especially interview LISTENING skills), and prepared to learn how to Overcome Strong Resistance To Change,
and“That is the way we’ve always done it” stinkin’ thinking.’

The CEO must have a meeting with this young innovator, plus all of the CEO’s direct reports. The mandate to Eliminate Paper is explained, and the CEO appoints the young innovator to gather information about all current paperwork, monitor, and report to the CEO about each department’s progress in making the mandate happen. Each piece of paper is a measure of avoidable COST, NOT departmental productivity. Eliminating paper properly should equate to lowered costs and improved operations. Executives should be measured and paper-savers rewarded for eliminating paper in a way that improves their departments’ productivity.

The innovator must meet with each direct report and their subordinate senior staff.

They begin by identifying the name (or form number) of all pieces of paper in each organization, and capturing a brief description. This list is kept in an online database that is accessible on the network. Security access protocols may be needed for some types of information.

Over time, more information is gathered about each piece of paper, such as the contents of each data field, who supplies and who needs the information (human or computer system). Cross reference links are created for data fields that appear on multiple pieces of paper.

Metadata (the attributes of the data fields) is gathered and made available so it can be accessed in a uniform way across the entire enterprise (regardless of how it is physically implemented or distributed).

As the volume of information about information increases, so must the resources available to the appointed paperwork eliminator. Early on in the paperwork elimination process, a lot of interdepartmental redundant information will be discovered. Where it is easy, it should be consolidated, simplified and shared, as necessary.

One of the first computing communication infrastructure components (after Internet or Intranet access is in place) is an Event-Oriented Publish-and-Subscribe System. For each piece of information that has multiple uses throughout an enterprise, one-or-more sources is identified (publishers), and multiple types of information consumers are documented (subscribers). When a business event takes place that supplies an element of this commonly-required information, an electronic MESSAGE (not paper) is sent to the Publish / Subscribe system, which then sends it to all authorized subscribers). This decade-old technology is often called Message Oriented Middleware (MOM). Many vendors are available with many competitive features.

The Object Management Group (world’s largest software consortium) has standards for MOM and the very-important related Metadata. Simple mapping software may be used when different subscribers want the data in different message types, communication protocols, formats and collection groupings (sometimes called “views”). Event-related messages may produce partial subset views, or consolidate information from multiple event types to produce a complex composite message view.

In many organizations, it is surprising how fast you can document distributed redundant information Metadata, and implement high-speed Publish / Subscribe. In today’s world, when an information input event takes place, you should be able to nearly-instantaneously synchronize all operational subscriber servers in only a few (two) elapsed seconds. Techniques are available for real time information synchronization (like worldwide airline seat assignments).

SUMMARIZED CAPABILITIES:
 Over twenty years of large-scale Enterprise Object Modeling and high-performance distributed-system development experience. Successful leading-edge innovator and enterprise information system development mentor. Excellent verbal / written communication and team-building skills: a prolific technical architecture author and well-received presenter. Strong industry technical background in advanced telecommunications, internetworking, air-and-ground transportation logistics, retail, financial, energy, aerospace, high-speed telemetry, real-time command and control, engineering and scientific computing systems. A trendsetter in Enterprise-Wide Process Reengineering, advanced software development methodologies, object-oriented architecture, enterprise application integration, zero-latency near-real-time enterprise information system integration, zero-defect / mission-critical software, decision support systems, operation optimization, enterprise resource optimization, configuration / version management, and the infrastructure to support enterprise-wide object consolidation and reuse. Extensive experience in: use-case requirements analysis, distributed object system design, development, testing, maintenance, management, marketing, promotion, and deployment of complex heterogeneous computer communication internetworks, with distributed, object-oriented, client-server, n-tier, and peer-to-peer computing environments.

Pioneered the use of advanced CASE tools and multiple methodologies since 1979; Object-oriented distributed system development since 1981 using: UML, enhanced Rational Unified Process (RUP), Rumbaugh-OMT, Jacobson-OOSE Use Cases, Booch-ROSE, Martin / Odell-OOIE, Mattison / OOE, Fusion, Coad / Yourdon, Shlaer / Mellor, Knowledge Engineering Environment, etc. Broad architectural knowledge of multiple hardware-and-software delivery platforms, with heterogeneous communications networks spanning mainframe legacy systems, parallel processors, mid-range systems, workstations, various PCs, Internet/Intranet and fault-tolerant real-time systems.
Specific focus has been on continuously improving software development and deployment methodology for high-quality, integrated, enterprise computing systems:

(1) Improving Software Quality, Productivity, and Usability, integrating advanced methodologies and tools, while optimizing complex computing internetworks with dissimilar evolving clients and servers,

(2) Software and Business Simplification: aggressive, reliable commitments to cost-effective zero-defect integrated computing solutions that are responsive to rapidly-changing requirements, easier to understand, develop, maintain and transport to new computing environments / deployment platforms,

(3) Emphasizing evolution to: Enterprise Application Integration, Zero Latency Enterprise, Component Architecture, Use-Case Requirements-Driven Development, Enterprise Object Modeling, Intranet Universal Repository, Rapid Cycle Iterative Incremental Risk Management, Structured Reusability, Transportability, and Worldwide Web Business-To-Business and Business-To-Consumer Technology.

Larry Hartweg Enterprise Application Integration (EAI) and Distributed-Object E-Commerce Architecture and Methodology Consultant.

Hartweg was the Chief Object-Oriented Architect of the paperless FedEx Global Operations Command and Control - super worldwide enterprise integration system in 1993. It is still the heartbeat of FedEx today. If GOCC was buggy, airplanes would crash, and your packages would not arrive. The fabulous GOCC integrated logistical excellence meant that FedEx airplanes and computer systems were used by our government and the FIRST ones allowed to land in NYC after the 9/11 attacks. FedEX GOCC goes far beyond many of the things that Sabre can do. GOCC was the state-of-the-art of enterprise integration in 1993, which few other companies have achieved a decade later.

EXPERIENCE: Object-Oriented Methodology and E-Commerce Architect / Mentor / Project Manager
Primary activity: large-scale, enterprise-wide, object-oriented information network consolidation: vision, strategy, architecture, analysis, modeling, design, software development management and system deployment. Consulting services include on-the-job training / mentor programs in the architectural issues, methodology, paradigm shift, tool selection / integration, organization, and management decisions required to cost-effectively optimize rapidly-evolving, state-of-the-art, information network technology.

Enterprise Object Modeling facilitates direct user / developer communication throughout the Software Life Cycle: from user-centered analysis through object / event modeling, enterprise architecture, design, development, quality assurance, end user training, and continual system enhancement. Enterprise-wide business object (data + process) modeling leads to Software and Business Simplification integrated with Business Process Reengineering. This yields improved quality, productivity, flexibility, application suitability, and end user satisfaction. A combination of high-performance event-driven, client-server, and peer-to-peer telecommunications networks (based on industry standards plus “submillisecond response time servers”) accelerate real-time access to critical operational data, and communication between geographically-distributed, dissimilar, evolving enterprise-wide computing systems and scaleable distributed object computing servers.

Larry Hartweg's valuable services range from introductory classes and technical vitality programs through turn-key, hands-on management of mission-critical development contracts with budgets up to $500 million. Hartweg's custom-tailored, advanced-technology presentations include: "Management Issues in Information Technology," "Object-Oriented Internet / Intranet Analysis and Design," "Object-Oriented Database Architecture," "Message Oriented Middleware / Message Brokers," "Object-Oriented / UML CASE Tools," "User-Centered Analysis: Use Cases, Objects, Interfaces and Business Events," "Enterprise Object Modeling," “Enterprise Application Integration,” “Zero Latency Enterprise,” "Usability and Reusability," “Enterprise Component Architecture,” "ENCORe: (Intranet-Based) Enterprise Network Common Object Repository", “Near-Real-Time Zero-Latency Enterprise Information System Integration”, "Information Strategy and Migration Planning," "Business Process Reengineering + Total Quality Management," "Enabling Innovation: Imagination Creativity and Judgment" "Interpersonal Managing Skills," etc. Planning, architecture, large-scale integration, self-determining team building, training for designers and developers, and competitive-advantage development services have been provided, with successful high-performance systems deployed on tens of thousands of advanced workstations and mainframes.

Larry is nearing completion of a 1,000 page technical book: Enterprise Object Modeling. Hartweg was a paid reviewer / editor of Grady Booch's book: Object Solutions.

Paper Files When a sheet of paper is printed, it immediately begins to become obsolete and therefore is misleading. Changes made to the original source in the future are NOT propagated to all of the paper copies of it. If paper is stored in a file, it does NOT represent the current state of anything. It is at best a historical archive of the way things used to be (IF it was accurate when it was printed in the first place). Paper files take up a lot of valuable office space (MUCH more than electronic data storage). Expensive work must be done to create, maintain, and access voluminous paper files. A paper file in one location does not help people in another location. Duplicating paper files in multiple locations multiples the costs, and increases the likelihood that they will quickly become out of synch, in addition to individually obsolete. Faxing a copy produces a lower quality low-resolution image. For example, faxed blood tests on colored paper are often misread. One-month-old paper blood test results can be very different than today’s dynamic test values, for some rapidly-changing diseases. When large piles of paper are stored in filing cabinets, they must be organized in only one way (like alphabetical by name). If you want to randomly access files by some other data attribute, (like social security number, part number, or customers that use a particular product), then you have to create some type of alternate index, which can be clerically flawed, or quickly get out of synch. The content of paper files cannot be searched electronically (the way a search engine like Google does so efficiently and fast). It is many times better to store information in integrated online databases, where near-real-time access to up-to-the-minute information is readily available to every authorized person or computer system around the world with a need to know. Publish / subscribe systems propagate validated error-free copies of digital information. They can be used to keep many information server systems in synch worldwide.

Back to Top
Need Help in Your Organization? What are YOUR questions? We have the Answers.

CONTACT US :

E-Mail To: LHartweg@aol.com


| | Copyright 1980 – 2007 Larry Hartweg www.ZeroEnergyDesign.com All international rights reserved - Tenth Edition - July 2007 - No reproduction in any form without explicit written permission

This site is being designed, developed and advertised by Rose Anne Meyer at rm6815@bellsounth.com Need help with yours?