2017 NASCOE Negotiation Items

ITEM 1: LOAN APPROVAL AUTHORITY

Issue:  Currently, 1-FLP, Par. 25 outlines that SED’s, in conjunction with FLC, should identify areas of their State that could justify and benefit from CED having loan approval and servicing authority.

The office or area where CED would be designated by SED to obtain loan making and servicing approval authority must meet both of the following conditions.

– Direct and/or guaranteed caseload in the office or area is high, complex, or geographically challenging and FLM, SFLO, or FLP team servicing the office or area needs additional help.

– CED has sufficient time for additional responsibilities required to obtain and maintain loan making and servicing authority without negatively impacting CED’s current farm program obligations.

The announcement of the new Microloan-FSFL program is an exciting opportunity to reach a new customer base with a streamlined loan product, but an already heavy workload of FLP loans may be an obstacle in this implementation.

NASCOE Position: Many Farm Loan teams already have a broad portfolio of direct and guaranteed loans, including microloans. Their workload in some locations is at a level that already equates to delayed processing of FSFL applications.  This impacts our ability to deliver Microloan-FSFLs, which by nature are intended to be streamlined, easily accessible, and quickly processed.

A good number of CED’s have either educational background or work history that includes finance, and equips them to be a candidate for Farm Loan approval authority.

When loan applicants present to FSA with a proposed project and are assigned to work with FLO/FLM to determine credit worthiness, we may see situations where customers could be redirected to the FLP Microloan program, instead of the FSFL.

A change in policy that would allow for CED’s to have a limited Loan Approval Authority specific to FSFLs up to $50,000 or $100,000, this would allow for a much more streamlined implementation of the FSFL Program, specifically the recently announced Microloan-FSFL.

A suggestion is for CED’s be required to complete Phase 1 of the FLOT program as currently prescribed in 6-PM, Part. 13, but then complete Phase 2 in a modified format to include meeting the state-established credit quality standards on a prescribed number of independently prepared files, which consist only of FSFLs up to $50,000/$100,000, or comparable direct microloans.

This delegation of authority would apply to loan approval only for FSFLs. It would accomplish a significantly improved delivery of service for FSFL applications, particularly in counties without a full-time FLP presence.

DAFLP Response: According to 1-FSFL Handbook, the COC or STC is the approval official for FSFL loans, and FLP loan approval officials only provides a recommendation.  FSFL loans are not mentioned in the loan delegation section of FLP Handbook (1-FLP), only Exhibit 15 for FBP, which describes how to document the recommendation.  Our FLP handbooks only cover FLP functions and program policies and procedures. We believe changes for approval of FSFL Microloans be a Price Support/DAFP, rather than DAFLP, decision.

DAFO Response: This would be a sea-change in CED duties requiring major discussions with DAFO, HRD, and FLP. Likewise, any such changes in the duties of the CED would require the assent of respective county committees to determine if the CED would be able to assume added duties.

DAFP Response: We appreciate the suggestion submitted requesting a change to FSFL policy where CED’s can be trained to have limited loan approval authority for FSFL’s up to $50,000 or $100,000.

The National Price Support Division and Farm Loan staff will work together to develop a modified “no cost” loan approval authority training package.  At a later time, we will share more details about the loan approval authority training package and intended audience.

Agreement: As resources may permit, DAFLP and DAFP agreed to put together a pilot program to give CED’s authority to conduct financial analysis on Farm Stored Facility Loans under the County Committee approval limits. The COC would still have final approval up to $100,000.00 for all FSFL loans. NASCOE accepts the response.


ITEM 2: MAILING CONTRACTS TO OTHER COUNTIES

Issue: Mailing of original FSA-578 certifications and ARC/PLC contracts after they are faxed or emailed to the office when working in nationwide customer service. I took a certification for a county and emailed the signed 578 & map to the county, now I have to take the time to also make out an envelope, make a copy of the original and mail the original to the county office that I just emailed the paperwork to. What a waste of time and finances (46.5 cents for each certification I have to mail to different offices.) Plus why do I need a copy of the contract since I have the copy of the email that I sent?

NASCOE Position: According to procedure State and County Office Action State and County Offices that process nationwide customer service FSA-578’s must: • immediately FAX a copy of the signed FSA-578 and map to the producer’s administrative county • mail the original signed FSA-578 and map to the producer’s administrative county • maintain a copy of the signed FSA-578 and map. When taking a FSA-578 or ARC/PLC contract under Nationwide Customer Service we must immediately fax or email the administrative county a copy of the certification or contract and then we must mail the original to the administrative county and keep a copy.

To remove the redundancy of having a lot of paper work in both offices by eliminating the mailing of the FSA-578 and/or ARC/PLC contract when working in Nationwide Customer Service because it will already either faxed or emailed the information and the original can be kept on file in the office. The forms should be emailed or faxed and the original filed in the office that took the form. The emailed form could be stored in a sent folder with the County’s name on it, but the original would still be available if needed.

DAFP Response: DAFP is not opposed to only requiring the emailed or faxed copy of the document being sent to the administrative county of the farm, however, there are some concerns that must be addressed.

Generally, the policy for sending/receiving contracts and certifications is outdated when compared to the technology available.  While this technology is usually reliable, there are times when it fails.  Also, the scanned and emailed copy of a map or the faxed copy of a map is not of the best quality which would necessitate the mailing of at least the map from one county to the other.

