Scheduling Question

You can use concurrent capacity to have the resource scheduled to multiple jobs.

 

A Mercer Sisson

Systems Manager - Insaco Inc

ams@...

215-536-3500 x 523

267-733-0641 (direct)

215-285-0332 (cell)

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 15, 2014 12:21 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Scheduling Question

 




Hi all,

 

First off, I am new to the world of Epicor. We are trying to setup up the resources and resource groups  to replicate the current production scenario. 

 

The scenario, is (FYI- we make custom trucks - in job shop kind of environment) 

 

Two truck building bays

 

Making the same truck 

 

Bay 1 (Setup as Resource Group 1 )

One Support assembler dedicated to one bay - Resource 1 

Lead assembler spends time between two bays - Resource 3 (1/2 time)

 

Bay 2 (Setup as Resource Group 2 )

One Support assembler dedicated to one bay - Resource 2

Lead assembler spends time between two bays - Resource 3 (1/2 time)

 

Can somebody please give me a way to correctly schedule this scenario ? Scheduling block won't let you enter 1/2 ? 

 

I hope one of the scheduling experts could answer this question.Thanks a lot in advance !!

 




This question is from one of our Project Managers. We are using Projects and WBS with parent jobs to build large, one a kind assemblies, which can take months to manufacture, not based on run rate per se, but based on the time to engineer, test, etc., which is not a hard and fast duration due to the fact that these are completely custom builds. The Project Manager would like to add a "fudge factor" to try and approximate the duration of the job. We only have one operation, manufacture, and move and queue times dont seem to be the answer. Thought about rough cut scheduling or production factors, just wanted to see what anyone else has done in this situation
Â
"Haven't seen a way to have concurrent jobs level set loads. System wants to forward or backward "stack" the entire job. i.e. if you have 200 hours/week of capacity in MFG, (5 guys/8 hours a day = 200) and you have a job that takes 40 hours of MFG, it plans all 40 hours in one day. but we want it to plan the 40 hours over 4 weeks (10 hours/week). If there are twenty of these 40 hour projects (that take 4 weeks each) at the same time, then MFG is loaded 100% over the 4 weeks."





[Non-text portions of this message have been removed]
Mark,



Setup your calendar for that resource/resource group to reflect your
actually plant capacity or staffing (however you want to look at it).
If you work a Monday - Friday you could do 2 hours per day, or if you
want you could just have that resource available for 10 hours on Friday
only etc. The second thing to look at is your scheduling blocks on the
job (I assume you build your mom on the job? Wherever, under job
details, operations, detail there is a field called scheduling blocks,
make sure this says 1, the system will then only ensure it gets 1
resource assigned to that operation. Regardless if the resource is
scheduled finite or infinitely it should at that point schedule your end
time 4 weeks from the operation start date.



Infinite scheduling in vantage does not assume you can get in infinite
number of hours completed per operation on a job, but assumes it can
schedule any number of operations to a resource at a given time
regardless of available hours. It will still calculate start and end
dates whether forward or backwards based on operation duration, which in
turn looks at the calendars. Infinite scheduling WILL honor days worked
or not worked, which again is dictated by your calendar setup.



Rob Bucek

Production Control Manager

PH: (715) 284-5376 ext 311

Mobile: (715)896-0590

FAX: (715)284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site) <http://www.dsmfg.com/>





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wagner
Sent: Wednesday, July 21, 2010 10:43 AM
To: Vantage User Group
Subject: [Vantage] Scheduling Question





This question is from one of our Project Managers. We are using Projects
and WBS with parent jobs to build large, one a kind assemblies, which
can take months to manufacture, not based on run rate per se, but based
on the time to engineer, test, etc., which is not a hard and fast
duration due to the fact that these are completely custom builds. The
Project Manager would like to add a "fudge factor" to try and
approximate the duration of the job. We only have one operation,
manufacture, and move and queue times dont seem to be the answer.
Thought about rough cut scheduling or production factors, just wanted to
see what anyone else has done in this situation

