Attachment 6 - Attachment A Optional Tasks SOW_v2.pdf

Attachment A

Optional Tasks - Scope of Work:

Campus and Building GIS for Space Visualization, Management, and Wayfinding

(ArcGIS Indoors)

This Attachment A establishes the optional task-specific Statement of Work (SOW) for ArcGIS Indoors at the VA Long Beach Healthcare System (VALBHS). Every task in this Attachment is separately exercisable only during Option Years 1 through 4 and only by written action of the Contracting Officer. This Attachment shall be read with the main SOW and the solicitation’s pricing and ordering provisions.

Building 126 LiDAR scanning and core ArcGIS Indoors implementation are Base Year work. LiDAR scanning and core implementation for every other building identified in the main SOW are Option Year 1 work. Those mandatory Base Year and Option Year 1 requirements are not optional tasks under this Attachment and shall not be repriced here. An Attachment A task may build on an accepted baseline, but it does not duplicate or replace the core survey, floor-plan conversion, Indoors information model, routable network, wayfinding, kiosk software configuration, testing, training, or turnover required by the main SOW unless a written order expressly identifies a discrete enhancement outside that baseline.

1. SUMMARY TABLE

Group Task No. Task Title Short Description

Group 1

1.1 ArcGIS Indoors Mobile (Non-IPS) and Workspace Reservations / Shared Space Management

Configure optional non-IPS mobile and reservation enhancements for the buildings, workspace areas, user groups, and reservation method identified in each order; excludes core Base Year and Option Year 1 map and network buildout.

Core Indoor Experience Augmentation Tasks

1.2 ArcGIS IPS Implementation for Indoors Mobile and Other Approved IPS-Aware Apps

Implement a Government-selected, currently supported ArcGIS IPS workflow for specified buildings and levels, subject to IPS licensing, radio infrastructure, device compatibility, cybersecurity, and accuracy approval.

1.3

ArcGIS Indoors Space Planner: Assignments, Planning Scenarios, and Portfolio Decision Support

Configure Space Planner for assignments, workspace areas, moves, allocation scenarios, and portfolio decisions. Assignment and reservation data are not measured utilization unless an approved measured-use source is separately integrated.

Group 2

2.1 Enterprise Data Governance Expansion and Stewardship Automation

Extend the accepted core governance baseline for ordered buildings, data domains, source systems, stewardship roles, review cycles, and automation without duplicating main-SOW implementation requirements.

Data Foundation and System Maintenance Tasks

2.2

Automated CAD/BIM-to- Indoors Update Workflow

Develop an optional, repeatable post-acceptance workflow for recurring CAD/BIM updates;

excludes the initial building conversion and core implementation required by the main SOW.

2.3 Utility, MEP, Furniture, and Asset Mapping in ArcGIS Indoors

Expand indoor content to include approved utility, MEP, furniture, and asset layers needed for operations, planning, and maintenance use cases.

Group 3

3.1 ArcGIS Indoors Integration

with Facility Management Systems

Integrate Indoors with approved facility-management source systems so location, space, asset, and work-order data can be synchronized.

Facilities Operations and Maintenance Capabilities Tasks

3.2 Configure Launch Actions in

Indoors Viewer to Include Work Order Integration with Field Maps & Survey123

Add role-based launch actions from Indoors Viewer so users can open the correct Field Maps or Survey123 workflow from mapped locations and assets.

3.3 Consulting Support of Field Workflows in ArcGIS Field Maps

Design and refine field-ready workflows for inspections, inventories, rounds, and mobile data collection tied to indoor locations and assets.

3.4

Real-Time Indoor Data Integration & Monitoring

Integrate specifically identified, Government-approved real-time feeds through a VA-approved Enterprise capability, with stated interface, rate, retention, security, monitoring, and acceptance requirements.

Group 4

4.1 ArcGIS Dashboards – FCA, Lifecycle, Utilization, and SCIP Planning

Develop executive dashboards that combine indoor data with capital-planning metrics for facility condition, lifecycle, utilization, and SCIP decision support.

Dashboards and Decision Support Tasks

4.2 ArcGIS Dashboards – Patient Flow, Capacity, and Room Utilization

Create dashboards using specifically approved sources and definitions.

Assigned, reserved, checked-in, observed, and measured use shall be labeled separately and shall not be treated as equivalent.

4.3 ArcGIS Dashboards – Safety, Security, Infection Prevention, Evacuation, and Life Safety

Develop dashboards that support situational awareness for emergency planning, safety infrastructure, response routing, and life-safety readiness.

4.4

ArcGIS Experience Builder

Develop a role-based web experience that brings together indoor maps, dashboards, forms, documents, and links into a single user interface.

Group 5

5.1

ArcGIS GeoBIM

Link indoor GIS content to BIM and project information so the medical center can manage facilities and capital projects with shared spatial context.

Planning, BIM, and Reality Mapping Tasks

5.2 ArcGIS Business Analyst –

