| E-Rate News for the Week |
| December 6, 2004 |
|
|
|
The E-Rate News for the Week, prepared by E-Rate Central, is sponsored by the
State E-Rate Coordinators’ Alliance (“SECA”). Official SLD news is provided in
the "Important Notices" section of the
SLD’s Web site. Additional E-rate information and archived copies of
this newsletter are located on the E-Rate
Central Web site. |
| Wave 10 funding for FY 2004
and Future Funding Outlook |
| Wave 10, the first new wave of funding commitments
for FY 2004 since the freeze began in August, was released on Friday, December
3, 2004. Funding in this wave was $317.1 million for 5,345 applicants. Total
funding for FY 2004 has now reached $1.08 billion.
Although Wave 10 is good news for a number of applicants, it is important to
note that the underlying accounting issue that led to the four month funding
freeze has yet to be solved. Without a change in procedures or law, future
funding will depend upon the accumulation of new and/or unobligated cash. This
will stretch out the release of new FY 2004 commitments well into 2005 with new
funding waves being released roughly once a month.
New Internal Connections funding, which the SLD had begun funding at the 90%
level prior to the freeze, is still frozen. No additional Priority 2 awards are
expected until the SLD has cash reserves exceeding the level of pending
Priority 1 commitments.
Prospects for a near-term solution to the accounting problem hinge on Senate
action over the next week or two to approve a measure excluding E-rate funding
from the Anti-Deficiency Act, at least until the end of 2005. The House has
already passed HR-5419 which contains such an exclusion. There is an equivalent
provision in a proposed Senate bill, S-2994, but action on it has been stalled
as a result of unrelated initiatives and concern dealing with boxing industry
reform and spectrum relocation.
In the absence of a legislative solution, consideration is being given to
pre-commitment notification letters. Under this approach, applicants would be
notified when their applications had been reviewed and would be given a
preliminary indication of the level of "approved" funding, but would be told
that final commitments would depend on additional cash availability. This would
provide applicants and vendors with information that may be useful for planning
purposes, but clearly does not solve the underlying problem.
|
| New PIA Initiatives Dealing
with Ineligible Functionality |
| The eligibility of network equipment serving, or
capable of serving, both eligible and ineligible functions is becoming an
increasingly difficult issue for applicants and PIA reviewers alike. In an
apparent effort to be both fair and precise, PIA is starting to request more
detailed and complex information dealing with such equipment as routers and
firewalls. While both devices are basically eligible, both often include
inherent capabilities to support ineligible remote access or VPN functions.
In the past, the typical approach taken by PIA in dealing with multi-function
routers, for example, was to require applicants to sign certifications that
such routers would not be used to provide remote access (or, more generally,
any ineligible function). The prohibition against remote access usage was meant
to avoid having E-rate funded equipment being used to provide general public or
other non-educational services. An outright prohibition, however, has the
effect of disallowing valid, or at least ancillary, use of such equipment to
support remote maintenance and other necessary applications.
Recently we have seen PIA inquiries that go one or two steps beyond strict
certifications on the use or non-use of equipment for ineligible functions. The
following is an example of a more detailed certification of eligibility than we
had seen before.
|
|
In general, E-rate funds are available to provide connectivity. Other uses are
not eligible for support. The products/services being requested may have some
ineligible functions including but not limited to: Content filtering, network
management, proxy services, caching, and Virtual Private Networks (VPN’s). In
order for us to further evaluate your request, please refer to the areas below
and indicate the statements that apply to you.
Do you plan to use any ineligible functions as part of your request for
Products or Services?
Yes____ No____
If no, please sign and date the following statement:
I certify that we will not utilize the ineligible functions contained within the
requested product or service and that we may be audited. If we are found to
have used these products/services in a way that is prohibited, recovery of
funds or revocations of funding commitments is a possibility.
|
|
|
In the past, being able to check “No” was the only way to protect a funding
request. The new enlightened, albeit, more complex, approach is to permit an
applicant to check “Yes” but to either exclude the ineligible portion of the
cost from the funding request, or to include a small ineligible portion as
ancillary.
In an allocation situation, the PIA inquiry proceeds as follows:
|
|
If yes, the ineligible function must be cost allocated out of the funding
request. The full SLD administrative policy of such products and services is
provided in “Cost Allocation Guidelines for Products and Services that Contain
Eligible and Ineligible
Components,” http:www.sl.universalservice.org/reference/costallocationguide.asp.
Please provide a cost allocation of the ineligible functions (to include all
related costs such as installations, maintenance, taxes, etc.).
In general, the method of cost allocation must be based on tangible criteria
and provide a realistic result. Please describe the approach used for the cost
allocation.
|
|
|
In an ancillary situation, the PIA inquiry proceeds as follows, returning to
the cost allocation approach if ancillary use cannot be certified:
|
If yes, the functions may be considered ancillary if they meet the following
criteria.
-
The package represents the most cost-effective bid for the eligible product or
service.
-
The consideration of cost-effectiveness must be made without considering
ineligible features.
-
The package is a standard product offering that includes the ineligible
features as an intrinsic part, with no separated pricing available.
-
Any added content must be minimal.
Did the functions meet all of the criteria? Yes___ No___
If yes, the ineligible function is ancillary. If no, the ineligible function is
integral to the requested product or service and must be cost allocated out of
the funding request.
If the ineligible functions are to be utilized and do not meet the ancillary
criteria, please provide a cost allocation of the ineligible functions (to
include all related costs such as installation, maintenance, taxes, etc.).
|
|
|
Our advice to applicants faced with these types of funding situations depends
on several factors (including, perhaps, their threshold for pain). At the two
extremes:
(1) Since these situations are usually confined to Internal Connections, low
discount applications and/or those with only one or two related pieces of
equipment should consider excluding such equipment from their funding requests
altogether.
(2) High discount applicants and/or those with a large equipment inventory
should address the allocation issues upfront in the Item 21 attachments
associated with their funding request. Whenever possible, allocation should
depend upon vendor provided information that can be easily documented.
|
| Disclaimer: This newsletter may contain unofficial information on
prospective E-rate developments and/or may reflect our own interpretations of
E-rate practices and regulations. Such information is provided for planning and
guidance purposes only. It is not meant, in any way, to supplant official
announcements and instructions provided by either the SLD or the FCC. |
|