I. Welcome -

Cliff shared the guidelines for evacuation of the building and shelter-in-place in the event of an emergency. He also reminded everyone that this was Lynda's last CAPPS meeting since she will be retiring on May 1, 2004. PPSPS provided cake and all were invited to please help themselves. Jody announced that anyone wishing to send an email to Lynda to be included in her memory book should address it directly to her at Lynda.Wilson@usda.gov.

II. Misc - Jo

A. z/OS Operating System - The LIVE tests will be held on May 15th and May 29th. Individuals needing specific information should read Al's April 7th E-mail which discuses the testing to occur in May. Individuals interested in participating should contact Al. Jo stressed that this is NOT being performed on a test database. Any changes made will apply to the system.

B. New Phone Exchange - For those of you still dialing the old NFC numbers for your contacts should be aware that the auto call forwarding terminates May 6th. At that time, the old phone numbers will be shut off (i.e., the 255 number will no longer roll to the new 426 exchange). As indicated earlier, the key 255 numbers will remain in effect. However, if you need the new number anyone, contact them soon.

C. 4th Quarter Training - NFC issued an e-mail announcing the 4th quarter training a few weeks ago. The STAR training was announced as STAR client. However, there will be no more STAR client training. All future STAR training will be for STAR web. EPIC/HCUP and TINQ are also scheduled in the 4th quarter. Please check the website for specifics.

III. Benefits Updates - Jody provided an update on the following benefit items:

A. TSP Updates - TSP Open Season will run from April 15th thru June 30th. The TSP Open Season flyers will be included in PP-07's E&LS and on the EPP.

1. Info from the March TSP Quarterly meeting -

a. Discussed changes in the loan process which includes effective this July 2004, only one general purpose loan; a $50 fee pre loan; employees must wait 60 days after paying off a loan to apply for a new loan.

b. TSP can provide on-line statements. They are also working on other website modifications and are interested in ideas from agencies - work with your agency's Benefits/TSP rep for this and submit comments to the Board.

c. TSP is considering termination of the waiting periods for TSP participation. It probably will not happen this year, but most likely next year. Capitol Hill appears to be receptive to this change; more on this later this year.

2. Elected Deferral Limit - Jody reminded reps of the elected deferral limit for highly paid TSP participants who are contributing at the maximum percentage. These employees will reach the annual TSP maximum contribution amount prior to PP-24. In order for these employees to receive the full benefit of matching contributions throughout the year, they must modify their withholding amount to spread the contribution amount over the remaining pay periods. While this is the employee's responsibility to understand this and make the changes, it is in the agency's best interest to remind them to avoid upset/angry employees.

3. TSP Catch-up - Participants must be age 50 year and older as well as participating at the highest percentage rate. Because of the elected deferral limit, agencies must be aware that we cannot edit against the maximum (highest percentage rate). Again it is suggested that CAPPS Reps & Agency Benefit Officers advise employee's of these rules.

