Silwatech
Prepared for TAQATAQA logo
OverviewLive demo
Act I · Introduction & Scope
01Introduction02Solution Overview03High-Level Modules
Act II · The Product
04Live Demo
Act III · Architecture & Engineering
05Solution Architecture06Frontend Architecture07Backend Architecture08Integrations09Security Architecture10Performance
Act IV · Delivery & Roadmap
11Execution Process12AI-Assisted Delivery13Project Schedule14Questions & Answers15Future AI Ideas
Technical Solution Walkthrough

A modern TAQANET for every TAQA employee.

An interactive walkthrough of the SharePoint Online intranet Silwatech has designed for TAQA under RFQ HQ-200155. It moves through the solution, the architecture, security, and the delivery plan in the order your engineering and communications teams review them, with the working prototype one click away.

Start the walkthroughLaunch live demo
RFQ HQ-200155SharePoint Online · Microsoft 365UAE data residency20-week delivery plan
Microsoft 365 · UAE regions
TAQANET · Digital WorkplacePreview · sample data
Search TAQANET: try “payslip”, a policy, or a colleague’s name⌘K
0
News stories this week
4 scheduled ahead
0%
HQ reach, CEO message
All departments
0
Ideas in Have Your Say
12 awaiting replies
New hybrid work policy takes effect 1 June
Human Capital · Announcement · 2 min read
Targeted · HQ
Publish confirmed · CEO message → All HQ audiencesSynced to Microsoft 365
Entra ID · Single sign-on
01 · Introduction

A group operating at national scale, and the intranet behind it.

TAQANET is the digital front door for the people who run one of the region’s most important energy businesses. This engagement replaces its SharePoint 2019 foundation with SharePoint Online, and this walkthrough shows exactly how.

TAQA
Abu Dhabi National Energy Company PJSCListed on the Abu Dhabi Securities Exchange · One of the largest listed integrated utility companies in EMEA

TAQA generates power, desalinates water, and moves both across transmission and distribution networks that serve millions of people, with operations spanning the UAE and markets across the Middle East, Europe, Africa, and Asia.

0+
GW gross power generation capacity
0
MIGD desalination capacity portfolio
0k+
km of power network
0
countries of operation
AED 0B
group revenue, FY 2025
0+
HQ employees on TAQANET at go-live

The brief, in plain terms

  • Move TAQANET from SharePoint 2019 on-premises to SharePoint Online, fully cloud, no on-premises dependencies.
  • Build with out-of-the-box SharePoint capabilities first, TAQA’s stated preference, so the platform stays upgrade-safe.
  • Serve ~400 HQ employees at go-live on an architecture that extends to the wider TAQA Group without redesign.
  • Migrate HQ content with validation and legacy URL redirects, so bookmarks and muscle memory survive the move.
  • Meet WCAG 2.1 AA accessibility and keep all data inside Microsoft’s UAE cloud regions.
What we’re leaving behindWeak searchDated interfacePoor mobile accessInformation silosNo personalizationNavigation maze
Delivered by Silwatech

Engineering partner for government and enterprise across the Gulf.

Silwatech is a technology consulting and digital engineering company with delivery across the UAE, Saudi Arabia, the wider GCC, Europe, and Africa. Its Microsoft practice covers Microsoft 365, SharePoint, Power Platform, Dynamics 365, and Azure, alongside enterprise software development and AI engineering.

ISO 27001 · Information SecurityISO 9001 · Quality Management
0+
Projects delivered
0+
Technology professionals
0%
Client retention
0
Global delivery locations
Trusted by government and enterprise across the region
TAQADubai ChambersRTADubai MunicipalityALDARAbu Dhabi CustomsGovernment of SharjahMinistry of TourismSharjah Airportwasl propertiesPUMA EnergyStarbucksORIXSOMPO

Portfolio reflects direct engagements and collaboration within partner-led programs.

02 · Solution Overview

One intranet, four surfaces, zero new platforms to buy.

TAQANET moves to SharePoint Online inside TAQA’s existing Microsoft 365 tenant. Every experience below is delivered through services TAQA already licenses, configured rather than custom-built, so the platform keeps improving as Microsoft ships updates.

