Attachment_1_-_PWS_CLD_6APR18_FINAL.pdf

Ver: Jan 2018

Performance Work Statement

Naval Special Warfare Command

Continuum of Leadership Development Software and Support Services

1. BACKGROUND

1.1 Naval Special Warfare Command (NSWC) and its subordinate Echelon Commands require a scalable, Commercial-Off-The-Shelf (COTS) software solution and support services necessary for the implementation and execution of its Continuum of Leadership Development (CLD) program within

Naval Special Warfare (NSW). CLD is a comprehensive feedback appraisal program designed to record, monitor, assess, and facilitate improvement of individual performance and character throughout every phase of a Naval Special Warfare operator’s training and career progression.

1.2 The foundational concept of CLD is to provide Naval Special Warfare (NSW) operators with regular feedback from all levels of their unit (superiors, instructors, and peers). In contrast to the Navy’s evaluation software, which is focused on informing promotion decisions through annual evaluations, CLD will provide 360-degree feedback focused on informing and guiding individual improvement after significant training or operational events. This evaluation allows for trends to emerge over time that might otherwise go unnoticed. Continuous evaluation of the same key traits across all levels of the leadership continuum facilitates ongoing reinforcement of critical character, performance, and leadership traits through an operator’s career. CLD enables leaders to be more engaged and to mentor teammates to identify possible shortfalls or problems with their performance or character and develop mitigating steps to correct before it becomes an issue. It will also enhance identification of an individual’s tactical profile and assist in identifying training trends that indicate aptitude and interest in specific high-demand/low-density qualifications.

2. OBJECTIVES

2.1 The objective is to obtain contractor provided support in the form of a Firm Fixed Price Indefinite

Delivery Indefinite Quantity Contract that provides a CLD enterprise solution in accordance with the requirements of this PWS.

3. SCOPE

3.1 This PWS identifies software requirements and services needed to support the CLD program across the NSW community.

3.2 The contractor-provided COTS Software shall contain existing scalability/customization that shall support all CLD program requirements without the need for any additional software development.

3.3 The contractor shall provide personnel and management necessary to provide CLD software and support services.

4. REQUIREMENTS

4.1 The contractor shall provide a Commercial-Off-The-Shelf (COTS) software solution for the implementation and execution of its Continuum of Leadership Development (CLD) program within

Naval Special Warfare (NSW). The foundational concept of CLD is to provide NSW operators with regular feedback from all levels of their unit (superiors, instructors, and peers). The software application shall be web based and accessible from any computer or mobile device with CLD software installed. The software shall also have the capability of receiving and managing large amounts of performance data and provide outputs in the form of assessment reports used to evaluate key traits across all levels of the leadership continuum. This assessment data will also be used to facilitate ongoing reinforcement of critical character, performance, and leadership traits throughout an operator’s career.

4.2 Phased Implementation

The program will be implemented throughout the NSW enterprise using a phased approach. Upon successfully demonstrating the required functionality within this PWS, and command need, the government will consider subsequent task order awards that will allow for further implementation within additional NSW organizations. Below is a draft conceptual timeline for the purpose of describing the potential growth of the CLD program. It is entirely subject to unilateral government discretion and does not represent any commitment to future task orders.

Fiscal Year Organization

FY18

Basic Training Command

FY19

Training Detachment

FY20

Groups (West Coast)

FY21

Groups (East Coast)

FY22

Sustainment

4.3 Key Personnel

4.3.1 Program Manager. The vendor shall provide a Program Manager to oversee and manage the contracting effort in support of the overall success of NSW. Core duties include:

resource allocation and management, planning and monitoring of program deadlines and milestones, and providing updates of key program elements (cost, schedule, performance). The program manager shall also attend/support quarterly reviews with program stakeholders. NSWC anticipates that the level of effort for this role shall be equivalent to approximately one half FTE, and is not required to support on-site.

Desired skills and qualifications are as follows:

4.3.1.1 8-12 years of managerial experience supporting the Department of Defense

4.3.1.2 Strong writing and verbal communications skills

4.3.1.3 Demonstrated experience managing cost, schedule, and performance

4.3.1.4 Demonstrated experience presenting and managing program risk

4.3.2 Discovery & Implementation Team Lead. The vendor shall provide a Discovery &

