Final_PWS.pdf

Performance Work Statement Warfighting and Lessons Learned Forums

AMO 18-55

Part 1 GENERAL INFORMATION

1. GENERAL: This Performance Work Statement (PWS) describes the administrative, research, analysis and technical performance requirements for Army Forums to include, but not limited to, Army Lessons Learned Forum (ALLF) Action Officer Working Groups (AOWG), Councils of Colonels (CoC), and General Officer Steering Committees (GOSC); and Warfighting Forum (WfF) Senior Mentor Symposium (SMS) support to the Maneuver Support Center of Excellence (MSCoE). This is a non-personal services contract. Consistent with Federal Acquisition Regulation (FAR) 37.104 guidance, the Government shall not exercise supervision or control over contractor personnel. Contractor personnel are accountable solely to Contractor, who in turn is responsible to the Government.

1.1 Background: The ALLF is an on-going 4-star level collaboration and coordination process outlined in Army Regulation (AR) 11-33, Army Lessons Learned Program (ALLP), which requires engaged proponent participation. The ALLF is led by the Combined Arms Center (CAC) Commander. The ALLF provides a venue where Army senior leaders can collaborate to rapidly address Army Command (ACOM), Army Service Component Command (ASCC), and theater commander issues concerning operations, training and resouces, and assign resolution action to appropriate agencies. It also provides a means for other venues such as the brigade combat team WfFs and other like bodies to elevate issues for senior level decisions. The intent of the ALLF is to provide a rapid Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P) issue resolution/response process as well as actioning critical issues requiring collaborative lead/support relationships across multiple Centers’ of Excellence (CoE)/schools. The battle rhythm includes weekly AOWGs, monthly CoCs, and quarterly GOSCs.

Figure 1. The Army Lessons Learned Forum (ALLF) Process

The intent of the WfFs is to engage the maneuver support community of interest (CoI) in order to advance center and school equities, and effect near term synchronization efforts along the domains of DOTMLPF-P with I Corps, III Corps, and XVIII Airborne Corps Commanders’ and staff. The WfF program capitalizes upon the senior mentor roles performed by Corps and CoE commanders who integrate the functions of the WfF into refined staff organizations, internal battle rhythms, and routine interactive sessions with subordinate commanders world-wide. Senior MSCoE and proponent school leader participation is necessary in each of these events to promote collaboration, share ideas, and find solutions to common problems. The battle rhythm includes quarterly SMS meetings for each WfF.

1.2 Hours of Operation: Contractor shall conductbusiness, Monday through Friday, 0730 – 1600, except for Federal holidays and occasional training holidays, or when Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Contractor shallat all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when Government facility is not closed for the above reasons. When hiring personnel, contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.3 Place of Performance: Contractor shall perform all work at MSCoE, 14000 MSCoE Loop, Building 3200, Fort Leonard Wood (FLW), MO.

1.4 Recognized Holidays: Government observes the following holidays:

New Year’s Days Martin Luther King Jr.’s Birthday President’s Day Memorial Day Independence Day Labor Day Columbus Day Veteran’s Day Thanksgiving Day Christmas Day Federal Employee Holidays as authorized by the President of the United States

PART 2 ACRONYMS AND REVELANT PUBLICATIONS

2. ACRONYMS and PUBLICATIONS:

2.1. ACRONYMS

AAR After Action Report AAR After Action Review ACOM Army Command AKO Army Knowledge Online ALLF Army Lessons Learned Forum ALLP Army Lessons Learned Program AOWG Action Officer Working Group AR Army Regulation ArCAT Army Capability Assessment Tool ASCC Army Service Component Commands AT Antiterrorism ATCTS Army Training Certification Tracking System CAC Combined Arms Center CAC Common Access Card CALL Center for Army Lessons Learned CBRN Chemical, Biological, Radiological, and Nuclear CMRA Contractor Manpower Reporting Application CoA Course of Action CoC Council of Colonels CoE Center of Excellence CoI Community of Interest CONUS Continental United States COR Contracting Officer Representative COTR Contracting Officer’s Technical Representative DCS Defense Collaboration System DD254 Department of Defense Contract Security Classification Specification DEERS Defense Enrollment Eligibility Reporting System DES Director of Emergency Services DFARS Defense Federal Acquisition Regulation Supplement DoD Department of Defense DoDD Department of Defense Directive DOTMLPF-P Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy EN Engineer EXSUM Executive Summary FAR Federal Acquisition Regulation FBI Federal Bureau of Investigation FLW Fort Leonard Wood FOUO For Official Use Only FPCON Force Protection Security FRAGO Fragmentary Order FSO Facility Security Officer FTR Federal Travel Regulation FY Fiscal Year GFI Government Furnished Information GFP Government Furnished Property GOSC General Officer Steering Committee HQDA Headquarters Department of the Army IA Information Assurance IAW In Accordance With IPR In Progress Review IT Information Technology