B. SF-2809 - the revised SF-2809 requirements were submitted to NFC in March, 2004. These are for the new permissible event changes that OPM established late last summer (see OPM's BAL 03-207). The changes will effect EPIC and all FEHB change events. The old A-K values have been changed and expanded upon. OPM will not permit a copy of the draft SF-2809 to be shared because they are still waiting on OMB's official approval, which will hopefully be later this year.

C. Personal Benefits Statements - Employees who are going to receive their Personnel Benefits Statements should have done so by now. However, most agencies have at least a few employees on the exception list, which Jody distributed at the meeting. The exception list covers all employees who will not receive a benefits statement because there database record contains invalid values. Some of the errors are due to invalid 6C retirement date values while others were in suspense due mainly to FEHB eligibility code errors . The cut-off date for a revised statement is the end of May. NOTE: Currently the benefits statement simply indicates that Long Term Care Insurance (LTCI) is available to employees; however, it doesn't indicate whether an individual is participating in LTCI. Q: Jody asked if agencies are interested in a notation that would indicate whether or not the employee is participating in LTCI? This statement could not provide any additional information since the payroll deduction for LTCI is the only information NFC has on file. A: Yes. However, the statement should simply indicate that the employee is participating via payroll deduction since they can participate via other methods.

D. Flexible Spending Accounts - Employees that are coded as ineligible for FEHB (FEHB coverage code = "2") cannot participate in FSA's. In many cases the employee's coverage eligibility changed upon a subsequent appointment but the code has not been updated to "4" - eligible pending. Please notify your users that it's imperative that they run a report of employees with FEHB Coverage Code 2 (ineligible) and review their data to determine if in fact that code should be changed.

IV. Employee Express Update - George shared key items from the monthly EEX meeting.

A. A resolution was not reached on the Interactive Voice Response (IVR) system. The biggest user of the EEX IVR is Treasury and they do not want to drop it as an option. The majority of the EEX clients wish to drop their support of this, because they do not use it. However, Treasury does not want to foot the bill for all of the modifications needed for the new IVR, so it is back in discussions again. EEX will probably provide some level of support on this.

B. Implementation of an on-line PIN validation change was also discussed. EEX is interested in utilizing the employee's retirement coverage code values as a security mechanism. A problem with this option is that not all of the codes are sent to EEX depending on the employee's coverage. The value for some employees are being submitted as "N" and others sending nulls. OPM has thus far refused to provide retirement coverage codes are all relevant retirement systems (e.g.., commissary exchange systems, etc.). George was not sure where this particular discussion would end up.

C. EEX is sending a security agreement pertaining to sanitation of testing data. In the test forum, it is very difficult to obtain a mix of employee's in the sample, yet properly screen the output reports to prevent unauthorized individuals to see another agency's data (i.e., names, SSN's, etc.). The payroll providers should receive the agreements. EEX would like to have this agreement signed and in place by May 14th. If an agreement cannot be reached by this time, it may affect the fall release testing. This proposed change in policy does not affect the transmission of data to/from EEX because the data is encrypted for this process. The proposal only concerns the data on the screens and reports during testing.

D. USDA is pulling out of EEX effective October 1, 2004. Other agencies are also considering dropping out of EEX because of costs and dual coverage with NFC's EPP/ESS.

V. PATCO Codes - George indicated that he had received a query from one of the clients regarding the new PATCO codes. He researched the issue and there are no new codes. The rumor is that EEOC is considering changing codes for EEOC reporting, however, this is unconfirmed. George asked that the clients notify him if they hear anything additional on this. At this time, it will not affect CPDF.

VI. NFC Updates - Jerry Lohfink gave a status of the following:

A. Cost and Pricing - November Briefing & January CAPPS - we discussed needing input from the clients regarding cost and pricing. We used to have more visibility in the old algorithm and want it back. NFC South is looking into this (the old blue book) and Jerry asked that the word be passed to Finance Folks, etc. A contact number was provided for replies. Based on feedback, we have put a model together and will share it next week at the HR Briefing. We are working on expanding the costs centers, specifically those relating to costs that the agency has in determining the use of cost centers (what services will be, elective choices, etc.). Additionally, we will have four more cost centers in 2006; currently, we don't have all the data ready but will have it in place by 2006...this will be a phased-in approach over the next couple of fiscal years. Thanks for your attention and support.

B. Request Tracking - Penny indicated the PATS6B - changing to ACCESS, 6B has been taken down for new ACCESS report. It's imperative that you remind everyone that if they don't have access to the Reporting Center on their User ID's, they must request this.

C. Status of Retro (2003) - does anyone have a question? Q: Doralee - with the 2003 retro we were informed that NFC didn't want to make payments unless the action was on the DB. If we have a situation where we can't enter the action on the DB, will NFC revise their policy? A: We will look at this on a case by case basis, talk to Mose.

D. Web FOCUS - past 18 months I've had 4-5 clients that want this group together and it was discussed in January - those interested in using this were to contact NFC South and help us identify the benefits for the business case. We heard from NO ONE! Lack of interest = shelving for the time being.

E. Customer Service Improvement Project - 1) feedback discussed and will again be discussed at the HR Briefing - help desk, best practice, bench marking, etc. This will involve additional customer surveys and feedback as well as establishing and implementing of metrics from industry standards and skill sets. 2) in the process of recommending the GESD restructuring to improve the customer service w/the clients. This information will be discussed next week...must be approved by USDA (Dept level) - would like to make it easier to allow clients to contact NFC South and have a follow up process of replying back to you...escalating process to ensure that it is not lost in the cracks....giving it supervisory/ managerial attention; 3) announcing a new Customer Advocate. This person (office) will not deal with inquiries but will be the first-line of defense, won't have ability to direct inquiries or calculate a manual pay but rather a relationship escalation process; if something goes awry, then you would deal w/this person to resolve the issues.

