ATTACHMENT 6 - Attachment A _36C26226Q1007.pdf

Attachment-A

Optional Tasks - Scope of Work:

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

(ArcGIS Indoors)

VA Long Beach Healthcare System

This Attachment-A establishes the optional task-specific Statement of Work (SOW) for Option Years 1 - 4 ArcGIS Indoors at the VA Long Beach Healthcare System (VALBHS). It is intended to be used in conjunction with the main SOW and corresponding ordering provisions.

These optional tasks may be exercised individually or in combination at the Government’s discretion.

1. SUMMARY TABLE

Group Task No. Task Title Short Description

Group 1

Core Indoor Experience Augmentation Tasks

1.1 ArcGIS Indoors Mobile (Non-

IPS) and Workspace Reservations / Shared Space Management

Configure Indoors Mobile and related reservation workflows for floor-aware indoor search, routing, and shared space management in approved buildings.

1.2 ArcGIS Indoors Mobile IPS

Implement indoor positioning to provide blue-dot location, floor awareness, and indoor navigation in selected facilities.

1.3 Indoors Space Planner:

Utilization & Portfolio Decision Support

Configure space-planning capabilities to support assignments, hybrid work, utilization analysis, and portfolio planning decisions.

Group 2

Data Foundation and System Maintenance

2.1 Indoors Information Model & Data Governance

Establish the campus data model, stewardship roles, standards, and governance needed to manage Indoors as an enterprise system.

2.2 Automated Data Ingest

Workflow (Replaces CAD/BIM to Indoors Update Workflow)

Develop a repeatable workflow to ingest approved CAD/BIM source files into the Indoors model with validation, logging, and handoff procedures.

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 workorder data can be synchronized.

Facilities Operations and Maintenance Capabilities

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 approved real-time feeds and monitoring logic so indoor maps and dashboards can display live operational conditions and alerts.

Group 4

Dashboards and Decision Support

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.

4.2 ArcGIS Dashboards – Patient

Flow, Capacity, and Room Utilization

Create dashboards that visualize room and space use, capacity, and operational patterns to support planning and workflow improvement.

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

Planning, BIM, and Reality Mapping Tasks

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.

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 Site Scan for ArcGIS / ArcGIS Reality

Provide reality-capture support for orthomosaics, 3D mesh, and related products that strengthen campus planning, project visualization, and digital-twin updates.

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 performed only when separately exercised by the Government.

• The Contractor shall align optional task execution with the approved ArcGIS Indoors architecture, contractor-hosted operating environment, and any future Government-directed migration to a VA enterprise environment.

• All deliverables, user documentation, dashboards, forms, and training materials intended for Government use shall be Section 508 compliant.

• 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.

• The Contractor shall provide testing, issue resolution, knowledge transfer, and turnover documentation for each exercised task.

3. 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 and deploy ArcGIS Indoors Mobile (non-IPS) and associated workspace reservation workflows for Government-approved buildings at VALBHS. Required steps:

• Review the base Indoors database, floor plans, room naming, categories, access rules, and rollout sequence for Building 126 and follow-on buildings.

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

• Configure reservable workspaces and meeting spaces using the Government-approved reservation method, including Microsoft 365 integration if authorized, or the Indoors reservation data model when directed.

• Pilot the workflow with designated users, validate routing behavior, booking rules, check-in/checkout logic, and map usability, and correct issues before production release.

• 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, all training and documentation shall be Section 508 compliant.

1.2 ArcGIS Indoors Mobile IPS

The Contractor shall implement ArcGIS Indoors Mobile with indoor positioning system (IPS) capability in the buildings authorized by the Government. Required steps:

• Confirm candidate buildings, use cases, and environmental constraints with the COR.

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

• Design and document the positioning approach for each building, including any required on-site collection, reference features, or hardware placement strategy approved by the Government.

• Configure, publish, and test the IPS data and services needed to support blue-dot positioning, floor awareness, and route guidance in the Indoors mobile experience.

