AUTOMATED CONTRACT INFORMATION

Document Type: 
Collection: 
Document Number (FOIA) /ESDN (CREST): 
CIA-RDP85B00803R000200010013-8
Release Decision: 
RIPPUB
Original Classification: 
K
Document Page Count: 
1
Document Creation Date: 
December 15, 2016
Document Release Date: 
December 3, 2003
Sequence Number: 
13
Case Number: 
Publication Date: 
November 29, 1966
Content Type: 
REPORT
File: 
AttachmentSize
PDF icon CIA-RDP85B00803R000200010013-8.pdf60.44 KB
Body: 
Approved For Release 2004/01/29: CIA-RDP85B00803R000~9019891?i-ger 1966 AUTOMATED CONTRACT INFORMATION Initial system (mid-1966) allowed for periodic input of contractor and inspection reports under "Due" and "Received" headings but the program was not capable of selecting only the latest data in such a periodic field nor could it compare a due date with a received date to determine that a report was overdue. During the first four or five months of the initial system's life, special requirements placed more of a burden on the system that the regularly scheduled items. Requirements of the system written into the Project Officer's Handbook meant modifying, converting or reprogramming the existing machine routines. After generally surveying the rgmts for a total integrated management information system, I have concluded that such a system is not really feasible without on-line remote terminals. This conclusion is concretely supported by the experience of organizations who have successfully implemented such applications. These applications are few in number to date due to lack of experience by computer systems analysts and programmers in their use. Generally speaking, usage design is five years behind hardware availability. Each day of delay increases this lag exponentially. OCS is no exception and is just begin- ning a 12-18 month experimental phase with a few remote installations. DDS&T should definitely be involved in the experimental stage for several reasons: 1) We shld set the example for the offices, some of whom have already ordered remote terminal installations. 2) The usage experience, even in experimental stage is as important to us as to the software designers. 3) The contract information file can be updated on a daily and errorxee basis and made quickly responsive to a variety of random I4ueries by all levels ofmanagement, as envisioned by the Handbook. 4) It will promote design flexibility for expansion of this basic system to include other data bases. (This impinges on the DDS responsibility for designing a total information system which is a major influence on the thinking of the Director of OCS in responding to rqmts with his limited /s/ STAT Approved For Release 2004/01/29 : CIA-RDP85B00803R000200010013-8