20180419_SSS-draft-pws.pdf

Contract #: TDB Attachment 1

Version date: 19 April 2018

PERFORMANCE WORK STATEMENT (PWS)

Multi-Source Assessment and Feedback (MSAF) System Support Operations

DRAFT

1. General: This is a non-personal services contract to support a multisource assessment and feedback (MSAF) system for leader development. The contracted services include information technology support to operate and maintain the platform (the hardware and application components of the MSAF program system), manuals and user documentation for the IT platform, quantitative and qualitative feedback reports to individual assessed leaders and unit commanders, improvement materials for assessed leaders, and other manuals and user documentation, provide support and administration of Unit 360 events, and conduct outreach for the MSAF System.

1.1. Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to operate and maintain the MSAF system as defined in this PWS except for those items specified as Government furnished property and services. The contractor shall perform to the standards in this contract.

1.2. Background: The Commanding General, Training and Doctrine Command (TRADOC) approved implementation of MSAF as an Army-wide program on 30 April 2007. The program was implemented in a phased manner in all leader development domains (operational, institutional, and self-development) to military leaders, E-5 to E-9, W-1 to CW-5, O-1 to O-6, and civilian leaders in the General Schedule. The MSAF system provides: 1) 360 degree performance assessment of leaders from the perspectives of subordinates, peers, superiors, and self-assessment by the leader --aligned to leadership and leadership development doctrine, 2) feedback to leaders (individually) and commanders (for units) about leadership performance, 3) resources to interpret the feedback and continue to develop as leaders, and 4) mechanisms to track completion of MSAF assessments in order to comply with Army regulations. The MSAF system now consists of 360 degree assessment sub-programs including, Leader360 (LDR360), Commander 360 (CDR360), Unit360, and Joint360.The MSAF System is a web based survey program that generates feedback reports from 360 and non 360 degree assessments to the users. The MSAF System is the public interface. The Center for Army Leadership (CAL) is responsible for the content and hosting of the agency web presence. Additionally, the CAL publishes leadership educational materials relating to all aspects dealing with the MSAF Program and Leader Development.

1.3. Objectives: This support contract enables CAL to execute its designated functions of executing the MSAF program and serving as the Army lead for leadership doctrine and leadership development. CAL’s mission is to identify leader development trends, requirements, training and education strategies and leadership management and leader development products and services. CAL operates in accordance with Army Regulation 600-100 and TRADOC Regulation 10-5-4. CAL’s Leadership Research Assessment and Doctrine Division (LRADD) has implemented the Army MSAF program and manages the operations of the program on a daily basis. Key objectives of assessments in the MSAF system are to provide:

1.3.1. Assessment.

1.3.1.1. Increase leader self-awareness through the use of quantitative and qualitative assessments that are consistent with leadership regulations and doctrine, and that can be accessed “on-demand”.

1.3.1.2. Ensure assessments adhere to best practices of psychological measurement.

1.3.2. Feedback.

1.3.2.1. Deliver error-free feedback in a manner that facilitates leader development and adheres to best practices in personnel development.

1.3.2.2. Maintain the privacy of individuals by ensuring source data and feedback reports are protected from accidental release.

1.3.3. Development

1.3.3.1. Facilitate individual and unit leader development by providing professional quality self-study material and coaching based on assessment results and leadership doctrine.

1.3.3.2. Facilitate skill development in the areas of counseling and coaching through training material.

1.3.4. Tracking

1.3.4.1 Facilitate the completion of individual and unit assessments by providing assessment completion reports, automated reminders, and help-desk functions.

1.3.5. The MSAF system is operated by government personnel and with support from contract functions and products. The current operating concept includes a) government personnel for oversight and management of the MSAF system and for evaluation functions, b) information technology support, and c) support operations and d) coaching.

1.3.6. The IT platform has the following general specifications. The IT platform exists on government furnished (GF) servers located at TRADOC MS Azure cloud services or at a comparable government facility. The GF multi-capacity servers are accessed via the internet using CAC authentication. The platform provides simultaneous access by multiple participants to meet the estimated needs of Army-wide use by other services and governmental agencies. The platform supports website accessibility through both high speed and low speed connections. The IT platform complies with all applicable DOD/DA regulations for operations security (OPSEC) and web security (WEBSEC).

