OPI PWS (FY21-26) Ready.docx

PERFORMANCE WORK STATEMENT (PWS)

Oral Proficiency Interviews (OPI)

PART 1

GENERAL

1. Contract: This is a non-personnel services contract to provide Oral Proficiency Interviews (OPI). Contract service providers shall be accountable solely to the Contractor who in turn is responsible to the government.

1.1. Description of Services/Introduction: Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Oral Proficiency Interview Testing services as defined in this Performance Work Statement except for those items specified as government furnished property and services. Contractor shall perform to the standards in this contract.

1.2. Background: The Department of Defense (DoD) launched the Defense Language Transformation Initiative in 2004 with the objective of improving the Armed Forces’ capacity to work effectively with international partners. In January of 2005, the Defense Language Transformation Roadmap was published requiring that the Department of Defense and its components train and maintain personnel with language skills capable of responding for operations with the correct levels of proficiency. In August 2005, the Undersecretary of Defense for Personnel and Readiness (OUSD) (P&R)) issued a memorandum tasking the Defense Language Institute Foreign Language Center (DLIFLC) to program funds for test development and field testing. DoD Directive (DoDD) 5160.41E and TRADOC Regulation 350-70 charged DLIFLC with overseeing the standardization, testing, research, development and evaluation of all foreign language training and education.

The requirements for foreign language testing have increased exponentially. Many more end-users, external to DLIFLC, continue to request Oral Proficiency Interviews. DLIFLC needs to continue serving these end-users by covering current and anticipated testing needs for the foreseeable future.

1.3. Objectives:

(a) Oral Proficiency Interviews (OPI) Testing

(b) OPI Quality Control Services

(c) OPI web-based system for request submission, scheduling, tracking, rating rationale, and reporting of test results

1.4. Scope: Contractor shall provide the following services:

1.4.1. Telephonic Oral Proficiency Interviews (OPI) Testing Services.

1.4.1.1. Contractor shall train OPI testers and provide OPI testing for 107 languages. Each test shall result in a speaking score based on the ILR scale, and some will require a Participatory Listening score (LPT) as well.

1.4.1.2. Contractor shall conduct up to 16,000 OPIs over a one-year period.

1.4.1.2.1. Tier 1 languages: 12,000 OPIs

1.4.1.2.2. Tier 2 languages: 3,500 OPIs

1.4.1.2.3. Tier 3 languages: 500 OPIs

1.4.1.3. Contractor shall provide up to 9,000 Participatory Listening Scores (PLS) over a one-year period.

1.4.2. OPI Quality Control Services (QC).

1.4.3. English Translations of OPIs.

1.4.4. Recruitment and scheduling of language experts for low-density language testing using Alternative/Guided OPIs.

1.4.5. Secure OPI tracking, scheduling, and reporting interface with IT support.

1.5. Period of Performance: The period of performance shall be for one (1) Base Year of 12-months and four (4) 12-month Option Years.

1.6. General Information.

1.6.1. Quality Control: Contractor shall develop, implement and maintain an effective Quality Control System which includes a written Quality Control Plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance to ensure all contract requirements are met. Contractor’s QCP must contain a systematic plan to monitor operations to ensure acceptable services are provided to the government. The QCP, as a minimum, shall address continuous process improvement, procedures for scheduling, conducting, and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints. Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. Contractor’s QCP is the means by which the Contractor validates that the work complies with the requirement of the contract. Contractor shall provide a report on monthly testing events, including number of splits/retests by language. Contractor-initiated norming sessions will be documented and a report provided to DLIFLC. Contractor shall provide to the government access to any and all documented rationales for OPI ratings not later than six (6) business days after the testing event. Contractor shall provide to the government access to all test audio files within one business day after the testing event. Contractor shall use the official government OPI review form when reviewing tests. Guidance using this form may be provided. QCP is to be delivered within thirty (30) days after contract award. Three copies of a comprehensive written QCP shall be submitted to the KO and COR within five (5) working days when changes are made thereafter. Any proposed changes by the government to the QCP after acceptance shall be submitted to the Contractor in writing by the KO. Contractor shall ensure services are performed in accordance with this PWS.

