PWS_FAS_Application_Development_-_Sources_Sought.pdf

1 | P a g e

SECTION C – PERFORMANCE WORK STATEMENT

INTRODUCTION

The United States Department of Agriculture (USDA) provides leadership on food, agriculture, natural resources, and related issues based on sound public policy, the best available science, and efficient management. The role of the USDA Foreign Agricultural Service (FAS) is to link U.S. agriculture to the world to enhance export opportunities and global food security.

The FAS Office of Chief Operating Officer (OCOO) is responsible for worldwide management operations, including budget and financial management, information technology applications support, human capital management, program and management compliance, international travel services, personnel security, emergency management, contracting, and training support. The OCOO Information Services Division (ISD) is the lead organization for this effort.

FAS is assessing and adjusting capital planning and investment control and acquisition planning policies and practices to more explicitly incorporate agile modular approaches in IT development and acquisition. Using these approaches, FAS expects to realize faster returns on IT investments and deploy technology solutions that will propel it towards a ͞21st century digital government, one that is efficient, effective and focused on improving the delivery of services to the American people.

C.1 BACKGROUND

As outlined in the 25 Point Implementation Plan to Reform Federal Information Technology Management, Federal agencies have traditionally taken a multi-year “grand design” approach for developing, modernizing, and enhancing investments in IT. This approach is grounded in the common notion that responsible development necessitates a full detailing of requirements before work can start. Although a seemingly reasonable assumption, practical evidence and private sector experience has shown that large and complex IT implementations often encounter cost and schedule overruns, as the painstaking process of requirements gathering too frequently takes years to complete.

Subsequently, agencies lose visibility into the performance of these multi-year IT development investments which affects their ability to implement corrective actions that reduce risk or mitigate financial exposure. The Government increases investment risk in these situations because: (1) the IT solutions that had once addressed agency requirements may no longer be pertinent or a priority; (2) substantial funds are allocated towards outdated solutions without any returns on the investments; or (3) agencies encounter budgetary constraints before substantive work is completed.

To help resolve these issues, modular approaches should be used in the development of IT investments, allowing agencies to implement significant capabilities for investments through the use of modular solutions that can be defined, developed, and deployed within months instead of several years.

2 | P a g e

The Information Services Division (ISD) has adopted agile software development practices as its modular approach to divide investments into smaller parts in order to reduce investment risk, deliver capabilities more rapidly, and permit easier adoption of newer and emerging technologies.

C.2 APPLICABLE DOCUMENTS

Contracting Guidance to Support Modular Development June 2012

C.3 ISD Services

Efforts in support of ISD may be deleted and added during the life of the contract.

C.4 SCOPE

As specified by the Government, the Contractor(s) shall perform the efforts required under this contract as part of Integrated Project Teams (IPT) comprised of a mix of Government and contractor personnel, including contractors working under other task orders and/or contracts to deliver business results using agile software development techniques.

The scope of this PWS encompasses six work streams. Each work stream consists of multiple subtasks. The work streams shall be performed on a labor hour basis.

Expert support is required to re-engineer the way the Agency uses technology to support agency-wide business process improvement initiatives and carry out its day-to-day work. Projects will vary in size and scope, depending upon the requirements of

FAS.

The Contractor shall be directly responsible for ensuring the accuracy, timeliness, and completion of all subtasks defined under this contract by the COR. The Contractor shall provide a wide range of contractor support to help FAS and its sub-organizations assess programmatic success, consolidate functions, and streamline management and IT processes to achieve transparency and better management controls. The Contractor shall ensure that software development work and deliverables will utilize secure coding techniques and meet all requirements for secure coding practices and assessment and authorization (A&A) as required by NIST, OMB, USDA, and FAS.

The scope includes development and modernization of IT applications and systems to achieve outcomes via improvement to or complete redesign of people/process/technology solutions; working with government staff to identify programmatic improvement opportunities that can be effected through more strategic deployment of information technology; and proposing plans for business process improvement and business process reengineering efforts that dovetail with the overhaul of the way the Agency uses information technology resources.

3 | P a g e

DEVELOPMENT ENVIRONMENT

