Addendum A - RFP-33-10-ADAMS- SOW.pdf

Addendum A to RFP NRC3310ADAMS IDIQ Statement of Work

Table of Contents

1. Background

2. Objective

3. ECM Program and Vision

3.1. ECM Program

3.2. ECM Vision

4. Overview of ADAMS

5. ADAMS Libraries and Access Mechanisms

6. Applications and Interfaces Dependent on ADAMS

7. Estimated Volume of ADAMS Documents

8. ADAMS and IBM FileNet P8 Challenges

9. Scope of IDIQ Contract

10. 508 Compliance

10.1. Section 508 Program Need

10.2. Section 508 Product Requirements

10.3. Section 508 Evaluation Factors

10.4. Section 508 Acceptance Criteria

11. NRC Enterprise Architecture (EA) Standards

12. Deliverables

13. Performance Measures

14. Instructions for Deliverables

15. Primary Place of Performance

16. Travel

17. Post Award Kick-Off Meeting

18. Status Meetings

1. Background The U. S. Nuclear Regulatory Commission (NRC) ensures that the nation safely uses radioactive materials for beneficial civilian purposes while ensuring that people and the environment are protected. The NRC regulates commercial nuclear power plants and other uses of nuclear materials, such as nuclear medicine, through licensing, inspection, and enforcement of its regulations. Information associated with these endeavors are stored in and accessed from many different repositories; the primary repository is a document management system known as the Agencywide Documents Access and Management System (ADAMS). ADAMS is discussed in detail in Section C.4, Overview of ADAMS.

The NRC Office of Information Services (OIS) plans, directs, and oversees the NRC's information resources, including technology infrastructure and delivery of information management and technology services to meet the mission and goals of the agency and is the business sponsor of this effort.

The OIS Information and Records Services Division (OIS/IRSD) plans, develops, and delivers programs and services related to the storage, retrieval, protection, and preservation of NRC information in paper and electronic media. It also assists internal and external stakeholders obtain NRC information through the Public Document Room, ADAMS Support Center, the Technical Library, the File Center, the NRC internal and external Web Sites, and the FOIA and Privacy Act programs. IRSD manages a centralized system for the electronic search and retrieval of internal and external agency documents. It also develops and administers the agency information collection budget and directs the agency's records management services.

The Enterprise Content Management (ECM) Program was established within OIS/ IRSD to address agency content management needs that include, but are not limited to, content storage, eForms, search/query/discovery, retrieval, versioning/change management, records management, compliance, capture/ingest, workflow, digital signature, collaboration, security (content security and Federal Information Security Management Act (FISMA) compliance), administration, taxonomy, metadata, data quality/integrity, Personally Identifiable Information (PII) management, rendering, publishing, and enterprise reporting.

2. Objective The objective of this IDIQ contract is to outline the required professional Information Technology (IT) Services for the NRC ECM Program. Contract services are intended to be provided primarily by an IBM FileNet P8 certified and authorized Contractor for the purpose of providing a full range of IT services, technical expertise, and project management expertise to:

1. Ensure ADAMS operations meets applicable standards by applying Agency adopted project management methodologies;

2. Provide implementation support and re-engineering services to migrate ADAMS applications operating under IBM FileNet Content Services operating system

(OS) to operate under the IBM FileNet P8 OS.

3. Maintain synchronized ADAMS Main Library (FileNet Content Services) with the FileNet P8 Main Library by operating existing synchronization routines. (see section 5, ADAMS Libraries and Access Mechanisms);

4. Retire and decommission the IBM FileNet Content Services OS and all related application as migrations are complete;

5. Provide operations and maintenance support for the IBM FileNet Content Services OS (while it remains operational during the migration effort) and the P8 OS as well as the applications that run on each of these environments;

6. Automate processes such as E-mail capture, records management, and document profiling by using the functions available in FileNet P8 and establish workflows for business processes for mission-critical programs and corporate-support operations;

7. Coordinate with the NRC Project Officer to provide them the information they need to perform the development, update and review of all required security documentation for the IBM FileNet P8-based system.

