17R0017_LRI_PWS_13Sept.docx

Performance Work Statement Language Readiness Index (LRI)

1.0 INTRODUCTION

The Defense Language and National Security Education Office (DLNSEO) requires support services for the continued maintenance and implementation of the Language Readiness Index (LRI) program to assist the Office of the Secretary of Defense (OSD), the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands (CCMDs), the Military Departments, and Components to manage their language, regional expertise, and cultural (LREC) capabilities and requirements in support of Department of Defense (DoD) missions.

2.0 BACKGROUND

The 2005 Defense Language Transformation Roadmap (January 2005) defined the actions for the DoD to build a system using a capabilities-based language requirement determination process to identify linguist and translator requirements as part of the deliberate and contingency planning processes for operations and plans. The Roadmap further instructed DLNSEO to develop and maintain a secure Web-based capability to collect and organize the data and establish a process to provide the Joint Staff, Combatant Commands (CCMDs), Services, and Defense agency representative access to this information.

The Chairman of the Joint Chiefs of Staff Instruction (CJCSI 3126.01A, 31 January 2013) provides policy and procedural guidance for the identification, planning and sourcing of LREC capabilities in support of the Department of Defense Strategic Plan for Language Skills, Regional Expertise, and Cultural Capabilities, national decision-making, and global military operations. The instruction identifies LRI as the decision support system DoD will use to achieve the goals of and implement the policies defined in the instruction.

A Department of Defense Directive (DoDD 7730.65, 11 May 2015) establishes the Defense Readiness Reporting System (DRRS) program to monitor the readiness of the DoD Components to provide capabilities to support the National Military Strategy (NMS) as directed by Presidential and Secretary of Defense guidance. DRRS encompasses the automated, near real-time readiness reporting systems that provide current readiness status for operational forces and defense support organizations in terms of their ability to perform their Mission Essential Tasks Lists (METL). LRI is one of the reporting systems in DRRS. This Directive applies to the Office of the Secretary of Defense, the Military Departments, the Chairman of the Joint Chiefs of Staff, CCMDs, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the DoD.

A Department of Defense Instruction (DoDI 5160.70, 30 December 2016) establishes LRI as the system to identify, prioritize, and input requirements for analyzing language proficiency, regional expertise, and cultural capabilities in support of readiness and risk assessment in DRRS. This includes reporting capability-based requirements for CCMD-specific foreign LREC capability requirements.

3.0 SCOPE

Support the implementation, operation, sustainment and evolution of the Language Readiness Index (LRI) program in DRRS-Strategic. Provide technical lead and advisory support to DLNSEO for the ongoing institutionalization and integration of designated programs, processes, and data sources into LRI.

4.0 REQUIREMENTS

4.1 General Personnel Qualifications

The Contractor shall provide the required services by employing and utilizing qualified personnel with appropriate combinations of education, training and experience.

4.2 Provide Subject Matter Expertise

Subject Matter Expertise support is essential to this effort and requires personnel with relevant education, knowledge, and documented experience in supporting DLNSEO programs. The SME will hold a Master’s Degree in Information Systems from an accredited college with a demonstrated experience managing IT projects for DoD and DLNSEO. SMEs may be called upon to, and should have demonstrated ability to provide formal training, brief senior leadership, and provide research products when required.

LRI SMEs shall have a working knowledge of the DoD Analytic Agenda, the Guidance for the Employment of the Force (GEF), the Defense Language Program (DoDD 5160.41E, DoDI 5160.70, DoDI 5160.71), the DRRS, the DoD LREC Strategic Plan, the LRI application, Combatant Command operational and deliberate/contingency planning, and the Capabilities Based Requirements Identification Process (CBRIP). LRI SMEs shall have demonstrated experience working with DLNSEO, the Joint Staff, the DRRS Integration Office, the National Security Agency (NSA), the Defense Manpower Data Center (DMDC), and the CCMDs related to LREC programs.

