Advertisim Product Management

Jetzt loslegen. Gratis!
oder registrieren mit Ihrer E-Mail-Adresse
Advertisim Product Management von Mind Map: Advertisim Product Management

1. Insight

1.1. Market research

1.1.1. Nayar observed an increase of the MS in Spain and all over the world

1.1.2. Adveritisim

1.1.2.1. Schindler is already Nayar client and has 1.300 Advertisim displays only in Spain

1.1.2.1.1. Advertisim sales in Spain are growing

1.1.2.1.2. Price

1.1.3. Market trends

1.1.3.1. OTIS is opening the market by installing MS masivelly

1.1.4. Nayar is being responsive to his bigest customer needs, Schindler

1.1.4.1. Schindler is one of the sectors leader with presence all over the world

1.1.4.2. Schindler has an own display solutions but doesn't fit the market

1.1.4.3. Reach TECH standards

1.1.4.3.1. High performance HW

1.1.4.3.2. Operating System

1.1.4.3.3. Player Software

1.1.4.4. Need to reach a competitive price for the display

1.1.4.4.1. Masive selling

1.1.4.5. Nayar to complement their DMS product portfolio

1.1.4.6. A smaller display (10" or 15")

1.1.4.7. Add value to the customer by showing the elevator information (Nayar technology) + Infotaiment

1.1.4.8. Scope for 2024: distribute the product globally starting by EI

1.1.4.8.1. How much?

1.1.4.8.2. SCH vs MB? (50%)

1.1.4.9. EI: Need to subtitute the displays in OTIS elevator captation

1.1.4.10. New HW maintaining Schindler actual existing player software and all integrations (CMS & Ecosystem)

1.2. Customer research

1.2.1. Monthly platform and SIM cost is a high sales barrier

1.2.2. Types of customers

1.2.2.1. Elevator manufacturer, installator or maintainer

1.2.2.1.1. In this case Nayar will focus in Schindler as the main customer

1.2.2.2. Final consumer

1.2.2.2.1. Corporate consumer

1.3. Competitive research

1.3.1. OTIS

1.3.1.1. Hardware

1.3.1.1.1. Similiar HW as Advertisim

1.3.1.1.2. 7" / 10" / 15"

1.3.1.2. Software

1.3.1.2.1. Mainly used to show news, weather, data and time

1.3.1.2.2. Not used to show adverts, information, or branding content

1.3.1.2.3. Camera and integration with the TA for emergency videocalls

1.3.1.2.4. Non compatibility with other lift brands

1.3.1.3. Pricing

1.3.1.3.1. Lower price than Nayars

1.3.1.4. Sales strategy

1.3.1.4.1. Include their displays as an added value for their lifts

1.4. Product performance (Need to complete with specific data)

1.4.1. Revenue

1.4.1.1. Revenue in Spain

1.4.1.2. Aprox price x aprox customers

1.4.2. Customer numbers

1.4.2.1. How much SCH EI?

1.4.2.1.1. How much countries?

2. Analysis

2.1. Segmentation

2.1.1. Types of customers

2.1.1.1. Elevator manufacturer, installator or maintainer

2.1.1.1.1. In this case Nayar will focus in Schindler as the main customer

2.1.1.2. Final consumer

2.1.1.2.1. Corporate consumer

2.1.1.2.2. Residential customer

2.1.2. This product will be used for all the customers or only for Schindler?

2.2. Propositions

2.2.1. Customer Value Proposition adapted for Schindler

2.2.1.1. 10 years of expertise in the MS market

2.2.1.2. High TECH standards

2.2.1.3. Show elevator information

2.2.1.3.1. Compatibility with multibrand controllers

2.2.1.4. High quality multimedia Advertisiments

2.2.1.4.1. Higher return for the investment

2.2.1.4.2. Allow to offer a lower price

2.2.1.5. Tailored HW and SW

2.2.1.5.1. HW

2.2.1.5.2. SW

2.3. Positioning

2.3.1. Based in product atributes

2.3.1.1. High Tech

2.3.1.2. Combine elvator information + Advertisement

2.3.2. Based in the value offered to the facility

2.3.2.1. Modernization

2.3.2.2. High standing

2.3.2.3. User Experience

2.3.2.4. Branding

2.4. Business cases (make as phase 2, after completing all the map)

2.4.1. Product description

2.4.2. Strategy

2.4.3. Market Analysis

2.4.4. Customer Analysis

2.4.5. Financial Analysis

2.4.6. Plans

3. Direction

3.1. Product & portfolio strategy

3.1.1. Current Nayar portfolio

3.1.1.1. AIO 10"

3.1.1.1.1. E

3.1.1.1.2. S

3.1.1.1.3. I

3.1.1.2. AIO 15"

3.1.1.2.1. E