The IT platform is compliant with Communications Tasking Order (CTO) 07-15.

The IT platform allows for ‘turn-key’ operation for CAL designated administrators, including all features to perform all the required functions. The system incorporates mechanisms to provide capabilities to match the following different types of MSAF applications, including uniformed personnel and Army civilians:

Personnel assigned to organizations under a modified table of organization and equipment (MTOE). Personnel assigned to organizations under a table of distributed allowances (TDA).

Students or personnel entering Army education system courses.

Individuals who have not had an MSAF opportunity or received a rating and who meet Army policy qualifications to do so.

1.3.7. The system is designed to prepare assessment instruments for administration.

The system is designed to prepare assessment groupings and assignments. The system has the capability to provide assessment assignments upon log-in to the system or to send emails that identify the assessment assignments and provide assignment notification or invitation to participate based on an administrator’s selection for a given instance. The system supports and tracks completion of assessments. The system checks data and prepares feedback. The system provides feedback for presentation to the target leader. The system provides portfolio storage. The system provides the capability for follow-up and evaluation with the target leaders. The system provides the capability for storing, aggregating and analyzing data to support program management and instrument validation and tracking including web analytics & the tracking of website usage, assessor load & assessor response rate profile, use of training, and Virtual Improvement Center (VIC) resources accessed by participant. Contractor shall be able to report these to CAL on a consistent, scheduled basis (e.g., monthly).

1.4. Scope: Contracted work for program support and information technology support operations of the MSAF System shall be conducted in four concurrent lines of operations. The maintenance and operation of the MSAF application and its Staging and Production servers at Fort Leavenworth Network Enterprise Center(NEC), until decommissioned, the continuous helpdesk functions and the standing up of the Development and Production servers, followed by the maintenance and operations of the MSAF application in the TRADOC MS Azure Cloud Services.

1.5. Period of Performance: The period of performance shall be for 12 months.

1.6. General Information

1.6.1. Quality Control: Quality Control: Quality Control is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the Government (see FAR 52.246-4, Inspection of Services – Fixed-Price).

The Contractor shall develop, implement and maintain an effective Quality Control System which includes a written Quality Control Plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance to ensure all contract requirements are met. The Contractors’ QCP must contain a systematic approach to monitor operations to ensure acceptable services/products are provided to the Government. The QCP, as a minimum, shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints. The QCP shall be provided to the Contracting Officer (KO) and contract specialist via e-mail within 10 business days of the performance start date (PSD). The Government will accept, or return the QCP for revision within 10 business days. Any change to the QCP after initial acceptance requires the review and acceptance by the KO.

1.6.2. Quality Assurance: The Government will evaluate the contractor’s performance under this contract in accordance with (IAW) the Quality Assurance Surveillance Plan.

This plan is a Government only document primarily focused on what the Government must do to assure that the contractor has performed IAW the requirements of the contract.

1.6.3. Federal Government Holidays:

New Year’s Day 1st day of January Martin Luther King Jr.'s Birthday 3rd Monday of January Presidents Day 3rd Monday of February Memorial Day Last Monday of May Independence Day 4th day of July Labor Day 1st Monday of September Columbus Day 2nd Monday of October Veterans Day 11th day of November Thanksgiving Day 4th Thursday of November Christmas Day 25th day of December

1.6.4. Hours of Operation: The contractor is responsible for conducting business while the facility is open, between the hours of 8:30 AM-4:30 PM Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

1.6.5. Place of Performance: Work to be performed under this contract will be performed at Government Facilities, Fort Leavenworth, Kansas. Help desk personnel are not required to be on-site. The remainder of the tasks shall be performed at Contractor Facilities.

1.6.6. Security Requirements: Contractor personnel performing work under this contract must have a SECRET security clearance upon the performance start date, and must maintain the level of security required for the life of the contract. The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service at the time of proposal submission and must maintain the level of security required for the life of the contract. The security requirements are in accordance with the attached DD Form 254, Department of Defense Contract Security Classification Specification. In addition, access to the Fort Leavenworth NIPRNET and SIPRNET is limited to United States citizens.