Operating systems: Windows 7, Windows 10, Windows 2003/2008/2012, Database: Microsoft SQL Server 2005, Microsoft SQL Server 2008 Development Tools/Components: Microsoft Visual Studio .NET 2005/2008/2010/2012, (VB.Net, C#, ASP.NET), Microsoft Visual Studio 6.0 (Visual Basic, Visual C++), HTML, and XML, Drupal, Infragistics NetAdvantage, Aspose, Dundas, Farpoint and Telerik components

BI/Reporting Tools: SAP Business Objects and Reporting Tools and Components, Microsoft Reporting Services, Crystal Reports, Hyperion SQR, PerformancePoint Server, SharePoint Server, SQL Server Analysis Services, SQL Server Data Mining, Excel and PowerPovit for Excel and SharePoint

Collaboration Tools: Microsoft SharePoint (WSS, MOSS 2007/2010/2013), Web Service Technologies: SOAP Requirements, Defect, Issue Management & Source Control: MS Team Foundation Server

(TFS) 2012

Vulnerability testing: Veracode Project Management: Microsoft Project & Project Online

C.4.1 Program Management Office Support - Labor Hour The Contractor shall provide the management structure and processes to support all of the technical and administrative efforts required by the task assigned under this PWS.

The Contractor shall organize and manage individual subtasks in accordance with the priorities communicated by the COR or their delegates (Government Project Managers).

Program Management Office (PMO) Support includes day to day on-site project management, direction of the work assigned to the Contractor and the reporting of subtask status. The Project Manager shall be the single point of contact for communications regarding agency directives or problems and any other administrative communications. The PMO shall be responsible for communicating to their subordinate employees as appropriate. The Project Manager shall ensure compliance with all NIST, OMB, USDA, FAS, FISMA and 508 procedures, laws and regulations in the execution of this contract.

The Contractor shall lead technical development including coordinating the work of the development team and assuring compliance with the ISD Enterprise Architecture.

The Contractor shall provide the Government Project Manager (PM) a Project Plan for each subtask within a work stream setting forth the Program Charter that describes the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for each assigned effort.

Microsoft Project shall be used to baseline the schedule, resources and content for all projects before their approval and work begins. The contractor shall maintain project plans in accordance with ISD’s Integrated Master Schedule standard operating procedures and perform Integrated Resource Management using ISD’s Enterprise Resource Pool shared by all projects. The Artifacts and Milestones defined in section

4.1.1 are required in all project plans delivered under this contract. ISD reserves the right to refine the milestones and artifacts defined in Section 4.1.1 over the life of this contract. The template in section 4.1.2 is an example of the kind of plan the contractor shall produce for each release of software.

4 | P a g e

Microsoft Team Foundation Server (TFS) is required to be used to track and manage user stories, product backlogs, detailed story requirements, Sprint content, test cases & test results, defects (bugs) and issues. TFS shall also be used as a code repository in accordance with FAS ISD’s standard operating procedures for deployment.

The Project Plan shall detail the key activities and milestones, allocation of staff and other resources necessary for the successful completion of this contract. The COR shall receive the Project Plan in both electronic form (Microsoft Project) and hard copy (when requested). The COR must provide approval to move forward on activities in the project plan before any development activities occur. The Contractor shall request prior approval on all activities not included in the plan or any modifications to the plan after approval has been given.

The Contractor shall minimize staff changes in order to minimize risk to the activities performed under this contract. Within three business (3) days of when it is known that such personnel changes are necessary, the Contractor shall arrange a personal or telephonic meeting with the COR and the Project Manager, to discuss the plan for transition of the work. Following the meeting, a report shall be submitted to the Government to address the meeting and topics, including the personnel change and a written transition plan to include the schedule for the transition; training and knowledge transfer approach; and any other details appropriate to ensure the least amount of disruption to the subtask(s) being impacted by the transition. The transition shall not in any way impact commitments associated with already existing work.

C.4.1.1 Project Artifacts & Milestones

Required Artifacts

Artifact Form Location

Product Backlog Work Items in TFS TFS Project Site

Project Plan Microsoft Project IMS Repository

Story Cards for each Sprint Tasks in project plan Project Plan

Acceptance Test Cases Work Items in TFS TFS Project Site

Acceptance Test Results <TBD> TFS Project Site

Regression Test Cases Work Items in TFS TFS Project Site

Regression Test Results <TBD> TFS Project Site

User Communication Plan Tasks in project plan Project Plan

User Training Plan Tasks in project plan Project Plan

Release Notes Word Document TFS Project Site

5 | P a g e

Code Base Code database in TFS TFS

Milestones

Milestone Purpose

Release Planning Complete Verify that the estimated schedule, cost and content (story cards) to be delivered in the release are well defined and baselined

Sprint 2..n Planning Complete Verify that the specific story cards to be delivered in the Sprint are well defined

Sprint Complete Verify that the Sprint delivered the story cards it was supposed to

Regression Test Complete Verify that new capabilities haven’t broken something in the rest of the application

Ready for UAT Verify that the release is in a staging environment and ready for User Acceptance Testing

Production Readiness Verify that the release is in a production environment in accordance with the FAS ISD deployment process and ready for production use

Go-Live Verify that the users have been notified and trained on how to use the release

C.4.1.2 Project Plan Template

ABCD Project

Release a.b Planning

Create/Update Backlog as TFS Work Items Estimate number of sprints in the release Prioritize backlog and Assign Stories (i.e., SC’s) to Sprints Create the Project Plan for the release, including

Test Plan (Unit, Sprint, Regression, Performance, Stress, User Acceptance tests) User Communication Plan User Training Plan

Project Plan approved by government Project Plan baselined in Microsoft project Milestone: Release Planning Complete (includes Sprint 1 Planning Complete)

Sprint 1

6 | P a g e

BA/User Support Fill in required details on the Sprint’s User Stories (S.C.’s) Define Sprint Acceptance Criteria

Development

SC1: ….

SCN: ….

Unit test developed code Move developed code to test environment

QA/QC:

Test Sprint against Acceptance criteria (e.g., SC1..SCN)

Log test cases and test results in repository File work items as appropriate

Demonstration: (if needed) Move developed code to staging environment Demonstrate capabilities to users Collect feedback/changes required File collected changes as Backlog/Work Items as appropriate

Sprint Completed Sprint 2… N (If needed for the Release)

Update Backlog as appropriate Prioritize backlog & update stories (i.e., SC’s) for remaining sprints Update the project plan as appropriate Sprint Planning Complete Execute the Sprint 1 template for the next Sprint

Deployment Regression test application, file work items as appropriate Move code to staging environment Milestone: Ready for UAT UAT, file work items as appropriate Training deliverables complete Release notes complete (what’s in release, any issues, exceptions) Check code into Code Database Move code to production environment Milestone: Production Readiness

Announce release to users with release notes Provide any pre-Go-Live training as required

Milestone: Go-Live Provide any post Go-Live training as required “Lessons Learned” review completed

C.4.2 Business Analysis and Process Re-engineering Support - Labor Hour The contractor shall provide leadership in requirements management, backlog prioritization and software release planning. For each development effort under this contract, the contractor, as part of an IPT, shall meet regularly to "groom the product backlog", in formal and informal meetings to accomplish:

• removing user stories that no longer appear relevant

• creating new user stories in response to newly discovered needs

• re-assessing the relative priority of stories

7 | P a g e

• assigning estimates to stories which have yet to receive one

• correcting estimates in light of newly discovered information

• splitting user stories which are high priority but too coarse grained to fit in an upcoming software release

As part of its planning activities, the Contractor shall identify related architectural, regulatory, security, interoperability, and integration requirements. All requirement specifications shall be at sufficient detail to perform system design and include quantifiable baseline business process operating metrics where appropriate. The Contractor shall utilize the prioritized product backlogs to develop sprint and software release plans for all development and modernization subtasks performed under this contract.

The Contractor shall provide recommendations based on thorough evaluations of product feature set, current needs, and cost/benefits to the Government.

In support of software conversion efforts involving re-hosting to another platform, architecture, operating system, database, programming language, and/or communications system, the Contractor shall provide a description\ of the current hardware and software environment, and if applicable, data distribution methods, as well as parallel processing and/or system validation of old and new systems prior to implementation.

The Contractor shall develop Business Process Re-Engineering (BPR) strategies that leverage the FAS enterprise architecture to bridge performance gaps in business processes. The Contractor shall identify opportunities for business process improvement across FAS by facilitating collaboration among all activities to improve FAS business practices and services, as required. The contractor shall make recommendations for improvements in efficiency, interoperability and integration among USDA and\or FAS processes and\or systems. Recommendations shall maximize the use of COTS software solutions, emerging technologies, and best practices to continuously enhance FAS’ operations and services while ensuring alignment with over-arching Enterprise Architecture guidelines. Furthermore, where applicable, recommendations shall identify FAS technology gaps and/or functional system duplications.

a. Requirements Analysis, Design and Planning USDA FAS uses a Software/System Development Life Cycle (SDLC) to describe important elements of software development in a common and consistent way. The FAS SDLC represents an iterative process broken down into Six Phases creating a methodology that satisfies the unique constraints of the FAS development environment.

Offeror shall provide services in performance of the following Phases for new development and to support maintenance and upgrade of existing, deployed and operational software:

• Requirements Analysis Phase: Gather and analyze business, functional and nonfunctional requirements to create one unambiguous set of requirements

• Design Phase: Perform both high level design and detailed design

8 | P a g e o High level design involves the diving or partitioning of the system into conceptual components and specification of the components' behavior o Detailed design specifies the implementation details and functionality of the components from the high level design

• Planning Phase: Perform both high level design and detailed level planning Key focus areas include:

1) Requirements Analysis Phase

