SB1341-09-RP-0078-A002.doc

SF30 Continuation of Block Narrative

9B. Date (See Item 11)

Aug 7, 2009

10A. Modification of Contract/Order No.

10B. Date (See Item 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDG-

MENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT

IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting and Appropriation Data (if required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

Set fourth item 14, pursuant to the authority of FAR 43.103 (b)

14. Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See continuation pages for details.

END OF TEXT

NTE

Travel costs will be reimbursed in accordance with FAR Subpart 31.205-46, Travel costs. The Contractor shall submit a copy of each receipt for an individual travel cost or other direct costs that exceeds $75.00 with their invoice for those costs.

Period of Performance: October 1, 2009 thorugh September 30, 2010

NTE

Travel costs will be reimbursed in accordance with FAR Subpart 31.205-46, Travel costs. The Contractor shall submit a copy of each receipt for an individual travel cost or other direct costs that exceeds $75.00 with their invoice for those costs.

Period of Performance: October 1, 2010 thorugh September 30, 2011

NTE

Travel costs will be reimbursed in accordance with FAR Subpart 31.205-46, Travel costs. The Contractor shall submit a copy of each receipt for an individual travel cost or other direct costs that exceeds $75.00 with their invoice for those costs.

Period of Performance: October 1, 2011 thorugh September 30, 2012

NTE

Travel costs will be reimbursed in accordance with FAR Subpart 31.205-46, Travel costs. The Contractor shall submit a copy of each receipt for an individual travel cost or other direct costs that exceeds $75.00 with their invoice for those costs.

Period of Performance: October 1, 2012 thorugh September 30, 2013

NTE

Travel costs will be reimbursed in accordance with FAR Subpart 31.205-46, Travel costs. The Contractor shall submit a copy of each receipt for an individual travel cost or other direct costs that exceeds $75.00 with their invoice for those costs.

Period of Performance: October 1, 2013 thorugh September 30, 2014

The purposes of this Amendment are to:

1) Provide the attendance sheet and presentation slides of the Preproposal Conference and Site Visit held at NIST on August 14, 2009 as Attachment 1 to this Amendment;

2) Revise clause I.37 to read as follows:

I.37 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 30 days of expiration of the contract.

3) Add the following clause to Section I of the solicitation:

52.219-6 Notice of Total Small Business Set-Aside (June 2003)

(a) Definition. “Small business concern,” as used in this clause, means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the size standards in this solicitation.

(b) General.

(1) Offers are solicited only from small business concerns. Offers received from concerns that are not small business concerns shall be considered nonresponsive and will be rejected.

(2) Any award resulting from this solicitation will be made to a small business concern.

(c) Agreement. A small business concern submitting an offer in its own name shall furnish, in performing the contract, only end items manufactured or produced by small business concerns in the United States or its outlying areas. If this procurement is processed under simplified acquisition procedures and the total amount of this contract does not exceed $25,000, a small business concern may furnish the product of any domestic firm. This paragraph does not apply to construction or service contracts.

4) To revise the Statements of Work for the first task order and second task order in Section J as follows:

J.1 Task Orders 1 & 2 Statement of Work

Statement of Work (SOW)

First Task Order

Title: Electronic Information Group (EIG) IT Technical Requirements Development

THIS TASK ORDER WILL NOT BE FUNDED BY AN AMERICAN RECOVERY AND REINVESTMENT ACT OF 2009 APPROPRIATION. CLAUSES 52.203-15, 52.204-11 AND 52.215-2 ALTERNATE I DO NOT APPLY TO THIS TASK ORDER.

Requirements:

1. EEEL Requires Contractor support for a 9 month period for the following EIG projects:

1) The Infrastructure for Integrated Electronics Design and Manufacturing (IIEDM) Project seeks to aid the growth of the electronics and semiconductor industries by technical support in two key efforts. First, the project provides expertise in the development of neutral data exchange specifications designed to support distributed supply chain integration and e-manufacturing activities. Second, the project acts as an impartial forum in the development of standards and assistance in resolving interoperability issues between similar, and often conflicting, standardization efforts. This project is working with industry to enable the infrastructure needed to support electronic commerce for both electronic components and manufacturing. As EIG develops these exchange standards, we must develop Reference Implementations of the IT standards, and develop software tools to help industry implement and deploy the standards.

