Applicable Doc. 22 - Identity Verification Integrated Control Document (ICD).pdf

Department of Veterans Affairs

Master Veteran Index (MVI) PSIM Service and

Education Data Repository (EDR)/Talent Management System (TMS)

Interface Control Document

November 2018

Version 1.3

MVI PSIM-EDR/TMS

Interface Control Document ii November 2018

Revision History

Date Version Description Author

11/2018 1.3 Updated ICD to add additional implementation details

By Light Professional IT Services

4/5/2017 1.2 Updated ICD to reflect move from Provisioning to MVI PSIM

By Light Professional IT Services

2/16/2017 1.1 Updated ICD to resolve anomalies Vidya Chandramohan

09/09/2016 1.0 Initial Draft By Light Professional IT Services

Interface Control Document iii November 2018

Table of Contents

1. Introduction

1.1. Purpose

1.2. Scope

1.3. System Identification

1.3.1. MVI PSIM

1.3.2. EDR/TMS

1.4. Operational Agreement

2. Interface Definition

2.1. System Overview

2.1.1. MVI PSIM Overview

2.1.2. EDR/TMS Overview

2.1.2.1. TMS

2.1.2.2. EDR

2.2. Interface Overview

2.3. Operations

2.4. Data Transfer

2.5. Transaction Types

2.6. Data Exchanges

2.7. Precedence and Criticality

2.8. Communications Methods

2.9. Performance Requirements

2.10. Security

3. Interface Requirements

3.1. SQL Server Requirements (Custom Interface)

3.1.1. Interface Processing Time Requirements

3.1.2. Message/File Requirements

3.1.2.1. Data Assembly Characteristics

3.1.2.2. Field/Element Definition

3.1.3. Communication Methods

3.1.4. Security Requirements

3.1.5. Physical Requirements

3.1.6. Structural Requirements

3.1.7. Mechanical Requirements

3.1.8. Electrical Requirements

3.1.9. Thermal Requirements

3.1.10. Special Fluid Requirements

3.1.11. Signal Requirements

Interface Control Document iv November 2018

3.2. Web Service Requirements (Custom Interface)

3.2.1. Interface Processing Time Requirements

3.2.2. Message/File Requirements

3.2.3. Communication Methods

3.2.4. Security Requirements

3.2.5. Physical Requirements

3.2.6. Structural Requirements

3.2.7. Mechanical Requirements

3.2.8. Electrical Requirements

3.2.9. Thermal Requirements

3.2.10. Special Fluid Requirements

3.2.11. Signal Requirements

3.3. sFTP Requirements (Custom Interface)...............Error! Bookmark not defined.

3.3.1. Interface Processing Time Requirements

3.3.2. Message/File Requirements

3.3.2.1. Data Assembly Characteristics

3.3.2.2. Field/Element Definition

3.3.3. Communication Methods

3.3.4. Security Requirements

3.3.5. Physical Requirements

3.3.6. Structural Requirements

3.3.7. Mechanical Requirements

3.3.8. Electrical Requirements

3.3.9. Thermal Requirements

3.3.10. Special Fluid Requirements

3.3.11. Signal Requirements

3.4. Email Notification Requirements (E-mail Notification Interface)

3.4.1. Interface Processing Time Requirements

3.4.2. Message/File Requirements

3.4.2.1. Data Assembly Characteristics

3.4.2.2. Field/Element Definition

3.4.3. Communication Methods

3.4.4. Security Requirements

3.4.5. Physical Requirements

3.4.6. Structural Requirements

3.4.7. Mechanical Requirements

3.4.8. Electrical Requirements

3.4.9. Thermal Requirements

3.4.10. Special Fluid Requirements

Interface Control Document v November 2018

3.4.11. Signal Requirements

4. Appendix A – TMS SOAP Service WSDL

5. Appendix B – Acronyms

Interface Control Document 1 November 2018

1. Introduction This Interface Control Document (ICD) describes the relationship between the Master Veteran Index (MVI) PSIM Service and Education Data Repository (EDR)/Talent Management System (TMS) in terms of an integration overview, data items and messages passed, protocols observed, endpoints utilized in each applications’ environments, and the timing and sequencing of events.

The ICD includes the purpose of the interface, the type of integration(s) between MVI and the partner system, any special requirements for the interface, and the details relevant to the setup of that interface.

1.1. Purpose

This ICD describes the interface between the MVI PSIM and EDR/TMS. The purpose of the Interface Control Document is to describe the interface between the systems including the requirements to be met by the participating systems. It describes the concept of operations for the interface, defines the message structure and protocols which govern the interchange of data, and identifies the communication paths along which the data is expected to flow. This document uses the ProPath template provided for VA process compliance.

1.2. Scope

This Interface Control Document specifies the interface(s) between MVI PSIM and EDR/TMS.

Upon formal approval for each participating system, this ICD shall incorporate into the baseline for each system. This document provides details on the functional, performance, operational and design requirements for the interface between MVI PSIM and EDR/TMS. This document describes the interaction between the systems including the content of data passed between the systems. It is intended for all parties requiring such information, including software developers, system designers, and testers responsible for implementing the interface.

1.3. System Identification

This Interface Control Document describes the interface between MVI PSIM and EDR/TMS.

1.3.1. MVI PSIM

Table 1: MVI PSIM System Details

System Details

Identification number 001

Title IAM AcS Provisioning Service

Abbreviation MVI PSIM

Version number 2.3.4

Release number 2

Point of Contact Danny Reed –AcS Architect (danny.reed@va.gov, 205-943-2415)

Vendor [optional] By Light Professional IT Services mailto:danny.reed@va.gov

Interface Control Document 2 November 2018

1.3.2. EDR/TMS

Table 2: EDR System Details

System Details

Identification number

Title Education Data Repository

Abbreviation EDR

Version number Microsoft SQL Server 2012 (SP3-GDR)

Release number

Point of Contact Feifei Liu

Vendor [optional]

Table 3: TMS System Details

System Details

Identification number 01-02-05-06-04-004

Title Talent Management System

Abbreviation TMS

Version number Plateau Learning 6.4

Release number B1502

Point of Contact Jeff Henry

Vendor [optional] Success Factors/Plateau

1.4. Operational Agreement

The MVI PSIM implementation will provide user access management to VA Applications external to AcS services. Specific details of the MVI PSIM solution architecture and design may be found in the AcS System Design Document (SDD).

Each responsible party, maintaining and supporting the two interface endpoints (namely EDR/TMS and MVI PSIM) shall notify the other in an event of any potential or planned changes in the interface. The party effecting the change shall promptly update the current document with any and all relevant technical details associated with the interface change. The updated document will be communicated to the other party for technical review and any required business approval(s). If any counter changes are required on the other side of the interface, those will be documented by the team responsible for the side of the interface making the changes.