Catchment, Drive-Time, Expansion, CBOC, and Telehealth Territory Analysis

Perform market and access analyses to support outpatient access, expansion planning, and territory-based decision making for VA Long Beach.

5.3

Reality Capture and Processing—Exact Product Specified in Each Order

Produce expressly ordered reality-capture products using the exact Government-approved Esri product, capture method, processing location, licensing, output formats, and accuracy criteria stated in the order.

The summary table is an index only. Scope, quantities, dependencies, pricing basis, Government-furnished items, and acceptance requirements are controlled by the written order and the detailed task provisions below.

2. GENERAL REQUIREMENTS APPLICABLE TO ALL OPTIONAL TASKS

• All optional-task work shall be coordinated through the Contracting Officer (CO) and Contracting

Officer’s Representative (COR) and may begin only after a written contract modification or other written ordering instrument issued by the CO states the task number, scope, quantity, Option Year, price, schedule, Government-furnished items, and acceptance requirements. Technical direction from the COR does not authorize additional work or cost.

• The Contractor shall perform optional-task work only in the Government-furnished National VA ArcGIS Enterprise environment hosted on the VA network, using Government-furnished ArcGIS licensing and VA-approved accounts and access. The Contractor shall not host the production solution, procure substitute ArcGIS licensing, or include Government-furnished hosting or ArcGIS entitlement costs in optional-task pricing. Portal, server, data store, network, identity, backup, disaster recovery, antivirus, platform patching, and infrastructure-security administration remain Government or National VA environment-owner responsibilities; the Contractor is responsible only for ordered solution configuration, content, testing, documentation, and support within its authorized access.

• All optional-task applications, electronic content, deliverables, user interfaces, dashboards, forms, maps, reports, training, and documentation shall conform to applicable Section 508 requirements and VA accessibility standards. The Contractor shall perform and document accessibility testing appropriate to the deliverable, remediate defects within scope, and provide the Government with test results and an accessibility conformance statement or other evidence required by the written order.

• The Contractor shall comply with applicable federal contracting requirements, VA site-access rules, VA privacy and cybersecurity requirements, and all facility safety and infection-control procedures in effect at the medical center.

• The Contractor shall protect sensitive room, asset, safety, security, and occupancy information through least-privilege access controls and Government-approved publishing and sharing methods.

• For each exercised task, the Contractor shall provide test evidence, defect resolution, reproducible configuration records, source files, editable project files, scripts with source code and dependencies, data dictionaries, item and service inventories, version and license compatibility information, administrator runbooks, export and restore procedures for contractor-configured content, training, and knowledge transfer sufficient for Government staff or a successor contractor to operate, maintain, modify, and reprocure the solution. Credentials, tokens, and secrets shall not be embedded in deliverables.

3. ORDERING, PRICING, GOVERNMENT-FURNISHED ITEMS, AND

ACCEPTANCE

• Each optional task shall be ordered by task number. Each written order shall state the Option Year, ordered unit or units, quantities, specific buildings, levels, areas, assets, workflows, interfaces, applications, dashboards, user groups, or data products in scope; due dates and milestones; and any expressly excluded work. No minimum quantity is guaranteed.

• The Contractor’s order-level price or quotation shall identify the applicable fixed-price units or labor categories and hours, assumptions, Government and Contractor dependencies, non-ArcGIS third-party software or services, other direct costs, and travel. Government-furnished ArcGIS licenses, Enterprise hosting, kiosk hardware, and other listed Government-furnished equipment or information shall not be priced.

• Each written order shall identify all Government-furnished equipment and information and required availability dates, including accepted Indoors data, CAD, BIM, and other source files, system and interface documentation, test data, devices or sensors, approved user accounts and roles, VA network access, environment endpoints, certificates, and Government technical points of contact. The Contractor shall promptly document any schedule effect caused by unavailable or late Government-furnished items.

• The Government will furnish only the ArcGIS Enterprise capabilities, user types, extensions, and named-user assignments expressly identified in the written order. Before work begins, the Contractor shall submit and obtain confirmation of a license and version dependency matrix covering ArcGIS Indoors Maps, ArcGIS Indoors Spaces, ArcGIS IPS, ArcGIS Pro, Network Analyst, 3D Analyst, ArcGIS GeoBIM, ArcGIS Business Analyst and GeoEnrichment, ArcGIS GeoEvent Server or another real-time capability, Reality Mapping, Site Scan for ArcGIS, and any other required product. Listing a product in this Attachment does not represent that the product is included in the National VA Enterprise Agreement or approved for use.

• Each written order involving Microsoft 365, Microsoft Entra ID, Microsoft Graph, Autodesk Construction Cloud or BIM 360, Autodesk Platform Services, AutoCAD, Revit, or another non-Esri service shall identify the responsible party for licenses and subscriptions, tenant or project access, application registration, administrator consent, API permissions, firewall or allow-list changes, test accounts, and ongoing administration. No connection to an external cloud service or transfer of VA data outside the VA network is authorized until the Government provides written security and privacy approval.