3. ECM Program and Vision

3.1. ECM Program

The ECM Program is an agency wide organizational framework of projects, technologies, policies, governance, and individuals focused on bringing to the NRC, a web-based and collaborative system for content management, streamlined content profiling, straightforward records management, simplified searching, and the ability to combine office workflows with content creation and use. The ECM program has direct responsibility over the establishment of policies, processes, activities, and technologies that involve delivering content management solutions for NRC.

3.2. ECM Vision

The ECM Vision is to improve the quality, efficiency, and security of our regulatory and administrative business processes by providing appropriate and straightforward access to information when needed, regardless of location or access device.

4. Overview of ADAMS The majority of the NRC’s electronic documents and records rely on aging technology known collectively as ADAMS. In addition, a number of mission-critical applications operate in conjunction with ADAMS.

The ADAMS system, which is based on IBM’s FileNet Panagon Content Services 5.4 (CS) platform, reached a point in its lifecycle where the system’s architecture, infrastructure, and software are outdated and no longer support the NRC’s needs.

Additionally, CS has reached its end of life and is operating at the NRC on extended support by the vendor.

The NRC delivered the first version of the ADAMS system based on the Panagon line of products to users in November 1999. The Panagon line of products did not include a records management component; thus, the NRC purchased the TruArc ForeMost records management product and integrated it into the ADAMS system. In May 2001, the NRC completed the integration of ForeMost and users were able to move electronic agency records into the ADAMS repository although ForeMost is providing only minimal value to the NRC, The NRC obtained Contractor support to develop and deploy many enhancements to ADAMS to accommodate new requirements, stay current with updates to the FileNet Panagon product suite, correct software and design errors, and to integrate additional Web-based products to support specific search needs. As the migration from CS to P8 approaches, the NRC has curtailed all but essential changes to the CS environment.

Building the ADAMS document management system involved more than just configuring and deploying the Panagon and ForeMost products. The NRC obtained Contractor support to customize the ADAMS system to make it easier to use and add missing capabilities. Some of the customizations helped ADAMS administrators by making it easier for them to correct data, administer user access, and keep the system in good repair. Other customizations benefited users, by allowing them to group related documents into packages, view different kinds of documents (e.g. Microsoft Word documents, Microsoft Excel spreadsheets, Corel WordPerfect documents, and Adobe PDF files), establish a process to convert document formats to a standard archival format (PDF), and make it difficult to accidentally delete agency records from the system.

The NRC also responded to public requests for a web-based ADAMS search by acquiring the Convera RetrievalWare search tool. This web-based version of the public database went live on January 24, 2003. The NRC developed the Public Information Portal (PIP) that the public uses to search and retrieve documents stored in the Public Library (see Table 1 in Section 5 for a description). Shortly after delivering PIP, the NRC developed the Staff Interface Portal (SIP). SIP, which went live January 2, 2006, lets the NRC staff search for and retrieve documents stored in the ADAMS Main Library repository (see Table 1 in Section 5 for a description) from their web browser.

Over the past several years, NRC program offices required additional content intake, management, and workflow that were developed and incorporated as add-ons to the original ADAMS. The ADAMS integrated applications and interfaces with these specific functionalities include Document Intake and Review Platform (DIRP), Email Capture, Electronic Request for Additional Information (eRAI), Generic Communication (GC), Electronic Information Exchange (EIE), interfaces to Licensing Support Network (LSN), etc.

As a result of NRC’s expanded business needs, in June 2008, NRC acquired additional licenses for IBM’s FileNet P8 as an upgrade path. P8 is considered a temporary solution to keep ADAMS operating and is expected to be in place through the two year base period and through the three years term award. Since late in 2008, the NRC has been testing and prototyping automated processes developed using FileNet P8 products and

FileNet Workplace XT. The NRC intends to rollout a parallel ADAMS environment based on P8 by the end of 2010.

5. ADAMS Libraries and Access Mechanisms The ADAMS libraries and respective access mechanisms are described in Table 1:

