SVC_18-163_PWS_with_corrected_travel_statement.docx
DOCX document 47 KB Posted
- Attached to
- Prototype Experiment Support Federal contract opportunity
- Solicitation number
- W911S7-18-R-0020
View the file
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT (PWS)
LIVE PROTOTYPE EXPERIMENTATION SUPPORT
MANEUVER SUPPORT CENTER OF EXCELLENCE
MANEUVER SUPPORT BATTLE LAB (MSBL)
FORT LEONARD WOOD, MO
Part 1 GENERAL INFORMATION
1. GENERAL: Maneuver Support Center of Excellence is tasked to support the ARCIC STRACD Live Prototype Assessment venues by researching and evaluating, existing and emerging maneuver support and protection capabilities, developing future concepts, force designs and organizational relationships, evaluating existing and emerging logistics technologies and facilities to support these activities. The MSBL participates in Joint, Army, and other service processes, experiments, and war-games in fulfilling its responsibilities. The contractor shall provide the analytical and technical support to the MSBL for planning, coordinating and execution the Maneuver Support, Sustainment and Protection Integrating Experiment (MSSPIX), which takes place annually in April.
1.1 Background: The contractor shall support the government by designing and supporting future experimentation and analysis venues to enable current, modular, and future warfare concepts. The contractor shall use scenarios containing multiple potential logistical lines of investigation spanning the range of military operations to develop scenario dilemmas at the strategic, operational, and tactical levels of conflict, throughout the joint phases of operation examining Army and Joint concepts and ideas. The contractor shall also coordinate functional and senior participants, as well as support the building of experimentation plans for the MSBL led and supported experimental venues and other analytical events as tasked by United States Army Training and Doctrine Command (TRADOC).
1.2 Hours of Operation: The normal projected hours of operation are 0800 to 1700 over a standard five-day work period, excluding Federal holidays. However, these operation hours and days may vary based on mission requirements. The contractor shall be encouraged to use flexible work schedules to adjust for a five-day work period to meet manpower requirements for extended duty period during events and experiments as required. A mix of required hours to meet the mission shall not exceed eighty hours in a two week period. The Government will not authorize overtime.
1.3 Place of Performance: Fort Leonard Wood, MO.
PART 2 ACRONYMS AND REVELANT PUBLICATIONS
2. ACRONYMS and PUBLICATIONS
2.1. ACRONYMS
| AR | Army Regulation | |
| ARCIC | ARmy Capabilities and Integration Center | |
| AT | Anti-Terrorism | |
| ATCTS | Army Training Certification Tracking System | |
| CAC | Common Access Card | |
| COR | Contracting Officer Representative | |
| CMRA | Contractor Manpower Reporting Application | |
| DA | Department of the Army | |
| DD254 | Department of Defense Contract Security Requirement List | |
| DEERS | Defense Enrollment Eligibility Reporting System | |
| DES | Directorate of Emergency Services | |
| DFARS | Defense Federal Acquisition Regulation Supplement | |
| DOD | Department of Defense | |
| FAR | Federal Acquisition Regulation | |
| FBI | Federal Bureau of Investigation | |
| FLW | Fort Leonard Wood | |
| FPCON | Force Protection CONdition | |
| FSO | Facility Security Officer | |
| FY | Fiscal Year | |
| GFI | Government Furnished Information | |
| GFP | Government Furnished Property | |
| HQDA | Headquarters Department of the Army | |
| IAW | In Accordance With | |
| IA | Information Assurance | |
| IT | Information Technology | |
| IPR | In Progress Review | |
| KO | Contracting Officer | |
| LAN | Local Area Network | |
| MSBL | Maneuver Support Battle Lab | |
| MSCOE | Maneuver Support Center of Excellence | |
| MSSPIX | Maneuver Support, Sustainment and Protection Integrating Experiment | |
| NACI | National Agency Check with Inquiries | |
| NEC | Network Enterprise Center | |
| NLT | No Later Than | |
| OCONUS | Outside Continental United States (includes Alaska and Hawaii) | |
| OPSEC | Operations Security | |
| POP | Period of Performance | |
| PRS | Performance Requirements Summary | |
| PWS | Performance Work Statement | |
| QA | Quality Assurance | |
| QC | Quality Control | |
| RAPIDS | Real-time Automated Personnel IDentification System | |
| STRACD | Science, Technology, Research and Accelerated Capabilities Division | |
| TA | Trusted Associate | |
| TASS | Trusted Associate Sponsorship System | |
| TE | Technical Exhibit | |
| TCO | Telephone Control Officer | |
| TRADOC | TRaining And DOctrine Command |
2.2 Applicable Publications (Current Editions):
| No. |
| Title |
| DATE |
TP 525-3-5
| The U.S. Army Functional Concept for Maneuver Support 2020-2040 |
| Feb 2017 |
| Maneuver Support Battle Lab Experiment/Study Standard Operating Procedure |
| April 2017 |
2.2.1 Contractor shall comply with all of the applicable regulations, publications, manuals, local policies and procedures listed in the table above.
PART 3 DELIVERABLES/TASKS
3. Specific Deliverables: Contractor shall provide the analytical and technical support to the MSBL for planning, coordinating and execution the Maneuver Support, Sustainment and Protection Integrating Experiment (MSSPIX), which takes place annually in April. This will include research, coordination with other government organizations, logistics and report writing.
1.1. Experiment Plan for MSSPIX. Contractor shall write the experiment plan for MSSPIX incorporating the MSCoE approved experiment objectives. The Experiment Plan shall be written in compliance with the MSBL Experimentation SOP template and contain, at a minimum, the experiment purpose, objectives, experiment design, experiment analysis, and logistics. The Experiment Plan contains the experiment analysis plan and data collection management plan.
1.2. Initial Insights for MSSPIX. Contractor shall write and prepare initial observations and insights based upon the analysis collected and analyzed during the experiment.
1.3. Final Report for MSSPIX. Contractor shall write the final experiment report for MSSPIX in accordance with the MSBL Experimentation SOP template and contain, at a minimum, an executive summary, experiment purpose, objective, experimental design, collected data, analysis, insights and conclusions.
1.4. Kick Off Meeting. Contractor shall attend, in person, a kick-off meeting with Government to discuss the scope of work and receive and sign for any GFI. All GFI/GFP provided by the Government will remain the property of the US Government at the end of the contract at which time all GFI/GFP shall be returned to the COR in fully serviceable condition. The meeting date shall occur not later than 7 days after Contract award, and shall be scheduled by the COR. Contractor shall provide minutes of this meeting within 5 (five) calendar days of the date of the meeting.
1.5. In-Progress Review (IPR). Not applicable.
1.6. Monthly Status Reports. Contractor shall provide a status report no later than 3 (three) calendar days following the final day of the month. This status report shall capture workload completed, workload in progress and any outstanding issues that need to be resolved.
1.7. Final Report Summary. Contractor shall submit a final report summary of all activities performed by Contractor in support of this Contract to the COR. It shall include a summary of all deliverables completed. The Final Report Summary report shall be due on the last day of period of performance.
1.8. General acceptance criteria and quality measures: Contractor shall submit deliverables as set forth below to each deliverable and other work products received from Contractor under this PWS. Reports shall be prepared in a generally accepted business format, Microsoft Word®, and submitted electronically to the COR
1.8.1. Accuracy – All deliverables shall be accurate in presentation, technical content, and adherence to accepted elements of style.
1.8.2. Clarity – All deliverables shall be concise and clear at every level of distribution containing no spelling or grammatical errors. Any and all diagrams shall be easy to understand and be relevant to the supporting narrative.
1.8.3. File Editing – All text and diagrammatic files shall be editable by Government.
1.8.4. Format – Deliverables shall be submitted as specified in the PWS.
1.8.5. Timeliness – Deliverables shall be submitted on or before the due date specified in this PWS.
TECHNICAL EXHIBIT (TE) 1 – DELIVERABLES SCHEDULE:
| DELIVERABLE |
| DATE DUE OR FREQUENCY |
SECTION
| Experiment Plan |
| NLT 60 days after contract award |
| 3.1 |
| Initial Insights |
| NLT 45 days after experiment conclusion |
| 3.2 |
| Final Experiment Report |
| NLT 90 days after experiment conclusion or 5 days prior to the last day of period of performance, whichever is first |
| 3.3 |
| Kick off Meeting. |
| NLT 7 days after contract award |
3.4
| Monthly Status Reports. |
| NLT 3rd day after the final day of the month |
| 3.6 |
| Final Report Summary. |
| NLT 6 days prior to the last day of the period of performance |
| 3.7 |
TRAVEL:
| Destination |
| No. of |
People No. of Trips No. of Days No. of Nights
| Fort Sill, OK |
| 1 |
| 1 |
| 5 |
| 4 |
| Fort Benning, GA |
| 1 |
| 1 |
| 5 |
| 4 |
| Fort Lee, VA |
| 1 |
| 1 |
| 5 |
| 4 |
3.8 OCONUS Travel: Not applicable.
3.9 Contractor Travel. Contractor personnel may be required to perform travel to locations within the Continental United States (CONUS) to carry out the requirements of this PWS. Travel projections are provided in the table below.
NOTE: These travel projections are provided as a planning tool to assist the contractor in proposal preparation. CONUS travel locations are not limited to those listed above; however, any increase to the quantities listed above shall be accomplished through a contract modification. The Federal Travel Regulation is available at http://www.gsa.gov/FTR.
PART 4 ADMINSTRATIVE TASKS
4. ADMINISTRATIVE TASKS: The below tasks will outline the administrative functions the Contractor will need to follow.
4.1 Qualifications/Licenses: none required.
4.2 Kick Off /Periodic Progress Meetings: Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The KO, COR, and other Government personnel, as appropriate, may meet periodically with Contractor to review Contractor's performance. At these meetings the KO will apprise Contractor of how Government views Contractor's performance and Contractor will apprise 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 Government.
4.3 Quality Control (QC): Not required.
4.4 Contractor Manpower Reporting Application (CMRA): Contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) via a secure data collection site. Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contracted services. Reporting inputs will be for the labor executed during the POP for each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported NLT October 31 of each calendar year. Contractors may direct questions to the help desk by clicking on “send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMRA website.
4.5 PHASE IN /PHASE OUT PERIOD. Not required.
PART 5 SECURITY/ACCESS
5. SECURITY/ACCESS
5.1 Required Security Clearance Requirements: Contractor (and subcontractor) personnel performing work under this contract must have a SECRET, and must maintain the level of security required for the life of the contract. The security requirements are IAW the attached DD254.
5.2 Physical Security: 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.
5.3 Key Control. Not applicable.
5.4 Antiterrorism (AT) Level I Training: All contractor/subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date 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 and subcontractor employee, to the COR (or KO if no COR is appointed) within 45 calendar days after completion of training by all employees and subcontractor personnel. AT Level I Awareness Training (JS-US007-14: Level I Antiterrorism Awareness Training) is available at the following website: http://jko.jten.mil/. AT performance (Level I AT Awareness Training attendance and compliance) may be documented as a performance metric under this contract, and be part of past performance information in support of future source selections
5.5 iWatch Training. The contractor and all associated subcontractors are required to review the Fort Leonard Wood, Directorate of Emergency Services (DES) Web link on iWatch. This locally developed Web-linked training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity. Suspicious Activity will also be reported to the COR (or KO if no COR is appointed). This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR (or KO if no COR is appointed) NLT 30 calendar days after contract award. The following iWatch Web link is provided http://www.wood.army.mil/LEC/iWatch/iWatch.htm.
5.6 Information Assurance (IA) Awareness Training for Contractors Requiring Access to Information Systems: All Contractor and sub-contractor personnel requiring network access to Government information systems shall successfully complete DoD Cyber Awareness Challenge training available at https://ia.signal.army.mil/ prior to accessing systems and annually thereafter. Training certificates shall be provided to the COR immediately upon completion. Contractor employees shall register in the Army Training Certification Tracking System (ATCTS) prior to commencement of work and shall sign the acceptable use policy IAW AR 25-2, Para. 3-3. The COR or KO will coordinate with the requiring activity Information Assurance Support Officer to input the DoD Cyber Awareness Challenge Training certificate and training information into the ATCTS and verify compliance.
5.7 Information Assurance/Information Technology (IT) Support Functions Certification. Not applicable.
5.8 The OPSEC (Operations Security) Plan and User Agreement: The OPSEC Plan and User Agreement will be available for Contractors to review at the Contracting Office located in Building 11400, FLW, MO, from the hours of 0730 to 1600. The COR will ensure Contractor is aware of the Installation’s OPSEC Plan and is in compliance with the Installation’s OPSEC Plan during contract performance.
5.9 OPSEC Training: Pursuant to AR 530-1, all Contractor personnel must complete initial Level I OPSEC training within 30 calendar days beginning performance on this contract. For contracts that cross fiscal years, or for contracts with option years, all contractor personnel shall complete annual OPSEC awareness training. The MSCoE OPSEC Officer will provide training. Contact information for this Government employee will be provided at the kick-off meeting. The MSCoE OPSEC Officer will provide a one hour training session conducted on FLW for Contractor personnel working on this installation. The COR will coordinate this training at the time of award. Contractor shall provide a list of personnel trained to the COR within five (5) calendar days of completion of training. Contractor personnel working at installations other than FLW shall coordinate with the COR and local OPSEC Offices to obtain training applicable to that installation.
5.10 Accompany Forces: Not applicable.
5.11 Performance or delivery in a foreign country. Not applicable.
5.12 Contractor access to the FLW Local Area Network (LAN): Contractor personnel shall obtain Common Access Cards (CAC), be registered in the Army Training Certification Tracking System (ATCTS) by a Government representative, and complete Information Assurance (IA)Training before being permitted to access the FLW LAN. For contracts crossing fiscal years, or those awarded with option periods, IA training shall be accomplished annually for all Contractor personnel. Access to the LAN is required in order to review key instruction materials necessary for performance of work. Contractor personnel shall not connect personal devices or Contractor / commercially provided equipment to the FLW network without first receiving written permission from the FLW Network Enterprise Center (NEC). Devices, such as desktop or laptop computers which are Contractor furnished, must be loaded with operating system and application software to standards defined by the FLW NEC prior to connection. The NEC must install and configure such devices prior to being operated on the network. All devices connected to the network will be managed under strict Information Assurance standards as prescribed by Army Regulation (AR) 25-2. The NEC retains sole administrator authority over devices connected to the network. Access to network resources are granted on a least-needed basis, therefore only minimal services will be provided to Contractor personnel unless explicitly granted through this PWS. Common services include physical connectivity, user-id and use of shared services related to work (printers, shared files, and public folders). Limited Internet access may be provided based on specific tasks identified in this PWS which indicates communication with Internet based hosts is a requirement to successfully execute the Contract. Contractor is subject to all access policies, particularly the Acceptable Use Agreement and AR 25-2. Contractor shall not load any software or make any changes to computer configurations. All requests for changes or problem reports must be submitted to the NEC through the work order process. Department of Defense (DoD) computer systems, including Contractor furnished devices connected to the FLW LAN, may be monitored for all lawful purposes. Contractor’s use of the DoD computer systems, authorized or unauthorized, constitutes consent to monitoring.
5.13 Contractor Access and Use of FLW Telephones and Telephone Services: Telephones and telephone basic service, including local and long distance, shall only be used for official Government purposes. Contractor is subject to AR 25-2 which established policies on telephone and Automated Information System use. Contractor shall not move, unplug or alter any telephone or voice device. Unique devices, such as speaker phones, cordless or conference phones, shall be requested through a Government Telephone Control Officer (TCO) work order at the expense of Contractor. All requests for changes or problem reports must be submitted to the NEC through the unit TCO who will be identified at the kick-off meeting. DoD telephones may be monitored for all lawful purposes. Contractor’s use of the DoD telephones, authorized or unauthorized, constitutes consent to monitoring.
5.14 For contractors requiring 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 favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.
Trusted Associate Sponsorship System (TASS): Contractor User Guide and other information see http://www.cac.mil/common-access-card/getting-your-cac/for-contractors/
Contractor must obtain a CAC for those Contractor employees whose functions require access to systems or facilities controlled by the CAC. To mitigate the risk of the contractor being misidentified as a Government Civilian, the Government will ensure all contractors wear badges identifying them as contractors, all emails will contain "CTR" after their names to identify them as contractors and when they answer telephones they will immediately identify themselves as “contractors”.
Contractor Representative shall notify TASS Trusted Agent (TA) (the TA is the COR) of new employee CAC requirements. Company Representative shall provide all personnel data required to process TASS application with the TA, including security investigation requirements.
Contractor employee(s) shall obtain their CAC at defense enrollment eligibility reporting system (DEERS) / real-time automated personnel identification system (RAPIDS) terminals when application is approved.
Contractor employee(s) shall inform Corporate Facility Security Officer (FSO)/Security Manager of approval/denial of CAC application, and shall return CAC to Corporate FSO upon departure or dismissal. Contractor shall be responsible for implementation and follow-up of this requirement.
Failure, inability or delay in obtaining the CAC does not relieve Contractor from performing under the terms of this Contract.
Contractor shall ensure all CACs issues to Contractor personnel are returned to the COR upon termination or completion of this Contract.
5.15 Access and General Protection/Security Policy and Procedures. Contractor and all associated sub-contractor employees shall comply with applicable installation, facility and area commander, installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Directorate of Emergency Services or Security Office. The requesting contractor will submit their request for an installation pass to their sponsor using the following link: https://vcc1.icmvcc.com/im3500/. A valid sponsor may be either the COR, COTR, or KO if neither is appointed. Contractor workforce must comply with all personal identity verification requirements 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.
STAND ALONE DOCUMENTS (not to be included in PWS):
GOVERNMENT FURNISHED PROPERTY:
Facilities: Government will provide the necessary workspace for Contractor staff to provide the support outlined in the PWS to include desk space, telephone, and other items necessary to maintain an office environment in Bldg 3201, Lincoln Hall 3691, MSBL Office.
Equipment: Government will provide Contractor with access to a computer, monitor, scanner, fax machine, printer, sound, desk phone, etc. All Government equipment shall be inspected by Contractor prior to signing for, and again before being turned back in to Government. Contractor shall inform Government of any deficiencies in the equipment upon its return. IAW AR 25-2, only GFP will be used on installation networks, unless expressly approved by NEC. Contractor shall operate and utilize all GFP in strict compliance with the GFP equipment technical manuals and manufacturer’s instructions that are available for Contractor use. All GFP shall be used only in the performance of these PWS requirements. Liability for GFP while in the control of Contractor shall be IAW FAR Clause 52.245-1.
Materials: The Government will provide the Contractor with access to research, studies, briefings, previous experimentation reports and other materials on programs related to military combat development processes and experimentation applicable to the period 2000-2040. These materials may be up to the SECRET classification level.
| No. |
| Title |
| DATE |
| Maneuver Support Battle Lab Experimentation SOP |
| April 2017 |
TECHNICAL EXHIBIT 1 PERFORMANCE REQUIREMENTS SUMMARY
Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.
Performance Objective
| Standard |
| Acceptable Quality Level (AQL) |
| Method of Surveillance |
PRS # 1.
Contractor shall provide an Experimentation Plan (PWS 3.1)
| Contractor provided report NLT 60 days after contract award via hardcopy and MS Word file. |
| No more than one customer complaint per report. |
| 100% Inspection |
PRS # 2
Contractor shall provide an Initial Insights Report (PWS 3.2)
| Contractor provided report NLT 45 days after experimentation conclusion via hardcopy and MS Word file. |
| No more than one customer complaint per report. |
| 100% Inspection |
PRS # 3
Contractor shall provide a Final Experimentation Report (PWS 3.3)
| Contractor provided report NLT 90 days after experiment conclusion or 5 days prior to the last day of performance, whichever is first, via hardcopy and MS Word file. |
| No more than one customer complaint per report. |
| 100% Inspection |
PRS # 4
Contractor shall provide a Final Summary Report (PWS 3.7)
| Contractor provided report NLT 5 days prior to the last day of performance via hardcopy and MS Word file. |
| No more than one customer complaint per report. |
| 100% Inspection |
File details come from the government source that posted it.