• Conduct acceptance testing with Government personnel, document accuracy limits, and provide maintenance procedures for recalibration or updates.

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

• Any beacon, sensor, or other physical installation shall require prior Government approval and coordination with facility operations and safety officials.

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.

1.3 Indoors Space Planner: Utilization & Portfolio Decision Support The Contractor shall configure ArcGIS Indoors Space Planner capabilities to support utilization analysis and portfolio decision support for the VALBHS campus. 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 scenarios, identify underused space, and support portfolio decisions across the buildings prioritized by the Government.

• 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 be delivered in a format that supports VA review, record retention, and future transfer to a VA-approved environment.

Group 2 – Data Model, Governance, and Asset Content

2.1 Indoors Information Model & Data Governance

The Contractor shall establish an ArcGIS Indoors information model and governance framework for VALBHS. 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 aligns the Indoors information model with base-contract operations and future campus expansion.

• 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.

2.2 Automated Data Ingest Workflow (Replaces CAD/BIM to Indoors Update Workflow) The Contractor shall develop and document an automated or semi-automated workflow to update ArcGIS Indoors from Government-approved CAD and BIM source files. Required steps:

Review incoming source formats, layer, and model standards, naming rules, and preprocessing steps used by VALBHS and supporting A/E teams.

• 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 the scripts, tools, or repeatable procedures needed to process approved updates for in scope buildings and log exceptions that require manual resolution.

• 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 Contractor shall ensure the workflow is supportable by Government staff or successor support contractors, does not overwrite production data without approved controls, and preserves all Government ownership rights in scripts, mappings, and documentation developed under the contract.

2.3 Utility, MEP, Furniture, and Asset Mapping in ArcGIS Indoors The Contractor shall configure ArcGIS Indoors content to include approved utility, MEP, furniture, and asset information for buildings identified by the Government. 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.

Group 3 – Integration and Field Workflows

3.1 ArcGIS Indoors Integration with Facility Management Systems The Contractor shall integrate ArcGIS Indoors with Government-approved facility management systems needed to support space, asset, and maintenance workflows. Required steps:

• Identify the target systems, interface methods, data owners, and approved exchange patterns.

• Define the integration scope, including which records and fields will be read, synchronized, or referenced between systems.

• 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.

3.2 Configure Launch Actions in Indoors Viewer to Include Work Order Integration with Field Maps & Survey123 The Contractor shall configure launch actions in ArcGIS Indoors Viewer to support Government approved work-order, inspection, and reporting workflows in ArcGIS Field Maps and ArcGIS Survey123. 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.

3.3 Consulting Support of Field Workflows in ArcGIS Field Maps The Contractor shall provide consulting and configuration support for Government-approved field workflows implemented in ArcGIS Field Maps. 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.

3.4 Real-Time Indoor Data Integration & Monitoring

The Contractor shall configure approved real-time indoor data integration and monitoring workflows that enhance situational awareness at VALBHS. Required steps:

• Identify Government-approved live data sources such as environmental sensors, occupancy feeds, equipment status, safety-system indicators, or other operational feeds.

• Define the target update frequency, retention needs, thresholds, and user roles for each feed.

• Configure the data flow, transformation logic, and hosted or connected services needed to bring the approved feeds into indoor maps or dashboards.

• Test alerting, status displays, filtering, and failure conditions and documenting the response procedures for data interruptions.

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

• Deliverables shall include the configured data flows, schema maps, alert logic, test results, 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.

Group 4 – Dashboards and User Experience

4.1 ArcGIS Dashboards – FCA, Lifecycle, Utilization, and SCIP Planning The Contractor shall develop ArcGIS Dashboards that support facility condition assessment (FCA), lifecycle planning, utilization analysis, and SCIP planning for the VALBHS campus. Required steps:

• Identify the approved data sources, business rules, and KPI definitions needed 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 Government-approved measures such as condition indicators, lifecycle needs, utilization patterns, portfolio comparisons, and planning status information.

• 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 be structured to support executive review, records retention, and future sustainment under the contract.

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

The Contractor shall develop ArcGIS Dashboards that visualize patient flow, capacity, and room utilization metrics approved by the Government. Required steps:

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

• Configure the required indoor maps, charts, indicators, and filters to display room utilization, service capacity, throughput, or bottleneck conditions at the approved level of detail.

• 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.

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.

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.

• The Contractor shall ensure all public-facing or broad-access content is Section 508 compliant, that sensitive operational information is restricted to authorized users, and that embedded content remains linked to approved authoritative sources.

Group 5 – Advanced Enterprise and Analytic Capabilities

5.1 ArcGIS GeoBIM

The Contractor shall configure ArcGIS GeoBIM capabilities, when exercised, to connect ArcGIS Indoors and other approved GIS content with Government-approved BIM and project information sources.

Required steps:

• Identify the buildings, projects, BIM models, issue sources, and document repositories approved for inclusion.

• Define the common identifiers, spatial relationships, and project or asset linkages required to connect GIS features with BIM and project records.

• Configure the GeoBIM views, dashboards, or web experiences needed to present approved cross system relationships.

• Test the workflows with designated users and verify that linked records, issue views, and model references open correctly and securely.

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

Deliverables shall include configured GeoBIM content, integration maps, test results, and user and administrator guidance.

• The Contractor shall use only Government-approved repositories and shall not expose controlled drawings, BIM models, or project documentation to unauthorized users.

• All mappings between BIM and GIS records shall be documented sufficiently to support future maintenance, audits, and transfer of operations.

5.2 ArcGIS Business Analyst – Catchment, Drive-Time, Expansion, CBOC, and Telehealth Territory Analysis The Contractor shall perform Government-approved ArcGIS Business Analyst studies to support catchment analysis, drive-time analysis, expansion planning, community-based outpatient clinic (CBOC) considerations, and telehealth territory analysis. Required steps:

• Confirm the study questions, geographies, service lines, and approved business rules with the COR.

• Compile the approved locations, population and service data, travel assumptions, and comparison areas needed for each analysis.

• Configure and run the required catchment, market, drive-time, service-area, or territory analyses using the approved methodology.

• Prepare maps, findings, and presentation-ready outputs that compare alternatives or illustrate access conditions identified by the Government.

• Document assumptions, data sources, limitations, and reproducible methods for future refreshes.

Deliverables shall include maps, dashboards or reports when directed, methodology notes, assumptions, and presentation-ready outputs.

• The Contractor shall clearly identify data vintage, assumptions, and limitations and shall avoid unsupported predictive claims.

• Any recommendations shall be framed as decision support for Government review and not as automatic siting or service-line determinations.

5.3 Site Scan for ArcGIS / ArcGIS Reality

The Contractor shall provide Government-approved reality-capture support using Site Scan for ArcGIS, ArcGIS Reality, or both, as applicable to the exercised option. Required steps:

• Develop a capture and processing plan identifying the site, intended products, control requirements, safety constraints, and approvals required before field work.

• Collect or process approved imagery, lidar, photogrammetry, or related source data needed to produce orthomosaics, 3D meshes, point clouds, or other specified outputs.

• Register and quality-check the resulting data against approved control or campus reference data and document accuracy limitations.

• Publish or deliver the approved products for use in planning, visualization, project support, or digital-twin updates as directed by the Government.

• Provide metadata, update procedures, and user guidance for future reuse.

• Deliverables shall include the approved reality products, metadata, QA and QC results, and update guidance.

• Any field collection shall comply with all Government site-access rules, safety requirements, and any applicable FAA or airspace restrictions.

• The Contractor shall protect sensitive campus imagery, avoid operational disruption, and coordinate all collection schedules with the Government before mobilization.