17R0017_LRI_Solicitation_31Mar18_FINAL.pdf

SEE ADDENDUM

(No Collect Calls)

H9821017R0017 31-Mar-2018

b. TELEPHONE NUMBER

(571) 372-8002

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 30 Apr 2018

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

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

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

H982109. ISSUED BY

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

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

TODD E. DAVIS

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

(TYPE OR PRINT)

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

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

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

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

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

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

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

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

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DEFENSE HUMAN RESOURCES ACTIVITY

4800 MARK CENTER DRIVE,

SUITE 06J25-01

ALEXANDRIA VA 22350-4000

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE HQ0054 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

DEF LANG NATIONAL SEC ED OFFICE (DLNSEO)

DLNSEO

4800 MARK CENTER DRIVE,

SUITE 08F09-02

ALEXANDRIA VA 22350

TEL: FAX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$27,500,000

NAICS:

541511

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

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

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

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

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

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

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

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

REPRESENTATIVE

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

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

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

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

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

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

H9821017R0017

Section SF 1449 - CONTINUATION SHEET

ADDENDUM TO 52.212-1

1. By submission of this package, you are stating that ALL terms and conditions of the entire solicitation are accepted and apply to your offer.

2. DEFENSE HUMAN RESOURCES ACTIVITY is the designated office for receipt of offer. The Offeror shall clearly mark envelope(s) / package(s) sent in response to this solicitation with the words “Solicitation Offer H98210-17-R-0017”. Mailed offers should be addressed to the following location:

Delivery by Mail Defense Human Resources Activity (DHRA) – PKEA Contracting Directorate Attn: Todd E. Davis (Contract Specialist) 4800 Mark Center Dr., Ste. 03E25 Alexandria VA, 22350-1300

Delivery by Hand Defense Human Resources Activity (DHRA) – PKEA Contracting Directorate Attn: Todd E. Davis (Contract Specialist) 4800 Mark Center Dr., West Tower / Ste. 03E25 Alexandria VA, 22350-1300

NOTE: If hand delivering proposal, contact the Contract Specialist via email at least five (5) business days prior to the due date for delivery instructions.

3. The NAICS code for this procurement is 541511 and the small business size standard is $27.5 million.

4. Questions Relating to Solicitation: Email questions to Contract Specialist Todd E. Davis at Todd.E.Davis2.civ@mail.mil or Contracting Officer Darryl D. Barnes at Darryl.D.Barnes4.civ@mailmil no later than April 10, 2018 10:00AM EST. If the date / time are updated an amendment will be issued on www.fbo.gov.

Reference the Solicitation Number in the SUBJECT LINE of the email. Responses will be provided by email / amendment to the solicitation. Ensure to include both personnel when sending an email.

5. System for Award Management (SAM): When the proposal is submitted in response to the solicitation the offeror must be registered in SAM. In accordance with FAR 52.232-33 Payment by Electronic Funds Transfer –

SAM.

6. See FAR clause 52.212-2 and Addendum to 52.212-2 Evaluation of Commercial Items for evaluation factors and evaluation criteria.

7. The proposal shall not merely restate the PWS, but demonstrate and provide convincing detail of how the offeror will meet the requirement of the PWS and associated sections of the PWS.

8. Facsimile proposals are not authorized. Do not return the entire solicitation.

• Vol. 1, Section I, Technical Capability

• Vol. 1, Section II, Past Performance

• Vol. 2, Section I, Price

• Vol. 2, Section II, Business Information

NOTE: Factor 1 Technical Capability and Past Performance, when combined, are significantly more important than price.

mailto:Todd.E.Davis2.civ@mail.mil mailto:Darryl.D.Barnes4.civ@mailmil http://www.fbo.gov/

A. Volume I, Section I, Technical Capability The offeror shall demonstrate their ability to comprehend and understand the Government’s requirements as set forth in the technical portion of the PWS and other associated sections. This will be expressed through the proposals presentation and understanding of the Language Readiness Index and the associated capabilities that require a web-based capability to gather, organize, distribute, identify, prioritize, and input requirements for analyzing language proficiency, regional expertise, and cultural capabilities in support of readiness and risk assessment in DRRS.