JCIDS Joint Capabilities Integration and Development System JLLIS Joint Lessons Learned Information System KO Contracting Officer LAN Local Area Network LOE Line of Effort MIMC MSCoE Integrated Master Calendar MP Military Police MS Maneuver Support MS Microsoft® MSCoE Maneuver Support Center of Excellence MSEC Maneuver Support Enterprise Calendar MSR Monthly Status Report NACI National Agency Check with Inquiries NDCS Non-Secure Defense Collaboration System NEC Network Enterprise Center NIPR Non-Secure Internet Protocol Router NLT No Later Than OPORD Operation Order OPSEC Operations Security PMID Program Management and Integration Directorate POP Period of Performance POC Point of Contact PWS Performance Work Statement QC Quality Control QCP Quality Control Program RAPIDS Real-Time Automated Personnel Identification System SDCS Secure Defense Collaboration System SIGACTS Significant Activities SIPR Secure Internet Protocol Router SITREP Situation Report SMS Senior Mentor Symposium SVTC Secure Video Teleconference TA Trusted Agent TASS Trusted Associate Sponsorship System TE Technical Exhibit TCO Telephone Control Officer TRADOC Training and Doctrine Command VTC Video Teleconference WfF Warfighting Forum

2.2 Applicable Publications (Current Editions)

No. Title DATE Army Campaign Plan TRADOC Campaign Plan Maneuver Support Center of Excellence Campaign Plan 8 Feb 2016 Federal Acquisition Regulation, 37.104, found at http://www.acq.osd.mil/dpap/dars

Defense Federal Acquisition Regulation Policies, Procedures and Specifications, found at http://www.acq.osd.mil/dpap/dars/about_dfarspgi.html

AR 5-1 Management of Business Operations, found at http://www.apd.army.mil

12 Nov 2015

AR 11-33 Army Lessons Learned Program (ALLP), found at http://www.apd.army.mil

14 Jun 2017

AR 25-1 Army Information Technology, found at http://www.apd.army.mil

15 Jul 2005

AR 25-2 Information Assurance, found at http://www.apd.army.mil 24 Oct 2007

AR 25-50 Preparing and Managing Correspondence, found at http://www.apd.army.mil

17 May 2013

AR 190-13 The Army Physical Security Program, found at http://www.apd.army.mil

25 Feb 2011

AR 190-16 Physical Security, found at http://www.apd.army.mil 31 May 1991 AR 340-21 The Army Privacy Program, found at http://www.apd.army.mil AR 380-5 Department of the Army Information Security Program, found at http://www.apd.army.mil 29 Sep 2000

AR 380-40 Safeguarding and Controlling Communications Security Material, found at http://www.apd.army.mil

9 Jul 2012

AR 380-53 Communications Security Monitoring, found at http://www.apd.army.mil

23 Dec 2011

AR 380-67 Personnel Security Program, found at http://www.apd.army.mil

24 Jan 2014

AR 420-1 Army Facilities Management, found at http://www.apd.army.mil

12 Feb 2008

AR 530-1 Operations Security (OPSEC) , found at http://www.apd.army.mil

26 Sep 2014

ADP 5-0 The Operation Process, found at http://www.apd.army.mil 17 May 2012 TC 25-20 A Leader’s Guide to After-Action Reviews Sep 1993 TR 1-11 Staff Procedures, found at http://www.tradoc.army.mil/tpubs/regndx.htm 26 Aug 2015

TR 350-70 Army Learning Policy and Systems, http://www.tradoc.army.mil/tpubs/regs/TR350-70.doc

10 Dec 2012

JP 1-02 DoD Dictionary of Military and Associated Terms, As Amended through 15 June 2015 http://www.dtic.mil/doctrine/new_pubs/jointpub_reference.htm

15 Jun 2015

Antiterrorism (AT) Level I Training found at http://jko.jten.mil/ iWatch Training found at http://wood.army.mil/LEC/iWatch/iWatch.htm

DoD Cyber Awareness Challenge Training found at https://ia.signal.army.mil/

Operation Security (OPSEC) Training

2.2.1 Contractor (to include subcontractors) shall comply with applicable DOD, Army, TRADOC, and local policies and procedures in effect at the time of award and as otherwise issued/modified during the period of performance (POP). These include, but are not limited to all of the applicable regulations, publications, manuals, local policies, and procedures listed in the table above or identified as the Contract progresses.