SMEs shall:

4.2.1. Support DLNSEO program and project managers in all aspects (analytical and technical) to support their OSD mission and to meet the intent of DoDD 5160.41E and DoDI 5160.70. SME shall have an in-depth understanding of the key requirements, the criticality of the tasks, and competencies required to successfully execute the LRI program.

4.2.2. Communicate across the Department with DLNSEO and stakeholders to not only assist defining potential LREC needs and requirements, but also how LRI can be used to facilitate their LREC planning and risk assessments.

4.2.5 LRI SMEs shall have a comprehensive understanding of the following DoD policies related to DLNSEO, LREC processes, and the LRI lifecycle.

4.2.5.1 The Defense Language, Regional Expertise, and Culture Program (DoDD 5160.41E and DoDI 5160.70)

4.2.5.2 The Defense Readiness Reporting System (DoDD 7730.65 and DoDI 7730.66)

4.2.5.3 The Department of Defense Strategic Plan for Language Skills, Regional Expertise, and Cultural Capabilities, 2011-2016

4.2.5.4 The LREC CBRIP (CJCSI 3126.01A)

4.2.5.5 The DoD Analytic Agenda

4.2.5.6 The Guidance for the Employment of the Force

4.2.5.7 CCMD operational and contingency planning processes

4.2.5.8 The Universal Joint Task List

4.2.5.9 Service Task Lists (Army, Navy, Air Force, and Marine Corps)

4.2.5.10 The Interagency Language Roundtable skill level descriptions for the listening, reading, writing, and speaking modalities and how language proficiency applies to combatant commander needs in their area of responsibility

4.2.5.11 Manpower and personnel structure of DoD organizations

4.2.5.12 MS SQL

4.2.5.13 IBM Cognos

4.3 Maintain, Update, and Enhance the LRI Application

The Contractor shall:

4.3.1. Provide the technical support and assistance to maintain, upgrade and improve the LRI application and its operation in DRRS. This task will include working closely with DLNSEO, the DRRS Implementation Office (DIO), and stakeholders to resolve issues. Issues are identified through feedback emails and within the LRI application. This effort shall include problem analysis, identifying solutions, planning for improvement, implementation of changes into the DRRS framework, creation of applicable code, and testing of software as part of the DRRS application.

4.3.2. Coordinate with the DIO and the DRRS development team to maintain and update LREC content, and analytic components, based on available data to capture requirements against capabilities and evaluate the gaps in the total force to determine acceptable risk levels and mitigation strategies.

4.3.3. Ensure that LREC inventory and requirement data sets are updated and current within DRRS. The LRI application shall utilize all relevant data available within the DRRS data warehouse. This task includes the discovery and implementation of new data sources into LRI. Analysis of data variances for issue resolution between LRI and other systems of record will be conducted as necessary.

4.3.4. Create analytical tools within the LRI system based off on feedback from community members and stakeholders in support of the DLNSEO mission. These tools will make use of all available data (current and historical) to create reports, visualizations, and dashboards to enable language users and senior leadership to better manage LREC assets and requirements. This will provide context for the current readiness and capability of the foreign language speaking community, and assist in projecting DoD’s future capabilities and deficiencies.

4.3.5. Consult with DLNSEO, LRI stakeholders, and the DIO to produce a visually distinctive interface that is on par with current government, commercial web, and usability standards format to logically display the associated LREC information in a manner that is user intuitive highlighting similarities, disparities, trends, and other relationships. Displays of information will include visualizations (tables, charts, graphs, plots, histograms, geographic, and others) that will allow users to answer questions, create scenarios, assist with planning, conduct risk mitigation.

4.3.6. Software Users Guide. As needed, provide and update the Software Users Guide with instructions for end users of LRI. Email the updated Users Guide