2) The Knowledge Facilitation project supports the eNIST objective to eliminate paper and to automate manual, labor intensive administrative activities. The project employs cutting-edge web-based technologies to develop custom applications in support of EEEL and NIST. The applications we develop are not available in commercially developed packages (Commercial-Off-the-Shelf, or “COTS”) and therefore need to be developed in-house. These applications automate tasks and decrease the administrative requirements of the technical and support staff, while increasing responsiveness to customers and implementing a secure eNIST paperless environment. As a result, EIG scientists are able to spend more time working in their labs than working at their computers to fulfill administrative requirements. Several web-based applications have been created to store and track all of EEEL’s publications, travel and project status reports provided to management. Management is able to obtain access to the information it needs easily, and the administrative burden on the technical staff has been decreased. Generation of required paperwork has been automated, removing that responsibility from the EIG support staff. The applications also serve as a data warehouse for all publications and reports, providing backups of all data stored. The project reporting database was developed as a web-based application; it has been created to reduce the duplication of the storage of information while providing management with immediate access to project data without interrupting project staff. This application contains all project-related information such as funding, milestones, staff, progress, etc. for all of the 97 projects in EEEL. Access to the data is provided by user roles; i.e., division chief, group leader, project leader, and staff. EIG is looking into new technologies like RFID (Radio Frequency Identification) technology to help in the equipment inventory for the lab. EIG is also developing a web-based database for body armor testing.

3) Smart Grid – A smart grid delivers electricity from suppliers to consumers using digital technology to save energy, reduce cost and increase reliability. Such a modernized electricity network is being worked on at NIST by the EEEL. To support this effort, applications may need to be developed to help in the collaborations and interactions and tracking progress that will be required by the technical staff. Also, several small custom applications may need to be developed to demonstrate technologies that will be used to support the Smart Grid.

For the entire SOW, reference to the EEEL Database will mean all four databases mentioned above, and any other systems indentified as being required.

2. Requirements

General:

NIST IT Architecture constraints:

· The existing Group Oracle database on switch.eeel.nist.gov and use of the OCIO Oracle databases will be retained – modifications to existing schemas will be permitted but NIST approval of all modifications is required before inclusion in technical design.

· Java (J2EE) technology using Apache Tomcat Engine and SPRING Framework is required for server-side logic processing, database interactions, workflow processing, web-service implementation and report generation.

· Macromedia Flex/Flash technology is permitted for client-side generation of user interfaces.

· Adobe PDF technology is permitted for generation and presentation of standard government forms and report generation.

· Javascript technology is permitted for client-side data validation and user interface automation.

Validation of the IT system design shall include the review of system design documents as well as the review of system functionality and user interfaces with respective user groups. Validation of data exchange standards (and associated software tools) will include the review of any design documents (models, use case scenarios, etc) and testing guidelines.

Specific:

Task Management:

The Contractor must develop and maintain the Project Plan in the EEEL eQMR Database, and update quarterly.

The Contractor shall adhere to the project plan developed by the Contractor and revised or updated by the team (the Contractor, Government and other participants as designated on the plan). The Plan shall include such things as deliverables, milestones, outputs, staffing and status reporting. The Contractor and COTR will review soft copy of the updated status of the plan at the scheduled bi-weekly meeting. The Contractor shall update the project plan when there are changes or as required by the NIST Point of Contact or the Contracting Officer’s Technical Representative.

The Contractor shall provide in the EEEL eQMR database the status of actual Contractor performance in relation to the anticipated performance/completion as specified in the Project Plan. Any and all differences between the Contractor’s proposed performance schedule, actual performance and completion dates shall be fully explained and documented in the report. The eQMR database must also include documented accomplishments and any potential or identified risk items.

The Contractor shall participate in bi-weekly progress review meetings with the COTR. The meeting will include the status of on-going tasks. It will also be the forum to discuss outstanding or anticipated issues or problems. Any discrepancies of non-performance will be discussed at each meeting and the Contractor shall provide proposed corrective action measures.

The Contractor shall be responsible for overall project management, including the development and monitoring/updating and submission of the Project Plan in the EEEL Project Database; task work plans, detailing specific deliverables, monitoring quality of deliverables, final reports, source code, and documentation.

The overall management plan shall address:

a. The flexibility needed to allow for multiple tasking of projects;

b. Tracking of contract staff and hours within and across individual tasks;

c. Maintaining running totals of staff and dollar expenditures by task (by hours) and overall project;

d. Appropriately staffing the project with team members who have extensive knowledge of the existing system and the business processes involved and the new technologies that will be required for this project, and

e. Oversight by a Project Manager who will also participate in the technical and planning activities of the project on a regular basis.

3.0 3.O RESERVED

Development, Production, and Support