1.6.6.1. Physical Security: The contractor shall be responsible for safeguarding all Government equipment, information and property provided for contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.6.7. Special Qualifications: Contractor shall utilize an Industrial/Organizational Psychologist and must have subject matter expert(s) to understand, analyze, contribute to, and advise the MSAF support tasks about best practices for 360⁰ assessment and feedback; personnel assessment; test validation; database design; interface usability, design and testing; leadership development; learning resources; and delivery and management of customer programs.

1.6.8. Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity IAW Federal Acquisition Regulation Subpart 42.5, Post Award Orientation. The Contracting Officer, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the Government will apprise the contractor of how the Government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.6.9. Contracting Officer Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions:

assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract;

issue written interpretations of technical requirements, including Government drawings, designs, and specifications; monitor Contractor's performance and notify both the KO and Contractor of any deficiencies; coordinate availability of Government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.10. Key Personnel: The following personnel are considered key personnel by the Government: Contract Lead (CL) and Lead Systems Administrator (SA). The contractor shall provide a Contract Lead who shall be responsible for overseeing the performance of the work. The name of this person and an alternate who shall act for the contractor when the lead is absent shall be designated in writing to the contracting officer. The

Contract Lead or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The Contract Lead or alternate and the Lead SA shall be available between 8:30 a.m. to 4:30p.m., Monday thru Friday except Federal holidays or when the Government facility is closed for administrative reasons. The Contract Lead is not required to work on-site. They shall be available by telephone and e-mail, during the stated core hours.

1.6.10.1 Contract Lead. The Contract Lead shall have a minimum of 5 years’ Program Management experience with a focus on integration of disparate tasks, preferably with IT program experience. The Contract Lead shall act as the central point of contact for the COR, for all requirements under this contract.

1.6.10.2 Lead Systems Administrator. The Lead SA shall meet the certification requirements of paragraph 1.6.23, with a computing environment of MCSA: Windows Server 2012 (Configuration) – or MCSE: Server Infrastructure.

1.6.11. Identification of Contractor Employees: The Contractor shall provide each employee an Identification (ID) Badge, which includes at a minimum, the Company Name, Employee Name and a color photo of the employee. ID Badges for Key Personnel shall also indicate their job title. ID Badges shall be worn at all times during which the employee is performing work under this contract. Each Contractor (to include subcontractors) employees shall wear the ID Badge in a conspicuous place on the front of exterior clothing and above the waist except when safety or health reasons prohibit.

The Contractor (to include subcontractors) shall be responsible for collection of ID Badges upon completion of the contract or termination of employee. All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials.

1.6.12. Supervision of Contractor Employees: The Government will not exercise any supervision or control over Contractor or subcontractor employees while performing work under the contract. Such employees shall be accountable solely to the Contractor, not the Government. The Contractor, in turn, shall be accountable to the Government for Contractor or subcontractor employees.

1.6.13. Contractor Travel: Occasional travel in support of Task 3 para 5.3 may be required in support of Unit360 event coordination. The Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/authorization and notification to the COR, prior to making travel arrangements.

1.6.13.1 Contractor employees traveling to Germany are required to follow the AE Regulation 600-77. The COR will verify DoD contractor personnel eligibility for SOFA certificate and complete AE Form 600-77A for verified member(s). Contractor employees will take passport and AE Form 600-77A to the local Passport Office for processing.

The Contractor shall provide the following information with their WAWF invoice to substantiate any Cost Reimbursable Travel Expense payment claim:

a. A brief description of the travel to include traveler(s) name(s), dates of travel, destination and purpose of travel.

b. Copies of receipts for all airfare, lodging and any expense in excess of $75.00.

c. Claims for payment of per diem shall be accompanied by a corporate worksheet or copy of the employee’s per diem voucher listing the location, dates and per diem rate applied to the claim.

d. Acceptable submissions include paid receipts from airlines and hotels or copies of corporate credit / purchase card statements providing that the statement lists the date, vendor name and amount of purchase.

e. All backup documentation shall clearly indicate the actual date that the contractor incurred the claimed expense.

f. Failure to provide the required documentation may result in rejection of the contractor’s invoice as not being a proper invoice as described in FAR 32.905(b)(2).