4.3.7. LRI Training and Outreach. At the direction of the Government, the Contractor shall conduct capability briefs, demonstrations and training to DoD Senior Leadership, CCMD staffs, and components to show current LRI capabilities, explain planned future enhancements, and discuss the needs of ODASD (Readiness) and how LRI can fulfill its requirements.

4.3.8. Ensure all deliverables involving coding (i.e. software) are coded in accordance with DIO and DRRS standards so as to be fully compatible with the Language Readiness Index on the DRRS platform and to be fully compliant with the overall DRRS software design and coding policies and practice.

4.3.9. Product Installation onto DRRS. The contractor shall conform to the DRRS program’s configuration control, testing, and release management processes and procedures. The contractor will work directly with the DIO and DIO designated parties to ensure developed software complies with Government-approved configuration requirements, is appropriately tested, installed and passes accreditation by the Government.

4.4 Data Sources and Variance

The Contractor shall:

4.4.1. Pursue acquiring data from sources related to DoD agencies, military services, civilian contractors, the National Language Service Corps, Allies/Coalitions, the National Virtual Translation Center, language technologies, and other sources as they become available. Updating LRI functions shall be dependent on when LREC data becomes available from authoritative sources, clarity of the data received, completion of Memorandums of Agreement/Understanding (MOA/MOU), and the application of applicable personal and privacy act permissions.

4.4.2. Identify variances in sources of language and culture data provided to the DRRS Data Warehouse from the Defense Manpower Data Center (DMDC), the Services, and other sources as they become available. The contractor shall conduct a comparative analysis of the data provided to make recommendations and take appropriate actions when directed by DLNSEO.

4.5 Capabilities Based Requirements Identification Process (CBRIP)

The Contractor shall:

4.5.1. Support the Joint Staff by creating tools to capture draft CCMD LREC inputs for review and approval as fully qualified needs and requirements. LRI will allow for the management and approval of inputs from the Joint Staff, CCMDs, and the Services using the CBRIP process. These tools will provide analytical products and reports based on demand signals from the CCMDs and Services.

4.5.2. Provide technical support for the identification of United States Marine Corps (USMC) CBRIP LREC requirements process.

4.5.3. Support the CBRIP workshops by traveling with the Joint Staff to CCMDs and other destinations as required. Presentations and training on LRI tools to assist in the CBRIP process will be presented.

4.6 LREC Dashboard

The Contractor shall:

4.6.1. Create a configurable and programmable environment utilizing widgets (an easy-to-use software application), and visualizations for LRI users that draws together key functional processes in LRI, CLPT, RPAT, and the Planners Tool into a single screen.

4.6.2. Collaborate with the LRI user community at key phases of development to ensure the Dashboard provides value to the community at large. The user community will provide feedback before deployment to production.

4.7 Country Language Prioritization Tool (CLPT)

The Contractor shall:

4.7.1. Support OUSD (Intelligence) by implementing the Countries Language Priority Tool (CLPT) to generate the Strategic Language List (SLL) in LRI. The CLPT will allow other analysts to input variables to perform comparisons.

4.7.2. Work with OUSD (I) to automate input processes in order to expedite updating the CLPT.

4.8 Regional Proficiency Assessment Tool (RPAT)

The Contractor shall:

4.8.1. Work with CASL and DMDC to begin importing the RPAT data once verification is received that data is available to the LRI. The regional proficiency modalities will become part of the LRI inventory and support other LRI processes.

4.8.2. Collaborate with the RPAT survey developers to identify relevant data for import into LRI.

4.9 Planner Tools

The Contractor shall:

4.9.1 Create a dedicated capability for a planner (COCOM or Component) to conduct risk analysis, create demand signal, run scenarios, and generate data to assist with the creation of “Requests for Forces” and similar documentation.

4.10 LRI Feedback Community

The Contractor shall:

4.10.1 Establish an LRI Feedback Community consisting of stakeholders and select users (including representatives from OSD, Combatant Commands, Combat Support Agencies, and the Services) who can provide insight, ideas, testing, and offer peer reviews of LRI products before general release.

