Attachment 3H myServices and eCC_Integration Documentation.docx

myServices – Procurement/Expendables Integrations: The myServices Procurement and Expendables integrations send Procurement and Expendables order request forms through ILMS to the Ariba/Expendables systems. When a request is submitted in myServices, it is tagged with an “MYS” status to designate that it has not yet integrated. A batch PeopleSoft job initiated by ILMS runs every 15/20 minutes to transfer Procurement/Expendables request data to the ILMS system, which in turn labels the request with “STI” in myServices. After another 15/20 minutes, requests are integrated from ILMS to Ariba/Expendables. myServices will continue to receive updates about requests in similar PeopleSoft batch jobs to alert customers about the progress of their requests.

myServices – Maintenance and Repair Integration: The myServices Maintenance and Repair Integration sends Maintenance & Repair work order forms through ILMS to the Global Maintenance Management System (GMMS) system. When a request is submitted in myServices, it is tagged with an “MYS” status to designate that it has not yet integrated. A batch PeopleSoft job, initiated by ILMS, runs every 20 minutes to transfer the Maintenance and Repair request data to the GMMS system, which in turn labels the request with “0” in myServices. myServices receives status updates about the open requests through a similar batch PeopleSoft job to alert customers about the progress of their requests.

myServices – DOS_MYS_TBLS job: The DOS_MYS_TBLS job transfers the Ariba approval flow and Request Office information from Ariba to myServices via a PeopleSoft job. This job also updates the following information for expendables catalog items within myServices: Item ID, Business Unit, Item Description, Item Category, Item Subcategory, Stock Number Available, Selected CB, Unit of Measure, Issue Price, Status.

myServices – Active Directory: myServices uses the LDAP integration with ADFS to create accounts for Department of State users with accounts in Active Directory who do not already have an existing myServices account. For existing myServices Department of State accounts, the integration matched the Active Directory account to the myServices account. The integration also populates and maintains the following fields from AD in the myServices user account: SAM Account Name/User ID, First Name, Last Name, Business Email, AD Country/Region, GUID, and Active status.

myServices – FMIS Integration: myServices integrates directly with the FMIS database through a Mid Server to submit motor pool trip requests. Requestors can submit motor pool trip requests and send the trip request data to the Fleet Management Information System (FMIS). Requestors are able to create and submit a Local Trip Request, Self-Drive Trip Request, or Courier Service Trip Request in myServices. myServices pulls status updates from FMIS to update the Motor Pool Trip Request ticket in myServices to ensure the user can see the status of their request throughout the process.

myServices – RPA: This is a manual integration where the data from Real Property Application (RPA) is automatically exported to the myServices Team then manually uploaded into the myServices location table to ensure all Properties and Units in myServices are kept up-to-date with the DOS system of truth.

myServices – EDW: myServices stores data for EDW in a custom set of tables, which are manually exported and uploaded to the EDW SharePoint site bi-weekly. This data is then used as part of the CMI monthly report.

myServices eCC – Dept. of Defense: myServices eCC is integrated with DOD’s itinerary management application, APACS. DOD travelers mostly do not require an eCC, but awareness at post is needed. When an itinerary is approved in APACS, there is an option to make available to eCC. myServices eCC initiates a pull of data from APACS every 3 hours, looking back 24 hours to check for newly approved itineraries. All itineraries meeting the 2 criteria are pulled into myServices: approved in APACS and marked for eCC. These records are pulled into a table along with copies of eCC itineraries where users can view them together. The itineraries seen are based off the user’s permissions within eCC. APACS records are shown for the entire country since they do no specify post the same way as myServices eCC.

myServices eCC – Dept. of Energy: myServices eCC is integrated with DOE’s itinerary management application, FTMS. DOE travelers are required to submit itineraries in both FTMS and myServices eCC. After completing a submission within FTMS, a user can select to transfer the itinerary to eCC. The integration occurs on demand and creates a draft itinerary within myServices eCC. The user who created the record in FTMS and the associated traveler both can view and edit the itinerary once in myServices eCC. The data input in FTMS will already be populated in the itinerary, and the user fills out the remaining fields before submission within myServices eCC. Itinerary status updates are sent to both the traveler and to FTMS, but changes that occur in FTMS or myServices eCC after the initial integration to not update the itinerary in the other location.