BARS/CLAS IMPLEMENTATION WORKING GROUP

• Document Type: CREST
• Collection: General CIA Records
• Document Number (FOIA) /ESDN (CREST): CIA-RDP90-00191R000100060031-3
• Release Decision: RIFPUB
• Original Classification: U
• Document Page Count: 4
• Document Creation Date: December 23, 2016
• Document Release Date: October 24, 2013
• Sequence Number: 31
• Publication Date: June 15, 1987
• Content Type: MISC

Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
UNCLASSIFIED
BARS/CLAS Implementation Working Group
15 June 1987
This paper defines an approach to exploring and investigating issues which must be understood to the extent possible to create a
master project implementation schedule.
This is a proposal developed by the OIT technical team, so that customer feedback may be obtained and incorporated as part of the
working group in the development of the BARS/CLAS master schedule.
Specific questions which must be answered as part of this group are broken down into three categories;
1. Background Information
2. New Requirements
3. Implementation Specific Questions
BACKGROUND INFORMATION-
The purpose of this category is to bring the project team up to speed with sufficient background information to understand
implementation issues. Since no specific requirements for the implementation of the packages are currently available, knowledge
of the current systems will help provide an understanding of requirements. These questions will be addressed at a very high
level.
Ti F2 1.) What are the major functional features of the current systems?
Ti 2.) What are the input and output of the current systems?
T1 F2 3.) What are the interfaces to/from the current systems?
Ti DBC82 4.) What are the security access restrictions of the current systems?
5.) What are the requirements for internal and external reports?
6.) What are the interfaces with systems external to the Agency?
What external policies, regulations, and statutory requirements have guided the development
of the current systems and what factors should be considered to facilitate adaptation to future
external requirements and policies?
8.) What are the database and operational environments of the current systems?
9.) What system architectural changes will impact the existing systems and what are the
implications of changes or modifications to the current IDMS?
10.) What are the basic policy assumptions of the current systems and how are these assumptions
likely to change, e.g.,
UNCLASSIFIED
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
(Same)
(same)
(same)
(same)
(new)
(new)
(new)
(new)
(new)
(new)
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
UNCLASSIFIED
PAGE 2
a. cash basis vs. accrual accounting
b. obligation based budgeting and accounting
c. use of revolving funds
d. single year vs. multi-year appropriations
e. costs vs. obligations, etc.?
11.) How will changes to current software package development impact current implementation plans? (new)
NEW REQUIREMENTS-
The purpose of this category is to explore various possibilities of implementation requirements. These questions investigate the
dependency on the availability of the 1.3 Release of the package software and other pertinent questions which require technical
team development efforts. These questions will be addressed at a concept level at first with further detailed investigation in
process warrants.
certain areas
as the
VI
F2
BEP/80P3
12.)
VI
U2
13.)
VI
F2
80P3
14.)
UI
VI
F2
15.)
VI
16.)
VI
17.)
Fl
18.)
Fl
19.)
20.)
What features can be implemented with the 1.2 version?
If we go with 1.2, what workarounds are needed and what are the risks involved?
What features will be available in 1.3?
What are the missing functions and how do we handle them?
What are Cullinet's implementation requirements for the specific packages and
functionality within those packages?
What is needed and where for data loading?
Which interfaces will require redesign or modification (19X, Payroll, STARS, ABF,
FMS, FARS, FEDSTRIP/MILSTRIP, External Agency Systems, etc.)?
What are the new security access requirements?
What are the differences in essential financial operations that are performed in a
commercial concern as opposed to an agency of the Federal Government?
a. What types of financial activities are unique to governmental operations?
b. How well has the needed package software identified and accommodated the similarities
and differences between commercial vs. governmental requirements?
c. What are the specific Agency functions which do not appear to have been adequately
developed and incorporated into existing software products?
d. Are there any governmental functions, such as accounting for commitments and
obligations, that are so fundamentally different that they should be executed
with new packages rather than with modified existing packages that were developed
initially for commercial use?
What are the implications of attempting to implement automated non-governmental
procedures into an obligation based system when funds control requirements are
paramount?
(same)
(same)
(same)
(same)
(same)
(same)
(modified)
(same)
(new)
21.) Is there a viable alternative to on-line real time funds availability checks? (new)
a. What do we gain from an interim, batch control, funds availability check?
UNCLASSIFIED
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
UNCLASSIFIED
22.) What are the problems inherent in implementing a system that does not provide for (new)
on-line certifications alid administrative approvals?
a. What accommodations can be made to allow the new system to function effectively
without these capabilities?
23.) How will we integrate the payroll system to meet existing accounting and reporting (new)
requirements?
24.) What archival requirements should be considered? (new)
IMPLEMENTATION ISSUES
PAGE 3
The purpose of this category is the explore specific implementation issues. These issues will be explored extensively and will
consistute the basis for the development of a master BARS/CLAS project schedule defining system deliverables. The investigation
of these issues will be pursued so that a low risk, stategic and viable BARS/CLAS schedule may be formulated.
Ti F2 25.) Are there any packages (or parts of packages) that can be implemented without reference (modified)
to fiscal year constraints?
Fl 26.) What specific problems are inherent in fiscal year-end accounting and reporting that (modified)
do not arise in normal month-end processing?
Ul T2 27.) Can a package be implemented with required functionality that is missing; and if so, (modified)
can the missing functionality be maintained in an existing system?
28.) How can the conversion of data be accomplished in the most efficient and expeditious manner? (modified)
29.) Is there a need to run a parallel test? (modified)
LAS
a. Do the BARS/requirements lend themselves to a pilot environment?
30.) What are the advantages of implementing AP, PUR, and GL without funds control? (new)
31.) What are the specific training requirements that should be incorporated into a (new)
comprehensive training plan, e.g.,
KEY
a. Who will require training?
b. What type of training should be conducted?
c. Who will serve as instructors?
d. Where will the training be held?
e. When will the training be given? Etc.?
32.) What kind of documentation (internal & external) is required during and after implementation? (new)
33.) What are the additional resources required to implement the new system? (new)
UNCLASSIFIED
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
4
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
DBCB- 011/Operations Group/Database Control Branch
T- Technical Support Team of Current Systems
F- Functional Experts
U- Us- The Planning Working Group
BEP- Bureau of Engraving and Printing
BOP- Bureau of Prisons
UNCLASSIFIED
?
UNCLASSIFIED
Declassified and Approved For Release 2013/10/24: CIA-RDP90-00191R000100060031-3
PAGE 4