1. Q: You had asked us to sign-up to be part of a group who wanted to be involved in customer service feedback...is that still open? A: Yes, it's part of the restructuring of GESD...this group would work with the CAPPS Reps to handle customer service issues; ideas on improvement; reactions and planning results of bench marking; couple of dedicated people focused on working with the CAPPS community.

2. Q: Doralee - you had discussed a need for two groups - one in NFC and one of CAPPS volunteers - to present the issues, discuss findings, etc.; how is that coming along? TR did not respond - did you get any response? A: No one responded but as part of the restructuring of GESD we will work with agency reps to help us out. FQ: Will this be discussed at the HR Briefing next week? A: Yes.

3. Q: PATS6B - if users had security to retrieve PATS6B report, is this the same access for the new ACCESS database report? A: If you have access to one, you have access to the other.

VII. Status of 2004 Retroactive Pay Adjustment Processing -

A. Glenda provided stats of suspense errors from Pass 1 which included all of the documents, there were 239 (the lowest) and 433 (the highest) for approximately 3,300 documents processed. Pass 2 brought in an average of 10-12% errors, depending on the CV's we were able to get an automated fix for the majority of the 088 errors. NFC did find that there were small isolated cases on CV05 (7 employees) were issued locality erroneously - for pay plan EF. Reports on CV06 & CV07 did not have this pay plan. Other small problems were affecting 2-3 individuals per situation. They are working through those items that they know are in error.

B. Peace Corp submitted actions to be deleted and they still have not been deleted. The requests were submitted last Tuesday and a follow-up on Monday morning. Glenda will check with Josie on this. Q: Did any one else have this type of problem? A: FDIC had 10 cases from Saturday. DOC had 12, Pre-trial had 5, DOJ has FQ's to address them. FQ: Were DEA's gone? A: DEA's were done. The FQ's will be done today.

C. Mike - during the last conference call they discussed error 478 - retirement system data invalid. Was this reviewed? How many individuals? FMS had over 100. Cliff added that this information should be placed in as valid data and not bogus to prevent any adverse affects.

D. Mike had submitted several cases with error message 612 and those packages were deleted. The new one is 616 and is an error and they cannot get around. What is your request? Cliff - the case is the employee was given a temp promotion then the temp promotion was made permanent without doing the CLG. He recommended that the agency do this to clear this error. Technically you should be able to process a permanent promotion w/o proc'g a CLG; however, PMSO cannot handle this. Lynda indicated that the agency does have to ensure the 612 is deleted, then they start the packages including the 713 in the package.

E. TR - Reports are still not being received. Is it possible to send them via a CD? NFC does not want to send these via the mail and would prefer that they get them electronically. There are several people in the room (FDIC, DHS, DOJ) that have also indicated they are not getting their reports. NFC is sending the data to these reports and are working with Ivan's staff to work on technical issues. DOJ's reports will be zipped and sent to you, they are going to the download center but you do not appear to be getting them. MHS-ICE and Customs are saying they are also having difficulty. The reports are typically sitting in SDSF waiting for an address. As far as we know, the only outstanding printing issues are due to incorrect printer numbers or technical difficulties.

F. Mike - if Lorraine cannot get the reports to us, can we get a zipped e-mail? Glenda will try to do this via printers.

G. Employees who crossed bureaus within a department were not by-passed, were they? A: No. FQ: we have an employee who switched agencies within DOC. The package seems to have been generated to the opposite agencies. FA: just one case. Cliff said it may have to do with the authentication date.

H. FEC has a case where new employees were not generated. A: send them into the pay raise mailbox and they'll look into it.

I. GAO has an action that they created in HCUP last night and they are getting the 088 message this morning. Was the 088 fix a one-time shot? A: Yes, a one-time shot. If an agency gets this message, they must follow the instructions to get it corrected.

J. When is the next conference call? Probably next week, prefer Monday or Tuesday. Glenda knows there is an agenda spot for discussion of this at 1:00, would agencies like a discussion on Friday to see what happened with the first pass of PAYE for CV05 and CV06 @ 10-10:30 EST? A: YES!!

VIII. Jerry expressed his thanks to Lynda for her many years of service.

IX. Pay Raise Suspense Errors - Cliff mentioned that PPSPS had been contacted regarding some of the PINE edits.