g. Travel invoices shall be submitted separately from labor invoices.

h. Travel invoices shall be submitted within 60 calendar days of completion of the travel event. Failure to do so will be noted in the performance assessment.

NOTE: Travel shall be reviewed and approved in writing by the COR prior to the contractor incurring any billable expenses. Unapproved travel expenses are not a billable expense.

1.6.14. Other Direct Costs: The government has provided to the contractor the hardware and software to set up a TFS/DEV/ environment to be located at BAH facility.

1.6.15. Organizational Conflict of Interest (OCI): The contracting officer has identified the potential for on OCI related specifically to paragraph 5.1.4.1, below, on the impaired objectivity basis. As a condition of award under this solicitation, the successful offeror cannot be a manufacturer or seller of the types of technologies being evaluated under this PWS.

1.6.16. Anti-Terrorism (AT) Level I Training. All contractor employees requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days of the performance start date (PSD) or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees. AT level I awareness training is available at the following website: http://jko.jten.mil.

1.6.17. Access and General Protection/Security Policy and Procedures. Contractor and employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

1.6.17.1. Contractors Requiring a Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management. The government issued credential (CAC) is the property of the U. S. government and shall not be retained upon expiration, replacement, or when the DoD affiliation of the employee has been terminated. The Contractor has a responsibility to ensure the government issued credential (CAC) is returned in accordance with local command or installation procedures. Unauthorized possession of an official credential, like a CAC, can be prosecuted criminally under section 701, title 18, United States Code.

1.6.17.2. Contractors Not Requiring a CAC but Require Access to a DoD Facility or Installation. Contractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190- 13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