1.6.2. Quality Assurance: Contractor performance shall be evaluated in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). The standards for surveillance will derive, in part, from the Contractor’s QCP and in part from standards imposed by the government for functionality. Contractor, upon request by the government, shall revise final test results, conduct retests, or perform test reviews.

1.6.3. Methods of Surveillance: Contractor overall performance shall be evaluated using periodic and random inspection methods of surveillance. Contractor timeliness for test scheduling, test administration and the posting of test results shall be evaluated and monitored 100% of the time. Contractor test reviews shall be inspected 100% of the time for accuracy. Contractor ratings shall be monitored using random methods of inspection for accuracy.

1.6.4. Federal Government Holidays:

1.6.5. Hours of Operation: Contractor is responsible for conducting examinations any day of the week except Federal holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government directed facility closings. Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.6. Place of Performance: Work shall be performed from anywhere in the Continental United States (CONUS), Alaska, Hawaii and U.S. territories.

1.6.7. Type of Contract: The government will award an Indefinite Delivery/Indefinite Quantity (IDIQ) type of contract.

1.6.8. Security Requirements:

1.6.8.1. Contractor personnel performing work under this contract must maintain a current listing of employees. The list shall include the employee's name, social security number and all information required for background checks to meet installation access requirements to be accomplished by the installation Security Office if contract work involves unescorted entry to government restricted areas or other sensitive areas designated by the installation commander. For each employee, the Contractor shall provide the type and date of federal background investigation conducted on each designated employee. If no investigation has been conducted, the DLIFLC will conduct a background investigation (NACI or NACLC) in order to determinate eligibility for government access. The list shall be provided to the Program Manager and sponsoring agency’s Security Manager. An updated listing shall be provided when an employee's status or information changes.

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

1.6.8.3. Retrieving Identification Media: Contractor shall retrieve all identification media, including vehicle passes from employees who depart for any reason before the contract expires; e.g. terminated for cause, retirement, etc.

1.6.8.4. Traffic Laws: Contractor and its employees shall comply with post traffic regulations.

1.6.8.5. Weapons, Firearms, and Ammunition: Contractor employees are prohibited from hand carrying weapons, firearms, or ammunition, to include on the contract-owned vehicle or privately-owned vehicle while on the Presidio of Monterey or any other federal installation.

1.6.8.6. For Official Use Only (FOUO): For Official Use Only (FOUO). Contractor shall comply with DOD 5400.11-R, DoD Privacy Act Program and DoD 5400-7-R, DoD Freedom of Information Act (FOIA) Program, requirements. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

1.6.8.7. Reporting Requirements: Contractor personnel shall report to an appropriate authority any information or circumstances of which may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information. Contractor employees shall be briefed by the immediate supervisor upon initial on-post assignment.

1.6.8.8. iWatch Training Requirements: Contractor will facilitate and track completion of annual in- person "iWatch Training for Contractors" for all assigned contract personnel via DLIFLC or Garrison Antiterrorism Officer (ATO). Contractor shall encourage personnel to report suspicious activity and/or stolen equipment. Contractor will provide a roster of attendees, then ATO will certify this attendee roster for the Contractor to provide to the COR no more than 10 days after project start. Individual records will be updated to reflect completion of the iWatch training.

1.6.8.9. Operational Security (OPSEC) and Training: Contractor shall be trained and practice good OPSEC to protect critical information for specific government contracts and subcontracts within 14 calendar days after contract start date or effective date of incorporation of this requirement into the contract, or within 30 calendar days of their reporting for duty. Contractor shall submit certificates of completion for each affected contractor and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training.

1.6.8.10. FPCON Charlie and/or Delta: During FPCONs Charlie and Delta, non-mission essential services may be discontinued. The Installation Commander (or DLIFLC Commandant) or their designee, will notify the COR when to resume services once the FPCON level is reduced to level Bravo or lower.

