Party-Bus-(ABMS-ADCE).md

+Party Bus is our internal name, Advanced Battle Management System - All Domain Common Environment (ABMS-ADCE) is the external name. 
+
+# Platform One - Party Bus Offering
+
+                    
+1. [Product] Provide a one stop DSOP development environment, compatible with the C-ATO.
+2. [Service] Guide customers through the C-ATO process.
+3. [Service] Train customers to be effective and efficient in the C-ATO environment.
+\#Translation  
+1. Cloud One Development and production environments, with a CI/CD pipeline.
+2. SMEs/Sherpa's/etc. that understand the C-ATO and can help customers operate and get their app to production.
+3. Provide training for our environment so that people understand all the things.
+
+
+## Customer Persona's
+
+                    
+1. A product team that wants their missions capability deployed
+2. A larger program, who's not landed on what they want or need. (They are evaluating the environment and learning)
+3. Missions capability end users. (Persons that want to engage with product teams and test capabilities)
+## Roadmap
+(*Note: nothing is done until the customer can use it on a daily basis*)  
+Current State: Cloud One Environment's P1D (dev) and P1P (prod) have mattermost deployed and available at IL2.
+### Now
+1. DSOP environment (IL2/IL4/IL5)
+   1. migration of "ninja" tools into P1D/P1P
+   2. integration of tools for Single Source Authenticaion and Authorization
+   3. migration of pipelines
+2. Self Service Registration and Onboarding
+   1. ChatBot customer registration
+   2. Automated environment creation
+### Next
+1. Enterprise Ticketing
+2. Enterprise Support
+3. Customer Facing Portal
+4. DSOP Environment (IL6) VI2E Collaboration
+### Later
+1. Internal Customer Landing Dashboard
+2. Platform One "Stack Exchange"
+
+Also, check out updates [here](https://p1.dsop.io/#/abms-adce) on the P1 site! 
\ No newline at end of file