TAQANET Home

The corporate front page: CEO messages, news, announcements, alerts, events, quick links, and key documents, curated by Group Communications.

Department portals

Hub-connected sites for functions, business units, projects, and communities. Each inherits navigation, branding, search, and permissions from the hub.

My TAQANET

A personalized layer that targets content by department, role, and location, and follows each employee across the intranet.

Search & knowledge

Microsoft Search across pages, news, people, and documents, tuned with verticals, promoted results, and metadata refiners.

Also everywhere employees already are:Microsoft Teams · Viva ConnectionsSharePoint mobile appFully responsive web, phone to desktop
TAQANET Home · concept design
TAQANET homepage concept showing CEO message, news, events, quick links, and Microsoft 365 applications
Homepage concept from the technical proposal. The final design is produced with TAQA’s brand and communication standards during the design phase, and validated against WCAG 2.1 AA.
03 · High-Level Modules

Ten functional domains, each mapped to the RFQ.

Every module below traces to a requirement in HQ-200155. Select a module to see what it does and which Microsoft 365 capability delivers it.

Home & Communications

The configurable corporate homepage that greets all of HQ: leadership voice at the top, organizational news underneath, and the tools people came for one click away.

Capabilities

  • CEO messages, corporate news, and announcements with featured placement
  • Alerts and urgent banners for time-critical updates
  • Events calendar, quick links, and key documents
  • Announcements targeted by department, role, or location attributes

How it’s built

SharePoint communication site with out-of-the-box web parts: News, Hero, Events, Quick Links, and Highlighted Content, arranged with audience targeting.

Communication siteNews web partAudience targetingEvents web part

Publishing & Governance

Structured authoring for a small, accountable publishing group: content moves draft to review to approval to publish, with scheduling and archiving handled by the platform.

Capabilities

  • Draft, review, approve, schedule, publish workflow for every page and news post
  • Centralized publishing governed by Group Communications, up to five content authors
  • Scheduled publishing, featured content rotation, and archiving rules
  • Authoring simple enough for non-technical editors, no HTML required

How it’s built

SharePoint page approvals driven by Power Automate flows, with content scheduling and version history native to SharePoint Online.

Power AutomatePage approvalsSchedulingVersion history

Search & Discovery

The fix for TAQANET’s weakest link today. One search box that understands pages, people, news, and documents, and puts the official answer first.

Capabilities

  • Microsoft Search across sites, pages, news, people, and files
  • Search verticals for the content types employees actually look for
  • Promoted results and bookmarks for high-intent queries such as payslips or VPN
  • Metadata-driven refiners powered by the enterprise taxonomy

How it’s built

Microsoft Search configuration: verticals, result types, bookmarks, and Q&A entries, refined continuously using search analytics.

Microsoft SearchVerticalsPromoted resultsManaged metadata

My TAQANET

The personal layer. Two employees in different departments open the same intranet and see different news, different quick links, and different documents, automatically.

Capabilities

  • Content targeted by department, role, location, and profile attributes
  • Personal shortcuts: frequently accessed content, followed sites, recent documents
  • Department-aware quick links and applications

How it’s built

SharePoint audience targeting bound to Entra ID attributes and Microsoft 365 groups, with Microsoft Graph powering recent and followed content.

Audience targetingEntra ID attributesMicrosoft Graph

Departments & Sites

A hub-and-spoke estate that gives every function its own portal while keeping navigation, branding, and governance consistent across the intranet.

Capabilities

  • Department, business unit, project, and community sites under one corporate hub
  • Mega menu, breadcrumbs, and categorized navigation across every level
  • Departmental autonomy inside enterprise-wide standards

How it’s built

SharePoint hub sites with inherited navigation, theme, search scope, and permission model. Full structure in the Backend Architecture section.

Hub sitesMega menuInherited governance

Social & Engagement

The features that turn an intranet from a noticeboard into a workplace: conversation, reaction, and feedback loops between leadership and employees.

Capabilities

  • Comments and likes on news and pages
  • Discussions, interest groups, and communities
  • Polls and surveys for structured feedback

How it’s built

Native SharePoint page reactions and comments, Viva Engage communities for discussion, and Microsoft Forms for polls and surveys.