Along with “Program Support” reflected throughout the project management plan, quality control plan and staffing plan.

B. Volume I, Section II, Past Performance Past Performance References: Offerors shall submit no more than three (3) relevant Past Performance references. All references shall address current projects or those completed within the last five (5) years by the Offeror as a prime contractor.

For each reference being submitted, complete and include a Past Performance Relevancy Questionnaire (PPRQ) found at Attachment 10. Complete and submit one PPRQ per reference. Offerors shall include no more than one contract for each reference. The Government will only review one contract. If the Offeror submits more than one contract for each reference; those contracts will not be reviewed.

Additionally, a Past Performance Questionnaire cover letter has been provided at Attachment 4, for vendors to provide to their selected POCs explaining the purpose and process of submitting Attachment 10 Questionnaires.

NOTE: If you have a CPARS in the last 3 years in reference to the PPRQ (Attachment 10), you will not need to submit any questionnaires, the government will take your CPARS from the system.

The Government will utilize the information submitted from Attachments 9 and 10 to obtain additional performance information on the Offeror. Subcontractors Past Performance will not be reviewed for Attachment 9 and 10; therefore the Government is only reviewing Past Performance from Offerors who performed work as prime contractor. Should the Offeror possess no relevant past performance, a written statement shall be provided by the Offeror so indicating. In this case, the Offeror will not be evaluated favorably or unfavorably on past performance and will be assigned a rating of Unknown Confidence.

C. Volume II, Section I, Price The offeror shall review the detailed requirements of the solicitation and propose prices based upon the provided information and associated labor categories. Prices shall be entered on the standard form 1449 for each Contract Line Item Number (CLIN) and into the price model spreadsheet (attachment 07) for each labor category in every Period of Performance (PoP).

D. Volume II, Section II, Business Information

1. Signed copy of the SF 1449, with blocks 17 and 30a-30c completed.

2. Signed copy of the Standard Form 30, with any amendment that was issued in reference to the RFP.

3. Offerors DUNS number, Cage Code and Tax ID number.

4. Representations and Certifications FAR 52.212-3 Alt I, 52.219-1 and 52. 222-22 are required to filled-in and returned with proposal.

5. Notice: If the proposal that is provided in response to the solicitation at the time of award is provided while the company is suspended, debarred, and ineligible for receipt of a contract from Government Agencies or in receipt of a notice of proposed debarment from any Government Agency, the proposal is voidable at the option of the Government.

6. Sub-Contracting Plan: reference attachment 11 for sub-contracting plan instructions

9. SUBMISSION OF PROPOSALS

(A) Proposals shall be prepared and submitted as follows: offerors shall submit one CD containing a complete copy of their proposal, hard copies and an email. All of the volumes will be separated into the following volumes.

Each volume shall be submitted in an individual folder / binder as stated below.

VOL. SECTION VOL.

TITLE

# OF PAPER

COPIES

# OF

ELECTRONIC

COPIES ( Email)

CD / DVD PAGE

LIMIT

I I Technical Capability

4 (3 Copies and 1 with original signatures)

1 (With scanned signatures from any document with signatures.)

1-2 CD /

DVD will contain every volume.

I II Past Performance

2 (1 orig. and 1 copy)

1 (With scanned signatures from any document with signatures.)

No page limit.

II I Price 2 (1 orig. and 1 copy)

1 (With scanned signatures from any document with signatures.)

No page limit.

II II Business Information

2 (1 orig. and 1 copy)

1 (With scanned signatures from any document with signatures.)

No page limit

(B) Format, Organization, Exceptions and Content

(1) Format

(a) Each volume must be separately bound and contain sufficient information to permit a detailed evaluation.

(b) The offeror’s proposal shall be prepared on standard 8 ½ ” by 11” paper, single-spaced, with 1” minimum margins.

(c) Foldouts may be used, but shall be no larger than 8 ½ ” by 14”, shall be printed on one side only.

(d) The type shall be no smaller than 10-pitch “Times New Roman”.

(e) The proposal shall follow the prescribed format.

