HC104717R0015.pdf

SEE ADDENDUM

(No Collect Calls)

HC104717R0015 27-Apr-2017

b. TELEPHONE NUMBER

301-225-4084

8. OFFER DUE DATE/LOCAL TIME

01:00 PM 22 May 2017

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10479. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

MICHELLE L. RAND

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DEFENSE INFORMATION SYSTEMS AGENCY

6910 COOPER AVENUE

FT. MEADE MD 20755

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$27,500,000

NAICS:

541511

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF97

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HC104717R0015

Section SF 1449 - CONTINUATION SHEET

PWS

PERFORMANCE WORK STATEMENT (PWS) as of 04/25/2017

Contract Number: Will be completed at time of award

Tracking Number: DTMSIDP

Follow-on to Previous Contract Number: HC1047-16-P-4010

1. Contracting Officer’s Representative (COR).

a. Primary COR.

Name: Will be completed at time of award

Organization: Will be completed at time of award

Department of Defense Activity

Address Code (DODAAC):

Will be completed at time of award

Address: Will be completed at time of award

Phone Number: Will be completed at time of award

Fax Number:

E-Mail Address: Will be completed at time of award

b. Alternate COR.

Name: Will be completed at time of award

Organization: Will be completed at time of award

DODAAC: Will be completed at time of award

Address: Will be completed at time of award

Phone Number: Will be completed at time of award

Fax Number: Will be completed at time of award

E-Mail Address: Will be completed at time of award

2. Contract Title. DISA Talent Management System (DTMS) Readiness Assessment and Individual Development

Plan (IDP) System and Workforce Development Competency Consulting Support Services.

3. Background. DISA personnel currently use the DTMS to conduct mission essential readiness assessments and

Individual Development Plans (IDPs) which support and improve the analysis, training, and professional development of the DISA workforce. This requirement is to provide a solution that meets the DISA requirements for the DTMS readiness assessment and individual development plan program for systematically assessing competencies. This capability includes several DISA-specific reports, for the purpose-built to efficiently support competency management, planning, implementation, training, reporting, and analysis by employees, supervisors, and managers. All DISA employees are required to use the IDP tool to assess their current skill set and identify gaps where additional training/experience is required. DISA Services Development’s Business Systems PMO

(SD2) and Workforce Development (MP5) are the main DISA stakeholders as SD2 is responsible for business systems development, and MP5 is responsible for developing the workforce and reporting on competency levels.

The current system has a webserver running on Cold Fusion that interacts with a Structured Query Language (SQL) database and provides a user interface. The SQL database interfaces with DISA’s Corporate Management

Information System (CMIS) and incorporates manpower reports (exported as csv). The system operates on two servers at present; one webserver, one database server, however will be transitioned to a Virtual Operating

Environment (VOE) at a DISA Data Center by the end of 3rd Quarter Fiscal Year 2017.

4. Objectives: The objective is to obtain a commercial, non-developmental solution that meets the requirements as identified in this PWS, for a competency assessment and readiness system. The system functionalities must track and report employee assessments, employee readiness, IDPs, supervisor review, approve or return-for-changes dates, completions of planned training, and completions of IDP developmental activities. In order to accomplish this, the contractor shall coordinate, resource, and execute the below functions:

Refining system requirements based on user requirements and implementing DTMS software and functionality.

Testing and validating DTMS software and functionality.

Sustaining and maintaining software and functionality and security posture.

Continued Competency Model analysis, updates, and Competency SME services.

5. Scope.

The contractor shall provide, implement, secure, and sustain a DISA Talent Management System (DTMS) to provide a Competency Readiness Assessment tool for DISA employees agency wide and fully document all work and system configuration completed under the contract pursuant to the guidelines entailed herein.

The government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed 20% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8.

6. Performance Requirements.

The contractor shall provide support for all application implementation, support, and onsite activities—including, but not limited to, training and competency workshops. The application shall be hosted in a Defense Enterprise

Computing Center (DECC) and shall include both a production and test environment. The contractor shall be responsible for configuring the application in compliance with the appropriate Security Technical Implementation

Guide(s) (STIGs). The contractor will not have privileged access to the operating system(s) of hosted servers. All configuration and application changes shall be tested in the test environment before being deployed in the production environment. The application shall be configured to interface, store, and display PII information in compliance with Federal and DoD Laws, Regulations, and Policies. All contractor DTMS work shall be completed pursuant to a contractor provided schedule following the tenets of the Project Management Body of Knowledge.