Table 1:

ADAMS

Component

Purpose

Main Library The Main Library is the primary repository for all NRC Official Agency Records. Electronic Official Agency Records are stored as Adobe Portable Document Format (PDF) files with a variety of other formats used (primarily based on the Microsoft suite of tools) for working versions.

Legacy Library The Legacy Library contains bibliographic metadata such as title, author, recipient, date, subject, and description which serve as pointers to the document’s location in the Nuclear Document System (NUDOCS)

- the paper and microfiche-based predecessor to ADAMS.

Public Library The Public Library contains publicly available agency records stored as Adobe Portable Document Format (PDF) files. The Public Library is a subset of the Main Library and is also referred to as Public Access Record System (PARS)

Public Legacy Library

The Public Legacy Library is a subset of the Legacy Library; this library contains only metadata such as title, author, recipient, date, subject, and description which serve as a pointer to the document’s location in the NUDOCS system.

ADAMS Desktop The ADAMS Desktop is a client/server application that allows NRC users to browse the Main Library and Legacy Library and permits users to add documents to the Main Library (including setting document access control). It also includes the ADAMS ‘Find’ feature used to search for and retrieve documents.

6. Applications and Interfaces Dependent on ADAMS ADAMS uses an early-generation client/server technology modified to meet the NRC business needs. The combination of outdated technology with customizations yielded an application architecture that is difficult to adapt to emerging NRC business needs. NRC needs to improve the platform with which it manages documents. Due to the inability of the existing technology to efficiently and effectively support new business processes, the NRC developed new integrated applications. In many cases, these work-around, custom applications, interfaces, and business processes are integrated with ADAMS to handle agency records processes. However, they do so at the expense of increased data duplication, system complexity, and sometimes over-engineered processes that add significantly to ongoing maintenance and support costs.

The NRC has a fairly extensive installed base of SharePoint sites. Usage ranges from out of the box functionality to extensive customization. Tomoye Ecco is also in use as a Community of Practice tool.

The ADAMS integrated applications and interfaces are described in Table 2:

Table 2:

Applications and Interfaces

Purpose

Document Intake and Review Platform (DIRP)

DIRP enables the NRC’s Document Processing Center to rapidly accept, process, and profile the electronic Combined Operating License Application / Design Control Document (COLA/DCD) submissions, provide a mechanism to ensure the integrity of the submissions at any given time, reduce the need for duplication, and provide easy access and navigation to the submitted documents.

Electronic Information Exchange (EIE)

EIE is a web-based tool that enables licensees regulated under 10 CFR Part 50 to submit information electronically. This tool also allows applicants for positions in Nuclear power plants to submit clearance forms.

Electronic Hearing Docket (EHD)

EHD is a system that enables authorized participants to electronically submit and retrieve general proceeding documents and supports public access to publicly available documents online.

EIP (Electronic Hearing Docket Interface Portal)

EIP is a portal that enables authorized participants to electronically query and retrieve general proceeding documents.

Staff Interface Portal

(SIP)

SIP is a web-based search tool used by the NRC staff to query and retrieve content stored in the main library.

Public Interface Portal

(PIP)

PIP is a web-based search tool used by the public to query and retrieve content stored in the public library, also known as Web-based Public Access Records System (PARS).

(Interface to the) Digital Data Management System (DDMS)

A custom interface was developed to DDMS. DDMS is a system supporting the high-level waste hearings by providing the necessary information technology and audio/visual (A/V) resources for a fully integrated courtroom environment.

(Interface to the) Licensing Support Network (LSN)

A custom interface was developed to LSN, which provides a web-based portal to the high-level waste hearing participants' documents.

Electronic Email Capture Electronic Email Capture is a process by which certain desktop e-mail (versus server-based) information is automatically captured, processed, provided a disposition, and provided a retention attribute.

Folder Level Automatic Profiling (FLAP)

FLAP provides automatic and configurable profiling of documents by placing them into a designated folder within ADAMS.