(2) Organization

(a) The proposal shall be organized / adhered to with the number of volumes, volume titles, sections and page limitations as described above.

(b) Pages shall be numbered consecutively within each volume.

(INTENTIONALLY LEFT BLANK)

PERFORMANCE WORK STATEMENT

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 and be able to demonstrate experience with DRRS or the capability to comply with DRRS software design and coding policies, practices and standards. 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.3. Implement stakeholder input and ideas through the creation of business rules for LRI that underwrite the intent of the program and enforce DoD policies. This includes confirming business rule functionality through Quality Testing (QT) and resolving issues related to business rule execution based on stakeholder and community input.

4.2.4. Provide training, educational materials, briefings, and gather input from the Services, COCOMs, and other stakeholders on how to use the LRI and respond to questions. This shall include conducting capability briefs and demonstrations to DoD Senior Leadership, CCMDs, CSAs and components to show current LRI capabilities, and discuss the needs of OSD Plans and how LRI can fulfill their requirements.

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 of 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. Every six months, provide and update the Software Users Guide with instructions for end users of the LRI and also posted on the website.

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 LRI 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 all Service (Army, Navy, Marine Corps, and Air Force) CBRIP LREC requirements process.

4.5.3. Support the CBRIP workshops by traveling with the Joint Staff to CCMDs and other destinations within the National Capital Region (NCR). 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 (a simple application that is often part of a larger application already installed on the device), and visualizations for LRI users that draws together key functional processes in LRI, Country Language Prioritization Tool (CLPT), Regional Proficiency Analysis Tool (RPAT), and the Planners Tool into a single screen.

4.6.2. Support DLNSEO led collaboration 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 DLNSEO in generating the Strategic Language List by incorporating into the LRI data and features available in the OUSD (Intelligence) Countries Language Priority Tool (CLPT) to support analyst input of variables for comparative analysis.

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

4.8 Regional Proficiency Analysis 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 Contractor will assist and participate in meetings such as the Defense Language Action Panel (DLAP), Defense Language Steering Committee (DLSC), CBRIP facilitated workshops, and others as needed.

4.11.2 Contractor will provide updates to the COR or DLNSEO as meetings are held on a scheduled / non-scheduled basis. The contractor shall provide program support documentation in the form of monthly project status books, IPRs, and whitepapers to support DLNSEO efforts.

4.12 Participate in a Post-Award Conference. This meeting shall provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting shall provide the opportunity to discuss technical and management issues.

The Post Award Conference will aid both the Government and Contractor in achieving a clear and mutual understanding of all requirements, and identify and resolve any potential issues. The Contractor shall be prepared to discuss any items requiring clarification and gather information as necessary to support each deliverable and shall submit a written summary of the Post-Award Conference to the COR.

4.13 Reports

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

4.14 Provide Transition of Contract Services. The contractor shall provide a plan for transition in and out services to ensure minimum disruption to vital Government business. This plan shall address how the Contractor will work with the incumbent and Government personnel to ensure that there will be no service degradation during and after the transition-in period (initial thirty (30) day period after date of contract award) and during the transition-out period (thirty

(30) day period prior to date of contract expiration). Additionally, all information about DRRS- LRI are proprietary government information and will be transferred to the incumbent.

4.14.1 Submit and maintain a transition plan detailing all related phase-in activities to and milestones to ensure successful phase-in to the DRRS operating system and the maintenance and upgrade of the Language Readiness Index. The plan shall also include all phase-out activities for transitioning services to a successor contractor under a future contract to ensure minimal disruption and no diminution in the quality of services.

4.14.2 Perform phase-in services during the 30-day implementation period between contract award and the start of performance.

4.14.3 Perform phase-out services during the 30-day transition to a successor contract.

5.0 DELIVERABLES

DLNSEO provides the COR for this contract. All deliverables will be submitted to the DLNSEO COR. 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.

Deliverable Ref. Delivery Date

List each deliverable separately for Base and Option Years

PWS

paragraph

Date each deliverable is due after contract award

Training and educational materials Briefing slides

4.5.3 NLT 7 business days before