a. Analyze a series of High Level Design artifacts based on requirements received from FAS and produce for approval by business sponsors

b. Allocate functionality, dividing the proposed system into subsystems and model the data requirements based on a combination of new and legacy data sources

c. Design and provide documentation of the user interface and any required interfaces between existing systems, including all artifacts necessary to support Assessment and Authorization (A&A)

d. Design and document the testing strategy for the completed system and its components

e. Develop Proof-of-Concept prototypes based on the design requirements, as necessary

2) Design Phase

a. Design and document systems, user interfaces, communications, requirements, application components, and security using the mandates of SDLC, the Reference Architecture, and the Common Application Framework in the stated order of precedence, following the completion of the High Level Design phase

b. Develop systems using current platforms previously identified, with the accepted knowledge that these platforms may change

c. Design Application programs to take advantage of state-of-the-art hardware and software capabilities

d. Identify all functions relating directly to the structuring of programming runs and the identification of programs, and modules within programs, that make up the application

3) Planning Support Phase

a. Provide government project managers with estimated completion dates for each software development lifecycle phase to meet deadline for completion of the WBS; Meet or complete before estimated completion dates for each assigned WBS task unless special circumstances approved by project manager permit missing the completion date

b. Prepare or assist in preparation of New/Revised Software Modules into Production Environment