Page reactionsViva EngageMicrosoft Forms

People Directory

Find a colleague by name, team, or role, then see where they sit in the organization and how to reach them, without asking around.

Capabilities

  • People search with profile cards: role, department, contact, presence
  • Organizational context: manager, team, and peers
  • One-click handoff to Teams chat, call, or email

How it’s built

Microsoft Search people vertical over Entra ID profiles, enriched through Microsoft Graph. Profile quality is validated during discovery.

People verticalEntra ID profilesMicrosoft Graph

Documents & Policies

A governed home for the documents people rely on: policies, procedures, forms, and templates, each with an owner, a lifecycle, and consistent metadata.

Capabilities

  • Standardized libraries with content types and managed metadata
  • Versioning, co-authoring, and controlled key document surfacing
  • Lifecycle management for policies, procedures, and corporate documents

How it’s built

SharePoint document libraries with enterprise content types, term store taxonomy, and retention behavior aligned to TAQA’s classification rules.

Document librariesContent typesTerm storeRetention

Analytics & Adoption

Evidence, not anecdotes. Dashboards that show what employees read, search for, and ignore, so Communications can steer content with data.

Capabilities

  • Executive dashboards for adoption and engagement
  • Page views, content consumption, active and returning users
  • Engagement metrics: likes, comments, polls, survey participation
  • Search analytics including failed queries, feeding continuous improvement

How it’s built

SharePoint and Microsoft 365 usage analytics, search reports, and curated dashboards for the executive and communications view.

Site analyticsSearch reportsUsage reports

Content Migration

The current HQ intranet arrives in the new TAQANET cleaned, validated, and findable, and old bookmarks keep working where feasible.

Capabilities

  • Content inventory and audit with TAQA before anything moves
  • HQ pages, news, and libraries migrated with metadata validation
  • Migration rehearsal before the production run
  • Legacy URL redirect management where feasible

How it’s built

SharePoint Migration Tool and Microsoft Migration Manager, with validation checkpoints and a migration report at completion.

SPMTMigration ManagerValidation checkpoints
04 · Live Demo

Stop reading. Start clicking.

Silwatech built a working interactive prototype of TAQANET alongside this proposal. It runs in any modern browser, needs nothing installed, and demonstrates every scope commitment with sample data.

The product, one click away

TAQANET Interactive Prototype

taqanet.share.silwatech.com
Access code shared separately with the TAQA evaluation team.Four personas, thirteen working micro-apps, seventeen screens, English and Arabic.Sample data only. No TAQA system is connected, nothing to provision.
Launch the prototype

Persona switching

Four fictional employees. Switch persona and watch Home retarget news, links, and apps live.

English · العربية

Full bilingual publishing preview with right-to-left layout, one click from the top bar.

Search that answers

Search “payslip” or “VPN” and get a promoted result with a working action, not ten stale links.

Publishing Studio

An interactive kanban of the draft, review, approve, schedule, publish lifecycle.

13 working micro-apps

Payslips, leave, expenses, helpdesk, meeting rooms, learning, travel, and more behind every quick link.

Ask TAQANET

A scripted assistant preview showing where Copilot-era answers fit into the intranet.

Adoption analytics

The engagement dashboard Communications would use, with a downloadable report.

URL continuity

A working demo of legacy link redirects, so old bookmarks land on the right new page.

Suggested five-minute path

Switch persona from the avatar menu and watch the homepage retarget.
Search “payslip” and open the promoted result’s micro-app.
Open Publishing Studio and walk a draft through approval.
Tap العربية to flip the experience to Arabic, right-to-left.
Finish in Adoption Analytics, including search insights.
The prototype demonstrates the target user experience. The delivered TAQANET is built on SharePoint Online with the architecture described in the next sections, not on the prototype’s codebase. A guided mapping from each prototype screen to the proposal scope is available inside the app under Prototype Guide.
05 · High-Level Solution Architecture

Cloud-native on Microsoft 365, end to end.

One diagram, the whole system. Employees authenticate through Entra ID and land on SharePoint Online in Microsoft’s UAE regions; every capability around it is a Microsoft 365 service. Select any component for its role in TAQANET.

