Appendix 4-Triggering Systems Amend 2.pdf
PDF 18 KB Posted
- Attached to
- Customer Satisfaction Survey (CSS) RFP
- Solicitation number
- HTC711-20-R-R021
View the file
Other files
Show all 34
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Appendix 4
System Triggers/Responses
Although two triggering systems are called out here, the triggering interface shall be used to connect any subscriber system approved by the Government.
Defense Personal Property System (DPS) is a centralized, web-based, and single point of access system for worldwide shipment of personal property Department of Defense (DoD) and United States Coast Guard (USCG). Currently, DPS is a self-service system, offering access for government and industry users to accomplish self-counseling, online rate solicitation, traffic distribution, shipment management and tracking, invoicing, Transportation Service Provider (TSP) performance evaluations, and Uniformed Service member and DoD/USCG civilian employee claims submittals following relocation. Additionally, DPS was recently updated to subsume the capability to order and manage storage for the Non-Temporary Storage (NTS) program.
MilMove (DPS Prototype) is a cloud-based system that is being developed using industry best practices in agile software development and user-centered design. MilMove will be used to support the Global Household Goods Contract (GHC) which includes on-boarding of DoD personnel who are relocating. Along with on-boarding, MilMove will also issue task orders, handle invoicing, and document receipt of service. Once MilMove is fully operational, DPS will be scaled down and eventually replaced by MilMove.
Integrated Data Environment & Global Transportation Network Convergence (IGC) is the DoD system of record for In-transit Visibility (ITV) and for Asset Visibility (AV). The enabling ITV capabilities provide USTRANSCOM’s customers the ability to track the identity, status, and locations of DoD unit and non-unit cargo and passengers, leveraging data provided by the military Services, commercial carriers, the Defense Logistics Agency (DLA), USTRANSCOM, and USTRANSCOM's components. IGC integrates that data and makes it available to the user, including historical data. The enabling AV capabilities provide global visibility of assets in all classes of supply, which are organized by categories: In-Storage, In-Transit, and Total Asset Visibility. Utilizing IGC, USTRANSCOM optimizes the effectiveness and efficiency of the DoD logistics pipeline in support of the users, Military Services, Combatant Commands (CCMDs), and subordinate Joint force commands including Joint Task Forces (JTFs).
The CSS contractor is to build two (2) interfaces to support two (2) external information exchanges, trigger and response.
1. Trigger. The Government expects this to be a web service and the offeror to maintain up to three versions of the service (previous, current and next). That way, if we evolve the service, interfacing partners will have a path to migrate between them without losing service. It should not matter whether we have one system or multiple systems connecting to CSS to submit triggers, the interface and process will be the same. CSS will have to ensure that only authorized systems are allowed to connect. The CSS contractor should include the WSDL(s) (Web Service Delimited Language) on their site so that the web service is documented and access process is explained. An example of that would be https://api-alpha.sam.gov/prodlike/ws/fboendpoint/fbo.wsdl
2. Response (IGC). This will be a point to point interface with the GEX, most likely using SFTP. No matter how many entities connect via the trigger, all the data will be fed to the GEX.
File details come from the government source that posted it. Updated .