May - Library

MERIT draws data from the Marine’s maintenance, supply,
logistics, and distribution systems as well as 3 rd party suppliers and
transportation systems as shown in Exhibit 4. The technology behind
MERIT is an open-source Java-based programming technique. The
common delivery method is through a web browser using a Java
Applet processed on the server and connected to a data source such
as Oracle, XML or delimited text. The graphical results are embedded
in HTML and displayed by the user’s web browser. The final product
is a small, flexible file that runs on virtually any platform and handles
a large number of users simultaneously.
Exhibit 4. Integrated Data Sources
Supply
Systems
MERIT Honeycomb
Interface
3rd party
Transportation
Systems
Database
(Oracle)
Maintenance
Systems
Depot
Systems
The integration of these data sources and the adaptation to MERIT
was done under a rapid application development (RAD) methodology.
Under this methodology requirements identification, commercial offthe-shelf
(COTS) integration, and database integration were
accomplished in a compressed time frame. Such a flexible,
responsive, and entre p reneurial development approach was well
suited to an environment characterized by rapid changes in IT policy
combined with multiple system modernization objectives. Exhibit 5
illustrates a rapid application development framework.
Traditional IT development approaches are similar to the rigid
design and development process within the construction industry.
R e q u i rements are turned into a building through a slow sequential
Plan Analyse Design Develop Test
Test
Equipment Readiness and Visibility Using Honeycomb Maps
Exhibit 5. Rapid Application Development (RAD) 4
process. Such an approach is reasonable with a building, since the
final product is costly to change or repair once built. However, this is
not the case with software. Software can be developed and designed
iteratively. A working “bare bones” version of the software can be
developed rapidly, and then improved and tested under the strain of
use. As the software is used, another round of re q u i rements and
i m p rovements are then initiated. RAD places working software in the
hands of users much more rapidly than the traditional approach. More
importantly, iterative design methods will provide more realistic and
useful design inputs from users. The user’s imagination is able to
function more creatively within the context of use, than in the context
of planning (hypothetical use).
Thus, the cornerstone of a successful rapid development process
is the production of a useful, working application at the end of each
development cycle. We were able to integrate the data into the first
MERIT prototype in less than three months because business
p rocesses had been defined and re q u i rements existed. Consistent
with rapid prototyping protocol, the users were co-opted into the
p rocess as beta testers. A web site was established where users
evaluated the new tool, responded to enhancements, and contributed
ideas for new improvements. This process lead to an evolving tool
that provided more and more of what the users wanted.
In the next section, we’ll see how weapon systems and program
managers, maintainers, and analysts can access detailed inform a t i o n
to initiate readiness responses.
MERIT Repair Cycle Visibility
Exhibit 6 illustrates the system’s repair cycle management
capability. This illustration simplifies the actual system, by reducing
both the number of data elements and levels within the system.
Assume a light armored vehicle (LAV-25) is in the red zone on the
honeycomb display. Assume the LAV-25 has 15 vehicles authorized
and three are in the maintenance shop, yielding a MR-rating of 80%
(12/15) as of September 15th. Thus, in this example the LAV-25 is in
the “red zone” and requires further analyst attention.
The analyst can click on the LAV-25 cell of the honeycomb map
and connect directly into the equipment maintenance system to
evaluate maintenance status of the LAV- 2 5 ’s. The equipment level
Sequential Development (one cycle)
Compressed Time
Deploy/Plan
RAD interative
Development
(multiple cycles)
Develop
Analyse/Design
Deploy
36