A. The 088 suspense error's have been fixed as indicated by Cliff's e-mail. The fix was implemented on Monday night and the 088 messages should have cleared then.

B. The 541 error message is on the SCD-TSP. This date cannot be prior to 01/01/1984 when TSP was established and the edit is programmed accordingly. Some FERS employees actually have records with SCD-TSP dates prior to 01/01/1984. If the record is corrected, the documents in suspense should apply. We are updating the SINQ Addendum to include a more in-depth explanation of this error message.

C. Agencies have also reported PINE edit "problems" where employees have separated and are reappointed. These errors are the "208 - Cannot Process" and "158 - Employee Separated - Cannot Proc Action". Both errors appear to be systemic problems and Cliff is working with the programmers. The resolution will not be completed before PAYE runs for PP-07, but it should be completed shortly thereafter. Do NOT send these cases down for deletion! Do NOT submit them to the PPO mail box as problems either. We are aware of the issue, please just hold them for now.

X. 2004 Retroactive Pay Adjustments for FWS Employees - Cliff discussed OPM's CPM 2004 -06 dated March 4, 2004. This CPM announced the legislative changes in the FWS areas and announcing that some FWS would have more than one wage table due to the various locality pay rates included in those areas. The end result is that we have multiple wage schedules to accommodate the link to locality pay for GS employees (e.g., Philadelphia Wage Area will now be subdivided into 3 different wage schedules). The number of pending tables is building up because we have additional wage schedules being issued every pay period. Some employees in the affected wage areas will have to be moved to new wage tables. Programmers are looking at how best to handle this implementation. There is NO implementation date at this time - these are the same programmers that are involved in the 2004 Retro Pay raise. Based upon volume of employees affected, the GS schedules took priority over the FWS schedules. NFC is considering a phased in type approach. The FWS areas that retain only one schedule would be loaded first and the split schedules would come next.

XI. Child Support - Steve L gave a brief update from last months discussion on the 3rd party payments via EFT. Treasury elected child support NFC is doing @ 11,000 child support payments each month. NFC is working with FMS and the office of child support at HHS to get a file of those we are initially editing. Sent to FMS and they are working with states on a case reconciliation process against the state's centralized offices which are called the State Disbursing Units (SDUs). (States have centralized their counties and other jurisdictions into one, state level office). Steve indicated that he had received approximately 30-40 particular reconciliations back from the states. However, he has not been able to fully review the data yet. In last month's CAPPS meeting Steve had proposed that the agencies be involved in changing some individual records. However, after reviewing the file and looking at the information, NFC will probably go ahead and change the case numbers to the State assigned numbers.

In PP-11 all of the child support checks will be converted to an EFT payment. Debbie Tatum's staff is working with TR's FS to facilitate this process. Since the agencies processed those that they could, agency staff need to be aware that there will be changes in the case number, as well as, the name and address of the recipient will change to EFT (i.e., routing and checking account numbers). These changes will occur between now and PP-11. Please do not make any changes to these records to modify the case number or EFT information.

A. Q: George inquired what should happen to any new cases? A: The new cases should come from the SDU with the valid case numbers. NFC is the last payroll office to do this conversion, so there should be no new cases from non-SDU facilities and the agency should put them in as they did in the past. There may be a few voluntary assignment of wage agreements and those will continue to be handled as they were in the past. (These may still be going to an individuals via a check.).

B. Q: George is NFC going to distribute a master list of all the cases that have been changed so that they can share it with the appropriate offices? It would need to be broken done by agency and POI. A: Yes, but agencies are not to do anything with it in the system..

The next step in the 3rd party automation process is to convert to EFT the state and local tax levies that are currently being issued as checks. This will most likely occur before the end of the calendar year. At some point, agencies will probably see all 3rd party payments centralized and mandated as EFT.

George indicated that the Office of Child Support Enforcement (OCSE) representative was unable to attend today's meeting. However, they wished to make it clear that they are willing to provide operational training to individual agencies. If agencies wish to avail themselves to the training, they should contact OCSE directly. OCSE has a road show and documentation that they can provide to agencies. Karen Anthony is the contact and she may be reached at 202-690-6275 or via email to Kanthony@acf.hhs.gov.

XII. User & Work Group Updates

