Re: associate many machines to a production run task

[Ricardo Chavez]

Hello everyone

I've decided to implement the corresponding screens: since the data
structures are already there, doing so should be a breeze thanks to the
framework (auto-fields-entity is sweet :)... ). However, I have some doubts
regarding the WorkEffortFixedAssetStd and WorkEffortFixedAssetAssign
entities:
- I thought both entites would have a relationship to the FixedAsset entity
(so the former would tell the fixed asset group and the latter would tell
the actual machine used), but a closer look to WorkEffortFixedAssetStd show
that it is related to FixedAssetType, so I'm obviously getting it wrong. Any
clues on why WorkEffortFixedAssetStd is related to FixedAssetType instead of
FixedAsset?
- About the estimatedDuration field in WorkEffortFixedAssetStd, which units
is it (intended to be) measured in? hours? milliseconds? user-decided time
unit?
- I see WorkEffortFixedAssetAssign has a statusId field, which (I suppose)
must be of type WorkEffort Asset (WORK_EFF_ASSET_STTS); however, I haven't
found any status of this type. Which would be those statuses?
Hope you can enlighten me on this matters, oh wise masters :)
Thanks in advance for your answers.
Regards,

-- Ricardo Chavez

On 10/4/06, Jacopo Cappellato <[hidden email]> wrote:

>
> Hi Ricardo,
>
> yes you are completely right!
> WorkEffortFixedAssetStd should be used to specify the standard machines
> associated to a routing task.
> WorkEffortFixedAssetAssign should record the actual machines assigned to
> a production run task.
> In general, this is the pattern we are using for this kind of things.
>
> Jacopo
>
>
> Ricardo Chavez wrote:
> > Hello everybody
> > I have recently found these two entities, WorkEffortFixedAssetAssign and
>
> > WorkEffortFixedAssetStd, and was wondering if anyone had some
> > information on
> > them, such as their purpose and how are they meant to be used, because
> they
> > might be what I'm looking for to implement the feature I described. So,
> any
> > thoughts?
> > Thanks in advance.
> > Regards,
> >
> > -- Ricardo Chavez
> >
> > On 9/29/06, Ricardo Chavez <[hidden email]> wrote:
> >>
> >> Hi Jacopo
> >>
> >> Thanks for the reply. Posting the JIRA feature request right now...
> >>
> >> -- Ricardo Chavez
> >>
> >> On 9/28/06, Jacopo Cappellato < [hidden email]> wrote:
> >> >
> >> > Hi Ricardo,
> >> >
> >> > there are no plans (that I'm aware of) of implementing this feature
> so
> >> > please post a Jira feature request because others could be
> >> interested in
> >> > helping you with this.
> >> >
> >> > This could be implemented in different ways:
> >> >
> >> > a) expanding the concept of FixedAsset groups (so that the data model
>
> >> > will
> >> > be left mostly unchanged); you create a fixed asset of type group (
> e.g.
> >> > "sewing machines of room A") and this fixed asset is associated to
> the
> >> > task; then you link each sewing machine (other fixed assets) to the
> >> > fixed
> >> > asset group
> >> >
> >> > b) (more complex) add new association entities to link a task
> >> > (WorkEffort)
> >> > to one or more machines (FixedAsset).
> >> >
> >> > If possible I'd follow the a) path... but I don't know what your
> >> > requirements are so this is just a 1 cent opinion.
> >> >
> >> > Jacopo
> >> >
> >> > Ricardo Chavez wrote:
> >> > > Hello everybody. I have this doubt about production run tasks and
> >> > machines.
> >> > > Is there a way to associate more than one machine (fixed asset) to
> a
> >> > single
> >> > > production run task? That would cover the case when you have many
> >> > machines
> >> > > working on the same production task, which I think is quite common
> in
> >> > any
> >> > > manufacturing business (e.g. many sewing machines working to
> complete
> >> > a
> >> > > production run of 1000 T-shirts).
> >> > > If this cannot be done yet, are there any plans to implement it? I
> >> can
> >> > post
> >> > > a JIRA feature request for this (unless, of course, you think it's
> >> not
> >> > a
> >> > > necessary feature and it needs not to be implemented)
> >> > > Thanks in advance for your answer.
> >> > > Regards,
> >> > >
> >> > > -- Ricardo Chavez
> >> > >
> >> >
> >> >
> >> >
> >>
> >
>
>

[Jacopo Cappellato]

Hi Ricardo,


Ricardo Chavez wrote:

> Hello everyone
>
> I've decided to implement the corresponding screens: since the data
> structures are already there, doing so should be a breeze thanks to the
> framework (auto-fields-entity is sweet :)... ). However, I have some doubts
> regarding the WorkEffortFixedAssetStd and WorkEffortFixedAssetAssign
> entities:
> - I thought both entites would have a relationship to the FixedAsset entity
> (so the former would tell the fixed asset group and the latter would tell
> the actual machine used), but a closer look to WorkEffortFixedAssetStd show
> that it is related to FixedAssetType, so I'm obviously getting it wrong.
> Any clues on why WorkEffortFixedAssetStd is related to FixedAssetType
> instead of FixedAsset?