1.6.8.11. Database Security: Contractor shall use and implement current industry and DOD security standards for obtaining and maintaining personal data. All test tracker interface and databases shall meet these security parameters. Contractor shall store and maintain data according to Risk Management Framework (RMF) for DoD Information Technology (IT) Instruction Number 8510.1, March 12, 2014, DoD Cloud Computing Security Requirements Guide (SRG), and DoD Memorandum – Updated Guidance on Acquisition and Use of Commercial Cloud Services. Government security standards regulating the usage of commercial platforms and the storage of government data is subject to change.

1.6.8.12. Physical Security: Contractor shall be responsible for safeguarding all government property and controlled forms provided for contractor use. At the end of each work period, all government facilities, equipment, and materials shall be secured.

1.6.8.13. Key Control: Not applicable.

1.6.9. Special Qualification: Not applicable.

1.6.10. Post Award Conference / Periodic Progress Meetings: Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The Contracting Officer (KO), Contracting Officers Representative (COR), and other government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the contracting officer will apprise the Contractor of how the government views the Contractor's performance and the Contractor will apprise the government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

1.6.11. Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: performs inspections necessary in connection with contract performance: maintains written and oral communications with the Contractor concerning technical aspects of the contract: issues written interpretations of technical requirements, including Government drawings, designs, specifications: monitors Contractor's performance and notifies both the Contracting Officer (KO) and the Contractor of any deficiencies; coordinates availability of government furnished property, and provide a site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.12. Key Personnel: The following personnel are considered key personnel by the government: Contract Manager/Alternate Contract Manager, Quality Manager, Automated Systems Manager, Test Management and Proficiency Standards Division Director /Associate Directors and Assistant Dean. Contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the KO. The contract manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate shall be available between 7:00 a.m. to 4:00p.m. (Pacific Standard Time) Monday through Friday, except Federal holidays or when the government facility is closed for administrative reasons.

1.6.13. Identification of Contractor employees: All contract personnel attending meetings and working in other situations where the Contractor status is not obvious to third parties are required to be identified as such to avoid creating an impression in the minds of members of the public that contract personnel are Government officials. Contractor must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.14. Contractor Travel: Contractor may be required to travel CONUS and within the NCR during the performance of this contract to attend meetings, conferences, and/or training. Contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. Contractor shall be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval/ authorization and notification to the COR. The work to be performed under this contract shall be performed from anywhere in the Continental United States (CONUS), Alaska, Hawaii, and U.S. territories.

1.6.15. Other Direct Costs: All non-conducted testing when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings on day of testing shall be charged at the No-Show rate per test, which is determined by the OPI testing method (Telephonic or alternate mediums). Changes to the testing schedule that results in additional costs for the above reasons must be pre-approved by the KO. Any additional costs once testing resumes must be pre-approved by the KO.

1.6.16. Data Rights: The Government has unlimited rights to all documents/material/data/files produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.17. Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may stipulate other remedies as deemed necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.18. Phase In / Phase Out Period: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the sixty (60) days, phase in / phase out period. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

PART 2

DEFINITIONS & ACRONYMS

2. Definitions and Acronyms:

2.1. Definitions:

2.1.1. Alternate/Guided OPI: A guided OPI using a DLIFLC or Contractor OPI trainer to guide a qualified Linguist through an oral interview with examinee.

2.1.2. Contractor: A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.3. Contracting Officer (KO): A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.4. Contracting Officer’s Representative (COR): An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.5. Defective Service: A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.6. Deliverable: Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.7. Key Personnel: Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.8. ILR Scale: Interagency Language Roundtable language proficiency scale provides descriptions of language proficiency levels. Levels range from “0” (no proficiency) to “5” (equivalent of a highly educated native speaker).

2.1.9. Interagency Language Roundtable Level Descriptions: Guide used for testers which contains detailed Skill Level Descriptions from level 0 to level 5.

2.1.10. Linguist: A person skilled in foreign languages.

2.1.11. Minor Modifications to Interface: Small changes to the OPI Tracking Interface System made by Contractor at the request of DLIFLC in order to better support end-users needs.

2.1.12. New Language Learner: Any examinee who is not a native or heritage speaker and is deemed to be below Level 3 in proficiency.