PART 3 DELIVERABLES/TASKS

3.0 Specific Deliverables: Contractor shall conduct research, provide written analysis and assessment, synthesize information, provide supporting documents/products, draft briefings, make recommendations, and deliver completed staff work in support of MSCoE’s mission to integrate Maneuver Support (MS); Military Police (MP); Engineer (EN); Chemical, Biological, Radiological and Nuclear (CBRN); and Protection considerations across WfF. Contractor shall attend Army Forums (WfF SMS; ALLF, AOWGs, CoCs, and GOSCs) as identified by the Contracting Officer Representative (COR) by e-mail. Venues for these forums/events include but are not limited to Secure Internet Protocol Router (SIPR) Secure Video Teleconferences (SVTC), Secure Defense Collaboration Services (SDCS), or Non-Secure Internet Protocol Router (NIPR) DCS (NDCS) facilities. After the events, Contractor shall write Executive Summaries (EXSUM) to include any MSCoE or school taskers and provide to the COR for acceptance and distribution to the CoI.

All written documents will meet criteria provided in paragraph 3.16. Assessments, analysis, reports, presentations, etc., shall be prepared in Microsoft (MS) Word®, Microsoft PowerPoint®, Microsoft Excel®, shall follow AR 25-50 (Preparing and Managing Army Correspondence) and U.S. Army Training and Doctrine Command (TRADOC) Regulation 1-11, (Staff Procedures) standards. Contractor shall submit all documents electronically to the COR ready for Army senior executive level presentation.

In no event shall Contractor act or hold himself out as representing the Government or any instrumentality thereof as an agent. Furthermore, Contractor shall not speak on behalf of or otherwise perform inherently governmental functions. Contractor shall serve as an integrator between I CORPS, III CORPS, XVIII CORPS, CAC, Center for Army Lessons Learned (CALL), TRADOC CoEs/schools and staff. Contractor shall include a status of each deliverable in the bi-weekly Significant Activities (SIGACTS) report (paragraph 3.10).

3.1. Research and Analysis. Contractor shall research general issues, gaps, best practices, and potential gap solutions for forum topic areas with MSCoE equities. Contractor shall identify, analyze, and characterize critical shoot, move, and communicate capability gaps that hinder the ability of Army maneuver support forces to operate effectively or enable maneuver forces. Contractor shall provide analytical summaries of Community of Practice (CoP) products, to include presentations, studies, after action reports (AAR), DOTMLPF assessments, warfighting capability assessments, risk assessments, gap analysis, testing plans, procurement plans, fielding plans, concept of operations, concept of employment, and campaign plans.

Contractor shall further provide information papers, point papers, white papers, briefing slides, oral presentations/briefings, staff studies, Courses of Action (CoA), and recommendations to inform and educate school/center leadership and to support the integration of MSCoE equities. Contractor shall conduct research on both NIPR and SIPR sites, CoP dialogue, and by attending the ALLF battle rhythm events and quarterly WfFs.

3.1.1. Community of Practice (CoP) Engagement. Contractor shall engage CoP points of contact (POC) for MSCoE MS, MP, EN, CBRN, and Protection at Army, Corps, Division, CoEs, and TRADOC schools to research general issues, gaps, best practices, and potential gap solutions for forum topic areas with MSCoE equities as identified by the COR by e-mail. Contractor shall provide analytical summaries, findings and recommendations in the appropriate written format (EXSUM, SIGACT, information paper, point paper, white paper, or briefing slides) to support the integration of MSCoE equities no later than (NLT) two working days after identification. The Government’s estimated time, that the contractor may spend on engagement, is identified in the Technical Exhibit.

3.1.2. Datamining. Contractor shall conduct research on both NIPR and SIPR sites through review of Army Capabilities Assessment Tool (ArCAT), MilSuite forums, Joint Lessons Learned Information System (JLLIS), Capability Needs Analysis database, Joint Capabilities Integration and Development System (JCIDS), Army Knowledge Online (AKO), professional discussion boards, and other enterprise systems. Contractor shall also visit the associated websites and portals for the Infantry, Armor, and STRYKER WfFs to maintain currency in CoP discussion threads, assess emergent Battalion, Brigade, and Division warfighting issues and concerns, and identify areas where MSCoE MS, MP, EN, CBRN, and Protection capabilities can support problem solving efforts and/or contribute to collaborative solution setsContractor shall provide analytical summaries, findings and recommendations in the appropriate written format (EXSUM, SIGACT, information paper, point paper, white paper,or briefing slides) to support the integration of MSCoE equities NLT two working days after identification. The Government’s estimated time, that the contractor may spend on datamining, is identified in the Technical Exhibit.