Each system’s developers and users are expected to protect each other’s data in accordance with the Privacy Act and Trade Secrets Act guidelines. The following considerations will be made when conducting interfacing operations with VA IAM:

• Each system team agrees not to misuse or disclose Personally Identifiable Information (PII) other than as permitted or required by this Agreement or as Required by Law.

Interface Control Document 3 November 2018

• Each system team agrees to use appropriate safeguards to prevent use or disclosure of the PII other than as provided for by this Agreement.

• Each system team agrees to mitigate, to the extent practicable, any harmful effect that is known to EDR/TMS of a misuse or disclosure of PII by any Business Partner in violation of the requirements of this Agreement.

• Each system team agrees to report to the IPEO any misuse or disclosure of the PII not provided for by this Agreement of which it becomes aware.

• Each system team agrees to ensure that any agent, including a subcontractor, to whom it provides PII received from the other system, agrees to the same restrictions and conditions that apply through this Agreement to EDR/TMS with respect to such information.

2. Interface Definition This section identifies and describes the types of interfaces between the systems.

There are two types of interfaces with EDR/TMS:

1. MVI PSIM Custom Interface

2. Email Notification

2.1. System Overview

2.1.1. MVI PSIM Overview

MVI PSIM provides an enterprise identity service for VA business lines; uniquely identifies all persons of interest; enables assigning universal VA identifiers to service members; and facilitates data sharing between VA LOB's and external partners.

2.1.2. EDR/TMS Overview

2.1.2.1. TMS

The VA Talent Management System (TMS) is a VA-wide training application that allows employees and contractors to take training online with the goal of maintaining a single official training record VA-wide. All VA employees and contractors systematically have a TMS account created for them once their information has been entered into the VA system.

2.1.2.2. EDR

Education Data Repository (EDR) is the internal database that supports VA TMS user profile management system. EDR, which is located inside VA’s firewall, maintains data elements that are not shared with TMS, but applies logic to certain data elements supplied from various data sources to ensure appropriate TMS user profile classification and management.

2.2. Interface Overview

The interactions between MVI PSIM and EDR/TMS will be comprised of the following interfaces:

Interface Control Document 4 November 2018

• Custom Web Service Interface – MVI PSIM invokes web service API provided by TMS to perform onboarding/offboarding operations for users in TMS. This custom interface is implemented in java in the PSIM service.

• Custom SQL Server DB interface – MVI PSIM calls stored procedures provided by

EDR to perform onboarding/offboarding/training operations for users in EDR. This is custom code implemented in java..

• Email Notification –Email notifications can enable applications to take advantage of workflow to facilitate access requests and approvals while enabling system administrators to manage accounts

2.3. Operations

There are three major operations that occur between MVI PSIM and the EDR/TMS:

• On-Board User

• Deactivate User

• Reactivate User

The integration patterns used to satisfy the major requirements between MVI PSIM/EDR and MVI PSIM/TMS are listed in section 2.5.

2.4. Data Transfer

The MVI PSIM system integrates with multiple systems, including Provisioning, Active Directory, TMS-EDR, VA-PAS, and Toolkit, to create and modify accounts to facilitate the onboarding of users into the VA systems. A high level diagram of the ICAM onboarding integrations is shown in Figure 1 below.

Interface Control Document 5 November 2018

Figure 1: ICAM Onboarding Integrations

Custom Code

SQL Server DB interface: In this interface, data is transferred via SQL Server Interface from MVI PSIM to the EDR user account table within EDR as a result of the onboarding activity.

Data is transferred using SQL Server Stored Procedures in EDR. Actions include “inserts” for creating new accounts, updates to account details for update requests, and finally updates to the “active/inactive” flag for user accounts in EDR that are being deactivated and reactivated. In addition, mandatory training assignments will also be provided to MVI PSIM via this interface.

Web Service Interface: This interface is used by MVI PSIM to transfer user account and training data to TMS via a Web Service.

SFTP interface: For TMS, the MVI PSIM service will also accept a feed from TMS. This feed will contain training completion notifications. MVI PSIM will use an sFTP connection to retrieve the feed file provided by TMS at a prescribed internal location..

E-mail Notification

This interface leverages SMTP messages sent to an application administrator mailbox or mail group to notify of a pending action from the MVI PSIM system. EDR and TMS will notify the system administrator of failed calls. MVI PSIM will send an email notification to the user when they have been assigned to complete mandatory training in TMS.

Interface Control Document 6 November 2018

The high-level integration between MVI PSIM and TMS-EDR is shown below.

*****Need to add a diagram******

Figure 2: MVI PSIM TMS-EDR Integration

2.5. Transaction Types

The follow table shows the major functional requirements and the integration pattern that will be used to fulfill the requirements.

Table 4: Functional Requirements and Integration Patterns

Major Functional Requirement Integration Pattern used Create/Update/Deactivate/Reactivate user account in

EDR

SQL Server Stored Procedure call

Create/Deactivate user account in TMS Web service call

Assign initial mandatory training in TMS Web service call

Update Employee training from EDR SQL Server Stored Procedure call

Update EDR with contractor data SQL Server Stored Procedure call

Update contractor training in TMS Web Service Call

2.6. Data Exchanges

Custom Interface

MVI PSIM uses custom java code to connect to the EDR database via a stored procedure. The following are the data elements that are exchanged with EDR.

Table 5: Data Elements Sent to EDR on ADD

Attribute (from iRSD) PSIM Attribute EDR Attributes

SEC ID <IDENTIFIER type='PN'> Secid

SSN <IDENTIFIER type='SSN'> Ssn

Last Name <LASTNAME> lastname

First Name <FIRSTNAME> Firstname

Station Number <ATTRIBUTE type='STATION_NUMBER'> StationNumber

Duty Station <ATTRIBUTE type='DUTY_STATION'> DutyStationCode

Interface Control Document 7 November 2018

Attribute (from iRSD) PSIM Attribute EDR Attributes

Organization Code <ATTRIBUTE type='ORGANIZATION_ID'> VAOrganizationCode

Supervisor/COR <ATTRIBUTE type='SUPERVISOR_ID'> SupervisorSECID

Occupation <ATTRIBUTE type='OCCUPATION_ID'> OccupationID

HR Type <ATTRIBUTE type='HR_TYPE_ID'> HRTypeID

Date of Birth (yyyymmdd) <ATTRIBUTE type='DOB'> dateOfBirth

Table 6: Data Elements Returned From EDR on ADD

Attribute (from iRSD) PSIM Attribute EDR Attributes

