[000]
[001]~ Addresses and contacts
[002]~ References and previous emails
[003]~ Start of the letter
[004]~ Pod
[005]~ Fighter to deploy
[006]~ Manned helicopter for UAV helicopter
[007]~ UAV helicopter engine
[008]~ Design
[009]~ Hardware
[010]~ Functions
[011]~ Data
[012]~ Context
[013]~ Network
[014]~ Software
[015]~ Power
[016]~ Communications
[017]~ Money & Cost
[018]~ Versions
[019]~ Standards
[020]~ Markets
[021]~ Benefits
[022]~ Reliability
[023]~ Safety
[024]~ Innovation,Creativity&Exploration
[025]~ partner profile
[026]~ To Do Together
[027]~ Sharing Markets
[028]~ Free
[029]~ Free
[030]~ Free
[031]~ Free
[032]~ Free
[033]~ Ending































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[001] ~ Addresses and contacts

LETTER:
To: your_company
Attn: your_person_title, your_person
From: Mr Ronnie Valkky, CEO, Small & Smart Inc

Web pages:
your_company
Small & Smart Inc (http://www.dragonxi.com)

E-mail:
your_person's email: your_person@your_company
Ronnie Valkky email: ceo@yourdragonxi.com

Addresses:
Small & Smart Inc
484B Washington Street Suite 326, Monterey CA 93940 United States

your_company_address



select: ~[Σ] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[002] ~ References and previous emails

Ref1:

Ref2:

Ref3:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[003] ~ Start of the letter

Dear your_person,

This letter is continuation to emails from your_person

We feel honoured to contact person having your_person_background

Please, consider the following proposals more as a starting point in a dialogue, which we hope to lead to a long-term
collaboration between S&S and your_company:


Our current UAV helicopter concept

Xi helicopter is designed to be rapidly deployable to target area in several ways
A manned fighter may deploy the Xi copter to remote theater and Xi copter should be capable to hatch in the air from the pod.
A manned helicopter's role is to deploy autonomous & unmanned Base4Xi to manage and support Xi copters in target theater.

Networked environment is essential for network-centric operations:
~ MILITARY NET
~ PATROL NET
~ BUSINESS NET

Xi copter drops wireless sensors Sensor4Xi and collects sensored data to autonomous Base4Xi which provides shelter and resources such as fuel to Xi copter:
~ Military
~ Patrol
~ Business

Above concept of rapidly deployable Xi copter for network-centric autonomous operations in remote theaters is the most challenging.
Xi copter can be deployed more traditionally as well as operated near a manned base with it's own sensors, if required.



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[004] ~ Collaboration scenario #1: Pod

Developing together the pod

Concept: pod embeds UAV helicopter and it can be used to drop UAV helicopter from a manned fighter or manned helicopter.

Details:
- view Network Design
- read Xi copter deployment options Rapidly Deployable

Challenges:
1) Xi copter should fit inside pod
2) Pod must be reliable so that hatching of Xi copter will succeed
3) There isn't any standard size for pods

Details:
a) Special Purpose Pod & Xi copter Size

Questions:
Q1_Pod: could your_company design the pod ?
Q2_Pod: if not, are there any pod suppliers in your_country to be collaborated with ?
Q3_Pod: how could the pod and Xi copter hatching be tested:
_Q3_1: with third_party fighter ?
_Q3_2: with your_company helicopter ?
_Q3_3: in special UAV test laboratory; will your_company develop these kind of UAV test laboratories ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[005] ~ Collaboration scenario #2: Fighter

Developing fighter related hardware and solutions


Challenges for Xi copter: fighter's take off, g-forces during manoeuvres, hatching in the air