c. Correctly prepare migration documents, transport and installation instructions for migrating new code to the production environment

d. Plan to Resolve overwrite and dependency checks for objects

e. Plan to Resolve questions regarding transports quickly

f. Plan and Review how changes impact current Environments

g. Plan to Identify and resolve application conflicts

9 | P a g e

C.4.3 Development, Maintenance and Administration of IT Applications and Systems – Labor Hour

The Contractor shall iteratively develop high quality software, with minimum defects, in accordance with the approved software release plan.

The Contractor shall ensure that all specified web-based system interfaces contain compatibility among system components in the operational environment.

The Contractor shall provide software solutions that include user interfaces that are intuitive, user friendly, conform to usability guidelines and meet Congressional mandate concerning access to federal information technology by members of the public and federal employees with disabilities (Section 508 of the Rehabilitation Act).

The Contractor shall ensure that new releases of software maintain previously provided functionality, while providing enhanced capabilities or systems corrections, unless otherwise directed by the Government.

The Contractor shall develop and/or, modernize FAS IT Applications and Systems using component-based solutions.

The Contractor shall utilize ISD’s development, staging, and production environments for all application software releases in accordance with ISD deployment and change management procedures. All software shall be thoroughly tested before being promoted from development to staging environments. The contractor shall support Use acceptance activities required by the ISD deployment procedures and change procedures.

The Contractor shall work with the Configuration Change Board (CCB) and Integrated Project Team (IPT) to ensure that application software releases are coordinated with the customer to minimize the impact on the user community. The Contractor shall ensure that a communication plan exists to notify the user community of releases of new functionality.

The Contractor shall utilize state-of-the-art development processes and standards that meet OMB guidelines, USDA OCIO standards, and industry best practices for all development and modernization responsibilities.

The contractor shall utilize role-based user permissions by application as approved by the application’s Government PM.

a. Coding, Integration and Systems Testing and Production Support As part of USDA FAS use of a Software/System Development Life Cycle (SDLC) to describe important elements of software development in a common and consistent way.

The FAS SDLC represents an iterative process broken down into Six Phases creating a methodology that satisfies the unique constraints of the FAS development environment.

Offeror shall provide services in performance of the following Phases for new development and to support maintenance and upgrade of existing, deployed and operational software:

10 | P a g e

• Coding Phase: Transform the designs into a working system that satisfies all the requirements

• Integration and Systems Testing Phase: Evaluate the software/system against the Test Plan to ensure proper function in the intended environment; Check for errors, bugs, and interoperability

• Production Deployment Support Phase: Support the deployment of completed software and systems within the application area, ensuring compliance with established operating procedures and policies.

• Operational / Production Support Phase: Provide expertise and support to resolve production problems identified during routine operation of Systems, be responsible for research and resolution of problems identified as a result of production processing of the systems, including improperly functioning code and incorrectly implemented requirements.

Key focus areas include:

1) Coding Phase

a. Follow FAS standards for construction on new systems and modifications made to existing systems

b. Responsible for all work products identified in the SDLC or otherwise specified in the individual task order

c. Write or modify code using programming techniques or industry appropriate technologies and as required by the specific requirements of each task order

d. Deliver required SDLC artifacts, conduct quality, code and performance reviews

e. Ensure code is designed and modified in compliance with FAS performance standards as outlined in the Software Quality Guidelines

f. Design and document the testing strategy for the completed system and its components

g. Develop Proof-of-Concept prototypes based on the design requirements, where required

h. Follow the FAS Change Management Process

2) Integration and Systems Testing Phase

a. Responsible for unit, integration, string/scenario, and system testing of all new systems and for all changes or enhancements made to the applications

b. Responsible for constructing real world testing scenarios

c. Review Test results to determine and confirm that all requirements have been satisfied and that no adverse changes have been inadvertently made to existing functionality

d. Do NOT transfer any code, test scenarios, or test results to Acceptance Testing until after the Government has reviewed the system or process and the COR or designated Government Technical Lead has authorized the move to Acceptance Testing