SECID <IDENTIFIER type='PN'> SECID

User Domain <ATTRIBUTE type='EDR_DOMAIN_ID' subtype='EDR'>

PlateauDomainID

Role <ATTRIBUTE type='EDR_ROLE' subtype='EDR'> role

Person ID <ATTRIBUTE type='EDR_PERSON_ID' subtype='EDR'> personID

Training Course ID(s) <ATTRIBUTE type='COURSE_LIST' subtype='EDR'> courses

2.6.1. ProvisionGenerateTMSRecordForProvision

The Data attributes exchanges for ProvisionGenerateTMSRecordForProvision transaction

Data Element IAM

Attribute

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

VA SEC ID <IDENTIFIER

type='PN'>

SECID String 10

Social Security

Number

<IDENTIFIER

type='SSN'>

SSN String 9

First Name <FIRSTNAME> firstname String 30

Last Name <LASTNAME> lastname String 30

Date of Birth <ATTRIBUTE type='DOB'>

DOB Date

Station ID <ATTRIBUTE type='STATION

_NUMBER'>

DutyStationCo de

String 100

Interface Control Document 8 November 2018

Organization ID <ATTRIBUTE type='ORGANI

ZATION_ID'>

OrganizationC ode

String 100

Supervisor Id <ATTRIBUTE type='SUPERVI

SOR_ID'>

SupervisorSEC

ID

String 10

Occupational Id <ATTRIBUTE type='OCCUPA

TION_ID'>

OccupationCo de

String 8

HR Type Id <ATTRIBUTE type='HR_TYP

E_ID'>

HRTypeID INT

The Data attributes exchanges for ProvisionGenerateTMSRecordForProvisionResponse transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

VA SEC ID <IDENTIFIER

type='PN'>

SECID String 10

DomainID String

Role String

PersonID String

TMSCourse String

2.6.2. ProvisionCheckExistingUserBySSN

The Data attributes exchanges for ProvisionCheckExistingUserBySSN transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

Social Security

Number

<IDENTIFIER

type='SSN'>

SSN String 9

The Data attributes exchanges for ProvisionCheckExistingUserBySSNResponse transaction

Data Element IAM Attribute EDR Atrribute Required /Optional

Data Field Type

Max Length

UserExists True

False

String personID separationIndicatorFlag N

Y

String

StudentID Supervisor

Student ID

SECID <IDENTIFIER

type='PN'> VA SEC ID String 10 plateauDomainID

Interface Control Document 9 November 2018 role

StationNumber <ATTRIBUTE type='STATION

_NUMBER'>

Station Number String 100

DutyStationCode <ATTRIBUTE type='STATION

_NUMBER'>

Station ID String 100

VAOrganizationCode <ATTRIBUTE type='ORGANIZ

ATION_ID'>

Organization ID String 100

SupervisorSECID <IDENTIFIER type='PN'> Supervisor Id String 10

OccupationCode <ATTRIBUTE type='OCCUPAT

ION_ID'>

Occupational Id String 8

HRTypeID <ATTRIBUTE type='HR_TYPE

_ID'>

HR Type Id INT dob <ATTRIBUTE type='DOB'> Date lastName <LASTNAME> Last Name String 30 firstName <FIRSTNAME> First Name String 30 emailAddress EMAIL_ADDRE

SS

Email Address ntLogin Network Login ssoCredential SSO Credential

2.6.3. ProvisionUpdateEmailNTLoginSECIDBySSN

The purpose of this operation is to update email, NTLogin and SEC ID.

The Data attributes exchanges for ProvisionUpdateEmailNTLoginSECIDBySSN transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

Social Security

Number

<IDENTIFIER

The ProvisionUpdateEmailNTLoginSECIDBySSN does not return results.

2.6.4. ProvisionUpdateEmailNTLoginSECIDByPersonID

The purpose of this operation is to update email, NTLogin and SEC ID.

Interface Control Document 10 November 2018

The Data attributes exchanges for ProvisionUpdateEmailNTLoginSECIDByPersonID transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

Person ID <ATTRIBUTE type='EDR_PER

SON_ID'

The ProvisionUpdateEmailNTLoginSECIDByPersonID does not return results.

2.6.5. ProvisionUpdateSSNByPersonID

The purpose of this operation is to update SSN

The Data attributes exchanges for ProvisionUpdateSSNByPersonID transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

Person ID <ATTRIBUTE type='EDR_PER

SON_ID'

subtype='EDR'>

PersonID String

Social Security

Number

<IDENTIFIER

The ProvisionUpdateSSNByPersonID does not return results.

2.6.6. ProvisionCheckExistingUserByPersonID

The purpose of this operation is to search using PersonID

The Data attributes exchanges for ProvisionCheckExistingUserByPersonID transaction

EDR

Atrribute

Required/Opt ional

Data Field Type Max Length

Person ID <ATTRIBUTE type='EDR_PER

SON_ID'

The ProvisionCheckExistingUserByPersonIDResponse returns.

Data Field

Type

Max

Length

Interface Control Document 11 November 2018 personID separationIndicatorFlag N

Y

String

VA SEC ID String 10 plateauDomainID role

StationNumber <ATTRIBUTE type='STATION

_NUMBER'>

Station Number String 100

DutyStationCode <ATTRIBUTE type='STATION

_NUMBER'>

Station ID String 100

VAOrganizationCode <ATTRIBUTE type='ORGANIZ

ATION_ID'>

Organization ID String 100

SupervisorSECID <IDENTIFIER type='PN'>

Supervisor Id String 10

OccupationCode <ATTRIBUTE type='OCCUPAT

ION_ID'>

Occupational Id String 8

HRTypeID <ATTRIBUTE type='HR_TYPE

_ID'>

HR Type Id INT dob <ATTRIBUTE type='DOB'>

Date lastName <LASTNAME> Last Name String 30 firstName <FIRSTNAME> First Name String 30 emailAddress EMAIL_ADDRE

SS

Email Address

2.6.7. ProvisionGetNewAdds

The purpose of this operation is to get new adds in EDR

Takes 2 Dates (From, To)

The ProvisionGetNewAddsResponse returns.

Data Field

Type

Max

Length personID separationIndicatorFlag N Y

String

Interface Control Document 12 November 2018

VA SEC ID String 10 plateauDomainID role

StationNumber <ATTRIBUTE type='STATION

_NUMBER'>

Station Number String 100

DutyStationCode <ATTRIBUTE type='STATION

_NUMBER'>

Station ID String 100

VAOrganizationCode <ATTRIBUTE type='ORGANIZ

ATION_ID'>

Organization ID String 100