3.1.3. Warfighting Needs (WfN) Analysis. Contractor shall identify and analyze immediate (Fight Tonight), emerging, mid-range (Fight Tomorrow), and long-range (Fight in the Future) WfNs of Soldiers and organizations to ensure that our combined arms formations possess the mobility, firepower, and protection to meet mission requirements, assure survivability, reduce vulnerability, and improve readiness. Contractor shall prepare, and provide to the COR, findings and recommendations in the appropriate written format (EXSUM, SIGACT, information paper, point paper, white paper, or briefing slides) for solutions NLT two (2) working days after identification.

3.1.4. Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities and Policy (DOTMLPF-P) Analysis. Contractor shall participate in efforts to find solutions that eliminate or mitigate survivability and vulnerability gaps through identification, evaluation, integration, and assessment of candidate solutions from across the DOTMLPF-P domains. Contractor shall prepare, and provide to the COR, an abbreviated DOTMLPF-P analysis with the findings and recommendations for solutions NLT two (2) working days after identification.

3.2. Kick-Off Meeting and EXSUM. Contractor shall schedule a kick-off meeting with the COR, at no additional cost to Government, to discuss the scope of work and receive Government Furnished Information/Government Furnished Property (GFI/GFP). The meeting date shall occur NLT five (5) working days after first day of POP. Contractor shall provide minutes of this meeting NLT two (2) working days after the date of the meeting. Minutes shall be prepared in Microsoft Word® and submitted electronically to the

COR.

3.3. Operations Order (OPORD) and Fragmentary Orders (FRAGO). Contractor shall prepare a Forums OPORD NLT 10 working days after first day of POP, for base and exercised option years, that designates Forum mission, assigned responsibilities, battle rhythms, and other key events. Contractor shall prepare FRAGOs as required NLT two (2) working days after battle rhythm changes/updates, but no less than once per quarter.

3.4. Calendars. Contractor shall ensure Forums and other significant event dates are added and maintained in the Base Training Guidance, placed on the MSCoE Integrated Master Calendar (MIMC)/Maneuver Support Enterprise Calendar (MSEC), and entered in the MSCoE Weekly FRAGO NLT two (2) working days of meeting invitation/notification and as identified by the COR by e-mail.

3.5. Forum/Meeting Attendance. Contractor shall attend all quarterly ALLF battle rhythm events and quarterly WfF SMS. The ALLF holds four quarterly GOSC cycles per year. Typically each cycle consists of five AOWGs, three CoCs, one Quarterly Program Review (QPR), one or two Stakeholder Meetings (SHM), and one GOSC. Each WfF SMS (Stryker, Infantry, and Armor) hold four meetings per year. Contractor shall distribute electronically and share online read-ahead slides and other forum related documents to the CoI NLT one (1) day after receipt of POC correspondence and COR approval to distribute.

3.6. Meeting Minutes and Executive Summaries (EXSUM). Contractor shall attend governance, management, project-related meetings, workgroups, briefings and discussions as identified by the COR, and provide notes, minutes, information papers, decision papers, EXSUMs, and supporting documents to the COR NLT two (2) working days after each meeting or event. Contractor prepared post meeting minutes (Technical Exhibit 2) and EXSUMs (Technical Exhibit 3) shall be provided to the COR NLT two (2) working days after the conclusion of each meeting. The minutes and EXSUMs serve as documentation of highlights, take-aways, and action items, and an overall synopsis of the each meetings discussion. The minutes shall include, at a minimum, an executive summary, objectives, and any resulting issues, resolutions or outcomes, and due-outs for MSCoE entities. The COR will accept or return documents NLT two (2) working days after receipt as final or return with questions or request for clarification of information or issues. Contractor shall edit, update and produce final reports, minutes, information papers, EXSUMs, and other management documents within two (2) working days of receiving the approved draft from the COR. Post meeting records and EXSUMs are not required for administrative meetings.

3.7. Situation Reports (SITREP).

3.7.1. Contractor shall prepare an initial SITREP, for COR approval, NLT 30 days prior to each GOSC cycle that identifies MSCoE MS, MP, EN, CBRN, and Protection equities based on research findings and relevancy for current and future Forum topics or areas of interest.

3.7.2. Contractor shall prepare a second SITREP NLT 15 days prior to the CoCs that identifies MSCoE MS, MP, EN, CBRN, and Protection equities for the current cycle and proposed topics for the following cycle.

Contractor shall also include a list of recommended organizations/participants to attend the CoC for COR approval.