"Haven't seen a way to have concurrent jobs level set loads. System
wants to forward or backward "stack" the entire job. i.e. if you have
200 hours/week of capacity in MFG, (5 guys/8 hours a day = 200) and you
have a job that takes 40 hours of MFG, it plans all 40 hours in one day.
but we want it to plan the 40 hours over 4 weeks (10 hours/week). If
there are twenty of these 40 hour projects (that take 4 weeks each) at
the same time, then MFG is loaded 100% over the 4 weeks."

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
Thanks Rob, very much in line with what I was thinking, good to get some confirmation that we are on the right track

--- On Wed, 7/21/10, Rob Bucek <rbucek@...> wrote:


From: Rob Bucek <rbucek@...>
Subject: RE: [Vantage] Scheduling Question
To: vantage@yahoogroups.com
Date: Wednesday, July 21, 2010, 3:20 PM


Â



Mark,

Setup your calendar for that resource/resource group to reflect your
actually plant capacity or staffing (however you want to look at it).
If you work a Monday - Friday you could do 2 hours per day, or if you
want you could just have that resource available for 10 hours on Friday
only etc. The second thing to look at is your scheduling blocks on the
job (I assume you build your mom on the job? Wherever, under job
details, operations, detail there is a field called scheduling blocks,
make sure this says 1, the system will then only ensure it gets 1
resource assigned to that operation. Regardless if the resource is
scheduled finite or infinitely it should at that point schedule your end
time 4 weeks from the operation start date.

Infinite scheduling in vantage does not assume you can get in infinite
number of hours completed per operation on a job, but assumes it can
schedule any number of operations to a resource at a given time
regardless of available hours. It will still calculate start and end
dates whether forward or backwards based on operation duration, which in
turn looks at the calendars. Infinite scheduling WILL honor days worked
or not worked, which again is dictated by your calendar setup.

Rob Bucek

Production Control Manager

PH: (715) 284-5376 ext 311

Mobile: (715)896-0590

FAX: (715)284-4084

<http://www.dsmfg.com/>

(Click the logo to view our site) <http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wagner
Sent: Wednesday, July 21, 2010 10:43 AM
To: Vantage User Group
Subject: [Vantage] Scheduling Question

This question is from one of our Project Managers. We are using Projects
and WBS with parent jobs to build large, one a kind assemblies, which
can take months to manufacture, not based on run rate per se, but based
on the time to engineer, test, etc., which is not a hard and fast
duration due to the fact that these are completely custom builds. The
Project Manager would like to add a "fudge factor" to try and
approximate the duration of the job. We only have one operation,
manufacture, and move and queue times dont seem to be the answer.
Thought about rough cut scheduling or production factors, just wanted to
see what anyone else has done in this situation

"Haven't seen a way to have concurrent jobs level set loads. System
wants to forward or backward "stack" the entire job. i.e. if you have
200 hours/week of capacity in MFG, (5 guys/8 hours a day = 200) and you
have a job that takes 40 hours of MFG, it plans all 40 hours in one day.
but we want it to plan the 40 hours over 4 weeks (10 hours/week). If
there are twenty of these 40 hour projects (that take 4 weeks each) at
the same time, then MFG is loaded 100% over the 4 weeks."

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]











[Non-text portions of this message have been removed]

Hi all,

 

First off, I am new to the world of Epicor. We are trying to setup up the resources and resource groups  to replicate the current production scenario. 


The scenario, is (FYI- we make custom trucks - in job shop kind of environment) 


Two truck building bays


Making the same truck 


Bay 1 (Setup as Resource Group 1 )

One Support assembler dedicated to one bay - Resource 1 

Lead assembler spends time between two bays - Resource 3 (1/2 time)


Bay 2 (Setup as Resource Group 2 )

One Support assembler dedicated to one bay - Resource 2

Lead assembler spends time between two bays - Resource 3 (1/2 time)


Can somebody please give me a way to correctly schedule this scenario ? Scheduling block won't let you enter 1/2 ? 


I hope one of the scheduling experts could answer this question.Thanks a lot in advance !!


Are you scheduling your work to the Bay?
I would have 2 resource groups

· Group - Bays

