L3AV DSP Programming Process v1.0.03
Purpose & Scope:
This card describes the complete process required for successful programming of custom DSP solutions for AV projects.
Process Flowchart:
Process:
- DSP task is assigned to programmer in NetSuite by Engineering Manager
- DSP Programmer shall attend all project related meetings
- PM shall invite the programmer to the internal KO meeting
- This is the time where any issues or discrepancies are addressed.
- Record any meeting notes in the One Note file for programming in the client's Team
- DSP tasks are added to the Programming calendar by Engineering Manager based on weekly meetings with the L3 Micron team and OPS
- All programmers have access to add/remove items from the programming calendar.
- This is designed to maintain visibility of items not directly related to programming jobs. Each programmer is encouraged to add any personal/professional obligations to the calendar for visibility
- In the event there is a conflict contact the Engineering Manager to resolve any schedule issues.
- Programmer creates folder in their individual Dropbox folder
- Sample folder structure is located at C:\Dropbox (Level 3 Audio Visual)\PROGRAMMING\_Resources\9999 - CLIENT - Job Name - DSP only
- This only applies when doing DSP only jobs
- Use of this folder structure is mandatory
- Files are created with the following naming convention
- Example = 4349_Carollo_Portland_Room1_SingleSIO_v1.07
- Format = [ProjectNumber]_[Client]_[ProjectName]_[SystemNameIfApplicable]_[DSPType]_v[Major].[Minor].[Fork]
- Use of this naming convention is mandatory
- Dropbox updates are synced daily
- In the event that Dropbox is not available at the end of a particular day and alternative backup is required. This is typically in the form of an external drive.
- If an external drive is needed, inform the Engineering Manager and L3AV will provide one
- Do not power off your laptop without an external copy somewhere
- Daily backup of changed files is mandatory
- The DSP file is created for the project and completed prior to staging date
- DSP time is scheduled by Engineering Manager, but it is the programmer’s responsibility to ensure sufficient time is allocated and to notify Engineering Manager if additional time is needed or if too much time has been allocated.
- For systems including Shure Microphones, a Designer file must be created during development and loaded during staging (latest MXA920 are highly affected by position)
- Staging is scheduled by Engineering Manager and Scheduling Coordinator in alignment with OPS efforts
- Prior to staging the a meeting MUST be scheduled for a warm handoff meeting with the assigned Field Engineer
- The Scheduling Coordinator will inform the DSP programmer who the FE assigned to staging is and when staging is scheduled to begin.
- With this information the DSP programmer will arrange the handoff with the assigned FE
- This requires a minimum of sharing the DSP file with the field engineer and being available to answer any questions.
- For larger site files a Teams meeting is required to review the file in detail (at the discretion of the FE)
- Staging includes complete testing of all DSP and programmed functions
- DSP programmers do not typically assist during staging unless architectural changes to the DSP file are required.
- Field Engineers load and test the DSP file in staging
- Onsite deployment is added to the programming calendar by the Engineering Manager in alignment with OPS
- The DSP programmer shall be available during the onsite deployment process and assist as needed
- Once all functions have been verified by the onsite team the Field Engineer shall copy the final version of DSP programming in L3AV format to Cortex once the onsite deployment is completed
- It is not the responsibility of the DSP programmer to get the final file from the Field Engineer