feat: add section_content reference

2026-05-07 11:50:05 -05:00
parent 4e1de19522
commit 4019cb7437
1 changed files with 127 additions and 0 deletions
@@ -0,0 +1,127 @@
 # Section Content Library
 Boilerplate and fill-in patterns for the sections that need to be generated fresh (not lifted from the template). Use these as starting points and customize per project.
 ---
 ## Executive Summary
 **Pattern** (1 paragraph, first section after the title page):
 > This Statement of Work defines the scope, responsibilities, and deliverables for the implementation of a {PROJECT_TYPE(s)} solution for {AGENCY_NAME}, procured through {RESELLER_NAME} and implemented by Message Point Media (MPM). The project encompasses {DISPLAY_COUNT} {DISPLAY_TYPE} at {SITE_COUNT} site(s) / across {BUS_COUNT} vehicles, along with associated professional services, licensing, installation, and support. The reference pricing for this engagement is captured in MPM Quotation(s) {QUOTE_NUMBERS}, dated {QUOTE_DATES}, which are incorporated by reference in Appendix A.
 **Example (StarMETRO Southside):**
 > This Statement of Work defines the scope, responsibilities, and deliverables for the implementation of a combined LCD Wayside and LED Wayside passenger information display solution for the City of Tallahassee (StarMETRO), procured through and implemented by Message Point Media (MPM). The project encompasses 4 EX49KV-Dual outdoor interactive kiosks and 8 LX24R dual-sided LED pendant displays at the Southside Transfer Center, along with associated professional services, MPTV and TransitPoint licensing, custom Vontas API development, and DBE-managed installation. The reference pricing for this engagement is captured in MPM Quotation S00794, dated 11/24/2025, incorporated by reference in Appendix A.
 ---
 ## Project-Specific Assumptions
 Open with this standard preamble:
 > The following assumptions form the basis for this Statement of Work. Material changes to any of these assumptions may trigger a Change Order as described in Section 6. If any of these assumptions are inaccurate as of the signing date, the affected party is responsible for notifying MPM in writing within five (5) business days of SOW execution.
 Then generate project-specific assumptions from the following pools, selecting only those that apply:
 ### Universal assumptions (always include)
 - The End-Client and Reseller will designate primary and secondary points of contact per the Communications Plan within ten (10) business days of project kickoff.
 - All pricing and line items referenced in Quotation {QUOTE_NUMBER} remain in effect through project completion, barring Change Orders executed per Section 6.
 - The End-Client will provide reasonable access to installation locations, personnel, and systems within agreed-upon scheduling windows.
 - The Reseller serves as the primary commercial interface between MPM and the End-Client; all scope changes, financial adjustments, and escalations route through the Reseller unless otherwise agreed in writing.
 - Work outside of published scope constitutes a Change Order regardless of whether it incurs additional cost.
 ### Connectivity assumptions (customize per user answer)
 **If Ethernet/WiFi agency-provided:**
 - The End-Client will provide reliable Ethernet or WiFi internet connectivity with sufficient bandwidth at each display location, configured to permit access to all MPM cloud endpoints required for operation. Connectivity must be verified and operational prior to the installation start date for each site.
 **If Cellular via MPM-supplied modem:**
 - Each display includes an integrated or accompanying cellular modem supplied by MPM. The modem hardware is included in the scope of this project as itemized in Appendix A. Cellular service activation, SIM provisioning, and monthly data plan costs are the responsibility of {DATA_PLAN_OWNER} per the answer confirmed during scope finalization.
 **If Cellular via agency-provided SIM/plan:**
 - The End-Client will provide compatible cellular SIMs and active data plans for each display location. SIMs must be installed and activated prior to the installation start date. MPM's hardware supports standard business tablet data SIMs from any of the three major U.S. carriers; the End-Client is responsible for verifying carrier compatibility and signal strength at each install site.
 ### Installation assumptions (wayside)
 - Site survey findings are assumed accurate as of the survey date. Material changes to site conditions between survey and installation may trigger a Change Order.
 - The End-Client is responsible for ensuring power is provisioned to each display location at the voltage and amperage specified in the installation design document, and that power is energized and verified prior to the installation team's arrival.
 - Mounting surfaces are structurally sound and suitable for the weight and wind-loading characteristics of the specified displays. Structural verification is the responsibility of the End-Client. See Section 1.6.2.
 - Network drops, conduit runs, and any cabling beyond the final display connection point are the End-Client's responsibility unless explicitly itemized in Appendix A.
 ### Installation assumptions (mobile retrofit)
 - The End-Client will make the specified vehicles available at a single staging location during the installation window. Vehicles must be serviceable, powered, and accessible during scheduled install shifts.
 - Bus models in the project are limited to those itemized in Section {BUS_FLEET_SECTION}. Retrofit kits are bus-model-specific; addition of other models requires a Change Order.
 - The installation schedule assumes a typical retrofit time of approximately {HOURS_PER_BUS} labor-hours per vehicle. Buses with non-standard interior configurations or prior retrofits requiring removal may exceed this estimate.
 - The End-Client will provide access to a covered or indoor bay where retrofit work can be safely performed, along with reasonable access to shop power, lighting, and tools during installation shifts.
 ### Pilot installation assumptions (if in scope)
 - The pilot installation consists of {PILOT_COUNT} units installed at {PILOT_SITE/BUS_DESIGNATION}. The pilot serves as a validation of the installation design, mounting approach, content rendering, and connectivity before full rollout.
 - Pilot acceptance is defined as {PILOT_ACCEPTANCE_CRITERIA — typically: 7 consecutive days of stable operation with no critical issues}. Bulk installation begins only after pilot acceptance, unless the parties mutually agree in writing to begin bulk installation in parallel.
 - Issues identified during the pilot may necessitate adjustments to the installation design, mounting hardware, content, or scheduling. Material adjustments will be captured as Change Orders if they affect project cost, timeline, or scope.
 ### Training assumptions
 - Training is delivered via {TRAINING_FORMAT} per the Training Plan developed during the Design and Planning phase.
 - The End-Client will designate appropriate personnel to attend training sessions and ensure those personnel have the prerequisite system access and familiarity with their operational role.
 - Additional training, re-training for new staff, or advanced instruction beyond the scope of this SOW is available under MPM's Support and Maintenance Agreement or via Change Order.
 ### Middleware / API assumptions
 **If TransitPoint licensed:**
 - TransitPoint middleware services are included in this SOW as itemized in Appendix A. These services provide translation and aggregation capabilities for supported data feeds (GTFS / GTFS-RT, etc.). The End-Client will provide credentials, feed URLs, and API access as needed.
 **If native API only:**
 - The project relies solely on native data APIs directly supported by the MP.TV Controller — specifically {NAMED_API}. Middleware services including GTFS / GTFS-RT translation, third-party schedule aggregation, dynamic bay support, and programmatic advertising are NOT included. Should these services be required, MPM will issue a Change Order for the appropriate TransitPoint license and supporting services.
 **If custom development:**
 - Custom development work itemized in Appendix A (specifically {DEV_LINE_ITEM_DESCRIPTION}) delivers {DEV_DELIVERABLE}. Source code and intermediate artifacts remain property of MPM; the End-Client and Reseller receive a non-exclusive license to use the deliverable in connection with the deployed system. Scope expansion requires a Change Order.
 ---
 ## Project-Specific Exclusions
 Open with:
 > The following items are explicitly NOT included in the scope of this Statement of Work. This list is illustrative of common points of confusion and is not exhaustive. If an item is not explicitly listed as in-scope in this SOW or itemized in Appendix A, it should be assumed to be out of scope. Requests for additional scope will be handled via the Change Order process in Section 6.
 Then itemize:
 - **Permitting and inspections.** MPM is not a licensed general or specialty contractor. All local permits, inspections, and associated fees are the responsibility of the End-Client.
 - **Professional structural and civil engineering.** Engineering review, stamping, or sign-off of mounting, structural supports, foundations, or electrical service is the responsibility of the End-Client unless explicitly quoted in Appendix A.
 - **ADA compliance certification.** MPM provides general guidance based on published ADA standards but does not certify compliance. Compliance determination is the responsibility of the End-Client.
 - **Network infrastructure.** Network provisioning beyond the final drop at each display location is the responsibility of the End-Client.
 - **Cellular data plans and service.** {If cellular + agency-paid: confirmed out of scope for MPM. If cellular + MPM-paid: state which term/duration is included and that renewal is separate.}
 - **Middleware not listed.** Middleware data services not itemized in Appendix A are out of scope.
 - **Content creation beyond design services.** Day-to-day content creation and ongoing editorial work are the responsibility of the End-Client or Reseller.
 - **Ongoing support, maintenance, and retraining.** These require a separate Support and Maintenance Agreement.
 - **Removal and disposal of existing equipment.** Unless explicitly itemized in Appendix A.
 - **Third-party integrations not specified.** Integration with systems not named in this SOW is out of scope.
 - **Any item not itemized in the referenced Quotation(s).**
 ---
 ## Hardware and Services Inventory
 Generate a table directly from the pricing file parse:
 | Category | Item | Qty | Notes |
 |---|---|---|---|
 | Hardware — Displays | {Product description from quote} | {qty} | {model codes} |
 | Hardware — Mounting | ... | ... | |
 | Hardware — Accessories | ... | ... | |
 | Professional Services — Project Management | Project Management (Tier N) | {hours} hrs | |
 | Professional Services — Design | ... | ... | |
 | Professional Services — Installation Labor | ... | ... | |
 | Professional Services — Training | ... | ... | |
 | Professional Services — Travel | Trip charges | {units} | Up to 3 days on-site per trip |
 | Installation — DBE | ... | ... | |
 | Licensing — Annual | MPTV Professional License | {qty} | Annual recurring |
 | Licensing — Annual | TransitPoint | {qty} | If applicable |
 | Warranty | {1/3/5-year term} | 1 | Factory warranty {included/extended} |
 | Shipping | Estimated outbound | 1 | Budgetary; actual on final invoice |
 Keep categories that appear; drop categories that don't. Total at the bottom should match the quote grand total.