I think that the original idea was to implement the concept of 'fixed
asset group' with the FixedAssetType entity: for example,
fixedAssetTypeId="SEWING_MACHINE" could represent the group of all the
real sewing machines (that are FixedAssets of type SEWING_MACHINE).
I don't know if it's better to keep this design decision or to implement
a fixed asset group as a special type of FixedAsset.
Any comments from others?

> - About the estimatedDuration field in WorkEffortFixedAssetStd, which units
> is it (intended to be) measured in? hours? milliseconds? user-decided time
> unit?

Adding a uomId field would be interesting... however right now the
convention is to store those values in milliseconds.

> - I see WorkEffortFixedAssetAssign has a statusId field, which (I suppose)
> must be of type WorkEffort Asset (WORK_EFF_ASSET_STTS); however, I haven't
> found any status of this type. Which would be those statuses?

Yes, I think that the type WORK_EFF_ASSET_STTS should be the correct
one. However, if you are not planning to use the statuses you could
ignore this field for now and we will decide about the right statuses
later on.

Jacopo

> Hope you can enlighten me on this matters, oh wise masters :)
> Thanks in advance for your answers.
> Regards,
>
> -- Ricardo Chavez
>
> On 10/4/06, Jacopo Cappellato <[hidden email]> wrote:
>>
>> Hi Ricardo,
>>
>> yes you are completely right!
>> WorkEffortFixedAssetStd should be used to specify the standard machines
>> associated to a routing task.
>> WorkEffortFixedAssetAssign should record the actual machines assigned to
>> a production run task.
>> In general, this is the pattern we are using for this kind of things.
>>
>> Jacopo
>>
>>
>> Ricardo Chavez wrote:
>> > Hello everybody
>> > I have recently found these two entities, WorkEffortFixedAssetAssign
>> and
>>
>> > WorkEffortFixedAssetStd, and was wondering if anyone had some
>> > information on
>> > them, such as their purpose and how are they meant to be used, because
>> they
>> > might be what I'm looking for to implement the feature I described. So,
>> any
>> > thoughts?
>> > Thanks in advance.
>> > Regards,
>> >
>> > -- Ricardo Chavez
>> >
>> > On 9/29/06, Ricardo Chavez <[hidden email]> wrote:
>> >>
>> >> Hi Jacopo
>> >>
>> >> Thanks for the reply. Posting the JIRA feature request right now...
>> >>
>> >> -- Ricardo Chavez
>> >>
>> >> On 9/28/06, Jacopo Cappellato < [hidden email]> wrote:
>> >> >
>> >> > Hi Ricardo,
>> >> >
>> >> > there are no plans (that I'm aware of) of implementing this feature
>> so
>> >> > please post a Jira feature request because others could be
>> >> interested in
>> >> > helping you with this.
>> >> >
>> >> > This could be implemented in different ways:
>> >> >
>> >> > a) expanding the concept of FixedAsset groups (so that the data
>> model
>>
>> >> > will
>> >> > be left mostly unchanged); you create a fixed asset of type group (
>> e.g.
>> >> > "sewing machines of room A") and this fixed asset is associated to
>> the
>> >> > task; then you link each sewing machine (other fixed assets) to the
>> >> > fixed
>> >> > asset group
>> >> >
>> >> > b) (more complex) add new association entities to link a task
>> >> > (WorkEffort)
>> >> > to one or more machines (FixedAsset).
>> >> >
>> >> > If possible I'd follow the a) path... but I don't know what your
>> >> > requirements are so this is just a 1 cent opinion.
>> >> >
>> >> > Jacopo
>> >> >
>> >> > Ricardo Chavez wrote:
>> >> > > Hello everybody. I have this doubt about production run tasks and
>> >> > machines.
>> >> > > Is there a way to associate more than one machine (fixed asset) to
>> a
>> >> > single
>> >> > > production run task? That would cover the case when you have many
>> >> > machines
>> >> > > working on the same production task, which I think is quite common
>> in
>> >> > any
>> >> > > manufacturing business (e.g. many sewing machines working to
>> complete
>> >> > a
>> >> > > production run of 1000 T-shirts).
>> >> > > If this cannot be done yet, are there any plans to implement it? I
>> >> can
>> >> > post
>> >> > > a JIRA feature request for this (unless, of course, you think it's
>> >> not
>> >> > a
>> >> > > necessary feature and it needs not to be implemented)
>> >> > > Thanks in advance for your answer.
>> >> > > Regards,
>> >> > >
>> >> > > -- Ricardo Chavez
>> >> > >
>> >> >
>> >> >
>> >> >
>> >>
>> >
>>
>>
>