4.11 DLNSEO Program Support

4.11.1 As required by DLNSEO, assist and participate in meetings such as the Defense Language Action Panel (DLAP), Defense Language Steering Committee (DLSC), CBRIP Roadshow, and others as needed.

4.11.2 As required by DLNSEO, the Contractor shall provide program support documentation in the form of Smart books, IPRs, and whitepapers as needed to support DLNSEO efforts.

During the Base Year and Option Years 1 and 2, the Contractor shall submit the following reports:

4.13.1 A project management plan as a formal, approved document used to guide both project execution and project control. The project plan is to document planning assumptions and decisions, facilitate communication among project stakeholders, and document approved scope, cost, and schedule baselines.

4.13.2 A software development plan is a comprehensive, composite artifact that gathers all information required to manage the project. It encloses a number of artifacts developed during the Inception phase and is maintained throughout the project.

4.13.3 Monthly status reports containing at a minimum: a description of the work completed that month for each deliverable; the work planned for the next month; and issues/concerns.

4.13.4 A final report that includes key milestones met, key deliverables completed, budget/schedule tracking, identified risks and issues, and any variances.

1. DELIVERABLES

The DLNSEO serves as the COR for this contract. All deliverables will be submitted to DLNSEO and DIO. The Contractor will also work in close coordination with the DIO on matters related to DRRS and with DMDC on matters related to the RPAT, including the continuous development and refinement of the LRI throughout the base and option years. All products generated in performance of the contract including any intellectual property, code, training, briefings, reports, or deliverables will become government property and must be provided to the Government representative in accordance with the Performance Work Statement or as requested. The Government wants to ensure that it retains all data and information generated.

Monthly Status Reports

6.0 Pertinent Documents

6.1 The references listed below are applicable to the systems described in this PWS:

· Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3170.01G, 1 March 2009, Joint Capabilities Integration and Development System (JCIDS).

· Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3401.01E, 13 April 2010, Joint Combat Capability Assessment.

· Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3401.02B, 31 May 2011, Force Readiness Reporting.

· Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01E, 15 December 2008, Interoperability and Supportability of Information Technology and National Security Systems (including Net-Ready Key Performance Parameter, NR-KPP, and the GIG Technical Guidance, GTG)

· Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3126.01A, 31 January 2013, Language, Regional Expertise, and Culture (LREC) Capability Identification, Planning, and Sourcing

· Department of Defense Directive 5124.02, 23 June 2008, Under Secretary of Defense for Personnel and Readiness (USD(P&R)).

· Department of Defense Directive No. 7730.65, 3 June 2002 (Certified Current 11 May 2015), Department of Defense Readiness Reporting System.

· Department of Defense Instruction No. 7730.66, 8 July 2011, Guidance for the Defense Readiness Reporting System (DRRS).

· Department of Defense Instruction No. 8500.2, 6 February, 2003, Information Assurance (IA) Implementation.

· Department of Defense Instruction No.5160.70, 30 December 2015, Management of the Defense Language, Regional Expertise, and Culture LREC) Program

· OSD Memo 2 Aug 2010, Defense Readiness Reporting System (DRRS) Standards and Technical Interface Specifications for Interoperability.

· DRRS Implementation Office, DRRS System Version Description

· DRRS Implementation Office, Program Management Plan for DRRS

· DRRS Implementation Office, Information Assurance Vulnerability Management Plan

· The Defense Language Transformation Roadmap, January 2005

· Section 117 of Title 10, United States Code (U.S.C.), Readiness Reporting System: Establishment; Reporting to Congressional Committees.

· ISO/IEC 12207:2008(E) (IEEE Std 12207-2008) Systems and Software Engineering- Software Life Cycle Processes.

· IEEE/EIA 12207.1-1997 IEEE Guide for Information Technology - Software Life Cycle Processes - Life Cycle Data.

