Multiple Versions of Adobe Reader Work With Grants.Gov

There has been some question lately as to which Adobe Reader version is usable with Grants.gov. The response is straightforward, there 4 versions compatible with Grants.gov.

1. Adobe Reader 8.1.1 – while compatible, submission made outside the browser will result in a broken pipe issue; therefore it is incumbent on the applicant to comply with instructions on the Grants.gov website.

2. Adobe Reader 8.1.2 – this version includes a security fix, but the “fix” was not applicable to Grants.gov forms; the same broken pipe issue remains as was in 8.1.1

3. Adobe Reader 8.1.3 – this version fixes broken pipe thereby allowing for submission outside the browser.

4. Adobe Reader 9.0 – this version contains the broken pipe issue, which will not be fixed until 9.1 is released.

First, it merits saying that Grants.gov does not “control” Adobe’s versioning system and releases.

Second, Adobe is, as are most computer-based software systems, constantly upgrading their capability. As a consequence, it is incumbent on Grants.gov and the applicant to remain attuned to the latest requirements and capabilities.

As Adobe releases a new version, it must be “tested” and “challenged” by Grants.gov to ensure compatibility and usability. When this is attained, the Grants.gov Program Management Office (PMO) then posts the updates on the Grants.gov website, its blog, and the information is disseminated via multiple venues to the applicant community.

Additionally, because Adobe is attuned to the needs of Grants.gov, many of their recent releases (i.e., newest versions) have been in response to Grants.gov needs. An excellent example of this is version 8.1.3; it fixed the “broken pipe” concerns evident in prior versions.

Because Adobe is constantly pursuing a better product with increased functionalities – and because it is operating in a highly competitive commercial arena – Adobe cannot “sit still.” If it were to freeze its product, Adobe would surrender the initiative to its competitors. As a consequence, it is a product seeking continuous improvements.

What does this mean to Grants.gov? This means as the Adobe product moves forward, so too must Grants.gov, and so too much the applicant community. That we must all constantly upgrade our capabilities is the price of success.

We well understand concerns regarding the many version changes. We at Grants.gov have the additional burden of testing and challenging each new version, validating its usability, and upgrading our capabilities. Unlike the individual applicant community wherein the latest version might merit only downloading, the applicant system-to-system and Grants.gov systems cannot remain stagnant but require continuous fine tuning.

Finally, why two versions of Adobe and not a single version? This is a question we posed to Adobe. Before presenting you their reply (below), the bottom-line is that Adobe has long maintained multiple product lines for different commercial audiences, in other words – the market place drives their products and relevant capabilities. This, too, becomes something we must live with.

The following is Adobe’s response:

-----
In product release cycles, there are three dates defined in the support policies. These include “General availability”, “End of core support”, and “End of extended support”. The products and their associated dates can be found on the Adobe website here: http://www.adobe.com/support/products/enterprise/eol/eol_matrix.html.

During the period between “General availability” and “End of core support” additional versions of Adobe Reader may be provided to the public and may include enhancements or product fixes. These enhancements may be made to any Adobe Reader version that has not reached End of core support. Depending on the product release cycle this may result in the availability of a specific enhancement in an “earlier” version of Reader. For example, an enhancement may be made available in Reader 8.1.3 that is not available in Reader 9.0 and will not be included in the Reader 9 series until Reader 9.1. Despite the version numbers, Reader 8.1.3 was released prior to Reader 9.1 but after Reader 9.0.
-----

Adobe has been an excellent partner with Grants.gov. We have the attention of the corporate headquarters, their developers, and staff. When we have encountered problems, Adobe has deployed, at their own cost, teams of people to our system integrator site to assist in problem resolution. Grants.gov and the applicant community are not part of the “acceptable noise level” in Adobe’s commercial arena. On the contrary, if and when we have problems, need support, and or voice our opinion, Adobe has a history of being responsive. They are our – Grants.gov and the applicant community’s – partner. But it is important to note that the partnership runs two-ways – as they support us, we must maintain pace with them (and their latest versions). Only in doing so will we all attain greater functionality and capability.

Rollback of R&R SF424 Form in AT07

This notice only applies to the Grants.gov Testing Environment (AT07): http://at07web.grants.gov/ and not the Production Environment.

On November 25, 2008, the Grants.Gov Program Management Office (PMO) rolled back the prototype version of the R&R SF424 Form that was in the AT07 Testing Environment to the same version that is currently in use in our Production Environment. The result is the AT07 Testing Environment mirrors the Production Environment.

Agencies that were testing the prototype version of the R&R SF424 Form that was in the AT07 Testing Environment until yesterday can keep any templates they developed and continue development using these templates when the prototype R&R SF424 Form is returned to AT07.

The prototype R&R SF424 Form was rolled back to the current version in use in the Production Environment in order to support some of our client agencies and their transition from PureEdge forms to Adobe forms. The strategy for releasing new versions of the R&R family of forms into the AT07 Testing Environment is being developed and will be published in the near future.