pre-workshop conference

Briefing slides and issue paper regarding language and culture data variances

4.4.2 NLT 7 business days before

meeting

Training, educational materials, and briefing slides

4.2.4 NLT 7 business days before

meeting

Software Users Guide 4.3.6 Update on a semi-annual basis (based on PoP)

Data Variance Update 4.4.2 Update on a Quarterly basis (based on PoP)

In Progress Review 4.11.2 Before 7th day of month Post-Award Conference (PAC) 4.12 NLT 10 business days after the contract award dated Draft Project Management Plan 4.13.1 45 days after contract award Final Project Management Plan 4.13.1 15 days after Gov’t approval of draft Software Development Plan 4.13.2 NLT 60 days after award Monthly Status Reports

4.13.3 30 days after contract award and every 30 days thereafter until contract end

Final Report 4.13.4 Final draft 30 days before end of performance period; final report 15 days from end of contract

Final Transition Plan (In & Out) 4.14 NLT 7 calendar days after start of the contract and within 30 calendar days prior to the end of the contract

Deliverable Ref. Delivery Date Trip Reports 7.0 Submit TR NLT the 15th of the month following period reported upon.

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.

Reference URL/Location DoDD and DoDI http://www.dtic.mil/whs/directives/index.html CJCSI http://www.dtic.mil/cjcs_directives/ USC Title 10, Section 117 http://www.gpo.gov/fdsys/granule/USCODE-2011-title10/USCODE-

2011-title10-subtitleA-partI-chap2-sec117 ISO http://www.iso.org IEEE http://www.ieee.org

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 provide one SME 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 Government travel requires prior approval/authorization by the COR. Below is the list of anticipated travel locations, commands, and the approximate number of days:

Travel: DMDC (PWS 4.4.2) Location Command Approx. Days

Seaside, CA DMDC 4 days Travel: CBRIP (PWS 4.5.3)

Location Command Approx. Days Tampa, FL USCENTCOM 4 days Miami, FL USSOUTHCOM 4 days Honolulu, HI USPACOM 7 days Colorado Springs, CO USNORTHCOM 4 days Stuttgart, Germany USEUCOM & USAFRICOM 12 days

9.0 SECURITY

9.1 Perform on-site work with Personally Identifiable Information (PII) only on systems that meet Department of Defense Information Assurance Certification and Accreditation Process http://www.dtic.mil/whs/directives/index.html http://www.dtic.mil/cjcs_directives/ http://www.gpo.gov/fdsys/granule/USCODE-2011-title10/USCODE-2011-title10-subtitleA-partI-chap2-sec117 http://www.gpo.gov/fdsys/granule/USCODE-2011-title10/USCODE-2011-title10-subtitleA-partI-chap2-sec117 http://www.iso.org/ http://www.ieee.org/ http://www.ecmra.mil/

(DIACAP) requirements and will be updated on an on-going basis to continue to meet DIACAP requirements.

9.2 Contractor and all Contractor personnel with access to or responsibility for nonpublic Government data under this contract shall comply with DoD Directive 8500.1 Information Assurance (IA), DoD Instruction 8500.2 Information Assurance (IA) Implementation, DoD Directive 5400.11 DoD Privacy Program, DoD 6025.18-R DoD Health Information Privacy Regulation, DoD 5200.2-R Personnel Security Program, and Homeland Security Presidential Directive (HSPD) 12.

9.3 Contractor shall establish appropriate administrative, technical, and physical safeguards to protect any and all nonpublic Government data to ensure the confidentiality, integrity, and availability of government data.

9.4 Contractor personnel with access to or responsibility for nonpublic Government data under this contract must comply with HSPD-12 Personal Identity Verification (PIV) issuance requirements, known as the Common Access Card (CAC) and must:

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)

Performance Standard

Acceptable Quality Level

4.4.2 Identify and

report language data

Submit a report with recommendation to

Submit a report with recommendation to variances between DMDC and LRI

COR NLT than 30 calendar days after request is received from COR

COR NLT than 45 calendar days after request is received from COR.

4.5.3 Update CBRIP