e. Implement automated testing processes and technologies in compliance with FAS standards while constructing the application

f. Participate in and support other Government test activities as required by the

COR

g. Support beta test activities, as required by the COR

h. Assist and provide advice and guidance on problem resolution

3) Production Deployment Support Phase

11 | P a g e

a. Detailed deployment plan for all software items

b. Fallback and recovery procedures in the case of deployment failure

c. Communications Plans for detailing deployments

4) Operational / Production Support Phase

a. Perform system maintenance, testing, log analysis, troubleshooting

b. Ensure code changes are correctly installed 100 percent of the time

c. Participate in conference calls or meetings to address user questions as needed after migration of new/revised code

d. Develop and review solution alternatives, and perform impact analysis with customers and system users for fixes, enhancements and other changes

e. Elicit customer requirements through facilitation sessions, joint application development sessions, or one-on-one meetings and interviews

f. Analyze operational problems, develop solutions and take corrective action

g. Assist specialists in analysis and corrective action

h. Assist with problem identification and resolution in existing applications by analyzing system processes, interrelationships, interfaces, and data

i. Resolve technical/application related issues

j. Coordinate with system/database administrators to resolve Production operational issues

k. Respond to production issues and assist in initiating recovery or restart services

l. Recommend application performance improvements

m. Provide Root Cause Analysis (RCA) for problem situations impeding operations

n. Support implementation of mandated code security patches and configuration changes

C.4.4 Training and Documentation - Labor Hour The Contractor shall be responsible for the development of training materials for software developed under this contract. The Contractor shall ensure that the training is appropriate according to user levels/needs (e.g. end users, administrators, analysts, help desk support, and management).

The contractor shall ensure delivered systems are fully documented in accordance with direction from the COR.

a. Requirements Documentation Offeror shall analyze and produce for approval by business sponsors a series of High Level Design artifacts based on requirements received from FAS business users.

Offeror shall allocate functionality, dividing the proposed system into subsystems, and document data requirements based on a combination of new and legacy data sources.

Key focus areas include:

1) Design and provide documentation of the user interface and any required interfaces between existing systems, including all artifacts necessary to support Certification and Accreditation (C&A)

2) Coordinate activities with the applications development, database management and the records management team in order to produce complete documentation

3) Produce and Provide documentation

12 | P a g e

• Document component construction and maintenance as required

• Document how-to aides, guides or manuals to support migration fixes, code, patches, updates to application components/modules

• Provide problem analysis, activity reports and white papers as required

b. Workforce Training Support Offeror shall provide subject matter expertise to assist the formulation and delivery of FAS workforce in-house training needs.

Key focus areas include:

1) Provide FAS Application Training and Coordination

2) Provide support to develop a highly skilled and engaged workforce through customized curriculum catered to FAS application needs. Provide training on upcoming enterprise technology changes. Create and deliver working group sessions to cover training topics relevant to the FAS enterprise.

3) Provide Lunch and Learn sessions on new technology and industry best standards relevant to the enterprise. Contribute and maintain self-service information knowledgebase on the FAS wiki. Create and deploy self-service training modules for implementation into AgLearn and/or storage on SharePoint

C.4.5 Security - Labor Hour The Contractor shall provide security services for development and modernization efforts, ensuring that system development complies with all applicable USDA regulations and secure coding practices. Security vulnerabilities detected in software created under this contract using Veracode or similar scanning tools shall be mitigated prior to deployment.

The contractor shall be responsible for understanding and identifying the risks associated with security vulnerabilities identified through independent software scanning and make mitigation recommendations to the Government. The contractor is responsible for developing a remediation plan for all identified Security vulnerabilities and a mitigation plan for all security vulnerabilities that cannot be resolved or pose no threat to the network.

a. Application Security Requirements Definition and Design Offeror shall provide technical expertise to support application specific security requirements for all corporate applications.

Key focus areas include:

1) Document application specific security requirements based on data classification, access control requirements, integration requirements and downstream dependencies

2) Recommend design patterns, coding standards and best practices that reinforce the security of information within the enterprise applications

3) Develop integration of specific applications with security services, identify repositories, and implement access control rules for business processes and applications

4) Document application-specific security requirements in the design documentation for the solutions and applications for reviews with Enterprise Architecture and IT Security reviews

13 | P a g e

5) Support Enterprise Architecture reviews and quality gates to ensure application-specific security requirements are tested before application and solutions are deployed in production environment

6) Recommend, develop and document application-specific security design for user access, data integration and application integration design patterns

C.4.6 Server Access Control and Database Administration - Labor Hour

As FAS prepares to migrate to the more secure Enterprise Data Center (EDC), and in its efforts to strengthen organizational implementation and monitoring of access controls (i.e, authorization, access, visitor control, transmission medium, display medium, logging), FAS requires support to manage Access Control Policy and Procedures based on FAS System Administration procedures. Access Control and System Administration procedures shall be defined at the information system level.