3.1.1.2.2. S

3.1.1.3. TCU 10E

3.1.1.4. KIT OTIS

3.1.1.4.1. TCU 10K

3.1.1.4.2. TCU 10B

3.1.2. Nayar portfolio atributes

3.1.2.1. TECH standards

3.1.2.1.1. High performance HW

3.1.2.1.2. Operating System

3.1.2.1.3. Player Software

3.1.3. Potfolio oportunities

3.1.3.1. Fit our portfolio to a main player in elevator market

3.1.3.2. Reach market high tech standards

3.1.3.3. More competitive price

3.1.3.4. Improve Plug&Play

3.1.3.4.1. High installation and set up costs

3.1.4. Company strategy FIT

3.1.4.1. More profitability

3.1.4.2. Plug&play product

3.1.4.3. Growth

3.1.4.3.1. Internationalization

3.2. Vision & evangelizing (SKIP)

3.3. Roadmaps

3.3.1. 2024

3.3.1.1. Develop solution with minimum technical requirements

3.3.1.1.1. EI

3.3.2. 2025

3.3.2.1. Ready to scale

3.3.2.1.1. Integration in COP NI & EI

3.3.2.1.2. Software enhancements

3.3.2.1.3. Remote access

3.3.3. 2026

3.3.3.1. Fully integrated solution

3.3.3.1.1. Global new products

3.4. Pricing

3.4.1. Lower manufacturing cost

3.4.2. Nayar gross margin method

3.4.3. Compite with OTIS price

3.4.3.1. Emulate their competitive strategy

3.4.3.1.1. They give the displays with 100% discount as an added value in their installation

4. Inbound Act.

4.1. Discover & design

4.2. Requirements

4.2.1. Hardware

4.2.1.1. H-01 Chip

4.2.1.1.1. Proposal RK3399 & RK3588

4.2.1.2. H-02 RAM

4.2.1.2.1. 4 GB RAM for RK3399 and 8GB for RK3588

4.2.1.3. H-03 Storage

4.2.1.3.1. Mass storage also should be from a reliable source for eMMC or SSD

4.2.1.4. H-04 Cooling

4.2.1.4.1. Sufficient thermal solution (cooling) considering the overall solution

4.2.2. Operating System

4.2.2.1. O-01 Version

4.2.2.1.1. A minimum of Android 11 is required

4.2.2.2. O-02 Access Root

4.2.2.2.1. Root access is recommended to avail the full feature set

4.2.2.3. O-03 Browser WebView

4.2.2.3.1. WebView (com.google.android.webview) must be implemented out of the box and must be updateable

4.2.2.4. O-04 Updates

4.2.2.4.1. Over-the-air (OTA) updates should be available by default

4.2.2.5. O-05 Security

4.2.2.5.1. OTA updates must be provided based on the newest secu- rity batches released by AOSP (Google) on a regular basis

4.2.3. Player Software

4.2.3.1. P-01 Player provisioning with AheadCMS

4.2.3.2. P-02 Playback scheduling with time, date, and location

4.2.3.3. P-03 Seamless transitions between spots

4.2.3.4. P-04 Player monitoring with logs

4.2.3.5. P-05 Automatic player software updates from server

4.2.3.6. P-06 Configurable playback reports

4.2.3.7. P-07 Video playback

4.2.3.8. P-08 Image playback

4.2.3.9. P-09 Website playback

4.3. Project & partner management

4.3.1. Product Management

4.3.1.1. Create an Advertisim team

4.3.1.1.1. Partner Management

4.3.1.1.2. Suppliers management

4.3.2. Project Management

4.3.2.1. Nayar project management team

4.4. Operational readiness & trials

4.4.1. Operational preparation

4.4.1.1. Inbound logistics

4.4.1.1.1. Spare parts suppliers

4.4.1.2. Operations

4.4.1.2.1. Sparte parts quality control

4.4.1.2.2. Spare parts preparation

4.4.1.2.3. External HW manufacturer

4.4.1.2.4. Stock management

4.4.1.3. Outbound logistics

4.4.1.3.1. Shipment systems for Schindler

4.4.1.4. Marketing and sales

4.4.1.4.1. Sales force technical training

4.4.1.4.2. Sales force samples and tools

4.4.1.4.3. Sales strategy

4.4.1.5. Support

4.4.1.5.1. Team training

4.4.1.5.2. Technical documentation

4.4.1.5.3. Define support processes

4.4.1.5.4. Troubleshooting

5. Outbound Act.

5.1. Launch

5.1.1. Nayar & Schindler

5.2. Product promotion

5.2.1. Nayar & Schindler

5.3. Sales & marketing content

5.3.1. Nayar & Schindler

5.4. Sales support

5.4.1. Nayar & Schindler