Policy for the sending and receiving of certifications and contracts needs to be removed from each program’s policy handbook and included in handbook 1-CM.  DAFP will move towards developing a more user friendly format in handling producers that are using the Nationwide Customer Access function to enroll or certify farms.

Agreement: NASCOE accepts the response.


ITEM 3: AGLEARN TRAINING

Issue: Training on various topics is provided for through the AgLearn website and employees are to log on and take the required training when the training has been posted to AgLearn and before the deadline.

NASCOE Position: Notification of training requirements are ongoing throughout the year, some have several months to complete, some have a relatively short timeframe to complete the training. During heavy workload times, it is difficult to complete the trainings with the short turnaround timeframe.

Have all required training issued and posted to Ag Learn at the beginning of the FY and have the year to work on the required training, or at least be able to see all the training at once and when it is due to be completed and be able to manage the completion of it more efficiently.

HRD Response: HRD appreciates NASCOE’s idea in this area. However, the Ag Learn courses are typically created by a specific program area (civil rights or IT) or at the Department level.  As a result, HRD cannot load the courses prior to their availability from the appropriate area.  HRD will; however, make a note and load the course just as soon as it is available thus giving employees the maximum amount of notice to complete their training requirement and meet the established deadlines.

Agreement: NASCOE accepts the response. HRD will work with the AgLearn contractor to enhance the software to add an email notification feature for when courses have been added to an employee’s worklist and the possibility of a 30-day deadline notification reminder email.


ITEM 4: STAFFING/PERSONNEL

Issue: The SWA RSO pilot has become an approved organization and consists of employees in state offices throughout the southwest area. There have been several job opportunities within the RSO, but they only list state offices as potential duty locations.

NASCOE Position: By limiting duty stations to state offices, numerous highly-qualified candidates do not apply because they don’t want to move across the state. If a job can be carried out across state lines, it doesn’t make sense that the same job couldn’t be carried out remotely in a county office.

RSO positions, as well as many other NOF jobs that allow STO duty stations, should allow the selected employee to work out of a county office.

HRD Response: HRD will defer to DAFO on this issue for the RSO positions.  If DAFO wishes to pursue this option, HRD can certainly accommodate the “area of consideration” in the vacancy announcement process.   As a side note, there are some STO positions which are located in county offices.

As far as National Office positions, this would be left up to the selecting official’s discretion. However, once again, HRD could certainly accommodate the “area of consideration” in the vacancy announcement process.

DAFO Response: The previous SED RSO Council established a policy, which strongly encouraged the duty station of RSO employees in SWA STO’s; however, they also afforded some latitude to the Selecting Official (in consultation with RSO Manager) to duty station an employee in a County Office.  A compelling reason for doing so was required.  Only one such request has been approved.

DAFO has discussed this item with the Manager of the RSO, who feels that the RSO needs its employees co-located, not scattered.  Concentrations of employees provide for a number of benefits including training, cross-training, and enhanced privacy protection because of the nature of the work performed, all of which ultimately provide payback to the end-user/customer in form of available and informed personnel to respond rapidly and efficiently.

There is also the issue of space to accommodate both the newly hired RSO employee in small offices.

Agreement: This item will be considered in the future. They will discuss the possibility of doing remote positions with the RSO management.  NASCOE accepts the response.


ITEM 5: CRP CONTINUOUS CONTRACTS

Issue: 7 CFR 1410.22 states “For general signup and continuous signup contracts except grasslands, mid-contract management must be conducted to implement management activities, such as disking and prescribed burning according to an approved conservation plan, as part of the CRP contractual obligation on all contracts entered into under general signup and continuous signup, as specified in 7 CFR 1410.30”.

NASCOE Position: Continuous CRP offers are made and approved based upon a determined resource need on the offered land. By requiring that the cover established on this resource concern be disturbed by a mid-contract management activity, it defeats the purpose of establishing a practice to correct a resource need

To maintain the intent of the Continuous CRP program, which is to address a resource concern and incorporate the appropriate practice to correct the resource concern, an update to the regulations needs to be made. Not all CRP contracts need to have mid-contract management practices which will disturb the established cover.

DAFP Response: The requirement for at least 1 management activity during the contract period for all practices, except CP87 and CP88, is to ensure the approved cover, applicable plant diversity and wildlife benefits are maintained, while ensuring the resource concern(s) continues to be addressed.  Management activities are site specific, developed in coordination with the appropriate technical agency with the experience necessary to ensure the resource concern(s) are not jeopardized during the approved management activity, and are included as part of the producers conservation plan of operations.  This is applicable to all practices, not just those enrolled under the continuous CRP signup provisions.  In addition, participants may receive cost-share for approved management activities to lessen the cost of such activities and further ensure the approved cover is in compliance with the practice standards and conservation plan of operations.   Over 30 years of experience with CRP cover establishment, maintenance, and management activities has shown that appropriate management activities performed at the appropriate time helps ensure the approved cover, plant diversity, and wildlife benefits are present and maintained throughout the contract period.  Such activities also assist participants in maintaining compliance with their contract requirements, which results in fewer contract violations for non-compliance, fewer contract terminations, and fewer required refunds of payments.  In addition, the required management activities ensure that tax payer funds are used in an efficient and effective manner for the benefits obtained, while treating all participants in a fair and equitable manner.

