# 02 — Classification

**Project:** Supply, Delivery, Installation, Integration, and T&C of MRT-7 Stations and Depot Electronics Networks (FDAS + ACS Integration)
**Customer:** **SMC MASS RAIL TRANSIT 7, INC.** (slug: `san-miguel-mrt7`; customer-kb entry: **no** — but brands model-locked by ANNEX_D1/D2 so the kb-absence is non-blocking)
**Date:** 2026-04-29 (revision 2 — formal bid pack incorporated)

## Discipline

- **Primary:** **Hybrid** — Electronics-Networks Integration (Philippines low-voltage / building-electronics scope), with closest single-discipline analog being BMS (centralized monitoring head-end + controllers + field devices + structured cabling pattern).
- **Secondary:**
  - **FDAS** — Fire Detection and Alarm System (Notifier NFS2-3030 platform; intelligent addressable; ONYX series networking)
  - **ACS / SMS** — Access Control System / Security Management System (Suprema CoreStation CS-40 platform; BioStar 2 software)
  - **Network / Communication infrastructure** — L2 Ethernet switches with SFP, FOC underground (multi-mode + single-mode per spec §1124.2.9), STP shielded twisted-pair (per spec §1124.2.10), interface to ROTEM IP-MPLS, structured cabling between Depot Admin OCC/CER/FCCR
  - **Civil-coordination** — limited (we install only at building stub-ups + workstation drops; underground conduit by Civil Contractor / REC per TOR §9.1)

The closest existing playbook overlay is `_playbook/modules/bms/`. Per Op#13 (D-002), this run **clones the BMS overlay structure into project-local `_clones/_playbook/modules/fdas/` and `…/acs/`** and authors starter overlay content there, anchored to the now-known panel models (Notifier + Suprema).

## Stage

- **Greenfield (new construction).**
- Cited evidence:
  - TOR §2: *"The MRT7 Project is approximately 26-km rail system, including 14 stations, from San Jose del Monte, Bulacan to North Avenue-EDSA, Quezon City."* — line is in construction.
  - TOR §5.1, §5.2: both phases are integration-with-other-contractors on a construction project, not a retrofit of operating system.
  - No existing-system inventory in the bid documents.
  - ANNEX_C1 + ANNEX_C2 are stamped *"FOR APPROVAL"* / *"PRELIMINARY SUBMISSION"* with revision dates 2024-12-16 (C2 rev 5) and 2025-05-22 (C1 rev 2) — current design documents.
- Triangulation: cover-letter wording, technical evidence, and TOR all align — no contradiction. Stage locked: **greenfield**.

## Scope type (legacy multi-select — superseded by `scope_shape:` below)

- [x] Supply
- [x] Installation
- [x] Programming (system integration / configuration / software / GUI development)
- [x] Testing & Commissioning (TOR §4.21 — Standalone + Integration + Performance tests)
- [x] Training (TOR §4.22 — for MRT7 + DOTr personnel)
- [ ] Maintenance — **NOT in scope** (warranty 2 yr + software support 3 yr only; no PMS contract)

## Scope shape (Op#12 — drives pathway activation)

```yaml
scope_shape:
  supply: full
  supply_categories: []  # all in-scope categories supplied per Resp. Matrix "New Contractor" column + TOR §4
  installation: full
  osm_categories: []  # not applicable — full installation
  services: full
  exclusions:
    - site_development_conduit  # TOR §9.1 — Civil Contractor / REC supplies and installs the underground interbuilding conduit/ductbank/manholes; we pull cables only
    - fdas_panels_at_civil_buildings  # TOR §6.4 — Civil Contractor supplies + installs Notifier NFS2-3030 FACPs at depot buildings; we connect cables and provide gateway/IF-card
    - acs_panels_at_civil_buildings   # TOR §6.4 — Civil Contractor supplies + installs Suprema CS-40 controllers; we connect cables and provide gateway/IF-card
    - rotem_managed_panels             # Resp. Matrix — ROTEM supplies FACP + AGP at Depot O&M / Aux / TPSSR / PH1&2 / STP; we connect
    - rotem_communication_network      # Resp. Matrix — ROTEM provides Station↔Depot IP-MPLS backbone; we connect via L2 switch interface in CER (TOR §4.7)
    - emcs                              # OUT of scope (D-015 user direction); C1 §1125-1127 + ANNEX_A 13008/13011A/B reference only
  notes: |
    Turnkey FDAS + ACS workstation + integration scope across the Depot Admin Building (OCC + FCCR head-ends)
    and 12 stations (Stations 1-12 per TOR §4.1, locked by D-015). Our scope BoM:
    - 4 workstation systems (FDAS @ OCC, ACS @ OCC, FDAS @ FCCR, ACS @ FCCR), each with workstation PC + server + UPS + monitor + peripherals
    - Workstation furniture (table for up to 4 PCs + ergonomic chairs) at OCC and FCCR
    - L2 industrial Ethernet switches at OCC and FCCR, interfacing to REC's CER L2 switch (TOR §4.7)
    - Gateway / interface cards: one per station (12 sets) + one per depot building hosting integration
    - Inter-building FOC + STP cables (Phase 2): terminations at Civil-installed FACP/Core Station + workstation racks at FCCR/OCC
    - Line surge protection at each inter-building FOC/STP termination
    - Conduit at building stub-ups + raceway at OCC/FCCR (the underground portion is excluded per TOR §9.1)
    - FDAS devices (smoke/heat/manual call points/notification appliances) in Genset Building + Guard Houses (per Resp. Matrix — these specific buildings have us providing the FDAS Devices line)
    - ACS Gathering Panel installation at Genset Building (per Resp. Matrix — though "Civil Contractor" is the supplier on that row; we likely install)
    - Engineering deliverables: Material Approval, Shop Drawings, ICD, T&C Plan, Method Statement, As-built (signed/sealed)
    - 2-yr spare-parts package; 3-yr software support; O&M training for MRT7 + DOTr
```

