H9821019R00011.docx
DOCX document 131 KB Posted
- Attached to
- Culture Ready Basics Federal contract opportunity
- Solicitation number
- H9821019R0011
- Issued by
- Defense Human Resources Activity
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| H9821019R0011_Amd_2.pdf | ||
| H9821019R0011_Amd_1.pdf | ||
| Culture_Ready_Basics_QA_RFP_H9821019R0011.pdf | ||
| Attachment_C-PRICING_TEMPLATE.xls | XLS spreadsheet |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
H9821019R0011
Section SF 1449 - CONTINUATION SHEET
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 9 |
| Months |
CultureReady Basics Support
FFP
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics in accordance with PWS section 4.0.
FOB: Destination
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
Unitless
Travel- DO NOT PROPOSE T&M A Not-to-Exceed Amount will be incorporated at contract award.
TOT ESTIMATED PRICE
CEILING PRICE
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 12 |
| Months |
| OPTION |
| CultureReady Basics Support |
FFP
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics in accordance with PWS section 4.0.
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
Unitless
| OPTION |
| Travel- DO NOT PROPOSE |
T&M
TOT ESTIMATED PRICE
CEILING PRICE
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 12 |
| Months |
| OPTION |
| CultureReady Basics Support |
FFP
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics in accordance with PWS section 4.0.
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
Unitless
| OPTION |
| Travel- DO NOT PROPOSE |
T&M
TOT ESTIMATED PRICE
CEILING PRICE
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| 12 |
| Months |
| OPTION |
| CultureReady Basics Support |
FFP
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics in accordance with PWS section 4.0.
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| OPTION |
| Travel- DO NOT PROPOSE |
T&M
TOT ESTIMATED PRICE
CEILING PRICE
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| OPTION |
| CultureReady Basics Support |
FFP
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics in accordance with PWS section 4.0.
NET AMT
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
| OPTION |
| Travel- DO NOT PROPOSE |
FFP
NET AMT
INSPECTION AND ACCEPTANCE TERMS
Supplies/services will be inspected/accepted at:
| CLIN |
| INSPECT AT |
| INSPECT BY |
| ACCEPT AT |
| ACCEPT BY |
| 0001 |
| Destination |
| Government |
| Destination |
| Government |
| 0002 |
| Destination |
| Government |
| Destination |
| Government |
| 1001 |
| Destination |
| Government |
| Destination |
| Government |
| 1002 |
| Destination |
| Government |
| Destination |
| Government |
| 2001 |
| Destination |
| Government |
| Destination |
| Government |
| 2002 |
| Destination |
| Government |
| Destination |
| Government |
| 3001 |
| Destination |
| Government |
| Destination |
| Government |
| 3002 |
| Destination |
| Government |
| Destination |
| Government |
| 4001 |
| Destination |
| Government |
| Destination |
| Government |
| 4002 |
| Destination |
| Government |
| Destination |
| Government |
DELIVERY INFORMATION
| CLIN |
| DELIVERY DATE |
| QUANTITY |
| SHIP TO ADDRESS |
| DODAAC / CAGE |
| 0001 |
| POP 30-SEP-2019 TO |
29-JUN-2020
| N/A |
| N/A |
| 0002 |
| POP 30-SEP-2019 TO |
29-JUN-2020
| N/A |
| N/A |
| 1001 |
| POP 30-JUN-2020 TO |
29-JUN-2021
| N/A |
| N/A |
| 1002 |
| POP 30-JUN-2020 TO |
29-JUN-2021
| N/A |
| N/A |
| 2001 |
| POP 30-JUN-2021 TO |
29-JUN-2022
| N/A |
| N/A |
| 2002 |
| POP 30-JUN-2021 TO |
29-JUN-2022
| N/A |
| N/A |
| 3001 |
| POP 30-JUN-2022 TO |
29-JUN-2023
| N/A |
| N/A |
| 3002 |
| POP 30-JUN-2022 TO |
29-JUN-2023
| N/A |
| N/A |
| 4001 |
| POP 30-JUN-2023 TO |
29-JUN-2024
| N/A |
| N/A |
| 4002 |
| POP 30-JUN-2023 TO |
29-JUN-2024
| N/A |
| N/A |
A. POINTS OF CONTACT:
Contracting Officer: Ralph M. Neely 4800 Mark Center Drive, Suite 03E25 Alexandria, VA 22350-4000 Email: Ralph.M.Neely.civ@mail.mil
Contract Specialist: James N. Shumway (Nathan) 4800 Mark Center Drive, Suite 03E25 Alexandria, VA 22350-4000 Email:james.n.shumway.civ@mail.mil
Contracting Officer's Representative (COR): TBD at contract award (COR) Address: TBD Email: TBD
The COR is not authorized to make any commitments or changes that will affect price, quality, quantity, delivery or any other terms and conditions of the contract. Reference DFARS clause 252.201-7000 (Contracting Officer’s Representative).
B. CONTRACT TYPE: Contract award type shall be Firm-Fixed Price (FFP).
C. PERIOD OF PERFORMANCE: The Period of Performance is one 9-month base period with four 12-month option periods.
Performance Work Statement (PWS)
CultureReady Basics
1. INTRODUCTION
The Defense Language and National Security Education Office (DLNSEO) requires development and maintenance of the web-based culture and language training tool, CultureReady Basics in a number of languages in support of the Defense Language Regional Expertise and Culture Program.
1. BACKGROUND
CultureReady Basics, was initially developed as an online training tool to support the improvement of culture education and training in the Total Force as well as support the development of culture competency in the Federal workforce. The development and evolution of the CultureReady Basics tool, featured lessons learned based on the culture competencies included in the Department of Defense Instruction 5160.70, dated December 2016. The current iteration of CultureReady Basics, incorporates a language learning component at a 2+/3 ILR proficiency level. CultureReady Basics provides online culture and language training focusing on the basic concepts of cross-cultural interactions to users in the Department of Defense and associated stakeholders. The CultureReady Basics product is embedded and accessible on the CultureReady.org website, http://www.cultureready.org/culture-language/culture-101/cultureready-basics. Historically, as part of the CultureReady basics online portal, the Government has required lesson content and associated service support for approximately two primary languages as well as government required regional language dialects support (as needed) per contract year.
3.0 SCOPE
The Contractor shall provide all personnel, management and materials necessary to develop and maintain the web-based culture and language training tool CultureReady Basics.
4.0 REQUIREMENTS The Contractor shall:
4.1. Develop lesson content for the culture and language learning tool accessible from the www.CultureReady.org website.
4.2. Collect scenarios based on interactions of at least 10 individuals who have experience living, working, or studying in areas that speak the target language.
4.2.1. Analyze the scenarios to be able to identify the culture competencies within the interactions, then map them to the competencies found in the Adaptive Readiness for Culture model, in accordance with DoDI 5160.70 Management of the Defense Language, Regional Expertise, and Culture (LREC) Program.
4.2.2. Translate all scenarios into target language.
4.3. Develop the product using target language script and narration at the ILR 2+ /3 levels in listening and reading on the Interagency Language Roundtable scale.
4.3.1. Include a translation assistance capability that gives learners the ability to request translation hints in English to assist the learner with lesson content.
4.3.3. Develop and implement a method to record the number of times that a user relies on the translation assistance. This function will be used to track how reliant the user is on the translation assistance function.
4.3.4. Incorporate images of the target area that represent what is being portrayed in the collected scenarios. Each frame must feature at least one image.
4.3.4.1. Include scenario narration with animation and moving images. .
4.4. Develop lesson content based on a learning strategy that includes exploratory learning, direct instruction, and deliberate practice. The strategy must allow learners to become familiar with the necessary information and then to reinforce and practice what they have learned.
4.5. Develop a product user’s guide in English using Adobe .pdf . Embed the user guide within the training tool so that it is accessible from a drop down menu or icon.
4.6. Provide a user feedback mechanism that specifically reflects the answers of the user upon course completion. Feedback must be accessible simultaneously by contractor and COR.
4.6.1. Include questions in a Likert Scale format as well as several open ended questions for narrative feedback for product improvement.
4.7. Enable users to save and print completion certificates.
4.8. Prepare and submit a test plan that details testing procedures for the training tool via MS Word. The COR will identify a small user group to participate in testing.
4.8.1. Provide test release notes within 10 calendar days following the completion of the testing phase, via MS Word document. The release notes must identify any known bugs in the test build and provide a plan to correct the bugs before the next testing phase or product release.
4.9. Present Interim Program Reviews (IPRs) to the COR that detail progress, activities, and any other project associated issues. For each IPR, email a power point presentation no later than two business days in advance of the scheduled IPR.
4.9.1. Provide summary notes of each IPR via MS Word document no later than three days after the meeting. The notes will detail an overview of the meeting, all actions for any issues, and the responsible entities for those actions.
4.10. Upload the completed product on the www.CultureReady.org website by working with the website content managers.
4.10.1. Provide a means to manage usage that can be tracked by government website content managers.
4.10.2. Provide usage reports to COR that shows data analytics of the CultureReady Basics product. The analytics will include:
4.10.2.1. Referral links (where are they coming from to get to each course?)
4.10.2.2. ISP locations (what cities are most frequent for site visitors? - does it correspond with certain base locations?)
4.10.2.3. Number of users accessing the course monthly
4.10.2.4. Number of users completing the course (via reaching an end page or filling out a certificate)
4.10.2.5. Indicate time spent on course for each user.
4.11. Conduct a Design Review at a location determined by the COR 45 calendar days after contract award. The Design Review must outline the overall project design process, determine a more accurate timeline of development, and provide an opportunity to verify probability outcomes for the product. The meeting must allow the COR and other stakeholders, to preview and make changes to the design plan and any other course content before the production process begins. The Design Review must be presented using a Power Point slide presentation.
4.11.1 Provide a summary report of the design review to the COR. The report will contain a list of the participants, agenda items, a summary, and action items. The summary will provide the action item discussions, and the list of action items will incorporate a list of the responsible individuals for each item and a suspense date.
4.12 Provide Transition In and Out of Contract Services
4.12.1. Transition In: The awarded contractor receives the source code from the incumbent not later than five days after contract award. Source Code is defined as Computer program written in a high-level language which is converted into machine language that can be executed directly by a computer without any conversion by a compiler. The source code is the only stage where a programmer can read and modify a computer program.
4.12.2. Transition Out: The incumbent will provide the awarded contractor with the source code for the existing Culture Ready Basics lessons not later than five days after contract award.
4.12.3. Transfer the source code electronically. Depending on the size of the file, arrangements to download the data from the incumbent will be coordinated through the COR for the awarded contractor.
4.13 Participate in a Post-Award Conference.
The meeting shall introduce the Contractor personnel and Government personnel who will be involved with the contract. The meeting shall provide the opportunity to discuss technical, management and security issues. The Post Award Conference must 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 operational plans for how they will successfully perform contract terms and conditions including all deliverable requirements.
1. DELIVERABLES
| Deliverable |
| PWS Ref. |
| Delivery Date |
| Format |
| Recipient |
| Test Plan |
| 4.8 |
| NLT 30 days before test start. |
| MS Word Document |
| COR |
| Test Plan Notes |
| 4.8.1. |
| NLT 10 days following test phase |
| MS Word Document |
| COR |
| IPR |
| 4.9. |
| Initial IPR is 30 days after Design review, subsequent IPRs every 45 days after contract award or as needed. |
| Meeting in person/Power Point Slide show |
| COR |
| IPR Notes |
| 4.9.1 |
| NLT 5 days following IPR. |
| MS Word Document |
| COR |
| Upload product |
| 4.10. |
| NLT 330 following exercising option year |
www.CultureReady.org
| Usage Report |
| 4.10.2. |
| Every 90 days after development or as requested. |
| .pdf or |
MS Word Document
COR
| Design Review Summary |
| 4.11.1. |
| NLT 5 days following Design Review meeting. |
| MS Word Document |
| COR |
| Transition In/Out |
| 4.12 |
| NLT 5 days after contract award. |
| Electronic File |
| Awarded Contractor |
| Post award conference |
| 4.13 |
| NLT 5 days after contract award. |
| Meeting in person |
| COR |
6.0 CONTRACTOR MANPOWER REPORTING
The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Defense Language and National Security Education Office via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, unless a later date is otherwise authorized by the Office of the Under Secretary of Defense (Personnel and Readiness). Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil
7.0 CONTRACTOR TRAVEL
The Government anticipates that the contractor will have to travel to support the Culture Ready Basics product. The contractor will travel to at least six conferences during the period of performance to discuss the merits of developing a culture trainer integrated with a language component. They will explain why CultrueReady Basics products are among the best culture and language training products available to organizations and stakeholders like the Department of Defense, Foreign Area Officers, language students, study abroad programs, and various anthropological and psychology organizations. The contractor will participate in the annual LREC Symposium, hosted by the Air Force Culture and Language Center in Montgomery, AL, as well as the annual conferences for American Council on the Teaching of Foreign Languages, NAFSA: Association of International Educators, the National Council of Less Commonly Taught Languages, the International Conference on Applied Human Factors and Ergonomics, and the Society for Intercultural Education, Training and Research. 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.
| 8.0 | SECURITY | The Contractor shall: |
| 8.1 | Establish appropriate administrative, technical, and physical safeguards to protect any and all nonpublic Government data to ensure the confidentiality, integrity, and availability of government data. The Contractor and all Contractor personnel with access to or responsibility for nonpublic Government data under this contract shall: |
8.1.1 Comply with:
DoD Instruction (DoDI) 8500.1, Cybersecurity The Privacy Act (5 U.S.C. 552a) DoD 5400.11-R, and DoD Directive 5400.11, DoD Privacy Program DoD 6025.18-R, DoD Health Information Privacy Regulation DoD 5200.2-R, Personnel Security Program HSPD-12, Homeland Security Presidential Directive.
8.1.2 Comply with HSPD-12 Personal Identity Verification (PIV) issuance requirements, known as the Common Access Card (CAC) and:
8.1.2.1 Be responsible for obtaining CAC or PIV ready status prior to reporting for work. At a minimum, all Contractor personnel must obtain/maintain a favorable FBI National Criminal History Check (fingerprint check), two forms of identity proofed identification (I-9 document), and submit a National Agency Check and Law Credit (NACLAC) vetting package for processing.
8.1.2.2 Be citizens of the United States.
8.1.2.3 Maintain favorable FBI National Criminal History checks and ensure completion and successful adjudication of a NACLAC as required for Federal employment.
8.2 If at any time, any Contractor personnel requiring a CAC is unable to obtain/maintain an adjudicated NACLAC, immediately notify the Requiring Activity’s Information Systems Security Group (ISSG) and remove such person from work under this contract.
8.3 Immediately report the discovery of any Privacy breach first to the Requiring Activity’s CIO/Privacy Office and secondly to the COR.
8.4 All Information Systems (IS), Platform Information Technology (PIT) and Information Technology (IT) Services or Products under this requirement, that receive, transmit, store, or process nonpublic government data must be accredited in accordance with Department of Defense (DOD) Instruction (DoDI) 8510.01 "Risk Management Framework (RMF) for DoD Information Technology (DIT)” issued March 12, 2014 (formerly the DOD Information Assurance Certification and Accreditation Process (DIACAP)). IS and PIT systems must be categorized in accordance with Committee on National Security Systems Instruction (CNSSI) 1253, implement a corresponding set of security controls from the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, and use assessment procedures from NIST SP 800-53A with additional DoD-specific assignment values, overlays, implementation guidance, and assessment procedures as required.
8.5 DoD-Controlled IS and PIT Systems operated by a Contractor or other entity on behalf of the DOD; to include contractor owned IS and PIT systems that are dedicated to DoD processing, must be authorized as DoD IS or PIT systems. The Requiring Activity’s Authorizing Official (AO) must render an authorization decision for this type of a DoD system prior to DoD use of the capability.
8.6 IT services provided by a commercial or other non-federal government entity under this requirement must ensure the security protections of the IS delivering the service is appropriate to the confidentiality, integrity, and availability needs of the Requiring Activity’s information and mission in order to be approved for acceptable use. The Government will assess the adequacy of security proposed by potential service providers, and accept the proposed approach, negotiate changes to the approach to meet DoD needs, or reject the offer. The accepted security approach will be documented and included as attachments to the resulting contract.
9.0 Mandatory Training Requirements for Contractors. Contractor employees shall complete the following mandatory trainings within 30 days of contract award and option is exercised.
1. DoD Training on Unauthorized Disclosures IAW OSD Memorandum dated September 19, 2017 and the training is available at https://securityawareness.usalearning.gov/disclosure/index.html.
1. Privacy Act and Personally Identifiable Information IAW DoDD 5400.11 dated September 1, 2011 and the training is available at https://iatraining.disa.mil/eta/piiv2/launchPage.htm.
1. IT Security Awareness IAW 5 CFR 930.301 and the training is available at https://iatraining.disa.mil/eta/disa_cac2018/launchPage.htm.
1. National Insider Threat IAW Executive Order 13587 and the training is available at https://securityawareness.usalearning.gov/itawareness/index.htm.
1. Counterintelligence Awareness and Reporting Training IAW DoDD 5240.06 and the training available at https://securityawareness.usalearning.gov/cidod.
Contractor employees shall provide a copy of each training certificate to Contracting Officer Representative (COR) to meet the mandatory training requirements. COR keeps the certificates in the COR file or CORT.
10.0 GOVERNMENT FURNISHED PROPERTY/EQUIPMENT/INFORMATION (GFP/GFE/GFI)
The Government will provide the Source Code for the existing CultureReady Basics products.
11.0 PLACE OF PERFORMANCE
The contractors will be working at the contractor’s facilities.
12.0 QUALITY CONTROL
The contractor shall implement and maintain a Quality Control Plan (QCP) to ensure work performed conforms to the scope of work and meets the requirements under this PWS. The QCP shall, at a minimum provide a method for performing inspections; identifying, correcting and preventing problems/defective service; addressing customer complaints, and improving the quality of services over the life of the contract.
13.0 QUALITY ASSURANCE
13.1. The Government reserves the right to perform random inspections and surveillance to evaluate the Contractor’s compliance to the contract terms and performance of the requirements in the PWS.
13.2. Contract Discrepancy Report (CDR). In the event of unsatisfactory contractor performance, the Contracting Officer (CO) in coordination with the Contracting Officer’s Representative (COR) will issue a CDR that will explain the circumstances and findings concerning the incomplete or unsatisfactory service. The contractor shall acknowledge receipt of the CDR and respond in writing as to how he/she shall correct the unacceptable performance and avoid a recurrence. The Government will review the contractor's corrective action response to determine acceptability and will use any completed CDR as part of an overall Contractor past performance evaluation.
14.0 ORGANIZATIONAL CONFLICTS OF INTEREST
The Contractor acknowledges that it is familiar with FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, and agrees to avoid, neutralize or mitigate such conflicts of interest in accordance with the principles set forth in the FAR. If the performance requires the Contractor (to include subcontractors) to supply technical support related to systems or projects with which the Contractor is already directly concerned, either by prime or subcontract, the Contractor shall immediately inform the Contracting Officer. The PWS may be withdrawn if a conflict is found. The Contractor shall not undertake performance of any PWS requirements which requires it to supply technical support regarding such systems until the notice is given, and written consent to proceed is issued by the Contracting Officer.
15.0 APPLICABLE DOCUMENTS
| Document |
| Web link |
DoD Instruction (DoDI) 8500.1, Cybersecurity http://www.dtic.mil/whs/directives/corres/pdf/850001_2014.pdf
DoD 5200.2-R, Personnel Security Program http://www.dtic.mil/whs/directives/corres/pdf/520002r.pdf
| CultureReady Basics |
| http://www.cultureready.org/culture-language/culture-101/cultureready-basics |
| A Model of Culture-General Competence for Education and Training: Validation Across Services and Key Specialties |
| http://www.cultureready.org/news-research/research/model-culture-general-competence-education-and-training-validation-across |
| Interagency Language Roundtable |
| http://govtilr.org/Skills/ILRscale1.htm |
1. PERFORMANCE REQUIREMENT SUMMARY (PRS)
16.1 Purpose. The PRS lists performance objectives for the required services the Government will surveil. The absence of any contract requirement from the PRS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses listed in the SF1449.
16.2 Components. The PRS states the performance objective (required service), and threshold (performance standard, accept and reject points (if applicable)) in either a qualitative or quantitative fashion for each critical success factor.
Performance Objective
PWS paragraph
Performance Standard/Acceptable Quality Level
Incentive/ Disinsentive
| Collect scenarios based on interactions of at least 10 individuals who have experience living, working, or studying in areas that speak the target language. |
| 4.2 |
| Performance is acceptable when |
· individuals provide verification of working, studying, or living in an area that speaks the target language.
· The interviewer is able to record a story of an interaction that caused the individual to make a decision.
Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
| Develop product using target language script and narration at the 2+ /3 levels |
| 4.3. |
| Performance is acceptable when: |
· all narration and script are in the target language
· meet the requirements listed on the ILR scale, http://www.govtilr.org/skills/ilrscale1.htm.
Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
| Translate all scenarios into target language. |
| 4.2.2. |
| Performance is acceptable when: |
· 100% of narration and script are in the target language
· 100% of translations meet the proficiency requirements listed on the ILR scale, http://www.govtilr.org/skills/ilrscale1.htm.
Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
| Develop lesson content |
| 4.4. |
| Performance is acceptable when: |
· Lesson content includes background of the importance of intercultural learning
· Lesson content includes learning objectives for each lesson
· Lesson content clearly focuses on the DoDI 5160.70 Section 8 Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
| Develop a product users’ guide |
| 4.5. |
| Performance is acceptable when: |
· Users’ guide has step by step instructions for using the CultureReady Basics trainer
· Users’ guide is embedded and accessible in the trainer
· Users’ guide is able to be downloaded from the trainer into .pdf Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
| Prepare and submit a test plan that will detail testing procedures |
| 4.8. |
| Performance is acceptable when: |
· testers are identified
· Plan provides a feedback methodology that allows the person being tested to record any issues that occur during the testing period and make comments.
Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
Provide quarterly usage reports to COR.
| 4.10.2. |
| Performance is acceptable when: |
1. The reports indicate amount of times the CultureReady Basics site http://www.cultureready.org/culture-language/culture-101/cultureready-basics, was accessed
1. the reports shows which courses were accessed
1. the reports shows which courses were completed Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
Develop and submit all required deliverables
| 5.0 |
| Performance is acceptable when: |
1. 100% of deliverable requirements are met and received on time
1. critical information is accurate Document past performance, paying particular attention to performance that meets the standard/ when performance is identified below standard for any reporting period, increase surveillance or contractor reporting.
Instructions to Offerors
0. SAM: Any Offeror that submits a proposal in response to this solicitation must be registered in the System for Award Management (SAM), in accordance with FAR Clause 52.232-33 and DFARS Clauses 252.201-7000 and 252.204-7004 Alt A, prior to contract award. Registration information can be found at: https://www.sam.gov/portal/public/SAM/.
0. Communications: This is a Request for Proposal potential offerors shall address questions, concerns, or requests for clarification in writing via email to the Point of Contacts below no later than 12:00 PM Eastern April 25, 2019. Questions received after this date may not be answered. DHRA/PK assumes no responsibility for non-delivery due to technical difficulties.
Nathan Shumway Contract Specialist James.N.Shumway.civ@mail.mil Ralph Neely Contracting Officer Ralph.M.Neely.civ@mail.mil
0. Proposal Submissions:
All proposal submissions in response to this solicitation must be received no later than the date and time shown in block 8 of page 1. Proposals received after the aforementioned date and time will not be evaluated; therefore, not considered for award. No electronic submissions will be accepted. Proposals shall be submitted to the following address:
DHRA PKEA
Attn: James Shumway Solicitation No. H9821019R0011 4800 Mark Center Drive, Suite 03E25 Alexandria, VA 22350-4000
NOTE: If hand delivering a proposal, contact the Contract Specialist via email at least three business days prior to the due date for delivery instructions. No electronic submissions will be accepted.
0. Proposal Page Size and Format: A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8½ x 11 inches. Pages shall be single-spaced and typed, except for displays and the reproduced sections of the solicitation document. The font shall be Times New Roman and no less than 12 point in size. Use a 1 inch margin all the way around. Pages shall be numbered sequentially by volume. When text is included within displays, it may be no smaller than 8 point, but must be clearly legible without magnification, as determined solely by the Contracting Officer (CO). The size of the displays shall not exceed the page size as defined above.
Quote Organization
| VOLUME |
| RFQ Para # |
| VOLUME TITLE |
| COPIES |
| PAGE LIMIT |
| I |
| 5 |
| Business and Pricing |
| One original and one copy |
| No page limit |
| II |
| 6 |
| Technical |
| One original and three copies |
| 35 pages inclusive of TOC, Appendices, attachments |
| III |
| 7 |
| Past Performance |
| One original and three copies |
| 15 pages inclusive of TOC, Appendices, attachments |
0. The Offeror shall submit one original copy, one hardcopy, and one CD of Volume I. The Volume shall include:
1. VOLUME I – Business and Pricing: Offeror shall submit one copy of Volume I. This volume shall include:
0. Signed copy of the Standard Form 1449, with blocks 17 and 30 completed.
0. Signed copy of the Standard Form 30 of any amendments issued against this RFP.
0. Offeror’s DUNS number, Cage Code, and Tax ID number.
0. Completed Representations and Certifications of Offeror (FAR Clause 52.212-3 Alt I).
0. All fill-in clauses that require an Offeror’s response.
0. Price Proposal: This volume shall include
5. The Offeror shall use Pricing template in Attachment C of this RFP. All pricing proposed by the Offeror shall be Firm-Fixed Price. As supporting documentation to the prices proposed, the Offerors shall include a description of the labor categories proposed, fully burdened labor rates for each labor category, and the number of labor hours proposed for each labor category for the base period and all option periods.
5. Price Evaluation Approach: The Government will evaluate price for award purposes by adding the total of all CLIN prices, including the government ceiling travel amount for the base period and all options. The Offeror’s total price for the purpose of evaluation shall be calculated by adding the total price for the base period, 1st Option Period, 2nd Option Period, 3rd Option Period, 4th Option Period plus the six months option to extend services per FAR clause 52.217-8. The optional six month period shall be calculated by adding one-half of the fourth option period price.
5. Proposed price will be reviewed to determine if the price is adequate, complete, and reasonable to assess the Offeror’s understanding of the Solicitation.
0. The Offeror shall submit one original copy, three hardcopies, and one CD of Volume II. In total, the page count for this volume shall not exceed 35 single-sided pages.
A. VOLUME II – Technical Proposal: Offeror shall submit one original, three hardcopies, and one CD of Volume II. This volume shall include:
i. Technical. This section shall address the Offerors technical capability of meeting the requirements of the PWS and Evaluation factors included in this solicitation.
The proposal shall address the following elements: Technical Approach and Methodology, Program and Project Management Plan, and Staffing Plan. The proposal will demonstrate the Offerors ability to comprehend and understand the Government’s requirements as set forth in the technical portion of the PWS. This will be expressed through the presentation and understanding and explanation of how all associated “Tasks” expressed in the PWS will be provided.
0. Volume III: Past Performance Proposal: The Offeror shall submit one original copy, three hardcopies, and one CD of Volume III. In total, the page count for this volume shall not exceed 15 single-sided pages.
A. Offerors shall submit no more than three (3) relevant Past Performance references. All references shall address current projects or those completed within the last five (5) years from the date of solicitation issuance by the Offeror as a prime contractor.
For each reference being submitted, complete and include a Past Performance Relevancy Questionnaire (PPRQ) found at Attachment B. Complete and submit one PPRQ per contract reference. Offerors shall include no more than one contract for each reference. The Government will only review one reference per contract. If the Offeror submits more than one contract for each reference; those contracts will not be reviewed by the Government. NOTE: If you have a Contractor Performance and Reporting System (CPARS) in the last 5 years in reference to any PPRQ (Attachment B), the Government will not issue to the named reference a past performance questionnaire. The government will retrieve and assess annual CPARS ratings from the system.
The Government will utilize the information submitted from Attachment B to obtain additional performance information on the Offeror. Subcontractors Past Performance will not be reviewed for Attachment B; therefore the Government is only reviewing Past Performance from Offerors who performed work as prime contractor. Should the Offeror possess no relevant past performance, a written statement shall be provided by the Offeror so indicating. In this case, the Offeror will not be evaluated favorably or unfavorably on past performance and will be assigned a rating of Unknown Confidence.
0. In addition to these requirements, provide the following on the cover page of each volume:
1. Solicitation title and number, H9821019R0011;
1. Name, address, and contact information of Offeror;
1. Name of volume;
1. Date of offer and validity date.
(END OF INSTRUCTIONS TO OFFERORS)
Attachment A: Evaluation Factors, Criteria, and Rating Methods
1.0. INTRODUCTION.
1.1. The Government will evaluate all proposals in accordance with the factors and criteria established in the evaluation criteria and in the Request for Proposal (RFP). The criteria provide the basis upon which each evaluation will be based, are established before receipt of the proposals, and are intended to ensure that the evaluation will be a structured process employing equitable measures. Proposals will be evaluated and a contract awarded under the Best Value Continuum approach, to the responsible Offeror whose offer is considered the most advantageous to the Government, price and other factors considered.
1.2. The Government intends to evaluate proposals and make award without discussions. The Government reserves the right to conduct discussions if the Contracting Officer later determines discussions to be necessary.
1.3 Offerors are cautioned that “parroting” of the PWS with a statement of intent to perform does not reflect understanding of the requirement or capability to perform.
2.0. EVALUATION FACTORS
2.1. Technical.
2.1.1. The purpose of the technical factor is to assess the offeror’s proposed approach, as detailed in its proposal, to satisfy the Government’s requirements. There are many aspects which may affect an offeror’s ability to meet the solicitation requirements to include technical approach, risk, management approach, personnel qualifications, facilities, small business participation and others. The evaluation of risk is related to the technical assessment.
2.1.2. Risk assesses the degree to which the offeror’s proposed technical approach for the requirements of the solicitation may cause disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Risk will be assessed as one aspect of the technical factor rating.
2.1.3. Any proposal receiving a rating of “Marginal or “Unacceptable” is deemed to have a risk that is so high that award cannot be made against the proposal and the proposal will not be further evaluated.
2.2. Past Performance.
2.2.1. The Past Performance Evaluation results in an assessment of the offeror’s probability of meeting the solicitation requirements, based on past performance information. The Performance Confidence Assessment rating is assessed as an overall factor after evaluating aspects of the offeror’s recent past performance, focusing on performance that is relevant to the technical factors and cost or price.
2.2.2. Recency refers to the state or quality of being current. The more recent the contract, the greater the likelihood that the offeror has the capacity to perform in a like manner. Information regarding contract performance that is recent and has a logical connection with the matter under consideration indicates relevancy.
2.2.3 Relevancy (1) Similarity in services, (2) Complexity, (3) Dollar Value, (4) Contract Type, and (5) Experience with translating the English language into a different language at the appropriate ILR levels.
The Government will evaluate the complexity in relation to managing the development of an online training product focusing on Language, Regional Expertise, and Culture (LREC) subject matter. The Government will focus on the ability to manage a project that relies heavily on information collection and analysis, but also has the capability to perform challenging tasks with language translation to the necessary Interagency Language Roundtable (ILR) levels. Per the solicitation the SSEB will not evaluate the past performance or cost for any proposal receiving a technical rating of “Marginal” or “Unacceptable”
3.0. EVALUATION FACTOR CRITERIA
3.1. Criteria for Technical Factor
Element A: Technical Approach and Methodology
i. The Offeror must clearly demonstrate that they have the adequate capabilities to develop an online culture and language training product of this magnitude in accordance with the performance work statement. The Government will evaluate the extent of the Offeror’s capabilities based on depth and thoroughness of the proposal. The proposal must include a plan or methodology for meeting the requirements in accordance with the performance work statement, not just state that the Offeror is able to meet the requirements.
ii. PWS 4.1.1. The Government will evaluate the methodology the Offeror states in the proposal to meet the language requirement in accordance with the PWS. The Offeror must demonstrate its capability to translate the English language to the target language at the appropriate levels.
iii. PWS 4.2.1. The Government will evaluate the Offeror’s stated ability and procedures to analyze scenarios and identify the competencies found in the Adaptive Readiness for Culture (ARC) model. The Government will ensure that the Offeror’s proposal issues a plan to map the competencies from the interactions to the ARC model.
Element B: Program and Project Management Plan
The Government will evaluate the Offeror’s capability to provide complete program management support that fully integrates, manages, controls and documents all phases of contract requirements. The project management plan must demonstrate the Offerors support throughout the project development cycle. The project management plan must demonstrate the ability to collect, analyze, and identify phases described under PWS 4.2/4.2.1, and the translation phases of the project described under PWS 4.1.1./4.2.2. The Offeror must be able to document the development progress to include thorough feedback for interim project reviews as well as throughout product testing.
Element C: Staffing Plan
The Government will evaluate the Offeror’s proposed staffing plan with focus on the experience of the Scientist, the Senior Scientist, and the Target Language SME(s). The Government will evaluate management experience and the offerors proposed plan to oversee proper staffing. The Government will concentrate on the capabilities of the Scientists with regards to their experience and knowledge of the Adaptive Readiness for Culture model, and the DoD culture learning programs (PWS 4.2.1.). The Government will evaluate the staffing plan to ensure that the proposal identifies the Target Language SME(s) necessary to translate and develop the script and narration of the product into the necessary ILR levels (PWS 4.2.2./4.1.1.).
3.2. Criteria for Past Performance Factor Confidence Assessment. The Government will conduct a performance evaluation based upon the past performance of the offerors performing major or critical aspects of the requirement as it relates to the probability of successfully performing the solicitation requirements.
3.2.1. The Government will consider each offeror’s demonstrated, current, relevant record of performance in supplying products and services that meet the contract’s requirement. Contracts completed within the last 3 years from the date of solicitation issuance shall be considered recent.
3.2.2. In conducting the performance risk evaluation, the Government may use data provided by the offeror and data obtained from other sources it considers current and accurate, including the Past Performance Information Retrieval System (PPIRS).
3.3. Criteria for Price Factor. This factor will be evaluated utilizing proposal analysis techniques identified in FAR 15.404-1. The analysis will be conducted on the total price of the basic contract to include the base and option periods.
1. The Government anticipates adequate price competition will establish fair and reasonable price, however the Government may use one or more of the following price analysis techniques to determine price reasonableness:
· Comparison of prices to other price proposals.
· Comparison of proposed prices to the independent government cost estimate.
· Review of commercially published pricing for similar services to requirements in this RFP.
· Review of current or recent contract pricing arrived at through competitive procedures for services similar to those in this RFP.
4.0. ORDER OF IMPORTANCE.
4.1. Proposals will be evaluated based on best value to the Government using the trade-off approach. For this solicitation, factors are listed below in descending order of importance. Price will be evaluated separately and will not be scored.
| 1. Technical |
| 2. Past Performance |
| 3. Price |
4.2. Technical and Past Performance, when combined, are more important than price.
1. RATING METHODS
5.1. Technical Factor: One of the following ratings will be assigned:
TECHNICAL RATINGS
| Rating |
| Definition |
| Outstanding |
| Proposal indicates an exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low. |
| Good |
| Proposal indicates a through approach and understanding of the requirements and contains at least one strength, and risk of unsuccessful performance is low to moderate. |
| Acceptable |
| Proposal meets requirements and indicates and adequate approach and understanding of the requirements and risk of unsuccessful performance is no worse than moderate. |
| Marginal |
| Proposal has not demonstrated and adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high. Any proposal receiving this rating will not be further evaluated. |
| Unacceptable |
| Proposal does not meet requirements of the RFQ, and thus, contains one or more deficiencies, and/or risk of unsuccessful performance is unacceptable. Proposal is unawardable. Any proposal receiving this rating will not be further evaluated. |
5.2. Past Performance Factor – Recency, Relevancy and Confidence Assessment:
5.2.1 Recency: an assessment of the past performance information will be made to determine if it is recent. To be recent, the effort must be ongoing or must have been performed during the past three (3) years from the date of issuance of this RFP. Recency will receive a rating of either “RECENT” or “NOT RECENT” as shown in the table below.
One of the following Recency ratings will be assigned:
RECENCY ASSESSMENT
| Rating |
| Description |
| RECENT |
| Performance was provided within the past years 3 years (Based on the issue date of this RFP.) |
| NOT RECENT |
| Performance was provided outside of the past 3 years (Based on the issue date of this RFP.) |
5.2.2. Relevancy: The Government will review attachment B and evaluate relevancy to the products/services performed under those contracts to determine if they relate to the Performance Work Statement and assign one of the following relevancy ratings. In determining relevancy for individual contracts, consideration will be given to the effort, or portion of the effort, being proposed by the Offerors whose contract is being reviewed and evaluated. Past performance information will be deemed “very relevant, relevant, somewhat relevant or not relevant.
One of the following Relevancy ratings will be assigned:
PAST PERFORMANCE RELEVANCY RATINGS
| Rating |
| Definition |
| Very Relevant |
| Present/past performance effort involved essentially the same magnitude of effort and complexities this solicitation requires as outlined in section 2.2.3 of the evaluation factors. |
| Relevant |
| Present/past performance effort involved much of the magnitude of effort and complexities this solicitation requires as outlined in section 2.2.3 of the evaluation factors. |
| Somewhat Relevant |
| Present/past performance effort involved some of the magnitude of effort and complexities this solicitation requires as outlined in section 2.2.3 of the evaluation factors. |
| Not Relevant |
| Present/past performance effort did not involve any of the magnitude of effort and complexities this solicitation requires as outlined in section 2.2.3. |
5.2.2. The combination of relevancy and recency, and performance documented by the information collected by the Government, results in the selection of a performance confidence assessment as outlined below.
PERFORMANCE CONFIDENCE ASSESSMENTS
| Rating |
| Description |
| Substantial Confidence |
| Based on the offeror’s performance record, the Government has a high expectation that the offeror will successfully perform the required effort. |
| Satisfactory Confidence |
| Based on the offeror’s performance record, the Government has an expectation that the offeror will successfully perform the required effort. |
| Limited Confidence |
| Based on the offeror’s performance record, the Government has a low expectation that the offeror will successfully perform the required effort. |
| No Confidence |
| Based on the offeror’s performance record, the Government has no expectation that the offeror will successfully perform the required effort. |
| Unknown Confidence |
| No relevant performance record is available or the offeror’s performance record is so sparse that no meaningful confidence assessment rating can be reasonably assigned. |
5.3. Price Factor: Price proposals will not be rated.
Attachment B
PAST PERFORMANCE RELEVANCY QUESTIONNAIRE (PPRQ)
1. Contractor (name, address, email and telephone number):
2. Name of Contract Awarding Activity / Agency and Project Title:
3. Contract Number and name, address, email, telephone number, of the awarding activity’s Procuring Contracting Officer and the Contracting Officer’s Representative (and other references – e.g. Administrative Contracting Officer – if applicable):
4. Type of Contract: Fixed Price_____ Cost_______ *IDIQ_______ *In the event a reference is a task order awarded under an IDIQ contract, for the purposes of past performance relevancy determination, each task order must be submitted on one attachment B form and will be reviewed, considered and rated the same as one contract reference.
5. Contract dollar value Base Period Total:
Option Periods Total:
Total Current Contract Value (base period and all exercised options):
*Contract # and Task Order #:
6. Period of Performance (PoP) Base period PoP:
Option periods PoP:
Total PoP of base and all exercised option periods:
7. Scope of work and complexity/diversity of tasks performed:
8. Skills/expertise required:
9. Relevancy of work:
(END OF ATTACHMENT B)
CLAUSES INCORPORATED BY REFERENCE
| 52.202-1 |
| Definitions |
| NOV 2013 |
| 52.203-3 |
| Gratuities |
| APR 1984 |
| 52.203-12 |
| Limitation On Payments To Influence Certain Federal Transactions |
| OCT 2010 |
| 52.204-4 |
| Printed or Copied Double-Sided on Postconsumer Fiber Content Paper |
| MAY 2011 |
| 52.204-7 |
| System for Award Management |
| OCT 2016 |
| 52.204-9 |
| Personal Identity Verification of Contractor Personnel |
| JAN 2011 |
| 52.204-10 |
| Reporting Executive Compensation and First-Tier Subcontract Awards |
| OCT 2016 |
| 52.209-6 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.