Printer Friendly

Is it AMSS or amiss?

The AMSS report is one of few communications that start at the company level and eventually reach senior Army leaders through the Readiness Integrated Database (RIDB) at the Logistics Support Activity (LOGSA). Those leaders use those company reports to make decisions that send maintenance dollars to units based on their AMSS reports.

Unfortunately, some units either don't file a report or they only take a stab at it, allowing flawed data or mistakes. A flawed report can't be used and is reflected in the system as no report at all.

Real-time maintenance decisions can be affected by trends noted in AMSS reports. If those trends are muddled by lack of reporting or by flawed reports, it can cost the Army dollars, time, and resources.

Obviously, non-reporting can be fixed by reporting. But flawed reports can only be fixed by what NCOs have long called "Attention to Detail."

Wrong report period date

Some units make the mistake of using the last reporting period's Julian date instead of using the current reporting date, so the report becomes invalid.

Wrong report date

Another case of lack of attention to detail. The date must be the 15th day of the reporting month. Enter the Julian date for the 16th and your report is invalid.

Unofficial unit identification code (UIC)

Don't use unofficial UICs created locally for property book uses. Use only the UICs recognized by the Army Status of Resources and Training System (ASORTS).

Wrong end item code (EIC) or weapon EIC

The EIC/WEIC must be a reportable item in the Maintenance Master Data File (MMDF).

Wrong utilization codes

Only use the authorized readiness utilization codes that are found in Para 2-4a, AR 700-138.

Impossible possible time

This reflects the possible days in the reporting period. Because the report is based on monthly cycles, the only possible numbers are 28, 29, 30 and 31.

Wrong format or length

The ULLS box saves the report in a specific format. People who then open the report in a word processor or spreadsheet cause unseen hard characters to corrupt the data which SAMS-2 boxes interpret as line breaks. The corrupted data cannot be read at LOGSA.

Checking Your Submissions

You can use the RIDB Feedback Reporting Statistics (All) or the Executive Summary Current View reports to verify that LOGSA received your unit's readiness data.

The feedback and executive summary reports are available through the Logistics Information Warehouse (LIW):

You'll find the feedback report within LIW follows this progression sequence: WebLIDB Readiness RIDB, Feedback Reports. Data can be presented by MACOM-level first. But the user can drill down to the unit by clicking on increasingly subordinate units.

The AMSS report isn't just a paperwork drill. It means maintenance dollars for your unit in the future and it helps senior Army leaders make real-time decisions based in part on trends in AMSS reporting. This is one report you want to get right every month.
COPYRIGHT 2007 PS Magazine
No portion of this article can be reproduced without the express written permission from the copyright holder.
Copyright 2007, Gale Group. All rights reserved. Gale Group is a Thomson Corporation Company.

Article Details
Printer friendly Cite/link Email Feedback
Title Annotation:Reporting ...
Publication:PS, the Preventive Maintenance Monthly
Date:Feb 1, 2007
Previous Article:Things up.
Next Article:Understanding the PS magazine issues and index webpage.

Related Articles
What do you have in your bird?
Got matches?
Let maintenance reports support your budget.
Corrosion team update.
What to carry or not carry?
Storing AMSS kit for missions.

Terms of use | Privacy policy | Copyright © 2022 Farlex, Inc. | Feedback | For webmasters |