tool with approved FY17 CCMD and Service LREC requirements data when documented in Monthly Status Report (MSR)

Submit CBRIP tool update through the MSR NLT the 10th of the month following the period reported detailing the update

Submit MSR NLT the 15th of the month following the period reported upon, detailing all tasks, with 95% of all tasks on track to be completed on time.

4.6 Creation of easy-

to-use software application called “widgets” that are configurable and programmable that draws together functional processes in LRI to enhance user interface

Document in MSR by the 10th of the month following the period reported of the successful creation, testing and upload to LRI of the widget

Document in MSR NLT the 15th of the month following the period reported of the successful creation, testing and upload to LRI of the widget

4.7 Performance of

tasks associated with Country Language Prioritization tool

(CLPT)

requirements in Monthly Status Report (MSR)

Submit MSR NLT the 10th of the month following the period reported upon, detailing all tasks, with 100% of all tasks on track to be completed on time.

Submit MSR NLT the 15th of the month following the period reported upon, detailing all tasks, with 95% of all tasks on track to be completed on time.

4.8 Performance of

tasks associated with Regional Proficiency Analysis Tool (RPAT) requirements in Monthly Status Report (MSR)

Submit MSR NLT the 10th of the month following the period reported upon, detailing all tasks, with 100% of all tasks on track to be completed on time.

Submit MSR NLT the 15th of the month following the period reported upon, detailing all tasks, with 95% of all tasks on track to be completed on time.

4.11.2. IPR

documentation in the form of Smart books and white papers as needed to

Provide, detailed, comprehensive, and accurate In-Progress (IPR) and subsequently

Provide, detailed, comprehensive, and accurate In-Progress (IPR) and subsequently minutes support DLNSEO efforts in the format specified by the

COR

minutes to the COR within 8 days after the IPR 100% of the time.

to the COR within 10 days after the IPR 95% of the time.

4.13.1; 4.13.2 Delivery and acceptance of Project Management Plan and Software Development Plan referenced in the paragraph in complete detail

Develop, detailed, comprehensive, and accurate Project Management Plan and Software Development Plan 100% of the time and within 14 days of approval of draft Project Management Plan and 45 days after contract award for the Software Development Plan in support of this effort.

Develop detailed, comprehensive, and accurate Project Management and Software Development Plan 100% of the time, within 15 days of approval of draft Project Management Plan and 60 days after contract award for the Software Development Plan

4.13.3 Delivery and

acceptance of Monthly Status Report (MSR) referenced in the paragraph in complete detail

Provide a monthly status report containing at a minimum: a description of the work completed that month for each deliverable; the work planned for the next month; and issues/concern using Microsoft Office Suite 100% of the time by the, 30th day after contract award and every 30 days thereafter until contract end.

Provide a 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/concern in a format required by the COR 100% of the time, no later than 31 days after contract award and every 31 days thereafter until contract end.

4.13.4 Delivery and

acceptance of a Final Report, due NLT 10 days from the end of contract

Provide, detailed, comprehensive, and accurate final report to the COR 100% of the time. Provided 10 days from the

Provide, detailed, comprehensive, and accurate final report to the COR 100% of the time, no later than 15 days from the end end of contract. of contract.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 8 Months Language Readiness Index, Labor

FFP

Language Readiness Index, Labor Categories FOB: Destination

NET AMT

0002 1 Unitless Other Direct Cost (ODC)

COST

Other Direct Cost (ODC) Printing

ESTIMATED COST

0003 10 Unitless Travel & Travel Related Expenses

COST

Travel & Travel Related Expenses (Do Not Propose - A Not to Exceed (NTE) amount will be provided at time of award)

0004 1 Months Transition-In, FFP

Language Readiness Index, Transition-In

1001 12 Months OPTION Language Readiness Index, Labor

FFP

1002 1 Unitless OPTION Other Direct Cost (ODC)

COST

Other Direct Cost (ODC)

1003 10 Unitless OPTION Travel & Travel Related Expenses

COST