3.7.3. Contractor shall prepare a third SITREP seven (7) days prior to the GOSC that identifies MSCoE MS, MP, EN, CBRN, and Protection equities for the current cycle, proposed topics for the following cycle, and draft talking points for the GOSC Senior Representative. Contractor shall also include a list of recommended organizations/participants to attend the GOSC for COR approval.

3.8. Read-Ahead Packet. Contractor shall prepare a read-ahead packet NLT three (3) working days prior to the GOSC pre-brief that includes MSCoE Staffing Paper (FLW Form 1416) with a synopsis of current and future operations in the following categories: (1) Immediate (Fight Tonight); (2) Emerging; (3) Mid-range (Fight Tomorrow); (4) Long- range (Fight in the Future), most current available slides, and talking points.

3.9. General Officer Correspondence/Aides.

3.9.1. Contractor shall provide draft talking points for the GOSC Senior Representative NLT five (5) working days prior to the GOSC prebrief for COR approval. The talking points shall be prepared using short bullets, include an introduction and conclusion, provide the bottom line upfront, and include facts and assumptions.

Talking points will be returned to the Contractor as approved or for correction within one (1) working day from the COR. Final talking points will be included in the Read-Ahead Packet.

3.9.2. Contractor shall prepare formal and informal memorandums, endorsements, letters, fact sheets, and other designated written products to address Forum leaders, Lines of Effort (LoE) leads, participants, etc. NLT two (2) working days after COR notification,

3.10. Significant Activities (SIGACTS) Report. Contractor shall submit SIGACTS input via e-mail to the COR NLT noon bi-weekly on Wednesdays throughout the duration of this contract. SIGACTS shall include events, taskings, functions, etc. that impact MSCoE MS, MP, EN, CBRN, and Protection. SIGACTS shall be submitted in the format at Technical Exhibit 4.

3.11. In-Progress Reviews (IPR). Contractor shall schedule IPRs with the COR at no additional cost to the Government. The meeting dates shall be scheduled within the first five (5) calendar days of each month and shall be conducted via teleconference, video-teleconference (VTC), or face-to-face at MSCoE, 14000 MSCoE Loop, Building 3200, Suite 236, Room 210. Contractor shall provide minutes of each meeting NLT two (2) working days after the date of the meeting. Minutes shall be prepared in a generally accepted business format, Microsoft Word®, and submitted electronically to the COR.

3.12. After Action Review (AAR)/After Action Report (AAR). Contractor shall schedule an informal AAR with the COR NLT two (2) working days after each GOSC cycle to retrospectively analyze the Forum processes regarding what happened, why it happened, and how it can be improved by participants and those responsible for the project/topic area. The Contractor shall provide a written AAR NLT two (2) working days after the review to the COR for approval.

3.13. Monthly Status Reports (MSR). Contractor shall provide a written status report NLT three (3) working days following the final day of each contract work month. This status report shall capture deliverables completed, workload in progress, and any outstanding issues that need to be resolved. The deliverables shall be reported associated with a Task number (Task 3.1.1 – Task 3.1.14) from this PWS. Reports shall be prepared in a generally accepted business format, Microsoft Word®, and submitted electronically to the COR.

3.14. Close-out Meeting and Final Report Summary. Contractor shall schedule a contract Close-Out meeting, at no additional cost to the Government, for the last working day of the contract to discuss the results of work completed throughout the entire contract (base and option years), and to turn-in GFI/GFP. Contractor shall submit a final report summary and analysis of activities performed in support of this contract to the COR. It shall include the results of all monthly status report deliverables, analyses, conclusions, and recommendations.

Report shall be completed in MS Word® using a generally accepted business format.

3.15. Security Requirements. Security requirements for the preceding tasks involve access to Sensitive, For Official Use Only (FOUO), and Secret information.

3.16. 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.

3.16.1. Accuracy – All deliverables shall be accurate in presentation, technical content, and adherence to accepted elements of style.

3.16.2. Clarity – All deliverables shall be concise and clear at every level of distribution. Any and all diagrams shall be easy to understand and be relevant to the supporting narrative.

3.16.3. File Editing – All text and diagrammatic files shall be editable by Government.

3.16.4. Format – Deliverables shall be submitted as specified in the PWS.

3.16.5. Timeliness – Deliverables shall be submitted on or before the due date specified in this PWS.

3.17. 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. In the event travel is required, Contractor shall provide a trip report to include Who traveled, What was the purpose, Where trip was located, When arrived & returned, Why the trip took place, How was the trip executed (if applicable); as well as identification of MSCoE and school equities and suspenses/follow-on work identified during the TDY, to the COR within five business days of the end of travel.Travel projections are provided in the table below.

Trip Purpose Number of Trips