The contractor shall develop, disseminate, and review/update:

• Formal, documented access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance

• Formal, documented procedures to facilitate the implementation of the access control policy and associated access controls.

• Implement management of information system accounts, including:

o Identifying account types (i.e., individual, group, system, application, guest/anonymous, and temporary) o Establishing conditions for group membership o Identifying authorized users of the information system and specifying access privileges o Requiring appropriate approvals for requests to establish accounts o Establishing, activating, modifying, disabling, and removing accounts o Specifically authorizing and monitoring the use of guest/anonymous and temporary accounts o Notifying account managers when temporary accounts are no longer required and when information system users are terminated, transferred, or information system usage or need-to-know/need-to-share changes o Deactivating: (i) temporary accounts that are no longer required; and (ii) accounts of terminated or transferred users o Granting access to the system based on: (i) a valid access authorization;

(ii) intended system usage; and (iii) other attributes as required by the organization or associated missions/business functions o Reviewing accounts

The contractor shall ensure the concept of least privilege, allowing only authorized accesses for users (and processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions, is in place.

The contractor shall continuously verify and validate documented system administrator procedures produce the desired outcome in each FAS hosting environment (Development, Staging, Production, etc.) based on FAS System Administration

14 | P a g e

Manuals. All contractors on this task should have a minimum of secret security clearance.

C.5 DELIVERABLES (for all streams)

C.5.1 Reports C.5.1.1 Monthly Reports

The Contractor shall document the efforts performed in the completion of each subtask in a detailed Monthly Status Report due on or before the 10th of each month. The status report shall include, at a minimum:

• Progress for the period: detailed progress report of findings, activities and accomplishments during the reporting period, and summary of work accomplished during the reporting period and percent complete, as appropriate.

• Activities planned for the next reporting period: planned activities, as well as the status of any/all deliverables, including planned delivery date(s) and actual and/or anticipated delivery date(s). Reports shall compare the status achieved to the planned goals and objectives of the subtask.

• Problems encountered: identification of any problems, issues or delays and recommendations as to their resolution, and any corrective action that was taken to correct identified problems.

• Strategy revisions: recommended changes to include any lessons learned

• Recommendations for improvement, and future plans.

C.5.1.2 Performance, Cost and Conference Reports

Performance and Cost Reporting shall be submitted on a monthly basis. Cost reporting shall consist of entering actual hours expended by labor category by subtask into the Government’s subtask management system (TMS). The total hours entered across all subtasks shall equal the amount of hours invoiced for the same month. Performance reporting shall consist of the current financial status and the projected requirement of funds and labor hours, for each subtask performed in support of sections C.4.1, C.4.2, C.4.3 and C.4.5, C.4.6, as well as the entire contract.

Conference Reports shall be submitted on an as required basis to document any significant understandings arrived at through the attendance of a conference or IPT working group meeting. Reports are also necessary to document any travel performed during the contract.

In addition to the items above, the Contractor shall, at the request of the COR, deliver:

• Project plans, including level of effort, WBS, and cost estimates

• Meeting minutes for all IPT and PMO meetings.

• Action item tracking of overall contractual support for FAS management

• Action item tracking on progress of subtasks within work streams

• Milestone status reporting to provide documentation on progress of overall contract support efforts

• Periodic reports on work stream progress

In fulfillment of this effort, the Contractor shall provide the applicable initial deliverables within 10 business days of contract/task signing:

15 | P a g e

• Plan to provide project management office support

• Plan to provide business analysis and process re-engineering support

• Plan to provide maintenance, development, modernization and enhancement of information technology applications and systems support

• Plan to provide operation of information technology applications and systems support

• Plan to provide documentation and training support

• Plan to provide server and database administration support

The contractor shall create and maintain a project schedule in accordance with ISD’s Integrated Master Schedule (IMS) Standard Operating Procedure (SOP) and perform Integrated Resource Management using ISD’s Enterprise Resource Pool shared for all projects. ISD reserves the right to refine the IMS SOP, milestones and related artifacts over the life of this contract.

The project schedule shall detail the key activities and milestones, allocation of staff and other resources necessary for the successful completion of this contract. The COR shall receive the project schedule in both electronic form (Microsoft Project) and hard copy (when requested). The COR must provide approval to move forward on activities in the project schedule before any activities occur. The Contractor shall request prior approval on all activities not included in the plan or any modifications to the plan after approval has been given.

All deliverables shall be submitted to the COR or COR designee, unless otherwise agreed upon. Unless otherwise specified, the Government will have a maximum of ten

(10) working days from the day the draft deliverable is received to review the document, provide comments back to the Contractor, approve or disapprove the deliverable(s).

The Contractor will also have a maximum of ten (10) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government.

C.5.1.3 Final Report The Contractor shall provide a final report, to the COR, at the conclusion of this effort.

The report will summarize objectives achieved, significant issues, problems and recommendations to improve the process in the future.

C.5.1.4 Deliverable Table Reference Milestone/Deliverable

Responsibility Date

C.8.1

Orientation Briefing Schedule

Government/Contractor

Contract Award (CA)+ 4 weeks

C.4.1

Project Plan

Contractor

Final before development work starts.

Weekly updates.

16 | P a g e

C.5.1 Monthly Status Report Contractor 10th of each month

C.1.3 Final Report Contractor End of Period of Performance Expiration

C.5.1.5 Inspection and Acceptance Criteria

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR.

C.5.1.6 General Acceptance Criteria General quality measures, as set forth below, will be applied to each work product received from the contractor under this Performance Work Statement.

• Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

• Clarity - Work Products shall be clear and concise. Any/All diagrams shall be easy to understand and be relevant to the supporting narrative.

• Consistency to Requirements - All work products must satisfy the requirements documented in product backlogs and/or other requirements artifacts.

• File Editing - All text and diagrammatic files shall be editable by the Government.

• Format - Work Products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals.

Timeliness - Work Products shall be submitted on or before the due date specified in this Performance Work Statement or submitted in accordance with a later scheduled date determined by the Government.

C.5.1.7 Performance Assessment Plan

17 | P a g e

C.5.1.8 Performance Based Remedy Process If the Composite score falls below 70, as stated in the Performance Assessment Plan, penalty costs will be incurred as follows: $2.00 per labor hour, which represents a portion of profit in the fully loaded labor rate. This amount will then be multiplied against the total number of hours expended for the specific performance period, either the Base Period or an Option period.

A detailed example of the remedy calculation is as follows:

EXAMPLE

LABOR CATEGORY: HOURS:

Project Manager 1920 Senior Business Analyst 1920 Business Analyst 1920 Design and Development Engineer 1920 Midlevel Application Developer 1920 Application Developer 5760 Documentation Specialist 1920 Senior Database Designer 1920 Quality Assurance Spec 1355 Senior Training Specialist 1000 Security Design & Development Engineer 1000 22555

Security Design & Development Engineer

TOTAL HOURS:

For a Composite score less than 70, the following adjustment will occur in this example: Hours 22,555 X $2.00=$45,110.00 in penalty costs are assessed.

End of Example.

0-69 Points Unsatisfactory

70-89 Points Satisfactory

90-100 Points Excellent

Cost 20% Funds expended before Subtask is completed. (Cost exceeds budget)

Subtask performed at or below budget.

Subtask is performed at least 5% under budget.

Actual Cost vs Budget

Schedule 50%

Late on one or more major milestones, or more than 25% of the minor milestones are late.

All major milestones on time, and 10% to 25% of the minor milestones are late.

All major milestones on time, and fewer than 10% of the minor milestones are late.

Actual vs Plan/Requirement

Customer Satisfaction (scale of 1 to 5, with 5 being best)

30% Average satisfaction score below 3.

Average satisfaction score between 3 (inclusive) and 4 (exclusive).

Average satisfaction score greater than or equal to 4.

Periodic Customer Surveys

Total Std Wt: 100% Total Work Area Wt: 100%

C.4.3 100.00%

Composite Score of less than 70 will be subject to reduction of $1.00 per hour of effort for the contract, in accordance with the Performance Based Remedy Process.

AQL Surveillance Method Incentive Work Area

Work Area Wt.

Standard Std Wt.

18 | P a g e

If such an adjustment as described above results in a refund of payments already made by the Government under the contract, the adjustment will provide for the recovery of such costs to the Government together with interest thereon computed at the rate determined by the Secretary of the Treasury pursuant to Public Law 92-41, 85 Stat. 97, from the time the payment by the Government was made to the time the adjustment is affected.

Any disagreement arising under this provision shall be a dispute under the Disputes Clause of this contract. In the event such a dispute arises, any adjustments under this clause will be deferred until resolution of the dispute.

C.6 SUBTASK PROCESS

The labor hour work to be performed by the contractor will be defined by Government personnel using the SubTask Form (ATTACHMENT 7).

The Contractor’s Project Manager shall serve as the primary liaison with FAS’ COR regarding the performance of this contract. The Contractor shall submit a written Project Plan in response to subtasks from the COR. This plan is the agreement between FAS and the contractor on all aspects of a subtask. The Project Plan shall establish the schedule of deliverables and the resources required.

The Contractor shall meet with the COR prior to implementation of a subtask to review and confirm functional requirements of each request. The Project Plan must be approved by the COR, before work begins.

At a minimum, the STMP shall include:

1. A description of any required user training and documentation.

2. The estimated schedule, to include each activity start and completion dates, as well as estimated number of hours required and cost to complete the subtask.

3. Contract personnel to be assigned to the subtask, by name and labor category.

The contractor shall assign personnel based upon the requirements defined in each subtask. The Contractor will have access to create and maintain project schedules using up to five ISD Microsoft Project licenses.

Weekly meetings shall occur between the Government PM and the contractor’s Technical Project Manager to review the status of each subtasks’ performance to plan.

The contractor shall submit monthly summary reports to the COR and CO on all work assigned by the 10th business day of each month.

C.7 Transition Plan The Contractor shall provide a well-organized transition plan that, at a minimum, addresses the items identified below. The Transition Plan should propose a logical strategy to mitigate risk to the Government.

a) Overview of how transition will be implemented and managed.