1.6.18. iWATCH Training. The contractor shall brief all employees on the local iWATCH program (training standards provided by the requiring activity’s ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of the PSD and within 30 calendar days of new employees commencing performance with the results reported to the COR no later than (NLT) 15 calendar days after completion of training.

1.6.19. Access to Government Information Systems. All contractor employees with access to a Government info system shall be registered in the Army Training Certification Tracking System (ATCTS), and shall successfully complete the DoD Information Assurance (IA) Awareness prior to gaining access to the IS and annually thereafter. DoD IA training is available at https://atc.us.army.mil/

1.6.20. OPSEC Training. Per AR 530-1, Operations Security, all contractor employees shall complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees shall complete annual OPSEC awareness training.

https://www.iad.gov/ioss/site/customer.cfm or http://www.cdse.edu/catalog/elearning/GS130.html

1.6.21. Information assurance (IA/DoD Cyber Assurance Challenge) training. All contractor employees and associated sub-contractor employees will complete initial IA/DoD Cyber Assurance Challenge training, Sign user agreement and an AUP prior to being granted access to the network and annual thereafter per AR 25-2. DoD Cyber Assurance Challenge awareness training is available at the following website:

https://ia.signal.army.mil/ . Contractor employees at a minimal must have a favorable National Agency Check with Inquiries (NACI) background investigation to access the non-classified internet protocol router network (NIPRNET).

1.6.22. Information Assurance (IA)/Information Technology (IT) Certification. Contractor personnel performing IA/IT functions shall be certified per DoD 8570.01-M, DFARS

252.239.7001 and AR 25-2. Contractor personnel shall be certified at the IAT Level II as stipulated in DoD 8570.01-M. The full range of applicable Computing Environment (CE) Certifications are: MCSA: Windows Server 2012 or MCSE: Server Infrastructure; MCTS:

SQL Server 2008, Implementation and Maintenance or newer; MCITP: SharePoint Administrator 2010 or newer, and MTA in Software Development Fundamentals or HTML5 App Development Fundamentals. See the table below for a crosswalk to the Task 1 subtasks. The Government expects that the individual holder a certain CE will perform the work against the applicable subtask. IAW AR 25-2, the IT level applicable to this PWS is IT Level II. Additionally, contractor personnel must meet the requirements of AR 25-2 for IT Level II functions, which includes a favorable National Agency Check with Local Agency and Credit Checks (NACLC) investigation. The contractor shall provide proof of all applicable DoD 8570.01-M certifications and AR 25-2 investigations for performance under this contract immediately following the Post Award Conference (PAC), or within 10 business days of an individual’s PSD. Contractor personnel shall complete the applicable AR 25-2 specified training requirements within 6 months of their PSD (Para 4-3.a(6)(a) and (b)).

All IT-II personnel shall hold the applicable baseline certification on their PSD. The Lead Systems Administrator shall hold the required CE certification on the PSD. At least one member of the team shall hold either a MCTS: SQL Server 2014, Implementation and Maintenance or newer, or MCITP. The remaining members of the team shall complete their applicable CE certification at beginning of PoP. As a team, each of the stated CE’s shall be covered.

1.6.24. Handling or Access to Classified Information. Contractor will have a personnel security clearance appropriate for the classification level deemed for the contract.

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause covers access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

1.6.25. Threat Awareness Reporting Program (TARP). Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees who possess a security clearance must receive annual TARP training by a CI agent or other trainer as specified in paragraph 2-4b. The COR will coordinate for the next available TARP class for each period of performance.

2. DEFINITIONS AND ACRONYMS:

2.1. Definitions:

2.1.1. Contractor: A supplier or vendor awarded a contract to provide specific supplies or services to the Government. The term used in this contract refers to the prime.

2.1.2. Contracting Officer: A person with authority to enter into, administer, and/or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

2.1.3. Contracting Officer’s Representative: An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. Defective Service: A service output that does not meet the standard of performance associated with the PWS.

2.1.5. Deliverable: Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. Government Furnished Property (GFP) or Government Property (GP): Property in the possession of, or directly acquired by, the Government and subsequently made available to the Contractor.

2.178. Key Personnel: Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS.

2.1.8. Physical Security: Actions that prevent the loss or damage of Government property.

2.1.9. Quality Assurance: The Government procedures to verify that services being performed by the Contractor are acceptable IAW established standards and requirements of this contract.

2.1.10. Quality Assurance Surveillance Plan: An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.11. Quality Control: All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.2. Acronyms:

AR Army Regulation CAC Common Access Card CAC Combined Arms Center CAL Center for Army Leadership CCB Configuration Control Board CFR Code of Federal Regulations CMR Contract Manpower Reporting COR Contracting Officer Representative CTO Communications Tasking Order DA Department of the Army DD254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DoD Department of Defense EVM Earned Value Management FAR Federal Acquisition Regulation IAW In Accordance With KO Contracting Officer LDIG Leader Development Improvements Guide LRADD Leadership Research Assessment and Doctrine Division MAIDIQ Multiple Award Indefinite Delivery Indefinite Quantity MSAF Multisource Assessment and Feedback MTOE Modified Table of Organization and Equipment OCI Organizational Conflict of Interest OPSEC Operational Security POC Point of Contact PRS Performance Requirements Summary

PSD Performance Start Date PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program SA System Administrator SCM System Configuration Management TDA Tables of Distribution and Allowances TRADOC Training and Doctrine Command VIC Virtual Improvement Center WEBSEC Web Security

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: Not applicable.

3.2. Facilities: The Government will provide the necessary workspace for up to five (5) contractor employees to provide the support outlined in the PWS Task 1, to include desk space, telephones, computers, and other items necessary to maintain an office environment.

3.3. Utilities: The Government will provide all utilities associated with paragraph 3.2 for the contractor’s use in performance of tasks outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions that preclude the waste of utilities.

3.4. Equipment: The Government will provide up to five (5) computers for onsite Contractor personnel providing Task 1 support, in conjunction with paragraph 3.2. In addition, all development, testing and production servers and software will be provided by the Government. The Contractor shall use Government property only for performing this contract, unless otherwise provided for in this contract or approved by the Contracting Officer. For code error fixes the following GFE is provided:6 Computer Workstations, Minimum of Intel Core i7 CPU @ 4 GHz, 64 GB Ram, 2 x 1 TB Hard Drive, 250 GB SSD Hard Drive, 2 x NICs & DVD +-RW; 1 Network Switch, Minimum of eight (8) port GigE Ethernet switch; 1 NAS(Network Attached Storage), Minimum 4 TB Network Attached Storage (NAS) RAID; 12 Computer Monitors; 6 Keyboards & Mice; 5 Power Strips; 4 NIPRNET Laptop, NIPR laptop with VPN access to the NANW G6 server environment; 1 Dell 710 server; 4 Visual Studio Enterprise with MSDN Licenses, Visual Studio, Windows Server, SQL Server and SharePoint software downloads & licensing; 3 ReSharper Ultimate licenses, Visual Studio extension to correct code.

Modifications or alterations of Government property are prohibited. Contractor personnel will be required to sign for electronics equipment provided herein.

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1. General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

5. SPECIFIC TASKS:

5.1. Task 1: Continue enhancements to MSAF2.1 to increase performance of the application on the TRADOC MS Azure cloud services. Upgrade the SP 2010 MSAF application through SP 2013 to SP 2016. Application will be developed and tested in TRADOC MS Azure Development environment before moving to TRADOC MS Azure Production environments.

5.1.1 Deliverable: Fully functioning Development and Production Environments, for all MSAF subprograms applications. (LDR360, Unit360, CDR360, Joint360) in SP 2016.

5.1.2. Standard: All servers in these environments will be configured and tested for full functionality in SP 2016 and completed NLT the end of the 10th month of the bridge contract.

5.2. Task 2: Maintenance and Operations of the MSAF applications in the TRADOC MS Azure Cloud services.

Maintain and Operate MSAF applications with debugs and programmed improvements.

Defect identification and analysis - Identify defects so that they can be fixed and avoided in the future and understand how to correct the defect, the cause of the defect, the frequency of the defect and the impact risk associated with the defect.

Defect Correction - Correct defects to improve the quality of the work products within one business day, or upon an otherwise government-contractor agreed upon date.

Defect Status Reporting - Provide quality and effective metrics for the work products and the maintenance team.

The maintenance includes providing system administration of MSAF servers and applications connected to wide area networks; and responsibilities involving account monitoring, application security, Operating System (OS) installation, and other wide area network administration related functions (i.e. Whitelist entries). Maintenance also includes the design and integration of new functionality into new and existing applications. Observations of the computing environment that lead to recommendations to improve reliability, performance, or cost effectiveness are encouraged. The contractor shall isolate and resolve complex problems involving the application. The Contractor shall function as the subject matter experts and shall have Microsoft or equivalent certifications.

The contractor shall perform Steady-State Corrective Maintenance such as modifications that fix application problems caused by design, logic, or coding errors.

This type of maintenance is often triggered by an explicit service desk ticket and often involves errors that must be addressed immediately. Examples of issues that require corrective maintenance include the following:

Calculations that generate incorrect totals Data screens that omit a required entry or store an entry in the improper location Improper logic in business rules Aborted programs Error messages Interfaces that are not functioning as designed Application configuration issues Maintain a record/log of issues, their repair as well as other changes to the system

In the event of a technical problem that the contractor cannot resolve, the contractor shall provide a written notice to the COR on the same day which, provides details of the nature of the problem and steps that the contractor took to resolve the problem. This downtime does not include events beyond the contractor’s control such as power failure or government-planned downtime. If system outages are caused by insufficient capabilities due to increased participation, the contractor shall provide a recommendation on changes needed to maintain the integrity of the system. This is intended to avoid obsolescence and associated sustainment problems; accommodate future growth potential to take advantage of greater efficiencies, lower costs, and other benefits provided by newer technology. This will be a quarterly review provided to the government on the last business day of each quarter. If system outage was caused by other reasons, corrections shall be made to resolve the problem, i.e. coding corrections, debugging.

Assess the adequacy of these applications for continued supportability, efficiency and effective operation. Recommend upgrades or replacements to the government. Assist the government in providing technical specifications of new applications. Upon government approval install, integrate, maintain, operate and configure new upgrade packages for both the web application and all application packages as appropriate. The government will provide the appropriate software.

5.2.1. Deliverable: Correction of defects deployed in operational MSAF application.

Monthly report identifying all MSAF application improvements (Captured in Monthly Report). Upgrade and replacement recommendations provided every three months via e-mail and verbal discussions.

5.2.2. Standard: Start the diagnosis and correction of application problems within a nominal response time once on site of no more than 3 hours. Network related hardware and applications available 98% of time, downtime not to exceed 24 hours per occurrence (excludes scheduled downtime for maintenance/upgrades). Ensure backup and restore completed successfully 100% of the time with no loss of data within the established time frame for that application or data set. Contractor shall troubleshoot/resolve technical issues no later than three hours from identification of an incident. Written report of correction delivered monthly, in MS Office format, which includes all of the information cited in the task.

5.3 Task 3. System Configuration Management: It is important to have a shared understanding among this contract, sponsoring agency and other contractors and agencies how the system is designed, integrated, updated, tested and deployed. The maintenance and delivery of the application has implications for the creation and delivery of training and supporting documents, revisions to Army-wide policy, socialization of changes among the users, delivery of coaching, and program evaluation. A standard system configuration management (SCM) process shall be used throughout the period of performance. The application at contract start shall be considered baseline. From this baseline, a SCM cycle shall be followed to identify all changes for that cycle and subsequent ones. The configuration management process shall include the use of a configuration control board (CCB) that will approve, reject or table all proposed changes to the baseline. The process shall include identification of proposed changes, configuration documentation, status process accounting, configuration auditing, managing the application build (to include pre-deployment testing), scheduling, documentation and defect tracking. All prior subtasks shall be managed as part of the SCM process. Membership on the configuration control board will include CAL deputy director, CAC G6, LRADD director, COR, MSAF program manager, MSAF lead scientist, government experts as required, and up to 3 contractor personnel as technical advisors.

5.3.1. Deliverables. Use of SCM processes on a 4 month cycle, 3 per contract year.

Multiple, scheduled meetings to execute the SCM process. The contractor shall plan and make recommendations for a future target state of the system. The contractor shall be responsible for recording all aspects of the SCM process and provide a System Configuration Management Plan (SCMP) for all changes which includes:

(1) Configuration identification

(2) Configuration control

(3) Configuration status accounting and reporting

(4) Configuration audits and reviews

(5) Updated Architectural artifacts reflecting current system configuration, interface documents, data-flows, and process map(s).

5.3.3. Standards. Contractor representation at every SCM meeting. Initial SCMP delivered by Month 3 for Government review and acceptance. Final SCMP delivered within 14 work days of receipt of Government comments.

5.4. Task 4: System Administration and Information Assurance in the TRADOC MS Azure Cloud services Development and Production environments: The Contractor shall perform technical security reviews and network analysis to include coordinating scanning, testing, and auditing to determine system and application vulnerability. IAW AR 25-2 and the Army’s IA Training and Certification Best Business Practices, appoint an Information Assurance Officer to enforce security guidance and policies as provided by the IAM. Enforce system and application access, operation, maintenance, and disposition requirements. Schedule and coordinate required Information Assurance Vulnerability Management scanning and vulnerability assessments IAW established DoD/Army policies and procedures. Ensure Configuration Management includes all pertinent patches and fixes by routinely reviewing vendor sites, bulletins, and notifications and proactively updating systems and applications with fixes, patches, definitions, and service packs with TRADOC IAM or IAPM approval. Ensure asset data is entered in the Asset and Vulnerability Tracking Resource (A&VTR) database.

Maintain current anti-virus (AV) engines and definitions on all ISs. Provide the government recommendations on suspending application user accounts for the following types of actions: actions that knowingly threaten, damage, or harm the IS, network or communications security; revocation, suspension, or denial of security clearance or interim security clearance investigations; or unauthorized use of IS and networks per AR 25-2 paragraph 4–5.s

5.4.1. Deliverable: Complete system and application scans, updates and patches as required by TRADOC G6.

5.4.2. Standard: Appoint a primary and alternate certified Information Assurance System Administrator (SA) to enforce applicable security guidance policies as provided by the TRADOC IAPM. Vulnerabilities shall be patched and remediated IAW the TRADOC time schedule.

5.5. Task 5: Application interfaces: Maintain Application Interfaces in the TRADOC MS Azure Development and Production environments. Use Batch Broker Service (BBS) or Real-Time Broker Service (RBS) through, Lightweight Directory Access Protocol (Windows) (LDAP) or similar interface.

5.5.1 Deliverable: Maintain current systems interfaces and data exchange interfaces with other systems DEE GAL and create two system interfaces Army Career Tracker (ACT) and Evaluation Entry System (EES) as determined by the government per contact year by month 6 of the contract year.

5.5.2. Standard: Current interfaces remain 98% functioning properly. Must be fully functioning and provide the type of interface to support functional requirements of the interface. Examples include Updating MSAF date planned and completion dates to ACT allowing for ACT to provide due date notification to MSAF participants or populating MSAF goals to the ACT IDP; auto populating MSAF completion date to OER in EES)