Location(s) Number of Travelers

Duration

Annual Lessons Learned Workshop

5 CAC, Fort Leavenworth, KS One (1) One (1) Week

Routine Meeting Attendance

15 CAC, Fort Leavenworth, KS; ARCIC, Fort Eustis, VA; HQDA, G3/5/7, Washington, DC; MCoE, Fort Benning, GA; etc.

One (1) One (1) Week

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.

3.18 Deliverables Schedule. The COR is responsible for monitoring delivery due dates and times and is authorized to recommend deliverable schedule changes to the Contracting Officer (KO). Said changes if any, may affect the term of the Contract. The KO is the only one authorized to make changes to the terms of the Contract.

DELIVERABLE DATE DUE OR

FREQUENCY

SECTION

COMMUNITY OF PRACTICE (COP)

ENGAGEMENT

SEE TECHNICAL

EXHIBIT 3.0, 3.1, 3.1.1, 3.16

DATAMINING DATAMINING ON NIPR AND

SIPR SITES. SEE

TECHNICAL EXHIBIT

3.0, 3.1, 3.1.2, 3.16

WARFIGHTING NEEDS (WFN)

ANALYSIS

NLT 2 WORKING DAYS AFTER

NEEDS IDENTIFICATION

PROVIDE FINDINGS AND

RECOMMENDATIONS IN

WRITTEN FORMAT

3.0, 3.1, 3.1.1, 3.1.2, 3.1.3, 3.16

DOCTRINE, ORGANIZATION,

TRAINING, MATERIEL, LEADERSHIP

AND EDUCATION, PERSONNEL,,

FACILITIES AND POLICY (DOTMLPF-P)

ANALYSIS

NLT 2 WORKING DAYS AFTER

IDENTIFICATION OF

CANDIDATE SOLUTION

PROVIDE ABBREVIATED

DOTMLPF-P ANALYSIS

3.0, 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.16

KICK OFF MEETING AND EXSUM NLT 5 WORKING DAYS AFTER

FIRST DAY OF POP START

DATE; EXSUM NLT 2

WORKING DAYS AFTER THE

MEETING

3.0, 3.2, 3.16

OPERATIONS ORDER (OPORD) NLT 10 WORKING DAYS

AFTER FIRST DAY OF POP FOR

BASE YEAR EACH EXERCISED

OPTION YEAR

3.0, 3.1, 3.2, 3.3, 3. 4, 3.5, 3. 6, 3.7, 3.8, 3. 9, 3.10, 3. 11, 3.12, 3.13, 3.14, 3.15, 3.16

FRAGMENTARY ORDERS (FRAGO) AS REQUIRED NLT 2

WORKING DAYS AFTER

BATTLE RHYTHM

CHANGES/UPDATES; NO LESS

THAN ONCE PER QUARTER

3.0, 3.1, 3.2, 3.3, 3. 4, 3.5, 3. 6, 3.7, 3.8, 3. 9, 3.10, 3. 11, 3.12, 3.13, 3.14, 3.15, 3.16

CALENDARS EVENTS ADDED TO BASE

TRAINING GUIDANCE,

MIMC/MSEC, MSCOE WEEKLY

FRAGO NLT 2 WORKING

DAYS OF

INVITATION/NOTIFICATION

3.0, 3. 4, 3.16

FORUM MEETING ATTENDANCE ATTEND ALL ALLF BATTLE

RHYTHM EVENTS AND WFF

SMS (ALLF PER QTR = 5

AOWG, 3 COC, 1 QPR, 1-2

SHM, 1 GOSC) (WFF SMS PER

QTR = 1 EACH PER STRYKER,

INF, AND ARMOR); READ-

AHEAD SLIDE DISTRIBUTION

NLT 1 WORKING DAY AFTER

RECEIPT

3.0, 3.1, 3.5, 3.16

MEETING MINUTES AND EXSUMS NLT 2 WORKING DAYS AFTER

EACH MEETING OR EVENT

PROVIDE ALL SUPPORTING

DOCUMENTS TO COR;

CONTRACTOR PREPARED

POST MEETING MINUTES

PROVIDED NLT 2 WORKING

DAYS AFTER EACH MEETING;

FINAL DOCUMENT TO THE

COR NLT 2 WORKING DAYS

(MINUTES/ EXSUMS NOT

REQUIRED FOR

ADMINISTRATIVE

MEETINGS)

3.0, 3.6, 3.16

SITUATION REPORTS (SITREP) INITIAL SITREP NLT 30 DAYS

PRIOR TO EACH GOSC CYCLE;

SECOND SITREP NLT 15 DAYS

PRIOR TO COC; THIRD SITREP