The contractor shall provide all necessary licenses and keys to the Government. The Government shall receive unlimited Government purpose rights to use the application as configured and delivered as stated in the software licenses. The license costs shall be separate line items on the contract.

6.1 Task 1 Program Management

The contractor shall provide oversight of all contracted efforts. The contractor shall communicate with the COR on all issues related to project outcomes. The contractor shall attend the kick-off meeting in person to discuss the project approach, schedule, milestones, and points of contact.

6.1.1 Subtask 1 – Kick-Off Meeting (KOM)

The contractor shall attend a KOM with all partners to establish a baseline of understanding after the contract award or as directed by the Contracting Officer (KO) at a location to be determined by the Contracting Officer

Representative (COR) within ten (10) business days of contract award. Participants will include SD2 and MP5

Staff, KO, COR and any key contractor personnel and Government staff. At the KOM, the contractor shall present the details of its intended approach and approximated project schedule for review and approval by the COR. The

KOM will serve to resolve strategic questions, refine goals, define success, and explore the biggest challenges and breakthrough opportunities for the Government. This will be the beginning of a dialogue between the Government and the Contractor to ensure successful execution of this contract by the contractor. The Contractor shall coordinate the agenda for the KOM and include, as a minimum, the following:

Introduction of management and technical teams

Presentation of management plans and reports, technical issues, resolutions, and mitigation strategies

Establishment of common understanding of the contract

Other relevant items may be introduced at the discretion of the Contractor and/or the Government

Deliverables: KOM Agenda

Briefing Materials

Action Item Lists

KOM Minutes

6.1.2 Subtask 2- Project Schedule

All contractor DTMS work shall be completed pursuant to a contractor provided schedule following the tenets of the

Project Management Body of Knowledge. The project schedule shall include key milestones and activity information for the program and tasks identified in this PWS. The schedule shall be maintained and updated once a month, at a minimum.

Deliverables: Project Schedule

6.1.3 Subtask 3- Monthly Status Report (MSR)

The Contractor shall submit an MSR that includes by-task financial, performance, and schedule status including proposed changes to the schedule as detailed in the management plan, property accountability, technical accomplishments, issues and risks, and planned activities for the next reporting period. Any issues requiring

Government response or action shall be identified to the Government immediately and status captured in monthly reports.

Deliverables: Monthly Status Report

6.1.4 Subtask 4- Contract Transition

Prior to contract expiration, or in the event of a contractual change or turnover, the contractor shall provide at a minimum all materials and support necessary to accomplish a seamless and expeditious transition of the tasks identified in this PWS to the incoming contractor. The shall include electronic copies of the following: all in-progress working files; historical files for all tasks; Concept of Operation (CONOPS) procedures, and final phase out meeting with Government, incumbent and the new contractor. The contractor shall support a formal contract close-out process, including the documenting of lessons learned throughout the life of the contract. All deliverables shall be provided 60 calendar days before the end of the contract.

Deliverables: Transition Plan

In-progress working files

Historical files

Concept of Operation (CONOPS) procedures

Lessons Learned

6.2 Task 2 System Implementation and Configuration

The contractor shall provide and implement a commercial, non-developmental solution that tracks and reports readiness assessments/IDP submission dates, supervisor review, approve or return-for-changes dates, completions of planned mandatory training, and completions of developmental activities. The contractor shall fully document in writing all work completed to implement and configure the system, to include the systems architecture, configuration settings, and software versions and shall provide the Government with the aforementioned documentation according to the parameters set in the deliverable timetable below.

The contractor-provided commercial, non-developmental solution shall provide the following:

6.2.1 DISA Organizational Hierarchy. The contractor shall ensure the system mirrors DISA’s existing and future organizational hierarchy. At present, DISA’s Organizational Hierarchy is represented by page 3 of the Technical Data Package and Joint Table of Distribution (JTD) including supervisor and employee information. The system shall import data from the JTD. This import and update of DISA organizational information shall be done on a nightly basis. All requisite reports shall reflect DISA’s existing and future organizational hierarchy and JTD and be filterable by component down to the Branch/Individual employee level. The system shall have the functionality for the assessments to have multiple proficiency levels (using Industry Standards and approved by

DISA) for the employee to select their skill level. Each competency/skill shall have a definition of the competency. This definition will be defined and approved by the COR. This information exchange will contain PII and shall be secured accordingly.

6.2.2 Reports. The following filtered, accurate ad hoc reports shall be available, accessible, and included, in real time, to the various organizational levels at DISA including percentage and total numbers: Assessments and IDPs submitted to the Supervisor, Assessments in progress but not submitted, Assessments and IDPs Approved by the Supervisor, Assessments and IDPs Denied by the Supervisor, Adjustable Readiness Measurement reports , Top 5 Competencies, Top 5 Below