SupervisorSECID <IDENTIFIER type='PN'> Supervisor Id String 10

OccupationCode <ATTRIBUTE type='OCCUPAT

ION_ID'>

Occupational Id String 8

HRTypeID <ATTRIBUTE type='HR_TYPE

_ID'>

HR Type Id INT dob <ATTRIBUTE type='DOB'> Date lastName <LASTNAME> Last Name String 30 firstName <FIRSTNAME> First Name String 30 emailAddress EMAIL_ADDRE

SS

Email Address ntLogin Network Login ssoCredential SSO Credential

DateCreated

Social Security

Number

<IDENTIFIER

2.6.8. ProvisionGetNewUpdates

The purpose of this operation is to get new Updates in EDR

Takes 2 Dates (From, To)

The ProvisionGetNewUpdatesResponse returns.

Data Field

Type

Max

Length personID separationIndicatorFlag N Y

String

Interface Control Document 13 November 2018

VA SEC ID String 10 plateauDomainID role

StationNumber <ATTRIBUTE type='STATION

_NUMBER'>

Station Number String 100

DutyStationCode <ATTRIBUTE type='STATION

_NUMBER'>

Station ID String 100

VAOrganizationCode <ATTRIBUTE type='ORGANIZ

ATION_ID'>

Organization ID String 100

SupervisorSECID <IDENTIFIER type='PN'>

Supervisor Id String 10

OccupationCode <ATTRIBUTE type='OCCUPAT

ION_ID'>

Occupational Id String 8

HRTypeID <ATTRIBUTE type='HR_TYPE

_ID'>

HR Type Id INT dob <ATTRIBUTE type='DOB'>

Date lastName <LASTNAME> Last Name String 30 firstName <FIRSTNAME> First Name String 30 emailAddress EMAIL_ADDRE

SS

Email Address ntLogin Network Login ssoCredential SSO Credential

DateCreated

Social Security

Number

<IDENTIFIER

Table 6: Activate/Deactivate Account Attributes

(from iRSD)

Required

(Y/N)

MVI PSIM

Attribute

MVI PSIM

Attribute

Data Type

TMS

Attribute

TMS Attribute

Data Type

Caller ID Y callerID String callerID A-Numeric

Student ID Y studentID String studentID

A-Numeric

Non Active Flag

Y N/A notActive Boolean

Interface Control Document 14 November 2018

NOTE: The tables above will be completed as information becomes available.

Table 7: Email Notification Attributes

Attribute (from iRSD) MVI PSIM

Attribute

Supervisor ID asOtherIDs classCode="SUPERVIS

OR_ID"

AD Account asOtherIDs classCode="SAM_ACC

OUNT_NAME"

User Email Address EMAIL_ADDRESS

User External Email Address EMAIL_ADDRESS

Supervisor Email Address N/A

SEC ID asOtherIDs classCode="PAT"

TMS Mandatory training N/A

Temporary Password password

NOTE: The tables above will be completed as information becomes available.

2.7. Precedence and Criticality

This interface is necessary to provision and de-provision EDR accounts. The interface will also be used when there is a modification in MVI PSIM that requires a EDR user account update that triggers an EDR user profile modification. This interface will also be used to load updated mandatory training assignments sent by EDR to MVI PSIM.

This interface is necessary to provision and de-provision TMS user accounts and user training data. The Interface will only be used when there is a modification in the MVI PSIM that requires a TMS user account/training update that triggers a TMS user or training profile modification.

Email Notification

This interface is necessary to notify the system administrator of failed calls to EDR. In the case of TMS, email notifications will be sent to the user’s external email address and the supervisor informing them when an account has been created and mandatory training has been assigned.

Email notifications will also be sent to the user’s external email address with their temporary password.

2.8. Communications Methods

Interface Control Document 15 November 2018

The custom code being used for this integration is the SQL Server Database Interface. It employs a native SQL Server connection from MVI PSIM directly to the EDR database using EDR Stored Procedure calls.

Another communication method used for this interface is via web service.

In addition, sFTP will be used to receive the feeds from TMS.

E-mail Notification

This interfaces leverages SMTP messages sent to an application administrator mailbox or mail group to notify of a pending action from the MVI PSIM system.

2.9. Performance Requirements

The MVI PSIM service will achieve the performance requirements details as defined by IAM in the Business Requirements Document (BRD).

EDR will achieve performance requirements details as defined in their requirements document.

2.10. Security

Information security has been mandated for all communication paths between interfaces. All information exchanges between the subsystems of MVI PSIM are transmitted over the industry standard TLS 1.2 high level encryption.

Both parties agree to work together to ensure the joint security of the connected systems and the data they store, process, and transmit as specified in this ICD. Each party certifies that its respective system is designed, managed, and operated in compliance with all relevant federal laws, regulations, and policies.

2.10.1. Security Authorization with TMS:

The diagram below represents the process IAM shall follow to get a Token that shall be used for the API calls.

Interface Control Document 16 November 2018

The process is:

1. Concatenate the client ID and secret, separated by a colon.

2. For example, if the client ID is t1 and the secret 52d85f24492ff918dcd1935a45a9d34acd79e249fe331753c6e0105b109e034a

• then the result is:

• t1:52d85f24492ff918dcd1935a45a9d34acd79e249fe331753c6e0105b109e034a

3. Encode the concatenated client ID and secret with base64 encoding.

For example, the following concatenation:

t1:52d85f24492ff918dcd1935a45a9d34acd79e249fe331753c6e0105b109e034a

Encodes to:

dDE6NTJkODVmMjQ0OTJmZjkxOGRjZDE5MzVhNDVhOWQzNGFjZDc5ZT

I0OWZlMzMxNzUzYzZlMDEwNWIxMDllMDM0YQ== 3.

4. Over HTTPS, call the token granting service.

Sample call to the token granting service:

POST {root}/learning/oauth-api/rest/v1/token4.

5. Pass the encoded client ID and client secret in the request header.

Interface Control Document 17 November 2018

Sample header:

• Authorization: Basic <encoded token from previous step>

6. Pass required OAuth token parameters.

7. Check the response header, which is either 200: OK or an error with the HTTP error code.7.

8. Store the information in response body for subsequent calls.

3. Interface Requirements This section specifies the requirements for interfaces between the two systems. It states the type and purpose of each interface and identifies all interface design requirements and constraints. It provides explicit definitions of the content and format of data passed between the systems and the conditions under which it is to be sent.

3.1. SQL Server Requirements (Custom Interface)

The following is the required information to connect to the EDR database. Also listed a re the