o Resource Bay 1 (Schedule capacity would be 24 hours)

o Resource Bay 2 (Schedule capacity would be 24 hours)

· Assemblers

o Resource Assembler 1 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

o Resource Assembler 2 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

o Resource Lead Assembler 3 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

Assembly Op

· Scheduling resource Requirements

o 10 – Bays (Where)

o 20 – Assemblers (With What/Who)

This would cover the requirements of where the work is being done and what you are using to get the work done.
Now you can schedule your resources, which Bay and with who.

Charlie Smith
Production Control Manager
ESSNER Manufacturing, L.P.
6651 Will Rogers Blvd.
Fort Worth, TX 76140
csmith@...<mailto:csmith@...>
ph: (817) 529-6165
fx: (817) 568-2625
[LOGO_Essner_Manufacturing]

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 15, 2014 11:21 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Scheduling Question


Hi all,

First off, I am new to the world of Epicor. We are trying to setup up the resources and resource groups to replicate the current production scenario.

The scenario, is (FYI- we make custom trucks - in job shop kind of environment)

Two truck building bays

Making the same truck

Bay 1 (Setup as Resource Group 1 )
One Support assembler dedicated to one bay - Resource 1
Lead assembler spends time between two bays - Resource 3 (1/2 time)

Bay 2 (Setup as Resource Group 2 )
One Support assembler dedicated to one bay - Resource 2
Lead assembler spends time between two bays - Resource 3 (1/2 time)

Can somebody please give me a way to correctly schedule this scenario ? Scheduling block won't let you enter 1/2 ?

I hope one of the scheduling experts could answer this question.Thanks a lot in advance !!





[Non-text portions of this message have been removed]
Dear Smith,

Thanks a lot for your timely reply. Like i said in the previous email, we are not live with epicor. So i am looking for options. The IDEA you suggested is awesome !!!  

So when i route the two trucks, i will be doing something like this 

Truck A
OPCODE  - TRUCK BUILD - 100 Hrs - with requirement of two resource groups (Bays & Assemblers )
Truck B 
OPCODE  - TRUCK BUILD - 100 Hrs - with requirement of two resource groups (Bays & Assemblers )

Would the work be split equally ? Should i have to change any setting in resource Group like Split operation, scheduling block etc






On Tuesday, July 15, 2014 9:43 PM, "Charlie Smith csmith@... [vantage]" <vantage@yahoogroups.com> wrote:


 
<div id="ygrps-yiv-1253089210yiv0930862277ygrp-text" class="ygrps-yiv-1253089210" style="">
  
  
  <div class="ygrps-yiv-1253089210" style="">Are you scheduling your work to the Bay?

I would have 2 resource groups

· Group - Bays

o Resource Bay 1 (Schedule capacity would be 24 hours)

o Resource Bay 2 (Schedule capacity would be 24 hours)

· Assemblers

o Resource Assembler 1 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

o Resource Assembler 2 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

o Resource Lead Assembler 3 (schedule capacity would be 7 hours or whatever the shift is including lunch/dinner and breaks)

Assembly Op

· Scheduling resource Requirements

o 10 – Bays (Where)

o 20 – Assemblers (With What/Who)

This would cover the requirements of where the work is being done and what you are using to get the work done.
Now you can schedule your resources, which Bay and with who.

Charlie Smith
Production Control Manager
ESSNER Manufacturing, L.P.
6651 Will Rogers Blvd.
Fort Worth, TX 76140
csmith@...<mailto:csmith@...>
ph: (817) 529-6165
fx: (817) 568-2625
[LOGO_Essner_Manufacturing]

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, July 15, 2014 11:21 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Scheduling Question


Hi all,

First off, I am new to the world of Epicor. We are trying to setup up the resources and resource groups to replicate the current production scenario.

The scenario, is (FYI- we make custom trucks - in job shop kind of environment)

Two truck building bays

Making the same truck

Bay 1 (Setup as Resource Group 1 )
One Support assembler dedicated to one bay - Resource 1
Lead assembler spends time between two bays - Resource 3 (1/2 time)