5.6. Task 6: Databases: Design, update, operate, maintain, databases in the TRADOC MS Azure Cloud Development and Production environments. These databases include

• those used to generate and present MSAF system capabilities to users,

• data that is input by users,

• data on system, page and feature use,

• feedback reports for users,

• trend reports for Unit 360 assessments,

• data exports of assessment results (preferred file transfer type is SPSS, but excel is acceptable) for LDR360, Unit360, CDR360, Joint360

• other data as designated by CAL.

Data security is of utmost importance; access to each type of data must be aligned to the level of privilege assigned to level of administrators or classes of users. Data are used to present the correct screens and information to users; to plan and provide assessment assignments; and data are captured, used in calculations and provided in feedback and usage reports. The contractor shall ensure that data provided to the government and provided in feedback reports to users are correct and that calculations are verified and follow business rules put in place to calculate feedback. The COR uses reports on system usage including demographics of participants and usage of various MSAF system site features (training materials, documents, on-line MSAF system programs training, and so on). Databases shall be optimized for accessibility, security, and accuracy. Access to key databases shall be restricted to allow for direct access by identified and approved CAL personnel with MSAF application administrative privileges.

Access, query, report creation and data management functions shall be provided for immediate data access by users and program administrators. Databases shall be structured in a relational format to allow grouping of data for 1) calculation and presentation of comparisons and norms in feedback reports, 2) aggregation in unit and institutional roll-up reports, 3) evaluation of instrument measurement qualities and use of system features, and 4) efficient storage of historical records that can be obtained by assessed individuals. The contractor shall maintain documentation on the structure and history of data including data dictionaries (to include documentation of all variable ID codes, value types and ranges, labels, additional database fields etc.). The contractor shall capture data designated by CAL and add or delete data fields as required. The contractor shall ensure that the databases are configured per government policies. The latest versions of database software shall be installed. Databases shall be properly backed-up, configured, and tuned for optimal performance (i.e. appropriate relational table design, field types and lengths, data entry constraints, indexes, etc.). The database schema shall be reviewed and revised as necessary without loss of data as new features/functions are added to the MSAF program. The contractor shall be responsible to assure accurate assessment data. They shall be responsible for accepting, storing, maintaining and exporting accurate assessment data. The contractor shall demonstrate accuracy of data and feedback report statistics through a track-able method of input, calculations and output using a range of cases (e.g., no basis to assess, business rules for minimum number of assessors). The contractor shall check data during input, calculation, and output processes for inconsistent, illogical or out-of-range responses or values.

5.6.1. Deliverable: Databases that support efficient MSAF functioning through all phases: instrument and feedback report design, instrument and feedback report creation or revision, uploading, testing, operational use, quality control checking, and aggregate analysis. Data structure and history documentation in the form of a log identifying what was changed, when and by whom in MS Excel format and included in report. System will generate the Individual Feedback Reports for all assessment programs within 24 hours after event close and Unit Feedback reports within 15 days after event closure. Unit Feedback Reports within 15 business days after event close.

5.6.2. Standard: Database 100% of errors corrected when identified. Contractor is responsible for QC and ensuring the data provided to CAL is error free. In all cases, all errors in the database are consistently corrected by the contractor within one business day, or upon an otherwise government-contractor agreed upon date, and communicated to the government. 99.5% of the calculated statistics on reports are demonstrated to be error-free and replicable by the government using the same databases. Contractor shall provide completion date when database changes go into effect.

5.7. Task 7: User interfaces: The Contractor shall provide ongoing support and recommendations to ensure that the design, layout, and organization of the MSAF system sites are intuitive and user-friendly, enhance navigation of the MSAF system websites based on current industry standards, maintain and create new additions and/or changes based on input from MSAF Team for survey tools and associated feedback reports.