H9821023R0001 - DLNSEO LRI Solicitation.pdf

SEE A DDENDUM

(No Collect Call s)

H9821023R0001 09-Dec-2022

b. TELEPHONE NUMBER

703-508-7682

8. OFF ER DUE DAT E/LOCAL T IME

03:00 PM 17 Jan 2023

5. SOLICIT ATION NUM BER 6. SOLICITAT ION ISSUE DAT E

A UTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STA NDARD FORM 1449 (REV . 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

( TYP E O R P RIN T)

(SIGNAT URE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Us e Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTA NCE IS DIFFERENT A ND PUT

BELOW IS CHECKED

TELEPHONE NO.

H982109. ISSUED BY

18b. SUBMIT INVOICES TO A DDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORM AT ION CALL:

a. NAME

MIKE CA RNLEY

2. CONTRACT NO. 3. AWARD/EFF ECTIVE DATE 4. ORDER NUM BER

(TYPE OR PRINT)

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

30a. SIGNA TURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

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. REQUISIT ION 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:

. Y OUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DEFENSE HUMAN RESOURCES ACTIVITY

4800 MARK CENTER DRIVE,

SUITE 03E25

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)

RAOUL VICENCIO

4800 M ARK CENT ER DRIVE,

SUITE 08F 09-02

ALEXANDRIA VA 22350

T EL: 571.256.0699 F AX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

X 8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$30,000,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. QUA NTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOM EN-OWNED SM ALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SM ALL BUSINESS P ROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF92

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 PAY MENT

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

STANDA RD FORM 1449 (REV. 2/2012) BA CK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCA L REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUA NTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

H9821023R0001

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 11 Months Language Readiness Information Services

FFP

Language Readiness Information Services in accordance with the Performance Work Statement FOB: Destination

PSC CD: DA01

NET AMT

0002 1 Unitless Travel (Do Not Propose)

T&M Language Readiness Information Services Travel in accordance with the Performance Work Statement paragraph 7.0. The contractor will be reimbursed for actual costs (no profit or fee) for government requested travel. Not to Exceed (NTE) amount will be provided at award.

TOT ESTIMATED PRICE

CEILING PRICE

0003 1 Months LRI Transition Period

FFP

Language Readiness Information Services in accordance with the Performance Work Statement paragraph 4.12 - 1 Month Transition Period

1001 12 Months OPTION Language Readiness Information Services

FFP

Language Readiness Information Services in accordance with the Performance Work Statement

1002 1 Unitless OPTION Travel (Do Not Propose)

T&M Language Readiness Information Services Travel in accordance with the Performance Work Statement paragraph 7.0. The contractor will be reimbursed for actual costs (no profit or fee) for government requested travel. Not to Exceed (NTE) amount will be provided at award.

2001 12 Months OPTION Language Readiness Information Services

FFP

Language Readiness Information Services in accordance with the Performance Work Statement

2002 1 Unitless OPTION Travel (Do Not Propose)

T&M Language Readiness Information Services Travel in accordance with the Performance Work Statement paragraph 7.0. The contractor will be reimbursed for actual costs (no profit or fee) for government requested travel. Not to Exceed (NTE) amount will be provided at award.

3001 12 Months OPTION Language Readiness Information Services

FFP

Language Readiness Information Services in accordance with the Performance Work Statement

3002 1 Unitless OPTION Travel (Do Not Propose)

T&M Language Readiness Information Services Travel in accordance with the Performance Work Statement paragraph 7.0. The contractor will be reimbursed for actual costs (no profit or fee) for government requested travel. Not to Exceed (NTE) amount will be provided at award.

4001 12 Months OPTION Language Readiness Information Services

FFP

Language Readiness Information Services in accordance with the Performance Work Statement

4002 1 Unitless OPTION Travel (Do Not Propose)

T&M Language Readiness Information Services Travel in accordance with the Performance Work Statement paragraph 7.0. The contractor will be reimbursed for actual costs (no profit or fee) for government requested travel. Not to Exceed (NTE) amount will be provided at award.

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 13-APR-2023 TO

12-MAR-2024

N/A DEF LANG NATIONAL SEC ED OFFICE

(DLNSEO)

RAOUL VICENCIO

4800 MARK CENTER DRIVE,

SUITE 08F09-02

ALEXANDRIA VA 22350

571.256.0699

HQ0054

0002 POP 13-APR-2023 TO

12-MAR-2024

N/A (SAME AS PREVIOUS LOCATION)

0003 POP 13-MAR-2023 TO

12-APR-2023

N/A (SAME AS PREVIOUS LOCATION)

1001 POP 13-MAR-2024 TO

12-MAR-2025

N/A (SAME AS PREVIOUS LOCATION)

1002 POP 13-MAR-2024 TO

12-MAR-2025

N/A (SAME AS PREVIOUS LOCATION)

2001 POP 13-MAR-2025 TO

12-MAR-2026

N/A (SAME AS PREVIOUS LOCATION)

2002 POP 13-MAR-2025 TO

12-MAR-2026

N/A (SAME AS PREVIOUS LOCATION)

3001 POP 13-MAR-2026 TO

12-MAR-2027

N/A (SAME AS PREVIOUS LOCATION)

3002 POP 13-MAR-2026 TO

12-MAR-2027

N/A (SAME AS PREVIOUS LOCATION)

4001 POP 13-MAR-2027 TO

12-MAR-2028

N/A (SAME AS PREVIOUS LOCATION)

4002 POP 13-MAR-2027 TO

12-MAR-2028

N/A (SAME AS PREVIOUS LOCATION)

PERFORMANCE WORK STATEMENT

Performance Work Statement Language Readiness Information (LRI) System

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 Information (LRI) System 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 Joint Staff, CCMDs, Services, and Defense agency representatives access to this information.

Department of Defense Instruction 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 the Defense Readiness Reporting System (DRRS). This includes reporting capability-based requirements for CCMD-specific foreign LREC capability requirements.

Department of Defense Directive 7730.65, 31 May 2018, establishes the 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 OSD, 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.

Chairman of the Joint Chiefs of Staff Instruction 3126.01B, 18 November 2020, 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.

The DoD Digital Modernization Strategy (2019) identified the Department’s goal of transforming data into actionable information while the DoD Data Strategy (2020) recognizes digital modernization as necessary to transform the Department into a data-centric enterprise.

The LRI supports these strategies using data analytics such as IBM COGNOS and will integrate large-scale analysis processes for data mining and modeling via DoD data lakes, enclaves (DRRS, Jupiter, Beacon, etc.), and other approved data sources.

3.0 SCOPE

Support the implementation, operation, sustainment, and progression of the Language Readiness Information (LRI) System 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.

The Contractor shall:

4.1.1 Ensure all personnel issued DoD Common Access Cards (CAC) have completed and are current on required DoD training. The status of personnel training will be tracked and reported as part of the Monthly Status Report (MSR).

4.2 Provide Subject Matter Expertise

Subject Matter Expertise (SME) support is essential to this effort and requires personnel with relevant advanced education, extensive knowledge of DoD readiness systems, and documented experience in supporting DLNSEO programs. The SME shall hold a Master’s Degree in Information Systems from an accredited college. The SME shall have extensive experience working with the DRRS and LRI programs to include an understanding of the processes and procedures to ensure compliance with DRRS software design and coding policies, practices and standards. The SME shall have corporate knowledge of DLNSEO programs and demonstrated experience working with DLNSEO personnel and language managers across the Department.

The SME may be called upon to provide formal training, brief senior leadership, and provide LREC research products as required.

LRI SMEs shall have a working knowledge of the DoD Analytic Agenda, the DoD Data Strategy, the Guidance for the Employment of the Force (GEF), the Defense Language Program (DoDD 5160.41E, DoDI 5160.70, DoDI 5160.71, DoDI 3300.07), the DRRS, the DoD LREC Strategic Plan, the LRI, CCMD 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 Implementation Office (DIO), the National Security Agency (NSA), the Defense Manpower Data Center (DMDC), the CCMDs, and the Services 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.

The 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, but also demonstrate 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. Research, plan, coordinate, and implement new technologies to evolve the LRI system using data-centric products and interfacing with systems that utilize data sources across the department through data mining, modeling, and predictive analytics.

4.2.5. Provide training, educational materials, briefings, and gather input from the Services, CCMDs, 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.6. LRI SMEs shall have a comprehensive understanding of the following DoD policies related to DLNSEO, LREC processes, and the LRI lifecycle:

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

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

4.2.6.3 Defense Intelligence Foreign Language and Regional and Culture Capabilities

(DoDI 3300.07)

4.2.6.4 The Department of Defense Strategic Plan for Language Skills, Regional

Expertise, and Cultural Capabilities, 2011-2016

4.2.6.5 The LREC CBRIP (CJCSI 3126.01B)

4.2.6.6 The DoD Analytic Agenda

4.2.6.7 DoD Digital Modernization Strategy

4.2.6.8 The DoD Data Strategy

4.2.6.9 The Guidance for the Employment of the Force

4.2.6.10 CCMD operational and contingency planning processes

4.2.6.11 The Universal Joint Task List

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

4.2.6.13 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.6.14 Manpower and personnel structure of DoD organizations

4.2.6.15 MS SQL

4.2.6.16 IBM Cognos

4.2.6.17 Apache HADOOP/NoSQL

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 system and its operation in DRRS. This task will include working closely with DLNSEO, the DIO, and stakeholders to resolve issues. Issues are identified through feedback, meetings, 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 sources 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 and other DoD sources. 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 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, and conduct risk mitigation.

4.3.6. Update 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 the Office of the Assistant Secretary of Defense for Readiness and how LRI can fulfill its requirements.

4.3.8. Ensure all deliverables involving coding (i.e., software) are coded in accordance with DoD, 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 to include working with data owners to ensure data quality, completeness, and accuracy.

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. LRI will allow for the management and approval of inputs from the Joint Staff, CCMDs, and the Services using the CBRIP. These tools will provide analytical products and reports based on demand signals from the CCMDs and Services.

4.5.3. Support LREC Requirements Appendices Support Services (LASS) workshops by traveling with the DLNSEO team to CCMDs and other destinations to conduct demonstration and training on LRI tools to assist in the CBRIP process.

4.5.4. Maintain and update an LRI and MS-Access CBRIP Input Tool to allow the input of fully qualified LREC needs utilizing business rules that ensure data input is accurate, correct, and will update the CBRIP database in near real time. The functionality will include features such as support for an approvals process. The MS Access database will provide a backup, stand-alone capability. The Input tools will provide data to support CBRIP reports and searches.

4.6 LREC Dashboard

The Contractor shall:

4.6.1. Create and maintain configurable and programmable dashboards utilizing widgets (a simple application that is often part of larger application already installed on the device), and visualizations for LRI users that draw together key functional processes in the LRI system. The dashboards will facilitate data analytics for LRI users across DLNSEO projects and disciplines.

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 have the opportunity to provide feedback before deployment to production.

4.7 Planner Tools

The Contractor shall:

4.7.1 Create capabilities for planners (CCMD or Component) based on input and feedback from the planner community such as the creation of a Request for Forces (RFF) that would assist and expedite RFF requests.

4.8 LRI Feedback Community

The Contractor shall:

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

4.9 DLNSEO Program Support

4.9.1 Contractor will assist and participate in meetings such as the Defense Language Action Panel (DLAP), Defense Language Steering Committee (DLSC), DLNSEO facilitated workshops, and other meetings as needed.

4.9.2 Contractor will provide updates to the Contracting Officer Representative (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 status reports, smart books, spreadsheets, In-Progress Reviews (IPR), and whitepapers to support DLNSEO efforts.

4.10 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.11 Reports

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

4.11.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.11.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.11.3 Monthly status reports containing at a minimum: status of training for contractor personnel with CACs, a description of the work completed that month for each deliverable; the work planned for the next month; and issues/concerns.

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

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

4.12 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 (thirty (30) day period prior to full performance start date) and during the transition-out-period (thirty (30) day period prior to date of contract expiration).

4.12.1 Submit and maintain a transition plan detailing all related phase-in activities and milestones to ensure successful phase-in to the DRRS operating system and the maintenance and upgrade of the LRI. 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.12.2 Perform phase-in services during the 30-day implementation period between contract award and the start of performance.

4.12.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, including the continuous development and refinement of the LRI throughout the base and option years. In accordance with paragraph 16, 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. If a deliverable due date falls on a weekend or holiday, the Contractor shall submit the deliverable on the last work day prior to the due date. In fulfillment of this effort, the Contractor shall provide the following deliverables to the COR.

Deliverable PWS Ref. Delivery Date

Software Users Guide 4.3.6 Not Later Than (NLT) 6 months after beginning of PoP and every 6 months thereafter

Briefings, demonstrations, and training

4.3.7 As directed by the COR

Educational materials, and briefing slides

4.3.7 NLT 5 business days before meeting

LRI software updates to DRRS 4.3.9 Document in MSR NLT the 15th of the month following the period reported of the successful creation, testing and upload to DRRS.

Briefing or issue paper regarding LREC data variances

4.4.2 NLT 45 calendar days after request

from the COR

Update the LRI/MS-Access CBRIP input tool for capturing fully qualified LREC needs and provide relevant reporting

4.5.4 Document in MSR NLT the 15th of

the month following the period reported of the successful creation, testing and upload to LRI.

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

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

LRI Feedback Community 4.8.1 Document in MSR NLT the 15th of the month following any action or decisions by the group.

LREC Workshops and Workgroups

4.9.1 Document in MSR NLT the 15th of

the month following the period reported of participation.

In Progress Review 4.9.2 NLT the 10th day of the month

Post-Award Conference (PAC) attendance and summary

4.10 Attend NLT 10 business days after

the contract award date, and provide summary NLT 10 calendar days after PAC

Draft Project Management Plan 4.11.1 45 calendar days after contract award

Final Project Management Plan 4.11.1 NLT 15 calendar days after Government approval of draft

Software Development Plan 4.11.2 NLT 60 calendar days after award and within 10 calendar days for each updated plan

Monthly Status Reports

4.11.3 30 calendar days after contract award and NLT the 15th day of each month until contract end

Contractor Training Status 4.11.3 As part of the MSR, 30 calendar days after contract award and NLT the 15th day of each month until contract end

Annual Report 4.11.4 NLT 10 calendar days after the base period and each option period (except last option period).

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

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

Trip Reports (TR) 7.3 Submit TR NLT the 15th of the month following period reported upon

Quality Control Plan (QCP) 10.0 NLT 60 days after award and updated as required by the COR

6.0 ANNUAL SERVICE CONTRACT REPORTING (SCR)

6.1 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via Service Contract Reporting which has replaced the legacy Enterprise Contractor Manpower Reporting Application (ECMRA). SCR is located in the System for Award Management (SAM) (https://sam.gov).

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, the reporting period for contractors in SAM is generally open from mid-October to mid-December for reporting against the prior government fiscal year, all data shall be reported no later than October 31 of each calendar year, unless a later date is otherwise authorized by the Department of Defense

7.0 CONTRACTOR TRAVEL

7.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 demonstration 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 the geographic CCMDs and are headquartered in the following locations:

U.S. Africa Command – Stuttgart, Germany U.S. European Command – Stuttgart, Germany U.S. Central Command – Tampa, Florida

U.S. Northern Command – Colorado Springs, Colorado U.S. Indo-Pacific Command – Honolulu, Hawaii U.S. Southern Command – Miami, Florida U.S. Strategic Command – Omaha, Nebraska U.S. Cyber Command– Columbia, Maryland U.S. Space Command– Colorado Springs, Colorado U.S. Transportation Command– Belleville, Illinois U.S. Special Operations Command– Tampa, Florida

The locations and schedule will be determined by the LREC Requirements Appendices Support Services (LASS) COR in coordination with the DLNSEO COR, CCMDs, stakeholder organizations (e.g., DLNSEO, Joint Staff, OUSD (I&S), Services, etc.). The LASS team anticipate travel to at least three CCMD headquarters per year and each trip is expected to last three to five business days.

7.2 The contractor will provide up to 2 developers to travel up to 6 trips per year and is expected to last up to 3 business days to the Mark Center (Alexandria, VA), during the performance of this contract to attend meetings, collaborate with DRRS-S developers, and provide technical services as required to maintain and upgrade the LRI.

Contractor costs for Government authorized travel are included in this contract. All travel shall be in accordance with FAR 31.205-46 and applicable travel regulations (Joint, Federal or Standardized). Contractor payment claims shall include applicable documentation to support actual costs incurred (e.g., airfare and hotel/lodging receipts) as well as any receipts valued at or above $75.00. Failure to provide appropriate documentation may result in loss of reimbursement of travel expenses. All Government travel requires prior approval/authorization by the COR.

7.3 The contractor shall provide a trip report to the COR no later than the 15th of the month following the completion of the travel. The report shall contain at a minimum the purpose of the trip, meeting(s) attended, as well as accomplishments and follow up actions as a result of the trip.

8.0 SECURITY

8.1 Personnel Security. Overarching security requirements are classified. The Contractor/Subcontractor personnel under this contract will require classified access to DoD network(s), Information Technology (IT) systems, Government Furnished Equipment (GFE), DOD credential, also known as the Common Access Card (CAC) for physical and logical access to federally controlled facilities and or DoD Information Systems (IS) with Personally Identifiable Information (PII) or Controlled Unclassified Information (CUI).

8.1.1 All Contractor personnel assigned to this contract are required to obtain and maintain the appropriate background investigation (BI) and adjudication or suitability determination in accordance with DODI 5200.02-DoD Personnel Security Program (PSP).

8.1.2 The contractor/subcontractor personnel on this contract will be designated a Critical Sensitive or Noncritical-Sensitive position for CLASSIFIED access as determined by the Government per position responsibilities.

8.1.3 Must have or be able to obtain a completed Tier 5 (T5) or Tier 3 (T3) an equivalent or higher BI according to the Defense Counterintelligence and Security Agency (DCSA) and the Office of Personnel Management (OPM) investigative alignment.

8.2 Security Clearances. Personnel performing on this PWS shall obtain a Secret clearance in accordance with the DD 254, Contract Security Classification Specification. The Contractor must possess or obtain a facility security clearance at the level of Secret prior to the first day of contract performance. The Contractor shall register and request security clearances through the National Industrial Security Program Central Access Information Security System (NCAISS) (https://www.dss.mil/is/ncaiss/). If subcontractors are utilized in performance of a classified contract, the Prime Contractor shall create a Subcontract DD 254 in the National Industrial Security Program Contract Classification System (NCCS). The Prime Contractor shall ensure that any teaming partners or subcontractors have the appropriate security clearances. Security Clearance Requirements:

8.2.1 All Contractor personnel requiring access to classified information will need to obtain the appropriate security clearance.

8.2.2 DHRA is not responsible for processing contractor personnel for national security clearance (Secret and Top Secret). Contractors shall follow security requirements per Code of Federal Regulations Title 32, Part 117 - Industrial Security Program Operating Manual

(NISPOM).

8.2.3 All personnel supporting this contract must have a favorably adjudicated Tier 5 or Tier 3 Reinvestigation (T5/T5R/T3/T3R) background investigation (BI) with Secret or higher eligibility or be in the process for the BI with a minimum of interim-Secret granted by the DCSA Consolidated Adjudication Services (CAS).

8.2.4 Interim Clearances (e.g., Interim-Top Secret, Interim-Secret) will be reviewed by DHRA Operations (D-OPS) Security.

8.2.5 It is the responsibility of the contractor Facility Security Officer (FSO) to notify DHRA D- OPS Security immediately if there is a change in clearance eligibility.

8.2.6 If at any time, any contractor person is unable to obtain/maintain an eligibility for access to classified information, the contractor FSO shall immediately notify DHRA D-OPS Security and DMDC Cybersecurity Division and remove such person from work under this contract.

8.2.7 A SF 312 Non-Disclosure Agreement (NDA) initiated by the company’s Facility Security Officer (FSO) is required for each of the Contractor’s personnel.

8.3 Staffing. The personnel supporting this contract requiring a DHRA sponsored CAC, access to DoD network(s), CUI/PII data or IT/Information Systems must be Citizens of the United States. This includes personnel assigned or working on the contract at any remote sites.

8.4 Onboarding. Prior to requesting access to DHRA sponsored resources (e.g., DoD credentials), IT systems, information systems, email or facility), the appointed contractor must have a favorably adjudicated T3 BI that meets the requirement for access at DHRA or be in the process of a Personnel Security Investigation (PSI) equivalent or greater in scope with a minimum of interim eligibility.

8.5 Listing of Employees. The Contractor shall maintain a current listing of employees. Within 10 calendar days of contract award, the Contractor shall provide the COR a list with the names, location of performance and clearance requirements of all company employees assigned to this effort. The list shall be validated and signed by the company DHRA Personnel Security. An updated listing shall be provided when an employee's status or information changes.

8.6 Access To Sensitive Information. To the extent that the work under this contract requires the Contractor to have access to DoD sensitive information the Contractor shall after receipt thereof, treat such information as confidential and safeguard such information from unauthorized use and disclosure. The Contractor agrees not to appropriate such information for its own use or to disclose such information to third parties unless specifically authorized by the Government in writing.

8.6.1 The Contractor shall allow access only to those employees who need the sensitive information to perform services under this contract and agrees that sensitive information shall be used solely for the purpose of performing services under this contract. The Contractor shall ensure that its employees will not discuss, divulge or disclose any such sensitive information to any person or entity except those persons within the Contractor’s organization directly concerned with the performance of the contract.

8.7 Information Technology (IT) Level Investigation Requirements. The contractor/subcontractor personnel supporting this contract will require IT-I access to DHRA IT and Information.

8.7.1 Contractor personnel, who perform work on sensitive networks, IT systems or applications, will be required to obtain and maintain the appropriate investigation and adjudication determination. The Contractor shall assure that individuals assigned to the contract undergo the respective BI and have obtained the proper eligibility, based on job function or tasks performed by the contractor personnel.

8.7.2 IT-Level position category designation does not imply or convey access to classified information.

8.7.3 The IT Level will determine the access level needed to perform work on the DoD IT Systems/Networks. The IT access level is designated based on the IT system/network requirements according to the DoD Cyber, Security Technical Implementation Guides (STIGs) https://public.cyber.mil/stigs/.

8.7.4 It is the responsibility of the contractor to ensure the employees meet the appropriate Tier investigation prior to requesting IT access. The applicable IT access levels are as follows:

8.7.5 IT- I – Privilege – High Risk: All personnel in positions in which the individual is responsible for the planning, direction, and implementation of a computer security program, which may include, but is not limited to:

• Enterprise Administrator

• Domain Administrator (AD Admin)

• Server or System Administrator

• Network Administrator

• Desktop/Workstation Administrator

• Database Design and Administration

• Database – System DBA (Sudo to Oracle, Remove Logs, Modify items that change STIG posture)

• Database – Application DBA (Select / add / update data, can deploy objects: SQL types, packages, triggers, etc.)

• Application Administrator

• Web Design and Administration

• Other: Positions with major responsibility include the direction, planning, design testing, maintenance, operation, monitoring, and/or management of systems hardware and software; or, can access a system during the operation or maintenance. (e.g., privileged access and/or systems security oversight).

8.7.5.1 Significant involvement in life-critical or mission-critical systems or relatively high risk for causing grave damage to National Security.

8.7.5.2 All personnel identified in one or more of these roles above must complete a T5/T5R, an equivalent or higher BI to meet the Special-Sensitive/Critical-Sensitive role.

8.7.6 IT-II – Authorize – Moderate Risk: All personnel in positions in which the individual is responsible for the-direction, planning, design, operation, or maintenance of a computer system, and whose work is technically reviewed by a higher authority of the IT-I to ensure the integrity of the system. All personnel identified in one or more of these job functions must complete a T3/T3R, an equivalent or higher BI to meet the Noncritical-Sensitive role. Roles may include, but are not limited to:

• Access to and/or processing of proprietary data, information requiring protection under the Privacy Act of 1974.

• Those with the ability to aggregate and extract data en masses from an automated records repository containing PII.

• Other positions designated by the Agency head that involve a degree of access to a system that creates a significant potential for damage or personal gain less than that in IT-I positions.

8.8 Personal Identifiable Information (PII) and Tier Investigations. All personnel supporting this contract must protect PII data according to the Privacy Act of 1974. Personnel requiring access to Information Technology (IT) or access to DoD Information Systems that contain military active duty, guard, or reservists’ PII or information pertaining to Service members that are otherwise protected from disclosure where such access has the potential to cause serious damage to national security, must be vetted accordingly and protect the data, including, but is not limited to the abilities and capability according to the job functions mentioned here:

8.8.1 Tier 5/Tier 5R for Special-Sensitive/Critical-Sensitive – High Risk: All personnel with administrative capabilities in a system storing PII, personnel security investigations or adjudication determination requires a Tier-5 (T5) BI.

8.8.2 Tier 3/Tier 3R for Noncritical-Sensitive – Moderate Risk: All personnel with the ability to aggregate and extract military PII en masses from an automated records repository requires at a minimum, a favorably adjudicated Tier-3 (T3) BI or equivalent.

8.8.3 Tier 1 for Non-Sensitive – Low Risk: All Personnel whose access to military PII is limited to data entry or singular search capability require, a minimum, a favorably adjudicated Tier-1

(T1) BI.

8.8.4 The Contractor shall report immediately to the DHRA Privacy Office and secondly to the COR discovery of any Privacy breach.

8.9 Controlled Unclassified Information Requirements for DoD Contractors. The following procedures will be used to protect Controlled Unclassified Information (CUI) documents and materials:

8.9.1 HANDLING: Access to CUI material shall be limited to those employees needing the material to perform their duties. The CUI marking is assigned to documents and material created by a DoD User Agency. CUI is not a classification, but requires extra precautions to ensure it is properly safeguarded and disseminated and is not released to the public without government authorization.

8.9.2 MARKING: Mark unclassified documents containing CUI: “CUI" at the top and bottom of each page, include the CUI warning box, and the CUI Designation Indicator Block as required in DoDI 5200.48. In a classified document:

8.9.2.1 Mark individual paragraph containing only CUI, but not classified material by placing “(CUI)" at the beginning of the portion.

8.9.2.2 Mark top and bottom of each page with classified material with the highest security classification of the material on the page.

8.9.2.3 If the document or material contains CUI under the category of Controlled Technical Information (CTI), use of distribution statements is required. See DoDI 5200.48.

8.9.2.4 If a classified document contains CUI material or if the classified material becomes CUI when declassified, place the following statement on the bottom of the cover or the first page under the classification marking: “NOTE: If declassified, review the document to make sure the material is not still CUI. If it does, then it must have the appropriate safeguarding, dissemination controls, and CUI markings applied.

8.9.2.5 Mark other records such as computer print outs, photographs, films, tapes, or slides in accordance with DoDI 5200.48 so the receiver or viewer knows that it contains CUI material.

8.9.2.6 Mark a message containing material in accordance with DoDI 5200.48. Unclassified messages containing CUI material must show the abbreviation (CUI) before the text begins.

8.9.2.7 Ensure documents transmitting CUI material call attention to any attachments containing

CUI.

8.9.2.8 CUI material released to a contractor by a DoD user agency must have the following statement on the front page or cover:

THIS DOCUMENT CONTAINS CUI MATERIAL AND MUST BE REVIEWED BY A

GOVERNMENT REPRESENTATIVE UNDER THE REQUIREMENTS OF DODI 5200.48,

DODI 5230.09, and DODI 5230.29.

8.9.3 STORAGE: During normal duty hours, place CUI material in an out-of-sight location if your work area is accessible to persons who do not have an authorized government purpose for access to the material. After normal duty hours, store CUI material to prevent unauthorized access. File with other unclassified records in unlocked files or desks when internal building security is provided and the file is marked as CUI. When there is no internal security, locked buildings or rooms usually provide adequate after hours protection. For additional protection, store CUI material in locked containers such as file cabinets, desks, or bookcases.

8.9.4 TRANSMISSION: CUI documents and materials may be transmitted via first class mail, parcel post or for bulky shipments-fourth class mail. Within the CONUS discussion of CUI material on the telephone is authorized if necessary for the performance of the contract and no alternative is available. Electronic transmission of CUI (voice, data, or facsimile) should be by approved secure communications systems whenever practical. If there is a fax transmission, the sender must ensure the intended receiver is available to receive it or a cover sheet will be used to allow carrying it to the final recipient to avoid unauthorized disclosure of the CUI.

8.9.5 RELEASE: CUI material shall not be released outside of the contractor’s facility except to the representative of DoD or DHRA.

8.9.6 DESTRUCTION: When the CUI material no longer meets the threshold for safeguarding and dissemination, it shall be immediately decontrolled, be processed through the records management process, and destroyed by the approved methods identified in DoDI 5200.48 precluding its disclosure to unauthorized individuals by rendering it unreadable, indecipherable, and irrecoverable.

8.10 Controlled/Restricted Areas. The Contractor shall be compliant with local procedures for entry to DHRA controlled/restricted areas where Contractor personnel will work.

8.11 Physical Security. The Contractor shall safeguard all Government property and controlled forms provided for Contractor use and adhere to the Government property requirements contained in this contract. At the end of each work day, all Government facilities, equipment and materials shall be secured.

8.12 Pass and Identification Items. The Contractor shall ensure the pass and identification items required for contract performance are obtained for employees and non-government owned vehicles.

8.13 DoD Credentials/Common Access Card (CAC). Contractor personnel who are assigned to perform work under this contract shall be suitable to obtain a DoD credential or CAC. The cost is borne by the Government.

8.13.1 Comply with HSPD-12 Personal Identity Verification (PIV) issuance requirements. Be responsible for obtaining a CAC or PIV and be in ready status prior to requesting access to DoD resources such as DoD Facilities, DoD IT/Information Systems (IS).

8.13.2 CAC Applicant supporting this contract will need to meet the following requirements:

8.13.2.1 Execute, obtain/maintain a…