NLT 7 DAYS PRIOR TO GOSC

3.0, 3.7, 3.7.1, 3.7.2, 3.7.3, 3.16

READ-AHEAD PACKET NLT 3 WORKING DAYS PRIOR

TO GOSC PREBRIEF FLW

1416 WITH A SYNOPSIS OF

CURRENT AND FUTURE

OPERATIONS , MOST

CURRENT SLIDES, AND

TALKING POINTS,

3.0, 3.8, 3.16

GENERAL OFFICER

CORRESPONDENCE/AIDES

DRAFT TALKING POINTS NLT

5 WORKING DAYS PRIOR TO

GOSC PREBRIEF (INCLUDE

FINAL IN READ-AHEAD

PACKET); CORRESPONDENCE

3.0, 3.9, 3.9.1, 3.9.2, 3.16

NLT 2 WORKING DAYS

AFTER COR NOTIFICATION

SIGNIFICANT ACTIVITIES (SIGACTS) E-MAIL NLT NOON EVERY

OTHER WEDNESDAY

3.0, 3.10, 3.16, 3.17

IN-PROGRESS REVIEWS (IPR)

MINUTES/EXSUM

NLT FIRST 5 CALENDAR

DAYS OF EACH MONTH;

MINUTES NLT 2 WORKING

DAYS AFTER THE MEETING

3.0, 3.11, 3.16

AFTER ACTION REVIEW (AAR)/AFTER

ACTION REPORT (AAR)

REVIEW NLT 2 WORKING

DAYS AFTER EACH GOSC

CYCLE; REPORT NLT 2

WORKING DAYS AFTER

REVIEW

3.0, 3.1, 3.2, 3.3, 3. 4, 3.5, 3. 6, 3.7, 3.8, 3. 9, 3.10, 3. 11, 3.12, 3.13, 3.14, 3.15, 3.16

MONTHLY STATUS REPORTS (MSR) NLT 3 WORKING DAYS

FOLLOWING THE FINAL DAY

OF EACH CONTRACT WORK

MONTH

3.0 3.13, 3.16

CLOSE-OUT MEETING AND FINAL

REPORT SUMMARY

NLT LAST WORKING DAY OF

THE CONTRACT; TURN-IN

GFI/GFP; SUBMIT FINAL

REPORT TO COR

3.0 3.14, 3.16, 5.3

TRIP REPORTS WITHIN 5 WORKING DAYS

AFTER THE END OF TRAVEL

3.0, 3.17

QUALITY CONTROL PLAN (QCP)/KEY

CONTROL

ONE COPY TO COR AT KICK-

OFF MEETING

4.2, 5.3, 5.33

CONTRACT MANAGEMENT

REPORTING APPLICATION (CMRA)

NLT 31 OCTOBER OF EACH

CALENDAR YEAR

4.3

ANTITERRORISM (AT) LEVEL I

TRAINING

NLT 30 CALENDAR DAYS

AFTER CONTRACT START

DATE; CERTIFICATES NLT 45

DAYS AFTER COMPLETION OF

TRAINING

5.4

IWATCH TRAINING NLT 30 CALENDAR DAYS

AFTER CONTRACT AWARD

AND NLT 30 CALENDAR OF

NEW EMPLOYEES

COMMENCING

PERFORMANCE; RESULTS

NLT 30 CALENDAR DAYS

AFTER CONTRACT AWARD

5.5

INFORMATION ASSURANCE (IA) -

DOD CYBER AWARENESS CHALLENGE

TRAINING

PRIOR TO ACCESSING

INFORMATION SYSTEMS AND

ANNUALLY THEREAFTER;

CERTIFICATES TO COR

IMMEDIATELY UPON

COMPLETION

5.6

ARMY TRAINING CERTIFICATION

TRACKING SYSTEM (ATCTS)

REGISTER PRIOR TO

COMMENCEMENT OF WORK

5.6

ACCEPTABLE USE POLICY

AGREEMENT

PRIOR TO COMMENCEMENT

OF WORK

5.6

OPERATION SECURITY (OPSEC)

TRAINING

NLT 30 CALENDAR DAYS OF

BEGINNING OF CONTRACT

PERFORMANCE; ANNUALLY

FOR CONTRACTS THAT

CROSS FYS; LIST OF

PERSONNEL TRAINED NLT 5

CALENDAR DAYS OF

TRAINING COMPLETION;

NEW HIRES REQUIRE

TRAINING NLT 30 CALENDAR

DAYS OF COMMENCEMENT

OF WORK

5.9

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 Quality Control (QC). Contractor shall develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with (IAW) this PWS. Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. Contractor’s QCP is the means by which he assures himself that his work complies with the requirement of the contract.