• Attachment A travel is not included in the Base Year site-visit allowances. Each written order shall state whether performance is remote or on site and, if on site, the authorized location, number and duration of trips, number of travelers, work hours, badging and escort needs, and whether travel is included in the ordered fixed price or separately reimbursable. No on-site mobilization is required unless the written order states it.

• Kiosk hardware, mounts, power, cabling, peripheral devices, procurement, physical installation, hardware warranty, and hardware maintenance are Government-furnished or provided under a separate contract and are excluded from Attachment A pricing. If optional work affects the kiosk experience, the Contractor shall configure and test the ArcGIS Indoors software, maps, routing, and VA-approved browser and session behavior against the Government-furnished kiosk interface and VA network after the Government-furnished equipment is available. The written order shall state kiosk quantity, locations, screen and browser characteristics, network and authentication method, and test access.

• Each written order shall include objective acceptance criteria and a Government-approved test plan.

Unless the written order states otherwise, acceptance requires delivery in the National VA ArcGIS Enterprise environment or a Government-approved repository; successful demonstration of all ordered use cases; reconciliation to approved source data; completion of applicable security, privacy, performance, and Section 508 testing; delivery of all turnover items; correction of critical and high-severity defects; and written COR validation followed by acceptance by the CO or other authorized official.

• The Contractor shall not modify production content or authoritative source systems without an approved change record and rollback plan. Development, test, and production content shall be separated as directed by the Government. A task that cannot begin because a prerequisite, license, approval, source system, or Government-furnished item is unavailable shall remain unperformed until the CO provides direction and shall not be replaced with a Contractor-hosted or external service.

4. SCOPE OF WORK:

Group 1 – Mobile, IPS, and Space Planning

1.1 ArcGIS Indoors Mobile (Non-IPS) and Workspace Reservations & Shared Space Management The Contractor shall configure optional non-IPS mobile and workspace-reservation capabilities beyond the accepted baseline for the buildings, levels, reservation methods, workspace areas, and user groups stated in the written order. Required steps:

• Confirm that the ordered buildings have accepted floor-aware data and a routable network under the main SOW; review the approved floor plans, room naming, categories, access rules, and mobile and reservation use cases.

• Publish the maps, mobile map packages, categories, and search settings needed to support floor selection, people/place search, routing, and shared location links.

• Configure each ordered workspace area and reservation method. If the written order selects Microsoft 365, use Government-provided Microsoft Entra application registration, Microsoft Graph permissions and administrator consent, tenant information, and configured workspace or resource mailboxes. If the written order selects the Indoors Reservations layer, use the Government-approved editable layer, booking rules, editor permissions, and retention policy.

• Pilot the workflow with designated users; validate routing, booking, cancellation, recurring-booking, check-in and check-out behavior, permissions, and map usability as applicable; and correct issues before production release. Booking, check-in, and assignment records shall be labeled as scheduled or self-reported and shall not be represented as measured occupancy unless a separately approved measured-use source is integrated.

• Deliver user training, administrator procedures, and turnover documentation for sustainment.

• Deliverables shall include configured maps and apps, reservation rules and configuration, test scripts and results, training materials, and administrator procedures.

• The Contractor shall not enable reservation fields containing PII beyond the minimum approved by the Government.

• Access shall be role based, and the Contractor shall document successful Section 508 testing for the ordered mobile and reservation workflows, training, and documentation.

• Order and pricing unit: one configured mobile and reservation deployment for one identified building or one Government-defined group of buildings using one reservation method. The written order shall state building and level count, number of workspace areas, reservable units and meeting rooms, user roles, supported device, operating-system, and browser profiles, expected concurrent users, reservation method, Microsoft mailboxes and application registration if applicable, and training sessions. Acceptance requires successful search, routing, create, update, cancel, recurring-booking, check-in, and check-out tests as applicable for every ordered role and device profile, with permissions and audit behavior verified.

1.2 ArcGIS IPS Implementation for Indoors Mobile and Other Approved IPS-Aware Apps The Contractor shall implement optional ArcGIS IPS capability using the current Esri-supported IPS information model and Indoor Positioning Data Service workflow for the buildings, levels, and applications stated in the written order. No radio infrastructure, hardware, positioning model, or external service is authorized until approved by the Government. Required steps:

• For each building, confirm the exact levels, use cases, target horizontal and floor-detection accuracy, supported mobile devices and operating systems, and Government-approved radio infrastructure.

Select one current Esri-supported method per building—survey-less Bluetooth beacon-based positioning or survey-based Wi-Fi positioning—and document compatibility with the National VA ArcGIS Enterprise and ArcGIS Pro versions and VA security requirements.

• Prepare the prerequisite Indoors layers and facility data needed to support positioning.