2.1.13. OPI Authorization & Reporting Web-Based System: Secure interface maintained and modified by Contractor to support DLIFLC’s OPI scheduling, tracking and score reporting.

2.1.14. Oral Proficiency Interview (OPI): A Government approved method of testing an individual’s speaking proficiency. The telephonic OPI will be scored asynchronously by two raters.

2.1.15. Participatory Listening Score: A second score derived from the OPI, one that will match the OPI score assigned.

2.1.16. Physical Security: Actions that prevent the loss or damage of Government property.

2.1.17. Quality Assurance: The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.18. Quality Assurance 3rd/4th Rating: A documented review of an OPI done to ensure the accuracy of the original rating.

2.1.19. Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.20. Quality Control: All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.21. Rater/Reviewer: Qualified Oral Proficiency Tester capable of issuing an ILR-based score.

2.1.22. Subcontractor: One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.23. Tester Feedback: Official or unofficial comments pertaining to any OPI test. Contractor shall provide Tester Feedback only when requested by DLI.

2.1.24. Test Iteration: A specific testing timeframe or window when a series of tests are conducted.

2.1.25. Tester Trainer: Experienced OPI tester of the language, who is able to guide less experienced testers through OPI procedures and able to act as the second rater in cases where only one native speaker is available to test.

2.1.26. Tester Training Workshops: Contractor or Government workshops designed to train new OPI testers, provide recertification training to certified testers, and to re-establish Norming standards.

2.1.27. Work Week: Monday through Friday, unless specified otherwise.

2.2. Acronyms:

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. Government Furnished Items and Services:

3.1. Services: Not applicable

3.2. Facilities: Not applicable

3.3. Utilities: Not applicable

3.4. Equipment: Not applicable

3.5. Materials: Not applicable

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. Contractor Furnished Items and Responsibilities:

4.1. General: Contractor shall furnish all supplies, equipment and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2. Secret Facility Clearance: Not applicable

4.3. Materials: Contractor shall furnish materials, supplies, and equipment necessary to meet the requirements under this PWS.

4.4. Equipment: Contractor shall furnish all equipment to meet the requirements under this PWS.

PART 5

SPECIFIC TASKS

5. Specific Tasks:

5.1. Basic Services: Contractor shall provide services for:

5.1.1. OPI Testing Services: Contractor shall identify, establish, and maintain cadres of certified OPI testers in all of the languages listed in Table A 5.1.2..

5.1.2. Table A

5.1.3. All languages serviced shall be categorized into 3 Tiers. Each Tier shall be assigned a specific CLIN and unit price. See Table A 5.1.2. for languages organized by Tier.

5.1.4. The list in Table A 5.1.2. is not inclusive and is subject to change. The COR will submit any language change that affects the positioning in the Tier structure to Contractor when required.

5.1.5. Contractor shall have 120 days to recruit, train and hire additional testers if the language shift requires larger tester cadres. Contractor shall have 120 days to recruit, train and hire a replacement tester(s) in the event of loss of a tester(s). Contractor shall have 120 days to recruit, train and hire new testers if a new language(s) testing requirement is needed. The contract will be modified to reflect these changes.

5.1.6. OPI Tester Training and Certification:

5.1.6.1. Contractor shall ensure all OPI testers employed under the contract are trained to adhere to the Interagency Language Roundtable (ILR) scale and DLIFLC’s OPI Testing protocols. The ILR scale is the Government authorized standard of rating factors from which OPI proficiency garnered.

5.1.6.2. Contractor shall conduct OPI norming workshops for testers in the languages specified in Table A 5.1.2. as needed. The COR and Government representatives may meet with the Contractor’s OPI Tester Trainers in person at DLIFLC, and/or video/telephone conference in order to provide performance feedback and clarification.

5.1.6.3. DLIFLC OPI subject matter experts (SME) shall meet with Contractor’s OPI Tester Trainers and specified OPI testers a minimum of three (3) Norming Summits per year. Each Tester Trainer or tester recommended by DLIFLC as requiring specific training shall attend at least one (1) of the Norming Summits. The Norming Summits will be either in person at DLIFLC or at a designated Contractor site.

