|
Business Systems Engineering
Business success has historically depended on focusing
on principles of:
- discipline(s),
- resources, & opportunity,
- planning
And most recently
The degree of successful business and not-so-successful
business outcomes have been the result of addressing these principles
in varying degrees of intensity and combinations.
The orchestration of applied principles to the numerous
functions within the BUSINESS ENVIRONMENT is the hallmark of PRMEAs
success.
- The basics of Discipline
- QUALITY OF CUSTOMER SATISFACTION
- Mission and Objectives of the business at hand
- The establishment of an infrastructure that supports the
mission and objectives
- The development of business processes that will serve the
business needs and align the numerous functions into a System-of-Systems.
- The appropriate checks and balances for control
- The basics of Resources and Opportunities
- Finance and Accounting Systems
- Human Resources Systems
- Marketing and customer relation systems
- Information Systems
- Applied technology and communications (properly aligned)
- Marketing Analysis
- Contracting, Procurement & Materials Control
- Planning applies to all of the above in the following forms
- Strategic Planning
- Operations Planning
- Cost and Budgeting development and controls
- Cost vs. Benefit Analysis
- Performance Measurement and Evaluation(s)
- Risk assessment and mitigation strategy
PRMEA delivers the optimum
combinations of these business elements and meld them into a technology
appropriate recipe for success, addressing the combined functions
of the specific business model.
Enterprise Resources Planning
(ERP)
(The Start of a Digital Nervous System)
Our experience with the ERP systemss can be described
as that of being the "master planner" who will insure
client satisfaction by developing an uncommonly precise scope definition,
statement-of-work, system(s) specification and operations blueprint
(data mapping and functional flow diagramming). ALL of which is
user defined and accepted. USER in this context are ALL persons
from the Chairman-of-the-Board, to the hands-on performer. USER
satisfaction must be the proof of a successful implementation. Most
importantly, the solution must not cost more than it is worth.
Let us recognize ERP for what it is.
ERP is a set of integrated applications that record
actual cost as they occur within spe-cific functions. Those actuals
are definable and organized to meet predefined specifica-tions.
The details of those specifications and subsequent architecture
of the recording processes are a critical step in successfully implementing
an ERP system. (This effort is, in my opinion, the single most important
reason ERP implementations are so costly and unsatisfactory to the
customer).
The implementation of the ERP is not the most user-friendly
experience a company will experience. Today's ERP is a disciplined
architecture that does not flex to the company functional idiosyncrasies.
Our observation is that of the client not understanding the in-herent
structure of the ERP and assumes the implementation will adjust
to the workplace.
The implementers assume the client understands the
adjustments needed to be made in the functional processes of the
workplace and proceeds to adapt the ERP modules to as close a fit
as possible.
During this "dance-of-assumption", no one
has included the functional workplace user in the schema of the
implementation; their current methods, concerns, fears, undocumented
steps of performance, needs and wants for a better work place.
PRMEA would function
as an orchestrator and conductor of an implementation. Imagine if
you will that the implementation team is a symphony of effort performed
by numerous persons. Some of which are the ERP vendor, some are
the client representatives, some are the hands-on user community
and for the enhancement, some are the EVM (Earned Value Management
System) practitioners.
PRMEA would make sure
we are playing from the same book of "music" with full
un-derstanding of the score and its arrangement to the client needs,
at the workman's level. PRMEA will maintain harmony and the cadence
because PRMEA understands the ele-ments
of the ERP, more important PRMEA
understands the value of melding in the EVM. ERP + EVM = MICS (Management
Information Control System) The system-of-systems and the digital
nervous system.
|