19-233-SOL-00098_000002.pdf
PDF 2 MB Posted
- Attached to
- Intelligent Automation/Artificial Intelligence (IAAI) solutions, services and products Federal contract opportunity
- Solicitation number
- 19-233-SOL-00098
About this file
Amendment 000002
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 19-233-SOL-00098_IAAI_Award_Notice.pdf | ||
| Attachment_J.3_-_HHS_Subcontracting_Plan_Template.docx | DOCX document | |
| 19-233-SOL-00098_Responses_to_Questions_Version_2.pdf | ||
| Attachment_J.3_-_HHS_Subcontracting_Plan_Review_Form.docx | DOCX document | |
| 19-233-SOL-00098_000001.pdf | ||
| 19-233-SOL-00098_000002_track_changes.pdf | ||
| 19-233-SOL-00098_Responses_to_Questions.pdf | ||
| 19-233-SOL-00098_Responses_to_Questons_Notice.pdf | ||
| 19-233-SOL-00098_BASE.pdf | ||
| IAAI_Cover_Letter_19-233-SOL-00098.pdf | ||
| Attachment_J.1_-_Past_Performance_Questionnaire.docx | DOCX document | |
| Attachment_J.2-__Pricing_Scenario_and_Instructions.xlsx | XLSX spreadsheet |
Show all 12
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
(x)
19-233-SOL-00098
x x
1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT
THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
x
DAM
Bethesda MD 20814 8th Floor 7700 Wisconsin Avenue
DHHS/PSC/AMS/DAM
01/28/2019000002
13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
FACILITY CODE CODE
10B. DATED (SEE ITEM 13)
10A. MODIFICATION OF CONTRACT/ORDER NO.
9B. DATED (SEE ITEM 11)
9A. AMENDMENT OF SOLICITATION NO.
CODE
8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)
7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY
PAGE OF PAGES
4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)
1. CONTRACT ID CODE
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
01/10/2019
CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
E. IMPORTANT: Contractor is not, is required to sign this document and return __________________ copies to the issuing office.
ORDER NO. IN ITEM 10A.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
The purpose of Amendment 000002 is to provide the Government's responses to questions received from potential offerors. As a result of the Q&A, the solicitation has been revised and is enclosed with this Amendment (see track changes and clean versions). Also enclosed with this modification is Attachment J.3 HHS Subcontracting Plan Review Form, as indicated in the Responses to Questions and the revised solicitation.
All other terms and conditions remain unchanged.
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)
15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED
(Signature of person authorized to sign) (Signature of Contracting Officer)
CASSANDRA A. ELLIS
STANDARD FORM 30 (REV. 10-83)
Prescribed by GSA
FAR (48 CFR) 53.243
NSN 7540-01-152-8070
Previous edition unusable
Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .
Solicitation No. 19-233-SOL-00098_000001
SECTION A - Solicitation/Contract Form
TABLE OF CONTENTS
Section Page No. Section Page No.
A 1-3 H 28-32
B 4-5 I 33-43
C 6-17 J 44
D 18 K 45-68
E 19 L 69-76
F 20-21 M 77-81
G 22-27
SECTION B - Supplies or Services and Prices/Costs
B.1 BRIEF DESCRIPTION OF SERVICES AND SUPPLIES
This contract is designed to procure Intelligent Automation/Artificial Intelligence (IAAI) solutions, services and products.
B.2 TYPE OF CONTRACT
The contract type awarded is Indefinite Delivery Indefinite Quantity (IDIQ)
B.3 TYPE OF ORDERS (IDIQ)
Task or delivery orders issued under this IDIQ contract shall be: Firm fixed-priced and time and material/labor hour orders.
B.4 MINIMUM AND MAXIMUM QUANTITIES (IDIQ)
During the contract period, the Government shall place orders totaling a minimum of $1,000.00.
This reflects the Task Order minimum for the entire period of performance, including any options. The contract maximum for the entire period of performance, including any options, shall be for the placement of orders totaling a maximum of $49,000,000.00.
B.5 CONTRACT LINE ITEM PRICING (IDIQ)
The price for each task order will be based on the negotiated unit prices listed below and estimated level of effort, or firm fixed price amount, to be determined at the time of task order award.
The Contractor will be reimbursed in accordance with pricing section of each task order for satisfactory performance of the work.
B.5.1 Time and Material/Labor Hour Orders
The Contractor shall not exceed the maximum, fully loaded hourly rates (inclusive of wages, indirect costs such as fringe, overhead, general and administrative expenses, any other indirect costs for labor, and profit) for each category listed below.
Loaded Labor Rate
Labor Category Contract
Year 1
(dates to be indicated upon award)
Contract
Year 2
(dates to be indicated upon award)
Contract
Year 3
(dates to be indicated upon award)
Contract
Year 4
(dates to be indicated upon award)
Contract
Year 5
(dates to be indicated upon award)
Class I
Class II
Class III
Class IV
Class V
Material (Non-Labor) Indirect Cost Rates - Pursuant to the General Provisions of this contract pursuant to FAR 52.212-4; Alt. I, the following fixed indirect rate to be applied against Materials is established:
to be incorporated upon award
Fixed Rate
B.5.2 Firm Fixed Price Orders
Firm Fixed Price orders shall comply with the labor rate maximums for each category listed above in Section B.5.1 Time and Material/Labor Hour Orders. A payment schedule for Firm
Fixed Price orders will be negotiated for individual task orders.
NOTE:
Task orders whose period of performance extends beyond the base contract period of five years, the Contractor shall use the rates in Year 5 as adjusted by the Employment Cost Index from the
Bureau of Labor Statistics, 12-month % change for Private Industry Compensation, shown as of the date of request for task order proposal submission. Rates are listed on the right hand side of the page under “Latest Numbers” on http://www.bls.gov/ncs/ect http://www.bls.gov/ncs/ect
SECTION C - Description/Specifications/Statement of Work
Intelligent Automation/Artificial Intelligence (IAAI)
C.1 PROGRAM DESCRIPTION AND BACKGROUND
C.1.1 INTRODUCTION
Will Intelligent Automation/Artificial Intelligence (IAAI) enable the government to run smarter? The Department of Health and Human Services (HHS) Program Support Center (PSC) believes the answer is a resounding yes. PSC is looking to transform the public sector by automating tasks and adopting innovative solutions utilizing advanced technologies enabling the government to shift from “Low Value” to “High Value” tasks. PSC believes that IAAI solutions will be doing everything from reducing backlog and cutting costs to performing functions; such as predicting fraudulent transactions and identifying critical suspects via facial recognition, which are considered difficult for an individual to complete on their own. Indeed, we expect that
IAAI technologies will fundamentally transform how the public sector gets work done -redesigning jobs and creating entirely new professions. In sum, PSC believes that IAAI will change the nature of many jobs and revolutionize facets of government operations. In this acquisition, PSC seeks to establish a contract vehicle that enables PSC Contracting Officers to order for HHS, or on behalf of other agencies, to quickly develop, procure and adopt innovative technical solutions across the full spectrum of technology types: Disruptive, Breakthrough, Incremental and Sustaining.
Examples of major IAAI fields or disciplines include, but are not limited to:
A. AUTOMATION:
What makes a system or process function automatically? One example of automation includes robotics process automation (RPA) can be programmed to perform high-volume, repeatable tasks that humans normally perform. On the other hand, IT automation can often adapt to changing circumstances.
B. MACHINE LEARNING:
Machine learning is the science of getting a computer to act without programming. This includes deep learning which is a subset of machine learning that, in very simple terms, can be thought of as the automation of predictive analytics.
C. SUPERVISED LEARNING:
Data sets are labeled so that patterns can be detected and used to label new data sets.
D. MACHINE VISION:
Machine vision is the science of allowing computers to see. This technology captures and analyzes visual information using a camera, analog-to-digital conversion and signal processing
Under this contract, Contractor(s) shall support federal agency piloting, testing and implementation of advanced technologies include, but are not limited to, intelligent automation/artificial intelligence (e.g. blockchain/distributive ledger technology (DLT), micro-services, machine learning, natural language processing, robotic process automation, etc.) that are able to transform business processes and enhance mission delivery in the Federal
Government. Individual task orders may require support in one or more advanced technologies.
C.1.2 PURPOSE
This is an Indefinite Delivery/Indefinite Quantity contract which sets forth the conditions and clauses under which future acquisitions between the parties shall be governed. The purpose of these indefinite delivery/indefinite quantity (IDIQ) contracts is to enable PSC Contracting
Officers to order for HHS or on behalf of other agencies to quickly obtain IAAI related solutions, services and products.
C.1.3 BACKGROUND
PSC is the largest multi-function shared service provider to the federal government. Hosted by the HHS, PSC provides services to help its customer achieve mission-critical results. PSC was created in 1995 to reduce duplication in federal administrative support service. PSC is a shared service provider offering over 40 services including acquisition support to HHS, its component agencies and other federal agencies on a competitive fee for service basis, allowing agencies to focus on their core mission. As a shared service provider, PSC’s focus is on delivering mission support functions better, faster and more efficiently. As a result, it is well positioned to procure technological solutions that generate efficiencies and cost savings across HHS and throughout the Federal Government.
On April 12, 2017, the Office of Management and Budget (OMB) issued memo M-17-22
Comprehensive Plan for Reforming the Federal Government and Reducing the Federal Civilian
Workforce, requesting that agencies look for solutions that “create a lean, accountable and more efficient government that works for the American people.” Further, the President’s Management
Agenda (PMA) laid out a long-term vision for modernizing the Federal Government in key areas that will improve the ability of agencies to deliver mission outcomes, provide excellent service, and effectively steward taxpayer dollars on behalf of the American people. The PMA identified four cross-agency priorities that intersect – IT modernization, data accountability, building a workforce of the future, and enhancing cybersecurity – that is expected to significantly leverage new trends and approaches to technology. Finally, on August 27, 2018, OMB released M-18-23
Shifting from Low-Value to High-Value Work, to emphasize leveraging such technologies to
“reduce repetitive administrative tasks” freeing Federal employees to focus their time and human capacity on higher value activities and decisions. Thus, an area in which the Federal Government can provide critical services to the American public in the digital age would be to modernize its mission-specific and back office operations with advanced technologies that streamline data collection and analysis, execute repetitive administrative tasks to reduce the burden on Federal employees and improve services quality and delivery.
In 2018, PSC created an Advanced Technologies Program (ATP) to develop and acquire solutions that will enable the Federal Agencies to meet the objectives identified in OMB M-17-
22, M-18-23 and the PMA mentioned above. The goal of the program is to rapidly adopt innovative technical solutions that fall within one of the four (4) technology types: Disruptive, Breakthrough, Incremental and Sustaining. More specifically, this contract is designed to obtain solutions that can address capability gaps in the area of Intelligent Automation / Artificial
Intelligence (IAAI). A description of the four (4) technology types is included below:
TECHNOLOGY TYPES AND DESCRIPTIONS
1. DISRUPTIVE
Disruptive innovations are often described as “revolutionary”.
Innovations that fall into this category create new value for government agencies and organizations. In many ways, such technologies disrupt an existing market and value network. In the case of government organizations, disruptive technologies often enable the government to do more with less. These innovations often provide whole new populations with access to a product or service that was only available to a few. In the case of the Armed
Forces, disruptive technologies radically alters the symmetry of power between competitors. The use of disruptive technologies in the public sector often outdates policies, doctrines and the organization of actors. Examples of disruptive technologies include 3D printers, collaborative commerce, cryptocurrency, ride sharing services and web based video.
2. BREAKTHROUGH
Breakthrough innovations are often described as “jumping the curve.” Innovations that fall within this category are cutting edge and represent a significant advancement in technological complexity or sophistication that jumps the curve of previous products and processes.
Breakthrough innovation introduces a new product, causes new product substitution or introduces a new way of doing things that require a new skill base. With respect to the Public sector an example of a breakthrough technology includes “new” parking meter solutions. In this example, government organizations replaced traditional, coin operated parking meters and expensive employees required to collect the coins. In this instance, drivers are now able to pay on internet-connected phones or by credit card without having to carry coins. This “breakthrough” technology was also a lot less expensive to the city to operate. Other examples of breakthrough technologies include personal computers, semi-conductor electronics, 3D metal printers, the first i-phone and the internal combustion engine.
3. INCREMENTAL
Incremental innovations are often described as “evolutionary.”
Incremental innovation tends to react to existing market needs but is more evolutionary than “sustaining innovations.” Incremental innovations can be thought of as a cycle of innovation, in which one actor that comes up with an innovation that beats out the competition; competitors then respond by coming up with an even better innovation to up the level of play within an existing category. An example of “incremental” innovation can be seen with “Smartphones.” In this instance, competitors added features like screen size, camera pixels, and built in applications to increase their sales and share of the market.
4. SUSTAINING
Sustaining innovations typically react to existing market needs and often support a company’s bottom line or a government organizations budget. Sustaining innovations often focus on improving performance and efficiency of an established product and try to extend the product’s lifecycle for as long as possible.
Given that the HHS has dominion over the vast majority of healthcare data, for the American public as well as responsibility for $1.145 trillion in taxpayer dollars through grants, operational budgets, and procurement of resources and services, HHS realized that leveraging IAAI technologies has the potential to transform how it conducts its business.
This contract is the next logical step to integrating IAAI technologies into all phases of government operations; providing Federal agencies opportunities to share critical insights and information regarding technologies and suppliers: learn from an abundance of small-scale tests and implementations, and find solutions that “create a lean, accountable and more efficient government that works for the American people.”
C.1.4 REFERENCED DOCUMENTS
1. Executive Office of the President, M-18-23 – Shifting from Low-Value to High-Value Work.
August 27, 2018.
2. The OMB M-17-22 – Comprehensive Plan for Reforming the Federal Government and
Reducing the Federal Civilian Workforce. April 12, 2017.
C.2 SCOPE OF IDIQ
The Contractor shall furnish all of the necessary personnel, materials, services, facilities, (except as otherwise specified), and otherwise do all the things necessary for or incident to the performance of the work as set forth in each task order.
C.2.1 TASK ORDERS
The Contractor(s) shall, in response to task orders issued under this contract, provide innovative
IAAI Solutions, Services and products to government agencies that potentially span a full spectrum of mission areas supported by the activities that comprise the various ordering offices.
Services within the functional areas identified below, may be performed under this contract:
1. Functional Area 1: IAAI Applied Ideation and Design Support
2. Functional Area 2: IAAI Engineering and Process Engineering Support
3. Functional Area 3: IAAI Systems Design Documentation and Technical Data Support
4. Functional Area 4: IAAI Engineering, Prototyping and Model Making Support
5. Functional Area 5: IAAI Interoperability, Test and Evaluation Support
6. Functional Area 6: IAAI Quality Assurance (QA) Support
7. Functional Area 7: IAAI Technical Training Support
8. Functional Area 8: IAAI Professional Development and Training Support
9. Functional Area 9: IAAI Program Support
10. Functional Area 10: IAAI Logistics, Operations and Maintenance (O&M) Support
Agencies considering procurements under this vehicle will be encouraged to focus on succinctly articulating the business problems they face to enable Contractor’s to exercise the full weight and breadth of their creative technology capacity on behalf of the Government, rather than on predetermined technology solutions. While individual task orders may require one or more advanced technologies, Contractor(s) are likewise challenged to present solutions that address precise, discrete transactions or activities and avoid “enterprise” offerings.
As such, task orders issued under this contract vehicle fall under one of five (5) task areas:
TASK AREA 1: IAAI APPLIED IDEATION PROCESS AND ENGINEERING SUPPORT
Functional Area 1: IAAI Applied Ideation and Design Support
Functional Area 2: IAAI Engineering and Process Engineering Support
Functional Area 3: IAAI Systems Design Documentation and Technical Data Support
TASK AREA 2: IAAI SOLUTION DEVELOPMENT
Functional Area 4: IAAI Engineering, Prototyping and Model Making Support
TASK AREA 3: IAAI TEST AND EVALUATION
Functional Area 5: IAAI Interoperability, Test and Evaluation Support
Functional Area 6: IAAI Quality Assurance (QA) Support
TASK AREA 4: IAAI TRAINING AND DEVELOPMENT
Functional Area 7: IAAI Technical Training Support
Functional Area 8: IAAI Professional Development and Training Support
Functional Area 9: IAAI Program Support
TASK AREA 5; IAAI MAINTENANCE AND SUSTAINMENT
Functional Area 10: IAAI Logistics, Operations and Maintenance (O&M) Support
C.3 TASK AREAS
C.3.1 TASK AREA 1: IAAI APPLIED IDEATION AND PROCESS ENGINEERING SUPPORT
The objective of the IAAI Applied Ideation and Process Engineering Support task area is to develop ideas, design or engineer solutions to solve specific, practical problems in order to develop a technology. The objective of this task is to stimulate technological innovation across a variety of solution areas. Work in this task area will allow innovators and suppliers the opportunity to think creatively and develop critical solutions to address IAAI capability gaps. This may encompass human centered design as well as other disciplines. Work executed under this task area will encompass examples of activities such as IAAI Applied Ideation and Design Support, IAAI
Engineering and Process Engineering Support and Systems Design, Documentation and
Technical Data Support.
C.3.2 TASK AREA 2: IAAI SOLUTION DEVELOPMENT
The objective of the IAAI Solution Development this task area is to develop and demonstrate prototype solutions in realistic environments or demonstrate the feasibility of prototype solutions over extended operating conditions. Work performed under this may also include proof of concept experiments for IAAI solutions. Activities to be included in this task encompass IAAI
Engineering, Prototyping and Model Making Support. In sum, the purpose is to execute research and or studies and other activities related to producing and delivering a prototype.
C.3.3 TASK AREA 3: IAAI TEST AND EVALUATION
The objective of the IAAI Innovation Test and Evaluation program is to test and evaluate technical and operational concepts and in some cases recommend improvements. This task area applies rigorous test and evaluation methodologies to IAAI solutions. Examples of activities supported within this task include IAAI Interoperability, Test and Evaluation Support and IAAI Quality
Assurance (QA) Support.
C.3.4 TASK AREA 4: IAAI TRAINING AND DEVELOPMENT
This functional area includes ensuring that the end users and technical support personnel are provided with adequate instruction resulting in the attainment and retention of knowledge and skills regarding IAAI solutions they will operate and maintain. Further, this area also includes organizational development and process improvement training activities. Examples of activities supported within this task include IAAI Technical Training Support, IAAI Professional
Development and Training Support and IAAI Program Support.
C.3.5 TASK AREA 5: IAAI MAINTENANCE AND SUSTAINMENT
This functional area includes providing maintenance and sustainment support. This encompasses formulating, implementing and executing sustainment strategies. The goal of this task is to deliver product support packages that maintain the systems operational effectiveness over the systems lifecycle. This includes developing and procuring sustainment support solutions throughout the lifecycle. Examples of activities supported within this task include IAAI Logistics, Operations and Maintenance (O&M) Support.
C.4 FUNCTIONAL AREAS - REQUIREMENT FOR IAAI SERVICES AND PRODUCTS
C.4.1 IAAI SPECIFIC REQUIREMENTS
The Contractor(s) shall provide IAAI solutions, support, knowledge, skills and abilities to meet overall organizational functions, mission and other activities of HHS and other Federal ordering agencies and offices. The functional areas to be under this contract are identified and described in the sections below:
1. IAAI Applied Ideation, Design and Process Engineering Support
This functional area supports the development and application of IAAI solutions. It encompasses the utilization of the creative process for generating and developing
IAAI solutions to solve practice problems. This includes the scientific and analytical disciplines to conduct studies and experimentation directed towards advancing the state of the art: increasing the knowledge or understanding, concept formulation, assessment of system requirements, development, analysis and evaluation of concepts or technologies and development of operational concepts with the end goal being the application results, developing or improving existing IAAI capabilities. This functional area encompasses activities that will “enable” PSC to assist HHS and other
Federal Agencies, to transition from “identifying” problems to brainstorming and designing solution. One practical example may include, but is not limited to, the conceptualization and high-level design of microservices, which involves and re-engineering of underlying business processes and associated applications.
2. IAAI Engineering and Process Engineering Support
This functional area supports the development and application of IAAI disciplines to support HHS and other federal agencies, in the development of new and existing
IAAI capabilities and systems. More specifically, this area supports the development of significant alterations to existing systems, integration and interfaces of existing solutions or software into different applications or platforms. Activities include, but are not limited to requirement elicitation (requirements gathering) analysis, specification development, which includes defining the architecture, components, interfaces and other characteristics. Practical examples may include, but are not limited to the technical design of microservices, the identification and engineering of interoperability requirements to include data formats and communications protocols, and the identification and engineering of the interplay between hardware, operating systems and applications (software).
3. IAAI System Design Documentation and Technical Data Support
This functional area involves the efforts required to prepare detailed technical data documentation necessary to support HHS and other federal agencies in IAAI solution development and implementation. Technical documents may encompass the design, configuration, integration and installation. Specifically, these documents will often identify and spell out specification requirements (system functionality), architecture design, source code, verification tests codes, and maintenance requirements that will help engineers or other technical team members understand the underlying technologies. Technical documentation may be in the form of paper or digital.
4. IAAI Engineering, Prototyping and Model Making Support
This functional area consists of the building, testing, evaluating and operating minimal prototypes to full-scale development (engineering) of IAAI solutions for
HHS and other federal agencies. A practical example includes, but is not limited to, the extraction of sample data, the production of minimal amounts of code to clarify the requirements or design elements under consideration. The prototype can also be used to build test models before building the full capacity in an “innovation lab” environment. Prototyping will enable designers and engineers to gain valuable feedback between software specifications, the actual build and predicting system performance. This area also encompasses the development of full-scale technical solutions.
5. IAAI Interoperability, Test and Evaluation Support
This area consists of the application, testing and evaluation of IAAI solutions to ensure that the developed solution performs in the required operational environment.
One example of testing may include interoperability testing which will reveal whether a microservices solution can interoperate with other software components, software or hardware. Testing, in this context, proves end-to-end functionality between communicating systems. Examples of other types of testing include, but are not limited to, performance testing, load, security, compliance and interface testing.
6. IAAI Quality Assurance (QA) Support
This functional area consists of applying engineering and analytical disciplines to ensure that processes and products used in the design, development and installation results in quality products.
7. IAAI Technical Training Support
This functional area includes providing adequate instruction in the attainment and retention of knowledge, skills regarding the IAAI system, platform or solution that will be operated and maintained. A practical example includes, but is not limited to change management in the technical context which encompasses methods to handle changes to IT assets which may result in unplanned problems or imposed compliance requirements. It also includes the development of training materials for IAAI solution maintainers. One practical example includes, but is not limited to, the training required to educate potential users on a new microservice. In also includes the training required for teams responsible to maintaining the new microservice.
8. IAAI Professional Development and Training Support
This functional area includes organizational development and process improvement training activities related to the IAAI system. This area includes the implementation of the IAAI solution, competency alignment, change management and other workforce training efforts related to human capital strategies.
9. IAAI Program Support
This functional area consists of applying the business, financial management and technical disciplines required to support the planning, organizing, staffing, controlling and leading the IAAI solution. This area represents the integration of a complex
IAAI system in addition to related functional disciplines that must work together to achieve program goals through the development, production and operations support.
One example includes, but is not limited to, the communication and marketing required to support the development and implementation of a new IAAI solution.
10. IAAI Logistics, Operations and Maintenance (O&M) Support
This functional area consists of applying analytical and technical disciplines required to ensure that IAAI solutions are sustained. The main objective is to ensure that solutions are available when required. This also includes the shipping (fielding) sustainment of IAAI solutions.
C.5 INFORMATION SECURITY AND/OR PHYSICAL ACCESS SECURITY REQUIREMENTS
To be completed in individual task orders, when applicable.
C.6 REQUIREMENTS FOR PRIVACY ACT RECORDS
C.7 REQUIREMENTS FOR GOVERNMENT INFORMATION PROCESSED ON
GOCO OR COCO SYSTEMS
C.8 REQUIREMENTS FOR CLOUD SERVICES
C.9 ADDITIONAL HSPD-12 REQUIREMENTS
To perform the work specified herein, contractor personnel will require access to proprietary, privacy protected and/or sensitive data, regular access to HHS-controlled facilities and/or access to HHS information systems. In addition to requirements stated elsewhere in this contract, the contractor shall comply with the following.
Contractor personnel subject to HSPD-12 credentialing requirements may not begin work requiring access to HHS facilities, information or information systems until codified credentialing standards are met and the HSPD12 badges have been issued.
The minimum Government investigation to receive an HSPD-12 PIV Credential is a Tier 1
(NACI), which consists of searches of records covering specific areas of a person’s background during the past five years. The minimum Government investigation to receive Elevated
Privilege (any access beyond normal email or data entry) is a Tier 4 (BI High Risk Public Trust).
The contractor must comply with the instructions and timeframes provided by the Contracting
Officer’s Representative (COR) regarding the handling of the security requirements specified in this section. Typically, each employee must submit at a minimum: a completed OF-306; a current resume; and a completed HHS 828 form. Additional requirements may apply to Foreign
National Applicants who will follow a slightly different level of initial checks. Contractors should ensure that the employees whose names they submit have a reasonable chance for access approval. In some cases, employees with existing background investigations commensurate with sensitivity designations will expedite performance. Inquiries, including requests for forms and assistance, should be directed to the COR.
Typically, the Government investigates personnel at no cost to the contractor, but the expense of multiple investigations for the same position is difficult to justify. Consequently, multiple investigations for the same position may, at the Contracting Officer’s discretion, justify reduction(s) in the contract price of no more than the cost of the extra investigation(s).
After final acceptance of the work specified herein or any employee departure, the contractor shall follow the COR’s instruction on the return of all identification badges, building access cards, Government Furnished Equipment, Government Furnished Data and Government
Furnished Property (GFE/GFD/GFP) as applicable.
HHS reserves the right to suspend or withdraw access at any time for any reason.
Language similar to this Security section shall be included in any subcontracts which require access to proprietary, privacy protected and/or sensitive data, regular access to HHS-controlled facilities and/or access to HHS information systems.
C.10 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)
The Government intends to utilize a Quality Assurance Surveillance Plan (QASP) to monitor the quality of the Contractor’s performance. The oversight provided for in the contract and in the
QASP will help to ensure that service levels reach and maintain the required levels throughout the contract term. Further, the QASP provides the COR with a proactive way to avoid unacceptable or deficient performance, and provides verifiable input for the Contractor
Performance Assessment Reporting System (CPARS). The QASP may be updated by modification to the contract. This is a Quality Assurance Surveillance Plan (QASP) that is applicable for all Task Orders, unless a different QASP is incorporated at the Task Order level.
Required
Services/Tasks
Performance Standards
Method of Surveillance
(Quality Assurance)
Standard to be Met/
Allowable Deviation
Customer
Satisfaction
Contractor complies with
SOW specifications.
Contractor adheres to guidance provided by COR.
COR feedback
Fewer than 2 written complaints from COR during the period of performance.
Overall Contract
Management, Including
Contractor maintains high level of quality assurance.
Contractor informs COR timely of issues or
COR and Contracting
Officer monitoring and review of activities and deliverables.
COR makes no more than
2 valid written complaints during the period of performance. No more
Timeliness problems.
Contractor meets time frames agreed upon.
than a two week delay in agreed upon schedule.
Written Products
Contractor provides high-quality written materials.
COR and other federal staff reviews of draft and final products.
Minimal rewriting or editing required; product utilized (e.g., disseminated) as planned.
Cost Performance
(For Applicable
Task Orders)
Contractor is performing within the budget of the contract.
COR to review monthly invoices and cost reports
Contractor shall perform within the negotiated budget/cost of the contract each month.
C.11 SECTION 508 ACCESSIBILITY STANDARDS
The following Section 508 accessibility standards apply to the work to be performed:
C.12 LABOR CLASS DEFINITIONS
OVERVIEW: The scope of the IAAI IDIQ contract encompasses a wide range of innovative
Information Technology services products and solutions for HHS and other federal agencies. The focus of this work is to proactively address IAAI issues deemed vital to the federal government.
This section “defines” the labor classes encompassed within this contract. The definitions are found below. Each definition correlates to a “compensation” range. It is important to note that while the general “classes” are defined below, the education and experience levels specified are just typical levels, and substitution of education for experience (and vice versa) may be considered at the task order (TO) level and at the sole discretion of the task order contracting officer.
CLASS I: Positions that fall within this class include senior management personnel, directors, subject matter experts (SME’s), senior consultants, senior machine learning engineers, senior software developers, senior product owners, senior program managers, senior software architects, senior data scientists, senior business intelligence developers, senior computer vision engineers, and senior research scientists just to name a few. Individuals who qualify for these positions, have senior skills, qualifications and or particular expertise that is highly unique and must demonstrate that they are able to lead corporate teams, or at the most senior / corporate levels. Individuals within this class are often recognized as leaders in their respective area of expertise. Personnel that falls within this class will typically hold an advanced degree with approximately 12 years of experience. Any position that may be required to conduct work under the ten (10) functional areas identified in Section C.4 may be considered.
CLASS II: Positions that fall within this class include management personnel, scrum masters, product owners, program managers, consultants, machine learning engineers, software developers, software architects, data scientists, human factors engineers, test and evaluation engineers, business intelligence developers, computer vision engineers, and research scientists just to name a few. Individuals who qualify for these positions, have mid to senior skills, qualifications and or particular expertise that is highly unique and must demonstrate that they are able to lead teams, at the mid to senior level. Individuals within this Class are often recognized as leaders in their respective area of expertise. Personnel that falls within this class, will typically hold an advanced degree with approximately eight (8) years of experience. Any position that may be required to conduct work under the ten (10) functional areas identified in Section C.4 may be considered.
CLASS III: Positions that fall within this class include non-manager technical personal which may include analysts, data specialists, software specialists, mid-level computer scientists, mid-level computer engineers, mid-level computer scientists, mid-level human factors engineers, mid-level software developers, mid-level quality assurance specialists, mid-level test engineers, mid-level research scientists and mid-level programmers just to name a few. Individuals who qualify for these positions have mid-level skills are often considered technical executors.
Personnel that fall within this class typically include personnel who hold at least a BS or BA degree with approximately five (5) years of direct experience. Any position that may be required to conduct work under the ten (10) functional areas identified in Section C.4 may be considered.
CLASS IV: Positions that fall within this class include junior technical personal which may include junior analysis, junior data scientists, junior software specialists, junior computer scientists, junior quality assurance analysts, junior test analysts, junior research assistants and junior programmers just to name a few. Individuals who qualify for this positions have entry level skills. Personnel who fall within this class typically include personnel who hold a BS or
BA with approximately three (3) years of direct experience. Any position that might be required to conduct work under the ten (10) functional areas identified in Section C.4 shall be considered.
CLASS V: Positions that fall within this category include other technical staff. Personnel that fall within this class typically include personnel who hold at least an Associate’s degree with approximately one (1) year of direct experience. Any position that may be required to conduct work under the ten (10) functional areas identified in Section C.4 may be considered.
SECTION D - Packaging and Marking
D.1 PACKAGING AND MARKING
All deliverables shall be delivered to the Contracting Officer’s Representative (COR) identified in Section G and shall be marked as follows:
1. Name and address of the Contractor;
2. Contract Number;
3. Description of item contained therein; and
4. Consignee's name and address.
D.2 PAYMENT OF POSTAGE AND FEES
All postage and fees related to submitting information including forms, reports, etc. to the
Contracting Officer or COR shall be paid by the Contractor.
SECTION E - Inspection and Acceptance
E.1 INSPECTION AND ACCEPTANCE
Pursuant to FAR clause 52.212-4, all work described in Section C to be delivered under this contract is subject to final inspection and acceptance by an authorized representative of the
Government. The authorized representative of the Government is the Contracting Officer’s
Representative (COR), who is responsible for inspection and acceptance of all services, materials, or supplies to be provided by the Contractor. The Contracting Officer’s
Representative (COR), named at the individual Task Order level, will be responsible for inspection and acceptance at the order level.
E.1.1 Inspection and Acceptance Criteria
Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COR.
E.1.2 General Acceptance Criteria
General quality measures, as set forth below, will be applied to each work product received from the Contractor under this Statement of Work.
Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.
Clarity - Work Products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.
Consistency to Requirements - All work products must satisfy the requirements of this
Statement of Work.
File Editing - All text and diagrammatic files shall be editable by the Government.
Format - Work Products shall be submitted in hard copy and electronic copy. The electronic copy must be in a format as indicated in the Deliverables Table.
SECTION F - Deliveries or Performance
F.1 RESERVED
F.2 PERIOD OF PERFORMANCE (IDIQ)
The period of performance for this contract is five (5) years.
The period of performance for individual task orders can extend beyond the expiration date of the IDIQ. In accordance with 52.216-22, Indefinite Quantity, options on task orders may be exercised after the expiration date of the IDIQ. The Contractor shall not be required to make any deliveries under this contract after the completion of the order, including options, which should not extend 60 months following the expiration of the IDIQ ordering period.
F.3 PLACE OF PERFORMANCE (IDIQ)
Work will be performed at locations specified in individual task orders.
F.4 DELIVERABLES AND DELIVERY SCHEDULE (IDIQ)
The contractor shall submit all required deliverables in accordance with the schedule established in each individual task order. Deliverables submitted under each individual task order shall reference and cite the contract number and the specific task order number.
F.5 DELIVERY REQUIREMENTS
Pickup and delivery of items under this contract shall be accomplished between the hours of 8:30 a.m. and 4:00 p.m., Monday through Friday unless changed by mutual agreement between the COR and the contractor. No deliveries shall be made on Saturdays, Sundays, and days of government closure or Federal legal holidays found at: http://www.opm.gov/operating_status_schedules.
F.6 OBSERVANCE OF LEGAL HOLIDAYS AND DAYS OF GOVERNMENT
CLOSURE – ONSITE CONTRACTOR EMPLOYEES
(a)(1) The performance of this contract requires contractor employees of the prime contractor or any subcontractor, affiliate, partner, joint venture, or team member with which the contractor is associated, including consultants engaged by any of these entities, to have access to, physical entry into, and to the extent authorized, mobility within, a Federal facility.
(2) The Government may close and or deny contractor access to a Federal facility for a portion of a business day or longer due to any one of the following events:
(i) Federal public holidays for federal employees in accordance with 5 U.S.C. 6103.
(ii) Fires, floods, earthquakes, unusually severe weather to include snow storms, tornadoes and hurricanes.
(iii) Occupational safety or health hazards.
(iv) Any other reason.
http://www.opm.gov/operating_status_schedules
(3) In such events, the contractor employees may be denied access to a Federal facility, in part or in whole, to perform work required by the contract. Contractor personnel already present at a
Federal facility during such events may be required to leave the facility.
(b) In all instances where contractor employees are denied access or required to vacate a Federal facility, in part or in whole, the contractor shall be responsible to ensure contractor personnel working under the contract comply. If the circumstances permit, the contracting officer will provide direction to the contractor, which could include continuing on-site performance during the Federal facility closure period. In the absence of such direction, the contractor shall exercise sound judgment to minimize unnecessary contract costs and performance impacts by, for example, performing required work off-site if possible or reassigning personnel to other activities if appropriate.
(c) The contractor shall be responsible for monitoring when the Federal facility becomes accessible and shall resume contract performance as required by the contract.
(d) For the period that Federal facilities were not accessible to contractor employees, the contracting officer may—
(1) Adjust the contract performance or delivery schedule for a period equivalent to the period the
Federal facility was not accessible;
(2) Forego the work;
(3) Reschedule the work by mutual agreement of the parties; or
(4) Consider properly documented requests for equitable adjustment, claim, or any other remedy pursuant to the terms and conditions of the contract.
SECTION G - Contract Administration Data
G.1 PROVISIONS APPLICABLE TO MATERIAL COSTS (IDIQ)
For Time and Material task orders, unless otherwise expressly provided elsewhere in the contract or in any modification thereto, the cost of the following items or activities shall be unallowable as material costs:
1. Acquisition by purchase or lease, of any interest in real property.
2. Special rearrangement or alteration of facilities;
3. Purchase or lease or rental of any item of general purpose; office furniture or office equipment (including data tapes);
4. Travel to foreign countries; and
5. Food and beverage costs unless part of per diem expenses paid in accordance with the
Federal Travel Regulations.
Any equipment having a unit acquisition cost in excess of $1,000.00, of which the Contractor wishes to be reimbursed as a material cost, shall not be acquired by the Contractor without the specific advance written approval of the Contracting Officer.
G.2 CONFERENCE EXPENSES
Unless the Contracting Officer provides explicit written approval for conference expenses, conference expenses are not allowable under this contract. For purposes of this contract, conference and conference expense are defined in the HHS Policy on Promoting Efficient
Spending, specifically Attachment 1, Use of Appropriated Funds for Conferences and Meeting
Space dated January 23, 2015. The attachment also provides a list of typical HHS meetings and events that are not considered conferences at Exhibit 2. The policy and associated attachments are located at the following site:
http://www.hhs.gov/grants/contracts/contract-policies-regulations/index.html)
G.3 RESERVED
G.4 AUTHORITIES OF GOVERNMENT PERSONNEL
Notwithstanding the Contractor's responsibility for total management during the performance of this contract, the administration of this contract will require maximum coordination between the
Government and the Contractor. The following individuals will be the Government's points of contact during the performance of this contract:
Contracting Officer
Name: Cassandra Ellis
Address: 7700 Wisconsin Avenue, Bethesda, MD 20814
Phone: 301-492-4662
Email: Cassandra.Ellis@psc.hhs.gov http://www.hhs.gov/grants/contracts/contract-policies-regulations/index.html mailto:Cassandra.Ellis@psc.hhs.gov
All communications pertaining to contractual and/or administrative matters under this contract shall be sent to:
Contract Specialist
Name: Jessica Treanor
Address: 7700 Wisconsin Avenue, Bethesda, MD 20814
Phone: 301-492-4527
Email: Jessica.Treanor@psc.hhs.gov
Contracting Officer's Representative
Name: TBD
Address: TBD
Phone: TBD
Email: TBD
Note: The Contracting Officer is the only individual authorized to modify the contract.
G.5 CONTRACTING OFFICER'S REPRESENTATIVE (COR) AUTHORITY
(a) Performance of work under this contract must be subject to the technical direction of the
Contracting Officer's Representative identified above, or a representative designated in writing.
The term "technical direction" includes, without limitation, direction to the contractor that directs or redirects the labor effort, shifts the work between work areas or locations, fills in details and otherwise serves to ensure that tasks outlined in the work statement are accomplished satisfactorily.
(b) Technical direction must be within the scope of the specification(s)/work statement.
The Contracting Officer's Representative does not have authority to issue technical direction that:
(1) Constitutes a change of assignment or additional work outside the specification(s)/statement of work;
(2) Constitutes a change as defined in the clause entitled "Changes";
(3) In any manner causes an increase or decrease in the contract price, or the time required for contract performance;
(4) Changes any of the terms, conditions, or specification(s)/work statement of the contract;
(5) Interferes with the contractor's right to perform under the terms and conditions of the contract; or
(6) Directs, supervises or otherwise controls the actions of the contractor's employees.
mailto:Jessica.Treanor@psc.hhs.gov
(c) Technical direction may be oral or in writing. The Contracting Officer's Representative shall confirm oral direction in writing within five work days, with a copy to the Contracting Officer.
(d) The contractor shall proceed…
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.