The Government estimates that a total of 4,344 Contractor labor-hours may be required to perform all requirements in this Statement of Work. This estimate is further broken down as specific estimates per subtask in this Statement of Work.

4.1 Subtask 1 – Customer Interaction for NIST systems The Government estimates that 312 Contractor labor-hours may be required to perform this subtask.

The Contractor shall provide support for any NIST/EEEL Customer of the applications being developed. Specifically, the Contractor shall

a. Respond to Bug requests reported either directly to the contractor or using TRAC reporting software.

b. Record additional information from the user as required ensuring full understanding of the customer’s needs.

c. Correct reported problem.

d. Document the fix using the TRAC software for the specific application and close ticket.

4.2 Subtask 2 – Design and Development for NIST Systems

The Government estimates that 1,560 Contractor labor-hours may be required to perform this subtask.

The Contractor shall Design, develop and document technical requirements/models for IT systems that satisfies EEEL Database requirements, gathered from Customer requirements meetings. Other designs may be required as they are identified.

The Contractor shall validate the design and technical requirements/ specifications with the COTR.

Validation shall include:

1. Review of design development team of how the proposed design implements requirements

2. Review of user interfaces and system interactions with user groups to ensure that user needs are met and that users can perform required operations within the current time required or less.

3. Continuous coordination and communication with the COTR and development team on the technical design to ensure the final design is approved by the COTR.

The Contractor shall develop user management modules for the each application requested. The user management modules will be designed and will include the following functionality:

1. Username and password authentication via the NIST Active Directory

a. All required communications with the NIST Active Directory implementation.

b. All audit logging required to meet NIST security guidelines.

c. Login interfaces required for collecting user input, communicating login errors and directing users to the NIST Enterprise Password Service for password maintenance.

2. User authorization

a. A EEEL Database authorization repository matching users with roles and data access permissions

b. Maintenance of authorization repository data.

3. User attribute management

a. Retrieval of read-only user attributes from the NIST Active Directory

b. A application user repository

c. Maintenance of read-write user attributes in the application user repository

The Contractor shall develop Workflow modules for the EEEL Database. The purpose of the workflow modules will be to facilitate the approval of projects. The Workflow modules will support the following actions:

1. Create new project

a. Internal Research Project

b. External project

2. Create/assign project staff

3. Create/assign Project Funding

4. Update project information, i.e., milestones, outcomes

5. Terminate project

6. Archive Project

7. Report Project Progress

Source Code:

The Contractor shall save source code developed under this task using Subversion (SVN) version control system located on SWITCH.EEEL.NIST.GOV. There is a repository for each application, and new repositories are to be created for any new application.

The source code shall include all project files: configuration files used by Integration Development Environments (IDEs), and files used for the compilation and testing of the software products.

These Contractor code deliveries will be in addition to any Source Code Version Control solution used in the development process.

Security Procedures

The Contractor must adhere to NIST and DoC IT Security Policies while performing all Requirements of this Statement of Work (SOW).

The Contractor shall develop security C&A documentation specific for the application, as required by NIST Special Publication 800-37. Additionally, any software developed must meet minimum mandatory controls as specified for Moderate Impact (Confidentiality and Integrity) systems as specified in NIST Special Publication 800-53, DoC IT Security Program Policy and Minimum Implementation Standards (2005), and NIST policy. The contractor should pay particular attention to SA-8 Security Design Principles. Control: The organization designs and implements the information system using security engineering principles. NIST Special Publication 800-27 provides guidance on engineering principles for information system security.

The contractor shall maintain a frequent dialog with the COTR concerning the appropriate level of security.

4.3 Subtask 3 –User Documentation Support for NIST systems

The Government estimates that 312 Contractor labor-hours may be required to perform this subtask.

a. User Documentation

Upon request by COTR, the Contractor shall update and maintain developed User Guides for the specific applications being developed and deploy them as web pages in the applications “Help” section. The Contractor shall update existing and write new USER Guides, which may include step-by-step instructions, screen prints, expected results.

4.4 Subtask 4 – Portal Applications and Reports & Downloads Development for NIST systems

The Government estimates that 624 Contractor labor-hours may be required to perform this subtask.

Upon request by COTR, the Contractor shall design, develop, test and implement new Portal front page applications and reports and downloads as needed to support EEEL Databases. The Contractor shall also perform modifications and enhancements to Portal front page applications and reports and downloads as requested by the COTR and/or their designee.

Specifically, the Contractor shall:

a. Participate in discussions with the COTR and/or their designee to document requests for modifications and enhancements to Application Pages, reports and downloads.

