Encl (1) to. COMDTINST 5230.53
and in compliance with recent mandates to develop process and
resultsmeasurements, such as the Government Performance and Results Act of
1993, Executive Order 12862 regarding customer service standards, and
COMDTINST 5224.9A (TQM Measurement). In each instance, the Legal
Program must be able to generate hard data. Used correctly, the LAWS-db
will provide this capability.
C.
Ease of Use. The LAWS-db was designed with the user in mind. When the user
logs into his or her computer, the database can be automatically opened in Context
Manager, where it remains available at all times, only a keystroke away. Only a few
entries are required to open or close a case, and on-screen help is available for
virtually every item. Pop up option windows are provided for entry of
supplementary information, and user level scheduling, reporting and case finding
tools require just a few key strokes.
II.
REQUIREMENTS.
A.
LAWS-db "Cases".
1.
The LAWS-db is structured.around the concept of a "case." For the most part,
each "case" is a separate "legal matter." For instance, each civil penalty appeal,
court-martial, mast, bridge regulation, administrative investigation, FTCA
claim, etc. generates an individual "case" in the LAWS-db. The concept of a
"case" needs to be more encompassing, however, because the LAWS-db is
inteended to gather information about each legal office and division's enter
work load*. Users also need to track QAT/NWGs, telephonic advice, training
time, recruiting visits, etc., even though these are not "cases", per se.
2.
To reduce the data-collection burden, offices may choose to group legal
matters not normally considered "cases" into single "consolidated" LAWS-db
cases. For instance, for Legal Program purposes it is not necessary to track
each individual phone call for advice as a separate LAWS-db case. Instead,
legal offices can collect this type of
________________________________________________________________________________
1
The term "work load" is intended to define the amount of time devoted to supporting all clients
even yourself, such as when you attend CLE (the Program supported would be Legal (GAL)).
"Work load" does not include "overhead". Consequently, users should keep track of training time, time spent in general TOM meetings (i.e., a
OMB, NOT a OAT/NWG dealing with a particular subject, and thus a particular program client), and professional reading (case type
"Training", program "GAL"). On the other hand, users need not keep track of routine administrative time such as time spent reading routine E-
Mails and general in box material, taking voice mail messages, etc. "Management" time also would be considered "overhead." Thus, time
spent by the Legal Officer/Division Chief/Ass't Chief managing the Office/Division need not be tracked.
3
Previous Page
