Skip to main content

Interim Report on Air Force Base Level Automation Environment Report to the Department of the Air Force (1986) / Chapter Skim
Currently Skimming:

II. Summary of Findings and Recommendations
Pages 5-12

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 5...
... c. The Air Force has taken important initial steps to evolve toward a more powerful post-Phase IV base-level system, but significant tasks remain.
Read the entire page →
From page 6...
... However, The Air Force needs an explicit policy statement to provide direction for future base-level automation efforts. O A first cut has been made at defining a framework or system architecture for future base-level information systems, but difficult technical issues*
Read the entire page →
From page 7...
... of modern software productivity fools, commercially available applications packages, or prime contractors in a base-level software development rode. O This failure to use modern, available tools and capabilities appears to stem from internal Air Force policies and traditions, a major hardware replacement without modernization of application software, and the fragmentation of responsibility for the base-level automation environment.
Read the entire page →
From page 8...
... Specify a standard Air Force base-level automation configuration, using the following suggestions as guidelines: o Specify the minimum set of hardware, system software, local area networks (LAN) , and off-base interfaces that will be present at Air Force bases, so that systems designers wild know that at least the minimum facility wild be present and can design accordingly.
Read the entire page →
From page 9...
... Recommendation f4 - System Program Office/Prime Systems Contractor Concept. Establish an Air Force System Program Office (SPO)
Read the entire page →
From page 10...
... This concept would be particularly useful in the development of automation systems to support the integrated logistics system and operations/combat support systems. O Survey commercially available software development and maintenance tools and acquire those determined to be most suitable .
Read the entire page →
From page 11...
... CORRESPONDENCE OF FINDINGS AND RECOMMENDATIONS FINDINGS 1. ...the Air Force is doing a good job of base-level automation, but much more remains to be done.
Read the entire page →

Key Terms

  • adp support
  • standard air
  • replacement program
  • enhancement plan
  • policy statement

  • critically dependent
  • software development
  • automation configuration
  • normal peacetime
  • communications arrangements

  • force prepare
  • prime contractors
  • software productivity
  • peacetime mission
  • explicit policy

  • documented plan
  • advanced concepts
  • strongly recommends
  • wartime operations
  • future air

  • reps aced
  • contractor concept
  • significant technological
  • capabilities appears
  • minimum set

  • operational peacetime
  • force policies
  • term resource
  • resource requirements
  • probably save


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.