Though not specifically referenced in 2-CRP (Rev 5), Mid Contract Management is required by the CFR and Statute.

As you have referenced, 7 CFR 1410.22 states “For general signup and continuous signup contracts except grasslands, mid-contract management must be conducted to implement management activities, such as disking and prescribed burning according to an approved conservation plan, as part of the CRP contractual obligation on all contracts entered into under general signup and continuous signup, as specified in 7 CFR 1410.30”.

Further, Section 1232(a)(5) DUTIES OF OWNERS AND OPERATORS.

(a) IN GENERAL — Under the terms of a contract entered into under this subchapter, during the term of the contract, an owner or operator of a farm or ranch shall agree (5) to undertake management on the land as needed throughout the term of the contract to implement the conservation plan.

Agreement: Farm Bill discussions are going on currently and there could be some discretion used in the future to work with NRCS technical determinations. At this point, mid contract management could be modified but it must be followed.

NASCOE accepts this response.


ITEM 6: COC ELECTION BALLOTS

Issue: There are no clear instructions on the election ballot that a title is required if the voter is an entity.

NASCOE Position: Clear instructions should be added to the election ballot stating that a title for an entity is required.

Under Step 3, Sign on label to the right, it says “You must sign on the label next to Signature (By) or your ballot cannot be counted”, we could add an additional sentence that states, If you are an entity, trust, corporation, partnership, etc., you MUST include a title such as trustee, member, etc. or your ballot will not be counted. This sentence could even be in bold or red print.

DAFO Response: Below is what the label looks like now. The suggested addition could be added under the directions for Step 3.  The label has not changed for years, and there have been no issues so far.  However, it is doable. We will have to discuss this matter with MSD and the various contractors involved in the ballot process.

Agreement: NASCOE accepts the response. DAFO has agreed to insert a statement (note) in red to list example titles for persons to enter for signing authority. DAFO also agreed to update procedure to allow County Committee’s discretion to determine validity of individuals signing on behalf of an entity without entering a title on the ballot.


ITEM 7: COT OPENINGS AND PLACEMENTS

Issue: Currently COT’s are hired, trained and then apply for county office openings. During 2015 negotiations, NASCOE proposed hiring COT’s for the county office where the COT would be permanently placed and then training would take place.  NASCOE noted that this proposal would increase applications from individuals who wanted to be in that specific county which would lead to a stable county office into the future.  Management expressed openness to consider NASCOE’s suggested changes and NASCOE provided a white paper with concepts on how these changes might benefit county committees looking for stability and provide more opportunities for county office employees.

NASCOE Position:  Just like the FLOT position, NASCOE feels that a COT should be hired for the county office where the CED position is needed.  Further, this proposal is of high priority for our membership.  Management has not formally responded to NASCOE’s suggested changes to the COT program hiring process.  NASCOE requests that management respond in writing to the concepts to allow further discussion on this topic and search for solutions to NASCOE’s and management’s differences.  A PT would be able to apply for a specific CED position and be trained for that position, in other than for hard to fill positions

The COC would make the selection for the county and the state committee would actually hire the COTS.   The position would be advertised for a specific county, the application is done through USAJOBS, the STC selects COTS and would submit 3 names for county openings. (This item was also submitted in 2016)

HRD Response: The decision on how to select and train COTs as well as place them upon completion of the training program is an agency choice.   Obviously, there are pros and cons associated with the current at-large method as well as the specific location method which NASCOE supports.  There is certainly value in the at-large program as it allows states the ability to hire and train COTs before actual vacancies occur.  This way, when the vacancy does occur, there are individuals ready to be interviewed and selected for the CED position rather than just beginning the training process.  HRD will defer to DAFO for their determination on what is best for the States and County Offices on this issue.

DAFO Response: Not all FLOTs are hired for a specific office, as the past.   DAFO continues to believe that states cannot determine with complete accuracy where vacancies will be in the future.

Agreement: NASCOE accepts the response.


ITEM 8: ENHANCING MIDAS SOFTWARE

Issue:  Currently MIDAS users can search farm number, tract number, owner, operator etc.  Being able to search in Midas by CRP contract # would be useful for farms that have multiple contracts on the same tract number.  For instance, if a farm was reconstituted and the farm number changed, every CRP contract would have to be revised. Every field with CRP would have to be revised in Midas as well to add the suffix to the CRP contract #.  If you could search by contract, you could ensure that all the field numbers were updated correctly.

NASCOE Position: Modify the search options in MIDAS to include being able to search by CRP contract number and have all CLU’s associated with that shown in the search results. This will lead to fewer omissions on the CRP mismatched report.

DAFP Response: This suggestion is being added to our list of enhancements and will be implemented as soon as resources and budget can be allocated to the enhancement.

Agreement: NASCOE accepts the response.


ITEM 9: MODIFY THE CCC-576

Issue: The Issue is that when you enter multiple losses for a producer and the notice of loss application prints, it prints to a continuous run of pages. The first page of the CCC-576 Notice of Loss, has the producer’s name, crop year and state and county code listed.  However, the continued pages of the CCC-576 do not have any information listed regarding to name, crop, year, state and county code or page number.  If the pages get out of order or mixed with another producers notice of loss you cannot tell which page goes where.