Grants.gov Initiative Updates

Speed & Reliability Update
Four of the five T-1000 servers to enhance speed and are currently in production. The fifth server is being used as a contingency back-up as we continue to develop maturity with the new servers that are in production now. We are currently working with Adobe engineers to fully implement advanced clustering capabilities upon completion of this task this phase of the speed and reliability will be complete. The final phase will be implemented with the release of the Build 2008 – 03, when the LDAP configuration is completed.

Build 08-03 Update
The December 13, 2008 Build – 03 will now occur on January 10, 2009. This build will now include a revision to Step 3 of the registration process. The delay in release of this build is a result of two factors. Resources have been dedicated to concluding the transition to Adobe for those agencies making the final move from PureEdge to Adobe. Also, since Step 3 of the registration process will change in this build several Agencies have requested additional time to update their applicant material to communicate the new upcoming registration process to their audience.

System Status - November 21

Grants.gov experienced a tremendous load on the system Thursday, November 20, 2008. There were a large number of closings. Today, November 21, 2008 there are 18 closings. As of 10:15 a.m. this morning we have increased activity on the system. We are anticipating system slowness as the day progresses.

The Contact Center is on alert. If system slowness occurs today we will notify applicants appropriately.

Regards,
Grants.gov PMO

Adobe Reader 8.1.3 Resolves "Broken Pipe" Issue

Adobe Reader version 8.1.3 resolves the "broken pipe" error intermittently experienced with other versions of Adobe Reader. Adobe supports multiple major version releases of its products throughout the life cycle of the particular main version. Adobe Reader 8.1.3 has been released, tested, and is compatible for use with Grants.gov.

If while using versions of Adobe Reader other than 8.1.3 you experience the "broken pipe" error message, you can submit your application package from an internet browser. For more information on this please visit the FAQ section for Adobe Reader.

"Comment" section of the blog is not being used by the readership to its fullest capability

"After a meeting this morning, it has become evident that the "comment" section of the blog is not being used by the readership to its fullest capability.

To not provide feedback and comment is a dis-service to all users of the Grants.gov system and the PMO. Moreover, to later claim you were not included 'in the decision making process' is disingenuous.

New communication means and transparency benefit everyone - when used. All readers are encouraged to participate in the future of Grants.gov by providing feedback via the blog."
- Eben Trevino

Update on FY2010 Migration Planning

Subject: Update on FY2010 Migration Planning

Reference: July 16, 2008 Grants.gov FY2010 Budget Meeting

Objective: Transition the Grants.gov PMO systems capabilities to a Platform-as-a-Service (PaaS) (i.e., cloud computing) business model.

Rationale: Transition the PMO away from the task of hardware & software management and focus on core mission of developing, testing, and placing into production Grant applications for the purpose of transmitting data.

PaaS/Cloud rationale:
1. Increase processing power
2. Responsive scalability
3. Increase system availability
4. Significantly enhance system availability
5. Increase redundancy (addressing COOP)
6. Security issues mitigated
7. Better economics (overall and individual costing)

Upon migration completion, the objectives are:
1. Employ full forms functionality
2. Employ self-diagnostic forms
3. Make available a self-diagnostic computer tool for applicants
4. Operate in an environment responsive to in-depth metrics collection
5. Replicate the user experience vis-à-vis forms submission
6. Automate opportunity notice & availability via RSS, Twitter, etc.
7. Reduce reliance on contact center
8. Create a more realistic & responsive test environment

Regarding the website, by FY2010:
1. Effectiveness to significantly increase
2. Efficiency increase
3. More dynamic & responsive to changing needs
4. Information Architecture = encyclopedic
5. Data bases to remain intact & updated
6. Use website for work-flow management & increased transparency with Grantor community

Timeline - Migration will occur in FY2010

Additional Information: Large Submission Volume

For PureEdge applications, applicants only need to submit one time. Although it is taking longer to process, the PureEdge applications are in Queue to be processed.

Regards,
Grants.gov PMO

Large Submission Volume

This week Grants.gov has received a large amount of PureEdge applications, over 1,300 per day. On November 6 we received over 2,100 PureEdge applications. This has resulted in a large number of applications in the Grants.gov queue for processing. This may cause slow processing time for submissions on Friday, November 7, 2008.

Regards,
Grants.gov

Grants.gov: 48 Hour Validation (PureEdge only)

This week Grants.gov has received a large amount of PureEdge application, over 1,300 per day. On November 6 we received over 2,100 PureEdge applications. This volume is causing the 48 hour validation of applications to be surpassed.

The 48 hour validation began to be exceeded at approximately 6:00 p.m. EST November 6. As of this message Grants.gov has approximately 1,000 PurEdge applications in que to be processed. Once the que clears we will notify you.

This is for PureEdge only. There is no impact on the Adobe system. If you have questions please contact the Grants.gov PMO staff.

Regards,
Grants.gov