Travel & Travel Related Expenses (Do Not Propose - A Not to Exceed (NTE) amount will be provided at time of

2001 12 Months OPTION Language Readiness Index, Labor

FFP

2002 1 Unitless OPTION Other Direct Cost (ODC)

COST

Other Direct Cost (ODC)

2003 10 Unitless OPTION Travel & Travel Related Expenses

COST

Travel & Travel Related Expenses (Do Not Propose - A Not to Exceed (NTE) amount will be provided at time of

3001 12 Months OPTION Language Readiness Index, Labor

FFP

3002 1 Unitless OPTION Other Direct Cost (ODC)

COST

Other Direct Cost (ODC)

3003 10 Unitless OPTION Travel & Travel Related Expenses

COST

Travel & Travel Related Expenses (Do Not Propose - A Not to Exceed (NTE) amount will be provided at time of

4001 12 Months OPTION Language Readiness Index, Labor

FFP

4002 1 Unitless OPTION Other Direct Cost (ODC)

COST

Other Direct Cost (ODC)

4003 10 Unitless OPTION Travel & Travel Related Expenses

COST

Travel & Travel Related Expenses (Do Not Propose - A Not to Exceed (NTE) amount will be provided at time of

4004 1 Months OPTION Transition-Out

FFP

Language Readiness Index,Transition-Out

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government N/A Government 0002 N/A Government N/A Government 0003 N/A Government N/A Government 0004 Destination Government N/A Government 1001 Destination Government N/A Government 1002 N/A Government N/A Government 1003 N/A Government N/A Government 2001 Destination Government N/A Government 2002 N/A Government N/A Government 2003 N/A Government N/A Government 3001 Destination Government N/A Government 3002 N/A Government N/A Government 3003 N/A Government N/A Government 4001 Destination Government N/A Government

4002 N/A Government N/A Government 4003 N/A Government N/A Government 4004 Destination Government N/A Government

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 06-JUL-2018 TO

05-MAR-2019

N/A DEF LANG NATIONAL SEC ED OFFICE

(DLNSEO)

DLNSEO

4800 MARK CENTER DRIVE,

SUITE 08F09-02

ALEXANDRIA VA 22350

HQ0054

0002 POP 06-JUL-2018 TO

05-MAR-2019

N/A (SAME AS PREVIOUS LOCATION)

0003 POP 06-JUL-2018 TO

05-MAR-2019

N/A (SAME AS PREVIOUS LOCATION)

0004 POP 06-JUL-2018 TO

06-AUG-2018

N/A (SAME AS PREVIOUS LOCATION)

1001 POP 06-MAR-2019 TO

05-MAR-2020

N/A (SAME AS PREVIOUS LOCATION)

1002 POP 06-MAR-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

1003 POP 06-MAR-2019 TO

N/A (SAME AS PREVIOUS LOCATION)

2001 POP 06-MAR-2020 TO

05-MAR-2021

N/A (SAME AS PREVIOUS LOCATION)

2002 POP 06-MAR-2020 TO

N/A (SAME AS PREVIOUS LOCATION)

2003 POP 06-MAR-2020 TO

N/A (SAME AS PREVIOUS LOCATION)

3001 POP 06-MAR-2021 TO

05-MAR-2022

N/A (SAME AS PREVIOUS LOCATION)

3002 POP 06-MAR-2021 TO

N/A (SAME AS PREVIOUS LOCATION)

3003 POP 06-MAR-2021 TO

N/A (SAME AS PREVIOUS LOCATION)

4001 POP 06-MAR-2022 TO

05-MAR-2023

N/A (SAME AS PREVIOUS LOCATION)

4002 POP 06-MAR-2022 TO

N/A (SAME AS PREVIOUS LOCATION)

4003 POP 06-MAR-2022 TO

N/A (SAME AS PREVIOUS LOCATION)

4004 POP 06-MAR-2023 TO

06-APR-2023

N/A (SAME AS PREVIOUS LOCATION)

CLAUSES INCORPORATED BY REFERENCE

52.202-1 Definitions NOV 2013 52.203-3 Gratuities APR 1984 52.203-6 Restrictions On Subcontractor Sales To The Government SEP 2006 52.204-10 Reporting Executive…