NASCOE Position: Modify the CCC-576 to include the producer’s name, crop year, state code, county code and page number in the header to each page of the CCC-576 when it prints.

DAFP Response: This enhancement is being adopted and will be implemented in the near future.

Agreement: NASCOE accepts the response.


ITEM 10: USING CO SLOTS AND HIRING PROCEDURE TO FILL GS POSITIONS

Issue: Several states have routinely utilized CO ceiling slots to fill positions for the GS side. More and more often this is being done because it is usually less complicated and quicker than going through the GS hiring procedure.  Many times the intent is to convert the position to GS in a few months but there are several cases around the country where this has not been done or has not been done timely.

NASCOE Position: NASCOE understands that FSA is understaffed both on the CO and GS side and that SED’s have the ability to flex ceiling slot from CO to GS and vice versus. While this might be a tool that is available for states to consider it should not be a common occurrence and the slots should revert back to the original ceiling as soon as possible.

HRD Response: While this can be done, HRD would caution offices on doing this as a way to circumvent merit promotion hiring policies on the GS side. This hiring method should truly be used when we don’t have an FTE available for the position needing to be filled.

DAFO Response: The “flexing” of staff years from CO to GS and vice versa is a tool used by some SED’s to mitigate short-term staffing short falls and meet critical needs. It should be understood that positions are not flexed, rather it is the staff year (I.e., funding) that is flexed to fill a critical need.   It continues to be DAFO’s policy that the flexing of staff years is a short term situation and not a common occurrence.  It is DAFO’s policy that approved flexing does not carry beyond the fiscal year for which it is approved.  In recent years, many State’s individual employment levels have been below their State ceiling levels and the need for flexing has been minimal. 

Agreement: NASCOE accepts the response.


ITEM 11: INCLUDING THE NASCOE NEW HIRE PACKET PART OF EXHIBIT 6 IN 28-PM

Issue: NASCOE and management have agreed in previous negotiation meetings that State Offices shall make NASCOE membership informational brochures and application forms available to all new hires. This has been communicated to SED’s and AO’s through emails and memos from DAFO to the state offices.  However, with routine turnover in SED’s and DAFO, NASCOE has to make subsequent requests that State Offices be reminded of this agreement.

NASCOE Position: If the membership informational brochure, membership application and FSA-444 were added to the new hire checklist in exhibit 6 in 28-PM it would be made available to all new employees as previously agreed to by NASCOE and Management.

HRD Response:  While HRD recognizes NASCOE as an employee organization, we do not feel that putting informational material in our agency handbooks is appropriate.  Exhibit 22 of Handbook 22-PM, contains a copy of the Labor-Management Relations Agreement between USDA/FSA and NASCOE, and Section 3, Item 15 of this handbooks specifically states that solicitation of membership shall be conducted during non-duty hours of the employees involved.

Agreement: NASCOE accepts the response. HRD has agreed to add the FSA-444 to the checklist of required forms in the exhibit of 28-PM in a handbook update. HRD also agreed to insert a link to all employee associations for information in 28-PM.


ITEM 12: IT CYBERSECURITY

Issue: Our Country is in an ongoing battle of cyber threats and attacks. In fact, several thousand Federal employees have had their SS#’s stolen. After which, and over the past 18 months, Federal employees have been offered a free service of identity protection through CSID.

NASCOE Position: The threats on our identity are still very real and the need for cyber security has only increased. Would like to see all employees offered Identity protection during their employment years and possibly at a reduced cost for retirees.

HRD Response: The decision as to what type of credit monitoring and identity protection employees/retirees will receive as a result of the cyber incidents falls with the jurisdiction of OPM rather than HRD.

Agreement: NASCOE accepts the response.


ITEM 13: IT/WEBTA

Issue: WebTA 4.2 is not user friendly. The screens are hard to read/follow when loading time and attendance. The screens in the new WebTA system are very hard on the eyes when reading them, and program codes are not listed in order.

NASCOE Position: Several modifications would greatly increase the efficiency of recording our time and attendance. Those would include differentiating each line, grouping the activities alphabetically and locking the header so that the day is always visible when you scroll to the bottom of the entries.  In addition, it does not read very easy when the CED’s time and attendance is printed for the County Committee’s review and approval.

OBF Response: OBF concurs with this recommendation. OBF and HRD are working together to have a change implemented by the NFC to address this at a future date to be determined.

HRD Response: The WebTA 4.2 dashboard issue came up after implementation. NFC responded that the WebTA 4.2 system is 508 compliant and the current display is as designed.   NFC advised that any requested screen changes to the application would be an enhancement. On February 27, 2017, HRD submitted a follow-up inquiry to OHRM to determine whether USDA has any plans to requisition the enhancements and if so, what specifically, and when might they be available in WebTA 4.2.  HRD will continue to follow-up on this issue.

Agreement: The request has been made to list activities alphabetically. There has been assurance from Kronos to simplify WebTa.  To ensure the headquarters team is notified of the problems.  They are working on setting up a SharePoint site for state offices to input problems and issues.  They are aware that there are attempts to address issues and this has bypassed headquarters and this is not a good situation.  Everyone is facing the same problems.  There are people from the field involved in testing.  NASCOE accepts the response.  A list will be compiled and submitted through STO.  A NASCOE POC (Dennis Ray) will have access to the SharePoint site to submit issues.


