DEFENSE SECURITY COOPERATION AGENCY  2800 DEFENSE PENTAGON  WASHINGTON, D.C. 20301-2800	12/16/2002

MEMORANDUM FOR :

DEPUTY ASSISTANT SECRETARY OF THE ARMY
FOR DEFENSE EXPORTS AND COOPERATION
ATTN: DASA (DE&C)/SAAL-NP
DEPARTMENT OF THE ARMY

DEPUTY ASSISTANT SECRETARY OF THE NAVY
(INTERNATIONAL PROGRAMS)
DEPARTMENT OF THE NAVY

DEPUTY UNDER SECRETARY OF THE AIR FORCE
(INTERNATIONAL AFFAIRS)
DEPARTMENT OF THE AIR FORCE

SUBJECT :

Security Cooperation Information Portal Configuration Control Board (DSCA Policy Memorandum 02-44)

DSCA is in the process of testing and deploying a new Security Cooperation Information Portal (SCIP). The SCIP was demonstrated for the first time at our Security Cooperation 2002 Conference and will allow security cooperation personnel, including our international partners, to have a tri-Service view of selected foreign military sales case-related data. I look forward to this new capability and the benefits it will provide to our community. The efforts of your organizations to define requirements for the SCIP and to supply data extracts from your legacy systems have been key to our success with this project.

As we begin SCIP deployment, it is important to think ahead to what it will take to maintain the integrity of a production environment. We must carefully consider and monitor any changes to the system. With this in mind, the time has come to establish a SCIP Configuration Control Board (CCB) effective immediately. The purpose of the board is to review any proposed changes to the SCIP production functionality to ensure these changes are consistent with approved policies. Each change will also be reviewed for necessity and prioritized accordingly before being submitted for programming action.

The SCIP Program Manager (Mr. Tom Sippel) will review all proposed changes submitted and will control those that involve data fixes, system integrity, security, technology upgrades, and software "bugs." The Program Manager will bring any concerns to the SCIP CCB for resolution. No changes or enhancements to business functionality will be made to the SCIP without the approval of the SCIP CCB. Currently, the functionality requirements for the SCIP are "fixed." The SCIP is intended to be the near-term solution to the lack of consistent TriService information---our long-term solution being the Case Execution Management Information System (CEMIS). After the CEMIS Analysis of Alternatives (AOA) is completed, we may find that an expansion of the Portal functionality would be consistent with the plans for CEMIS. Until that analysis is completed, requests for functionality enhancements to SCIP will be held for future consideration.

I am appointing Beth Baker, DSCA/P3-P2 as the Chairman of the CCB. We are asking for your help to ensure the needs of your individual Service are also considered in this process. Each Military Department is requested to appoint an individual to serve on the board. This representative will be responsible for reviewing changes from your unique Service perspective and providing recommendations on approval/disapproval and priority. Please identify your representative to Ms. Baker, e-mail: beth.baker@osd.pentagon.mil. Once all the representatives have been named, a meeting will be held to determine how the board will operate.

Thank you in advance for your support. Together we can build on our successes and ensure the SCIP meets all of our needs.

Tome H. Walters, Jr.
Lieutenant General, USAF
Director

CC :

AFSAC
USASAC
NAVICP
DLA
DTRA
DISA
DFAS-DE
NIMA
DRMS
DCMA
SSG Gunter
DSADC