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-17AV refreshCopenhagen officeSimulated
Copenhagen office meeting room refresh
Plan gate due 30 Oct · 4 open tasks, none waitingchecked just now
ScheduleOn planPlan is due 30 Oct; target 18 Jun.
CostDKK 0 in handDKK 0 spent or ordered of DKK 84,000 approved, DKK 84,000 still estimated.
ScopeAs chartered4 spaces, av refresh; no change requests.
Next gatePlan gatedue 30 OctProgramme manager signs it off. Scope and budget agreed. Batches fit the year plan.
Nothing stuckNo tasks or dependencies waiting on anything, and no open issues.
Timeline
12 Oct to 18 Jun, following the AV refresh playbook, version 1.4Today
PlannedActualPast the planGate, filled when signed off
Plan: what happened
Open, due 30 Oct
Collecting units due and a budget line for the Q2 review.
Tasks in this phase
Pull the units past their years in serviceAnna Byrne · DoingConfirm the current standard model for each positionSofia Reyes · To doBudget line for the Q2 planning reviewTomás Varga · To doGroup rooms into batches around the year-end freezeKatya Novak · To doThe gate, signed off by Programme manager
- Scope and budget agreed
- Batches fit the year plan
What the playbook says: 4 steps
- AV and IT delivery engineerPull the units past their years in service from the refresh plan
- Service manager, AVConfirm the current standard model for each position
- Project managerGroup spaces into batches that avoid busy weeks
- Programme managerBudget line and purchase request
Design: what happened
Not reached yet. Planned to end 4 Dec (the playbook allows 1 to 2 weeks).
Tasks in this phase
None recorded.
The gate, signed off by Service manager, AV
- Every swap is to the current standard
- No change to space types or wiring
What the playbook says: 3 steps
- AV and IT delivery engineerSwap sheet per space: position, old model, new model, hostname kept
- AV and IT delivery engineerCheck mounts, cables and power suit the new model
- AV and IT delivery engineerTake the configuration from the new model's configuration page
Procure: what happened
Not reached yet. Planned to end 18 Mar (the playbook allows 3 to 6 weeks).
Tasks in this phase
None recorded.
The gate, signed off by Project manager
- Everything received
- Addresses reserved
What the playbook says: 3 steps
- Project managerOrder units, mounts and one spare per ten
- Network engineerSend MACs to the network team for address reservations before delivery
- On-site technicianRecord serials on arrival against the swap sheet
The Deploy board33 devices in 4 spaces, each through four steps. Tick each device's checklist, or hand it to the agent.0/33Provision0/33Install0/27Configure0/33CommissionOpen Deploy
Deploy: what happened
Not reached yet. Planned to end 10 Apr (the playbook allows Half a day per space, then 1).
Tasks in this phase
None recorded.
The gate, signed off by AV and IT delivery engineer
- Every space in the batch installed
- Every space passes, or its snags are accepted
What the playbook says: 9 steps
- On-site technician · ProvisionRetire the old unit in the asset register the same day
- Integration vendor · ProvisionWhen a vendor does the swap: record serial and MAC for each position, with a label photo
- Project manager · InstallBook the space out
- On-site technician · InstallSwap the unit, keeping position and hostname
- AV and IT delivery engineer · ConfigureConfigure each device in its setup order, then set and verify its settings
- AV and IT delivery engineer · CommissionRun the verification for each space
- On-site technician · CommissionTest call on the room's meeting platform
- AV and IT delivery engineer · CommissionSnag list
- Integration vendor · CommissionWhen a vendor did the swap: fix snags on their work within five working days
Hand over: what happened
Not reached yet. Planned to end 3 May (the playbook allows 1 weeks).
Tasks in this phase
None recorded.
The gate, signed off by Service manager, AV
- Records match what is in the spaces
What the playbook says: 2 steps
- Project managerHandover note to the service desk
- Project managerRedeploy or dispose of the old units
Closed: what happened
Not reached yet. Planned to end 18 Jun (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
Spaces
People and time
TVTomás VargaProgramme manager1 of 8 h · Budget and sequencing
KNKatya NovakProject manager2 of 50 h · Batches and bookings
ABAnna ByrneLead engineer1 of 40 h · Units due and swap sheets
TATom AshbyTechnician0 of 44 h · Swaps; travels from London
SRSofia ReyesService owner (sign-off)0 of 4 h · Standard model
Budget
DKK 84,000approved
- Spent
- DKK 0
- Ordered, not yet paid
- DKK 0
- Still an estimate
- DKK 84,000
- Left if all goes to plan
- DKK 0
To do3
Doing1
Waiting on0
Done0
Pull the units past their years in servicePlanDue 23 Oct
Confirm the current standard model for each positionPlanDue 26 Oct
Budget line for the Q2 planning reviewPlanDue 26 Oct
Group rooms into batches around the year-end freezePlanDue 30 Oct
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.
Agents only propose; a person accepts a proposal as a task before anything changes. What the agents do