Bay 2 (Setup as Resource Group 2 )
One Support assembler dedicated to one bay - Resource 2
Lead assembler spends time between two bays - Resource 3 (1/2 time)

Can somebody please give me a way to correctly schedule this scenario ? Scheduling block won't let you enter 1/2 ?

I hope one of the scheduling experts could answer this question.Thanks a lot in advance !!




[Non-text portions of this message have been removed]

</div>
 


<div style="color:#fff;height:0;" class="ygrps-yiv-1253089210"></div></div>
#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 -- #ygrps-yiv-1253089210yiv0930862277ygrp-mkp { border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp #ygrps-yiv-1253089210yiv0930862277hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp #ygrps-yiv-1253089210yiv0930862277ads {
margin-bottom:10px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp .ygrps-yiv-1253089210yiv0930862277ad {
padding:0 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp .ygrps-yiv-1253089210yiv0930862277ad p {
margin:0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mkp .ygrps-yiv-1253089210yiv0930862277ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ygrp-lc {
font-family:Arial;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ygrp-lc #ygrps-yiv-1253089210yiv0930862277hd {
margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ygrp-lc .ygrps-yiv-1253089210yiv0930862277ad {
margin-bottom:10px;padding:0 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity span {
font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity span:first-child {
text-transform:uppercase;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity span a {
color:#5085b6;text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity span span {
color:#ff7900;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277activity span .ygrps-yiv-1253089210yiv0930862277underline {
text-decoration:underline;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277attach div a {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277attach img {
border:none;padding-right:5px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277attach label {
display:block;margin-bottom:5px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277attach label a {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 blockquote {
margin:0 0 0 4px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277bold {
font-family:Arial;font-size:13px;font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277bold a {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 dd.ygrps-yiv-1253089210yiv0930862277last p a {
font-family:Verdana;font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 dd.ygrps-yiv-1253089210yiv0930862277last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 dd.ygrps-yiv-1253089210yiv0930862277last p span.ygrps-yiv-1253089210yiv0930862277yshortcuts {
margin-right:0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277attach-table div div a {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277attach-table {
width:400px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277file-title a, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277file-title a:active, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277file-title a:hover, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277file-title a:visited {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277photo-title a, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277photo-title a:active, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277photo-title a:hover, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div.ygrps-yiv-1253089210yiv0930862277photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 div#ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg #ygrps-yiv-1253089210yiv0930862277ygrp-msg p a span.ygrps-yiv-1253089210yiv0930862277yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277green {
color:#628c2a;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277MsoNormal {
margin:0 0 0 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 o {
font-size:0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277photos div {
float:left;width:72px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277photos div div {
border:1px solid #666666;height:62px;overflow:hidden;width:62px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277reco-category {
font-size:77%;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277reco-desc {
font-size:77%;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 .ygrps-yiv-1253089210yiv0930862277replbq {
margin:4px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-actbar div a:first-child {
margin-right:2px;padding-right:5px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg table {
font-size:inherit;font:100%;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg select, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 input, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg pre, #ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 code {
font:115% monospace;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg * {
line-height:1.22em;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-mlmsg #ygrps-yiv-1253089210yiv0930862277logo {
padding-bottom:10px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-msg p a {
font-family:Verdana;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-msg p#ygrps-yiv-1253089210yiv0930862277attach-count span {
color:#1E66AE;font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-reco #ygrps-yiv-1253089210yiv0930862277reco-head {
color:#ff7900;font-weight:700;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-reco {
margin-bottom:20px;padding:0px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ov li a {
font-size:130%;text-decoration:none;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ov li {
font-size:77%;list-style-type:square;padding:6px 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-sponsor #ygrps-yiv-1253089210yiv0930862277ov ul {
margin:0;padding:0 0 0 8px;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-text {
font-family:Georgia;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-text p {
margin:0 0 1em 0;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-text tt {
font-size:120%;}

#ygrps-yiv-1253089210 #ygrps-yiv-1253089210yiv0930862277 #ygrps-yiv-1253089210yiv0930862277ygrp-vital ul li:last-child {
border-right:none !important;}
#ygrps-yiv-1253089210