Items from 2016 NASCOE Negotiations (Resubmitted)

ITEM 2: SHARED MANAGEMENT PROCEDURE

Issue:  “Before STC approval of the establishment of a permanent shared management operation, the SED will consult the NASCOE state affiliate.”  At present, many STO’s are not following this procedure.

NASCOE Position: NASCOE recommends that SED’s be reminded of applicable handbook procedures in 27-PM, paragraph 52C. SED’s are to consult in pre-decisional format before the establishment of a shared management operation.

HRD Response:  We agree that the policy requires the consultation and defer to DAFO on any reminders to or reinforcement of the policy with the States.  We do stand ready to assist if any clarifications or changes to the handbook need to be issued.

DAFO Response:  States routinely send in requests for approval of shared management proposal.  DAFO always ascertains if consultation has taken place.  If this is not happening, we should be informed.

Negotiation agreement: NASCOE would like an official response from the state association attached to the decisions regarding shared management to ensure the NASCOE state affiliate is involved. DAFO will review this issue to come up with a solution to show a written NASCOE position accompanying the State request for permanent shared management.  A response will be sent back to NASCOE within 30 days.  This is to ensure the states are following current policy.  NASCOE will provide feedback in the consultation.  Written documentation of the consultation with the state association included in the submission to DAFO for permanent shared management. An email will be sufficient for a response.  HRD can draft policy for DAFO review to be submitted to NASCOE.

DAFO Response: Shared management is and has been a reality for many years. Given budgetary and   legislative restrictions, we see no realistic alternatives in the near future.  DAFO approves all shared management requests and ensures that NASCOE affiliates have been contacted and that all requisite COC and STC approvals have been obtained. 

HRD Response: HRD will defer to DAFO on this issue; however, if the decision is made to incorporate this into the handbook, HRD can certainly update Handbook 27-PM, Paragraph 52C accordingly.

Agreement: Management will agree to consulting the associations during the proposed establishment of a permanent shared management situation and having COC involvement.   There will be an amendment to 27 PM to include such reference.  NASCOE accepts this response.


ITEM 4: TEMPORARY SHARED MANAGEMENT-LENGTH OF TIME

Issue:  Provisions in 27-PM paragraph 53C “temporary shared management operations shall not exceed 120 calendar days.”  At present, many STO’s are not following this procedure.

NASCOE Position:  NASCOE recommends that SED’s be reminded of applicable handbook procedures. Procedures shall be followed in instances where shared management operations exceed 120 days by SED’s meeting with COC’s to “work out a permanent solution.  Any exceptions to the 120 calendar day limitation shall be approved in advance by DAFO.”

HRD Response:  We concur with the statement of the policy and defer to DAFO on any reminders to or reinforcement of the policy with the States.  We do stand ready to assist if any clarifications or changes to the handbook need to be issued.

DAFO Response:  All extensions are approved by DAFO after it is determined how long the shared management operation will continue and what plans the State has to end it.  As was have reiterated many time, budgetary and current Congressional restrictions prevent us from taking necessary steps to ease the situation of so many shared management office.

Agreement: DAFO agreed to have temporary defined as 6 months and the review will have attached COC minutes showing the consultation with the state affiliate of NASCOE was done.

DAFO Response: Given the many variables is each situation, it is often difficult to determine prospectively when it might be feasible to discontinue a share management operation. DAFO always asks the state what their future plans are.

HRD Response: The 120 days has already been changed to 6 months in Handbook 27-PM. As soon as Revision 2 is released, this will be visible to all employees.

Agreement: Management agreed to have COC’s involved in shared management extensions. DAFO agreed to have temporary defined as 6 months and the review will have attached COC minutes showing the consultation with the state affiliate of NASCOE was done.

NASCOE accepts this response.

Programs Submission Response: Farm Reconstitutions and Transfers

ISSUE:
Difficulty in tracking reconstitution history and county transfers

FACTS:
It can be difficult to trace the history of a farm after multiple recons. MIDAS currently shows the “Combined from” and “Divided from” information in Farm Records. 

SOLUTIONS:
Would it be possible to include the Combined from and Divided from information print on the FSA-156EZ?

NATIONAL OFFICE RESPONSE:
Thank you for submitting the concerns with tracking reconstitutions and the suggestions for the FSA-156EZ. We recognize that the ability to track reconstitutions has been a pain point with the field staff since the expected reconstitution reports were not able to be implemented immediately in MIDAS CRM. I am hoping that the software update that occurred this last weekend with MIDAS Release 2.19 provides the tools and reconstitution reports the users are needing to assist with tracking the history of a farm or tract through the completed reconstitutions. Please see Web Transmittal No. 536 for additional information on the new reconstitution ID and reports that are now available. A notice will also be posted in the near future with additional information and instructions.

While the new reports in CRM Farm Records will not reference the reconstitutions completed in CRM prior to the software update, all reconstitutions completed from this time forward will be assigned a Reconstitution ID number and reports can be generated to identify the parent and/or child farms and tracts associated with the specific reconstitution. Concerning the FSA-156EZ, this initial release of the reconstitution reports did not include populating the FSA-156EZ with the reconstitution ID. This has been identified as a needed update. We will also look into adding the “combine from” and “divided from” on the form. Adding the reconstitution ID and the additional reconstitution data to the FSA-156EZ will be an enhancement to the existing functionality and will be subject to prioritization and funding.