5.1.6.4. The Government may require Contractor to travel to the DLIFLC to provide a familiarization session to DLIFLC OPI SMEs on the Contractor’s OPI training methods. The session may be broken into two parts, each lasting 5 days. Contractor shall expect up to twenty (20) DLIFLC SMEs per session.

5.1.6.5. For Faculty Personnel System (FPS) applicants, Contractor testers shall be at minimum of 3+ or the equivalent level in the target language.

5.1.6.6. Contractor Tester Trainers will receive guidance from DLIFLC subject matter experts covering the procedures involved in the Alternate/Guided OPI. For an outline of the Alternate/Guided OPI process and associated questions, see Attachment.

5.1.6.7. All OPI Contractor testers shall consistently meet the minimum PWS accuracy requirements. If the tester continues to fail in meeting the minimum testing standards, the tester is to be barred from testing under the auspices of this contract.

5.1.6.8. Contractor shall document and provide a plan to redress the performance of an OPI Contractor Tester who receives up to three (3) validated examinee complaints.

5.1.6.9. Contractor shall conduct performance evaluation sessions for Contractor testers when requested by the Government.

5.1.6.10. Contractor shall conduct up to three (3) annual general re-norming summits with Contractor tester trainers and testers. The Government will select languages targeted for re-norming for each summit.

5.1.6.11. Contractor shall conduct two (2) annual ILR elicitation Contractor/DLI SME workshops.

5.1.6.12. Contractor shall provide upon request a report of OPI Tester norming sessions.

5.1.7. Tester Quantities and Tester Availability:

5.1.7.1. Minimum number of testers and tester availability for each language is as defined in Table B 5.1.7.2.

5.1.7.2. Table B

(**) Contractor shall report on which 45 of the 54 languages are to be supported as of day 14.

5.1.7.3. Contractor shall have 120 days to recruit, train and hire additional testers if a language(s) shifts from one Tier to another Tier and requires larger tester cadre.

5.1.7.4. Contractor shall have 60 days to recruit, train and hire a replacement tester(s) in the event of loss of a tester(s) for Tier 1 languages.

5.1.7.5. Contractor shall have 90 days to recruit, train and hire a replacement tester(s) in the event of loss of a tester(s) for Tier 2 languages.

5.1.7.6. Contractor shall have 120 days to recruit, train and hire a replacement tester(s) in the event of loss of a tester(s) for Tier 3 languages.

5.1.7.7. Contractor shall have 120 days to recruit, train and hire new testers if a new language(s) testing requirement is needed. The contract will be modified to reflect these changes.

5.1.7.8. Contractor shall have 120 days to hire and train new tester(s) when the Government specifies a particular region/dialect/accent for a language listed on Table A 5.1.2..

5.1.7.9. Contractor shall notify the COR immediately when there is a loss of language testing capability. Contractor shall provide the COR with a written update every month on the status of re-establishing minimum testing capability.

5.1.8. Scheduling:

5.1.8.1. Contractor shall schedule an OPI and notify the requestor a minimum of five (5) business days prior to a stipulated testing date made by the requestor.

5.1.8.2. An OPI request that does not stipulate a particular date, but rather a broader set of dates or test window, Contractor shall schedule an OPI and notify the requestor a minimum of five (5) business days prior to the first available day of the timeframe.

5.1.8.3. Contractor shall schedule an OPI and notify the requestor a minimum of two (2) weeks prior to the start date of any testing iteration.

5.1.8.4. If a language not listed on Table A 5.1.2. is requested, Contractor shall begin the process of scheduling the test as Alternate/Guided OPI as per agreement with the Government.

5.1.9. Testing:

5.1.9.1. Contractor shall provide telephonic OPI modality testing per Government request.

5.1.9.2. Contractor shall provide OPI testing for 107 languages. Each test shall result in a speaking score based on the ILR scale, and some will require a Participatory Listening score (LPT) as well.

5.1.9.3. Contractor shall conduct up to 16,000 OPIs over a one-year period.

5.1.9.3.1. Tier 1 languages: 12,000 OPIs

