Prerequisites: How to Join Party Bus
Overview
Use this document to understand the prerequisites for onboarding onto Party Bus.
Required Items to Be a Party Bus Customer
All teams require the below to be onboard to Party Bus:
- Government Sponsor/Funding
- Government POCs
- Explanation of your tech stack
- Dockerfiles of your application (if applicable)
- No Foreign National involvement
Onboarding Steps
There are six steps to the onboarding process. This process may take up to a few months to complete.
Overview of Onboarding Steps
- Complete the Get Started with P1 Form
- Attend an AES
- Attend a Technical Fit Session
- Assess price quote and complete contract
- Prepare for pipeline or package creation
- Attend LEAP Workshop
A series of P1 teams will contact you during your onboarding process. These teams include:
- CST
- PBO
- LEAP
- Party Bus Engineers
- TAMs
- MDO
- BAMs
1. Complete the Get Started with P1 Form
Complete our Get Started with P1 Form. The CST will then reach out to schedule a meeting based on your responses to the form.
What will happen during the introductory meeting:
- Collect/confirm the names and email addresses of your team’s Government and Technical POCs, and organizational data.
- P1 will gain a deeper understanding of your application.
- P1 will provide a product and services overview for all applicable P1 offerings that align with your application’s requirements.
- CST will provide you with a pricing ROM for any associated P1 services.
After your call with the CST, the TAM will reach out to schedule an AES.
Well-qualified Party Bus applicants may have the CST call and AES at the same time.
2. Attend an Application Evaluation Session
During an AES, the TAM will gather lower-level details about your application. The following items will need to be known by your team before attending an AES:
- Programming languages
- Package managers
- Database type
- External connections
- Number of images compiled from the source
- IL needed for deployment (staging and/or production)
After your AES session, the PBO team will reach out to schedule a Technical Fit Session if applicable.
3. Attend a Technical Fit Session
During a Technical Fit Session, you'll discuss your architectural diagram with the TAM and PBO team to determine whether your application is compatible with Party Bus's offerings. They will also brief you on what makes deploying to Party Bus different from other platforms, including the platform's limitations and restrictions.
The TAM will conclude if your application is one of the following:
- A good fit for Party Bus,
- A potentially good fit for Party Bus after some modification (e.g., splitting out a monolithic application into separate front-end and back-end applications), or
- Not a good fit for Party Bus.
4. Assess Price Quote and Complete Contract
Once your application has passed the Technical Fit, the CST will prepare your official price quote.
After receiving your quote, you have 30 days to review and approve it. Should you accept the quote, the CST and BAMs will facilitate your payment or funding. Your team will then be provisioned access to GitLab, P1 ChatOps, Jira, Confluence, and various pipeline tools.
5. Prepare for Pipeline or Package Creation
It’s time to prepare your application and teams for the Party Bus Pipeline. Review your next onboarding steps with the MDO team to prepare for the Pipeline Queue.
6. Attend LEAP Workshop
Congratulations! It’s time to attend your team’s LEAP Workshop. The PBO team will provide you with information on the LEAP Workshop, including agenda, scheduling, and links.
Welcome to Party Bus!