Electronic Request for Additional Information (eRAI) eRAI is a SharePoint-based workflow for creating Requests For Additional Information (RAI), used by the license reviewer community and is fully integrated with ADAMS

Electronic Generic Communication (GC)

GC is a SharePoint based tracking system that tracks activities on Generic Communications issued to the licensees.

SharePoint Portal The NRC acquired the SharePoint Connector for Document Library and Web Part as part of the P8 suite of products. SharePoint at the NRC facilitates collaboration, provides content management features, implements business processes, and provides access to ADAMS information that is essential to the NRC mission in a collaborative environment.

Tomoye Ecco Portal The Tomoye Ecco Portal at NRC facilitates the sharing of new ideas, best practices, and collaboration.

Applications and Interfaces

Purpose

Microsoft Office and Outlook ADAMS Integrations.

NRC developed a custom ADAMS interface to Microsoft Office for the MS Windows operating environment, which supports Microsoft Word, Microsoft Excel, and Microsoft PowerPoint. These three products allow a user to add, open, check-in, and cancel check-out of a document from the menu bar in the respective tool. In addition, NRC developed an add-in to Microsoft Outlook that allows a user to automatically and seamlessly add an e-mail to ADAMS and create an ADAMS package from the menu bar in Microsoft Outlook.

7. Estimated Volume of ADAMS Documents The NRC manages its documents (e.g., Microsoft Office documents, PDF files, audio/video, images, etc.) in several systems (e.g., Microsoft SharePoint, Tomoye, DDMS, Intranet, etc.) and in several repositories (e.g., network drives, local drives, Microsoft Exchange, etc.) with ADAMS being the primary and largest of all the repositories. Currently, there are approximately 4 million files in ADAMS consisting of

1.7 million documents and 2.3 million versions.

8. ADAMS and IBM FileNet P8 Challenges ADAMS is a mature system based on dated technology - IBM FileNet Panagon Content Services 5.4 platform which is nearing the end of vendor support. In addition, there are critical components in ADAMS that do not function properly and the ability to successfully recover from future failures is uncertain. Certain ADAMS FileNet Operating System components are on limited support by the vendor while others are rapidly approaching end of life.

As part of its maintenance on ADAMS, the NRC needs to ensure a reliable operating environment for ADAMS. To achieve this, NRC must move ADAMS from its current base platform, IBM’s FileNet Panagon Content Services 5.4, to IBM’s FileNet P8 platform.

The challenges NRC faces include migrating an estimated: 1) 5,000 users, 2) content (estimated 4 million files and packages (multiple files consolidated into one file)), 3) several applications, and 4) dozens of reports. The integrated applications and interfaces (in Table 2 in Section 6) and their associated business processes need to be migrated to, or re-engineered for the IBM FileNet P8 platform. It is the NRC’s intent to perform system migrations and re-engineering efforts using a phased, incremental, and secure approach without disruption to NRC operations, which will be the responsibility of the Contractor. The applications also may need to be revised to improve the efficiency and interoperability of their operation.

9. Scope of IDIQ Contract Task orders may be negotiated and awarded to the Contractor to perform the following types of tasks under the IDIQ contract:

- Ensure ADAMS operations meets applicable standards by applying NRC-adopted project management methodologies.

- Migrate applications from the Content Services operating system (OS) that rely on

ADAMS (see section 6, Integrated Applications and Interfaces Dependent on ADAMS) and revise them to operate under the P8 OS as well as provide re-engineering, migration, integration, and implementation support.

Maintain synchronized ADAMS Main libraries and existing synchronization routines for both ADAMS OS’- Content Services, and P8 as well as the applications that run on each of these environments; (see section 5, ADAMS Libraries and Access Mechanisms).

- Retire and decommission the Content Services OS and all related application as migrations are complete.

- Provide operations and maintenance support for the Content Services OS (while it remains operational during the migration effort) and the P8 OS.

- Automate processes such as E-mail capture, records management, and document profiling by using the functionalities available in P8 and establish workflows for business processes for mission-critical programs and corporate-support operations;