People & Devices
Access & Identity
Microsoft 365 Platform · UAE Data Residency
Integration & Extension
Security & Governance · every layer
Management & Monitoring
Intranet coreMicrosoft 365 serviceUAE data residency boundaryAnimated dots show the sign-in and content flow
Cloud-native SaaS, no serversSecure by design · Zero Trust99.9% Microsoft SLACopilot & Viva readyScales to the TAQA Group
The flow

How a page reaches an employee

Every request is authenticated by Entra ID under Conditional Access and MFA, then served by SharePoint Online from Microsoft’s UAE data centre regions. No component below sits outside Microsoft 365.

  • Configure-first: native services before custom code
  • No on-premises dependencies anywhere in the design
  • Extensible for Phase 2 enterprise integrations

Why it matters: the platform inherits Microsoft’s availability, security, and roadmap, and TAQA’s team operates configuration, not infrastructure.

06 · Frontend Architecture

The experience layer, engineered to stay standard.

TAQANET’s interface is built from SharePoint’s modern experience: the same components Microsoft maintains, themed to TAQA’s brand. Custom code is a last resort with a governance gate, not a starting point.

Step 1 · Default
Most of TAQANET

Configure

Out-of-the-box web parts and settings: News, Hero, Events, Quick Links, Highlighted Content, People, and site navigation.

Step 2

Compose

Page templates, section layouts, audience targeting, and the TAQA theme applied through supported theming and site designs.

Step 3 · Exception

Extend with SPFx

SharePoint Framework web parts or extensions only where a requirement has no native answer, code-reviewed and tenant-safe.

Never

Fork the platform

No unsupported customization, no modified system files, nothing that breaks when Microsoft ships an update.

Brand & theming

TAQA’s colors, typography, and header applied via supported theming, aligned with brand and communication standards during design.

Responsive & mobile

Every page responsive from phone to desktop, plus native reach through the SharePoint app and Viva Connections in Teams.

Accessibility

WCAG 2.1 AA as an acceptance criterion: contrast, keyboard paths, focus order, and alt text validated during testing, not assumed.

Bilingual readiness

SharePoint multilingual publishing keeps English and Arabic page variants linked, with right-to-left rendering handled by the platform.

Why the restraint matters: TAQA asked for out-of-the-box first. Every step down this ladder adds maintenance cost and upgrade risk, so each SPFx candidate needs a requirement no native feature can meet, agreed at design stage gate before any code is written.
07 · Backend Architecture

SharePoint Online does the heavy lifting.

There is no application server to build and no database to administer. The backend is SharePoint Online’s content services, organized through a hub-and-spoke estate and automated with Power Automate.

TAQANET Corporate HubNavigation · branding · search scope · permissions · governance, inherited by every site
About TAQA
  • Leadership
  • Vision & values
  • Corporate pages
Business Units
  • Per-unit team sites
  • Unit news
Functions
  • HR · Finance · IT
  • Policies & services
Projects
  • Project team sites
  • Working documents
Communities
  • Interest groups
  • Viva Engage spaces
Departments keep autonomy inside their sites while the hub keeps the estate consistent. New business units or regions join by associating a new site to the hub, which is how TAQANET later scales across the TAQA Group without redesign.

Content architecture

Enterprise content types, managed metadata in the term store, naming conventions, and standardized libraries. The taxonomy that makes search and navigation work.

  • Hierarchy aligned to TAQA’s organization
  • Breadcrumbs and contextual navigation
  • Document lifecycle management

Process automation

Power Automate carries the operational load: approval routing, scheduled publishing, notifications, and governance checkpoints, all configuration rather than code.

  • Draft to publish approval flows
  • Publishing schedules and reminders
  • Notification and escalation rules

Data & services

Microsoft Graph supplies people, organization, and activity signals for personalization. Content lives in SharePoint repositories with versioning and audit built in.

  • Graph-driven profiles and targeting
  • Version history on every artifact
  • Activity captured in unified audit logs
08 · Third-Party Integrations

Deep in Microsoft 365 now, ready for the enterprise next.

Phase 1 keeps integration inside the Microsoft ecosystem, exactly as the RFQ scopes it. The same integration layer then accepts TAQA’s enterprise systems in Phase 2 without rework.

