This document specifies the requirements for indigo-bareilly, a campus navigation system for the RBMI Group of Institution, Bareilly branch. The system is built to run on a robot that assists visitors inside the college: a visitor physically present at the Bareilly campus who does not know the layout states or selects where they want to go, and the system returns a clear route from their current position to that destination.
The product intent is a wayfinding instrument, not a marketing site. It must be understood in three seconds from two metres away, work for a first-time visitor who may be a parent, a prospective student, an external examiner, or a delivery person, and it must be as fast as possible with a beautiful UI. Scope is limited to the RBMI Group of Institution Bareilly branch campus.
indigo-bareilly is a first-party web application delivered as the interface of a visitor-assistance robot at the RBMI Group of Institution Bareilly branch. It presents a schematic campus plan of the Bareilly branch, lets a visitor choose or search a destination within that campus, and returns a step-by-step route from the visitor's current position to that destination.
Actors. The accepted active-human catalog is closed: Campus Visitor and Robot Navigation Assistant. The Campus Visitor is the person physically present at the campus who needs to reach a specific location. The Robot Navigation Assistant is the in-product role that serves the visitor at the robot — presenting the campus map, accepting the destination, and returning route guidance. No other personas are introduced.
Accepted behavior. The system provides a navigation map for the RBMI Group of Institution Bareilly branch; it is delivered for use on a robot that helps visitors navigate inside the college; it must be fast to load and respond; and it must have a beautiful UI.
Ownership. All three accepted destinations — Campus Map, Destinations, and Route — are application-owned custom pages with no access requirement. The robot is the delivery context for the interface; the interface itself is first-party.
Exclusions. No campus outside the RBMI Group of Institution Bareilly branch is in scope. No account, login, or identity management is introduced. No adjacent capabilities (timetabling, admissions, fee payment, staff directories beyond wayfinding labels, transport booking) are part of this product.
The product is a kiosk-style wayfinding surface mounted on a robot that moves through the RBMI Group of Institution Bareilly branch. It is anonymous by design: a visitor walks up, sees the campus plan, says or selects where they want to go, and receives a route. There is no sign-in, no profile, and no persistent visitor account, because the accepted journeys do not require a visitor to privately own or resume durable state — each visit is a self-contained wayfinding session.
The delivery boundary is the Bareilly branch campus only. The map, the destination catalog, and the routes all describe that one campus. Nothing in this document authorizes a multi-campus or inter-city navigation product, and nothing authorizes a mobile app, a public website, or a staff-facing administration console.
The current horizon covers the three accepted destinations and the visitor journeys they serve. Future ideas (multi-campus expansion, indoor positioning hardware integration, voice-only interaction, accessibility routing preferences) are explicitly out of the current scope and are recorded only in the future section.
Not applicable. No reference directive in the planning scope declares content_source, so no source content inventory is produced.
The page contract is versioned and final. The three pages below are copied exactly, in order, with their access and identity ownership unchanged.
Each requirement below is a distinct story point with provenance, lifecycle facts, and observable acceptance.
FR-1 — Campus navigation map for the Bareilly branch (explicit) As a Campus Visitor, I should see a navigation map of the RBMI Group of Institution Bareilly branch so that I can understand the campus layout.
FR-2 — Robot-delivered visitor assistance (explicit) As a Robot Navigation Assistant, I should present the campus navigation map and route guidance on the robot so that a visitor at the robot can be helped without staff assistance.
FR-3 — Fast load and response (explicit) As a Campus Visitor, I should get the map, the destination list, and the route quickly so that I am not kept waiting at the robot.
FR-4 — Beautiful, legible UI (explicit) As a Campus Visitor, I should see a clear, well-designed interface so that I can read it from a standing distance and trust it.
FR-5 — Browse the campus plan (required_inference) As a Campus Visitor, I should browse the schematic plan of the Bareilly branch so that I can orient myself before choosing a destination.
FR-6 — Search for a place (required_inference) As a Campus Visitor, I should search for a room, department, or person so that I can find a destination I cannot locate on the plan.
FR-7 — Filter destinations by category (required_inference) As a Campus Visitor, I should filter destinations by category so that I can narrow the list to the kind of place I need.
FR-8 — Select a destination (required_inference) As a Campus Visitor, I should select a destination from the list or the plan so that the system knows where I want to go.
FR-9 — Receive a route from current position to destination (required_inference) As a Campus Visitor, I should receive a route from my current position to the chosen destination so that I can walk there.
FR-10 — Follow step-by-step route instructions (required_inference) As a Campus Visitor, I should follow numbered step instructions so that I can reach the destination without asking staff.
FR-11 — Start over with a new destination (required_inference) As a Campus Visitor, I should be able to start over with a new destination so that I can make a second trip or correct a wrong choice.
FR-12 — Robot Navigation Assistant presents the map and route (required_inference) As a Robot Navigation Assistant, I should present the campus map, accept the visitor's destination, and return the route so that the visitor reaches the intended location.
Product context. A person physically present at the RBMI Group of Institution Bareilly branch who does not know the campus layout. They may be a parent, a prospective student, an external examiner, or a delivery person. They are often in a hurry, often reading Hindi-accented English, and sometimes have low literacy in wayfinding systems. They are standing in front of a robot kiosk in a lobby or corridor.
Primary goal. Reach a specific campus destination — a department, an office, a facility — without asking staff for help.
Distinct accepted responsibilities. State or select where they want to go; read the campus plan to orient themselves; choose a destination from the list or the plan; follow the numbered route steps to arrive.
Relevant inputs or decisions. The destination they need; whether to search by name or browse by category; whether to accept the shown route or start over with a different destination.
Interactions with other accepted participants. The Campus Visitor interacts with the Robot Navigation Assistant, which presents the map and returns the route. The visitor does not interact with any other human role in this product.
Observable success. The visitor arrives at the intended campus location without staff help, having followed the route from the robot.
What makes this role different. The Campus Visitor is the only human actor who initiates a wayfinding request and physically walks the route. Their work is defined by a single, time-pressured decision (where do I want to go?) followed by physical execution of the returned steps.
Product context. The in-product role that serves the visitor at the robot. It is the surface through which the visitor sees the campus map, states a destination, and receives route guidance. It is not a separate human operator; it is the robot's presentation role within the product.
Primary goal. A visitor who reaches the intended campus location without staff help.
Distinct accepted responsibilities. Present the campus navigation map; accept the visitor's destination; return the route guidance the visitor follows; keep the interface fast and legible at standing distance.
Relevant inputs or decisions. The visitor's stated or selected destination; the current position on the campus plan; the route computed to that destination.
Interactions with other accepted participants. The Robot Navigation Assistant serves the Campus Visitor directly and is the only participant on the robot side of the interaction.
Observable success. The visitor completes the journey from the robot to the chosen destination using the presented route.
What makes this role different. The Robot Navigation Assistant does not choose a destination and does not walk the route. Its work is presentation and handoff: it must make the map, the destination choice, and the route legible and fast enough that a first-time visitor can act on them in seconds.
The creative direction is authoritative for this section. The muse is Erik Spiekermann; the headline idea is typographic infrastructure for a campus that must be walkable at a glance. The register is reassurance and legibility, not delight or luxury: the product is a wayfinding instrument, like a transit map or an airport sign, understood in three seconds from two metres away.
| Role | Hex | Use |
|---|---|---|
| Background | #F4F1EA | Warm paper ground; the plan surface |
| Surface | #FFFFFF | Pure white panels; the rail and cards |
| Text | #17181A | Ink for all type |
| Primary | #0F2A5C | Deep transit blue: headers, rules, campus boundary, primary route line, left rail |
| Accent | #E2231A | Signal red, reserved ONLY for "you are here", the destination pin, and the active route segment |
| Muted | #7A7369 | Warm grey for secondary metadata: floor numbers, room codes, distances |
| Category — Academic | #E8A33D | Mustard; 3px map strokes and 8px chip dots only, never fills |
| Category — Facilities | #1F7A6B | Teal; 3px map strokes and 8px chip dots only, never fills |
| Hairline rule | #D8D2C6 | 1px rules dividing every block |
No gradients anywhere. All colour is flat and printed. The generic indigo/blue-on-white SaaS template is forbidden for this project.
clamp(40px, 7vw, 96px).Rectilinear and honest. 2px radius on buttons and chips, 4px on panels — barely rounded, like printed signage with a trimmed corner. 1px hairline rules in #D8D2C6 divide every block; 3px rules in transit blue mark section boundaries. Map rooms are flat rectangles with 1px ink outlines and no shadows. One deliberate exception: the "you are here" pin is a filled red circle with a 2px white ring and a 12px pulsing halo — the only circular, the only animated, the only soft form in the whole interface.
A 12-column grid with a hard left rail.
No photography. The imagery IS the map: flat vector floor plans, transit-style route lines with 45-degree rounded corners at turns, numbered step markers as filled blue squares with white numerals, and a small set of 24px pictograms drawn on a 2px stroke grid (staircase, lift, washroom, canteen, library, auditorium, parking, reception). One decorative element only: a faint 8% opacity blueprint grid (32px squares) behind the campus plan.
The public entry is a working instrument, not a marketing hero. It looks like the control surface of a wayfinding kiosk, because that is what it is.
#0F2A5C) running full viewport height. At the top, "RBMI GROUP OF INSTITUTIONS" set in 14px small-caps white letterspaced type. Below it, the oversized question "Where do you want to go?" in Fira Sans 700 at clamp(40px, 5vw, 72px) white. Directly beneath it, a white search field with a red 2px left edge and the placeholder "Type a room, department or person".#F4F1EA with the 8% blueprint grid, the red "you are here" pin already pulsing near the bottom-centre entrance, and eight category chips (Academic, Administration, Library, Hostel, Canteen, Sports, Medical, Parking) laid as a horizontal row along the bottom edge of the plan, each with a coloured dot.The signature moves that carry the concept:
#E8A33D), Administration (transit blue #0F2A5C), Facilities (teal #1F7A6B) appear as 3px strokes on the map and 8px dots on chips, so a visitor learns the campus by colour the way they learn a subway system.Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
prefers-reduced-motion: the route appears fully drawn, the pin halo is static at 0.35 opacity, and viewport snaps become instant cuts.NFR-1 — Performance (explicit) The interface must be as fast as possible. Page loads, search keystrokes, category filters, and route computations must respond without perceptible delay. Rationale: the visitor is standing at a robot and must not be kept waiting.
NFR-2 — Legibility at distance (explicit, from creative direction) Type must be readable from two metres away. No text a visitor must read may be set below 14px. Rationale: the product is a wayfinding instrument used standing up.
NFR-3 — Campus scope (explicit) The map, destination catalog, and routes cover only the RBMI Group of Institution Bareilly branch campus. Rationale: explicit hard constraint in the authoritative source.
NFR-4 — Robot delivery context (explicit) The interface is delivered for use on a robot that assists visitors navigating inside the college. Rationale: explicit hard constraint in the authoritative source.
NFR-5 — Anonymous access (required_inference) All three pages are reachable without sign-in. No account, profile, or identity management is introduced. Rationale: the accepted journeys are self-contained wayfinding sessions that do not require durable visitor state.
NFR-6 — Responsive integrity (from creative direction) Readable text and needed content stay whole at 375px, 768px, and 1280px. Headlines, wordmarks, labels, numbers, cards, and controls stay entirely inside the viewport and their container, wrapping or scaling to fit. No other element covers any part of them. Crops, bleeds, and off-edge placement are for decoration only. Rationale: the direction's readable-text rule.
NFR-7 — Reduced motion (from creative direction)
Under prefers-reduced-motion, the route appears fully drawn, the pin halo is static at 0.35 opacity, and viewport snaps become instant cuts. Rationale: accessibility and the direction's motion contract.
NFR-8 — No photography, no gradients (from creative direction) No photographic campus aerial shots or stock student imagery. No gradients anywhere. Rationale: the direction's imagery and colour rules.

RBMI GROUP OF INSTITUTIONS
Showing 10 of 10 places
Campus plan
RBMI Bareilly · campus plan
Room records are available, but their coordinates are not verified building locations. To avoid misleading visitors, the campus map is not drawn until an authoritative Bareilly site plan is supplied.
10 room records available · placement unverified

RBMI GROUP OF INSTITUTIONS
Showing 10 of 10 places
Campus plan
RBMI Bareilly · campus plan
Room records are available, but their coordinates are not verified building locations. To avoid misleading visitors, the campus map is not drawn until an authoritative Bareilly site plan is supplied.
10 room records available · placement unverified
No comments yet. Be the first!