Implementation Team Lead to execute a seamless transition and data migration that minimizes disruption to the end user. The D&I Team Lead shall be a subject matter expert and lead the efforts to configure the software to meet the requirements as stated in this SOW. Core duties include: establishing an understanding of NSW culture, training and practices, engaging with program stakeholders and end-users to configure software to meet requirements, assist end-users with any technical issues that require reconfiguration. NSWC anticipates that the level of effort for this role shall be equivalent to one FTE, working on-site at NSWC. Desired skills and qualifications are as follows:

4.3.2.1 Bachelor’s Degree from an accredited college or university in Information

Systems, Data Systems, Computer Science, Engineering, a Mathematics-intensive discipline, or a major field of study which either provides substantial knowledge useful in managing large, complex business systems projects or is closely related to the work as described and required by the Statement of Work

(SOW).

4.3.2.2 Demonstrated experience reviewing, analyzing, evaluating and manage user requirements

4.3.2.3 Demonstrated experience documenting scope and objectives for software customization

4.3.2.4 Strong technical writing and communications skills

4.3.3 Field Service Representative. The vendor shall provide a Field Service Representative

(FSR) to provide technical assistance, training, and support. NSWC anticipates that the level of effort for this role shall be equivalent to one FTE, working on-site at NSWC.

Duties may include:

4.3.3.1 Technical support

4.3.3.2 Software diagnosis and troubleshooting

4.3.3.3 Conducting individual and group training for both end users and administrators

4.3.3.4 FSR shall possess excellent interpersonal skills, and public speaking abilities

4.3.3.5 FSR shall be a Subject Matter Expert on all aspects of the software product

4.4 Services

In addition to the key personal, the contractor retains the performance flexibility to propose to provide additional personnel if it believes they are needed (analysts, technical support, trainers, etc.…) to support this SOW.

4.5 Phase-In

Upon contract award, the vendor will be given access to the data structure for the purpose of gaining further clarification of the requirements.

4.5.1 The contractor shall stand up a discovery team of contractor Subject Matter Experts

(SMEs) led by the discovery team lead to gain a strong understanding of NSW processes in order to scale and customize the COTS software for NSW use.

4.5.2 The contractor shall import and display/archive/categorize all existing pilot program technical data (user profiles, reports, surveys, etc...) into the provided software solution, where possible. NSWC will provide the vendor with the data in the form of a comma-separated values (.csv) file.

4.6 Licensing, Implementation, Maintenance, and Support

4.6.1 The contractor shall provide a COTS software solution and Enterprise License to support the phased implementation of CLD across the NSW enterprise.

4.7 Scalability

4.7.1 The software will have an estimated end-user base of approximately 5,500 personnel accounts.

4.8 Role-based Access

4.8.1 The software shall provide Role-Based Access Control (RBAC) to personnel data, allow for compartmentalization, and must provide role-based access control to the functionality as required.

4.8.1.1 The software shall have an administrative capability that will allow administrators to assign roles to personnel.

4.8.1.2 The software shall allow for access to data and functionality to be based on a combination of elements such as role, command, and training phase.

4.8.2 The software user accounts shall be controlled by a directory service (e.g., Microsoft

Active Directory).

4.9 Data

4.9.1 CLD shall be a tool for importing, and a source for creating and compiling exportable data products, (pdf, PowerPoint, excel, etc...).

4.9.2 The software shall allow for uploading personnel data to, or importing personnel data from, NSW Operational Data Store (NSW OSD) or DoD data source, and other Navy information repositories, when a person joins the NSW community and periodically thereafter.