In scope now

Phase 1
Microsoft Teams

TAQANET inside Teams through Viva Connections, news pushed to channels, and person-to-chat handoffs from the people directory.

Microsoft Entra ID

Single sign-on, profile attributes for personalization, and the group membership that drives audience targeting.

Exchange Online & Outlook

Events surface on the intranet calendar; invitations and mail handoffs open where people already work.

OneDrive & Microsoft 365 apps

Documents open in Word, Excel, and PowerPoint with co-authoring; personal files stay in OneDrive.

Migration tooling

SharePoint Migration Tool and Microsoft Migration Manager carry HQ content from SharePoint 2019 with validation checkpoints.

Architecture-ready

Phase 2 · Future scope
Oracle Fusion & HR systems

Employee services and HR data surfaced into the intranet through Graph connectors and supported APIs.

ServiceNow

Tickets raised and tracked from TAQANET, with status visible where employees look first.

Audit Tracker & BTMS

TAQA’s named business systems join the same integration layer as demand matures.

Phase 2 integrations are explicitly out of the current scope. The commitment made now is architectural: they connect through the patterns on the left without reengineering the intranet.
Integration patterns
Microsoft Graph APIREST APIsSupported connectorsSPFx surfacesPower Automate connectors
On third-party intranet accelerators: we propose none. The RFQ requires any accelerator to be fully SharePoint Online compatible, UAE-resident, and free of architectural or security risk. Building on native Microsoft capability satisfies all three by construction, and removes a licence and a vendor from TAQA’s risk register.
09 · Security Architecture

Five layers between the internet and a TAQANET page.

Defence in depth on a Zero Trust footing: every request is verified, every permission is least-privilege, and every action is auditable. Select a layer to see its controls.

Layer 1 · Identity

Nobody reaches TAQANET anonymously

Microsoft Entra ID is the single front door. Every session is authenticated with corporate credentials, challenged with multi-factor authentication, and evaluated against Conditional Access policies before a single page loads.

  • Single sign-on through Microsoft Entra ID
  • MFA enforced by policy
  • Conditional Access evaluates user, device, and location
  • No separate intranet credentials to manage or phish

TAQA requirement: SSO through Microsoft Entra ID with Conditional Access and MFA, met natively.

Zero Trust principlesAll data in Microsoft’s UAE regionsNo Secret or Confidential data storedMeets or exceeds Microsoft SaaS security SLAs
10 · Performance Management

Fast because it stays light.

Performance on SharePoint Online is won by discipline, not tuning servers: standard web parts, optimized media, and metadata-driven queries on Microsoft’s globally distributed infrastructure. Performance testing runs inside the testing phase before UAT sign-off.

0.0%
Microsoft 365 availability SLA, financially backed
OOB
Standard web parts keep pages light and cacheable
0
Servers for TAQA to size, patch, or scale
400→Group
Same architecture from HQ pilot to group-wide rollout
Microsoft-managed CDN and edge deliveryImage renditions and lazy loadingMetadata queries instead of heavy rollupsSearch tuned continuously from analyticsPerformance validated in Phase 4 testing
11 · Project Execution Process

Six phases, each closed by a stage gate.

A milestone-driven methodology combining Microsoft Success by Design, agile delivery, and PMI-style governance. Nothing moves to the next phase without a formal review and sign-off. Select a phase.

Initiation & Discovery Weeks 1–3

What happens

  • Kick-off, governance and communication plan, stakeholder map
  • Current state assessment and discovery workshops with Communications and IT
  • Content inventory and migration assessment of the existing HQ intranet
  • Risk identification and detailed project planning

Gate deliverables

Project Management PlanRequirements Traceability MatrixRequirements documentCurrent State AssessmentSolution BlueprintProject Schedule

Solution Design Weeks 4–6

What happens

  • Information architecture, hub strategy, and site hierarchy design
  • Homepage UX, navigation, and mega menu design with TAQA branding
  • Metadata and taxonomy model, security model, search architecture
  • Integration design and the content governance framework

Gate deliverables

Solution Architecture DocumentInformation ArchitectureUX wireframesNavigation blueprintSecurity designMetadata modelGovernance framework