Questions:
Q1_Fighter: Are your_company's test facilities available ?
Q2_Fighter: Is it possible to collaborate with third_party companies?
Q3_Fighter: Are there specifications such as those of f-35 (http://www.globalsecurity.org/military/systems/aircraft/f-35-specs.htm), available about third_party_fighter ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[006] ~ Collaboration scenario #3: Manned helicopter for UAV helicopter

Developing a manned helicopter specialized to develop, test, tailor, deploy and support UAV helicopters in networked environments

S&S:
~ one deployment method of Xi copter is a manned helicopter, see Rapidly Deployable
~ a manned helicopter is designed to deploy unmanned, autonomous Base4Xi to target area to support Xi copter by providing more fuel and shelter
~ Xi copter has been designed to generate more sales and new business also to manned helicopters such as the ones your_company manufacturers
~ a your_company manufactured helicopter could be developed together to be used for development, testing and programming (tailoring) UAV helicopters in different countries
~ algoritms could be developed together (for navigation and obstacle detection for example) to be tailored to different UAV helicopters instead of reinventing the wheel
Links and details:
1. MILITARY NET
2. PATROL NET
3. BUSINESS NET

Case 1: a manned your_company_helicopter can't operate long times in the same area without disturbing the area
Solution: A swarm of Xi copters is dropped by a manned your_company_helicopter over the target area.
~ Xi copters could survey that area in more detail while the manned your_company_helicopter would continue flying to other targets.
~ Clients would save money and be able to optimize resources because pilots and manned your_company_helicopters would not be used to survey small areas

Case 2: a manned your_company_helicopter could deploy Xi copter in a special pod tailored to manned helicopters
~ This would increase the sales of manned your_company_helicopters
~ A special built pod is normally not needed but the same pod could be used as for fighters

Case 3: a manned your_company_helicopter could deploy Base4Xi as well as to send service persons to maintain Xi copters
~ A special your_company_helicopter could be used to deploy Base4Xi in which case Base4Xi would be embedded in your_company_helicopter's fuselage
~ Base4Xi could be customized to certain manned your_company_helicopters which would help marketing Xi copters

Questions added to the above ones:
Q1_Manned_Helicopter_For_UAV: a gas company as client/partner to develop UAVs for gas industry ?
Q2_Manned_Helicopter_For_UAV: an oil company as client/partner to develop UAVs for oil industry ?
Q3_Manned_Helicopter_For_UAV: possibility to upgrade manned helicopter to support UAV helicopters in networked environments ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[007] ~ Collaboration scenario #4: UAV helicopter engine

Integrating engine developed by a third party and/or your_company
A S&S's partner in United States, for example, could develop engines for business model Xi copter.
Patrol and military markets may require engines developed in certain countries.
Fuel and power options offer possibilities to develop different kind of engines depending on appliations and clients.

Technical issues:

1. engine itself
~ fitting engine into the envilope defined and leaving space for other components such as electronics and cameras
~ designing space inside 7.6 ft length and 1.1 ft diameter for the engine to occupy
~ reliability to guarantee hatching in the air and autonomous operations at remote theaters

2. ancillary systems
~ cooling, exhaust, and whether or what kind of re-drive (belt or gear) is anticipated
~ if weight is an issue, going direct drive
~ operating profile of military/patrol/business
~ two/three rotor engine
~ engine has to stand temperature extremes, vibration inputs, g-forces, thrembling
~ electronic control of engine and diagnostics for development, test and maintenance

3. deployment of UAV helicopter with a fighter
~ UAV helicopter must take vectored thrust and sudden strong g forces (from any angle, if possible)
~ engine has to have full-authority digital electronic control (FADEC)
~ data flow via ARINC429 or RS232/422 between fighter and UAV helicopter
~ it should be possible for a fighter to carry engine around at high altitude in relatively level flight without being used
~ oil spill out of the engine must be prevented to contaminate the gas path when the carrying aircraft is doing a lot of aerobatics
~ handling carrier landings which can entail high G loads (in this case a fighter is returning with UAV copter i.e. it has not dropped pod)

Manufacturing issue - designing by taking manufacturing into account:
1. small parts
2. fewer moving parts
3. parts being available common across all sizes (single rotors, twin rotors, tri-rotors, and/or quad-rotors)
4. reliability: guaranteed start” engine, as long as proper charge (battery), fuel, oil, and air are available in the required quantities

Commercial issues:
~ Business Plan
~ Branding

Questions:
Q1_Engine: Oil industry UAV engines ?
Q2_Engine: Gas industry UAV engines ?
Q3_Engine: Developing sales channels where the end user, oil/gas company is the customer and distributor ?
Q4_Engine: "Off the shelf" engines with minimal modification for military, patrol and business ?
Q5_Engine: Sourcing the production globally, if required ?
Q6_Engine: Is it ok to have engine designed in United States ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[008] ~ Collaboration scenario #5: Design

Detailing the current design of Xi copter & designing together new UAV helicopters

Details:
~ Xi4M
~ Xi4P
~ Xi4B
~ Zeta series Helicopter Xi Design

Opportunities for collaboration:
~ space needed for pilots in manned helicopters can be used for electronics, sensors and cameras in UAV helicopter as done when designing Xi copter
~ design of Xi copter already uses some of the latest science, engineering, hardware and software available, but more opportunies are available
~ proper test facilities are missing for designers to test UAV concept designs and prototypes, professional level studios, building and facilities are needed

About design of Xi copter at Zeta series Helicopter Xi Design specially note:
~ Rapidly Deployable
~ Shape: designed to fit
~ Embeddable inside Bomb,Missile,Torpedo
~ Foldable Blades
~ Hatching
~ Special Purpose Pod & Xi copter Size
~ Refuelling

Read Benefits of Xi copter
~ Xi copter is capable to carry and drop sensors to target area.
~ Xi copter has extensive communication abilities designed for network centric operations.
~ Xi copter is designed to be rapidly deployable to military missions.
~ Several Xi copters can be rapidly deploeyed to target area packed in Smart Pods/Magazines.
~ Xi copter offers wireless connectivity to other Freedom Devices.
~ Xi copter has no unrealible and extra devices,for example, LEDs are being used instead of displays.
~ Xi copter has been designed to fit inside a compact, easily transportable and storable pod

Questions:
Q1_Design: is Inventor by Autodesk (http://usa.autodesk.com) , Solidworks, Rhino 3D (http://www.rhino3d.com) or similar software in use by your_company ?
Q2_Design: does your_company plan to design everything itself or are there collaboration opportunities in design ?
Q3_Design: how does your_company plan to test UAV helicopter designs; special buildings, air space available near your_city ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[009] ~ Collaboration scenario #6: Hardware

Both developing together and using off-the-self commercial hardware

Details: Zeta series Helicopter Xi Hardware

Questions:

Q1_Camera: are off the self cameras available in your_country or is a third_party necessary ?
~ Xi copter is now designed to have three (3) video cameras and one (1) still camera, but these are for ISR purposes
~ If cameras would be used for navigation and to avoid obstacles Xi copter would need
~ one (1) camera pointing forward and one (1) camera each side to measure optical flow and determine distances

Q2_Sensors: what kind of helicopter sensors are available in your_country ?
~ Epsilon Series

Q3_Microprocessors: any available in your_country & would your_company use ones from third parties?

Q4_DSP Processors: any available in your_country & would your_company use ones from third parties?

Q5_Other Hardware: any special hardware such as navigation hardware available in your_country & would your_company use ones from third parties?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[010] ~ Collaboration scenario #7: Functions

Developing together autonomous and unmanned functions of UAV helicopters

Xi4M has been designed specially for ISR, intelligence, reconnoitering, surveying
Hatching in the air, networking, dropping sensors, sheltering at Base4Xi, collaborating and biomimicing are special function of Xi copter
Common UAV functions include uploading, downloading, managing devices, flying, communicating, processing, handling exceptions, start, stop, erase

Details: Zeta series Helicopter Xi Functions

Opportunity:
~ utilize common functions and tailor them to different UAV helicopters
~ develop functions to oil, gas and energy industries collaborating with companies such as client_gas_companyand client_oil_company, for example
~ explore new functions for UAV helicopters and develop industry standards which would help UAV development community

Questions:

Q1_Functions: main functions your_company has decided & is planning for UAV helicopters?
Q2_Functions: what functions of UAV helicopter your_company regard special ones and is interested to develop together ?
Q3_Functions: what functions your_company regard common and shareable between UAV helicopters ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[011] ~ Collaboration scenario #8: Data

Developing together data

Opportunities:
~ the value and benefits UAV helicopters provide to clients are often based on data UAV helicopter can provide
~ Xi copter collects data from sensors it drops and from it's own sensors & cameras and downloads data to Base4Xi for processing
~ new data format such as XML and RDF combined to Semantic Web OWL open markets to sell data UAV helicopters can collect

Details:
~ Zeta series Helicopter Xi Data

Questions:
Q1_Data: XML, RDF or other data standards planned by your_company ?
Q2_Data: your_company's opinion about Sematic Web and OWL ?
Q3_Data: any specific data your_company thinks UAV helicopters should collect ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[012] ~ Collaboration scenario #9: Context

Exploring and developing internationally context to UAV helicopters

Details: Zeta series Helicopter Xi Context

Questions:
Q1_Context: a gas company as partner ?
Q2_Context: an oil_company as partner ?
Q3_Context: your_company manned helicopter to deploy Xi copter

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[013] ~ Collaboration scenario #10: Network

Developing together UAV helicopters capable to operate in modern networks

Details: Zeta series Helicopter Xi Network

Questions:
Q1_Network: GPS ?
Q2_Network: Galileo ?
Q3_Network: NCOIC (http://www.ncoic.org) or your_company's plans to join similar organizations ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[014] ~ Collaboration scenario #11: Software

Developing together and share UAV helicopter software and ontologies

Details: Zeta series Helicopter Xi Software

Not only have above Xi copter helicopters common software but they also may embed software developed to other UAV helicopters and tailored to Xi copter.
S&S is developing open software and is a member of the OBSAI (http://www.obsai.org/), which is for open mobile base station architecture
Software is an essential part of Xi copter and S&S is committeed to develop software to Xi and other devices such as Base4Xi and Sensor4Xis connected to Xi copter

Questions:

Q1_Software: what software algoritms your_company plans to develop and is fuzzy logic being examined ?
Q2_Software: operating systems your_company is going to use ?
Q3_Software: ontologies and reasoners your_company will use ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[015] ~ Collaboration scenario #12: Power

Developing together power and fuel solutions to UAV helicopters

Details: Zeta series Helicopter Xi Power

Questions:

Q1_Power: gas

Q3_Power: petrol

Q3_Power: hydrogen and fuel cells

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[016] ~ Collaboration scenario #13: Communications

Developing together communication solutions to UAV helicopters

Details: Zeta series Helicopter Xi Communications

Questions:

Q1_Communications: protocols planned to be used by your_company in UAV helicopters ?
Q2_Communications: what would be communication protocol for Xi copter with manned your_country's fighters ?
Q3_Communications: what would be communication protocol for Xi copter with your_company_helicopters ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[017] ~ Collaboration scenario #14: Money & Cost

Making together money by developing UAV helicopters, saving money by optimizing & getting money by acquiring capital


Details: Zeta series Helicopter Xi Money & Cost

Questions:

Q1_Money & Cost: which price categories your_company has planned to UAV helicopters (Xi copter price is $170.000 - $210.000)?
Q2_Money & Cost: your_company_leasing UAV helicopters ?
Q3_Money & Cost: your_company's target for market share ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[018] ~ Collaboration scenario #15: Versions

Developing together different kind of UAV helicopter versions

Details: Zeta series Helicopter Xi Versions

Questions:

Q1_Versions: will your_company's full sized flight platform version be targeted to business only?
Q2_Versions: will there be only one version of your_company's UAV helicopter for military purposes ?
Q3_Versions: does your_company have plans to have UAV helicopter versions containing third_party parts such as engines ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[019] ~ Collaboration scenario #16: Standards

Developing together standards for UAV helicopter industry

Details: Zeta series Helicopter Xi Standards

Questions:
Q1_Standards: does your_company use helicopter production standard MAPL (Modular Affordable Product Line) components in helicopter production ?
Q2_Standards: could we develop together a virtual design environment integrating design and manufacturing processes to improve the production process ?
Q3_Standards: any other standards used by your company ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[020] ~ Collaboration scenario #17: Markets

Marketing together UAV helicopters

Details: Zeta series Helicopter Xi Markets

Questions:

Q1_Markets: military markets and your_company's plans for UAV helicopters there ?
Q2_Markets: patrol markets and your_company's plans for UAV helicopters there ?
Q3_Markets: business markets and your_company's plans for UAV helicopters there ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[021] ~ Collaboration scenario #18: Benefits

Creating together benefits to UAV helicopter's clients

Details: Zeta series Helicopter Xi Benefits

Questions:

Q1_Benefits: what kind of benefits does your_company see for UAV helicopters ?
Q2_Benefits: special benefits offered by your_company UAV helicopters ?
Q3_Benefits: would it be possible to do research with current helicopter clients of your_company about benefits they would expect from UAV helicopters ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[022] ~ Collaboration scenario #19: Reliability

Developing together reliability of UAV helicopters

Details: Zeta series Helicopter Xi Reliability

Questions:

Q1_Reliability: does your_company see any special reliability issues with UAV helicopters ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[023] ~ Collaboration scenario #20: Safety

Developing together safety of UAV helicopters

Details: Zeta series Helicopter Xi Safety

Questions:

Q1_ Safety: does your_company see any special safety issues with UAV helicopters ?
Q2_ Safety: will your_company develop safety procedures specially for UAV helicopters ?
Q3_ Safety: UAV legistlation in your_country (for example, use of air space with manned air vehicles) ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[024] ~ Collaboration scenario #21: Innovation,Creativity&Exploration

Innovating, creating & exploring UAV helicopters and their technology and applications

Details: Zeta series Helicopter Xi Innovation,Creativity&Exploration

Questions:

Q1_Innovation: any your_company's innovations available to be used for Xi copter ?
Q2_Creativity: where do your_company's creative people come from ?
Q3_Exploration: is your_company developing, testing or prototyping any UAVs ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[025] ~ Collaboration scenario #22: partner profile

Creating partner profile suitable to both companies

Questions:

Q1_partner_profile: what kind of partner profile does your_company expect about this collaboration ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[026] ~ Collaboration scenario #23: To Do Together

Exploring and developing collaboration between companies

Details: what we do

Questions:

Q1_To Do Together: in which areas of UAV helicopters your_company is specially interested to collaborate with ?
Q2_To Do Together: your_company's interest to networked environments and UAV helicopter there ?
Q3_To Do Together: is your_company interested of other UAV helicopter related devices such as Base4Xi and Sensor4Xi ?

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[027] ~ Collaboration scenario #24: Sharing market

Sharing UAV helicopter markets

Details:
~ Usage
~ ZetaSeries Military Helicopter Xi Markets

Questions:

Q1_Sharing market: your_company's target markets seems to be military ?
Q2_Sharing market: your_company's plans for patrol markets ?
Q3_Sharing market: your_company's plans for business markets ?

your_company's views:


select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[028] ~ Collaboration scenario #25: FREE

FREE

Details:

Questions:

Q1_FREE:
Q2_FREE:
Q3_FREE:

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[029] ~ Collaboration scenario #26: FREE

FREE

Details:

Questions:

Q1_FREE:
Q2_FREE:
Q3_FREE:

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[030] ~ Collaboration scenario #27: FREE

FREE

Details:

Questions:

Q1_FREE:
Q2_FREE:
Q3_FREE:

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[031] ~ Collaboration scenario #28: FREE

FREE

Details:

Questions:

Q1_FREE:
Q2_FREE:
Q3_FREE:

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[032] ~ Collaboration scenario #29: FREE

FREE

Details:

Questions:

Q1_FREE:
Q2_FREE:
Q3_FREE:

your_company's views:



select: ~[Σ] ~[Ω] ~[Δ]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[033] ~ Collaboration scenario #30: Ending

The goal of this letter is to determine the sphere in which the joint cooperation is possible

Summary about the content

The content of this letter should be read more as a starting point in a dialogue, which we hope to lead to a long-term collaboration between S&S and your_company:
It is not meant to be technical i.e. this letter does not contain detailed information to specialists but rather attempts to open doors to them to meet face-to-face.

Small & Smart Inc looks forward to know which of above suggestions your_company is interested of and to know if there are other joint cooperation possibilities !

Please, send feedback and answer letters as follows:
~ in your_language to Small & Smart Inc P.O.Box 1259, 00101 Helsinki Finland (for translation).
~ in english to Small & Smart Inc 484B Washington Street Suite 326 Monterey CA 93940 United States
and let us know by email about your answer letter !

Small & Smart Inc
Ronnie Valkky /CEO
ceo@yourdragonxi.com

your_company's views:


select: ~[Σ] ~[Ω]!































































~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Small & Smart Inc reserves rights to change this document without any notice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~