b. Fully document and track requirements using TRAC for both application, report and download modifications and enhancements.

c. Develop design documents, outlining the modifications/ enhancements to be done to existing reports and downloads and/or new reports to be developed. Review design documents with the COTR and/or their designee.

d. Develop modifications and enhancements to existing reports and downloads, including all coding and unit testing necessary.

e. Develop new reports and downloads as needed. Ensure that new reports and downloads meet all available NIST standards for report development, data presentation, headers/footers, etc.

f. Develop test conditions and scripts and execute integration test of all modified or newly developed application enhancements, reports and downloads.

g. Deploy Portal front page enhancements, Portal application enhancements, reports & downloads in production environment.

4.5 Subtask 5 – Technical Support for NIST systems

The Government estimates that 312 Contractor labor-hours may be required to perform this subtask.

Upon request by COTR, the Contractor shall provide Technical Support in areas of software management, data management, and instance management. The Contractor shall work with NIST COTR and/or their designee to carry out requests for software migrations, data migration, maintenance, and ORACLE table updates. The Contractor shall help ensure the integrity of software instances by applying rigorous attention to configuration management.

a. Software Management

The Contractor shall coordinate software promotion activities from development into other instances (testing, production) according to specified migration procedures.

b.

Data Management

The Contractor shall coordinate with system support and end user groups to facilitate additions or modifications to production data. In addition, the Contractor shall ensure the proper flow of automated interface data into all data instances and ensure that proper security functions are in place to prevent unauthorized update of production data.

c.

Instance Management The Contractor shall coordinate the creation/modification of database instances and object owner definitions within the EEEL environment to meet system and user requirements. The Contractor shall also coordinate the synchronization of data between instances and the migration of object changes between instances as required.

d.

Project Support:

The Contractor must support the EEEL Databases plus small ad-hoc projects as needed.

EEEL Project Database – as the new EEEL Project database is completed, existing data from the old eQMR system will be ported to the new system. Meetings with the COTR will determine the new fields the old fields must map on to.

4.6 Subtask 6 – Change Management for NIST systems

The Government estimates that 612 Contractor labor-hours may be required to perform this subtask.

EEEL recognizes the importance of change management and communication as key elements in the success of changes in the production environment.

The Contractor shall provide continuity for a continuous technology change management and communications methodology that will support EEEL and its efforts over an extended period of time.

The Contractor shall make appropriate recommendations to the COTR and/or their designee as necessary to maximize efficiency in change management.

4.7 Subtask 7 – IPC Modeling Support for 258X Series of Standards The Government estimates that 612 Contractor labor-hours may be required to perform this subtask.

The Printed Circuit Board (PCB) industry users have become accustomed to seeing clear and unambiguous GUIs that they can use to complete information or get descriptive data and once you have captured what is necessary a tool that can give you an analysis of the risk or compromises that have been made by the decisions. The key to having this ability is unambiguous data exchange standards. One key standard is the IPC 2581 (“Generic Requirements for Printed Board Assembly Products Manufacturing Description Data and Transfer Methodology”). Moving beyond the generic base standard, industry is now seeking to add sectionals which cover assembly and test sections. To support this effort the contractor will provide IPC with modeling and technical support in the completion of IPC 258X series of standards.

Deliverable: Report on technical efforts and models generated. Also copies of any models generated.

5. Deliverables

Project Plan and Meetings

Documentation shall include:

1. Required modifications to any EEEL Oracle database schema

2. Entity relationship diagrams for all new applications developed.

3. Identification and detailed description of required system modules

4. Detailed specifications for each system module to include:

a. Sub-Components of each system module

b. All externally available methods, inputs, outputs and configuration parameters.

c. All significant internal methods and variables

d. Descriptions of the functions performed by each method

e. Descriptions of the use and legitimate values for each variable, input, output and configuration parameter

f. All methods shall be documented with a pseudo-code description of required actions.

g. All external calls shall be identified by the module and function being called.

5. Listing of all Functional Requirements met by the system design

6. Listing of all Functional Requirements not met or eliminated in the design phase

7. Approval Sign-off of COTR on each module specification produced.

Source Code Documentation shall include:

1. Source code for all developed modules

a. Source code shall be adequately documented to facilitate code review including: descriptions for each method, definitions of all input and output parameters

2. Build instructions for all modules requiring compilation

3. Build scripts for all database modifications

4. Test plans, scenarios, code and results

Security Documentation shall include:

1. All security Certification & Accreditation (C&A) documentation for the application. Work with the EEEL IT Security Officer to help document requirement for the Certification.

