Answers to Questions and Sage Advice

Answers to questions which could be asked and sage advice which could be offered during collaborations with initial member(s) of the next client’s Architecture Team to compete an Initial Investigation by deciding it is in their enterprise’s best interest to complete the 2022 version of Enzweiler’s Architecture Team Methodology.

Why Is the Staffing of An Architecture Team a CEO, CFO, CIO, and One of the #1 Consulting Firm’s Senior System Architects?

An Architecture Team Has an Enterprise Perspective

Collectively an Architecture Team has an enterprise perspective and will be guided by a true north of:

  • Data on managers’ contributions consistently made to hitting top line targets, over the very long duration Targets System(s) will be used as their enterprise’s #1 system
  • Data on expenses which will be incurred over the very long duration Targets System(s) will be hosted and supported on-premise and/or in the Cloud on virtual private networks (VPNs)
  • Answers to questions which can be easily validated using facts
  • Lessons learned accumulated over a long career of monitoring as managers managed to go-live within budget using; models, dashboards, analytics of databases, synchronized databases, and systems used to maintain databases, as planned by their Architecture Team

During collaborations to complete the 2022 version of Enzweiler’s Architecture Team Methodology by making decisions and plans which are in their enterprise’s best interest on using; integral parts of Targets Systems, synchronized databases used to integrate parts of Targets Systems(s), databases, and systems used to maintain databases.

What Are the Integral Parts of Targets System(s)?

Models, Dashboards, Analytics of Databases, Synchronized Databases, and Systems Used to Maintain Databases

Architected integral parts of Targets System(s) which will be; developed, demonstrated, used, and continually improved as will be planned by the next client’s Architecture Team are;

  • Earnings projection model(s) which use managers’ set metric targets to project at least four (4) future quarters top line targets of; revenue, costs, and margins and to project SG&A expenses listed on Income Statement(s) used to compute future earnings targets
  • Forecasting models used to forecast the impact of external head/tail winds on top line targets, which were computed using earnings projection model(s)
  • Actual vs Metric Targets dashboard(s) used by managers to manage to hit their metric targets, which were set using earnings projection models(s)
  • Customer demand forecasting models and supply chain planning models used by managers to plan to hit their metric targets for delivering quality products and/or services to customers on-time as promised
  • Other planning models required by managers on organization chart(s) to plan to hit their metric targets to make their contributions to hitting top line target for; revenue, costs, and margins
  • Analytics of databases

Synchronized databases architected, developed, and maintained as will be planned by the next client’s Architecture Team will be used to integrate parts of Targets System(s).

Targets System(s), social media systems, digital advertising systems, digital marketing systems, Customer Relationship Management (CRM) systems, Human Capital Management systems, Enterprise Resource Planning (ERP) systems, and as required other systems which are currently or will be used to maintain databases which will be analyzed.

Databases maintained by using systems will be synchronized to be used by managers to set and manage to hit their metric targets to consistently make their contributions to hitting top line targets on Income Statement(s) using Targets System(s).

Is It Certain Top Line Targets Will Be Hit Every Quarter Using Targets System(s)?

No, External Head Winds Could Cause a Miss

What is certain – managers on organization charts will consistently make their contributions to hitting top line targets on Income Statements over the very long duration audited Income Statement(s) are published to report quarterly earnings, which members of the next client’s Architecture Team collaborated over a very short duration to decide will be made by using; integral parts of Targets System(s), synchronized databases used to integrate parts of Targets System(s), databases, and systems used to maintain databases.

What is also certain – members of the next client’s Architecture Team will collaborate over a very short duration to decide if it is in their enterprise’s best interest to use artificial intelligence or to use forecasting models to forecast the impact of external head/tail winds of future earnings targets, computed using earnings projection model(s).

Who Coined the Term “Targets System”?

One of the #1 Consulting Firm’s Senior System Architects

During an Architecture Team’s collaborations to decide on managers’ metric targets which will be hit for delivering quality manufactured products to customers on-time as promised by using; customer demand forecasting models, Materials Requirements Planning (MRP) models, other supply chain planning models, synchronized databases, and databases maintained by using an ERP System, Al Enzweiler had one of those eureka moments when Rick Savitz*, CFO of Justin Boot Company, said, “We are setting metric targets for every manager responsible for fulfilling and increasing customer demand, because metric targets which get set will get hit to consistently make their contributions to hitting top line targets.”

Next client’s engagement started with members of an Architecture Team collaborating with the team’s Senior System Architect to use their enterprise’s organization chart(s) and Income Statement(s) to architect integral parts of Targets System(s) and synchronized databases used to integrate parts of Targets System(s).

*The #1 consulting firm doing business in the United States and Canada does not publish client’s names, but Rick Savitz, CFO of Justin Boot Company, agreed to have his interview published in an educational video. The video was published in 1998 by the Computer Channel and featured Al Enzweiler marketing the 1998 version of Enzweiler’s Architecture Team Methodology.