Configuration & Development Weeks 7–14

What happens

  • Hub, communication, and department sites created and configured
  • Homepage, mega menu, quick links, and branding implemented
  • Microsoft Search, metadata, and Power Automate workflows configured
  • SPFx extensions and Microsoft Graph integrations, only where approved
  • Progress demonstrated in sprint reviews throughout

Gate deliverables

Configured SharePoint environmentCorporate homepageDepartment portalsWorkflow configurationEnterprise searchSecurity configuration

Migration, Testing & Validation Weeks 13–17

What happens

  • Migration rehearsal first, then the validated production content run
  • Functional, integration, and security testing
  • Accessibility validation against WCAG 2.1 AA and performance testing
  • UAT with Communications and IT, defects resolved to closure

Gate deliverables

Test strategy & casesTest resultsMigration reportUAT sign-offProduction readiness report

Production Deployment Week 18

What happens

  • Production deployment and validation, including DNS and URL checks
  • User verification with the launch group
  • Go-live support alongside TAQA’s launch communications

Gate deliverables

Production deployment reportGo-live checklistProduction sign-off

Hypercare & Transition Weeks 19–20

What happens

  • Hypercare support with incident management on the live platform
  • Administrator and content author training, end-user awareness sessions
  • Knowledge transfer to TAQA’s IT team and formal project closure

Gate deliverables

Training materialsAdministration guideUser guideClosure report

Governance cadence

  • Daily stand-up, project team
  • Weekly status, TAQA PM and Silwatech PM
  • Bi-weekly risk and issue review
  • Monthly steering committee with sponsors
  • Design reviews with architects as required

Delivery discipline

  • Requirements Traceability Matrix from RFQ to acceptance
  • Stage gate reviews closing every phase
  • Sprint demos for continuous stakeholder validation
  • RAID register reviewed in governance meetings
  • Formal change requests, impact analysis within 5 working days

Toolchain

  • Azure DevOps and Azure Boards for agile delivery
  • Microsoft Project for the plan, Teams for collaboration
  • Figma and Visio for wireframes and architecture
  • Azure Test Plans for test management
  • SPMT and Migration Manager for content migration
12 · AI-Assisted Delivery

We use AI to move faster. People stay in charge.

Silwatech runs an AI-accelerated delivery pipeline: named consultants own every decision and deliverable, and AI compresses the mechanical work between decisions. TAQA gets the same governed outputs, sooner.

Requirements & traceability

RTM drafts generated from the RFQ and checked for coverage, so no requirement is silently dropped between discovery and testing.

Design acceleration

More wireframe and information architecture options explored per design cycle, so TAQA chooses between real alternatives, not a single take.

Configuration & code

Provisioning scripts, SPFx scaffolding, and Power Automate patterns drafted by AI, then reviewed line-by-line before anything reaches a TAQA tenant.

Quality engineering

Test cases generated from the RTM, accessibility checklists derived from WCAG 2.1 AA, and regression suites kept current as scope evolves.

Migration assistance

Content inventory classification and metadata suggestions prepared by AI for human review, cutting the audit effort on legacy HQ content.

Documentation & training

Admin guides, user guides, and training material drafted alongside the build instead of after it, in English with Arabic support.

The guardrails

Human-led, always

Every artifact is reviewed, corrected, and owned by a named consultant. AI drafts; people decide.

Data protection

No TAQA confidential content enters public AI services. Work stays inside controlled environments.

Same quality gates

AI-assisted code and configuration pass the identical review, testing, and stage gate process as any other work.

Accountability unchanged

Deliverables are signed off by people at stage gates. How a draft was produced never dilutes responsibility for it.

Proof, not promise: the interactive TAQANET prototype accompanying this proposal was produced with this exact pipeline: AI-accelerated build, human architecture, review, and three full QA passes. It is the difference between telling you our approach works and handing you the result.

13 · Project Schedule

Twenty weeks from kick-off to closure.

Development completes by week 14; migration, UAT, go-live, and hypercare land in the six weeks after, matched to TAQA’s four-to-five-month expectation. Hover any bar or milestone for its deliverable.