6. Inspection and Acceptance

All Deliverable are subject to review and approval by the COTR. The period of review will be designated within the project plan and shall be commensurate with the complexity of the deliverable but shall in no cases be less than 5 working days.

7. Period of Performance The period of performance for this task order is October 1, 2009 through June 30, 2010.

8.

Reserved

9. Place of Performance Most of the task order will be performed on-site at the NIST campus in Gaithersburg, Maryland, but some of the task order may be performed off-site as approved by the COTR.

10. Section 508 Accessibility All Electronic and Information Technology (EIT), as defined at FAR 2.101, supplied under this task order must conform to the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology Accessibility Standards (36 CFR Part 1194). The applicable standards are available at http://www.access-board.gov/sec508/508standards.htm.

The following standards have been determined to be applicable to this Statement of Work:

____X___ 1194.21 Software applications and operating systems

____X___ 1194.22 Web-based intranet and internet information and applications

11. Government Furnished Information, Facilities, Supplies, and Services

NIST will:

· Provide the Contractor with the appropriate hardware, software, and equipment required for accomplishing day-to-day work requirements.

· Provide telephones for the Contractor’s business use only.

· Provide systems access and all necessary database and web server permissions, as necessary, to meet the requirements of this task order.

12. Reporting Requirements

Table 1: Schedule for General Reports

Statement of Work

Second Task Order

Title: SMART GRID SUPPORT TO EEEL RECOVERY – THIS TASK ORDER WILL BE FUNDED BY AN AMERICAN RECOVERY AND REINVESTMENT ACT OF 2009 APPROPRIATION. CLAUSES 52.203-15, 52.204-11 AND 52.215-2 ALTERNATE I APPLY TO THIS TASK ORDER.

Purpose: The purpose of this task order is to for the Contractor to provide support services to EEEL in support of their efforts in standards developing and modeling to support the Smart Grid.

Contractor Requirements

Estimated Level of Effort The Government estimates that a total of 2,320 Contractor labor-hours may be required to perform the requirements of this Statement of Work.

The Contractor shall provide the following:

Subtask 1.0 – Smart Grid Support to EEEL

1.1 The Contract shall attend and participate in weekly SmartGrid status and/or transmission and distribution group meetings located at NIST as determined by the COTR. The Contractor shall provide a written electronic report to the COTR that documents the meeting and the attendees.

1.2 Smart Grid Face-to-Face Meetings: The contractor shall attend, participate, and provide technical support in monthly SmartGrid meetings with NIST personnel as determined by the COTR in support of the development of the Smart Grid infrastructure. The Contractor shall provide a written electronic report to the COTR that documents the discussion Subtask 2.0 – Improving Requirements Capturing for Smart Grid Standards Development

The Contractor shall design the methodology for improving capturing the requirements for the new Smartgrid standards within the SmartGrid application of the EEEL Database development efforts by completing the following tasks in sequence:

2.1.1 Developing a Model of Uses Cases - Currently Unified Modeling Language (UML) specifications contain use cases, but they do not specify the internal structure of use cases. The contractor shall develop a metamodel that specifies the structure of use cases and their components in a way that’s flexible enough to rigorously capture many existing use case formats.

Deliverable: The Contractor shall deliver the metamodel to the COTR.

2.1.2 Model for Change Tracking and Concurrency Control - The contractor shall provide an UML model for change tracking and concurrency control that:

· Determines when and how a use case (or component of a use case) changed;

· Determines who made a given change;

· Determines why a given change was made; and

· Reconstructs the state of a given use case at a particular given time

The Contractor must produce this model and have the model perform the above while ensuring that changes made at the same time by different users will not cause problems within the system.

Deliverable: The Contractor shall provide the UML Model to the COTR two weeks after delivery of the metamodel.

2.1.3 Functionality Tests

The Contractor shall develop a set of tests designed to test editor basic functionality

Deliverable: The Contractor shall provide a the tests developed as written electronic report to the COTR

2.1.4 Use Case Editor – The Contractor shall develop a working basic editor for all use cases. The editor must be:

· Based on the above use case, change tracking, and concurrency models

· Web browser based

· Developed with AJAX

· Provide the capability to display and store styled user-entered text

Deliverable: Use Case Editor to the COTR

2.1.5 Tests for Change Tracking – The Contractor shall develop a set of tests designed for the change tracking feature.

Deliverable: The Contractor shall provide all tests developed in an electronic written report to the COTR.

2.1.6 Enhance Use Case Editor – The Contractor shall enhance the existing editor by:

· Providing the ability to browse different version of uses cases and components; and

