NOTE: Phases intentionally overlap in time during iterative design/build/test process.
Phase 1: Initiation
- Engagement Plan: Establish a clear communications plan between the vendor and the project team.
- Formal Project Plan: Mapping out the rest of the project in schedule, expectations, and agreement between City and vendor on how to approach the specific deliverables for the remainder of the project.
- Training: Initial core team training on the primary software components of the system.
- Infor Public Sector (IPS) - permitting software
- ProjectDox - digital plan review software
- Sandbox /Training Environment: Setup a training environment for the new software.
- Proof of Concept: 12 sample configurations to demonstrate that the software can meet the City’s needs.
Phase 2: Design
- Develop detailed specifications for:
- All application and permit types
- Data conversion from TRACS and other current City databases
- Interfaces with SAP and other City systems, as well as with the State’s system
Phase 3: Build
- Configure system and integrate platforms to provide functions matching the requirements gathered in Phase Two.
Phase 4: System Test and Acceptance Test
- System Test: Team Sierra (vendor) tests workflow configurations as-built
- Acceptance Test: City tests workflow configurations to confirm they include all functions listed in requirements
Phase 5: Training and Final Testing
- Train BDS Technology Team to maintain the system
- Train all City permitting employees to use the system
- City tests system with all data loaded and interfaces connected
Phase 6: Go-Live
- Launch new system and begin using it
- TRACS available as archive only
Phase 7: Warranty
- 3 month duration
- Vendor available to fix any bugs