Phase / week
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Initiation & DiscoveryPhase 1
W1–3Discovery · Project plan, discovery report, RTM
Week 1 · Kick-off, project plan approvedWeek 3 · Discovery report & RTM delivered
Solution DesignPhase 2
W4–6Design · Architecture, IA, UX wireframes
Week 6 · Architecture & UX sign-off
Configuration & DevelopmentPhase 3
W7–14Build · Sites, homepage, search, workflows, branding
Week 14 · SharePoint solution configured
Content MigrationPhase 4
W13–15Migration · Rehearsal, production run, validation
Week 15 · Content migration report
Testing & UATPhase 4
W15–17Validation · Functional, security, accessibility, UAT
Week 17 · UAT sign-off
Production Go-LivePhase 5
W18Go-live · Production deployment & sign-off
Week 18 · Production deployment
Hypercare & TransitionPhase 6
W19–20Hypercare · Support, training, knowledge transfer
Week 20 · Project closure
DiscoveryDesignBuildMigrate & validateGo-liveHypercareMilestone
Timelines are tentative and are refined after the discovery phase. UAT, go-live, and hypercare dates depend on TAQA’s readiness: environment access, content approvals, and UAT participant availability. Deliverable reviews are assumed within five business days.
RoleCountResponsible for
Project Manager1Plan, coordinate, and manage delivery to scope, schedule, budget, and quality.
Business Analyst1Gather and document requirements; translate them into functional specifications and the RTM.
Solution & Technical Architect1Own the solution architecture; keep implementation aligned with business, security, and scalability requirements.
Microsoft 365 SharePoint Consultants3Configure, customize, and implement the SharePoint Online and Microsoft 365 solution.
UI/UX Consultant1Design the homepage, navigation, and page experiences to TAQA brand and WCAG 2.1 AA.
QA Consultants2Plan and execute functional, integration, security, accessibility, and performance testing.
Training Consultant1Build and deliver admin, author, and end-user training with documentation for adoption.
Delivery runs primarily from Silwatech’s Delivery Centre with remote collaboration over Microsoft Teams. Key personnel are not replaced during the project without TAQA’s prior written approval. Detailed profiles are in the Project Profiles annexure.
ActivitySilwatech PMTAQA TechTAQA ITTAQA Business
Project governanceAIRC
Discovery and assessmentRRCI
Environment readinessARCI
Solution configurationARII
Custom app remediationARCC
UAT testingARRR
Production migrationRRCI
UAT sign-offIIRA
Go-live sign-offIIRA
Knowledge transferARRI
RResponsibleAAccountableCConsultedIInformed
14 · Questions & Answers

The questions your engineers will ask. Answered.

Ten questions we expect from the TAQA evaluation, with the answers we stand behind. Anything not covered here becomes an agenda item for the clarification workshop.