SQL Server database stored procedures that the Provisioning service will call to connect and send data to EDR. It should be noted that some stored procedure calls to EDR are bi-directional in nature. The Stored Procedure ProvisionGenerateTMSRecordForProvision is called to create a user account in EDR. This call returns an acknowledgement by including the following return values: SEC ID, User Domain, User Role, Person ID and Training Course IDs. The MVI PSIM service will save the returned values using the SEC ID to match the user account and will also log the successful creation of the EDR account. The Stored Procedure ProvisionGetContractorToEmployeeList is called without any parameters to return the contractor list from EDR. For Stored Procedure calls that are not supposed to return a value, a null value indicates a success. If an error is raised from a Stored Procedure, an error code will be returned.

Successful processing or exception processing will be logged by the MVI PSIM service.

Table 8: EDR Server Information

REGION EDR SQL Server Name Network Name

(Preferred)

Port

DEV VAAUSLIBSQL80.AAC.DVA.VA.GOV Not provided 1433

SQA VAAUSLIBSQL80.AAC.DVA.VA.GOV Not provided 1450

PREPROD VAAUSLIBSQL80.AAC.DVA.VA.GOV Not provided 1450

PROD VAAUSLIBSQL20.AAC.DVA.VA.GOV EDRSQL.LRN.VA.GOV 1450

Table 9: EDR SQL Database Information

Database Name People

Service Account ProToEDRSQLAccount

Password (not included for security reasons)

Interface Control Document 18 November 2018

Table 10: EDR SQL Server Objects

Stored Procedure Name Function Input Parameters Return Values

ProvisionGenerateTMSRecordForProvision Create an account in

EDR

SECID, SSN, lastname, firstname, StationNumber, DutyStationCode, VAOrganizationCode, OccupationCode, HRTypeID, SupervisorSECID, DateOfBirth

SECID,

PleateauDomainID, role, personID, TMSCourse(s)

ProvisionUpdateTMSContractorRecord ForProvision

Update User Account

SECID,lastname , firstname, StationNumber, DutyStationCode, VAOrganizationCode, NTLogin, EmailAddress, SupervisorSECID

Nothing

ProvisionSeparateTMSRecordForProvision Deactivate Account

SECID Nothing

ProvisionActiveTMSRecordForProvision Reactivate Account

SECID, SSN, lastname, firstname, StationNumber, DutyStationCode, VAOrganizationCode, OccupationCode, HRTypeID, SupervisorSECID

SECID,

PleateauDomainI

D, role, personID, TMSCourse(s)

ProvisionGetContractorToEmployeeList Get EDR

Contractor & Employee List

No Parameters SECID, Last name, first name, ItemID, DateCreated

ProvisionCleanContractorToEmployeeListBy

SECID

Clean

SECID

From Contractor

& Employee List

SECID Nothing

ProvisionCheckExistingUserBySSN Search By

SSN

SSN

PersonID, SeparationInd, StudentID, SECID, PlateauDomainID, role, StationNumber, DutyStationCode, VAOrganizationCo de, SupervisorID, OccupationCode, HRTypeID, DOB, LastName, FirstName, Interface Control Document 19 November 2018

EmailAddress, NTLogin, SSOCredential

ProvisionCheckExistingEmailByEmail Search by Email

Email PersonID, SeparationInd, StudentID, SECID, PlateauDomainID, role, StationNumber, DutyStationCode, VAOrganizationCo de, SupervisorID, OccupationCode, HRTypeID, DOB, LastName, FirstName, EmailAddress, NTLogin, SSOCredential

ProvisionUpdateEmailNTLoginSECIDBy

SSN

Update email, NTLogin

SSN

Nothing

ProvisionCheckExistingUserByPersonID Search by

Person ID

PersonID PersonID, SeparationInd, StudentID, SECID, PlateauDomainID, role, StationNumber, DutyStationCode, VAOrganizationCo de, SupervisorID, OccupationCode, HRTypeID, DOB, LastName, FirstName, EmailAddress, NTLogin, SSOCredential

ProvisionGetNewAdds Get new

ADDs to

EDR

Takes 2 Dates (From, To) PersonID, SeparationInd, StudentID, SECID, Interface Control Document 20 November 2018

PlateauDomainID, role, StationNumber, DutyStationCode, VAOrganizationCo de, SupervisorID, OccupationCode, HRTypeID, DOB, LastName, FirstName, EmailAddress, NTLogin, SSOCredential, DateCreated, SSN

ProvisionGetNewUpdates Get new

UPDATEs to EDR

Takes 2 Dates (From, To) PersonID, SeparationInd, StudentID, SECID, PlateauDomainID, role, StationNumber, DutyStationCode, VAOrganizationCo de, SupervisorID, OccupationCode, HRTypeID, DOB, LastName, FirstName, EmailAddress, NTLogin, SSOCredential, DateCreated, SSN

3.1.1. Interface Processing Time Requirements

The MVI PSIM interface processing time requirements are not established. However, the performance of the MVI PSIM interface will be dependent on the performance of the VA network and connection between the MVI PSIM service and the consuming application database.

The MVI PSIM system has been designed to handle complex operations asynchronously to minimize processing time when requests are made of the service. The system is designed with a high degree of fault tolerance with retry mechanisms in place.

3.1.2. Message/File Requirements

3.1.2.1. Data Assembly Characteristics

Interface Control Document 21 November 2018

N/A

3.1.2.2. Field/Element Definition

See Section 6.2 for attribute names, lengths, data type and description.

3.1.3. Communication Methods

3.1.3.1. Interface Initiation

The SQL Server Interface will open a single connection to the EDR user table in order to provision the account, once approval has been received for the request. Attributes will be updated into the SQL data store real-time, as the approvals, modifications or rejections are received.

3.1.3.2. Flow Control

Connection to the SQL Server will be made in real time. The code to create the connection and to execute the prepared statement is surrounded by a try/catch block. If the connection is not obtained, an exception is caught and logged.

3.1.4. Security Requirements

The interface is FIPS 140-2 compliant.

MVI PSIM and EDR must both maintain a VA Authority to Operate and follow VA guidelines detailed within the VA Handbook 6500. VA Handbook 6500 includes federally-mandated security requirements. Access to the EDR database requires a service account created for MVI PSIM that is password protected. The passwords will be transmitted securely and encrypted in transmission. Only the system administrator will have knowledge of the passwords and passwords will not be shared with any other person. Password Management Policy will be used that will be controlled by Database Administrators (DBA’s) and security officers using user profiles. The communication channel to the EDR database is also using SSL and encrypted.

3.1.5. Physical Requirements

3.1.6. Structural Requirements

N/A

3.1.7. Mechanical Requirements

N/A

3.1.8. Electrical Requirements

3.1.9. Thermal Requirements