b) Transition of key personnel and non-key personnel.

c) Transition of Existing Efforts.

19 | P a g e

d) Staffing plan implementation

e) Resources required for the transition

f) Responsibilities

g) Timeline

h) Risks and associated implications.

i) Risk mitigation procedures.

C.8 OTHER PERFORMANCE REQUIREMENTS

C.8.1 Orientation Briefing Within two weeks of contract award, the Contractor shall conduct an orientation briefing for the senior staff of FAS to initiate the communication process between the FAS and Contractor. In this session, key contract participants will be introduced. Roles will be explained, communication ground rules will be reviewed, and discussion of work streams, and subtask requirements and objectives will be discussed to assure a common understanding.

The Orientation Briefing will be held at a date and time that is mutually agreed upon by both parties.

The completion of this briefing will result in the following:

a) Introduction of both Contractor and Government personnel performing work under this contract.

b) The Contractor will demonstrate confirmation of their understanding of the work to be accomplished under this PWS.

C.8.2 Contractor Interfaces

The Contractor and/or his/her Subcontractors may be required, as part of the performance of this effort to work with other Contractors working for the Government. Such other Contractors shall not direct this Contractor and/or their Subcontractors in any manner.

Also, this Contractor and/or their Subcontractors shall not direct the work of other Contractors in any manner unless otherwise directed by the COR.

