Where the data is held, and who can see it

← All Insights

1. The window a partner actually sees

Most of the systems that carry a foreign military sale are closed to the buyer. One is not. The Security Cooperation Information Portal gives web based visibility of sales and other programs. It draws case information from the development system and selected execution data from the military department systems, and presents them in a standard format (SAMM C13.3.5.1).

The point of the standard format is that the buyer does not have to know whose case it is. "SCIP provides case information, regardless of which MILDEP/IA is managing the case and is a tool for foreign partners, customer agents (e.g., freight forwarders), and USG personnel with appropriate permissions" (SAMM C13.3.5.1).

The named agents are worth noticing. A freight forwarder appointed by a partner is contemplated as a portal user, which fits the role described in delivery term codes and freight forwarders. The portal sits in the group of systems built to monitor what has been transferred and to meet reporting duties, the subject of what end use monitoring is.

2. The enterprise picture above it

Two systems exist to give the government a view across programs rather than across one case. The first integrates information and data to provide reporting and visualization for the full life cycle of security cooperation programs, covering both grant assistance and sales (SAMM C13.3.2.1). It is hosted on the department’s analytics platform and draws on three streams: case lifecycle data, non sale program and activity data including evaluation work, and other agency requirements (SAMM C13.3.2.1.1).

It does not displace what already exists. "SC-COP does not replace existing reporting capabilities in legacy systems" (SAMM C13.3.2.1.2). The older systems keep the functions that give users immediate case information for development, execution and reporting.

The second is a system of record rather than a dashboard. "Socium is the DoD enterprise-wide system of record for SC program design, planning, budgeting, assessment, monitoring, evaluation, and reporting in support of all U.S. SC initiatives and legal-authority based activities to include the integration of Title 10 funded and Title 22 funded programs" (SAMM C13.3.2.2). Why that integration matters is set out in Title 10 and Title 22 funding.

Its reach is set by its interfaces. It takes data in from combatant command systems and from the partner portal, exchanges data with the case development system, and pushes data out to a mapping instance and the analytics platform (SAMM C13.3.2.2). Access runs up to controlled unclassified information on non defense networks and up to secret on the classified network, and releases arrive every six to nine weeks.

3. Training and workforce data

Training has its own cluster, built around a portal. "SANweb is a portal through which Security Cooperation - Training Management System (SC-TMS) can be accessed" (SAMM C13.3.6.4). It serves the embassy offices, the commands, the departments, the finance service, the schoolhouses and the regional centers.

The training system itself is used by the people closest to a student. "The SC-TMS resides within the SANweb and is used primarily by Security Cooperation Organizations (SCOs) and International Military Student Offices (IMSOs) to manage the SC training program for the foreign partner" (SAMM C13.3.6.5). Through it those offices view training lists and course data, record contact details, issue travel orders, and edit country training plans.

It also carries the vetting adjudication described in screening international military students, and the travel documents described in invitational travel orders and English requirements. Training data moves to and from the case development system daily through an automated interface, and what the offices enter feeds the annual training report to Congress (SAMM C13.3.6.5.8).

The regional centers run a separate system. "RCPAMS is the System of Record for the RCs' administrative information about individual students, their course enrollments, event attendance, and RC operations" (SAMM C13.3.6.3.1). It is the only system in this chapter with a stated log in requirement: "RCPAMS requires Common Access Card (CAC) authentication to gain access" (SAMM C13.3.6.3.2).

Two more sit alongside. A commercial learning platform, run through a partnership with the acquisition university, handles workforce training, certification and career tracking (SAMM C13.3.6.1.1). A workforce database held inside the same portal records positions worldwide by organization and funding source (SAMM C13.3.6.6).

4. The rules that keep it consistent

Systems this numerous only work together if the data inside them matches. The agency runs a data management program under its chief data officer, established under defense instruction 8320.02, to make security cooperation data visible, accessible and usable across its life (SAMM C13.5.1).

Governance sits with a board. "Chaired by the DSCA CDO, and composed of representatives from across the SC community, the SC Data Governance Board (DGB) supports the development, approval, and compliance of DSCA and SC community data products and standards" (SAMM C13.5.3). That chair also carries data recommendations into the two investment boards described in how security cooperation systems get funded.

Two obligations have teeth. A standards baseline must be used by every system development and modernization activity the agency funds, and "Non-compliance with these standards may result in a reduction and/or termination of funding and resources" (SAMM C13.5.5). Separately, "SC information systems must utilize the DSCA data dictionary specification when developing and updating their data dictionaries" (SAMM C13.5.6).

5. What this means in practice

A partner asking where its equipment is will be told from the portal, and the answer there is only as current as the feed behind it. A question about a program rather than a case belongs with the enterprise system of record, which is where money from two different titles of the code is brought into one view.

The consistency rules explain something suppliers notice without being told. Field names, code lists and formats look the same across systems run by different services because a central baseline requires it, and funding is the lever that enforces it.

Key terms

SCIP	The web portal giving partners, their agents and cleared government staff a standard view of case information. SAMM C13.3.5.1.
Socium	The defense wide system of record for program design, planning, budgeting, monitoring, evaluation and reporting.
SANweb	The portal through which the training management system and the workforce database are reached.
RCPAMS	The regional centers’ system of record for students, enrollments and events, reached by card authentication.
Data standards baseline	The mandatory standard set for systems the agency funds, enforced through funding.

Every statement above links to the document behind it. The full source list for this piece is on the sources page.

This page describes public United States government programs for general information. It is not legal, regulatory or procurement advice, and it does not address the facts of any particular case.

How Sentfore supports this

Visibility in a portal is not the same as control on the ground. Sentfore supports defense programs at the delivery end, providing secure movement, protective security, accommodation and site support in complex environments. Requirements can be sent through the contact page.