Official Architecture -> Meta

Question

The question I have is totally architectural. I will expose a case just below to further illustrate the doubt that I am tapping directly into my system.

I have a feature that aims to register an employee. Such employee is composed of basic fields such as name, surname, date of birth, function and etc... OK! Until then we have no problem, but this employee has associated with him the sales targets that need to meet, IE, in each month of the year I have a value "hitched".

If we were to imagine the relationship between such entities, I soon created something like this:

An employee has many goals, which in turn has the months of the year.

Below are the bean's sparingly:

public class Funcionario implements Serializable {

        private static final long serialVersionUID = 1L;

        @Id
        @GeneratedValue(strategy = GenerationType.IDENTITY)
        private Long id;

        @OneToOne(cascade = CascadeType.PERSIST)
        @JoinColumn(name = "fk_metas")
        private Meta metas;

        ///Getters and Setters
}

public class Meta implements Serializable {

    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String ano;

    @OneToMany(cascade = CascadeType.PERSIST, mappedBy = "metas")
    private Set<Mes> meses;

    ///Getters and Setters
}

public class Mes implements Serializable {
    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    @ManyToOne
    @JoinColumn(name="fk_ano")
    private Meta metas;

    private Double janeiro;

    private Double fevereiro;

    ///Getters and Setters... Meses restantes
    }

That would be the smartest way?