• Prepare an IPS design package identifying the selected positioning method, infrastructure inventory, collection and processing workflow, coverage and accuracy targets, test method, maintenance approach, and rollback plan. For Bluetooth, identify beacon make, model, firmware, quantity, mounting, power, placement, and replacement responsibilities. For Wi-Fi, identify survey plan, compatible Android collection device, access-point information, and collection requirements.

• Create or update the approved IPS data model; conduct the authorized survey-less or survey-based collection; generate, quality-check, and publish the Indoor Positioning Data Service; make the ordered maps IPS aware; and test blue-dot positioning, floor awareness, transitions, pathway snapping, and route guidance as applicable.

• Conduct acceptance testing with Government personnel at the Government-approved test points and routes, report achieved horizontal accuracy and floor-detection performance, document coverage gaps and device variability, correct defects within scope, and provide maintenance and recalibration procedures.

• Deliverables shall include the IPS implementation plan, configured services, testing results, maintenance procedures, and user guidance.

• No beacon, sensor, network component, mobile device, mounting material, or physical installation is included unless the written order identifies its exact make, model, quantity, furnishing party, installation responsibility, and cybersecurity, safety, infection-control, and facilities approvals. The Contractor shall not install or alter physical infrastructure without prior written Government authorization.

• The Contractor shall document all dependencies, protect building-security information, and ensure the IPS deployment does not interfere with medical center operations, life-safety systems, or approved cybersecurity boundaries.

• Order and pricing unit: one IPS implementation for one identified building and stated number of levels using one approved radio-infrastructure method. The written order shall state building gross area, floor count, survey or collection area, access windows, existing Wi-Fi or beacon inventory, hardware quantity and furnishing party, supported devices and applications, Enterprise and ArcGIS Pro versions, license assignments, accuracy and floor-detection thresholds, test points and routes, and recalibration period. Acceptance requires the Government-approved quality assessment and representative route tests to meet the stated thresholds, successful floor transitions and route guidance, published service and map operation in National VA ArcGIS Enterprise, and complete as-built infrastructure, survey, test, and maintenance records.

1.3 ArcGIS Indoors Space Planner: Assignments, Planning Scenarios, and Portfolio Decision Support The Contractor shall configure optional ArcGIS Indoors Space Planner capabilities beyond the accepted baseline for the buildings, organizational units, workspace areas, and planning scenarios stated in the written order. Space Planner represents assignments, allocations, moves, workspace areas, and planning scenarios; it does not by itself measure physical occupancy or actual utilization. Required steps:

• Review approved organizational structures, occupancy categories, planning assumptions, and space-management business rules.

• Prepare or refine the Areas, Units, Occupants, and related layers and tables needed to support assignments and planning scenarios.

• Configure scenarios for office assignments, shared workspace allocation, move planning, department adjacency review, and other Government-approved use cases.

• Test reporting outputs and map-based views needed to compare assignments, allocations, moves, and planning scenarios. The Contractor may compare planned allocation with utilization measures only when the Government provides or separately orders an approved measured-use source and definition; assigned, reserved, checked-in, modeled, observed, and measured values shall remain separately labeled.

• Train designated users and deliver procedures for maintaining scenario data and publishing approved outcomes.

• Deliverables shall include configured planning layers, scenario templates, data dictionaries, job aids, and summary outputs.

• The Contractor shall maintain traceability between approved source data and planning outputs, clearly identify assumptions used in each scenario, and prevent unauthorized exposure of occupant or workspace assignment data.

• Planning products shall support VA review, records retention, controlled publication, and continued operation in the National VA ArcGIS Enterprise environment.

• Order and pricing unit: one Space Planner configuration for one identified portfolio, building group, or planning-scenario set. The written order shall state buildings and levels, organizational units, occupant and assignment record counts, workspace areas, scenario count, planning rules, source systems, user roles, reports, and training sessions. Acceptance requires traceable import and reconciliation of the ordered records, successful creation, comparison, and approval of each scenario, verified role restrictions, and clear labeling of assigned, reserved, checked-in, observed, modeled, and measured data. Measured utilization is accepted only when its approved source, time window, denominator, refresh rule, and data-quality threshold are stated and validated.

Group 2 – Data Model, Governance, and Asset Content

2.1 Enterprise Data Governance Expansion and Stewardship Automation The Contractor shall extend the accepted ArcGIS Indoors information model and governance baseline for the additional buildings, data domains, source systems, stewardship roles, or review processes stated in the written order. This optional task does not replace the governance, naming, data-dictionary, quality-control, or stakeholder-approval deliverables required by the main SOW. Required steps:

• Inventory the Government-approved source systems, drawings, BIM files, room and space records, asset sources, and organizational data used to populate Indoors.

• Define the target schema, field mappings, unique identifiers, naming conventions, metadata standards, and authoritative data sources for buildings, levels, units, details, occupants, assets, and related records.

• Develop a governance structure identifying stewardship roles, review cycles, approval authorities, update triggers, and issue-resolution procedures.

• Establish QA and change-control rules for adding new buildings, revising floor plans, correcting records, and publishing production updates.