· Enabling the use case editor to display color coded differences between selected versions

Deliverable: Enhanced Use Case Editor

2.1.7 Pre-Conditions and Post-Condition Tests: The Contractor shall develop a series of precondition and post condition tests.

Deliverable: The Contractor shall provide all tests developed to the COTR.

2.1.8 Add Pre-conditions and Post-conditions to Editor – The Contractor shall Enhance the existing editor by:

· Adding the ability to add specific / precise preconditions and postconditions in the editor;

· Enable the editor to parse and apply Beanshell, YAML, or some other way approved by the COTR of describing an object graph; and

· Enabling Object Constraing Language (OCL) support or some similar way approved by the COTR of specifying constraints on object graphs.

Deliverable: Enhanced Editor

2.1.9 Scenario Merge Tests: The Contractor shall develop a set of tests designed for merging scenarios.

Deliverable: The Contractor shall provide all tests developed to the COTR in an electronic written report.

2.1.10 Merge Linear scenarios – The contractor shall add the ability to merge linear scenarios into a state or activity models. This merge is necessary for future test code generation.

Deliverable: Enhanced Editor with merge linear scenario ability.

2.1.11 Report Generation Tests: The Contractor shall develop a set of tests for report generation.

Deliverable: The Contractor shall provide all tests developed to the COTR in an electronic written report.

2.1.12 Develop Report Generator: The contractor shall develop a report generator that:

· Produces a state or activity diagram;

· Generates a PDF or Word “catalog” that organizes and summarizes all use cases;

· Generates a PDF or Word document containing everything about a use cases at a given point in time; and

· Provide a compilation of the above information in a single PDF or Word document.

Deliverable: Report Generator

2.1.13 Tests for Multiple Vocabularies Support: The Contractor shall provide tests for multiple vocabulary support for use in the use case editor Deliverable: The Contractor shall provide all tests developed to the COTR in an electronic written report.

2.1.14 Multiple Vocabularies Support for Use Case Editor: The Contractor shall enhance the Use Case editor to support multiple vocabularies. Specifically it provides the ability to have users in different domains view the same model, with different (domain specific) names for the same data.

Deliverable: Enhanced Use Case Editor to include Multiple Vocabularies Support.

Subtask 3.0 - Automated Generation of a Reference Implementation from Information Model

The Contractor shall take the new methodology developed in Subtask 2.0 and to build a software reference implementation in order to directly apply it to the SmartGrid standards development efforts.

3.1 Tests for Relational Database Code - The Contractor shall develop tests for developing relational database related code.

Deliverable: Tests for Relational Database Code developed provided to the COTR in an electronic written report.

3.2 Relational Database Implementation – The Contractor shall develop a working implementation of a relational database derived from the UML. This task will require the contractor to:

· Generate the SQL schema to hold the data;

· Generate initialization scripts; and

· Generate basic configuration files.

Deliverable: SQL Schema, Scripts, and Configuration Files

3.3 Tests for Schema Generation: The Contractor shall develop tests for schema generation which is really an expansion of the existing tests.

Deliverable: The Contractor shall provide all tests developed for Schema Generation provided to the COTR by electronic written report within one week of completion.

3.4 Process to Generating XML Schemas: The contractor shall develop a process for generating (from low noise UML models) XML schemas for validating data express as XML. This task involves modifying existing tools to support:

· Association classes;

· Object graphics; and

· Qualifiers (single level)

Deliverable: The contractor shall document and provide all written documentation describing the developed process to generate XML Schemas to the COTR within three weeks of completion.

3.5 Tests for Graphical User Interface (GUI): The contractor shall develop tests for the graphical user interface.

Deliverable: The Contractor shall provide all tests developed for Graphical User Interface to the COTR by electronic written report within one week of completion.

3.6 Functional GUI Browser: The Contractor shall develop a functional browser GUI that provides the ability to view and edit the data without any knowledge of XML This tool needs to be driven by meta-data. In addition, this tool must operate as:

· An inspector/editor for local objects;

· An inspector/editor for remote objects; and

· A viewer/editor for files

Deliverable: The contractor shall document and provide all code for Functional GUI Browser and provide a demonstration of the Functional GUI Browser to the COTR within three weeks of completion.