5.1.9.3.2. Tier 2 languages: 3,500 OPIs

5.1.9.3.3. Tier 3 languages: 500 OPIs

5.1.9.4. Contractor shall provide up to 9,000 PLSs over a one-year period.

5.1.9.5. Contractor Tester shall conduct no more than six (6) OPI tests per day.

5.1.9.6. Contractor shall provide a quarterly statistical report on all testing events as specified by the Government.

5.1.10. Posting Final Scores:

5.1.10.1. Contractor shall provide a final score(s) no more than five (5) business days after test date.

5.1.10.2. For DLIFLC’s resident students, final scores shall be provided within 24 hours after OPI exam but not to exceed two (2) business days.

5.1.11. Contractor shall record all OPIs conducted. The recordings shall be maintained for the duration of the contract.

5.1.12. Language Tiers:

5.1.12.1. Each of the 107 languages shall fall under one of three (3) Tiers and be assigned to a Tier-specific CLIN pricing.

5.1.12.2. The list in Table A 5.1.2. is not inclusive and is subject to change.

5.1.13. Substitute Languages:

5.1.13.1. The Government may request an OPI for a mission-critical language(s) not listed on Table A 5.1.2.. Such a language requested shall be considered a Tier 3 language.

5.1.14. Contractor shall document each OPI conducted. Documentation shall include a score and ILR rational.

5.1.15. Reporting Requirements:

5.1.15.1. Contractor shall submit monthly/quarterly reports about the activities related to deliverables in the following areas:

5.1.15.1.1. Telephonic Oral Proficiency Interviews (OPI) Testing Services

5.1.15.1.2. Contractor shall provide any and all information related to Contractor testing and processed test requests, to include individual tester/rater (s) assigned score and rating rationale for each finalized record. Data will include a Tester/Rater identification number. Contractor, upon request by the government, shall provide test audio files for training and norming purposes.

5.1.15.1.3. OPI Quality Control reviews as stated in the Performance Requirements Summary (PRS) document.

5.1.16. Contractor shall provide a Participatory Listening Score for examinee(s) when requested by the Government. The PLS will match the OPI score up to the proficiency level determined by the Government. Contractor shall notify the Government prior to posting if the OPI score is higher than the PLS.

5.1.17. Contractor shall provide quality control non-Contractor reviews per Government request.

5.1.18. Contractor shall provide English Translation of an OPI test(s) upon request by the Government.

5.1.19. Contractor shall conduct an Alternate/Guided OPI when a language requested by the Government is not on the current Tiered language list, or when there are no fully trained testers available for the target language in the timeframe requested by the end-user. For low-density languages, the Contractor may utilize the language expertise of a third party to perform a guided OPI. These third-party language experts are not required to attend the Contractor’s OPI tester training program.

5.1.20. OPI Tracking Interface System Functional Requirements:

5.1.20.1. Contractor shall provide a fully functional secure web-based OPI request tracking system that shows all tests requested, scheduled, scores pending and final ratings for requests. The site shall also include a calendar listing of all available testing dates per language. When testing occurs prior to the website being accessible to the Government, scores will be posted to a secure environment authorized by the Government.

5.1.20.2. Contractor shall provide additional customizations to the OPI Tracking Interface per Government’s request as needed. Customizations shall be completed within four (4) weeks of Government request.

5.1.20.3. Contractor shall also provide General IT support via the Technical Help Desk on an as needed basis. The billing will be on a monthly basis and will be in 30-minute segments, with the total blocks rounded up to the nearest hour.

5.1.20.4. Contractor shall use and implement current industry and DOD security standards for obtaining and maintaining personal data. All test tracker interface and databases shall meet these security parameters.

5.1.20.5. Contractor shall store and maintain data according to Risk Management Framework (RMF) for DoD Information Technology (IT) Instruction Number 8510.1, March 12, 2014, DoD Cloud Computing Security Requirements Guide (SRG), and DoD Memorandum – Updated Guidance on Acquisition and Use of Commercial Cloud Services.

5.1.20.6. Government security standards regarding commercial platforms and storage of Government data shall be adhered to at all times.