• Deliver implementation guidance that extends the accepted main-SOW baseline without duplicating core Base Year or Option Year 1 governance work and that supports controlled campus expansion within National VA ArcGIS Enterprise.

• Deliverables shall include a governance plan, data dictionary, update matrix, QA and QC checklist, metadata requirements, and change-control procedures.

• All data standards shall be structured to support auditability, records retention, and controlled access to sensitive space, occupant, and asset information.

• Order and pricing unit: one governance package for a stated set of buildings, data domains, source systems, and stakeholder groups. The written order shall quantify source systems, layers and tables, fields and mappings, standards, workshops, review cycles, and approval authorities. Acceptance requires approval by the named Government data owners of the data dictionary, authoritative-source and field mappings, stewardship and approval matrix, change-control process, metadata requirements, and a representative traceability and quality-control sample.

2.2 Automated CAD/BIM-to-Indoors Update Workflow

The Contractor shall develop and document an optional automated or semi-automated workflow for recurring post-acceptance updates to ArcGIS Indoors from the specific Government-approved CAD or BIM source format stated in the written order. This task does not include the initial building conversion, LiDAR scanning, or core data-model implementation required by the main SOW. Required steps:

• Review the ordered source-file types, quantities, sizes, versions, layers, model categories, coordinate information, naming rules, quality conditions, and preprocessing requirements. Identify any need for AutoCAD, Revit, Autodesk Construction Cloud, BIM 360, Autodesk Platform Services, IFC-processing, or other non-Esri software and the party responsible for its license and access.

• Design the source-to-target workflow for recurring updates, including file intake, validation, transformation, field mapping, geometry cleanup, floor assignment, and publish-ready outputs.

• Configure scripts, tools, or repeatable procedures in the Government-approved environment to process the ordered updates, preserve stable identifiers, prevent unapproved production overwrites, log all changes and exceptions, and avoid embedded credentials or workstation-specific dependencies.

• Test the workflow against representative source files and demonstrate that update outputs preserve schema integrity, spatial alignment, and required attributes.

• Deliver standard operating procedures, troubleshooting guidance, and turnover documentation for Government use and future contract transition.

• Deliverables shall include the configured workflow, scripts or automation tools, validation reports, exception logs, standard operating procedures, and test results.

• The workflow shall be supportable by Government staff or a successor contractor. The Government shall receive source code, dependency and version manifests, configuration files, field mappings, test fixtures when releasable, deployment and rollback instructions, and unrestricted Government rights required by the contract in all scripts, mappings, and documentation developed under the order.

• Order and pricing unit: one automated ingest workflow for one specified source format or template and one target data domain or building family; each additional CAD standard, Revit or IFC version, transformation path, or source system shall be separately quantified. The written order shall state file and model counts, sizes, versions, layers or categories, buildings and levels, expected update frequency, exception categories, non-Esri license responsibility, representative test files, and required manual-review threshold. Acceptance requires repeatable processing of the stated test files, compliance with the approved schema and identifier rules, successful spatial-alignment and attribute checks, an exception log for unresolved records, no unapproved production overwrite, and complete code and operational turnover.

2.3 Utility, MEP, Furniture, and Asset Mapping in ArcGIS Indoors The Contractor shall configure optional utility, mechanical, electrical, plumbing, furniture, or asset content beyond the accepted core building geometry and Life Safety baseline for the specific asset categories, buildings, levels, and source records stated in the written order. Required steps:

• Define the feature classes, attributes, symbols, identifiers, and business rules required for each asset category.

• Collect and evaluate existing Government-approved source data, including drawings, BIM content, asset lists, inspections, and room-based inventories.

• Convert, load, or digitize the required information into the approved geodatabase structure and align the records to rooms, floors, buildings, and asset identifiers where applicable.

• Perform QA and resolve data gaps, duplicate records, geometry issues, and symbology inconsistencies before publication.

• Publish the approved map layers, document update procedures, and train designated users on data maintenance and use.

• Deliverables shall include configured layers, asset and category dictionaries, symbology standards, QA and QC results, and update guidance.

• The Contractor shall coordinate closely with VA technical staff before loading any utility or life-safety data and shall apply access restrictions where operational sensitivity requires limited visibility.

• Asset data shall be structured to support downstream use in maintenance, planning, and dashboard and reporting workflows exercised under this contract.

• Order and pricing unit: one identified asset category for one building or Government-defined building group. The written order shall state buildings and levels, source-file and record counts, estimated asset count, required attributes and identifiers, collection or digitization method, accuracy and completeness thresholds, sensitive-data restrictions, publication groups, update frequency, and training. Acceptance requires delivery of the ordered records and layers, reconciliation to the approved source totals, successful identifier and room or level relationship checks, completion of the stated spatial and attribute quality sample, approved symbology and access controls, and turnover documentation.

Group 3 – Integration and Field Workflows