3.7 Test for Local Data API (Java Language: The Contractor shall develop tests for local data Application Programming Interface (API), based on Java Programming Language.

Deliverable: The Contractor shall provide all tests developed to the in electronic written format to the COTR within one week of completion.

3.8 Functional API (Java): The Contractor shall develop and fully document a Functional API that has the ability to manipulate local data utilizing Java programming language. This API must have the:

· Generation ability of code for each language including:

· Class definitions

· Object relational mappings

· Create, Retriever, Update, and Delete code (also known as CRUD)

· Ability to generate documentation

· Compilation and deployment of scripts Deliverable: Functional API (JAVA) and documentation provided in an electronic written report to the COTR within three weeks of completion.

3.9 Test for Local Data API (Agile Language): The Contractor shall develop test for local data APT based on the Agile Programming Langaugae.

Deliverable: All Tests developed for Local Data API provided in a written report to the COTR within one week of completion.

3.10 Functional API (Agile: The contractor shall develop and fully document a functional API for manipulating local data using an agile language (such as python, ruby on rails, JavaScript, Smalltalk, etc).

Deliverable: API and all documentation in a written report to the COTR within 2 weeks of completion.

3.11 Tests for Remote Data (Java): The Contractor shall develop tests for remote data API, based on Java programming language Deliverable: The Contractor shall provide all tests developed in a written electronic report to the COTR within one week of completion.

3.12 Functional API Remote (Java): The Contractor shall create and fully document a functional API for manipulating remote data using Java. This includes generation of:

This includes generation of:

· Client/Server sub and skeleton code

· Service endpoint code

· Documentation

· Configuration data

· Server management scripts

The Contractor must develop the Functional API Remote (Java) with at least two transpiration mechanisms from the following list: (Java RMI, XML over SOAP, Representational State Transfer (REST) using XML, Representational State Transfer (REST) using YAML (or JSON), ASN.1, and CORBA).

Deliverable: The Contractor shall provide a Functional Report API (Java) and all associated documentation to the COTR within three weeks of completion.

3.13 Tests for Remote Data (Agile): The Contractor shall develop tests for remote data API based on the Agile programming language.

Deliverable: The Contractor shall provide all tests developed for Remote Data (Agile) in a written report to the COTR within one week of completion.

3.14 Functional API Remote (Agile): The Contractor shall

create and fully document a functional API for manipulating remote data using an Agile Programming language (such as python, ruby on rails, JavaScript, etc).

Deliverable: The Contractor shall provide a functional fully documented API Remote (Agile) to the COTR within two weeks of completion.

3.15 Tests for Service Discovery: The Contractor shall develop tests for local service discovery.

Deliverable: All Service Discovery Tests developed provided in an electronic written report to COTR within one week of completion.

3.16 Functional Service Providing Discovery: The Contractor shall develop a fully documented functional service providing for discovery of services that utilize the data. This will require:

· Generation of service descriptions;

· Deployment and other management of service descriptions; and

· Management of discovery service itself.

Deliverable: The Contractor shall provide all documentation and a demonstration of the Service Providing Discovery to the COTR within one week of completion.

3.17 Integration of Reference Implementation: The Contractor shall integrate all previous tasks and subtasks of this SOW into a complete reference implementation. This reference implementation must include:

· Management scripts;

· All Documentation of Tasks and Subtasks Completed within this SOW; and

· Compellation of all Tests Developed within this SOW.

Deliverable: The Contractor shall provide an electronic written report and demonstration of all software code developed within this SOW to the COTR within one week of completion.

Period of Performance The period of performance for this task order is October 1, 2009 through June 30, 2010.

Place of Performance Most of the task order will be performed on-site at the NIST campus in Gaithersburg, Maryland, but some of the task order may be performed off-site as approved by the COTR.

Section 508 Accessibility All Electronic and Information Technology (EIT), as defined at FAR 2.101, supplied under this task order must conform to the Architectural and Transportation Barriers Compliance Board Electronic and Information Technology Accessibility Standards (36 CFR Part 1194). The applicable standards are available at http://www.access-board.gov/sec508/508standards.htm.

The following standards have been determined to be applicable to this Statement of Work:

____X___ 1194.21 Software applications and operating systems

____X___ 1194.22 Web-based intranet and internet information and applications

Government Furnished Information, Facilities, Supplies, and Services

NIST will:

· Provide the Contractor with the appropriate hardware, software, and equipment required for accomplishing day-to-day work requirements.

· Provide telephones for the Contractor’s business use only.

· Provide systems access and all necessary database and web server permissions, as necessary, to meet the requirements of this task order.

5) Revise Provision L.3 to read as follows:

L.3 PROPOSAL SUBMISSION INSTRUCTIONS

(a) General

(1) Each proposal volume shall be printable on 8½-inch x 11-inch paper.

(2) The proposal shall be submitted using only the following format(s): Microsoft Word (2003 or higher), Microsoft Excel (2003 or higher), Adobe Acrobat (version 9 or higher) .pdf.

(3) To aid in evaluation, the proposal shall be clearly and concisely written as well as being neat, indexed (cross-indexed as appropriate) and be assembled according to the provisions in this section. All pages of each part shall be appropriately numbered and identified with the name of the Offeror, the date, and the solicitation number.

(4) The Offeror shall submit its proposal electronically to Janine Kerns at janine.kerns@nist.gov so that it is received no later than the due date and time specified in this solicitation.

(5)

(6) Alternate Proposals. Alternate proposals are permitted. Each proposal submitted by an Offeror shall be an entirely separate proposal that addresses all solicitation requirements. Alternate proposals will be evaluated as a separate proposal.

(b) Overall Arrangement of Proposal

(1) VOLUME I - BUSINESS VOLUME

(A) Volume I consists of the actual offer to enter into a contract to perform the desired work. It also includes required representations, certifications, and acknowledgments; justifications for noncompetitive proposed subcontracts; identification of technical data to be withheld; and any other administrative information.

(B) Format and Content. Volume I shall include the following (in the order listed):

(1) A transmittal page that must show—

(i) The solicitation number;

(ii) The name, address, and telephone and facsimile numbers of the Offeror (and electronic address if available);

(iii) Names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this solicitation;

(iv) Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office; and

(v) Any other business or administrative information that the Offeror wishes to include in its proposal.

(2) Completed page 1 of the solicitation (“OFFER” section only); the person signing this document must have the authority to commit the Offeror to all of the provisions of the proposal. The offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation "DUNS" or "DUNS +4" followed by the DUNS or DUNS +4 number that identifies the offeror's name and address exactly as stated in the offer. The DUNS number will be used by the Contracting Officer to verify that the offeror is registered in the CCR database;

(3) Completed Solicitation Section K, Offeror Representations and Certifications; and

(4) A list of proposed labor categories, associated fixed labor rate for each proposed labor category, and associated functional responsibility for each proposed labor category that may be utilized on the contract to fulfill potential task order requirements (including but not limited to the first two task orders included in Solicitation Section J); these labor categories would become part of Section B of the IDIQ contract.

(2) VOLUME II - TECHNICAL VOLUME

(A) General

(1) Volume II consists of the Offeror’s response to the technical and management aspects of the acquisition. It should detail the means that the Offeror intends to use to satisfy the requirements of Sections C and J of this solicitation. It should be specific and complete in every detail. The proposal should be practical and be prepared simply and economically, providing straightforward, concise delineation of what it is that the Offeror proposes to do to satisfy the requirements of Solicitation. The proposal shall not merely offer to perform the work in accordance with the Statement of Work, but shall outline the approach proposed as specifically as practicable. A proposal that includes a mere repetition of solicitation requirements may be deemed to lack understanding of solicitation requirements and may not be considered further for award.

(2) In order that Volume II may be evaluated strictly on the merit of the material submitted, no cost/price information should be included in Volume II.

(3) Volume II shall not exceed 50 pages; the Government will not evaluate any pages beyond the 50th page.

(B) Format. Volume II shall include:

(1) Table of Contents

(2) List of Tables and Figures

(3) Technical Discussion. The technical discussion section should be the major portion of Volume II. It shall include three separate parts ((a), (b) and (c) below). The Offeror shall confine information pertaining to each part to its appropriate part.

A. Technical Approach

(1) The offeror shall provide a written, detailed technical approach describing how it proposes to satisfy the requirement of the Statement of Work for the first task order and for the second task order in Section J as follows:

a. Staffing Plan – The Offeror shall provide its Staffing Plan and an organizational chart, including proposed labor categories, for only the first task order and the second task order in Section J of the solicitation. The Staffing Plan shall identify the labor categories it proposes to complete the requirements of the first task order and the second task order, identify the ceiling number of labor hours proposed for each labor category, and thoroughly describe the rationale for the proposed labor mix.

b. Work Plan – The Offeror shall describe its proposed plan to accomplish the following: (a) manage individual subtasks required by the Statement of Work for Section J the first task order and the second task order; and (b) ensure that Contractor services and deliverables comply with the requirements of the Statement of Work.

B. Experience

(1) The Offeror shall provide the following:

a. A written detailed narrative that demonstrates the Offeror’s organizational background, experience, and qualifications performing work that is similar in scope to the requirements of Section C and Section J of the solicitation;

b. Complete resume for all proposed personnel for the first task order and the second task order.