Interface Control Document 22 November 2018

N/A

3.1.10. Special Fluid Requirements

N/A

3.1.11. Signal Requirements

N/A

3.2. Web Service Requirements (Custom Interface)

Table 11: Web Service Requirements – Custom Connector

REGION TMS Endpoints Service account

DEV https://va-train2.plateau.com/learning/cxfservices/cxfWebServices Va-prov-stage

SQA https://va-train2.plateau.com/learning/cxfservices/cxfWebServices

Va-prov-stage

PREPROD TBD Va-prov-stage

PROD TBD Va-prov

A service account is used to establish identity and for authentication of the MVI PSIM web service client to TMS web server.

3.2.1. Interface Processing Time Requirements

The MVI PSIM interface processing time requirements are not established. However, the performance of the MVI PSIM interface will be dependent on the performance of the VA network and the connection between the MVI PSIM service and the consuming application database. The MVI PSIM system has been designed to handle complex operations asynchronously to minimize processing time when requests are made of the service. The system is designed with a high degree of fault tolerance with retry mechanisms in place.

3.2.2. Message/File Requirements

3.2.2.1. Data Assembly Characteristics

N/A

3.2.2.2. Field/Element Definition

See Section 2.6 for attribute names and data types.

3.2.3. Communication Methods

3.2.3.1. Interface Initiation

Connections are made to this interface via Web Services. MVI PSIM will use client code written in Java to communicate with and send data to TMS.

Interface Control Document 23 November 2018

3.2.3.2. Flow Control

MVI PSIM will use web services to send data to TMS to add a student to TMS, update contractor training and to activate/deactivate student accounts.

Following are the sample web service requests and responses for the applicable operations.

3.2.3.2.1. Create EDR Account

Creating EDR Account shall invole the a store procedure called

ProvisionGenerateTMSRecordForProvision in EDR

The sequence diagram for the ProvisionGenerateTMSRecordForProvision store procedure:

The ProvisionGenerateTMSRecordForProvision message format

EXEC ProvisionGenerateTMSRecordForProvision

‘SECID’, ‘SSN’, ‘lastName’, ‘firstName’, ‘dob’, ‘StationNumber’, ‘DutyStationCode’, ‘OrganizationField’, ‘SupervisorIDUserID’, ‘OccupationSeries’, ‘HRTypeID’

Sample: ProvisionGenerateTMSRecordForProvision

'1008797154','111330030','PSIM','MVI','200','200A','19061000','1008786612',null,9,'1952-03-04'

Interface Control Document 24 November 2018

The Data attributes exchanges for ProvisionGenerateTMSRecordForProvisionResponse transaction

Data Element Required/Optional Data Field

Type

Data Definition Max Length

SECID String VA SEC ID 10

DomainID String Domain ID 30

Role String Role 30

PersonID String Person ID 30

TMSCourse String TMS Course 50

The ProvisionGenerateTMSRecordForProvisionResponse message format

EXEC ProvisionGenerateTMSRecordForProvision

‘SECID’, ‘DomainID’, ‘role’, ‘personID’, ‘TMSCourse’, ‘

Sample: ProvisionGenerateTMSRecordForProvision

[secid=1008804188, domainId=EPM, role=INTERNAL, personID=1638421, courses=[10176], success=true, errorCode=null, errorText=null]

3.2.3.2.2. Obtain Student ID of the Supervisor

In order to add a new student to TMS 2.0 IAM needs to first obtain the Student ID of the person being Supervisor of the person being onboarded from EDR.

This shall be accomplished by calling a store procedure ProvisionCheckExistingUserBySSN

The sequence diagram for the ProvisionCheckExistingUserBySSN store procedure:

Interface Control Document 25 November 2018

The Data attributes exchanges for ProvisionCheckExistingUserBySSN transaction

Data Definition Max Length

SSN String Social Security

Number

The ProvisionCheckExistingUserBySSN message format

EXEC ProvisionCheckExistingUserBySSN

‘SSN’

Sample: ProvisionCheckExistingUserBySSN

'111330030'

The Data attributes exchanges for ProvisionCheckExistingUserBySSNResponse transaction

Data Definition Max Length

UserExists String True

False personID

Interface Control Document 26 November 2018 separationIndicatorFlag String N

Y

SECID String VA SEC ID 10 plateauDomainID role

StationNumber String Station Number 100

DutyStationCode String Station ID 100

VAOrganizationCode String Organization ID 100

SupervisorSECID String Supervisor Id 10

OccupationCode String Occupational Id 8

HRTypeID INT HR Type Id dob Date lastName String Last Name 30 firstName String First Name 30 emailAddress Email Address

[userExists=true, personID=293708, separationIndicatorFlag=N, studentID=Supa.Supavisor0101, secid=1008786612, plateauDomainID=EPM, role=NO_EIDP_STANDARD, stationNumber=116, dutyStationCode=D , VAOrganizationCode=19863000, supervisorID=602210, occupationCode=221002, hrTypeID=1, dob=1975-01-01, lastName=Supa, firstName=Supervisor, emailAddress=supervisor.supa@va.gov, ntLogin=VHAISDSUPAS, ssoCredential= supervisor.supa

@VA.GOV]

3.2.3.2.3. Create TMS Account

TMS uses OData (Open Data Protocol) to provide and receive data from clients using RESTful API’s.

The API’s MVI is using is:

3.2.3.2.3.1.Find User

Resource Description IAM Usage

Request

URL

https://<<hostname>>/learning/odatav4/public/admin/vauserservice/ v1/Users? $filter=criteria/learnerID

IAM is only using

StudentID

Interface Control Document 27 November 2018

Method

GET

Description Search Users in LMS

Header Authorization: Bearer {oauth_token} (user type)

Parameter customColumn, domainIDs, emailAddr, firstName, isActive, jobPositionIDs, lastName, learnerID, middleInit and organizationIDs.

IAM is only using

StudentID

Request

Body

Response

Header

200: OK. or ERROR see HTTP error codes.

RESPONSE

Body

Sample Response Body:

