PWS.docx
DOCX document 58 KB Posted
- Solicitation number
- W911QX-22-R-0021
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Synopsis (RFI).doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Base Performance Work Statement (PWS) Technology Transition Training June 2022 Background The Army Research Lab (ARL) Strategic Partnerships Office launched the Mission Transition program in 2021 through award of W911QX-21-F-0145 as a pilot program with a focus on providing skill sets needed to aid ARL researchers in transitioning their technology. Transitioning technology is taking research from the very basic proof of concepts organizations typically accomplish to the next stage of development and eventually to other partner offices and organizations who can transition into programs of record. Through the training provided under that order, researchers have been introduced to basic principles that will help them to communicate more effectively, identify potential customers, conduct interviews, understand customer needs, understand the value proposition of their technology, how it will be used, who will use it, and determine the next steps. A major focus of the training is helping researchers and technologists develop relationships with key stakeholders, to understand their needs and help shape research programs to achieve the greatest potential of transition. The provided training under this award will expand and extend that pilot training, as well as center on teaching scientists and researchers how to become their own best advocates for transitioning their technology and defining their transition pathway.
Objective The Government requires technology transition training covering multi-faceted topics conducted via a variety of methods and formats and provided to a varying number of employees at a time. The training methods and arrangements are provided as a broad assortment of strategies that Requiring Activities will be able to purchase as needed via specific orders that combine one or more methods to meet specific needs. The training provided will build upon the training already accomplished via the pilot program conducted under the prior order and will allow specific organizations outside ARL to also award orders off of this vehicle, which will provide an overall benefit to the Government as it strives to further develop its technology for practical use in the field. Goals for the training program will focus on encouraging researchers/scientist to apply intrapreneurial and human-centered approaches to improve outcomes; empower laboratory scientists, tech specialists and researchers with tools, approaches and processes to better align innovation to end user needs; and improve opportunities for commercialization, tech transfer and transition.
Requirement The Contractor shall provide the following technology transition training and guidance to the awarding agency of each Task Order (TO) per the specific requirement stated in each TO. Quantities and delivery periods for requirements in C.3 will be specified in each TO. Locations where the services are needed will be specified in each TO. The location and method for training will be tailored to the need of each specified task, remaining flexible in order to accommodate remote, in-person and/or potential for extended site visit activities with key stakeholders. Communication will occur between the contractor and COR to establish a channel of communication between the Government and the contractor.
TRAINING TYPE #1: Intrapreneurship Seminar Series & Webinar Workshops The Contractor shall provide remote webinar training that is made available to an open audience across the organization. The webinars shall be one hour in length. The Contractor shall ensure this instructional series provides attendants with the principals of intrapreneurship, technology transfer, and transition best practices. The Contractor shall provide a series of webinars applicable towards a general audience of multiple skill levels, where attendees will obtain learning on independent topics and some that build upon previous sessions. These sessions will be designed to expand researchers’ skill sets and processes to develop compelling and timely plans to advance their technologies. The Contractor shall provide a certificate of competency to attendees that complete the webinar series.
TRAINING TYPE #2: Deep Dive Innovation Cohort Training Program The Contractor shall provide an in-depth, multi-week structured training programs for specific cohorts of employees chosen by the Government to participate. The program shall be an immersive experiential process aligned to cohort participant’s individual needs and leverage intrapreneurial processes and techniques to further their solution development. The Contractor shall ensure the support is tailored for the specific technology or project the cohort members are focusing on, to include transition planning support. The Contractor shall ensure the training programs consist of multiple sessions split between lecture and break-out rooms for participants to receive one on one coaching support to practice material and review status of accomplishments. Sessions must address design thinking, customer discovery, implementation of agile methodologies, and other lean startup practices to align participants technologies to multiple users needs and commercialization opportunities. The Contractor shall provide sessions on stakeholder and customer discovery, effective communication, pitch training and relationship building skills for the cohort’s projects. The multi-week program must culminate with a pitch competition for cohort members.
TRAINING TYPE #3: Entrepreneur-in-Residence Training The Contractor shall provide entrepreneur-in-residence training in the form of direct support and advice for individual identified technology projects and the teams working those projects. The Contractor shall ensure this consulting team service facilitates on-demand, flexible innovation support at any stage of the innovation cycle and is focused on providing assistance as needed to assist with transition pathway definition. The Contractor shall advise on transfer planning, customer discovery, prototyping, business model development, and transfer pipeline acceleration. The Contractor shall respond to ad hoc requests for advice from project team members. The Contractor shall regularly review progress, accomplishments, and make recommendations for next steps and potential pivots in strategy. The Contractor shall support logistical and outreach tasks with outside organizations to establish interviews and meetings with potential key partners. The Contractor shall ensure this training offers immediate feedback, advice, best practices, and direction in support of the teams working the selected projects during key tasks and at specific milestones.
TRAINING TYPE #4: On-Demand Team-Based Training and Support The Contractor shall provide up to a specific amount of hours of customized training support through on-demand and tailored full-service discovery support utilizing individual, sprint based, and immersive formats that require researcher participation to lead actual interviews. The Contractor shall provide ad hoc training and support that includes a range of customer discovery topics to include securing interviews, interview best practices, ecosystem development, pattern finding analysis, tech transition model creation, pitch preparation and value proposition creation. The Contractor shall develop training that aids Government employees in identifying key stakeholders, conducting effective interviews, and making sense customer data to increase evidence-based understanding and reducing burden on the researcher. The Contractor shall design team-based sessions and workshops to facilitate, explore and generate focus on understanding different customer personas, problem solving, and solution generation. The Contractor shall provide training support to increase evidence-based learning and increase outcomes in customer discovery through varied team-based exercises.
TRAINING TYPE #6: Immersive Customer Discovery Experiences The contractor shall support logistical and outreach tasks with outside organizations to establish interviews and meetings with potential key partners. The Contractor shall work with the Government to coordinate experiential learning experiences with key stakeholders, users, industry and academic partners that can help research/technical staff appreciate stakeholder perspectives and identify pathways for transition. This includes outside visits to Military installations, Innovation Centers or other stakeholder locations as applicable. The Contractor shall arrange opportunities for stakeholder discovery and facilitate introductions that can be instrumental to laboratory staff program growth and transition.
TRAINING TYPE #7: Experiential Workshops The Contractor shall develop experiential workshops, with the duration specified per task order, that facilitates off campus real-world immersive sessions and workshops designed to increase research staff understanding of key areas and personnel that align to tech transfer and transition goals. The Contractor shall lead set-up and coordination of immersive activities in various formats that can include trend safaris, innovation lab tours, entrepreneur immersion, warfighter immersive sessions, tours and interviews at stakeholder locations/facilities designed to increase the collision of scientific staff and key stakeholders with a goal of facilitating relationship building through experiential learning that will increase tech development and transition outcomes.
TRAINING TYPE #8: Ad Hoc Custom Assignments The Contractor shall lead the setup, coordination (of fully scoped and approved custom projects that meet the clients’ requirements with a focus on improving impact), outcomes, and best practices for technology transition. Ad hoc assignments can include benchmarking, case study development, roadshows, and other activities that address issues facing tech transfer, transition, and organizational outcomes. The expected participant commitment is approximately ½ day to 2 days with a duration of assignment to be determined per order.
TRAINING TYPE #9: Situational Cohorts The Contractor shall provide coaching and guidance in the support of a portfolio of relevant trainings to meet researchers where they are in their program life cycle and can be tailored as necessary per order. Format of these cohorts may be varied and include varying services such as providing pitch training for internal or external research funding opportunities, instructional sprints focused on discovery/team launch ideation/leadership development, Hackathon support, and can be instructional in nature. The duration of this training can be 1-4 weeks for approximately 10-20 hours in length. The Contractor shall ensure the value of this training is focused on generating higher quality outcomes and include one on one coaching on relevant goals.
Capturing Metrics The Contractor shall capture the identified metrics in each order and provide all metric data per the delivery method and timeframes identified in each order, with the overall goal of using the metrics to measure training effectiveness and employee improvement. In addition to delivering metric data, the Contractor shall provide suggestions for improvement based upon the metric data captured.
Summary Reports C.3.10.1 The Contractor shall provide summary reports, as required per task order, that document relevant metrics and track progress of employees and cohorts who have participated in the training. The Contractor shall ensure the reports also contain the specific information and data as identified in each task order.
AT/OPSEC
C.4.1 Access and general protection/security policy and procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.
C.4.2. For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.
C.4.3 For contractors that DO NOT require CAC, but require access to a DoD facility or installation. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local Security policies and procedures (provided by Government Representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.
Duty Time The services to be performed under this contract shall be performed during normal Government working days, Monday through Friday except for Federal Holidays, between the hours of 0700 to 1600 local time. If services are scheduled by the Contractor to be performed on a regular federal holiday (see below), or one designated by Presidential proclamation, rescheduling shall be at the discretion of the Contracting Officer’s Representative (COR) and requires written approval.
New Year’s Day January 1* Martin Luther King’s Birthday 3rd Monday in January Presidents Day 3rd Monday in February Memorial Day Last Monday in May Juneteenth June 19th Independence Day 4 July* Labor Day 1st Monday in September Columbus Day 2nd Monday in October Veterans Day 11 November* Thanksgiving Day 4th Thursday in November Christmas Day 25 December*
*The holiday is observed on the preceding Friday or the following Monday when the holiday occurs on Saturday or Sunday, respectively.
C.6 Government Furnished Property (GFP)/ Government Furnished Equipment (GFE) / Government Furnished Information (GFI)
GFP, GFE, or GFI may be provided to the Contractor by the Government to facilitate performance of the individual orders under this contract. Should such circumstances arise, GFP/GFE/GFI will be addressed in each individual TO. The Contractor is required to furnish all materials and information needed to accomplish performance that are not identified and provided as GFP/GFE/GFI C.7 Identification of Contractor Employees:
All Contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel will be required to obtain and wear badges appropriate for the facility they are performing.
C.8 HSPD-12
C.8.1 Routine access to Government-controlled facilities is required. CAC cards will be provided to Contractor personnel as needed.
C.8.2 Access to Government-controlled information systems will be required as directed in each task order.
C.8.3 The Contractor shall ensure HSPD-12 standards are followed and met throughout performance.
C.8.4 Only Federal Information Processing Standard Publication (FIPS 201) products and components will be issued to Contractor employees.
C.8.5 Contractors shall return Government-issued IDs and building passes upon completion of the contract or as directed by the Contracting Officer.
C.9 Implementation of Enhanced Security Protections for Contractor Information Systems C.9.1 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews Within thirty (30) days of contract award, unless otherwise notified by the Government, the Contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the Contractor's facility. The SSP(s) shall describe how the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 security requirements are implemented as required by Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract, and identify all applicable Commercial and Government Entity Code codes affected. The Contractor shall fully cooperate in the Government's review of the SSPs at the Contractor's facility.
If the Government determines that the SSP(s) does not adequately describe how the NIST SP 800-171 security requirements are implemented, then the Government shall notify the Contractor of each identified deficiency. The Contractor shall correct any identified deficiencies within thirty (30) days of notification by the Government. The contracting officer may provide for a correction period longer than thirty (30) days and, in such a case, may require the Contractor to submit a Plan of Action and Milestones (POAM) for the correction of the identified deficiencies. The Contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.
Upon conclusion of the correction period, the Government may conduct a followon review of the SSP(s) at the Contractor's facilities. The Government may continue to conduct follow-on reviews until the Government determines that the Contractor has corrected all identified deficiencies in the SSP(s).
The Government may, in its sole discretion or in response to a cyber incident, conduct subsequent reviews at the Contractor's site to verify the information in the SSP(s). The Government may conduct reviews at any time upon thirty (30) days' notice to the Contractor.
C.9.2 Compliance to NIST SP 800-171 The Contractor shall fully implement the Controlled Unclassified Information (CUI) Security Requirements (Requirements) in NIST SP 800-171 in effect at the time the solicitation is issued or as authorized by the Contracting Officer, or establish a SSP(s) and POAMs) that varies from NIST SP 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.
Notwithstanding the allowance for such variation, the Contractor shall identify in any SSP and POAM their plans to implement the following, at a minimum:
Implement Requirement 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, a combination of physical and logical protections acceptable to the Government may be substituted;
Implement Requirement 3.1.5 (least privilege) and associated Requirements, and identify practices that the Contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;
Implement Requirement 3.1.12 (monitoring and control remote access sessions)-Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods;
Audit user privileges on at least an annual basis;
Implement Requirement 3.13.11 (Federal Information Processing Standards (FIPS) 140-2 validated cryptology or implementation of National Security Agency- or NIST-approved algorithms (i.e., FIPS 140-2 Annex A: Advanced Encryption Standard (AES) Or Triple Data Encryption Standard (DES) or compensating controls as documented in a SSP and POAM));
Implement Requirement 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation which can be evaluated by the Government Program Manager for risk to the program;
Implement Requirement 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.
C.9.3 Cyber Incident Response:
The Contractor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period in DFARS clause 252.204-7012 ), deliver all data used in performance of the contract that the Contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact. Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media available at http://www.acq.osd.mil/dpap/dars/pgi/docs/lnstructions_for_Submitting_Media.docx. In delivery of the incident data, the Contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.
If the Contractor subsequently identifies any such data not previously delivered to DC3, then the Contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the Contractor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.
C.9.4 Army Counterintelligence (Cl) Outreach The Contractor shall engage, whenever practicable, with Army Cl industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting Army programs and technologies; and make Contractor personnel available for threat briefings specific to foreign intelligence threats to Army programs and technologies.
C.9.5 Army Cl/Industry Monitoring In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the Contractor shall cooperate with the Army Cl, which may include cooperation related to: threat indicators; pre-determined incident information derived from the Contractor's infrastructure systems; and the continuous provision of all Contractor, subcontractor, or vendor logs that show network activity, including any additional logs the Contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.
If the Government determines that the collection of all logs does not adequately protect its interests, the Contractor will coordinate with Army Cl to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by the Army Cl, on the Contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an Army Cl network device shall be the subject of a separate agreement negotiated between Army Cl and the Contractor. In the alternative, the Contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by Army Cl. Use of this alternative approach shall also be the subject of a separate agreement negotiated between Army Cl and the Contractor.
In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.
C.10 Travel The contractor shall notify the COR if travel is required for each TO and any reimbursable travel will require authorization from the COR prior to the travel date.
Contracting Officer:
image1.emf image2.emf
File details come from the government source that posted it. Updated .