Arjen said:
Source:
http://www.dote.osd.mil/pub/reports/FY2011/
[...]
The program failed to design the unit-level ALIS hardware for deployability. The squadron operating unit weighs 2,466 pounds and measures 79 inches high by 40 inches deep and 24 inches wide. It also requires climate-controlled'environments. The program worked through late 2010 and 2011 to redesign the system and provide improved deployability by late 2014. However, there is no plan for end-to-end testing of the system, and funding of retrofits or changes to the units that will be purchased in the meantime. The problem needs correction in order to take advantage of F-35 capability in forward operating locations expected in combat.
Data Quality and Integration Management (DQIM) is a vital part of the autonomic logistics global sustainment plan for the F-35. The ALIS version 1.0.3 is supposed to incorporate DQIM; however, missing data elements (e.g. part number, logistics control number, serial number) of vendor supply databases have prevented timely testing and fielding of ALIS version 1.0.3. This results in the development of manual data tracking processes for early LRIP aircraft. The program expects to have DQIM data products available to support ALIS 1.0.3 fielding in May 2012.
quellish said:
Many of the issues I've outlined - most - are not system maturity issues but design issues. While ALIS certainly has issues stemming from system maturity, there are many issues that are due to the design or architecture of the system.
I agree with quellish: ALIS has serious design issues. ALIS redesign/modification isn't due to deliver until late 2014; implementing a job that big without end-to-end testing of ALIS seems like bad management to me.
This is in reply to GTX's complaint about me picking up 'factoids' and subsequently blowing them up to calamity level.
My day job involves software development and implementing changes in testing and production environment. I went through DOT&E's 2011 report in search of information on ALIS's status and found some fairly disturbing 'factoids' concerning ALIS's design
1) ALIS as in use in 2011 is not designed for deployability (by the way: I never wrote redesign for deployabilty meant total redesign for ALIS)
2) in 2011, deficiencies in ALIS's <edit>
datamodel database</edit> were such that testing and fielding Data Quality and Integration Management (DQIM) was severely impaired
I take it both 'factoids' have been recognized by project management as serious issues and are being acted upon. So far, so good.
ALIS redesign for deployability is not to deliver field results until late 2014. This implies redesign and subsequent implementation is a major effort, entailing significant changes to ALIS. Not bothering with end-to-end testing of such big changes, nor taking into account the cost of retrofits or changes to equipment already in use, to me speaks of a cavalier attitude to project management. Act in haste, repent at leisure. As for the reliability of promises for solving this issue by late 2014: I will believe it when I see it.
Just as disturbing, after this many years of development, was the absence in ALIS's database
of <edit>data-entities 'data elements (e.g. part number, logistics control number, serial number) of vendor supply databases' </edit> critical to implementation of DQIM, resulting in 'the development of manual data tracking processes for early LRIP aircraft', directly affecting operating costs. The DOT&E report stated this was to be remedied by May 2012. Other people may know if this has been achieved.
<edit>The absence of these data points to either
- sloppy data-modeling, or
- a persistent communication problem between vendor supply databases and ALIS, or
- insufficient/incompatible bookkeeping by vendors
This is not an exhaustive list of possible causes, but an issue of this kind, this late in development, is another pointer at defective project management.</edit>
GTX made a point of ALIS's issues being mainly immaturity issues, I repeat I'm of the opinion that ALIS has serious design issues. For ALIS to be 'mainly' suffering from immaturity, would mean, in my opinion, those immaturity issues to be even bigger. As for 'calamity', that's GTX's choice of words, not mine.