3.1 ArcGIS Indoors Integration with Facility Management Systems The Contractor shall implement the specific optional interface or interfaces between ArcGIS Indoors and Government-approved facility-management systems stated in the written order. No source system, direction of exchange, interface method, or write capability is implied by this task title. Required steps:

• Identify each source and target system by product, version, environment, data owner, system of record, interface owner, approved API, service, file exchange, or middleware method, authentication method, network endpoint, and security boundary.

• Define the objects and fields, data direction, authoritative source, frequency, volume, history, retention, transformation, reconciliation rules, retry behavior, and whether the interface is read-only or may perform expressly authorized writes.

• Configure and test the interfaces needed to pass location identifiers, room data, asset data, occupancy data, or work-order references, as approved by the Government.

• Develop monitoring and reconciliation procedures so the Government can identify failed transfers, stale data, or mismatched records.

• Deliver support documentation and train designated administrators on the approved integration workflows.

• Deliverables shall include interface specifications, field-mapping documentation, test scripts and results, issue logs, and support procedures.

• The Contractor shall use only Government-approved APIs, services, exports, or middleware and shall not introduce direct writes to authoritative systems unless expressly authorized in writing.

• Any system integration involving sensitive information shall follow approved privacy, cybersecurity, and least-privilege controls.

• Order and pricing unit: one interface for one identified source-to-target system pair and one stated data flow. The written order shall quantify endpoints, objects and fields, historical records, expected transactions or records per interval, environments, refresh frequency, error and retry requirements, monitoring, and support window. Government-furnished dependencies include approved endpoints, interface documentation, test data, credentials, network access, and source-system technical support. Acceptance requires successful end-to-end positive, negative, permission, reconciliation, failure, retry, stale-data, and recovery tests; confirmation that no unauthorized writes occur; and complete interface, monitoring, rollback, and support documentation.

3.2 Configure Launch Actions in Indoors Viewer to Include Work Order Integration with Field Maps & Survey123 The Contractor shall configure optional launch actions beyond the baseline Survey123 and field-data workflows required by the main SOW for the specific buildings, asset or room types, user roles, downstream applications, forms, and parameters stated in the written order. Required steps:

• Identify the facilities, asset types, room records, and user roles that require launch actions.

• Define the parameters that must pass from Indoors to downstream workflows, such as building, level, room, unit, asset ID, coordinates, and task type.

• Configure the launch actions, URLs, app links, forms, and role-based visibility required to open the correct workflow from the Viewer.

• Test the behavior across supported browsers and devices and validate that the correct record context is passed to Field Maps or Survey123.

• Deliver configuration documentation, user guidance, and maintenance procedures for future updates.

• Deliverables shall include configured launch actions, parameter maps, testing results, user guidance, and support procedures.

• The Contractor shall ensure launch actions do not expose restricted asset or room information to unauthorized users and shall coordinate any external links or app dependencies with the Government before implementation. All configured workflows shall be documented sufficiently to support future maintenance.

• Order and pricing unit: one launch action for one identified target application and form or workflow; each materially different parameter map, target environment, or role-specific behavior shall be separately quantified. The written order shall state action count, source layer and record types, target app and form, parameters, user roles, browsers and devices, online or offline behavior, and test records. Acceptance requires every ordered action to open the correct target and record context, pass only authorized parameters, enforce role visibility, handle missing or invalid values safely, operate on all stated browser and device profiles, and include maintainable parameter and configuration documentation.

3.3 Consulting Support of Field Workflows in ArcGIS Field Maps The Contractor shall provide optional consulting and configuration for new or expanded ArcGIS Field Maps workflows beyond the field-verification and baseline Survey123 or Field Maps work required by the main SOW. Each written order shall identify the exact workflow, layers, forms, assets, buildings, users, devices, and connectivity conditions. Required steps:

• Work with the COR and designated stakeholders to define priority use cases such as inspections, asset verification, deficiency tracking, utility rounds, furniture updates, or room-based field inventories; configure maps, editable layers, forms, related tables, domains, attachments, and offline areas as needed to support those workflows.

• Align the field workflows with approved indoor maps, launch actions, asset identifiers, and quality-control requirements.

• Test the workflows with end users, refine the form logic and editing rules, and correct usability issues before deployment.

• Deliver training, administrator guidance, and recommended sustainment practices for continued field use.

• Deliverables shall include configured field maps, form logic, offline settings, data standards, training materials, and test results.

• The Contractor shall ensure the field workflows operate within approved access controls, clearly separate production and testing environments, and preserve an auditable record of edits, attachments, and status changes.

• Any workflow involving safety-sensitive or operationally sensitive assets shall be coordinated with the appropriate VA functional lead before deployment.

• Order and pricing unit: one field workflow consisting of one map and one related form or editing process for a stated asset or inspection domain; additional forms, asset domains, offline areas, or materially different user roles shall be separately quantified. The written order shall state feature and related-table counts, required fields and rules, attachment types and limits, offline areas, user and device counts, synchronization expectations, training sessions, and source-data dependencies.