Three reasons. It is TAQA’s stated preference in the RFQ. It removes an entire class of risk: native capability is maintained, secured, and improved by Microsoft, so nothing breaks on platform updates. And it avoids a third-party accelerator licence with its own data residency and security due diligence. Custom SPFx remains available for genuine gaps, behind a design stage gate.
TAQANET content lives in SharePoint Online within Microsoft’s UAE data centre regions, under the tenant’s data residency configuration. The solution introduces no component that stores TAQA data outside Microsoft 365: no external database, no third-party SaaS, no accelerator. Residency is verified as part of the security design deliverable in Phase 2.
HQ intranet pages, news, and document libraries, after a joint inventory and audit in discovery decides what moves, what is archived, and what is retired. TAQA reviews and approves content before migration. We run a full rehearsal before the production migration, validate metadata afterward, and manage legacy URL redirects where feasible so bookmarks and links in circulation keep resolving.
SharePoint Online is the same infrastructure Microsoft runs for organizations far larger than TAQA, with a financially backed 99.9% availability SLA. The design choices that matter at scale are already in: hub architecture instead of one monolithic site, metadata-driven queries, image renditions, and standard web parts. Group rollout means associating new sites to hubs, not re-platforming.
Only where a requirement has no native answer after the design phase confirms it, and each candidate is agreed with TAQA at the stage gate. All SPFx follows tenant-safe practices: supported APIs only, code review, no interference with platform updates. The starting position is zero custom components; every addition must earn its maintenance cost.
Audience targeting bound to Entra ID: department, role, location, and group membership drive which news, links, and applications appear, with Microsoft Graph adding recent and followed content. Nothing is manually curated per person, so personalization scales with zero authoring overhead. The prototype’s persona switcher demonstrates the exact behavior.
Through SharePoint’s multilingual publishing: English and Arabic versions of a page stay linked, translators are notified when the source changes, and right-to-left rendering is native platform behavior. The bilingual toggle in the prototype previews the experience. The rollout language strategy is confirmed with Group Communications during design.
Three paths, all standard: fully responsive pages in any mobile browser, the SharePoint mobile app with notifications, and TAQANET surfaced inside Microsoft Teams through Viva Connections. No native app is built or maintained, which the RFQ scopes out, and nothing extra is deployed to devices.
Yes, by design rather than by accident. Copilot quality depends on exactly what this project builds: clean metadata, sensible permissions, governed content, and current pages. Because everything stays native Microsoft 365, enabling Copilot or wider Viva later is a licensing and adoption decision, not an integration project. The Future AI Ideas section sketches the sequence.
Four things, all ordinary: a named TAQA project manager and IT lead; tenant and environment access at kick-off; content reviewed and approved ahead of migration; and UAT participants from Communications and IT in weeks 15 to 17, with decisions and deliverable reviews inside five business days. Every dependency is tracked openly in the RAID register from week one.
15 · Future AI Ideas

Where TAQANET goes after go-live.

Ideas for TAQA’s roadmap conversation, sequenced by readiness. None of this is in the current scope or price; all of it becomes possible because the foundation is native Microsoft 365 with clean metadata and governed permissions.

Near termFirst 6 months

Switch on what’s already there

Microsoft Copilot activation

The intranet’s clean metadata and least-privilege permissions are exactly what Copilot needs to answer safely. Activation becomes a licensing decision.

Ask TAQANET pilot

A grounded assistant answering from intranet content only, with citations. Previewed today inside the prototype.

AI-assisted authoring

Drafting, summarising, and English–Arabic translation support inside the publishing flow for the Communications team.

Mid term6 to 18 months

Let the intranet tune itself

Auto-tagging & metadata enrichment

Classification suggestions applied against the term store as content is published, keeping search quality high without author effort.

Search intelligence loop

Failed and trending queries mined monthly to create promoted results and close content gaps before employees complain.

Personalized digests

A weekly “your TAQANET” summary in Teams or email, assembled per person from targeting data and reading behavior.

Long term18 months +

From intranet to workplace agent

Employee service agents

Once Phase 2 connects HR, Oracle Fusion, and ServiceNow, requests like leave or tickets complete conversationally from TAQANET.

Group-wide knowledge mining

As entities join the hub estate, cross-company search and insight over policies, projects, and expertise across the TAQA Group.

Leadership insight, in plain language

Natural-language questions over adoption and engagement analytics for the executive dashboard audience.

Each idea is subject to TAQA’s licensing, security review, and data governance, and would be scoped through the standard change process. We flag them now so the platform decisions made in this project keep every one of them open.
Closing

Let’s build TAQANET.

A modern digital workplace on the platform TAQA already owns, delivered by a team that has done this before, with the product already visible in a working prototype.

SharePoint Online, out-of-the-box firstUAE data residency, Zero Trust security400 HQ users, group-scale architecture20 weeks, stage-gated, RTM-tracedWorking prototype available today
Next step 01Walkthrough & demo session

A guided session of this walkthrough and the live prototype with TAQA’s evaluation team.

Next step 02Technical clarification workshop

Deep-dive with TAQA IT and security on architecture, residency, and governance questions.

Next step 03Discovery kick-off

On award: governance setup, workshop calendar, and the week 1 project plan.

Launch the prototypeBack to the start
Silwatech
Technical Proposal · TAQANET Intranet Modernization (HQ-200155) · Version 1.0 · July 2026
© 2026 Silwatech · Confidential, prepared for Abu Dhabi National Energy Company PJSC (TAQA). www.silwatech.com
ISO 27001ISO 9001
01 / 17 Welcome