A. Awards - Jo informed the reps that the next meeting is scheduled for May 12th from 9:30-11:30 in Lincoln 3. Clients were reminded that if you do not participate, you accept what decisions are made by those who do.

B. EPIC - Lynda reminded users that the next release of EPIC v2.06, is scheduled for PP-08, April 26. It is on the download center and if you need a CD, please let her know. The new version becomes mandatory for use in PP-10. Prior to this, users will receive a message as they log-on reminding them of the cutoff date. Please make arrangements to get software thru your labs, etc. and installed no later than PP-10.

1. Lynda indicated that future EPIC issues should be sent to PPO@usda.gov. The NFC Payroll Operations is making arrangements to respond to this mailbox. She also indicated that NFC will be issuing a vacancy announcement for her position shortly and they are also considering contractual help to handle additional functions.

2. FESI - There was no one in attendance to provide an update. Jo indicated that this was an agenda item at the HR Briefing the week of April 27th.

C. Leave Share - Jo indicated that there was no update this month. However, she also indicated that she had spoken to the new supervisor in NFC unit to get a status of the package. The package as reviewed by NFC staff will be sent to Jo so that the LS Work Group can go over it.

D. PMSO - George indicated that he had received no volunteers for this group. However, he did receive a thick package from USDA based upon a PMSO review that they had done earlier. Since there is no group to share it with, George will review it and share key portions with the CAPPS group. It will NOT be discussed at length in CAPPS - the package is too large for this. If clients are interested in participating in this and other reviews, please contact George. He reminded clients that PMSO is critical and it is the first part of the HR process. He encouraged clients to participate in discussions on what is "broken" and can be fixed or modified for the benefit of all.

E. Work Group / User Group Process - Jo briefly outlined this process. These groups are basically sub-groups of CAPPS reps (or CAPPS rep designees) who work together to develop requirements and provide info to NFC in those program areas. NFC staff recognize that this can be a long drawn out process and the clients are frequently as short-staffed as NFC. However, it is critical that NFC obtain client input on these issues to ensure that your needs are taken into consideration. Without your input we cannot do it.

F. T&A - Jo informed the reps that the next User Group meeting is scheduled for May 13th from 9:30-11:30 in the Resource Room and that the next Requirements meeting is scheduled for May 13th from 1-3 in the Resource Room. (First pay day Thursday is the regular user group meeting.) Q: Requirements for STAR Web is closed, right? A: yes, there is a demo on the website; what's on 4.0 is a go...we will go live in PP 15. Idea is not to negotiate this but to move forward....implementing in phases, first phase is closed but we can discuss for the next phase. Any changes made now will not be in 4.0. DK: when timekeepers come in PP 15 all new screens will be there, right? A: Yes....3.0 will go away and 4.0 will be up and running. FC: are you willing to allow our timekeepers to join this pilot? No time for training these folks....although we feel an overview is necessary; our experience is to have an overview w/their timekeepers - concerned about not participate in pilot and then enter in PP 15, they have no choice, no longer a client version. A: Jo says that you should contact your CSR b/c no move to restrict the pilot participants. FA: Penny said you'll have the same issue if you have those come in PP 13....pilot is a subset of the community in STAR today....you do realize that you can't do both for a few PP's and you are advancing the deadline. If DOJ begins now to developing something they have more time...vs PP 13 to PP 15 from pilot to production....Q: Doralee - have we rec'd an email about the pilot? A: Yes, but Jo will forward the message again to CAPPS. DOJ will call Johanna about this after they rethink this. Penny says we can accommodate this. Doralee told their clients in January that STAR will be going to daily and a new transmission record will occur, right? A: No the record layout will not change; what will be sent is a weekly segment record...allow daily entry on T&A w/o passing to the transmit record....that layout will not change at this point in time. Will PC TARE be sunset? A: at the same time we retire STAR Client - end of FY 05...will discuss at the HR Briefing.

XIII. Potpourri

A. Q: Peace Corp - We have been having problems with our Spot awards. How is NFC handling these. We have done several and they reflect in the system but are not paid? A: Jo - What mechanism are you using? The 840 V3G indicate to NFC that you merely wish to document that the spot award has been issued and the agency will distribute the money. If you use the PAY authority, NFC will generate the payment. What is the error? F: We are using the PAY and the document applies but it is not paying. FA: Please send the SSN(s) to Jo at Jo.Bonner@usda.gov.

