|
Defense Business System Modernization & Automated
Technology
House Rpt.108-767 addresses legislative
concern over Business System Modernization (BSM) accountability.
Specifically there is concern over wasted expense, time delays,
and even the possibility of complete failure in the attempt to
modernize DoD business systems. Many of the problems encountered
by BSM involve the procurement and interoperability of Commercial
Off The Shelf (COTS) products meant to replace legacy systems.
Consideration has been given to modernizing existing legacy
systems, but not to the degree it should given the advancements
in Automated System Modernization (ASM). When examining
congressional mandates for Defense business
systems: architecture, accountability, and
modernization, BSM managers should include ASM
technology in their strategic planning.
Excerpts
from theRONALD W.
REAGAN NATIONAL DEFENSE AUTHORIZATION ACT FOR FISCAL YEAR
2005have been reproduced below and augmented with
explanations for the appropriate use of ASM to meet listed
requirements, reduce costs, shorten project time lines, and
mitigate risks.
Wherever
used, the acronym ASM implies (at a minimum) that 100% automation
is used for a complete system modernization, including: (1)
transforming the legacy software language(s) into C++, C#, Java
or other modern object oriented language; (2) re-factoring the
code to eliminate redundant and dead code; (3) integrating with
an appropriate modern database; (4) web-enabling the system when
appropriate; (5) retaining the look, feel, and functionality of
the original legacy system. It should be noted that the
capability to perform these tasks has already been demonstrated
in over 25 projects and that each of these projects was
successfully completed quickly, cost effectively, and accurately
by a US based company.
Scroll
through the excerpts below to consider the ASM inclusions and
Case Studies.
[House Rpt.108-767] - RONALD W. REAGAN
NATIONAL DEFENSE
AUTHORIZATION ACT FOR FISCAL YEAR 2005
__________________________________________________________
`Sec. 2222. Defense business systems: architecture,
accountability, and modernization
`(a) Conditions
for Obligation of Funds for Defense Business System
Modernization- Effective October 1, 2005, funds appropriated to
the Department of Defense may not be obligated for a defense
business system modernization that will have a total cost in
excess of $1,000,000 unless--
`(1)
the approval authority designated for the defense business system
certifies to the Defense Business Systems Management Committee
established by section 186 of this title that the defense
business system modernization--
`(A) is in compliance
with the enterprise architecture developed under subsection
(c);
ASM adheres
to best practices with Architecture Driven Modernization (ADM) as
outlined by the Object Management Group (OMG).
`(B) is necessary
to achieve a critical national security capability or address a
critical requirement in an area such as safety or security;
or
`(C) is necessary to
prevent a significant adverse effect on a project that is needed
to achieve an essential capability, taking into consideration the
alternative solutions for preventing such adverse effect;
and
In some cases
unsupported legacy hardware begins to fail having a significant
and immediate adverse effect. ASM is quick, low cost and
effective, whether it is considered a permanent or interim
solution. [Case Study]
`(2) the certification by the
approval authority is approved by the Defense Business Systems
Management Committee.
`(b) OBLIGATION OF FUNDS IN
VIOLATION OF REQUIREMENTS- The obligation of Department of
Defense funds for a business system modernization in excess of
the amount specified in subsection (a) that has not been
certified and approved in accordance with such subsection is a
violation of section 1341(a)(1)(A) of title 31.
`(c) Enterprise
Architecture for Defense Business Systems- Not later than
September 30, 2005, the Secretary of Defense, acting through the
Defense Business Systems Management Committee, shall
develop--
`(1)
an enterprise architecture to cover all defense business systems,
and the functions and activities supported by defense business
systems, which shall be sufficiently defined to effectively
guide, constrain, and permit implementation of interoperable
defense business system solutions and consistent with the
policies and procedures established by the Director of the Office
of Management and Budget, and
`(2) a transition
plan for implementing the enterprise architecture for defense
business systems.
Stringent DoD
architectural requirements are met with ASM. Homogeneous systems
are created by targeting the modern software language(s) of
surrounding systems requiring interoperability. [Case Study]
`(d) COMPOSITION
OF ENTERPRISE ARCHITECTURE- The defense business enterprise
architecture developed under subsection (c)(1) shall include the
following:
`(1)
An information infrastructure that, at a minimum, would enable
the Department of Defense to--
`(A) comply with all
Federal accounting, financial management, and reporting
requirements;
Automated
system enhancements and modernizations meet Congressional
financial reporting mandates. [Case Study]
`(B) routinely
produce timely, accurate, and reliable financial information for
management purposes;
`(C)
integrate budget, accounting, and program information and
systems; and
`(D)
provide for the systematic measurement of performance, including
the ability to produce timely, relevant, and reliable cost
information.
`(2) Policies,
procedures, data standards, and system interface requirements
that are to apply uniformly throughout the Department of
Defense.
`(e) COMPOSITION
OF TRANSITION PLAN- (1) The transition plan developed under
subsection (c)(2) shall include the following:
`(A) The acquisition
strategy for new systems that are expected to be needed to
complete the defense business enterprise architecture.
`(B) A listing of the defense
business systems as of December 2, 2002 (known as `legacy
systems'), that will not be part of the objective defense
business enterprise architecture, together with the schedule for
terminating those legacy systems that provides for reducing the
use of those legacy systems in phases.
`(C) A listing of the legacy
systems (referred to in subparagraph (B)) that will be a part of
the objective defense business system, together with a strategy
for making the modifications to those systems that will be needed
to ensure that such systems comply with the defense business
enterprise architecture.
Most legacy
systems that are retained as part of the defense business system
will require modifications. ASM includes fully automated and
semi-automated refactoring strategies to modify the software
after its transformation into a modern target language. By
re-factoring (re-engineering) object oriented code compliance
with the defense business enterprise architecture is ensured.
Other 'half-way' system modernizations, such as wrapping and
re-hosting the legacy code, may require that modifications be
made within the legacy language, require the procurement of
middle wear for inter-operability, and add architectural
constraints. [Case Study]
`(2) Each of the strategies under
paragraph (1) shall include specific time-phased milestones,
performance metrics, and a statement of the financial and
nonfinancial resource needs.
ASM provides
incremental phases with testing following each phase.
Deliverables for each phase are firm
fixed-price.
------NOTE:
Accountability and Congressional reporting sections have been
removed ------
`(j) Definitions-
In this section:
`(1)
The term `approval authority', with respect to a defense business
system, means the Department of Defense official responsible for
the defense business system, as designated by subsection
(f).
`(2)
The term `defense business system' means an information system,
other than a national security system, operated by, for, or on
behalf of the Department of Defense, including financial systems,
mixed systems, financial data feeder systems, and information
technology and information assurance infrastructure, used to
support business activities, such as acquisition, financial
management, logistics, strategic planning and budgeting,
installations and environment, and human resource
management.
`(3)
The term `defense business system modernization' means--
`(A)
the acquisition or development of a new defense business system;
or
`(B)
any significant modification or enhancement of an existing
defense business system (other than necessary to maintain current
services).
While
ASM
facilitatessignificant modifications and
enhancements, it is also the best choice to maintain
current services. Cost savings over a COTS solution are
achieved because functionality is retained and end-users require
no additional training on a new system. [Case Study]
`(4)
The term `enterprise architecture' has the meaning given that
term in section 3601(4) of title 44.
`(5)
The terms `information system' and `information technology' have
the meanings given those terms in section 11101 of title
40.
`(6)
The term `national security system' has the meaning given that
term in section 2315 of this title.'.
In
conclusion, most major IT integrators are already aware of ASM
capabilities. However, it is our belief that Business Systems
Modernization decision makers need a better understanding of this
Artificial Intelligence (AI) based technology. Only then will
automated solutions be appropriately included in the global
planning of business systems modernization. For more information
on the automated services available for Business System
Modernization contact the
referenceslisted below.
|