Viewing as , ,
Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Projects is switched off
Projects, the schedule, planning, the work plan and the Lab. This demo has the Projects module switched off in Organisation settings.
Project PRJ-22Firmware rolloutDublin officeSimulated
Poly VideoOS 4.7.0 rollout
Plan gate due 30 Oct · 12 open tasks, none waitingchecked just now
ScheduleOn planPlan is due 30 Oct; target 11 Dec.
Cost€1,000 in hand€0 spent or ordered of €4,000 approved, €3,000 still estimated.
ScopeAs chartered5 spaces, firmware rollout; no change requests.
Next gatePlan gatedue 30 OctService manager, AV signs it off. Lab test passed. Version approved as the standard.
Nothing stuckNo tasks or dependencies waiting on anything, and no open issues.
Timeline
12 Oct to 11 Dec, following the Firmware rollout playbook, version 1.0Today
PlannedActualPast the planGate, filled when signed off
Plan: what happened
Not reached yet. Planned to end 30 Oct (the playbook allows 2 to 4 weeks).
Tasks in this phase
Read the 4.7.0 release notes and ADV-002 for the X52, X32 and TC10Anna Byrne · Done · fix capturedLab pass: every check in LAB-07 on the X52, X72, X32 and TC10, including a rollback to 4.6.2Nora Walsh · DoingDecide whether 4.7.0 becomes the standardSofia Reyes · To doChoose the pilot rooms and the waves by office, and avoid the year-end freezeKatya Novak · To doThe gate, signed off by Service manager, AV
- Lab test passed
- Version approved as the standard
- Pilot spaces and waves agreed
What the playbook says: 5 steps
- AV and IT delivery engineerRead the release notes and the advisories for every model that runs this firmware
- Innovation engineerLab pass: every check on every model, including a rollback
- Service manager, AVDecide whether the version becomes the standard
- AV and IT delivery engineerCount the units per site and choose the pilot spaces, one of each space type
- Project managerPick the waves by office and avoid busy weeks and change freezes
The Deploy board51 devices in 5 spaces, each through four steps. Tick each device's checklist, or hand it to the agent.0/51Provision0/51Install0/42Configure0/51CommissionOpen Deploy
Deploy: what happened
Not reached yet. Planned to end 23 Nov (the playbook allows 2 to 6 weeks).
Tasks in this phase
Tell the Dublin and Copenhagen offices the day and time of their wavesKatya Novak · To doUpdate Heron (pilot) to 4.7.0Liam Doyle · To doUpdate Gannet (pilot) to 4.7.0Liam Doyle · To doReboot Heron and check its camera source, then run the verification for both pilot roomsAnna Byrne · To doUpdate Kestrel (wave 1) to 4.7.0Liam Doyle · To doUpdate Heron at the Copenhagen office (wave 2) to 4.7.0Tom Ashby · To doUpdate Curlew at the Copenhagen office (wave 2) to 4.7.0Tom Ashby · To doThe gate, signed off by AV and IT delivery engineer and Service manager, AV
- Pilot spaces passed
- Every wave updated
- Every unit reports the target version
What the playbook says: 10 steps
- AV and IT delivery engineer · ProvisionPut the target version in the configuration, and check updates are still off in device management
- Project manager · ProvisionTell each site the day and time of its wave
- On-site technician · InstallUpdate the pilot spaces and leave them a week
- On-site technician · InstallUpdate each wave, one site at a time
- AV and IT delivery engineer · InstallUpdate remotely where device management can do it, and on site where it cannot
- AV and IT delivery engineer · ConfigureCheck each unit's settings survived the update, and fix any that did not
- AV and IT delivery engineer · CommissionRun the space verification for every pilot space, and for a sample in each wave
- AV and IT delivery engineer · CommissionCheck the points the advisories name, such as the camera after a reboot
- Service manager, AV · CommissionRead the pilot report and decide whether to continue, pause or roll back
- On-site technician · CommissionRoll back a space if it fails, and raise an incident for the fault
Hand over: what happened
Not reached yet. Planned to end 29 Nov (the playbook allows 1 weeks).
Tasks in this phase
Set 4.7.0 as the standard on the firmware line and the model pagesSofia Reyes · To doHandover note to the service desk: what changed and which symptoms to expectKatya Novak · To doThe gate, signed off by Service manager, AV
- The standard matches what is in the spaces
What the playbook says: 2 steps
- Service manager, AVSet the firmware line's standard version and update the model pages
- Project managerTell the service desk what changed and which symptoms to expect
Closed: what happened
Not reached yet. Planned to end 11 Dec (the playbook allows - weeks).
Tasks in this phase
None recorded.
The gate, signed off by Programme manager
- Lessons captured
What the playbook says: 1 step
- Project managerFeed what was learned back into this playbook and the model pages
Spaces
3.03 HeronNot started: Pilot room: a Studio G62 with an external E60 camera. ADV-002 names the X52 and X32, so this room shows whether the G62 does the same3.05 GannetNot started: Pilot room3.06 KestrelNot started: Wave 1: Dublin office4.03 HeronNot started: Wave 2: Copenhagen office4.04 CurlewNot started: Wave 2: Copenhagen office
People and time
KNKatya NovakProject manager3 of 20 h · Picks the waves and tells each site its day
ABAnna ByrneLead engineer6 of 24 h · Reads the advisories, checks each pilot room and reads the pilot report
NWNora WalshLab testing8 of 16 h · Runs the Lab pass (LAB-07) on every model
LDLiam DoyleTechnician0 of 12 h · Updates the Dublin office rooms
TATom AshbyTechnician0 of 8 h · Updates the Copenhagen office rooms
SRSofia ReyesService owner (sign-off)1 of 4 h · Decides whether 4.7.0 becomes the standard
Budget
€4,000approved
- Spent
- €0
- Ordered, not yet paid
- €0
- Still an estimate
- €3,000
- Left if all goes to plan
- €1,000
To do11
Doing1
Waiting on0
Lab pass: every check in LAB-07 on the X52, X72, X32 and TC10, including a rollback to 4.6.2PlanDue 30 Oct
Decide whether 4.7.0 becomes the standardPlanDue 2 Nov
Update Heron (pilot) to 4.7.0Deploy · 3.03 HeronDue 9 Nov
Update Gannet (pilot) to 4.7.0Deploy · 3.05 GannetDue 9 Nov
Reboot Heron and check its camera source, then run the verification for both pilot roomsDeploy · 3.03 HeronDue 16 Nov
Update Kestrel (wave 1) to 4.7.0Deploy · 3.06 KestrelDue 18 Nov
Update Heron at the Copenhagen office (wave 2) to 4.7.0Deploy · 4.03 HeronDue 24 Nov
Update Curlew at the Copenhagen office (wave 2) to 4.7.0Deploy · 4.04 CurlewDue 24 Nov
Set 4.7.0 as the standard on the firmware line and the model pagesHand overDue 4 Dec
Handover note to the service desk: what changed and which symptoms to expectHand overDue 11 Dec
Archived tasks 0
Assign to
Risks (might happen), issues (have happened), decisions and dependencies, in one place. Open first.
No risks, issues, decisions or dependencies on record for this project.
A change to what the project delivers. Anyone on the project can propose one; the approver decides, and the log keeps who and when.
No change requests. The scope is as chartered.