B. Q: PTSA - We have just started using STARweb, and the accounting is not validating against Tables. They have checked against the PQ screens and TMGT screens that the accounting is correct but they do receive error messages. A: Jo - Are there spaces in your accounting string that you are not entering in STARweb? F: No, we are doing them exactly the same and cannot figure out what is going on. FQ: Deborah King from DOJ who provides technical support for this agency requested that PTSA get with her after the meeting. She believes this has something to do with PTSA's conversion from DOJ.

C. Q: DOJ - Inquired if Jo had found any additional information about the problems DOJ was experiencing with employee who use military leave. A: Jo - Is playing phone tag with a programmer to obtain more information. Another agency has also reported this issue. C: Jo also indicated that she does not have a resolution on the leave accrual issue when a part-time employee donates annual leave. Jo asked if any of the clients had an employee who had done this so that an additional test case could be used. A: No one spoke up. FQ: Treasury - What is the military leave situation? FA: Employee's Military Leave Used YTD field is reflecting 120 hours and the employee has not used Military Leave this fiscal year. It appears that some agencies are having the problem and others are not. Jo will continue to research.

D. Q: Treasury - We are interested in implementing the transaction descriptors on their T&A's, but some of their agencies are using non-NFC systems. Where is this data stored in the transmit file? A: Jo does not know. She has asked that question and will follow-up on that inquiry. Based upon an earlier conversation with the programmer, she did know that the it is stored one character here and the other one somewhere else in the layout.

E. Q: DOC - They had to enter the employee's base/total salary since NFC did not automatically process their GM employees. They entered the adj salary where the base is. Will this pay correct? A: Cliff - No because this value edits against special rate table and it will reject that rate. This only occurred this year because steps 8, 9, and 10 are at the maximum for the pay band. Employees at the step 10 received the locality. When you have multiple steps at the same salary rate, it creates a problem with the programs. Cliff recommended that all of their pay-band step 10's have 0's - next year. If your Step 9 goes to a higher locality rate, we have no way of identifying this in the system. Best solution is to switch to GS and put the employees on a step, in most cases this does not involve a large sum of money per employee. GM's need to be moved to GS to clear this up permanently. Otherwise, the problem will continue to exist.

F. Q: DOJ - transmit file - sunseting of T&A applications is FY 05 (Sept 05) so all agencies regardless of what software they are using, only going to sunset those that we support., STARClient and PC TARE; if you are using their own system and using transmit descriptors, where to put them....

G. Q: SBA - why are some of the GM salaries done and some are not irregardless of their PRD, would a 790 affect this? A: Glenda asked if they were GM's since PP 01. YES. How many affected? 16 - send those SSN's into the pay raise mail box. Are they in suspense? FA: no, on the TM098 report but what is deceiving is some applied and some didn't. BEAR60 in January is not the User ID on these actions; that's the original user ID on the first pay adjustment in January. PTO has some of these issues as well. Cliff indicated some got proc'd some didn't - go thru first report and send those SSN's to Pay raise mailbox. Glenda will get the rationale behind this and share with others. GM's are not paid on Tm098 and that maybe the issue.

H. Q: Mike - in analyzing some of the HCUP packages to sinq, 2 actions w/same eff and auth dates; is this a PERHIS problem in updating? I don't know if the actions went down that way. A: Jo indicated that the auth date can be the same if entered the following day....Cliff says entering a 903 ZOO and the auth dates can be the same and one date must be changed. Jo says it's a good time to bring up that you should NOT be entering actions with the same eff/auth dates...Mike says he can't go to the 2xx series in IRIS to see the auth dates....yes you can on the IR122 and 522; not on 222 is this a PERHIS problem or applied that way? Cliff & Lynda says it applied that way. FQ: didn't that used to be impossible? FA: not sure

I. Q: Multiple (cash) awards - modify the edits - still on target? Jo send out an email about this.

XIV. Attendees

A. In-Person

1. Clients - AG, ARC, CCR, CFTC, CSOSA, MHS, DOC, DOJ, FEC, FDIC, FMC, GAO, HUD, NCPC, OFHEO, Peace Corps, PSA, SBA, Smithsonian, & TR

2. NFC - Cliff, George, Jo, Jody, Lynda, & Mark

B. Via-Teleconference

1. Clients - MHS, IBWC, TR

2. NFC - Jerry, Penny, Glenda, Mose, & Steve L.