- Provide security consulting and Certification and Accreditation (C&A) services.

The Contractor may be tasked to provide a full range of IT services, technical expertise, integration services, software development services, and project management. The Contractor shall furnish the necessary personnel, materials, equipment, facilities, travel, and other services required to satisfy the requirements of task orders negotiated and awarded under this IDIQ contract. The contractor may also be tasked to make recommendations for improvements to NRC business processes and organizational effectiveness and develop and deliver training on these recommendations at the discretion and direction of the NRC Project Officer.

In performing task orders under this IDIQ contract, the Contractor shall store all documents associated with the contract in NRC’s IBM Rational Clearcase system and use NRC’s IBM’s Rational ClearQuest system for tracking changes. In addition, the Contactor shall follow NRC Management Directive (MD) 2.8, “Project Management Methodology (PMM)”, and its associated handbook, the PMM Manual. This single Management Directive includes both the policy and a configurable process with guidance, tools, and templates to support the implementation of that process. For Information pertaining to NRC Management Directive (MD) 2.8 and “Project Management Methodology (PMM)”, and its associated handbook, the PMM Manual, see solicitation attachments.

Specific task order requirements for the types of work within the scope of this IDIQ contract will be specified in each task order Performance Work Statement (PWS) and will be negotiated with the Contractor before they are awarded.

10. 6 508 Compliance The Contractor shall support the NRC in its compliance with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), throughout the period of performance of the contract. Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

10.1. Section 508 Program Need

Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant for the following program need: "Web applications."

10.2. Section 508 Product Requirements

Technical standards from 36 CFR part 1194 Subpart B have been determined to apply to this acquisition. Solicitation respondents must describe how their proposed Electronic and Information Technology (EIT) deliverables meet at least those technical provisions identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

Functional performance criteria from 36 CFR part 1194 Subpart C have been determined to apply to this acquisition. Solicitation respondents must describe how their proposed Electronic and Information Technology (EIT) deliverables meet at least those functional performance criteria identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

Information, documentation, and support requirements from 36 CFR part 1194 Subpart D have been determined to apply to this acquisition. Solicitation respondents must describe how the information, documentation, and support proposed for Electronic and Information Technology (EIT) deliverables meet at least those information, documentation, and support requirements identified as applicable in the attached Government Product/Service Accessibility Template (GPAT).

10.3. Section 508 Evaluation Factors

Responses to this solicitation will only be considered for award after it has been determined that the proposal adequately addresses the requirements for Section 508.

Only proposals which contain adequate information to document their responsiveness to the Section 508 requirements (e.g. a completed GPAT, VPAT or equivalent and supporting documentation) will be eligible for any additional merit consideration.

10.4. Section 508 Acceptance Criteria

Web applications delivered as a result of this solicitation will be accepted based in part on satisfaction of identified Section 508 requirements for accessibility. Web applications delivered must include a completed GPAT, a sample of which is included as a part of this solicitation.

Table 3 - Government Product Accessibility Template (GPAT)

CFR 1194

Standard Sections

Total Number of Applicable Provisions

Notes Total Number of Supported Provisions

Please explain

Fully Partial Not

Section 1194.21 Software Applications and Operating Systems (12 provisions)

12 If the Webapp includes software applications, such as Browsers, Plug-ins, extensions, etc, then this Section applies.

Section 1194.22 Web-based Internet Information and Applications (16 provisions)

16 This Section applies to Webapps.

It also applies IF information, documentation, and support are provided via an intranet or the Internet.

Section 1194.31 Functional Performance Criteria (6 provisions)

6 Functional performance criteria always apply.

Section 1194.41 Information, documentation, and support (3 provisions)

3 If information, documentation, and support are to be provided by the vendor, then this Section applies.

11. NRC Enterprise Architecture (EA) Standards The Contractor shall ensure the IBM FileNet P8 platform suite of products and any non- IBM third party ECM software procured (by the NRC, not the Contractor) and provided to the Contractor under the task order shall execute in an environment containing the following technology elements and products currently implemented at NRC. As the NRC EA landscape evolves, the Contractor shall ensure the IBM FileNet P8 platform suite of products and any non-IBM third party ECM software executes in that EA.