There currently is not a plan to add a County Transfer report in CRM Farm Records, but there will be a County Transfer report in the new reporting application that is being developed. Hopefully this report will assist counties with tracking the farm transfers as needed.

Programs Submission Response: Measurements in MIDAS

ISSUE:
When measuring lines in MIDAS with the measurement tool, the lines disappear when measuring multiple lines. They do not stay on the screen.

FACTS:
It makes it hard to have a guideline for a split when the measure line disappears.

SOLUTIONS:
Suggestion would be to be able to keep each line on the screen until an “erase all” or “delete measurements” icon was selected. This way multiple measurements could be made and used for splits.

NATIONAL OFFICE RESPONSE:
You are correct that the measurement service tool available from the General GIS Toolbar in CRM does have limitations. As you stated, the user is limited to only a single measurement session at a time. We can look into adding additional functionality to the measurement service tool, though this enhancement will be subject to prioritization and funding.

 In the meantime, I want to make sure that users are aware of the existing functionality of the measurement service tool. Users can draw out multiple measured boundaries as long as the segments measured are connected and drawn in a single measurement service session. The measurement service graphics will also stay on the screen so users can use them as reference when delineating a field with the drawing tools as long as the user was in an Edit mode prior to drawing the measurement service. Additional functionality includes the ability to “snap” to the measurement service graphics while delineating the permanent boundary using the regular snapping functions (Holding the control-key and clicking on a vertex of the measurement service boundary).

Below is an example of measurement service using the Draw Polygon option:

midas example

I am in an Edit mode. The Draw Polygon tool was used to measure a new area. The length/distance of each segment of the measurement service is labeled on the screen. Once I select the field that the measurement service is within (and zoom to the correct extent), the GIS editing tools become active and the measurement service stays on the screen. The new boundary can be delineated and the snapping function can be used to snap the new boundary to the measurement service graphic. The measurement service graphic will stay on the screen until a Save and Sync is completed.

 

Programs Submission Response: CARS & MIDAS Interface

ISSUE:
Re-entering FSA-578 information into the CARS software after a reconstitution has been performed.

FACTS:
The amount of time it takes to re-enter crop certification after a recon has been performed on the farm is inefficient and time consuming. We are replicating data that has already been manually loaded once.

SOLUTIONS:
Link MIDAS CRM Farm Records software, specifically the reconstitution aspect to CARS. When completing a recon, the software could ask us whether we want to retain or discard the current FSA-578 information on the child farm(s). Most of the time, the basic field level data from CARS will remain the same. It would be much more efficient if there was a way to roll the information over into the child farm(s) in CARS, and prevent the need for reloading the information.

NATIONAL OFFICE RESPONSE:
This is something that we have been wanting to do for years. We have this item in our list of enhancements.

 

Programs Submission Response: MIDAS KFC Requests

ISSUE:
Business Partner-KFC requests to inactivate producer record.

FACTS:
Producer record inactivation requests must be submitted to the STO specialist in charge of Common Management for process through MIDAS BP. Producer inactivations include both those who have social security and/or entity ID numbers established with IRS and producers who do not receive any payments and are assigned a temporary ID number by MIDAS.

SOLUTIONS:
Producer inactivations for those with temporary ID numbers could be taken care of at the county office level. The potential for overpayments due to inactivation does not exist since these producers have not received payment. This would result in STO specialist time being spent on more important issues and result in cost savings.

NATIONAL OFFICE RESPONSE:
We cannot implement the proposed solution, for the following reasons.

Handbook 1-CM (Rev. 3) subparagraph 177 B defines a long list of criteria that must be met prior to inactivating a customer. The criteria is not limited to non-receipt of payment.

Temporary IDs are not permitted, but the customer can have “No Tax ID” recorded.  Customers with “No Tax ID”:

  • Can be recorded in BP as a Farm Loan Customer
  • Can be recorded in BP as an NRCS Customer
  • Can be recorded on a Farm

Even if the customer did not have any payments issued to him, if any of the above criteria are true, or any others defined in subparagraph 177 B, the customer record CANNOT be inactivated. It is for this reason that it is critical for the Business Partner State Security Officer (SSO) to review and approve all requests to Inactivate a customer record.

The inactivation request process was not automated in SCIMS, even though the provisions were the same. COFs were required to email or call the STO to request an inactivation. In CRM, the KFC Request workflow was designed as a process improvement to streamline and expedite those requests.

President’s Notes from NASCOE Meetings with Management

 

NASCOE Vice President, Dennis Ray, and I recently visited WDC and feel that we had a really productive trip. We met with the following people in management:

  • Val Dolcini, FSA Administrator
  • Mark Rucker, Deputy Administrator of management (DAM)
  • Greg Diephouse, Deputy Administrator of Field Operations (DAFO)
  • Radha Sekar, Chief Financial Officer (CFO)
  • Brad Pfaff, Deputy Administrator of Farm Programs (DAFP)
  • Chris Beyerhelm, Associate Administrator
  • Mike Schmidt, Associate Administrator
  • Thomas Mulhern, Human Resources Director
  • Darren Ash, Chief information Officer (CIO)

