MilMove Technical Summaryv2.pdf

Introduction: MilMove is a replacement for the current Defense Personal Property System (DPS) which moves shipments using an individual tender based contracting approach. Personal property customers will log in to MilMove to request their shipments. Government office personnel will use MilMove to hold the Global Household Goods Contract (GHC) accountable, a contract mechanism using a more traditional Indefinite Delivery Indefinite Quantity (IDIQ) contract instead of picking from a pool of about 900 providers. MilMove is currently working to interface with the Global Household Goods contractor’s systems so that government shipping office personnel can review customer requests in MilMove, issue task orders for moving and storage of personal property, as well as management of payment requests received from the GHC prime. MilMove sends approved payment requests to the Third Party Payment System (TPPS) for payment via EFT to GHC. Quality Assurance Evaluators will file their reports on GHC performance in the MilMove system. MilMove will connect to Advana data warehouse for analysis of operational data provided. A future goal of MilMove is integration with personnel systems from the Military services to receive move orders to enable accurate flow of entitlement and accounting information to reduce errors that occur in the current system. However, there are still several remaining features needed for customers, office users, admins, and GHC prime to build prior to orders integration.

MilMove is a web application built primarily using Google’s Go language for the backend Application Programming Interfaces (API). The frontend is a JavaScript application that calls the backend APIs. The application and infrastructure use many Amazon Web Services (AWS) Cloud Service Offerings (CSO) that are maintained by AWS to reduce the overhead and maintenance of the application and infrastructure while taking advantage of the strong security investment this commercial entity has placed in hardening its CSOs. MilMove is currently hosted in the AWS GovCloud (US West) region. The MilMove ecosystem also includes use of a few Software-as-a-Service CSOs (e.g., JIRA, CircleCI, GitHub, etc.) from other Cloud Service Providers (CSP). The application runs within Docker containers via AWS Fargate. The number of containers will automatically scale up and down based on resource demands during the full production release. The application stores its business data in AWS Relational Database Service (RDS) for PostgreSQL. The application containers are fronted by either an Application Load Balancer (ALB) or a Network Load Balancer (NLB) that receive traffic and distribute it across the Fargate containers.

Current ecosystem:

• MilMove public open source repositories:

https://github.com/transcom/mymove: my.move.mil application repository https://github.com/transcom/milmove_orders: orders.move.mil application repository https://github.com/transcom/milmove_admin: engadmin.move.mil application repository https://github.com/transcom/milmove_load_testing: load testing repository for application code https://github.com/transcom/prime_api_deliverable: documentation for usage of the Prime API https://github.com/transcom/circleci-docker: Docker image repository for build and deploy https://github.com/transcom/nom: Navy Orders Muncher repository

• Go, HTML, CSS, JavaScript, JSON, XML, SQL, Terraform

• React and Redux JavaScript libraries

• PostgreSQL RDBMS

• Docker Containers

• Linux Operating System

• Git, Homebrew, Chamber, Node Package Manager

• Okta, Slack, Google G-Suite, JIRA, Github, CircleCI, PagerDuty, Keeper Password Security and

Secrets Manager, Cypress libraries

• Amazon Web Services (AWS)

• DoD Risk Management Framework (RMF)

• Cyber Security Service Provider (CSSP)

• Defense Information System Agency (DISA) Security Technical Implementation Guides (STIGs)/Security Requirements Guides (SRGs).

• National Security Agency Security Configuration Guides