7.0 CONTRACTOR MANPOWER REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Defense Language and National Security Education Office (DLNSEO) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil

8.0 CONTRACTOR TRAVEL

8.1 The contractor will be required to travel CONUS, OCONUS and within the National Capital Region (NCR) during the performance of this contract to attend meetings, conferences, and conduct demonstrations and training. 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. Below is the list of anticipated travel locations, commands, and the approximate number of days:

9.0 SECURITY

9.4.1 Be cleared at least to the SECRET level.

9.5.2 Be CAC or PIV ready prior to reporting for work. At minimum all Contractor personnel must obtain/maintain a favorable FBI National Criminal History Check (fingerprint check), two forms of identity proofed identification (I-9 document), and submit a National Agency Check and Law Credit (NACLAC) vetting package for processing. Obtaining CAC or PIV ready status is the responsibility of the contracting agency.

9.4.3 Be citizens of the United States.

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

9.5 If at any time, any Contractor person requiring a CAC is unable to obtain/maintain an adjudicated NACLAC, the Contractor shall immediately notify DLNSEO and remove such person from work under this contract.

9.6 The Contractor shall report immediately to the DIO Security Manager and secondly to the COR if there is a discovery of any Privacy breach.

10.0 GOVERNMENT FURNISHED PROPERTY/EQUIPMENT

DLNSEO will arrange access to the Defense Readiness Reporting System (DRRS) for analysts identified by the contractor and will arrange access to a Secure Internet Protocol Router Net (SIPRNet) computer terminal and the necessary TOKENs for its use.

11.0 QUALITY CONTROL

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

12.0 QUALITY ASSURANCE

12.1. The Government reserves the right to perform inspections and surveillance to evaluate the Contractor’s compliance to the contract terms and performance of the requirements in the PWS. The Government will make every effort to ensure that the surveillance methods described below are conducted in an objective, fair, and consistent manner.

12.1.1. Periodic Surveillance. This action occurs when the COR or other Government official observes a deficiency. Examples include evidence from accidents, incidents, or delays. Regardless of where in the line-of-duty the COR observes contractual procedures not being followed, he/she has an obligation to document and report the deficiency to the Contracting Officer.

12.1.2. Customer Complaint Surveillance. This action is instituted when the COR receives a complaint from a stakeholder regarding contractor service. The COR will obtain the complaint in writing and then conduct an investigation to determine its validity. If the complaint is deemed valid, the COR will immediately notify the contracting Officer for action. The COR will notify both the Contract Manager and the complainant of the Government’s response to their complaint.

12.2. Contract Discrepancy Report (CDR). In the event of unsatisfactory contractor performance, the COR or CO will issue a CDR that will explain the circumstances and findings concerning the incomplete or unsatisfactory service. The contractor shall acknowledge receipt of the CDR and respond in writing as to how he/she shall correct the unacceptable performance and avoid a recurrence. The Government will review the contractor's corrective action response to determine acceptability and will use any completed CDR as part of an overall evaluation of Contractor performance when determining present or future contractual actions.

13.0 PERFORMANCE REQUIREMENT SUMMARY

The Contractor performance requirements are summarized into performance metrics that relate directly to essential items. The Performance Standards briefly describe the required level of service and the minimum Acceptable Quality Level of service for each requirement.

Performance Requirement Summary (PRS)

Performance Objective/Required Services (s) (PWS Paragraph)

4.13. Timely delivery and acceptance of Monthly Status Report (MSR) referenced in the paragraph in complete detail

timely, detailed, comprehensive, and accurate Project Management Plan and Software Development Plan 100% of the time, as required in support of this effort.

4.11.2. IPR documentation in the form of Smart books and white papers as needed to support DLNSEO efforts in the format specified by the COR

13.0 APPENDIX

(A) Draft DD254, Security Classification Specification