Competencies standards, and skill gaps (job series shortages and overages which include where we have excess skills and where we are lacking). The system shall have an Employee Self-

Assessment Report which will include the following fields: competency/skill; target proficiency level; employee selected proficiency level and skill gap (difference between target and employee selected proficiency level). Reports shall be able to be viewed on screen, or downloaded in different print ready PDF and Microsoft Excel formats.

6.2.3 Formulas. The contractor shall ensure all calculations, formulas and/or algorithms align with key terms, metrics, reports and related DTMS system outputs.

6.2.4 Visual Display of Reports. The contractor shall provide graphs, charts and tables to align with terms, calculations, formulas and algorithms throughout the DTMS system. Each report shall be evaluated for distribution restrictions and properly marked (e.g. FOUO and / or PII).

6.2.5 Data Integrity. The contractor shall ensure and verify that all graphs, charts, and tables match the terms, calculations, formulas and algorithms throughout the DTMS system.

6.2.6 IDP Functions: The system shall prepopulate all the employee's competency skill gaps from their self-assessment into the IDP Short-term Goals field. The system shall integrate with the DISA eLearning System and DISA Online Training System (DOTS) to allow employee to select a course which fulfills IDP identified development activity or competency shortfalls and populate the corresponding elements in DTMS. DOTS is a listing of scheduled training events, which can include DISA hosted, DISA funded, Directorate Funded and Program Based training. DOTS also provides a method for DISA employees to submit requests and receive approval to attend the various training events.

6.2.7 IDP Functions. The IDP functions shall be configured as follows and as changes are made further configuration changes may be necessary to ensure the desired functionality is achieved: The IDP function shall have three (3) fields available (short-term goals/long-term goals/objectives). A link to lookup courses in DOTS or eLearning shall be available. If a course is selected, the fields shall be filled-in automatically. The fields shall also have the functionality to be manually entered. The email when submitted by the employee to the supervisor shall be programmed with prepopulated with customized DISA verbiage, to be provided post contract award by the COR. The employee’s supervisor shall have the ability to approve or disapprove the IDP. If the supervisor selects disapprove, the system shall allow the supervisor to add comments that will be sent to the employee. The disapproval and comments shall be automatically emailed to the employee by the system, with the reasons identified by the supervisor. Once actions are taken by employee for updating the IDP, the system shall allow the supervisor to go through approval process again. The system shall allow employees to edit a previously approved developmental activity to show completion of activity (does not need supervisor approval). All other IDP changes (including updates to short-term goals, long-term goals, developmental objectives, and additions/deletions to developmental activities) shall require approval from the employee's supervisor. The system shall allow for the use of a previously approved IDP as a template to create a new IDP, which shall follow the approval process stated above. The IDP shall be approved as a whole, not at the individual development activity level.

6.2.8 Assessments. The contractor-provided system shall allow employees to take self-assessments based on the Competency Model defined by DISA, based partially on the OPM Competency

Dictionary: Multipurpose Occupational Systems Analysis Inventory Competencies (MOSAIC) and National Institute of Cybersecurity Education (NICE) cybersecurity specific competencies.

The competency model associates the employee’s series, grade, and focus with a collection of questions on a 1-5 rating scale. The employee self-assessment shall have the functionality to be routed/viewed by the employee's supervisor for a decision to approve or deny/reject. If the supervisor denies/rejects the self-assessment, the system shall have the functionality to notify the employee of the denial/rejection. The supervisor shall have an area to give feedback or justifications for why assessment is denied. Once employee action is taken on updating assessment, the supervisor must review and again approve or deny/reject the assessment. The assessment will be completed once it has the supervisor’s approval. The system shall have the functionality for the assessments to have multiple proficiency levels (using Industry Standards and approved by DISA) for the employee to select their skill level. Each competency/skill shall have a definition of the competency. This definition will be defined and approved by the COR.

6.2.9 Assessment/IDP Tracking/Reporting. To ensure IDPs and assessments can be tracked during all sections of the process, the system shall include the following system statuses/terms: Not Started

{Definition: Employee has not started the assessment/IDP}; In Progress {Definition: Employee has started the assessment but has not Submitted the assessment to the supervisor}; Submitted

{Definition: Employee has submitted the assessment/IDP to the supervisor for approval}; Denied