We met with the Deputy Administrator of Management (DAM), Mark Rucker, on leasing, phone, and office environmental conditions, space issues and wavier requirements. DAM understands our county office environment and needs. We also talked about the CISCO phone system and the upgrades that seem to be helping improve the system. There are a few environmental issues across the country that were discussed, and DAM agreed to follow up on those. DAM is always receptive to improving our working conditions.

We met next with Greg Diephouse, Deputy Administrator of Field Operations (DAFO) and his staff Linda Treese, Pat Spalding, Rick Pinkston, and Trina Brake. DAFO agreed to send out a NASCOE Membership Packet for STO use with new CO hires. DAFO has mailed every SED and STO a NASCOE Membership packet. DAFO encourages all employees to join their respective associations and realizes the importance of each association’s mission. NASCOE appreciates DAFO’s effort and support with this, and many other issues. The status of the shared management negotiation item was discussed. There should be an amendment out soon that requires written confirmation that a proposed shared management arrangement has been discussed with all the COC’s involved, as well as with the NASCOE State Association President. Other topics included COC authority, BTO update, staffing issues, temps, county office footprint and structure, performance issues and the NAPA Study.

Radha Sekar, FSA Chief Financial Officer (CFO), and Bob McGrath discussed budget, workload, and staffing. The CFO says we are not tremendously understaffed, as most CO employees think, because we continue to meet most of our program deadlines and get payments out timely. We discussed several staffing issues, including that our FTE’s aren’t figured considering the permanent disaster programs like LFP and ECP. It was agreed that some administrative funds should come with the implementation of these types of programs. There currently are no provisions for this, and it was suggested that NASCOE work with DAFP on this issue. NASCOE asked about the workload tool and its release. NASCOE still feels strongly that we are understaffed across the country and that a workload measurement tool is needed. The CFO has agreed to share some data from the proposed workload tool with NASCOE for constructive feedback.

Brad Pfaff, Deputy Administrator of Farm Programs (DAFP), and his staff Brad Karman and Kim Viers (on a detailed assignment) met with us on COC authorities in 2-CRP. NASCOE has asked for DAFP to reinstate COC authority to approve CRP-1’s and delegate that authority to CED’s. The current handbook policy allows the CED to approve CRP-1’s without delegation. DAFP has promised to try and reinstate this policy. DAFP recently has asked NASCOE to review certain information on ACRSI as it would pertain to county office operations. NASCOE has had a task force working on ACRSI for over a year-and-a-half and appreciates management allowing us to provide constructive feedback on its impact to the field. NASCOE had asked DAFP for some relief for those states that just learned that their forage reporting date would now become November 15th. DAFP waived late file fees for those states for thirty days. NASCOE also shared some concerns with other agencies having the ability to make MIDAS edits. DAFP didn’t feel that any of these edits would interfere with FSA, but agreed to go back and look at a few concerns that NASCOE membership had. We wrapped up the DAFP session discussing our geospatial needs.

Dennis and I met next with Chris Beyerhelm, Associate Administrator, on directives, staffing, cost analysis update, county office footprint, COC authorities, WEBTA, and GovDelivery. The Associate Director intends to get all of our directives updated and simplified. As always, staffing and budget issues dominate most of the conversations with our Associate Administrator.

Val Dolcini, FSA Administrator, discussed what he thought FSA’s future looked like. He felt that NASCOE’s role with employee issues and negotiations has been very effective. He hopes we will continue to have the all-association negotiation sessions. The Administrator feels that there is a benefit to all the associations being in WDC at one time. The Associations, including NASCOE, feel that the joint negotiations meetings have been successful. NASCOE thanked Val for his leadership and the support he has given NASCOE during his administration. He has allowed us to work with all of FSA’s management personnel on a lot of different issues during his time in WDC.

Mike Schmidt, Associate Administrator, and his assistant, Katina Hanson, met with us on ACRSI and COC authority. The Associate Administrator supports the COC system and its role. As new farm bill talks begin, NASCOE will continue to stress the importance of a strong COC delivery system.

Thomas Mulhern, Human Resource’s Director, and Barbara Boyd, Deputy Director for Human Resources, met with us on the status of the PT position description task force. This task force has met with some success on rewriting PT position descriptions. NASCOE had asked for a task force, which resulted from a negotiation item from last year. The task force is also looking at adding a position with promotion opportunities for PT’s as well as continuing to look into the possibility of a grade reclassification. We also discussed the CO hiring process. It has been mandated that the CO hiring process will start using a questionnaire to replace the current KSA’s. NASCOE will have representation on this task force as well.

Darren Ash, Chief Informational Officer (CIO), met with us and gave us an update on IT issues. We discussed MIDAS edits and ACRSI. The CIO addressed our ability to have reports and query information that we need to perform our job at a more efficient level. There should be some much awaited information on this coming soon. We discussed the IT Steering Committee and its future. Darren has worked hard to communicate well with the field on all of our concerns and issues and is making progress in resolving them. NASCOE appreciates the time that the CIO gives us and the personal touch he has given the field in addressing our needs.

Respectfully Submitted by,

Wes Daniels
NASCOE President

Programs Submission Response: CCC-505 and CCC-517 Tools Enhancements

ISSUE #1:
CCC-505 tool, ‘Complete/Print’ button reminder. Selecting the ‘Complete/Print’ button sends a workflow to the CED, who should not execute decision until verifying that all signatures have been obtained. Why not change it so that the form can be printed at the “Save as Draft” option?