5.1.20.7. Contractor shall have an interface that assigns authorized account holder identification.

5.1.20.8. The interface shall be able to accept, receive and process electronic requests from authorized holders.

5.1.20.9. The interface should be able to assign or forward requests to designated testing resources.

5.1.20.10. The Government should be able to view the request testing status and retrieve test ratings that were assigned to testing resources.

5.1.20.11. Contractor shall provide a Language Availability List.

5.1.20.12. The interface should be able to generate statistical reports and run queries as needed by the Government.

5.1.20.13. The interface shall provide the ability for authorized account holders to submit requests or orders for single or multiple tests, check test status and retrieve test schedules and test information, receive final results (or can be blocked) and ability to print DLIFLC Score Report or other Certificate (can be blocked).

5.1.20.14. The interface shall provide the ability for posting testing and rating information, viewing and retrieving scheduled OPIs, displaying a list of tests to be 3rd or 4th rated, providing functionality for testers and raters to add ratings and rating comments, filling-out rating grids, etc.

5.1.20.15. OPI Interface Business Flow:

1. Requesting Official submits request for approval.

2. Service Approving Authority approves or denies request.

3. Processor forwards approved request to appropriate testing resource based on testing requirements.

4. Scheduler coordinates testing schedule and allocates testing date.

5. Test score data is posted to interface for approval.

6. Test score data reviewed, approved, and released.

7. Requesting Official retrieves score report.

5.1.20.16. Access Roles:

(a) Site Security Manager (Administrator): Able to view, authorize, edit, assign, activate, deactivate all user accounts. The administrator shall be able to perform all functions assigned to all access levels.

(b) Service Approving Authorities (SAA): Views, approves/disapproves all requests and views all final results under the account.

(c) Processor: Views all submitted requests and assigns testing resource based on language requested.

(d) Scheduler: Views assigned requests and allocates testing dates.

(e) Score Reporter: Input test result data and submits for approval.

(f) Score Approval: Reviews and approves/disapproves final scores for release to Requesting Officials.

(g) Requesting Official: Submit requests and view request status at any stage (submitted, approved, scheduled, released scores). Print finalized score report.

5.1.20.17. Functions and Features:

(a) Interface and Database Security: Access to the interface shall initiate with a warning notice, requiring users to consent to governmental monitoring of activities and stated compliance and stated compliance with the terms of accessing the system containing sensitive but unclassified (SBU) and privacy act data. Multi-level user security shall ensure that sensitive data are only accessible by authorize users and that functionalities are authorization dependent.

(b) User Authorization and Authentication: All end-user accounts shall be approved by the Government site-security manager and password protected.

(c) User Management: Tasks and functions within the interface will be determined by a user’s access level, which are controlled by the Site Security Manager role.

(d) Tracking: User activities should be tracked and logged in such a manner that it is auditable and retrievable.

(e) Reporting: Requires ability to report and display test score data. Requester shall have the capability to view and print final score reports in PDF format.

5.1.20.18. Monitoring Requirements:

(a) Interface will be available 24/7.

(b) Interface will enable audit tracking.

(c) Interface will uniquely identify users and user activities.

5.1.20.19. Interface shall be in compliance with all Federal, DOD, Department of the Army, and Army Training and Doctrine Command Information Systems Standards, including, but not limited to FIPS publication 140-2, DOD Instruction 8500.1, DODD 8000.01, DODD 8115.01, DODD 8190.1, Army Certificate of Networthiness (CoN) and US Army Regulations 5-12, 25-1, 25-2, and 700-127, to include any additional approval processes.

5.1.20.20. Contractor shall provide the ability for raters to listen to the interview recordings.

5.1.20.21. Contractor shall make available to the Government the rating history of any rater upon request.

5.1.20.22. Contractor shall provide to the Government a 100% backup copy of data download of all obtained personal information and test data that has been stored on the test tracker database on a yearly basis or upon request.

5.2. Deliverables:

5.2.1. Within sixty (60) days of the contract award date, Contractor shall be prepared to schedule, test, report scores, and perform Quality Control reviews.