NRC’s current technology elements and products are evolving and currently include:

a) Standard Desktop Hardware Configuration - The current standard NRC desktop workstations are the Dell OptiPlex GX520, GX570, and 755 (PC-compatible, x8086 family, equipped with an Intel Pentium processor) running Windows XP Professional, SP2.

b) Standard Desktop OS/Software Configuration - The current standard NRC desktop OS and software configuration is setup with Windows XP Professional, SP2, Microsoft Office Pro 2003, Microsoft Office Outlook 2007, Internet Explorer (IE) V6, Adobe Acrobat Reader V9, Microsoft Visio 2003 Viewer and AutoCAD Design Review. Note: A new version of IE will be implemented.

c) Laptop Hardware Configuration - The current laptop models are the Dell

Latitude E4300 and E6400 and a variety of other PC-compatible platforms.

d) Laptop OS/Software Configuration - Generally, the configuration of laptop computers follows closely those of the Standard Desktop Configuration.

e) Web Server Hardware Configuration - The current standard NRC web server runs on a Dell PowerEdge 2850 or an HP Proliant DL380/DL580 (equipped with Intel Pentium or Xeon processors) running with Windows Server 2003 Standard Edition, SP2. The NRC also utilizes the Sun hardware (v210, v240, v440) for its development, testing and production environments for some web servers.

Note: The models vary – predominantly HP Proliants.

f) Web Server OS/Software Configuration – The current standards include

Microsoft Windows Server, Internet Information Services (IIS), iPlanet Web Server Enterprise Edition, Sun ONE Web Server , Apache HTTP Server, and Oracle HTTP Server. The NRC will continue to implement web server technologies to provide efficient and stable publicly available documents. The NRC will continue to expand existing agreements with its Web-caching Contractor to duplicate the public document collection to remote sites.

g) Application Server Hardware Configuration - The current standard NRC application servers run on a Dell PowerEdge 2850/2950/6850 or a HP Proliant DL380/DL580 (equipped with Intel Pentium or Xeon processors) running Windows Server 2003 Standard Edition, SP2. Note: The models actually vary quite a bit – predominantly HP Proliants.

h) Application Server OS/Software Configuration - The NRC will continue to implement and integrate application server technologies like BEA WebLogic, Microsoft .Net and Oracle Application Server to provide efficient workflow infrastructure. The NRC uses a combination of Windows 2003 and 2008 server O/S in both 32-bit and 64-bit versions.

i) Database Server Hardware Configuration - The current standard NRC database servers run on a Dell PowerEdge 2850/2950/6850 or a HP Proliant DL380/DL580 (equipped with Intel Pentium or Xeon processors) running Windows Server 2003/2008 Standard/Enterprise Edition. Note: The models vary quite a bit – predominantly HP Proliants.

j) Database Server OS/Software Configuration - The NRC predominantly uses

Microsoft SQL and Sybase database technologies. The NRC uses a combination of Windows 2003 and 2008 server O/S in both 32-bit and 64-bit versions.

k) Storage Configuration (SAN and NAS Server) - The NRC predominantly uses

XIOTECH Magnitude 3000 storage management system, and Hitachi Data Systems Thunder modular storage system.

Note - Microsoft Office 2007 is currently targeted for FY 2010 (October 2009 – September 2010). Windows 7 is targeted for FY 2011 (October 2010 – September 2011).

12. Deliverables The Deliverables are identified at each Task in this PWS.

13. Performance Measures Contractor Performance Measures and Contractor Performance Evaluation Form will be used to evaluate Contractor performance under this task order every six (6) months.

14. Instructions for Deliverables

Each deliverable shall first be submitted to the Project Officer for Project Officer review.

