This article outlines the collaborative team structure and initial administrative requirements for new OPS-COM enterprise clients. It is intended for administrators and project leads to ensure all stakeholders are prepared for a seamless system deployment.
### Team Accountability A successful deployment relies on a collaborative approach between your organization and the OPS-COM team. To ensure the system aligns with your specific operational processes, we require clear roles and responsibilities from both sides. #### OPS-COM Team Responsibilities - **Overall Project Manager**: Manages the technical deployment, coordinates training, assists with system setup, and ensures all custom requirements are met. - **Setup and Configuration Specialist**: Advises on system best practices, shares solutions from other clients, and assists in mapping your current business processes to the system. You will receive a document containing business requirement questions that must be completed before the configuration phase begins. - **Trainer and Support Liaison**: Provides system training and introduces you to post-launch support processes. #### Client Responsibilities Every client must designate an internal **Project Manager**—often the Parking Manager—who understands your business goals and can dedicate time to the project. This person is responsible for assembling the following team: - **IT Contact**: Manages Single Sign-On (SSO) and system integrations. - **Hardware Contact**: Manages handheld devices, printers, and cameras. - **Financial Contact**: Manages hosted payment details and billing information.If your organization is unable to provide a dedicated **Project Manager**, one can be provided by the OPS-COM team for an additional fee.
### Setup of Customer Account and Billing Once your contract is signed, you will be initialized in our billing system and receive a welcome email containing your account details. To finalize your account setup, please provide the following: - **Accounts Payable Contact**: Provide a name, email address, and telephone number. - **Main Project Contact**: Provide a name, address, email address, and telephone number. - **Departmental Contacts**: Provide the names and email addresses for your **IT**, **Hardware**, and **Financial** contacts. - **Purchase Order Number**: Provide this if applicable to your organization. ### Security and Support #### Communication of Security Information We prioritize data safety and system security. If your IT department requires documentation regarding our security protocols, please share the **OperationsCommander Security White Paper**. If further information is required, email **support@ops-com.com** to arrange a consultation with our security specialist. #### Utilizing OPS-COM Support Our support team is dedicated to your success throughout the rollout process. You will be directed to communicate various setup requirements and questions directly to **support@ops-com.com**. Do not hesitate to reach out to this address for assistance throughout your deployment. --- ### Best Practices and Considerations - **Active Participation**: Your **Project Manager** must be available to attend the **Project Kickoff**, as well as all subsequent training and setup sessions. - **Preparation**: **Complete all pre-configuration questionnaires promptly to ensure your project timeline stays on schedule.** - **Integration Planning**: Engage your **IT Contact** early in the process to ensure all technical requirements, such as **SSO** or hardware integrations, are identified before the configuration phase begins.