5.2.2. Within seven (7) days of the contract award date, Contractor shall attend an on-site, teleconference, and post-award meeting at DLIFLC. The mode of the meeting will be decided by the COR.

5.2.3. Within fourteen (14) days of the contract award date, Contractor shall provide a list of the tester names and languages for each of the three (3) Tiers.

5.2.4. Within fourteen (14) days of contract award date, Contractor shall have a secured environment authorized by the Government. Such secure environment shall allow for the posting of the scores and for the Government to run queries against on a temporary basis.

5.2.5. Contractor shall have fourteen (14) days to be able to process single or multiple tests requests. The process includes entering single or multiple tests requests, receiving and processing test requests, scheduling a test, assigning reviewers to a test, finalizing test score, running reports and generating official Score Reports.

5.2.6. Contractor shall provide the ability to generate a range of adaptable and sortable reports: schedules, ratings, tester, language, etc. that can be saved, emailed or printed, and the ability to provide accounting functions.

5.2.7. Contractor shall provide an OPI tracking interface system that is password secure. The system shall be able to maintain language, tester, client and appointment databases.

5.2.8. Contractor shall have the ability to create new hierarchical “accounts” for new locations with main roll-up, i.e., Marines and then all Marine locations.

5.2.9. The OPI tracking interface system shall be compatible with the Government hardware and software system.

5.2.10. Contractor shall provide access to the OPI interface system and the user manuals to the Government.

5.2.11. Contractor shall provide Technical Help Desk (8a.m. to 7 pm. EST) for the site.

5.2.12. Contractor shall provide Quality Control (QC) reports to the Government on the last day of each month outlining the results of the Contractor’s reviews.

5.2.13. Contractor shall provide the Government with copies of all QC rating worksheets, when requested.

5.2.14. Contractor shall provide recordings of Contractor tests to be posted to the secure environment within twenty-four (24) hours upon completion of the OPI test.

5.2.15. Contractor shall transfer all data and recordings to the Government no later than forty-eight (48) hours prior to the conclusion of the contract Period of Performance (PoP). Contractor shall also submit a written statement that all data and recordings have been transferred.

5.2.16. Contractor shall destroy all data and recordings outside the Government control no later than ten (10) days after the conclusion of the contract. Contractor shall also submit a certificate of destruction or equivalent that all data and recordings have been destroyed.

5.3. Contractor Management Reporting (CMR): The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. Contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil. The required information includes:

(a) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also known as the Contracting Officer’s Representative (COR)

(b) Contract number, including task and delivery order number

(c) Beginning and ending dates covered by reporting period

(d) Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data

(e) Estimated direct labor hours (including sub-Contractors)

(f) Estimated direct labor dollars paid this reporting period (including sub-Contractors)

(g) Total payments (including sub-Contractors)

(h) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different)

(i) Estimated data collection cost

(j) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information)

(k) Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website)

(l) Presence of deployment or contingency contract language

(m) Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country) As part of its submission, the Contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a Contractor’s system to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website.

PART 6

APPLICABLE DOCUMENTS / PUBLICATIONS

6. Applicable Documents / Publications (Current Editions)

6.1. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures.

6.1.1. Interagency Language Roundtable (ILR) Level Descriptions (See Attachment)

6.1.2. Process for Conducting ILR Alternative/Guided OPIs (See Attachment)

6.1.3. DLIFLC OPI 3rd/4th Rating Form (See Attachment)

6.1.4. The Directorate of Testing will provide additional documents to Contractor as needed.

6.1.5. Risk Management Framework (RMF) for DoD Information Technology (IT) Instruction Number 8510.1, March 12, 2014 (See Attachment)

6.1.6. DoD Cloud Computing Security Requirements Guide (SRG) (See Attachment)

6.1.7. DoD Memorandum – Updated Guidance on Acquisition and Use of Commercial Cloud Services (See Attachment)

PART 7

ATTACHMENT / TECHNICAL EXHIBIT LISTING

7. Attachment / Technical Exhibit List:

7.1. Attachment 1 / Technical Exhibit 1 – Performance Requirement Summary…