Contractor shall provide one (1) copy of the QCP to COR at the kick-off meeting. The plan shall include:

4.2.1 An inspection system covering all the support provided by Contractor. It shall specify the areas to be inspected on both a scheduled or unscheduled basis, how often inspections are accomplished, and the title of the individual(s) who shall perform the inspection.

4.2.2 The methods for identifying and preventing defects in the quality of support performed before the level of performance becomes unacceptable.

4.3 Contractor Management 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 Department of Defense (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.

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 level security clearance and must maintain the level of security required for the life of the contract. The security requirements are IAW DD Form 254.

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. Contractor shall establish and implement methods of making sure all keys/key cards issued to Contractor by Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to Contractor by Government shall be duplicated.

Contractor shall develop procedures covering key control that shall be included in the QCP. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the KO.

5.3.1 In the event keys, other than master keys, are lost or duplicated, Contractor shall, upon direction of the KO, re-key or replace the affected lock or locks; however, Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by Government and the total cost deducted from the monthly payment due Contractor.

5.3.2 Contractor shall prohibit the use of Government issued keys/key cards by any persons other than Contractor’s employees. Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the KO.

5.3.3 Lock Combinations. Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

These procedures shall be included in Contractor’s QCP.

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.

AT Awareness Training for Contractor Personnel Traveling Overseas: Nonapplicable.

5.5 iWatch Training. The contractor and all associated subcontractors are required to review the FLW, 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 information 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. Contractor and subcontractor personnel performing IT functions shall successfully complete IA training and certification for their assigned IA Technical or IA Management level IAW AR 25-2, Para 4-3, DoD 8570.01-M and Department of Defense Directive (DoDD) 8570.01. DFARS Clause 252.239-7001 Information Assurance Contractor Training and Certification: (JAN 2008) (a) Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions IAW DoD 8570.01–M, Information Assurance Workforce Improvement Program.

Contractor shall meet the applicable information assurance certification requirements, including — (1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01–M; and (2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01–M. (b) Upon request by Government, Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions. (c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

All contractor employees and associated subcontractor employees must complete the DoD IA Awareness training (available at https://ia.signal.army.mil) before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within 6 months of appointment to IA/IT functions.

Certificates of completion for each affected contractor employee shall be submitted to the COR (or KO if no COR is appointed) within 30 calendar days after completion of training.

5.8 The OPSEC 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 FYs, 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 Contractor access to the FLW Local Area Network (LAN). Contractor personnel shall obtain Common Access Cards (CAC), be registered in the ATCTS by a Government representative, and complete IA Training before being permitted to access the FLW LAN. For contracts crossing FYs, 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 that 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 IA standards as prescribed by AR 25-2. The NEC retains sole administrator authority over devices connected to the network. Access to network resources is 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. 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.11 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 speakerphones, 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.12 For contractors requiring CAC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated NACI or an equivalent or higher investigation IAW 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 six (6) months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on favorable review of the Federal Bureau of Investigation (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.

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 issued to Contractor personnel are returned to the COR upon termination or completion of this Contract.

5.13 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, Contracting Officer Technical Representative (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.

PART 6 TECHNICAL EXHIBIT / ATTACHMENT LISTING

6. Technical Exhibits and Attachments

6.1 Technical Exhibit 1 – Performance Requirements Summary

6.2 Technical Exhibit 2 – Government Furnished Property (GFP)

6.3 Technical Exhibit 3 – Post Meeting

6.3 Technical Exhibit 4 – Executive Summary (EXSUM)

6.4 Technical Exhibit 5 – Bi-weekly Significant Activities (SIGACTS) Report

6.5 Technical Exhibit 6 – Surveillance Checklists

Technical Exhibit 1 – Performance Requirements Summary

6.1 Technical Exhibit 1 - 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.

3.0, 3.1, 3.1.1 Community of Practice (CoP) Engagement

1. Contractor shall engage with CoP POCs to research general issues, gaps, best practices and potential gap solutions with MSCoE equities. The Government’s estimate for CoP engagement is approximately 10 hours per week.

2. Contractor shall prepare and provide findings and recommendations in written format NLT 2 working days after need identification.

3. Deliverables shall be submitted electronically, prepared in MS Word®, PowerPoint®, Excel®, follow AR 25-50 standards, using generally acceptable business format, using correct grammar, spelling, and punctuation, and ready for Army senior executive level presentation.

1. Provide findings and recommendations in written format NLT 2 working days after need identification.

2. Initial draft information paper shall contain 80% or better informational content, be accurate, complete, and correct.

3. Final revised…