**Pattern match:** Closest fit is **Pattern 1 — Turnkey BMS** in `_playbook/checklists/pathway-activation.md` (`supply: full`, `installation: full`, `services: full`), with explicit exclusions list. Discipline differs (FDAS+ACS+Networks instead of BMS) — handled via Op#13 transmutation per D-002, anchored to Notifier (FDAS) + Suprema (ACS) brand platforms.

## Facility type

**Multi-site rail-transit infrastructure** — 12 MRT-7 stations (Elevated / Depressed / At-grade — see TOR Table 1) + depot compound (industrial maintenance facility with Admin Building + multiple operations buildings). Closest playbook category: "Industrial / Manufacturing" for the depot compound; stations are "Other / Transit-infrastructure." Treat as **mixed-use multi-site infrastructure**.

## Estimated tier

- **Large** — basis:
  - **Multi-site:** 12 stations + 10+ depot buildings.
  - **Multi-discipline integration:** FDAS + ACS + Networks + civil-coordination.
  - **Multi-phase delivery:** Phase 1 + Phase 2 in 180 CD.
  - **Performance bar:** PEE-supervised (R.A. 9292), 5-similar-projects requirement, no-subcontracting on Electronics works.
  - **Schedule pressure:** 24-hour shifts contemplated (TOR §11.4) to meet completion.
  - **Bonds + retention:** total provisioning ~30% of contract price (advance + 20% performance + 10% retention) — large-tier financial exposure.

## Implications for later phases

- **Required-doc checklist key:** No exact match exists. Phase 3 (re-run with formal pack) extends `bms-greenfield` baseline with FDAS + ACS + Networks rows; the engineering specs (ANNEX_C1 + ANNEX_C2) close most "soft gap → assumption" cells.
- **Module catalog:** `_playbook/modules/bms/` (read-only baseline) → cloned into `projects/<this>/_clones/_playbook/modules/fdas/` and `…/acs/` per D-002. Phase 5b instantiates from the clones, using:
  - **FDAS module template parameters** anchored to Notifier NFS2-3030 platform (panel-and-network item, Class A SLC wiring spec, ONYX networking, OnyxWorks workstation software, VeriFire Tools)
  - **ACS module template parameters** anchored to Suprema CS-40 platform (controller, OSDP/Wiegand reader interface, BioStar 2 server software, biometric enrollment device, badge printer)
- **Stage-specific assumptions:** Greenfield baseline. **Coordination-with-other-contractors** is the dominant risk — four-way coordination (us + ROTEM/REC + Civil Contractor + System Contractor REC). The ICD (Interface Coordination Document) is an explicit deliverable per TOR §4.6.
- **Special considerations:**
  - **Brand-locked at panel level** — bid uses Notifier OnyxWorks + Suprema BioStar 2, anchored to ANNEX_D1 + D2 + ANNEX_C1 §1123/§1124. Internal preferred-brand defaults (Siemens etc.) do NOT apply.
  - **No-China rule (TOR §8.10)** — affects supplier selection for L2 switches, UPS, servers, monitor. RFQ template must enforce.
  - **No subcontracting on Electronics** (TOR §8.6) — affects organizational bid (in-house team only) and FAT travel logistics.
  - **FAT abroad** (TOR §8.11) — Notifier USA + Suprema Korea — Q-019/Q-020 on cost burden (bidder or owner).
  - **Site-dev conduit excluded** (TOR §9.1) — major cost-line removed vs typical turnkey.
  - **EMCS exclusion** (locked by D-015) — Phase-5a applicability matrix marks C1 §1125/1126/1127 rows N-A and ANNEX_A 13008/13011A/13011B as reference-only.
  - **Multi-station cable-route reasoning** — Phase 5a `A3-route-lengths.yaml` uses ANNEX_A drawings as primary basis (measure from D-DEP-IE-13002/3/4/5/6/7 + ANNEX_B); typical-range fallback only for the Stations side which doesn't yet have a drawings annex (Q-016).
  - **6-month proposal validity** — supplier RFQ template requires matching validity (Phase 9).