4.9.3 The software shall only exchange data with authorized data sources, whether directly or indirectly, via authorized mechanisms (NSW Operational Data Store (ODS) or protocols.

4.9.4 The software shall consist of a COTS, relational, hierarchal (non-flat file) database.

4.9.5 Data in the software shall be capable of being tagged with customizable/tailorable metadata tags to enable discovery of data by users.

4.9.6 The software shall allow only authorized personnel to delete personnel from the software.

4.9.6.1 The software shall allow for tagging personnel as “not active” so they can no longer be selected as part of a group or be assessed. The profile and information shall remain fully intact but shall be excluded from being part of a group or being assessed.

4.9.6.2 The software shall allow personnel tagged as not active to be included for data analysis.

4.9.7 The software shall permit only authorized administrative staff (Government and contracted FSRs) to remove categories or attributes from the software.

4.9.7.1 The software shall allow for tagging of categories and attributes as not active so they are unavailable for selecting for group tracking.

4.9.7.2 The software shall allow categories and attributes to be tagged as not active to be included for data analysis.

4.9.8 The software shall have a government-accessible audit log that clearly displays system or user events. The audit log shall document what resources were accessed, to include:

destination and source addresses, a timestamp and user login information (user login information shall allow NSW to identify user with first and last name).

4.10 Data Rights

4.10.1 All technical data and computer software developed and delivered under the contract will be governed by the clauses contained within the terms and conditions and will not be superseded.

4.10.2 In accordance with the included data rights provisions, computer software, technical data and form, fit and function data associated with the enterprise solution shall be made portable, enabling migration to a future enterprise application. This includes the

Government’s ability to move the entire enterprise solution to a new location, supported by the Government or by a different vendor, if deemed necessary. Data in the enterprise solution shall be exported and made available in a fully importable and usable format as required by the USG, and all data in the software shall also be provided as an archive artifact milestone at the end of the contract. At contract end and prior to contract end at time of enterprise solution migration, the vendor shall provide data exports in a comma separated values (.csv) format that allows the Government to move, copy or transfer data easily from the pilot application to a future enterprise application.

4.11 User Interface Capability

4.11.1 Navigation, help and search tools/functions should be clearly visible/accessible.

4.11.2 The software shall provide a Graphical User Interface (GUI) for all CLD software capabilities and end user devices. The GUI shall be designed using the user-centered-design (UCD) methodology and provide efficient access to data while minimizing the number of layers, menus, and “clicks,” required to get there.

4.11.3 Software shall provide easy access to an online user’s guide.

4.12 Status

4.12.1 Status in this context is identifying the current state of an individual in the CLD software.

4.12.2 The software shall allow for each person to have a current status associated with the grouping in which they have been selected to participate. (As CLD grows to enterprise-wide, personnel not selected for a grouping will have a generic “at large” or “available” default status.)

4.12.3 Status types and hierarchies in the CLD software shall be defined by NSW leadership, and the software shall allow for the addition, modification, or deletion of status categories by both NSW and contractor personnel.

4.13 Character Attribute Tracking

4.13.1 The three main areas being tracked in the CLD program are character, physical and technical. Each of these areas tracks different aspects of an individual’s character traits, physical condition, and technical ability.

4.13.2 The least tangible of the three attributes being tracked by the CLD program is character.

Character attributes are the most difficult to measure because they are subjective. The

CLD programs endeavors to minimize this subjectivity by clearly defining each character attribute and its associated metrics.

4.13.2.1 The software shall be capable of displaying provided definitions of character attributes and examples of associated behaviors and metrics.

4.13.2.2 The software shall be capable of displaying additional information associated with those attributes.

4.13.2.3 The software shall allow for selecting from a pre-determined list data elements to apply the traits deemed necessary for a selected activity or career assessment.

4.14 Character Metrics

4.14.1 The software shall allow (but not require) character elements to be tracked during any career phase. When it is tracked, the software must allow for the category to be weighted at the appropriate level in relation to importance of technical and physical attributes.

4.14.2 The software shall allow for adding and removing character data elements.

4.14.3 The software shall allow for measuring character element results against provided NSW standards.

4.14.4 The software shall allow for archiving data on character activities data elements and/or standards that are no longer used.

4.15 Physical Metrics

As part of the three main areas of tracking and assessing (character, physical, technical), the physical attribute is typically a category that is tangible and can be easily measured.

4.15.1 The software shall allow (but not require) physical data elements to be tracked during any career phase. When it is tracked, the software must allow for the physical category to be weighted at the appropriate level in relation to importance of technical and character attributes.

4.15.2 The software shall allow for adding and removing physical data elements.

4.15.3 The software shall allow for capturing timing and other metrics on physical activities data elements.

4.15.4 The software shall allow for measuring physical activity results against provided NSW standards.

4.15.5 The software shall allow for archiving data on physical activities data elements and/or standards that are no longer used.

4.16 Technical Activities

4.16.1 Like physical ability, technical ability is tangible and can also be tracked easily (i.e.

score on a test, completed the task or not). The list of technical ability data elements can vary, so the software shall allow these elements to be altered over time. The software shall allow for entering the standard against which a technical ability is measured. For example, on a written test a score of 90 may be required to pass. Technical data elements and/or standards that are no longer active shall not be deleted from the software if they are no longer available for selecting, they shall be archived for trending and analysis, or for other requirements.

4.16.2 The software shall allow for archiving technical activities and associated data that are no longer used.

4.16.3 The software shall allow for adding, removing, or modifying, technical activities included in-training evolutions.

4.16.4 The software shall allow for measuring technical skill results against NSW standards.

4.17 Reporting

4.17.1 The CLD software shall provide output in various formats, such as surveys, questionnaires, lists of comments, reports, metrics, and analytic results.

4.17.2 Surveys/Questionnaires/Reports

4.17.2.1 The software shall allow for input and/or creation of new surveys and questionnaires.

4.17.2.2 The software shall allow selecting surveys and/or questionnaires from a library for groupings in a report.

4.18 Peer Rating/Ranking

4.18.1 The software shall allow for selecting from a pre-determined data elements checklist for rating an individual(s).

4.18.2 The software shall allow for individuals to rate/rank peers in their groups in plain text comments.

4.18.3 The software shall allow selecting rating/ranking reports from a library of reports.

4.19 Student-Instructor/Staff Rating/Ranking

4.19.1 The software shall allow for selecting from a pre-determined behavior checklist (drop down menus) for rating an individual, but also allow for free text descriptions. The software shall also provide readily-available instructions for each section as well as a

Help menu to assist with more in-depth questions.

4.19.2 The software shall allow for instructors/staff to rate/rank students in their groups.

4.19.3 The software shall allow for multi-level or multi-tier rating/raking of student-instructor/staff.

4.20 Mentoring

4.20.1 CLD methodology incorporates the concept of mentoring to promote self-awareness in personnel, and provide guidance for improvement based on the observations and perceptions of peers, instructors, and the chain of command.

4.20.2 The software shall allow for entering NSW generated mentoring talking points for various mentoring topics to serve as a guide, thereby improving the consistency of personal mentoring.

4.20.3 The software shall allow for a mentor to select and associate mentoring talking points to a mentored person.

4.20.4 The software shall allow the mentor to be listed in the mentored person’s record to identify mentoring relationship.

4.20.5 The software shall allow the mentor to add mentoring related comments in the software to clarify a previous comment or note (positive or negative) progress.

4.21 Analytics

4.21.1 The software shall provide analytical tools that simplify the process of assessing the effectiveness of each major element of the CLD program.

4.21.2 The software shall have a selection of standard data trend charts and/or tools to facilitate trend analysis.

4.21.3 The software shall provide the ability to analyze subjective data.

4.22 Comments

4.22.1 Comments are an important element in the CLD software. Comments are the main method for recording observations regarding character attributes, and are helpful in understanding the results of physical and technical abilities. The CLD software will provide for comments to be recorded for all activities, and during each phase of career development.

4.22.2 The software shall allow for comments to be added or modified in plain text and be associated with individual personnel.

4.22.3 The software shall allow for comments to be added or modified about a specific activity.

4.22.4 The software shall allow for comments to be added or modified for an individual’s specific character attributes.

4.22.5 The software shall allow comments to be tagged as positive, negative, neutral, or other acceptable tagging descriptors.

4.22.6 The software shall allow for comments to be added for a whole grouping of personnel.

4.23 Mobility

4.23.1 The technology challenges that could be encountered involve the disconnected or wireless capability needed to sync mobile devices to the enterprise system. While the technology is standard and stable, the absence of wireless or cellular hot-spot connectivity presents challenges that can be overcome by using stand-alone systems that will synchronize with the enterprise system when those services become available.

Devices will be GFE but versatility across a variety of mobile devices is required to respond to changing technologies. (And IAW with 4.21)

4.23.2 Contractor shall provide a mobile application for GFE mobile device that allows for encrypted data at rest and Common Access Card (CAC) accessibility.

4.23.3 The software shall provide the ability for sync and exchange data pertinent to an evolution, class, or mission from mobile devices such as laptops, notebook computers, and tablet computers, with the CLD software.

4.23.4 The mobile application shall allow capturing individual behavior observations as written comments, as automatic speech-to-text comments, and as event check-box entries, as appropriate.

4.23.5 Comments recorded on the mobile device (as text) shall be available for editing on the unit, or when uploaded to the CLD system workstation.

4.23.6 The mobile application will be required to be made available to and be installed on a government wireless device exclusive and independent of a commercial application store (e.g., will not have access to Google Play, Microsoft Store, Apple iTunes to download to GFE). The mobile application shall receive relevant and timely updates as required.

4.24 Class/Group Training Administration

4.24.1 Class/group training administration includes a variety of administrative utilities that support the tracking and assessment of NSW personnel.

4.25 Student Management

4.25.1 The software shall allow for the creation of student roster and student data.

4.25.2 The software shall allow for selection of students from a pre-populated list of NSW personnel. New personnel can be added manually if needed.

4.25.3 The software shall allow a training class to be created, assigned a name, and populated with personnel associated with the class and in what role (e.g. student, instructor, etc…).

4.25.4 The software shall provide instructors with student data relevant to the evolution being conducted.

4.25.5 The software shall provide instructors with student roster, and the ability to assign students to sub-groups (boat crew, etc.).

4.25.6 The software shall allow for updating student information with individual status including: unavailability due to medical condition, dropped status, rolled (including information on new assignment), reassigned to other/new sub-group, assignments/tasks/classes missed, etc.

4.26 Class/Group Training Performance Boards

4.26.1 The CLD software will be used to display student assessment information and summary-type “baseball card” reports. In some cases, a student may be allowed to submit a written statement to explain why an adverse assessment should be reversed. The software must provide the capability to upload, or input on-line, student statements. The software must allow for digitally signing outcome statements by the student and leadership with CAC authentication.

4.26.2 The software shall provide an individual performance summary capability, as needed, to review a student’s progress within the training pipeline.

4.26.3 The software shall also have the ability for students and instructors/board members and leadership (i.e. CO/XO) to digitally sign the form with CAC authentication.

4.27 Class/Group Assessment Management

4.27.1 The software shall allow for selecting which categories and attributes (physical, technical, character) will be tracked for a grouping and allow for them to be weighted as they relate to the evolution or mission needs.

4.27.2 The software shall be flexible enough to allow selection of the type of information about categories and attributes (i.e. free text (comments), numerical (metrics), dropdown

(select from multiple answers) required for each evolution or task being performed, or for the data analysis needed. (Note: Types are determined at time categories/attributes are created not on the fly for each grouping.)

4.27.3 The software shall allow for creating physical and technical categories (4M run, tests) and character attributes (i.e. Dependability, Attitude, Motivation, Team before self, and

Military Bearing) that are specific to an evolution or mission by authorized personnel.

4.27.4 The software shall allow for deleting, modifying, or archiving categories and character attributes that are specific to an evolution or mission by authorized personnel.

4.27.5 The software shall allow for the option to enter instructor certifications and/or qualifications required for instructors to conduct training for the specific evolution or mission (e.g. instructor training record, team operator card), with a verification and validation process

4.27.6 The software shall allow for certifications and qualifications to be selected from a populated list of common certifications and qualifications.

4.27.7 The software shall allow for selecting or adding new certifications and qualifications, and certifications and qualifications that are unique to NSW.

4.28 Group Instructor/Management Support

4.28.1 The software shall provide an Instructor Management (Instructor Development) capability that will allow entering certification and/or qualification dates for NSW personnel selected as a high-risk instructor for a group. Certification data may be downloaded from an authoritative source or uploaded.

4.29 Miscellaneous Tracking

4.29.1 The software shall allow for adding a description, and a quantitative limit, for an item being tracked, to be able to show when the limit has been hit.

4.29.2 The software shall associate an item being tracked to the individual responsible for it.

4.30 Email Notification

4.30.1 The software shall provide an email notification capability that will allow for sending out email notifications to specific individuals for specific triggers (e.g., instructor qualification dates)

4.31 Security and Privacy Requirements

4.31.1 Under this contract, the contractor will have access to Personally Identifiable

Information (PII) which is any information that can be used to distinguish or trace an individual’s identity. Examples include but are not limited to: name, social security number (SSN), date of birth, home address, home phone number, personal e-mail address, financial information, fingerprints, and photograph.

4.31.2 As the software will contain PII information, the contractor must comply with requirements as set forth in the Privacy Act of 1974 (5 U.S. Code 552a), OMB

Memorandum 07-16 Appendix J, NIST 800-53 Rev. 4, COMNAVSPECWARCOMINST 5211.1B as appropriate. The contractor must ensure that the PII is secure and protected. PII must only be accessible to those with an “official need to know”; b. the contractor must minimize the use, display or storage of SSNs and all other PII and DoD ID number or other unique identifier should be used in place of the SSN whenever possible; c. the contractor must review PII practices to ensure that all information is timely, accurate and relevant to the purpose for which it was collected; d.

the contractor should delete personal information when no longer required in accordance with appropriate DoD Records Management instructions regarding retention and disposition requirements; And, e. the contractor and contractor personnel must comply with all incident notification requirements in the event that contractor personnel suspect or discover that PII has been lost or compromised.

4.31.3 The software will require encryption of PII data in transit and at rest.

4.31.4 The software shall display a Privacy Act Statement banner on every instance of the software.

4.31.5 Accreditation and Software Security

4.31.5.1 Prior to production, the software shall be granted an Interim Authorization to

Test (IATT) decision and subsequently an Authorization to Operate (ATO) in accordance with Department of Defense Instruction 8510.01 Risk Management

Framework (RMF). The contractor shall provide all requested documentation in support of the accreditation process and shall ensure that the software meets both the IATT and ATO accreditation requirements (0006).

4.31.5.2 The contractor must comply with the controls in PWS Exhibit 1 to receive an

IATT or ATO. The controls may be tailored at the discretion of the government. Additionally, both during and after the accreditation process additional controls may be identified by the government and met by the contractor.

4.31.6 Authentication and Authorization

4.31.6.1 User accounts to the CLD software shall be controlled by enterprise level relational database server (e.g. Microsoft SQL, Oracle) or directory service

(e.g. Microsoft Active Directory).

4.31.6.2 The software shall be HSPD-12 compliant. The software shall utilize a DoD

Common Access Card (CAC) for authentication for access to CLD software

(mobile device, workstation, laptop, data systems, etc.).

4.31.6.3 The software shall connect to a Credential Server to validate that CACs used for accessing the CLD software are valid.

4.31.6.4 All data visible and/or collected via this web site including, but not limited to

Personally Identifiable Information (PII) and other information, shall belong to the Government and not be used by the Contractor for any other purpose without written prior approval from the Contracting Officer. Additionally, the contractor shall not use any government furnished information or any data developed and/or incorporating government furnished information without written prior approval of the Contracting Officer.

4.32 Software Security Requirements

4.32.1 Software Hosting

4.32.1.1 The software shall be hosted on the Unclassified SOF Information

Environment (SIE).

4.32.1.2 Database servers and application web-server software shall be hosted on separate servers.

4.32.1.3 Web Server(s) shall be hosted behind a security firewall with only port 443 secure access to services unless specifically identified and approved.

4.32.1.4 Database Server shall be hosted behind a secondary firewall to protect privacy and sensitive data from direct access.

4.32.1.5 Data held in the CLD software database shall be encrypted and hashed to the greatest extent possible to protect from human readable access to those data.

4.32.1.6 The software shall use enterprise level relational database server software.

4.32.2 Computer Communications

4.32.2.1 The web-based software shall use SSL (https) for all communications.

4.32.2.2 The web-based software shall be hosted in an authorized data DoD data center.

4.32.2.3 The software shall use a secure SOF unclassified network to communicate between the CLD servers and the mobile devices. If no secure SOF wireless network is available, mobile devices shall be synchronized using a hardwired

Local Area Network (LAN) connection.

4.32.3 Personnel-related Requirements

4.32.3.1 All system-administrator personnel who require system level access shall have a DoD 8140.01, Cyber Security Workforce, appropriate level certification prior to being granted access.

4.32.4 Software

4.32.4.1 All software shall have vendor support available for security updates, system user manuals, system specifications, and system upgrades for the duration of the master IDIQ contract, or until all aspects of CLD operation, medication and maintenance are transferred to Navy personnel. All security findings must be remediated or mitigated within 21 days of discovery. All software will be configured in accordance with Defense Information Systems Agency Security

Technical Implementation Guides, Security Requirements Guides, Security

Content Automation Protocol benchmarks, and Industry Best Practices. Vendor will provide responses to NIST SP 800-53 Rev 4 requirements and Committee of National Security Systems Instruction 1253.

4.32.4.2 The contractor shall provide a Software Implementation Plan that details the software solution, timeline, and support services required, as outlined within this PWS, no later than 45 days, post award.

4.33 Phase-Out

4.34 The contractor will provide the government all technical data at contract end in comma separated values form.

4.35 Post-Award Conference

4.35.1 The contractor shall participate in a Post-Award Conference. This meeting shall provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting shall provide the opportunity to discuss technical, management and security issues. The Post Award Conference will aid both the Government and Contractor in achieving a clear and mutual understanding of all requirements, and identify and resolve any potential issues. The Contractor shall be prepared to discuss any items requiring clarification and gather information as necessary to support each deliverable. The Contractor shall provide a written summary of the

Post-Award Conference.

5. DELIVERABLES

Description Number PWS

Ref.

Delivery Date

Fully Updated and

Complete Enterprise

License

0001 4.2.1 As requested and contract end

Monthly Status Report 0002 4.2.5 5 days after month end

Training Material 0003 4.2.5 No later than 30 days after every software build/update/version

Documentation for

Accreditation/Issuance of

Favorable Authority to

Operate Decision

0004 4.25.5 As requested. Contractor shall provide documentation in support of the accreditation process.

Software Implementation

Plan

0005 4.26.4.2 45 days after contract award

Post Award Conference

Minutes

0006 4.29 5 business day post award conference

Contractor Manpower

Reporting

0007 6 Annually by 31 October or at completion.

6. CONTRACTOR MANPOWER REPORTING

6.1 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Naval Special Warfare Command via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs

October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil.

7. CONTRACTOR TRAVEL

7.1 Contractor travel is authorized (CONUS and OCONUS), subject to government approval, to support software updates, provide live training, stakeholder discussions and the phased implementation of software.

7.2 All travel shall be in accordance with FAR 31.205-46 and applicable travel regulations (Joint, Federal or Standardized). Contractor payment claims shall include applicable documentation to support actual costs incurred (e.g. airfare and hotel/lodging receipts) as well as any receipts valued at or above

$75.00. Failure to provide appropriate documentation may result in loss of reimbursement of travel expenses.

8. SECURITY

http://www.ecmra.mil/ http://www.ecmra.mil/

8.1 Security shall be in accordance with the attached DD254. Contractor team individual(s) supporting this requirement shall be cleared at the Secret level at the start of the requirement.

8.2 The contractor shall insure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor's management system shall prevent unauthorized disclosure of classified and Controlled Unclassified Information (CUI). The government shall be immediately notified if any security incident or any indication of a potential unauthorized disclosure or compromise of classified information or CUI.

8.3 The contractor shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

8.4 Contractor shall establish appropriate administrative, technical, and physical safeguards to protect any and all nonpublic Government data to ensure the confidentiality, integrity, and availability of

Government data.

8.5 The Contractor and all Contractor personnel with access to or responsibility for nonpublic Government data under this contract shall comply with Department of Defense Instruction 8510.01, Risk

Management Framework (RMF); DoD Instruction 8500.1 Cybersecurity; DoD Instruction 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling; DoD Directive 5400.11-R, DoD

Privacy Program; DoD 6025.18-R, DoD Health Information Privacy Regulation; DoD 5200.2-R, Personnel Security Program; and Homeland Security Presidential Directive (HSPD) 12.

8.6 Contractor personnel with access to or responsibility for nonpublic Government data under this contract shall comply with HSPD-12 Personal Identity Verification (PIV) assurance requirements, known as the Common Access Card (CAC) for DMDC and must:

8.6.1 Be CAC ready prior to reporting for work. At a minimum all Contractor personnel must obtain/maintain a favorable FBI National Criminal History Check (fingerprint check), two forms of identity proofed identification (I-9 document), and submit a National

Agency Check and Law Credit (NACLAC) vetting package for processing. Obtaining

CAC ready status is the responsibility of the contracting agency. It is the responsibility of the contracting agency to notify NSW when this is complete.

8.6.2 Be citizens of the United States.

8.6.3 Maintain favorable FBI National Criminal History checks and ensure completion and successful adjudication of a NACLAC as required for Federal employment.

8.6.4 If at any time, any Contractor person requiring a CAC is unable to obtain/maintain an adjudicated NACLAC, the Contractor shall immediately notify the NSW Information

Systems Security Group (DISSG) remove such person from work under this contract.

8.6.5 The Contractor shall report immediately to the NSW CIO / Privacy Office and secondly to the COR discovery of any Privacy breach.

9. SAFETY

9.1 Contractor Responsibility

9.1.1 Nothing in the Performance Work Statement nor any Government action or failure to act in performance of the contract shall relieve the contractor of its responsibility for the safety of the contractor's personnel and property, the Government's personnel and property, and the general public. Furthermore, nothing in this PWS shall relieve the contractor of its responsibility for complying with applicable Federal, State, and Local laws, ordinances, codes and regulations (including those requiring applicable licenses and permits) in connection with the performance of this contract.

10. GOVERNMENT FURNISHED PROPERTY/EQUIPMENT/INFORMATION (GFP/GFE/GFI)

10.1 Office working spaces located in Coronado, California including standard office furniture (desk, chair, desk phone, printer/scanner access).

11. QUALITY CONTROL

11.1 The contractor shall implement and maintain a Quality Control Plan (QCP) to ensure work performed conforms to the scope of work and meets the requirements under this PWS. The QCP shall, at a minimum provide a method for performing inspections; identifying, correcting and preventing problems/defective service; addressing customer complaints, and improving the quality of services over the life of the contract.

12. QUALITY ASSURANCE

12.1 The Government reserves the right to perform inspections and surveillance to evaluate the

Contractor’s compliance to the contract terms and performance of the requirements in the PWS. The

Government will assign a Contracting Officer’s Representative (COR) who will be responsible for monitoring performance in accordance with the requirements of the PWS and the Quality Assurance

Surveillance Plan (QASP). The COR will make every effort to ensure that the surveillance methods used are conducted in an objective, fair, and consistent manner.

12.2 Contract Discrepancy Report (CDR). In the event of unsatisfactory contractor performance, the CO will issue a CDR that will explain the circumstances and findings concerning the incomplete or unsatisfactory service. The contractor shall acknowledge receipt of the CDR and respond in writing as to how he/she shall correct the unacceptable performance and avoid a recurrence. The

Government will review the contractor's corrective action response to determine acceptability and will use any completed CDR as part of an overall evaluation of Contractor performance when determining present or future contractual actions.

13. APPLICABLE DOCUMENTS

Document Web link (if applicable)

DoDD 8140.01, Cyberspace Workforce

Management http://www.dtic.mil/whs/directives/corres/pd f/814001_2015_dodd.pdf

DoDI 8500.01, Cybersecurity http://www.dtic.mil/whs/directives/corres/pd f/850002p.pdf

DoDI 8510.01, Risk Management Framework

(RMF) for DOD Information Technology http://www.dtic.mil/whs/directives/corres/pd f/851001_2014.pdf

DoDI 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling http://www.dtic.mil/whs/directives/corres/pd f/852002p.pdf

DoD 8570.01-M, Information Assurance

Workforce Improvement Program http://www.dtic.mil/whs/directives/corres/pd f/857001m.pdf

DODI 1322.26, Development, Management, and

Delivery of Distributed Learning http://www.dtic.mil/whs/directives/corres/pd f/132226p.pdf

Department of the Navy Policy on Digital

Product/Technical Data, Assistant Secretary of the

Navy for Research, Development and Acquisition, ASN (RDA) memo of 23 October 2004 http://www.navsea.navy.mil/Portals/103/Doc uments/NSWC_Carderock/Policy.Guidance.

041023.pdf

Software Process Improvement Initiative Contract

Language, ASN (RDA) memo of 13 July 2007 http://www.secnav.navy.mil/rda/Policy/2007

%20Policy%20Memoranda/13jul07spiicontr actlanguage.pdf

NIST 800-88 Guidelines for Media Sanitization http://spin1-www.nist.gov/customcf/get_pdf.cfm?pub_id

=50819

14. PLACE OF PERFORMANCE

14.1 Place of performance is the Naval Amphibious Base, Coronado, CA

15. PERIOD OF PERFORMANCE

15.1 Period of performance to be determined.