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-16Comms room refreshDublin officeSimulated
Dublin office IDF switch refresh
Procure gate due 6 Nov · 1 task waiting on somethingchecked just now
ScheduleSlipped, now on planDesign ended 3 days late. Procure is due 6 Nov.
Cost€20,300 in hand€47,500 spent or ordered of €74,000 approved, €6,200 still estimated.
ScopeAs chartered3 spaces, comms room refresh; no change requests.
Next gateProcure gatedue 6 NovProject manager signs it off. Everything received and pre-staged.
Timeline
14 Sept to 1 Jan, following the Comms room refresh playbook, version 1.3Today
PlannedActualPast the planGate, filled when signed off
Plan: what happened
Ended 25 Septon time
Two IDFs in scope; cutover on a weekend so no rooms are lost in the working week.
Handed onScopeChange window request
Gate signed off by Tomás Varga, 25 Sept
Tasks in this phase
Audit every port in both IDFsMarco Bianchi · Done · fix capturedThe gate, signed off by Service manager, IT infrastructure
- Scope and window agreed
- Change request raised
What the playbook says: 4 steps
- Network engineerFind the switches past vendor support
- Service manager, IT infrastructureChoose the model from the infrastructure standard
- Project managerPick a change window, usually a weekend
- Project managerRaise the change request
Design: what happened
Ended 12 Oct3 days late
Port map drawn for both floors; every AV device keeps its VLAN.
Handed onPort mapNew switch configurationRack elevation for each IDF
Gate signed off by Declan Moore, 12 Oct
Tasks in this phase
List every AV device's port and VLANAnna Byrne · DoingThe gate, signed off by Service manager, IT infrastructure
- Port map and rollback plan approved
- AV devices listed
What the playbook says: 5 steps
- Network engineerPort audit: what is on each port, its VLAN and power draw
- Network engineerPort map from old switch to new
- AV and IT delivery engineerList every AV device affected and how to check it
- Network engineerRack elevation, power and UPS check
- Network engineerRollback plan
Procure: what happened
Open, due 6 Nov
Switches ordered; optics on back order.
Tasks in this phase
Order switches and opticsRuth Kelly · DoneReceive the opticsRuth Kelly · Waiting onThe gate, signed off by Project manager
- Everything received and pre-staged
What the playbook says: 3 steps
- Project managerOrder switches, optics and patch leads
- Network engineerPre-stage the configuration in the Lab
- On-site technicianLabel every port before the cutover
The Deploy board26 devices in 3 spaces, each through four steps. Tick each device's checklist, or hand it to the agent.0/26Provision0/26Install0/22Configure0/26CommissionOpen Deploy
Deploy: what happened
Not reached yet. Planned to end 20 Nov (the playbook allows One weekend, then 1).
Tasks in this phase
Label ports before the cutoverLiam Doyle · To doCutover weekendMarco Bianchi · To doRe-verify every AV room after the cutoverAnna Byrne · To doThe gate, signed off by Network engineer and Service manager, IT infrastructure
- Every port moved and up
- Every device back and monitored
What the playbook says: 7 steps
- Integration vendor · ProvisionWhen a vendor racks the equipment: record serial and MAC for each unit, with a label photo
- Project manager · InstallFreeze changes on the affected floors
- Network engineer · InstallCut over port by port from the map
- Network engineer · InstallRoll back if the checks fail
- Network engineer · ConfigureLoad the pre-staged configuration and verify each port against the map
- AV and IT delivery engineer · CommissionRe-verify every AV room on the list
- Network engineer · CommissionCheck monitoring sees every device
Hand over: what happened
Not reached yet. Planned to end 4 Dec (the playbook allows 1 weeks).
Tasks in this phase
None recorded.
The gate, signed off by Service manager, IT infrastructure
- Records match the racks
What the playbook says: 2 steps
- Network engineerUpdate the as-built rack and port records
- Project managerRetire the old switches
Closed: what happened
Not reached yet. Planned to end 1 Jan (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 manager2 of 6 h · Fits the cutover weekend into the year plan
RKRuth KellyProject manager12 of 40 h · Runs the cutover plan, the change request and facilities access
MBMarco BianchiLead engineer20 of 64 h · Audits ports, builds the new switch configuration, runs the cutover
ABAnna ByrneEngineer2 of 16 h · Lists every AV device's port and signs off the re-verification
LDLiam DoyleTechnician0 of 24 h · Labels ports before the cutover and checks each room after
DMDeclan MooreService owner (sign-off)3 of 6 h · Approves the switch model and the change window
Budget
€74,000approved
- Spent
- €0
- Ordered, not yet paid
- €47,500
- Still an estimate
- €6,200
- Left if all goes to plan
- €20,300
To do3
Doing1
Waiting on1
Done2
Audit every port in both IDFsPlan2 Oct
List every AV device's port and VLANDesignDue 30 Oct
Receive the opticsProcureDue 6 Nov
Order switches and opticsProcure16 Oct
Label ports before the cutoverDeployDue 4 Dec
Cutover weekendDeployDue 12 Dec
Re-verify every AV room after the cutoverDeployDue 15 Dec
Archived tasks 0
Assign to
Risks (might happen), issues (have happened), decisions and dependencies, in one place. Open first: 1 open.
DependencyOptics on back order until mid OctoberThe switches are here; the uplink optics are not. Install cannot start without them.T-1603 Receive the opticsRKRuth Kellyby 6 NovWaiting
DecisionOne IDF per evening, third floor firstKeeps every floor on the network during the day.DMDeclan Mooredecided 1 OctDecided
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