"value": [

{“attribute”; value/null, …….(see data attributes in the Appendix B )

"customColumn": [

"iD": "User_1.0_Active", "value": "Column 10", "columnNumber": 10, "__hashCodeCalc": false

"iD": "User_1.0_Active", "value": "Column 30", "columnNumber": 30, "__hashCodeCalc": false

"iD": "User_1.0_Active", "value": "Column 30", "columnNumber": 1012, "__hashCodeCalc": false

Processing the results

For the Supervisor ID – IAM is checking if {} has any values.

If there are values, IAM will only take the

"superField"

Interface Control Document 28 November 2018

3.2.3.2.3.2.Add User

Resource Description IAM

Usage

Request

URL

https://<<hostname>>/learning/odatav4/public/admin/vauser-service/v1/Users IAM is only using

StudentI

D

Request

Method

POST

Descriptio n Create new user in LMS and BizX

Header Authorization: Bearer {oauth_token} (user type)

Parameter None

Body

Response

Header

200: OK. or ERROR see HTTP error codes.

RESPONS

E Body

"bizx_firstName": "Va_New_User_1", "bizx_username": "Va_New_User_1", "bizx_userId": "1008804188", "bizx_status" : "t", "bizx_manager": " Va_New_User_Manager", "studentID": "Va_New_User_1", "roleID": "DEFAULT USER", "domainID": "PUBLIC", "supervisorID": "Va_New_User_Manager", "currencyID" : "USD"

Sample

"studentID":"1008804188", "bizx_userId":"1008804188", "customColumn":

{"iD":"1008804188","value":"1638421","columnNumber":146,"__hashCodeCalc ":false}, {"iD":"1008804188","value":"1638421","columnNumber":9,"__hashCodeCalc":f alse} "bizx_custom15":"1638421", "roleID":"INTERNAL", "domainID":"EPM", "notActive":"No", Interface Control Document 29 November 2018

"bizx_status":"t", "lastName":"Number", "bizx_lastName":"Number", "f irstName":"Letter", "bizx_f irstName":"Letter", "emailAddress":"Letter@slsolutions.com", "bizx_email":"Letter@slsolutions.com", "supervisorID":"Supa.Supervisor0101", "bizx_manager":" Supa.Supervisor0101", "employeeTypeID":"9", "bizx_empId":"111421", "bizx_username":"111421", "currencyID":"USD", "locale":"English", "bizx_defaultLocale":"en_US", "timeZone":"America/New_York", "bizx_timeZone":"America/New_York", "bizx_hr":"NO_HR", "bizx_loginMethod":"PWD"

Sample ADD Success Response

See Sample Add Success Reponse in Appendix B

3.2.3.2.3.3.Set User Preference

Resource Description IAM

Usage

Request

URL

https://<<hostname>>/learning/odatav4/public/admin/vauserservice/ v1/UserPreferences('<<StudentID>>')

IAM is only using

StudentID

Request

Method

PUT

Description Update User Preference both in LMS and BizX

Header Authorization: Bearer {oauth_token} (user type)

Parameter StudentID

Body

Sample {"userID":"1008804055", "bizx_username":"1008804055", Interface Control Document 30 November 2018

"bizx_status":"t", "timeZone":"America/Chicago", "displayScheduleInUserTimeZone":true, "localeID":"English", "bizx_localeID":"en_US", "bizx_timeZone":"America/Chicago", "languageCode":"en", "percentageSymbol":"%", "currencyPattern":{

"patternID":"Currency_01", "decimalSeparator":".", "groupingSeparator":",", "hint":"1000,001.01", "maxFractionDigit":2, "minFractionDigit":2

"currencyPreference":{

"currencyID":"USD", "currencySymbol":"$", "description":"US Dollar", "labelId":"data.currency.USDollar", "active":true, "globalDefault":true

"datePattern":{

"dateTimePatternID":"M/d/yyyy", "hint":"MM/DD/YYYY", "pattern":"M/d/yyyy"

"doublePattern":{

"patternID":"Double_01", "decimalSeparator":".", "groupingSeparator":",", "hint":"1000,001.01", "maxFractionDigit":2, "minFractionDigit":2

"longPattern":{

"patternID":"Long_01", "decimalSeparator":null, "groupingSeparator":",", "hint":"1000,001", "maxFractionDigit":0, "minFractionDigit":0

"percentPattern":{

"patternID":"Percentage_01", "decimalSeparator":".", "groupingSeparator":",", "hint":"1000,001.01", "maxFractionDigit":2, Interface Control Document 31 November 2018

"minFractionDigit":2}, "timePattern":{"dateTimePatternID":"hh:mm aaa", "hint":"hh:mm AM/PM", "pattern":"hh:mm aaa"

Response

Header

200: OK. or ERROR see HTTP error codes.

Sample Set User Preferences Request

{"userID":"1008804055", "bizx_username":"1008804055", "bizx_status":"t", "timeZone":"America/Chicago", "displayScheduleInUserTimeZone":true, "localeID":"English", "bizx_localeID":"en_US", "bizx_timeZone":"America/Chicago", "languageCode":"en", "percentageSymbol":"%", "currencyPattern":{"patternID":"Currency_01","decimalSeparator":".","groupingSeparator":",","hint":"

1000,001.01","maxFractionDigit":2,"minFractionDigit":2}, "currencyPreference":{"currencyID":"USD","currencySymbol":"$","description":"US

Dollar","labelId":"data.currency.USDollar","active":true,"globalDefault":true}, "datePattern":{"dateTimePatternID":"M/d/yyyy","hint":"MM/DD/YYYY","pattern":"M/d/yyyy"}, "doublePattern":{"patternID":"Double_01","decimalSeparator":".","groupingSeparator":",","hint":"100 0,001.01","maxFractionDigit":2,"minFractionDigit":2}, "longPattern":{"patternID":"Long_01","decimalSeparator":null,"groupingSeparator":",","hint":"1000,0

01","maxFractionDigit":0,"minFractionDigit":0}, "percentPattern":{"patternID":"Percentage_01","decimalSeparator":".","groupingSeparator":",","hint":

"1000,001.01","maxFractionDigit":2,"minFractionDigit":2}, "timePattern":{"dateTimePatternID":"hh:mm aaa","hint":"hh:mm AM/PM","pattern":"hh:mm aaa"}

Sample Set User Preferences Response

{"@odata.context":"$metadata#UserPreferences/$entity","@odata.metadataEtag":"W/\"d444f430- 486e-4caa-b274-d2c98296b0cf\"","userID":"1008804055","countryCode":null,"currencyPattern":{"patternID":"Currenc y_01","decimalSeparator":".","groupingSeparator":",","hint":"1000,001.01","maxFractionDigit":2,"mi nFractionDigit":2,"pattern":null},"currencyPreference":{"cacheKey":null,"currencyID":"USD","curren cySymbol":"$","description":"US

Interface Control Document 32 November 2018

Dollar","labelId":"data.currency.USDollar","lastUpdateTimestamp":null,"lastUpdateUser":null,"active

":true,"globalDefault":true},"datePattern":{"dateTimePatternID":"M/d/yyyy","hint":"MM/DD/YYYY"

,"pattern":"M/d/yyyy"},"displayScheduleInUserTimeZone":true,"doublePattern":{"patternID":"Double

_01","decimalSeparator":".","groupingSeparator":",","hint":"1000,001.01","maxFractionDigit":2,"min

FractionDigit":2,"pattern":null},"languageCode":"en","localeID":"English","longPattern":{"patternID" :"Long_01","decimalSeparator":null,"groupingSeparator":",","hint":"1000,001","maxFractionDigit":0, "minFractionDigit":0,"pattern":null},"percentPattern":{"patternID":"Percentage_01","decimalSeparato r":".","groupingSeparator":",","hint":"1000,001.01","maxFractionDigit":2,"minFractionDigit":2,"patter n":null},"percentageSymbol":"%","rtl":false,"timePattern":{"dateTimePatternID":"hh:mm aaa","hint":"hh:mm AM/PM","pattern":"hh:mm aaa"},"timeZone":"America/Chicago","bizx_localCurrency":null,"bizx_localeID":"en_US","bizx_time Zone":"America/Chicago","bizx_username":"1008804055","bizx_status":"t"}

Sample FindItem Request

/learning/odatav4/public/admin/search-service/v1/Items?$filter=icriteria/itemID%20eq%20'10176'

Sample FindItem Response

{"@odata.context":"$metadata#Items","@odata.metadataEtag":"W/\"f3e7225e-d563-47e3- 9b33-a1f5e9704b39\"","value":[ {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1062098040000," itemTitle":"VA Cyber Security Awareness - FY05","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"","deliveryMethodID":"17","domainID":"EES","active":false,"tota lCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1062388860000," itemTitle":"VA Cyber Security Awareness - FY03","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"","deliveryMethodID":"17","domainID":"EES","active":false,"tota lCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1064980860000," itemTitle":"VA Cyber Security Awareness - FY04","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"","deliveryMethodID":"17","domainID":"EES","active":false,"tota lCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1096603260000," itemTitle":"VA Cyber Security Awareness - FY05","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"","deliveryMethodID":"17","domainID":"EES","active":false,"tota lCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1128184380000," itemTitle":"VA Cyber Security Awareness - FY06","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"","deliveryMethodID":"17","domainID":"EES","active":false,"tota lCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1159794960000," itemTitle":"VA Cyber Security Awareness - FY07","classificationID":"CONTINUOUS

ONLINE

ACCESS","sourceID":"LIBRIX","deliveryMethodID":"17","domainID":"EES","active":false ,"totalCount":null}, {"icriteria":null,"itemID":"10176","itemTypeID":"VA","revisionDate":1170949980000," itemTitle":"VA Privacy and Information Security Awareness and Rules of

Interface Control Document 33 November 2018

Behavior","classificationID":"CONTINUOUS ONLINE ACCESS","sourceID":"ICONTENT","deliveryMethodID":"17","domainID":"DVA","active":tru e,"totalCount":null}

Sample AssignCurriculum Request

{ "primaryKey":"", "curricula" : [

"studentID":"Student.Student0101", "personGUID": "", "qualificationID":"DVA-003", "assignmentDate":1540589452471, "priority": 1

Sample AssignCurriculum Response

{"@odata.context":"$metadata#Curricula/$entity","@odata.metadataEtag":"W/\"f3e7225e-d563-47e3-

9b33-a1f5e9704b39\"","primaryKey":"","curricula":[

"studentID":” Student.Student0101", "personGUID":"", "qualificationID":"DVA-003", "assignmentDate":1540589452471, "priority":1, "errorMessage":null

Sample Email Messages – TMS Create – Login Info

From: MVI.System@va.gov [mailto:MVI.System@va.gov]

Sent: Wednesday, October 10, 2018 10:00 AM

To: student@slsolutions.com

Subject: TMS Training Account Notification: Temporary Login Information

Importance: High

This is an automated email sent from the Department of Veterans Affairs

(VA). Your Talent Management System (TMS) Account login information is below:

Username: 1638411

Temp Password: 1638411

TMS Login URL: https://www.tms.va.gov/secureauth34

** Please do not reply to this message. Replies to this message are routed to an unmonitored mailbox.

mailto:MVI.System@va.gov mailto:MVI.System@va.gov mailto:student@slsolutions.com https://www.tms.va.gov/secureauth34

Interface Control Document 34 November 2018

Sample Email Messages – TMS Create – Assign Item

From: MVI.System@va.gov [mailto:MVI.System@va.gov] Sent: Tuesday, October 16, 2018 11:25 AM

To: student@slsolutions.com

Subject: Action Required - TMS Onboarding Training Account Notification: TMS

Onboarding Training Account

A new Talent Management System (TMS) account for LEARNER, STUDENT has been created by the VA Onboarding Solution.

Listed below is the training assigned to facilitate the onboarding process.

Please take action by 11/14/2018. Please follow up with your VA Supervisor /

VA Contracting Officer Representative for any questions about this notification. You will receive a separate email with your TMS login credentials.

Username: LEARNER, STUDENT

Training: 10203-Privacy and HIPAA Training [2007-02-14T14:47:00-06:00] DUE

DATE: 11/14/2018

Sample Email Messages – TMS Create – Assign Item

From: MVI.System@va.gov [mailto:MVI.System@va.gov] Sent: Tuesday, October 16, 2018 11:25 AM

To: Student@slsolutions.com

Subject: Action Required - TMS Onboarding Training Account Notification: TMS

Onboarding Training Account

A new Talent Management System (TMS) account for LEARNER, STUDENT has been created by the VA Onboarding Solution.

Listed below is the training assigned to facilitate the onboarding process.

Please take action by 10/21/2018. Please follow up with your VA Supervisor /

VA Contracting Officer Representative for any questions about this notification. You will receive a separate email with your TMS login credentials.

Username: LEARNER, STUDENT

Training: 10176-VA Privacy and Information Security Awareness and Rules of

Behavior [2007-02-08T09:53:00-06:00] DUE DATE: 10/21/2018 mailto:MVI.System@va.gov mailto:student@slsolutions.com mailto:MVI.System@va.gov mailto:susan@slsolutions.com

Interface Control Document 35 November 2018

3.2.3.2.4. Update Mandatory Training

3.2.3.2.5. Deactivate EDR Account, Reactivate EDR Account

Deactivate EDR account consists of the following ghappy path flow:

Using the EDR Person ID call ProvisionSeparateTMSRecordForProvision

Sample Deactivate EDR Account

3.2.4. Security Requirements

The interface is FIPS 140-2 compliant.

MVI PSIM and TMS must both maintain a VA Authority to Operate and follow VA guidelines detailed within VA Handbook 6500. VA Handbook 6500 includes federally mandated security requirements.