Remuneration

General Information

Opened with a video - all about controlling the market around you
Definition - "remuneration is a payment made to or for the benefit of a worker, this is not as simple as a wage or salary as it includes such things as remuneration return and reconciliation statement" 

"What do I have to pay for" vs "what do I want my remuneration package to say"

Different types of Remunerations 
Example of a Successful remuneration package includes:

• $ per hour 
• non monetary 
• direct 
• indirect

Pros

Good use of video to introduce the topic - motif of "fuck you" getting in the best position you can

Interesting use of colour as a "contents page"

Good knowledge of topic

Good minimal use of slides - not to much text

Use of statistics to relate to the audience

Used hextic and own project as an example

Cons

No pictures - (although might be hard for topic)

could have at outside use of remuneration

How it relates to us

The employer: contractors (UNSW)

The Employees: (The Students)

All the conditions are already set eg. Hours, leave ect.

We cannot take any risk and not effected by profit loss, ect.

How it relates on a personal level

23% of UNSW FBE job seeker rate

$53.27 average hourly rate

Going to university (UNSW) adds to your overall Remuneration package

You can add to your "personal value" by

• General education
• Good Results
• Extra curricular projects
• Study tours
• Networking
• Internships

How to move forward

• documentation
• codes, regulations and legislation
• project evaluations, programs and feasibility studies
• consultants

Conflict

Summary of Information

Different Sources of Conflict

• Change
• Clash of personalities
• Leadership
• Poor Communication
• Sub Par Performance
• Emotions - Anxiety - Distrust - Disagreements

Pros

Covered a range of situations involving conflict
Incorporated the use of Hextic into the presentation which responds with the audience
Good use of statistics - (Might be generalized)
Good use of graphics and list of types of people that cause conflict.

Cons

Slides were a bit cluttered with text, pictures, banners and silhouettes

How it can relate to our group

Avoiding conflict before it "snowballs"
Need to use communication
Conflict and conflicting interests are different things, and one can lead to the other
As a group leader need to address the conflicting interests before they turn to a conflict.
Due to the nature of our project -(not design based) conflict is already limited, main issue is the allocation and shared equal work loads between team members

Intellectual Property

Main summary of information

4 Main Types

Regested Design -> physical
Trademark
Patent -> Process or Function
Copyright

Boosting innovation

Pro's

Good delivery - not relying on notes
Simple minimal presentation aids - providing efficient information
Some examples of IP in their personal project as well as other groups like blacktown marker 
Good knowledge of information - response to questions

Con's 

Repetition of some information
Colours in video not always clear.

My Question and answers

Q. How would you protect something that you intend to give away for free, so others cannot make money off it.

A. Make it an open source program and/or make your users agree to a end user license agreement (EUlA)

Also copyright only apply's to something before it reaches 50 production units, then it is void and the user need to apply for a resisted design


How it apply's to our group

Registered design is the look, form, how it is protected.
Computer -> circuit layout

If we want protect our project we would need to get: 

Patent on the code
EULA on use (end user license agreement)

If we want to commercialize the production we would need to:

Register the design
Seek a partnership with arduino as we are currently using it as fair use agreement.

Fritzing Arduino Recorder

Russell showed my a program called fritzing, that is incredibly beneficial to the documentation of our project.Here you can customize the arduino to your needs, and it creates a schematic in real time.

Arduino Documentation

Initial Documentation stage

As Elliot, Daming and Nev finish up on the final stages of coding, editing the arduino and importing into unreal I am starting to document this for others to be able to repeat. It is still in initial stages as the information that is to be recorded is not finalized yet. The plan is to create a"blueprint".

Here is an example of the Aesthetic we are aiming for, however there is a balance between the amount of information we provide.

These First two images may provide too much information confusing the user, whereas these next two are more user friendly. Also worth noting is type of diagram we provide, from an electronics point of view or a more physical photographic example to which the user can compare.

The diagrams we create are from Daming's work which we recorded. Below are examples that both Daming and myself recorded.

We can also include an exploded view of the final design we use for the wheel / dashboard.

Because the code is not too long, and the nature of it we will include the entirety within.