Who Coined the Term ERP System?

One of an IT Supplier’s Ecosystem Partners

There is a story told in the IT industry. An IT supplier who had released a Materials Requirements Planning (MRP) System in the 1970s, who had released an MRPII System in the 1980s, released in the early 1990s the third system architected by the IT supplier. Shortly after the 1.0 release of the third system in the United States and Canada, an ecosystem partner coined the term “Enterprise Resource Planning (ERP) System”. The story may or may not be a fact.

It is a fact that; an ERP System can be used to; maintain bill-of-materials, customer transactions, supplier transactions, financial, and other databases which could be analyzed, and which could be synchronized to be used by managers to hit their metric targets using integral parts of Targets System(s) and synchronized databases used to integrate parts of Targets System(s).

What IT Innovations Enabled Using Synchronized Databases?

Extract, Transform, Load (ETL) Tools and Networks

A Senior System Architect can explain how databases maintained by using an ERP System and other systems could be extracted, transformed, and loaded to be the synchronized databases hosted and supported on-premise and/or in the Cloud on virtual private networks (VPNs) used to integrate parts of Targets System(s).

A Senior System Architect can offer sage advice on how before the Internet enabled VPNs, system development tools were used to synchronize databases and how synchronized databases were hosted and supported on-premise on private networks.

What IT Innovation Enabled Databases?

Systems Used to Maintain Databases

In 1974 Al Enzweiler was one member of Holiday Inns’ Architecture Team responsible for completing IBM’s Business System Planning (BSP) system development methodology.

First task to be completed was to interview managers and subject matter experts on the organization charts of the more than thirty (30) enterprises owned by Holiday Inns, to define and document requirements for managing and performing responsibilities.

The Architecture Team documented that; customer transaction systems, accounts receivable systems, supplier transaction systems, accounts payable systems, payroll systems, financial systems, were currently being used by business units on the organization charts of more than 30 enterprises to perform their responsibilities. The team also documented a consolidation system was being used by a financial business unit at the Memphis headquarters to publish Holiday Inns’ audited financial statements required to report quarterly earnings to the SEC, creditors, stockholders, and Wall Street’s analysts.

The Architecture Team documented only one database was being maintained. The database was being maintained by using Holidex.

Holidex was a leading-edge reservation system jointly developed by Holiday Inns and IBM in the early 1970 to take advantage of the IT innovation of using a private network to update databases in “real time.” Holidex digitally transformed the hospitality industry by maintaining a database of business transacted with customers in one or more currencies and by maintaining in real time a database of the number of rooms available to be reserved by customers at Holiday Inns. The Holiday Inns were owned and operated by Holiday Inns and by franchise holders.

The Architecture Team analyzed the databases being maintained by Holidex to discover data correlations. Discovered data correlations were used to; architect, develop, demonstrate, use, and improve models.  The models were used and continually improved by planners and analysts collaborating with system development specialists using system development tools to;

  • Forecast future customer demand for rooms at Holiday Inns
  • Plan to raise the price of rooms to improve margins, when forecasted customer demand was greater than the number of rooms available to be reserved
  • Plan to lower the price of rooms to increase customer demand, when forecasted customer demand was less than the number of rooms available to be reserved

Holiday Inns’ Architecture Team did analyze databases after; Materials Requirements Planning (MRP) systems, production planning systems, inventory management systems, customer transaction systems, accounts receivable systems, supplier transaction systems, accounts payable systems, payroll systems, financial systems, and a consolidation system were; developed, tested, implemented, and went live within budget, as planned by Holiday Inns’ Architecture Team.

Holiday Inns’ Architecture Team would have analyzed databases being maintained by using; social media systems, digital advertising systems, and digital marketing systems, except smart phones and the Internet had not been invented.

In the podcast “Birthing of Hampton Inns” published by No Vacancy, Raymond Schultz the IBM Account Manager who architected and managed to develop Holidex recounts how Kemmons Wilson, the founder of Holiday Inns, told him before Holidex he had to sell Holiday Inn franchises, after Holidex he took orders for franchises.

Any Sage Advice on Using Databases in 2022

Caveat Emptor, a Latin Term for “Let the Buyer Beware”

In an August 13, 2022, article titled “The data is in”, Johnson, the Economist’s columnist on language, decided the Economist will now use the term “data” when the data in question is considered as a mass. Johnson was offered sage advice by a Senior System Architects on how the term “database” has been used since the 1970s when the data in question is considered as a mass, such as a database of products and/or services sold to customers, or a financial database used to publish audited financial statements required to report quarterly earnings.

A reader of the word “database” could easily understand the data in question is a mass. A reader of the word “data” could believe a database is being considered as a concept—as in data is the new oil.

Data is a Latin term and so is caveat emptor. Both terms were coined and used before IT suppliers and their ecosystem partners of; consulting firms, IT advisory firms, IT services firms, academics, and journalists starting coining and using terms for using databases to market their products, services, and publications.