Acceptance requires successful create, edit, validation, attachment, offline, synchronization, conflict, permission, and audit-history tests as applicable, plus complete administrator and sustainment documentation.

3.4 Real-Time Indoor Data Integration & Monitoring

The Contractor shall configure the specifically identified, Government-approved real-time indoor data feeds and monitoring workflows stated in the written order using a VA-approved capability within or connected to National VA ArcGIS Enterprise. No live source, external service, ArcGIS GeoEvent Server license, other streaming capability, sensor, or interface is implied or included unless stated in the written order. Required steps:

• Identify each approved live source by owner, system, endpoint, interface or protocol, schema, authentication method, security classification, update behavior, and authoritative status. Examples such as environmental sensors, occupancy feeds, equipment status, or safety-system indicators are illustrative only and do not establish scope.

• Define expected message or record volume, update frequency, latency, transformation, retention and historical-storage needs, data-quality rules, thresholds, alert ownership, user roles, failure behavior, and support responsibilities for each feed.

• Configure the approved data flow, transformation logic, monitoring, and ArcGIS Enterprise services using ArcGIS GeoEvent Server or another exact Government-approved capability stated in the order. The Contractor shall not substitute ArcGIS Online, ArcGIS Velocity, Contractor hosting, or another external service without express written authorization.

• Test normal operation, thresholds, alerting, filtering, duplicate or malformed messages, source interruption, stale-data indication, retry, reconnection, and recovery, and document response and escalation procedures for data interruptions.

• Deliver monitoring guidance, support documentation, and turnover materials for ongoing administration.

• Deliverables shall include interface and schema specifications, configured data flows, transformation and alert logic, capacity and license dependencies, source and service inventories, monitoring views, test results, issue and recovery procedures, and administrator documentation.

• Real-time integrations shall use only Government-approved interfaces and shall not bypass cybersecurity review or established network boundaries.

• The Contractor shall document any dependencies on external services, ensure dashboards clearly distinguish live data from static reference data, and provide the Government with sufficient information to maintain or reprocure the monitoring workflow.

• Order and pricing unit: one real-time source-to-target feed or pipeline. The written order shall state endpoints, protocols, fields, messages or records per second or interval, retention period, dashboards and alerts, environments, uptime or support window, test duration, and latency, completeness, and reconciliation thresholds. Government-furnished dependencies include approved endpoints, representative live or simulated test data, credentials, network routes, certificates, licenses, and source-system support. Acceptance requires the ordered sustained-load test, stated latency and data-loss results, successful access-control and outage, retry, recovery, and stale-data tests, clear distinction between live and static information, and complete operational turnover.

Group 4 – Dashboards and User Experience

4.1 ArcGIS Dashboards – FCA, Lifecycle, Utilization, and SCIP Planning The Contractor shall develop the optional ArcGIS Dashboards, pages, indicators, filters, and measures stated in the written order to support FCA, lifecycle, utilization, or SCIP decision support beyond the accepted baseline. Required steps:

• Identify each approved source, data owner, authoritative status, KPI definition, formula, denominator, time window, refresh rule, target or threshold, filter, and data-quality limitation required for dashboard calculations.

• Configure map-driven and chart-driven views that allow users to filter by building, service, floor, department, asset type, or planning category.

• Display only Government-approved measures. Any utilization measure shall identify whether it is based on assignments, reservations, check-ins, observations, sensors, or another measured source;

these evidence types shall not be substituted for one another or presented under an ambiguous utilization label.

• Test the dashboards with designated users and refine symbology, filters, labels, and calculations before release.

• Deliver documentation and training so the dashboards can be sustained and updated under the contract.

• Deliverables shall include configured dashboards, data definitions, test results, and user and administrator guides.

• The Contractor shall clearly identify any assumptions or data limitations that affect prioritization outputs and shall avoid presenting draft analytics as authoritative decisions unless approved by the Government.

• Dashboards shall support executive review, records retention, reproducible calculations, controlled access, and turnover for sustainment by Government staff or a successor contractor.

• Order and pricing unit: one dashboard with a stated number of pages, data sources, KPIs, charts, maps, filters, and user roles; additional dashboards or materially different source models shall be separately quantified. The written order shall state record volumes, refresh rate, supported browsers and displays, expected concurrent users, performance target, export needs, and training.

Acceptance requires reconciliation of every KPI against approved sample calculations, successful refresh and filter tests, performance and permissions testing, Section 508 evidence, documented data lineage and limitations, and complete editable configuration and administrator turnover.

4.2 ArcGIS Dashboards – Patient Flow, Capacity, and Room Utilization The Contractor shall develop optional ArcGIS Dashboards for the specific patient-flow, capacity, and room-use questions, approved data sources, measures, buildings, service areas, and user roles stated in the written order. No clinical, sensor, reservation, assignment, or occupancy data source is implied by the title. Required steps:

• Confirm the operational questions, metric definitions, and approved data sources with the COR and stakeholder groups.

• Configure the ordered indoor maps, charts, indicators, and filters to display only approved and defined measures. Assignment records, reservations, check-ins, sensor observations, manual observations, and clinical throughput records are distinct evidence types and shall not be substituted for one another. Assignment or reservation counts shall not be labeled as measured occupancy or utilization.

• For every occupancy, utilization, capacity, or patient-flow measure, document the source system, numerator, denominator, unit, time window, refresh rule, missing-data handling, validation owner, and whether the result is assigned, scheduled, self-reported, observed, modeled, or measured.

• Align the analytics to buildings, clinics, departments, or service areas designated by the Government and validate the dashboard logic against source data.

• Conduct user testing and refine displays so they are understandable to leadership and operational users.

• Deliver guidance on refresh cycles, interpretation of measures, and sustainment responsibilities.

Deliverables shall include configured dashboards, business-rule definitions, testing results, and user guidance.

• The Contractor shall ensure the dashboards do not expose protected health information unless specifically authorized and properly safeguarded.

• Any patient-flow analytics shall be presented as operational decision support and not as a replacement for clinical systems of record or clinical judgment.

• Order and pricing unit: one dashboard with the stated buildings or service areas, pages, measures, sources, filters, roles, and refresh interval. The written order shall quantify data sources, metrics, locations, historical period, expected record volume, user groups, displays, and training. Acceptance requires Government-owner approval of every definition, reconciliation to approved source samples, correct evidence-type labels, successful refresh, filter, role, performance, privacy, and Section 508 tests, and confirmation that no unauthorized PHI or PII is displayed or retained.

4.3 ArcGIS Dashboards – Safety, Security, Infection Prevention, Evacuation, and Life Safety The Contractor shall develop ArcGIS Dashboards that support Government-approved safety, security, infection prevention, evacuation, and life-safety use cases. Required steps:

• Identify the approved layers, assets, plans, and incident indicators to be visualized, such as exits, stairwells, shutoffs, extinguishers, alarm zones, isolation areas, muster points, or other response-related content.

• Configure dashboards that combine indoor maps with indicators, filters, lists, and status views appropriate to the authorized user roles.

• Incorporate routing, floor-aware filtering, or operational status displays when approved by the Government.

• Test the dashboards with designated functional users and refine performance, visibility, and usability before release.

• Deliver sustainment documentation and user guidance for future updates and drills. Deliverables shall include configured dashboards, data definitions, role-based access documentation, and test results.

• The Contractor shall treat safety and security layers as sensitive information, limit visibility to authorized users, and ensure no dashboard content conflicts with official emergency plans, life-safety procedures, or infection-prevention protocols established by the Government.

• Order and pricing unit: one safety, security, infection-prevention, evacuation, or Life Safety dashboard for a stated building group and approved user community. The written order shall quantify buildings, floors, layers, assets, plans, indicators, filters, roles, source systems, refresh rate, displays, and drills or test scenarios. Acceptance requires approval by each named functional data owner; successful role, routing, floor-filter, source-reconciliation, performance, security, and Section 508 tests; confirmation that the display does not supersede official emergency or Life Safety documents; and complete controlled-access and sustainment documentation.

4.4 ArcGIS Experience Builder

The Contractor shall configure ArcGIS Experience Builder applications that consolidate approved ArcGIS Indoors content, dashboards, forms, and related tools into a unified user experience. Required steps:

• Define the user personas, access groups, and primary business tasks for the application.

• Design the experience architecture, navigation, widgets, embedded content, and data sources.

• Configure responsive pages and role-based views that present the approved mix of indoor maps, dashboards, forms, documents, and external links.

• Test performance, usability, and permissions across supported devices and browsers and correct issues before release.

• Deliver administrator guidance, training, and sustainment documentation for future updates.

Deliverables shall include the configured Experience Builder application, design documentation, test results, and user and administrator guides.

• All ordered Experience Builder content, not only public-facing content, shall be Section 508 compliant and supported by documented accessibility testing. Sensitive operational information shall be restricted to authorized roles, embedded content shall use approved authoritative sources, and unavailable or unauthorized external content shall fail safely without exposing data or credentials.

• Order and pricing unit: one Experience Builder application with a stated number of pages, widgets, maps, dashboards, forms, documents, links, data sources, responsive breakpoints, and role-specific views. The written order shall state supported browsers and devices, expected concurrent users, authentication, accessibility and performance targets, and training sessions. Acceptance requires successful navigation, responsive-layout, widget, embedded-content, permission, broken-link, performance, and Section 508 tests on every stated profile, with complete editable application configuration, dependency inventory, and administrator turnover.

Group 5 – Advanced Enterprise and Analytic Capabilities

5.1 ArcGIS GeoBIM

The Contractor shall configure optional ArcGIS GeoBIM capabilities only when the written order identifies the exact National VA ArcGIS Enterprise and…