The Government shall establish an initial contact between the Contractor and other Contractors and shall participate in an initial meeting at which the conventions for the scheduling and conduct of future meetings/contacts will be established. Any Contracting Officer’s Representatives (CORs) of other efforts shall be included in any establishment of conventions.

C.8.3 Contractor Employees Contractor personnel shall present a neat appearance and be easily recognized as contractor employees by wearing a Security Identification Badges at all times while on Government premises. When Contractor personnel attend meetings, answer phones, and work in other situations where their status is not obvious to third parties they must identify themselves as such to avoid creating the impression that they are government employees.

20 | P a g e

C.8.4 Physical Security

The Contractor shall be responsible for safeguarding all government property provided for contractor use. At the end of normal duty hours and/or after normal duty hours, all government facilities, equipment and materials must be secured.

C.8.5 Key Controls The Contractor shall establish and implement methods of making sure all keys issued to the contractor by the government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall not duplicate any keys issued by the government. The Contractor shall immediately report to the COR any occurrences of lost or duplicated keys.

In the event keys, other than master keys, are lost or duplicated, the contractor may be required, upon written direction of the COR, to re-key or replace the affected lock or locks at no cost to the government. The Government may, however, at its option, replace the affected lock or locks or perform re-keying and deduct the cost of such from the monthly payment due the contractor. If a master key is lost or duplicated, the government must replace all locks and keys for that system and the total cost deducted from the monthly payment due the Contractor.

The Contractor must prohibit the use of keys issued by the government by any persons other than the contractor's employees. Opening of locked areas by Contractor employees to permit entrance of persons other than contractor employees engaged in performance of work requirements in those areas is prohibited.

C.8.6 Emergency or Special Event Services Occasionally, the Contractor may be required to perform and/or provide services outside the normal hours of duty. These occasions will be infrequent and require services be performed after normal working hours in the evening and/or weekends (Saturday and Sunday). The COR and the Contractor will mutually agree upon any/all deviations to the schedule.

C.9 QUALITY ASSURANCE

The COR will review, for completeness, preliminary or draft documentation that the Contractor submits, and may return it to the Contractor for correction. Absence of any comments by the COR will not relieve the Contractor of the responsibility for complying with the requirements of this PWS. Final approval and acceptance of documentation required herein shall be by letter of approval and acceptance by COR. The Contractor shall not construe any letter of acknowledgment of receipt material as a waiver of review, or as an acknowledgment that the material is in conformance with this PWS.

Any approval given during preparation of the documentation, or approval for shipment shall not guarantee the final acceptance of the completed documentation.

The contractor shall document unit, integration, system, user acceptance, performance and stress testing milestones, test cases and test results for all software…