FACTS #1:
Some COFs are doing manual forms to get signatures and thus doing dual duty to ensure that everything is obtained before the CED approves in MIDAS. Having the print option at the draft level would ensure that we have a form, without having to do a manual, to get the signatures, but it wouldn’t be put on the CED’s worklist for approval until after the signatures are obtained and the PT goes back in and clicks “Complete/Print.”

SOLUTION #1:
Either change the “Save as Draft” option to “Save as Draft and Print” or add a “Print 505” option separate from “Complete/Print.”

WDC RESPONSE #1:
This suggestion is not being submitted as a future enhancement. Through the automated CCC-505 process, the form cannot be printed until the base acreage reduction request has been submitted for approval in the system.  This ensures that the reduction request submitted for approval matches the form printed for signatures. The concern with allowing the form to be printed as a draft is that the producer could sign the draft form, but changes to the base reduction data in the system could be completed (after it is printed) and then submitted and approved. In this instance the signed CCC-505 does not match the approved reductions.   


ISSUE #2:
Currently the CCC-517 form prints only the information for base acres that are being proposed for a change when completing the form through MIDAS.

FACTS #2:
When more than one base is present on a tract, this can be confusing for a producer to see only the base acres that are being revised.

SOLUTION #2:
Having all bases print on the CCC-517 would be less confusing for producers. This would let them see all the bases that are still present on the tract of land, and not just list the base that is being revised. Would this revision be possible?

WDC RESPONSE #2:
Thank you for this suggestion. With the current design of the automated CCC-517 process, all base crops are available as an option to redistribute within the wizard. It is only when the redistribution request is submitted and the form is available to be printed, that the base crops not involved in the redistribution are omitted from the form. It is believed this would be a minor change to the application to include all crops on the printed CCC-517 form. This suggestion will be submitted as a future enhancement for management to prioritize. 

Programs Submission Response: MIDAS GIS Enhancement

ISSUE:
MIDAS/GIS  

FACTS:
After selecting Save and Sync in MIDAS following a CLU revision, the zoom resets to the farm level, requiring the user to select the tract again, then pan and zoom back to the area of interest in which they were working

SOLUTIONS:
After Save and Sync is selected in MIDAS, it would be beneficial for the GIS screen to return to the most recent view. If the user wants to then return to the whole farm view instead, it would simply require the user to click once on the farm level in the menu, which would be far more efficient than the current method.

NATIONAL OFFICE RESPONSE:
Returning to the farm level following a save and sync and the need to select the tract again and then zoom and pan back to the specific area of interest are documented pain points in the current CRM Farm Records design. As planning for future enhancements and alternative approaches for farm records functionality take place, elimination of these pain points is at the forefront of considerations.

Under the current design at the time GIS edits are saved and passed to CRM the GIS layers visible to the user change. This change occurs because the software switches from edit mode to display mode. When this change in modes occurs, the system resets GIS display and zoom settings to pre-established default values. Additional logic must be added to the software in order to maintain the specific location and zoom scale that existed at the time GIS edits are saved and synced. It is expected that this improved logic will be included as part of a larger plan to redesign GIS and Farm Records.

Programs Submission Response: Business Partner Enhancement

ISSUE:
MIDAS Business Partner-Representative Capacity  “In-Creation” records

FACTS:
When reviewing the Representative Capacity record in MIDAS it’s easy to overlook an “In Creation” status. If pending records in creation were easier to identify this would help in reducing errors.

SOLUTIONS:
If the words “In Creation” were in a RED font on the Representative Capacity tab it would be easier to identify those particular records.

NATIONAL OFFICE RESPONSE:
We will work with the CRM/Business Partner development team to discuss options. Red font would likely not be 508 compliant, but there may be alternatives that are. If there are users that are still having difficulty identifying Active vs. In Creation entries, we will find a solution to make them stand out more.  We appreciate the suggestion, I will follow up with you when I have a proposed solution.

ADDITIONAL NATIONAL OFFICE INFORMATION:
MIDAS Development team was able to include an enhancement for this issue in the MIDAS 2.16 Release, this past weekend (OCT 15-16/2016). The full details of the release are covered in Web Transmittal 492. In Representative Capacity, the Status column will be sorted in descending order so that ‘In Creation’ entries will be displayed at the top, followed by ‘Active’ entries. This should help field offices quickly and accurately identify the current status of the RepCaps.

 

Programs Submission Response: MIDAS

ISSUE:
An office indicated that they haven’t had a MIDAS Death Master worklist item in several months.  They are aware of producers who have deceased and were wondering if there is a problem in the downloads. It may be that the Social Security folks haven’t been informed of those particular individuals.

FACTS:
I know the CO can manually record individual deaths in MIDAS, but I wanted to follow up just in case there was something larger going on that needed following up on.

NATIONAL OFFICE RESPONSE:
The Death Master file has been “on hold” for 3 weeks because we are transitioning from a 3rd party data source, to getting the data directly from SSA. Once the SSA data source is flowing, you may see a large number of workflows come thru. An IB will be issued when that occurs, as an FYI to COFs.

However, if you haven’t had any come through for months (rather than 3 weeks), it’s just likely that those customers haven’t been reported via that 3rd party data source to FSA. The main reason for getting the data directly from SSA is to cut down on the lag time it takes us to get the DOD updates.