Project Officer will have 10 calendar days to review each draft deliverable and respond to the Contractor in writing with comments or approval. If the NRC does not provide comments to the Contractor at the end of 10 days, the Contractor shall assume the deliverable has been approved by the Project Officer.

If revisions are required based on written comments from the Project Officer, the Contractor shall complete such revisions within 7 calendar days and submit the revised draft deliverable to the Project Officer. For each deliverable (draft and final), the Contractor shall provide one (1) electronic version of the deliverable via e-mail to the Project Officer.

All deliverables and supporting documentation gathered or developed under the task order may not be stored on any device or piece of equipment that has not been approved in writing by the Project Officer.

The Contactor shall ensure all deliverables and supporting documentation gathered or developed under the task order are stored in NRC’s of IBM Rational Clearcase and follow the NRC PMM approved template format.

All final deliverables shall be:

a. Free of formatting and spelling errors, be clearly written, and have no incomplete sections.

b. Submitted in a Microsoft Office tool such as Word, Excel, PowerPoint, etc., version 2007 or higher and shall be free of computer viruses.

c. “Plain English” language that can be understood by a non-technical layperson.

Statistical and other technical terms used in the deliverable shall be defined in a glossary.

d. Microsoft Project 2007 for use to develop and maintain the Project Plan Accompanied by a cover letter from the Contractor on company letterhead.

Multiple deliverables may be delivered with a single cover letter describing the contents of the complete package.

15. Primary Place of Performance

The Contractor shall perform work under this task order on-site at the headquarters of the U.S. Nuclear Regulatory Commission in Rockville, MD located in the Washington, D.C. Metropolitan area. If approved in writing in advance by the Project Officer, work may also be performed at the Contractor’s site. Government furnished equipment on-site at NRC will include a desktop for the on-site Contractors for general office use with connection to the NRC LAN and a telephone.

If Contractor personnel are performing work off-site, Contractor personnel shall be available to travel to the NRC in Rockville, MD for meetings within 24 hour written notice from the Project Officer.

The Contractor shall have access to the Government facilities: five (5) days per week, Monday through Friday from 7:00 a.m. to 4:30 p.m. EST, except when the Government facility is closed due to local or national emergencies, administrative closings, Government holidays, or similar Government-directed facility closings. The NRC office location is:

U. S. Nuclear Regulatory Commission Headquarters 11545 and 11555 Rockville Pike Rockville, MD 20852

16. Travel

Performance under this task order may require travel to NRC’s four regional offices located in:

U.S. NRC Region I 475 Allendale Road King of Prussia, PA 19406-1415

U.S. NRC Region II Sam Nunn Atlanta Federal Center, 23 T85 61 Forsyth Street, SW Atlanta, GA 30303-8931

U.S. NRC Region III 2443 Warrenville Road Suite 210 Lisle, Illinois 60532-4352

U.S. NRC Region IV Texas Health Resources Tower 612 E. Lamar Blvd., Suite 400 Arlington, TX 76011-4125

17. Post Award Kick-Off Meeting

The Project Officer will schedule a kick-off meeting at NRC Headquarters in Rockville, MD, within five (5) days after task order award. The Project Officer will provide an agenda to the Contractor in writing prior to the meeting. The Contracting Officer, the Project Officer, and the Project Officer’s technical personnel will represent the NRC.

The Contractor shall have equivalent representation at the meeting. The Contractor shall be responsible for recording and distributing the minutes of this meeting to the Project Officer.

18. Status Meetings

The Contractor shall attend, at a minimum, weekly status meeting with the Project Officer at NRC Headquarters in Rockville, MD, to discuss ongoing work, issues, risks, and upcoming work that needs to be completed. The Contractor shall propose an agenda for the meeting and will send the agenda to the Project Officer at least three days before the meetings are to be convened. The Project Officer will finalize the agenda and distribute the agenda at least one day before the meeting. At the discretion of the Project Officer, the meetings may be conducted via conference calls or video conferencing. Ad-hoc status meetings may be convened as the need arises. The Contractor shall be responsible for recording and distributing the minutes of these meetings to the Project Officer.