{Definition: The supervisor has denied the assessment/IDP and has sent back to the employee for changes. Once the employee starts the changes, the stamp will change back to In Progress; and

Approved {Definition: The supervisor has approved the assessment/IDP, no more changes are required.}.

6.2.10 Assessment Proficiency Scale Definitions. The assessment proficiency scale definitions shall use industry standards and reflect the following: N/A- Not applicable; No Experience or Knowledge;

Novice – Basic skill level, knowledge and experience, requires close supervision; Intermediate –

Intermediate skill level, knowledge and experience, requires minimal supervision; Advanced -

Advanced skill level, knowledge, and broad experience, requires little or no supervision; and

Expert – Expert skill level and knowledge, extensive experience, requires no supervision.

6.2.11 Assessment Proficiency Scale Numbers. The assessment proficiency scale definitions shall use industry standards and be used to calculate skill gaps. Example: No Experience or Knowledge =

0; Novice = 1; Intermediate = 2; Advanced = 3; and Expert = 4.

6.2.12 Skill Gap Calculations. The system shall have the functionality to calculate an employee's skill gaps by using the DISA defined Competency Model. For reporting and calculations, a Skill Gap of 0 Meets Standard; Skill Gap of a positive number indicates a skill gap; Skill Gap of a negative number is above standard.

6.2.13 Employee Readiness Calculations. The system shall have the functionality to calculate the readiness of an employee based on the assessment skill gaps and determine if the employee is at required level, above required level or below required level. The system shall use only an approved assessment to show employee readiness.

Future Changes to Readiness Calculations: The COR may make changes to the calculation used for employee readiness. These will depend on outcomes from SME discussions and competency workshops.

Each competency score shall be put in one of two categories: Core or Non-Core. Only core competencies shall count for the employee readiness calculation / score. The employee’s Skill

Gap for each Competency shall be added together to get a final score. A score of 0 is the Target; a positive number is Above Target; a negative number is Below Target. Reports must be available showing the readiness of individual employees and for each organization level.

6.2.14 Supervisor Readiness Dashboard: The systems shall (1) Provide a view or tab to show the following information for each organizational level: All DISA, Center, Directorate/Organization, branch, or multiple branches. Tab shall include: Total Number of Employees, % Submitted, %

Approved, % Above Target and % At Target, % Below Target. (2) Provide a view or tab for “by

Series”, to show the following: Total Number of Employees, % Submitted, % Approved, %

Above Target, % and At Target, % Below Target.

6.2.15 Agency Readiness Calculations. The contractor shall calculate agency readiness based on COR approved assessment readiness scores. All approved employee assessment readiness scores will be defined by DISA after post award.

6.2.16 Top/Below 5 Competencies. The Top and Below Competencies calculations, charts and reports shall reflect the following: Competencies shall be determined by using COR approved assessments only. Only core competencies shall be used in the calculations. For Top 5

Competencies, approved assessments with core competencies at or above standard. Each competency with this score shall be summed up and the competency with the highest sum down to the 5th competency with be considered as the top 5. The Top 5 Competency Chart/Report shall show only the following information: Name of competency (from highest rank) and number of times scored at at/or above standard for all approved assessment. For Below 5 Competencies, all approved assessments with core competencies below standard shall be included. Each competency below standard shall be summed up and the competency with the highest sum down to the 5th competency with be considered as the below 5. The Below 5 Competencies

Chart/Report shall show only the following information: Name of competency (from highest rank) and number of times scored below standard for all approved assessment. A separate report shall show by job series Top/Below 5 for each competency type. The system shall have the functionality for skill gap reports to be made available by individual employee, top 5/below 5 skill gaps by job series.

6.2.17 Competency Levels. The system shall have the functionality to customize the competency model to meet DISA’s requirements. The system shall have the functionality to drill down to a minimum of four (4) levels, For example, entry level, intermediate level 1, Intermediate level 2, Senior

6.2.18 Competency Development Guide. The system shall create Competency Development Guides

(CDGs) that shall be included for each series, Information Assurance (IA), and (Defense

Acquisition Workforce Improvement Act (DAWIA), and FM 500 Series and for each performance level. The CDGs provide employees with a comprehensive list of professional, leadership, and technical competencies as well as associated developmental activities from DISA eLearning training, DOTS, DAU, etc. The CDGs shall be available to view on screen, for download via

PDF and Excel, and for printing. The CDGs can assist in employee preparation to advance in a current position, move into a new career path, or become a leader. The contractor shall be responsible for ensuring that CDGs are updated to reflect updates/changes make to skills and developmental activities in real time (i.e. when SME workshops are completed). The Competency

Development Guides are based upon Career Development Guides which are the output of the

Competency Workshops identified in section 6.5, Task 5.

6.2.19 The system shall utilize PKI Authentication.

Milestone Completion Schedule for Task 6.2

Task

Location in System Description Due Date

A Initial Solution

Implementation

The initial solution should be installed / implemented, following appropriate Risk Management Framework (RMF) process for Authorization and Accreditation.

Within 1 month of award

B Risk Management

Framework (RMF) Receive Interim Authority to Operate (IATO) within

Within 4 months of award

C Risk Management

Framework (RMF) Authority to Operate (ATO)

Within 9 months of award

D Assessments Update DTMS assessment reports to meet new calculations, terms and definitions, as confirmed by SD2 and MP5

Within 3 months of implementation

Deliverables: Initial System

First Draft Systems Documentation

Documentation of the Application STIG and necessary application configurations

Evidence to support A&A to be loaded in eMass

Systems Documentation

Release Schedule and Plan

Release Notes

Requirements Matrices

Systems Diagrams

Report Descriptions, Maps, and Calculations Data (trace the calculations and data pulls)

Inclusion of progress status in Monthly Summary Report (See Task 1)

6.3 Task 3 System Maintenance

The contractor shall provide DISA with standard system maintenance, to include upgrades throughout the performance year to keep the system current with any DISA organizational, regulatory, or otherwise required, changes, to include but not limited to, security requested upgrades or documentation. The contractor shall resolve, within 48 hours, issues that impact the core functionality of the system and usability of the system, system problems, access issues, bug fixes, security vulnerabilities, and software updates that occur during supported year. Support shall be provided for technical problems with the functions of the software. Contractor shall not make updates or changes to system functionality without prior approval from the COR.

The contractor shall work with the COR to maintain remote access to the DTMS environment which will enable the contractor to provide the required levels of support for purposes of performing diagnostics, maintaining the security posture, examining configuration, evaluating competency activities, and generating/publishing new reports. The contractor shall conduct monitoring and sustainment activities which shall cover required coding (i.e. SQL, Java, ColdFusion, etc.) and configuration activities necessary to sustain the application’s security posture.

The contractor shall support the effort using Government tracking systems as required; including IT Service

Management (ITSM) for help desk tickets, Forge for Change Management, and eMass as necessary for Risk

Management Framework Authorization and Accreditation

The contractor shall use a Government environment external (test environment) for the production DTMS system accessed by DISA, including any required databases, etc., for testing system upgrades, troubleshooting system issues and testing of new features. The system shall be available to DISA for user acceptance testing for new requirements, upgrades, training materials creation, etc.

If development activities are required for this system, as determined by the COR, the contractor shall provide a development environment aligned with system requirements.

Deliverables:

User Accounts to Complementary Systems (i.e. test environment)

Inclusion of issues or concerns in Monthly Summary Report (See Task 1)

6.4 Task 4 Issue / Incident Resolution

The contractor shall provide support to the DISA Global Service Desk ITSM Ticket resolution process. The contractor shall act as a Subject Matter Expert in support of the DISA Help Desk personnel. The contractor shall provide and maintain scripts addressing common Tier I issues and frequently asked questions to help the DISA

Global Service desk with one-call resolution. The contractor shall provide DISA with on call Tier II email and phone support during normal business hours (8 AM- 5 PM) for any issues that may arise with operation or usage of the system. Tier II support is for those issues that cannot be resolved by DISA Global Service Desk. The contractor shall resolve all Tier II incidents within four business hours of the incident being reported and ticket created...

Deliverables: Inclusion of incidents in Monthly Summary Report (See Task 1)

6.5 Task 5 DTMS Readiness/Competencies

The contractor shall update Readiness and Competency definitions, measures and requirements, annually, to ensure currency with regulations, standards, policies, guides, or doctrine, etc. DISA will review and update readiness and competency definitions at least annually. Out of cycle changes shall comply with emerging laws, regulations, or policies as mandated by the Office of the Secretary of Defense (OSD) and public law. The contractor shall make the required changes to the system using proper agile software development and deploy practices.

The contractor shall facilitate and support up to eight annual Subject Matter Expert Workshops, focused on reviewing and updating competencies by job series. The contractor shall be the expert on working with DoD/OPM, and/or federal Government competency models and the vendor’s software. Any changes to the system resulting from these workshops shall follow the deliverable requirements for systems changes as specified in Tasks 1 and 2 above, including release documentation, updated system documentation, release notes, and updated system descriptions and diagrams.

Deliverables: Inclusion of results in Monthly Summary Report (See Task 1)

6.6 Task 6 System Training

The contractor shall create and maintain documentation for all DTMS functionality by role

(employee/supervisor/admin). Documentation should include DTMS Manuals (admin/employee/supervisor);

DTMS reports guide, a Quick Reference Guide for Employees and Supervisors, and system frequently asked questions (FAQs). In addition, the contractor shall create training courses and materials for the system functionality based by role (employee/supervisor/admin) for the workforce. The contractor shall create 508 compliant videos for employees and supervisors on system usage. All initial training documentation and videos, as well as updates to documentation and video must be reviewed and approved by the COR. Any changes to system functionality will require updates to all documentation and videos. Updates to the documents and/or videos shall be completed within

30 calendar days of the change/update. The contractor shall train DISA select administrative personnel on all system functionality including admin functions, employee and supervisor role functionality. Additionally, the contractor shall train DISA admin personnel after any major changes/updates which result in a new functionality.

Deliverables: Inclusion of training material completion status in Monthly Summary Report (See Task

1)

Role Functionality Documentation

Reports Guides

Manuals

508 Compliant Instructional Videos

Quick Reference Guide

Frequently Asked Questions

Training Courses

6.7 Task 7. Additional Enhancements – SURGE/Optional Task

Additional enhancements to DTMS are envisioned and are deemed as optional tasks at this time. Due the current uncertainty of these requirements the Government plans to use the SURGE CLIN to exercise these additional tasks once the Government becomes aware of the exact requirements, timeline, and funding availability for these enhancements. It is anticipated that Surge support over the life of the contract will not exceed 20% of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to FAR 52.217-8. These enhancements include:

6.7.1 Automated Database Interfaces: The system shall import information from automated learning systems (i.e. eLearning, DOTS, DAU), and pre-populate course information into the system for the IDP development activity. Note, 6.1.7 and 6.1.8 are for the linking and incorporation, whereas this section (6.7.1) is for the automated and near real time population of data.

6.7.2 Automated parsing of JTD into DISA Organizational structure: The system shall parse the JTD down to the division and branch DCodes. This requirement builds on the system’s capability to parse the DISA organizational information from the JTD import file into the current DISA organizational structure with appropriate

DISA personnel. The enhancement to the capability, is that organizational information shall go down to the individual branch and division (DCodes) levels.

6.7.3 Archive of IDP Courses: The system shall keep an archive of IDP courses completed for each employee for 5 years (regardless of employee status).

Deliverables for 6.7: Updated Software reflecting automated database interfaces

Updated Software reflecting automated JTD parsing to the branch level

Updated Software reflecting enhanced archive capabilities

7. Performance Standards.

Performance Standard Acceptable Quality Level (AQL) Method of Surveillance

Task 1: Program

Management

Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection

Task 2: Implement and

Configure the system

Materials contain required information and are delivered on time at least 90% of the time.

Revisions that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection with Customer Input

Task 3: System Maintenance Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection

Task 4: Issue Resolution Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection

Task 5: DTMS Readiness /

Competencies

Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection with Customer Input

Task 6: System Training Materials provided with no required re-performance or re-work, on time, at least 90% of the time.

Documents are delivered on time at least 90% of the time, with minimal grammatical editing required.

Revisions for grammar and content are minor and are resolved within 2 business days.

Periodic Inspection

Task 7: Additional

Enhancements- Optional

Task

Performance occurs with no required re-performance or re-work at least 90% of the time. Problems that occur are minor and are resolved in a satisfactory manner.

Periodic Inspection

8. Incentives. The Government will positively and/or negatively review the contractor’s performance based on the success or failure in meeting quality assurance surveillance plan objectives. The Government will make determinations for option period awards based on contract performance, as measured by this surveillance plan. The contractor is incentivized to earn favorable Government reviews to support continuation of DISA work and to support contract awards with other Government agencies seeking DISA’s input on the contractor’s past performance and the CPARS.

Failure to meet a stated delivery performance standard as identified in the Milestone Completion Schedule for Task

6.2 will result in a $1,000 credit to the Government for the 1st instance; $3,000 for the 2nd, & $5,000 for the 3rd instance. The credit will be reflected in the invoice following the event. Disincentives applied will be reflected in the relevant CPARS entry.

9. Place of Performance.

The tasks shall be performed at the contractor’s site and at DISA HQ 6910 Cooper Ave, Ft. Meade, MD, 20755.

Travel in and around the primary place of performance may be required throughout the period of performance.

Additional travel within CONUS may be required to support the requirements of this PWS.

9.2 Alternate Place of Performance - Contingency Only. As determined by the Contracting Officer’s

Representative (COR), contractor employees may be required to work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, Government closure due to inclement weather, etc.). Non-emergency/non-essential contractors should not report to a closed Government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.

9.3 Travel

Travel in and around the primary place of performance may be required throughout the period of performance.

Additional travel within CONUS or OCONUS may be required to support the requirements of this PWS.

9.3.1 Local Travel:

Travel will be considered local travel within 50 miles of the individual’s main place of performance/duty station.

Local travel will not be reimbursed.

9.3.2 Continental US (CONUS)

In coordination with the COR or ACOR, the contractor may be required to support activities outside the NCR. The contractor shall inform the COR, in writing, of the estimated total travel costs prior to any travel outside the NCR.

The COR or ACOR will coordinate such requests. Travel outside of the National Capital Region shall be approved in writing by the COR prior to the travel occurring. Specific travel requirements shall be coordinated with the

COR/ACOR and shall be in accordance with Federal Acquisition Regulation (FAR) 31.205-46 requirements and limitations. Reimbursement for travel expenses shall be made in accordance with the Federal Travel Regulations.

10. Period of Performance. The period of performance will be one (1) base year plus three (3) 12-month option years to be exercised as the discretion of the Government. In addition, FAR clause 52.217-8 will be included which allows the Government to authorize performance for an additional 6 months if deemed necessary.

11. Delivery Schedule.

The deliverables identified below are required under this effort.

PWS Task# Deliverable Title Format Due Date Distribution/Cop ies

Frequency and Remarks

6.1.1 Subtask 1

Program

Management

KOM Agenda

Contractor (CTR) propose preferred format for SD2 approval.

5 business days after award

Standard

Distribution

Single time

6.1.1 Subtask 1

Program

Management

Briefing Materials CTR propose preferred format for SD2 approval.

5 business days after award

Standard

Distribution

Single time

6.1.1 Subtask 1

Program

Management

Action Item Lists Microsoft Excel Final

Wednesday of the month post contract award

Standard

Distribution

Monthly, Final

Wednesday of the month

6.1.1 Subtask 1

Program

Management

KOM Minutes CTR propose preferred format for SD2 approval.

5 business days after KOM

Standard

Distribution

Single time

6.1.2 Subtask 2

Program

Management

Project Schedule CTR propose preferred format for SD2 approval.

15 business days after award

Standard

Distribution

Updated

Final

Wednesday of the month

6.1.3 Subtask 3

Program

Management

Monthly Status

Report

Microsoft Word Final

Wednesday of the month post contract award

Standard

Distribution

Monthly, Final

Wednesday of the month

6.1.4 Subtask 4

Contract

Transition

Transition Plan Varied based on

Documentation type. MS

Word is acceptable.

Upon notification from the Government

(not less than 2 months before end of contract)

Standard

Distribution

Two months prior to the conclusion of contract

6.1.4 Subtask 4

Contract

Transition

In-progress working files

Varied based on

Documentation type. MS

Word is acceptable.

Upon notification from the Government

(not less than 2 months before end of contract)

Standard

Distribution

Two months prior to the conclusion of contract

6.1.4 Subtask 4

Contract

Transition

Historical files Varied based on

Documentation type. MS

Word is acceptable.

Upon notification from the Government

(not less than 2 months before end of contract)

Standard

Distribution

Two months prior to the conclusion of contract

6.1.4 Subtask 4

Contract

Transition

Concept of

Operation

(CONOPS)

procedures

MS Word Upon notification from the Government

(not less than 2 months before end of contract)

Standard

Distribution

Two months prior to the conclusion of contract

6.1.4 Subtask 4

Contract

Transition

Lessons Learned MS Word Upon notification from the Government

(not less than 2 months before end of contract)

Standard

Distribution

Two months prior to the conclusion of contract

6.2 Task 2

Define and implement

DTMS

software and functionality

Initial System Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

30 calendar days after award

Standard

Distribution

30 calendar days after award

6.2 Task 2

Define and implement

DTMS

software and functionality

First Draft

Systems

Documentation

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

30 calendar days after award

Standard

Distribution

First Draft is complete upon approval from COR

6.2 Task 2

Define and implement

DTMS

software and functionality

Documentation of the applications

STIG and necessary application configurations

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

30 calendar days after award

Standard

Distribution

30 calendar days after award

6.2 Task 2

Define and implement

DTMS

software and functionality

Evidence to support A&A to be loaded in eMass

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

30 calendar days after award

Standard

Distribution

30 calendar days after award

6.2 Task 2

Define and implement

DTMS

software and functionality

Systems

Documentation

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

15 calendar days after receiving approval of First

Draft from MP5

Standard

Distribution

Quarterly, first Monday of the month

6.2 Task 2

Define and implement

DTMS

software and functionality

Release Schedule and Plan

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

At minimum, 30 calendar days prior to a release

6.2 Task 2

Define and implement

DTMS

software and functionality

Release Notes Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

At maximum

3 calendar days post release

6.2 Task 2

Define and implement

DTMS

software and functionality

Requirements

Matrices

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Quarterly, first Monday of the month

6.2 Task 2

Define and implement

DTMS

software and functionality

Systems

Diagrams

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Quarterly, first Monday of the month

6.2 Task 2

Define and implement

DTMS

software and functionality

Report

Descriptions, Maps, and

Calculations Data

(trace the calculations and data pulls)

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Quarterly, first Monday of the month

6.3 Task 3

System

Maintenance

User Accounts to

Complementary

Systems (i.e. test environment)

Email As scheduled per the Project

Schedule

Standard

Distribution

As needed

6.6 Task 6

System

Training

Role

Functionality

Documentation

Varied based on

Documentation type. CTR propose preferred format for MP5 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Annually

6.6 Task 6

System

Training

Reports Guides Varied based on

Documentation type. CTR propose preferred format for MP5 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Updated as needed with each software release

6.6 Task 6

System

Training

Manuals Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Updated as needed with each software release

6.6 Task 6

System

Training

508 Compliant

Instructional

Videos

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

Within 30 calendar days of software delivery

Standard

Distribution

Updated as needed with each software release

6.6 Task 6

System

Training

Quick Reference

Guide

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Updated as needed with each software

6.6 Task 6

System

Training

Frequently Asked

Questions

Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Updated as needed with each software release

6.6 Task 6

System

Training

Training Courses Varied based on

Documentation type. CTR propose preferred format for SD2 approval.

As scheduled per the Project

Schedule

Standard

Distribution

Updated as needed with each software release

6.7 Task 7

Optional

Enhancements

Updated Software reflecting automated database interfaces

Varied based on

Documentation type. MS

Word is acceptable.

30 calendar days after exercise of option.

Standard

Distribution

Updated as needed with each software release

6.7 Task 7

Optional

Enhancements

Updated Software reflecting automated JTD parsing to the branch level

Varied based on

Documentation type. MS

Word is acceptable.

30 calendar days after exercise of option.

Standard

Distribution

Updated as needed with each software release

6.7 Task 7

Optional

Enhancements

Updated Software reflecting enhanced archive capabilities

Varied based on

Documentation type. MS

Word is acceptable.

30 calendar days after exercise of option.

Standard

Distribution

Updated as needed with each software

*Standard Distribution: Contracting Officer and Contracting Officers Representative.

12. Security Requirements. The work under this PWS will be at the Unclassified level. All security requirements are specified in the PWS and DD Form 254, Contract Security Classification Specification.

This section shall be considered a supplement to block 13 of the Government provided DD 254, Contract Classifi-cation Specification. The following security requirements shall apply to this effort.

References:

a. DOD 5200.2-R, DOD Personnel Security Program.

b. DISAI 240-110-36, Personnel Security.

c. DOD 5220.22-M, National Industrial Security Program Operating Manual.

d. DOD 5220.22-R, Industrial Security Regulation.

e. DODM 5200.01, Vol 1-4 Information Security Program, 24 February 2012

f. DISAI 240-110-8, information Security

g. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 Sep 2013

h. DISA Form 786

12.1 Facility Security Clearance. The work to be performed under this contract is up to the Unclassified level.

Therefore the company is not required to have a Facility Clearance from the Defense Security Service Facility

Clearance Branch.

12.2 Security Clearance and Information Technology (IT) Level. All personnel performing on or supporting a DISA contract in any way will be U.S. citizens. There are two level(s) of personnel security requirements under this contract covering the following types of positions: (examples below, remove the content that is not applicable.)

12.2.2 The following type(s) of position(s) and task(s) require(s) an interim secret IT-II eligibility when performance starts. The following task(s) require(s) an interim secret IT-II eligibility (Task 1-3, 5-7):

- Subject Matter Expert (Intermediate) (Tasks 1-3, 5-7)

- Software Systems Engineer / Senior Analyst (Tasks 1-3, 5-7)

12.3 Investigation Requirements.

12.3.1 All personnel requiring Secret access under this contract shall undergo a favorably adjudicated…