23.02.2013 Views

Do Stryker Brigade Combat Teams Need Forward Support ...

Do Stryker Brigade Combat Teams Need Forward Support ...

Do Stryker Brigade Combat Teams Need Forward Support ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

previous diagnoses and provides the statistically most<br />

likely disease (fault) and treatment (repair).<br />

The medical profession has done well to embrace<br />

evidence-based medicine; the Army maintenance community<br />

also might do well to embrace evidence-based<br />

maintenance. Not only would such a system speed<br />

troubleshooting and proper fault diagnosis, it would<br />

also perform the same function as prognostics by supporting<br />

the building of better authorized stockage lists.<br />

It would also provide a better grasp of whole-life and<br />

life-cycle costs. A system like this for Army maintenance<br />

could limit misdiagnosis of vehicle faults. An<br />

evidence-based maintenance system would reduce the<br />

multicapable maintainer’s reliance on his intuition to<br />

make sound repair decisions and allow him to diagnose<br />

problems and correct them. His data then could<br />

be included in later regressions to ensure that faults<br />

were categorized correctly.<br />

The program should be able to determine the result<br />

statistically. For instance, if the maintainers normally say<br />

that a certain fault is found during testing, we could probably<br />

determine what the true fault usually is (and more<br />

importantly, what the fix is) or if the “how found” data<br />

mean nothing to the outcome. I would say, at this point,<br />

that we do not really know if these data mean anything,<br />

because we have “intuitively” said they mean nothing.<br />

The most intriguing benefit of intelligent fault diagnosis<br />

is that it eliminates the need for the intuition of<br />

the maintainer. A maintainer’s intuition results from his<br />

general maintenance experience, training, and experience<br />

with the given piece of equipment. We need to<br />

find a way to capture the shop data and fault data from<br />

the Standard Army Maintenance System Enhanced or<br />

from a Department of the Army Form 2407, Maintenance<br />

Request, database that captures the “how found”<br />

data and ties them directly to the “how repaired” data.<br />

Collecting Data<br />

With the advances in controller area network bus<br />

technology over the past 10 years, several large commercial<br />

truckers have developed evidence-based service<br />

regimens based on what they have learned from<br />

their electronic monitoring systems. The Army needs<br />

similar systems that will support “fight with what you<br />

brought” because new prognostic-laden equipment and<br />

smart vehicle systems will not be widely used for years<br />

to come, but evidence-based maintenance is available<br />

today. It also would be free because the data are<br />

already there—just not being used. Worse yet, we are<br />

losing the information by not properly archiving it.<br />

We have all the tools needed to use evidence-based<br />

maintenance without adding anything to the vehicle<br />

systems in current inventory. The type of bus used<br />

on virtually all heavy vehicle systems has the data we<br />

46<br />

need and stores them quite accurately, but we rarely<br />

interrogate it.<br />

Onboard Sensors<br />

One might do well to study exactly what commercial,<br />

even consumer, products provide. OnStar<br />

offers a level of condition-based maintenance to the<br />

consumer. My truck lets me know, based on my driving<br />

habits over the past few months, that it will need<br />

an oil change soon. The onboard computer sends a<br />

message that generates an email telling me I am down<br />

to a percentage of oil life remaining. Lo and behold,<br />

a few days later my service engine light illuminates.<br />

Granted, all of this is done with the assistance of a few<br />

sensors, but I think more weight is given to the “profile”<br />

of miles driven (such as revolutions per minute<br />

duration) than to the oil condition itself.<br />

Time and time again, I read on LOGNet about the<br />

need for simpler vehicles that align with the workload<br />

and skill set of the Army maintainer. Perhaps the greatest<br />

single issue that comes up is the complexity of maintaining<br />

a central tire inflation system (CTIS). Soldiers<br />

in the field seem to be content with vehicles that do not<br />

have CTIS or that have disabled CTIS systems. CTIS is<br />

a complex system, and many fleets still do not have it. I<br />

am not privy to the results of the surveys that take place,<br />

but I think units in the field have overwhelmingly said<br />

they do not want CTIS systems since any prognostics<br />

undoubtedly will increase the cost of the vehicles and<br />

make them inherently more difficult to maintain. Maintainers<br />

do not want to have more complicated vehicles<br />

unless they have the proper tools and adequate knowledge<br />

and understanding of the vehicle system. A proper<br />

tool, in this case, would be a diagnostic system that has<br />

the information needed to diagnose a fault properly with<br />

a high degree of accuracy.<br />

Anything less than having a high degree of accuracy<br />

in troubleshooting diagnoses equates to simply changing<br />

parts. If we know more about the predicted actual<br />

fault, we can eliminate some of the practice of “changing<br />

parts until the fault goes away.” More importantly,<br />

we might be able to use the data to redesign our resupply<br />

operations. To shrink the logistics footprint, we need to<br />

do several things. If we are not going to make vehicles<br />

simple, we need to make diagnosis simpler. We can do<br />

it without adding anything to the ground fleet.<br />

Staff Se r G e a n t MichaeL wi n K L e r iS a Senior e D i t o r<br />

a n D c o u r S e w r i t e r f o r t h e LeaDerShip DeveLopMent<br />

Directorate, 84th ar M y reServe reaDineSS tr a i n i n G<br />

co M M a n D, at fo r t Mcco y, wiSconSin. he h o L D S<br />

a bacheLor o f buSineSS aDMiniStration D e G r e e f r o M<br />

Marian coLLeGe a n D a MaSter o f buSineSS a D M i n i Stration<br />

D e G r e e f r o M in D i a n a weSLeyan univerSity.<br />

JULY–AUGUST 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!