16-236-SOL-0002_Amendment_004.pdf

(x)

16-236-SOL-00002

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

Indian Health Service

Indian Health Service

10/13/2015000004

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

10/13/2015

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.)

RPMS Quality Assurance and Customer Support Services

The purpose of this amendment is to:

1. Provide answers to questions received as specified in Section L. of the solicitation.

2. As a result of the answers to questions, the following sections have been amended.

However, the Government encourages all offerors to review the solicitation in its entirety:

Section C.1.6.1

Section I.1

Section J.

Continued ...

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)

STEPHEN J. YUTER

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 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 100

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

16-236-SOL-00002/000004

Section K.

Section L.2

Section L.3.A

Section L.8

Section M.5.A

3. All proposals incorporating the revisions listed above, must be signed by an authorized signatory authority of the Offeror and submitted electronically to Michael.Fischer@ihs.gov by

2:00pm EST, December 22, 2015.

All other terms and conditions have remain unchanged

NSN 7540-01-152-8067 OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

RPMS Quality Assurance and Customer Support Services Solicitation Number: 16-236-SOL-0002 Amendment 004

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

ORGANIZATION OF CONTRACT DOCUMENTS

The purpose of this contract is to obtain services to provide development, maintenance and support for clinical, administrative, clinical, and infrastructure applications used to care for patients through the use of the IHS Resource and Patient Management System

(RPMS).

B.1. MINIMUM AND MAXIMUM CONTRACT AMOUNTS

The guaranteed minimum amount for this contract is $1,000.00 for each year of contract performance. This minimum shall be met through the issuance of one or more task orders. The maximum contract amount, including the base year and all option years exercised under the contract, shall not exceed $80,000,000.00.

B.2. TYPE OF TASK ORDER

This is an IDIQ contract with provisions for the issuance of Time-and-Material/Labor

Hour task orders.

B.3. CONSIDERATION AND PAYMENT

The term-type level of effort services required under this contract are on a continuing or recurring basis therefore it’s completely descriptive of “severable services.”

The Contractor shall provide the necessary personnel, equipment, supplies and support services to perform as described in Section C of this document. In consideration for successful performance of these services, the Contractor shall be reimbursed on a

Time-and-Material/Labor Hour basis in accordance with the Schedule shown below.

The number of hours per labor category, other direct costs, travel costs and fee shall be negotiated on a per task order basis.

The Contractor shall not exceed the maximum, loaded hourly direct labor rates for each category listed below.

B.3.1. BASE YEAR: (EXACT DATES TO BE COMPLETED UPON AWARD)

LABOR CATAGORIES

The labor categories below may be required to support the system over the duration of the contract including implementation and maintenance phases. If proposed labor categories are different, offerors should map their labor category titles to those in the pricing table.

No. Labor Category

Contractor

Labor Category

Estimated Level of Effort Rate Total

1.1 Deployment/Training/ User Support Manager 2,000 (hrs)

1.2 Deployment/Training/User Support Specialist 12,000 (hrs)

1.3 Program Manager Level II 2,000 (hrs)

1.4 Quality Assurance Analyst 6,000 (hrs)

1.5 Quality Assurance Manager 2,000 (hrs)

1.6 Technical Writer Level I 4,000 (hrs)

1.7 Technical Writer Level II 2,000 (hrs)

1.8 Test Engineer 6,000 (hrs)

B.3.2 OPTION YEAR ONE: (EXACT DATES TO BE COMPLETED UPON AWARD)

including implementation and maintenance phases. If proposed labor categories are different, offerors

Labor Category

Estimated Level of Effort Rate Total

1.1 Deployment/Training/ User Support Manager 2,000 (hrs)

1.2 Deployment/Training/User Support Specialist 12,000 (hrs)

1.3 Program Manager Level II 2,000 (hrs)

1.4 Quality Assurance Analyst 6,000 (hrs)

1.5 Quality Assurance Manager 2,000 (hrs)

1.6 Technical Writer Level I 4,000 (hrs)

B.3.3. OPTION YEAR TWO: (EXACT DATES TO BE COMPLETED UPON AWARD)

The labor categories below may be required to support the system over the duration of the contract including implementation and maintenance phases. If proposed labor categories are different, offerors

Labor Category

Estimated Level of Effort Rate Total

1.1 Deployment/Training/ User Support Manager 2,000 (hrs)

1.2 Deployment/Training/User Support Specialist 12,000 (hrs)

1.3 Program Manager Level II 2,000 (hrs)

1.4 Quality Assurance Analyst 6,000 (hrs)

1.5 Quality Assurance Manager 2,000 (hrs)

1.6 Technical Writer Level I 4,000 (hrs)

B.3.4. OPTION YEAR THREE: (EXACT DATES TO BE COMPLETED UPON AWARD)

including implementation and maintenance phases. If proposed labor categories are different, offerors

Labor Category

Estimated Level of Effort Rate Total

1.1 Deployment/Training/ User Support Manager 2,000 (hrs)

1.2 Deployment/Training/User Support Specialist 12,000 (hrs)

1.3 Program Manager Level II 2,000 (hrs)

1.4 Quality Assurance Analyst 6,000 (hrs)

Labor Category

Estimated Level of Effort Rate Total

1.5 Quality Assurance Manager 2,000 (hrs)

1.6 Technical Writer Level I 4,000 (hrs)

B.3.5. OPTION YEAR FOUR: (EXACT DATES TO BE COMPLETED UPON AWARD)

including implementation and maintenance phases. If proposed labor categories are different, offerors

Labor Category

Estimated Level of Effort Rate Total

1.1 Deployment/Training/ User Support Manager 2,000 (hrs)

1.2 Deployment/Training/User Support Specialist 12,000 (hrs)

1.3 Program Manager Level II 2,000 (hrs)

1.4 Quality Assurance Analyst 6,000 (hrs)

1.5 Quality Assurance Manager 2,000 (hrs)

1.6 Technical Writer Level I 4,000 (hrs)

SECTION C - DESCRIPTION/SPECIFICATION /WORK STATEMENT

1. General: This is a non-personal services contract to provide quality assurance, training, de-ployment, and application user support services. The Government shall not exercise any super-vision or control over the contract service providers performing the services herein. Such con-tract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equip-ment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform quality assurance, training, deployment, and application user support services as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: The Indian Health Service (IHS) develops and supports a comprehensive integrated health information system of systems which support a broad range of clinical and business functions at IHS, Tribal and Urban (I/T/U) hospitals and clinics across the country.

The Resource and Patient Management System (RPMS) is similar to the Veterans Health In-formation Systems and Technology Architecture (VistA) in use at the Veterans Administration, having been derived from the same legacy system and sharing many of the same infrastructure and business applications. The RPMS as currently deployed has a MUMPS (Intersystems

Cache) database architecture and VA FileMan file structures. A number of graphical user inter-face (GUI) applications utilizing various languages, ranging from Delphi to C# .NET, have been developed to support certain business processes, while other applications retain legacy charac-ter-based interfaces. RPMS GUI applications principally use a two-tiered architecture utilizing broker-based remote procedure calls, although recent development has focused on a three-tier architecture using web services.

Business functions supported by the RPMS include, but are not limited to, practice management

(e.g. patient registration, scheduling, billing and accounts receivable, release of information), ancillary clinical applications (e.g. inpatient and outpatient pharmacy, laboratory, radiology, im-age archiving, consults and referrals), and point of care clinical applications for behavioral health, inpatient and ambulatory care. The RPMS is certified as a Complete Electronic Health

Record (CEHR) for inpatient and ambulatory settings according to the 2014 version certification criteria published by the Office of the National Coordinator (ONC) for Health Information Tech-nology (HIT). In recent years, the system has been extended to include a personal health record

(PHR) system, RPMS Direct secure messaging, a health information exchange (HIE) system, and supporting middleware services.

1.3 Objectives: The objectives of this contract are to provide quality assurance, training, de-ployment, and application user support services and meet the mission needs of the IHS through effective quality assurance / quality control over software development activities, and use of computer assisted software engineering tools and practices in the key areas below.

Software testing

Implementation and deployment support

Training and documentation support

RPMS application user support

Process quality assurance

Documentation support

1.4 Scope: This PWS provides Task Areas that define functional and programmatic services that may be required to address mixed-lifecycle software applications and mixed method soft-ware development approaches. The Contractor shall furnish all of the necessary personnel, materials, services, facilities, (except as otherwise specified herein), and otherwise do all the things necessary for or incident to the performance of the work for the following task areas:

1. Basic services to support the PWS objectives

2. Software testing

3. Implementation and deployment support

4. Training and documentation support

5. RPMS application user support

6. Process quality assurance

7. Documentation support

8. Software testing tools

9. Transition Management

10. Product Release Management

11. Contractor Management Reporting

1.5 Task Areas

1.5.1. Task 1 - Basic Services:

The contractor shall provide fully qualified staff to support ongoing quality assurance, deploy-ment support, and user support for the existing RPMS applications that are oriented toward:

health information management, clinical care, clinical quality measurement, practice manage-ment, health information exchange, and software infrastructure. Existing system capabilities include, but are not limited to the following:

Electronic Health Record o Inpatient clinical documentation o Ambulatory clinical documentation o Laboratory services o Pharmacy services o Radiology and electronic imaging systems o Case Management services o Additional supporting clinical and ancillary services

Practice Management Suite o Patient Registration & Scheduling o Medical Claim Generation & Billing o Accounts Receivable o Referred Care & Purchased Care services o Additional supporting practice management services

Clinical Performance Reporting o Government Performance Reporting Act (GPRA) data collection and re-porting o Additional clinical quality measurement reporting services

Infrastructure o MUMPS/Cache Ensemble Database Management services o VA FileMan system support o Standard Terminology Services support o Additional software infrastructure development and maintenance services

In addition, the Contractor shall provide fully qualified staff to support and assess evolving

RPMS software lifecycle programs and processes to verify alignment with current best practices in agile software development. This includes a full range of quality assurance activities.

1.5.2 Task 2 Software Testing:

The Contractor shall provide services including module test planning, module accessibility test-ing (both Section 508 and WCAG), module performance and load testing, module unit testing, module integration testing, module regression testing, module standards conformance testing, formative usability testing (remote and mobile lab), meaningful use and industry certification testing support, alpha/beta testing support, and test results reporting. The Contractor shall work collaboratively with other Contractors to support integration testing, alpha testing, and beta test-ing. The Contractor shall be responsible for ensuring compliance with the published integration, alpha, and beta testing schedules. The Contractor shall also coordinate with the respective product owners during all testing activities. The Contractor shall ensure that program, project, and executive leaders always have a situational awareness of the user acceptance level of their respective products.

1.5.3 Task 3 Implementation and Deployment Support:

The Contractor shall provide technical support during implementation and deployments. This support may take the form of remote and onsite installation/configuration support, supporting release management activities, maintaining the release calendar, development deployment help aids (e.g. notes, checklists, and guides), and open source community coordination.

1.5.4 Task 4 Training and User Documentation Support:

1.5.4.1 Sub-Task 4.1Training and User Documentation Support Services]: The Contractor may be asked to supplement on site or online training with the product owners or the Contracted trainers. The Contractor shall train federal product owners on their selected software develop-ment methodology initially and on a continuous basis to ensure the success of the product de-velopment teams. The Contractor will also train the federal product owners on their role in a

CMMI compliant process. For projects the Contractor shall include the documentation require-ments listed below for all software developed. The Government will provide templates to the

Contractor for manuals.

Release notes – a text file distributed by SQA in a standard format defined by IHS. Re-lease notes shall briefly describe issues fixed and/or new functionality delivered by the software and shall contain sufficient information to allow a site manager to safely install the software into RPMS. This includes software prerequisites, any atypical hardware or system requirements, and any additional caveats or warnings. Release notes may be abbreviated if installation instructions are delivered in a separate installation or technical manual.

Installation manual – prepared in a format defined by IHS, an installation manual is re-quired for all applications that require procedures for installation and initial configuration that differ significantly from those of other RPMS applications. Installation manuals are not required for software patches, as long as the installation instructions are clearly specified in the release notes. For most applications, installation instructions can be in-cluded in the technical manual. If applicable, the installation manual shall be provided in draft form to IHS no later than the beginning of alpha testing to be finalized by an OIT technical writer. Final document will be due upon software release.

Security manual – prepared in a format defined by IHS, a security manual is required for all new software versions. Security manuals describe a variety of security features of the subject software. Security manuals are not distributed to the public but are designed for the internal use of the IHS OIT. Release to other entities must be approved by the

Information Systems Security Officer. The draft security manual shall be provided to IHS no later than the beginning of alpha testing with the final document due upon software release.

User manual – the Contractor shall provide a plain language draft of all user functionali-ty delivered by the software application (or new functionality in the case of software up-grades – patches or versions). This will form the basis for the official user documenta-tion to be prepared by an OIT technical writer. The draft user manual shall be provided to IHS no later than the beginning of alpha testing, and the final document will be due upon software release.

Help documentation – for all GUI software the Contractor shall provide a draft of online user help documentation within the application. This documentation will be edited and formatted by an OIT technical writer. The resulting help files will be bundled by the de-veloper into the final software build. The draft help documentation shall be provided to

IHS no later than the beginning of alpha testing.

Test checklists and scripts – requirements for test checklists and scripts will be speci-fied by the individual project. Test cases and scenarios for user acceptance and usabil-ity testing should be coordinated with the federal product owner.

Draft training materials – the Contractor may be required to develop training materials for specific projects.

Other documentation – certain tasks may require additional documentation, which will be specified in projects.

1.5.5 Task 5 User Support:

1.5.5.1 Sub-Task 5.1 User Support Analysis and Resolution Services: The Contractor shall pro-vide services including program/project level help desk integration within service levels, monitor-ing, researching, and responding to help desk tickets, documenting and updating tickets, resolv-ing and closing tickets, escalating issues, maintaining systems’ knowledge base records, moni-toring and reporting on system and program service levels, and providing remote and onsite support nationwide.

These services may include such activities as:

Bringing RPMS systems up to date with current patches

Installing and/or configuring RPMS software applications

Assistance with transition from application versions

Organizational planning and preparation for implementation

1.5.6 Task 6 Quality Assurance

The Contractor shall provide services including implementing a process maturity framework, ex-ecuting a continuous process improvement framework, supporting independent verification and validation (IV&V), development and implementing corrective action plans and process change requests, management reporting, and Quality Assurance Surveillance Plan (QASP) reporting.

1.5.7 Task 7 Project Documentation Support

The Contractor shall provide services including development, review, approval, and version con-trol of required project documentation in an accessible format that conforms to the chosen

SDLC methodology and government security and privacy requirements. Supporting documenta-tion activities would include the development and implementation of consistent processes and procedures to maintain a centralized project documentation repository and associated stand-ards.

1.5.8 Task 8 Software Testing Tools

The Contractor shall provide services to facilitate the selection, implementation, maintenance and support of applicable tools for distributed, agile development teams, including support for the following domains: innovation management, requirements management, change manage-ment, configuration management, source control, project scheduling, resources planning, earned value, testing, build management, release management, risk management, issue man-agement, problem management, management reporting, project communications, and docu-mentation management. Through this task the Contractor shall help to position the Government with the most efficient and cost effective method to provide quality software products on a con-tinuous basis and to meet the communications, policy, and usability needs of all product stake-holders.

1.5.9 Task 9 Transition Management

The Contractor shall provide services including preparing and conducting knowledge acquisition sessions with the incumbent at the beginning of the performance period and preparing and con-ducting knowledge acquisition sessions with follow-on contractors at the end of the performance period.

1.5.10. Task 10 Product Release Management Support

The Contractor shall provide services including customer response to product inquiries, docu-mentation development, review, approval, and version control of official product releases. The established process shall conform to government security and privacy requirements. Supporting activities will include the development and implementation of consistent processes and proce-dures to maintain a centralized history of project released documentation, adherence to associ-ated standards and the management of the associated product repository and respective FOIA releases.

5.11 Task 11 Contractor Management Reporting

1.5.11.1 Sub-task 11.1 Planning and Scheduling: All work specified under this contract shall be planned and scheduled through the use of Work Breakdown Structure (WBS) documents. In responding to each Work Plan, the Contractor shall propose a work plan that describes how the

Contractor intends to carry out the requirements of the order. The plan shall include the re-sources (personnel) that the Contractor will be using for the work as well as a WBS for the task.

Unless otherwise specified by IHS, the WBS shall be provided as a Microsoft Project document.

Proposed work plans and WBS documents must be approved by the COR in consultation with the federal lead for the specific Work Plan. Deliverable dates in the approved WBS will be used as a basis for determining Contractor performance. Some tasks will be incompletely specified at the time of Work Plan acceptance (e.g. final software requirements pending, training dates pending, etc.). The Contractor’s work plan will indicate such unknowns where they exist. The schedule will be regularly updated to reflect completed and pending work, as well as approved adjustments to the schedule. At any point during the period of performance, the Contractor shall be able to produce a current work plan and WBS for each Work Plan and the contract as a whole. The WBS will be the basis for the product roadmap, backlogs, and release/iteration plans.

1.5.10.2 Sub-task 18.2 Monthly and Earned Value Reporting: Each month, coincident with the submission of an invoice to IHS, the Contractor will provide a brief narrative report. The report will be broken out by Work Plan and describe activities and accomplishments during the month, as well as any identified issues, risks, or problems that the Contractor wishes to bring to the at-tention of IHS. Issues, risks, and problems should also include corrective action plans or mitiga-tion plans. The report shall also include contract and program level burn charts (projected ver-sus actual (dollars and hours)), a QASP dashboard (with performance against performance ob-jectives in the PWS), and current staffing plan. It will also be used by the government as a pro-gram management tool. The monthly report is not intended to be duplicative of the EV report but to supplement the numeric data in the EV report with narrative comment.

Each month on a date to be established by mutual agreement, the Contractor will provide IHS with the Contractor Performance Reporting (CPR) forms 1-5, or their equivalent, for the preced-ing Earned Value (EV) reporting period. The CPR forms constitute the appropriate data needed for an EV report. The CPR forms shall be itemized by Work Plan and include a breakout of all costs (staff hours by category, travel, and materials) attributed to the work. The report shall provide monthly and cumulative data from the beginning of the contract period. Any EV report-ing or procedure requirements imposed by the government that do not adhere to the EV Man-agement standard set forth in the ANSI/EIA 748 1998 standards will be clarified before imple-mentation. Any changes to Work Plans that substantially affect the scope of work will be re-flected in the EV reporting system to accurately reflect the work requirements on which perfor-mance will be evaluated. IHS will provide guidance on the completion of the CPR forms, and detailed specifications for the monthly EV report will be provided by IHS to the Contractor.

1.5.11. Task 11 Meaningful Use – Future Phase Development Quality Assurance and De-ployment Support (OPTIONAL)

The contractor shall plan, design, and develop enhancements to the Resource and Patient

Management System (RPMS) applications to comply with the requirements for the proposed

2015 version Certified EHR Technology (CEHRT) and Stage 3 Meaningful Use (MU). The next major EHR certification requirements will be released in late Fiscal Year (FY) 2015 as the Final

Rule for what is known as the 2015 version of the ONC certification program. This will launch a new major development project for the RPMS. New capabilities and services developed for and delivered with the 2015 version Certified EHR will require ongoing operational support and maintenance in subsequent years. Participation in MU is critical for the agency since penalties in Medicare payments will occur if IHS does not participate. Expected sub-tasks include analysis and documentation of technical and functional requirements for the enhancements to RPMS, completion of development of potential new systems, testing and certification with ONC, and deployment/implementation. The ultimate accomplishment will be in achievement of Meaningful

Use of the FY 2015 version Certified EHR across IHS. Performance and project milestones will be monitored through existing program management and governance processes.

1.5.12. Task 12 Innovation Lab Development Quality Assurance and Deployment Support

(OPTIONAL)

The contractor shall support OIT in innovative development initiatives, using the RPMS suite of applications. These kinds of innovation initiatives are difficult to project in terms of scope, cost, and schedule. However, these innovation projects will leverage the same Agile development practices described elsewhere in this PWS. The contract will be expected to leverage user-centered design and Agile innovation techniques to discover new requirements for product de-velopment. The specific deliverables will be specified in a project process agreement and work breakdown structure.

1.5.13. Task 13 CMMI Audit Support (OPTIONAL)

The contractor shall provide certified auditor support via an independent auditor to assess the

RPMS program against the CMMI maturity framework.

1.6 General Information

1.6.1 Quality Control The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which work is assured to comply with the requirements of the contract. The contractor’s proposal is an evaluation factor and three (3) copies of a comprehensive written Quality Control Plan (QCP) shall be submitted to the Contracting Officer and COR within one (1) month (Amendment 004) of the start date of the contract and subsequently within five days of a change to the plan thereafter. After ac-ceptance of the QCP the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to the contractor’s QC system. The approach to Quality Control should map to the contractor’s selected development methodology. However it must also address sup-port for QASP reporting requirements.

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in ac-cordance with the performance standards. It defines the performance standards, how the per-formance standards will be applied, and the frequency of surveillance. The government may use contractors, acting as agents of the government, to carry out QASP monitoring and reporting requirements.

1.6.3 Recognized Holidays:

The contractor is not required to perform services on the federal holidays listed below.

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus Day

President’s Day Veteran’s Day

Memorial Day Thanksgiving Day

Independence Day Christmas Day

1.6.4 Key Personnel: The contractor shall propose Key Personnel whose technical skills and experience are essential to the accomplishment of the task. The Offeror’s Technical Proposal shall include the resume of any individuals designated as key personnel. No substitutions shall be made of accepted key personnel except for sudden illness or death, or termination of em-ployment. Contractor requests for substitution of key personnel shall be submitted in writing to the COR and the Contracting Officer at least twenty-five (25) calendar days in advance of the effective date, whenever possible. Such requests shall include a detailed explanation of the cir-cumstances necessitating the proposed substitution, a resume for the proposed substitute, and any other information requested by the Contracting Officer necessary to approve or disapprove the proposed substitution. An interview may also be requested. The COR and the Contracting

Officer will evaluate substitution requests and promptly notify the Contractor of approval or dis-approval in writing.

The Government reserves the right to evaluate the technical skill and competence of any Con-tractor staff members, to require removal and replacement, upon written notice, of any individu-als whose qualifications or performance are judged deficient at any time.

The follow personnel are considered key personnel by the government: Project Management

Lead (Project Manager Level II), Quality Assurance Manager, and Deployment/Training/User

Support Manager. The contractor shall provide a contract manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer.

The contract manager or alternate shall have full authority to act for the contractor on all con-tract matters relating to daily operation of this contract. The contract manager or alternate shall be available between, 9:00 a.m. to 5:30p.m Eastern Time, Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons.

Individuals in the role of program or project manager must have an active certification of at least one of the following: Project Management Institute (PMI) Program Management Professional

(PgMP), PMI Project Management Professional (PMP), PMI Agile Certified Practitioner (PIM-

ACP), certified ScrumMaster (CSM), or Scaled Agile Framework Agilist (SAFe Agilist). All key personnel must have a minimum of 10 years of experience in their respective functional special-ty area.

At least one individual member of the team must be a Certified SCAMPI Appraiser.

1.6.5 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, using government email, 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 Gov-ernment officials. They must also ensure that all documents or reports produced by contractors that render the contractors opinion or position as a consultant are suitably marked as contractor products or that contractor participation is appropriately disclosed. However, documents being prepared by the Contractor on behalf of the Government, especially for external stakeholder consumption, shall not be branded by the Contractor. Contract personnel shall be required to obtain badges issued by the government as outline in section 1.6 Security Requirements.

When performing services on site, contract staff shall wear badges as required.

SECTION D: PACKING AND MARKING

D.1. PACKAGING

All deliverables shall be packaged and packed in accordance with normal commercial practice to meet the packing requirements of the carrier, including that which is necessary to prevent deterioration and damage due to the hazards of shipping, handling and storing.

D.2. DELIVERY AND MARKING

All deliverables shall be delivered to the address shown in Section F.5., entitled “Place of Performance” and shall be marked as follows:

(a) Name and address of the Contractor;

(b) Contract Number: (to be completed upon award)

(c) Description of item contained therein; and

(d) Consignee’s name and address.

SECTION E: INSPECTION AND ACCEPTANCE

E.1. INSPECTION AND ACCEPTANCE

The COR, as a duly authorized representative of the Contracting Officer, shall assume the responsibilities for monitoring the Contractor’s performance, evaluating the quality of services provided by the closeout Contractor, and performing final inspection and acceptance of all deliverables.

E.2. FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

FEDERAL ACQUISITION REGULATIONS (48 CFR CHAPTER 1) CONTRACT

CLAUSES

FAR 52.246-6 Inspection of Services – Time-and-Material and Labor-Hour (MAY

2001)

SECTION F - DELIVERIES OR PERFORMANCE

F.1. PERIOD OF PERFORMANCE

The period of performance for this IDIQ contract shall consist of a base period of (12) months and four (12) month option periods, at the discretion of the Government.

F.2. DELIVERABLE SCHEDULE AND DELIVERABLES

This lists any reports or documentation that is required as a deliverable to include the due date, frequency, medium/format and who/where it is to be submitted. The program management deliverables are the minimum required. Offerors may proposed a revised schedule of deliverables for software development projects in support of their proposed software development methodology. Offerors should also review other sections of this document for other deliverables.

Deliverable Due Date Frequency Medi-um/Format Submit To

Contract kick-off meeting

One week after contract start.

Once Meeting with presentation materials

COR and Investment Manager

Transition-in Plan One week after contract start.

Once Electronic document

COR and Investment Manager

Revised staffing plan

Two weeks after contract start and then month-ly with status report.

Monthly Electronic document

COR and Investment Manager

Invoice and Sta-tus Report (in-cluding all sup-plemental reports)

NLT 15th of each month

Monthly Electronic document

COR and A/R

Quality Control Plan

One month after contract start.

Once and then up-dated as needed

Electronic document

COR, Investment Manager, and Process Asset Library

Product Owner Orientation to Quality Assur-ance Methodolo-gy

Two months af-ter award and then semi-annually.

Semi-annually

Electronic document and oral presenta-tion

COR and Investment Manager

CMMI audit 9 months after award

Annually Electronic document and reports

COR and Investment Manager

Configuration Baseline report

One month after award and then annually.

Annually Electronic document

COR and Investment Manager

Project Manage-ment Plans (in-cluding compo-nent plans as specified in the HHS Enterprise Performance Lifecycle) (Note:

Non security and non-CPIC related deliverables may be tailored to meet the re-quirements of the selected SDLC methodology)

As needed. As needed. As needed. COR and Investment Manager

Test plans, scripts and reports

As needed. As needed. As needed. COR and Investment Manager

Summative usa-bility report

6 months after award and then annually.

Quarterly Electronic document

COR and Investment Manager

Communications and training de-liverables

As needed. As needed. As needed. COR and Investment Manager

User support dashboard

Four months af-ter start date and monthly thereaf-ter

Monthly Online reports COR and Investment Manager

Policy and stand-ard operating procedures (SOP) documents

As needed. As needed. As needed. COR, Investment Manager, or Enterprise Architect

Position papers / engineering study reports

As needed. As needed. As needed. COR, Investment Manager, or Enterprise Architect

Meeting facilita-tion

As needed. As needed. As needed. COR, Investment Manager, or Enterprise Architect

Testing tools as-sessment and plan

Two months af-ter contract start.

Once and then yearly

Electronic document

COR, Investment Manager, and Enterprise Architect

Complete Soft-ware Builds (product feature

TBD (1st release date determined within one month

Quarterly Electronic Source code repository with notice to SQA lead.

releases) of contract start date).

Executive Presentations and reports

TBD As needed. As needed. COR and TBD

Work Breakdown Schedule and corresponding documentation

3 months after contract start date and quar-terly thereafter

Quarterly Electronic document

RPMS Investment Manager

QASP Dashboard (and supporting reports and evi-dence)

One month after contract start date

Monthly Electronic Document and Online Dashboard

COR

Section 508 Compliance Re-port

11 months after contract start date and annual-ly thereafter

Annually Electronic document

COR

FOIA Software Release

4 months after contract start date and then semi-annual thereafter

Semi-annually

Source code Open source source code re-pository

Retrospective re-view meetings

TBD As needed. Meeting COR, Investment Manager, and Process Asset Library

Corrective action plans

TBD As needed. Electronic document

COR, Investment Manager, and Process Asset Library

Transition Plan – Transitioning Out

3 months before end of contract performance pe-riod.

Once Electronic document

COR, Investment Manager, and Process Asset Library

Employee Clear-ance Forms

TBD As needed. As needed. COR

F.3. OBSERVANCE OF FEDERAL HOLIDAYS

A. Government personnel observe the following days as holidays:

FEDERAL HOLIDAYS

New Year’s Day Martin Luther King’s Birthday President’s Day

Memorial Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day

F.4. FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): https://www.acquisition.gov/far/index.html

FAR 52.242-15 Stop Work Order (AUG 1989)

F.5. Place of Performance

Most of the work will be completed at the contractor’s facility. However, the Government requires all personnel listed as Key Personnel (Section G.3) must be located with a commutable distance from the Rockville, MD headquarters for items that require onsite support.

https://www.acquisition.gov/far/index.html

SECTION G - CONTRACT ADMINISTRATION DATA

G.1. AUTHORITIES OF GOVERNMENT PERSONNEL

The name and address of the Contracting Officer’s Representative (COR) assigned to this project is:

(TO BE COMPLETED UPON AWARD)

G.1.A. Performance of work under this contract must be subject to the technical direction of the COR 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.

G.1.B. Technical direction must be within the scope of the specification(s)/work statement.

The COR does not have authority to issue technical direction that:

Constitutes a change of assignment or additional work outside the specification(s)/performance work statement;

Constitutes a change as defined in the clause entitled “Changes”;

In any manner causes an increase or decrease in the contract price, or the time required for contract performance;

Changes any of the terms, conditions, or specification(s)/work statement of the contract;

Interferes with the Contractor's right to perform under the terms and conditions of the contract; or

Directs, supervises or otherwise controls the actions of the

Contractor's employees.

(a) Technical direction may be oral or in writing. The COR shall confirm oral direction in writing within five (5) work days, with a copy to the Contracting Officer.

(b) The Contractor shall proceed promptly with performance resulting from the technical direction issued by the COR. If, in the opinion of the Contractor, any direction of the COR, or his/her designee, falls within the limitations in (b), above, the Contractor shall immediately notify the Contracting Officer no later than the beginning of the next Government work day.

(c) Failure of the Contractor and the Contracting Officer to agree that technical direction is within the scope of the contract shall be subject to the terms of the clause entitled “Disputes.”

G.2 INVOICE SUBMISSION

G.2.A. Time Frame

The Contractor shall submit invoices once per month. A complete invoice with all required back-up documentation shall be sent electronically, via email, to:

Contract Specialist via IHS mailbox: michael.fischer@ihs.gov.*

Contracting Officer’s Representative: (To be completed upon award.)

Financial Management Service (FMS): HQinvoices@ihs.gov.*

* No other non-invoice related documents (i.e., deliverables, reports, balance statements) shall be sent to HQinvoices@ihs.gov. Invoices Only.

The subject line of your email invoice submission shall contain the contract number, contract line item number, the order number, if applicable, and the number of invoices. The Contractor shall send one email per contract per month.

The email may have multiple invoices for the contract. Invoices must be in the following formats: PDF, TIFF, or Word. No Excel formats will be accepted. The electronic file cannot contain multiple invoices; example, 10 invoices requires 10 separate files (PDF or TIFF or Word).

Invoices shall be submitted in accordance with the contract terms, i.e., payment schedule, progress payments, partial payments, deliverables, etc.

All calls concerning contract payment shall be directed to the COR.

G.2.B. Prompt Payment

In accordance with FAR 52.232-25 Prompt Payment, a proper invoice must include the following items:

1. Name and address of the Contractor.

mailto:michael.fischer@ihs.gov.*

2. Invoice date and invoice number (Contractor should date invoices as close as possible to the date of mailing or transmission.)

3. Contract number or other authorization for supplies delivered or services performed (including order number and contract line item number).

4. Description, quantity, unit of measure, unit price, and extended price of supplies delivered or services performed.

5. Shipping and payment terms (e.g., shipment number and date of shipment, discount for prompt payment terms). Bill of lading number and weight of shipment will be shown for shipments on Government bills of lading.

6. Name and address of Contractor official to whom payment is to be sent (must be the same as that in the contract or in a proper notice of assignment).

7. Name (where practicable), title, phone number, and mailing address of person to notify in the event of a defective invoice.

8. Taxpayer Identification Number (TIN) and Dunn and Bradstreet

Number (DUNS). The Contractor must include its TIN and DUNS on the invoice.

9. Electronic funds transfer (EFT) banking information.

(a) The Contractor must include EFT banking information on the invoice only if required by agency procedures.

(b) If EFT banking information is not required to be on the invoice, in order for the invoice to be a proper invoice, the Contractor must submit correct EFT banking information in accordance with the applicable solicitation provision

(e.g., 52.232-38, Submission of Electronic Funds Transfer Information with

Offer), contract clause (e.g., 52.232-33, Payment by Electronic Funds

Transfer-Central Contractor Registration, or 52.232-34, Payment by

Electronic Funds Transfer-Other Than Central Contractor Registration), or applicable agency procedures.

(c) EFT banking information is not required if the Government waived the requirement to pay by EFT.

10. Any other information or documentation required by the contract

(e.g., evidence of shipment).

In accordance with OMB Memorandum, M-11-32, Agencies shall make payments to small businesses as soon as practicable, with the goal of making payments within 15 days of receipt of a proper invoice. If a small business Contractor is not paid within this (15 day) accelerated period, the Contractor will not be given a late-payment interest penalty. Interest penalties, as prescribed by the Prompt

Payment Act, remain unchanged by means of this memorandum. All small businesses shall label all invoices as “Small Business.”

Additionally, in accordance with OMB Memorandum, M-12-16, all prime

Contractors are encouraged to disburse funds received from the Federal

Government to their small business subcontractors in a prompt manner. To assist prime Contractors in expediting Contractor payments to small business subcontractors, agencies shall, to the full extent permitted by law, temporarily establish an earlier, accelerated date for making agency payments to all prime

Contractors. Consistent with OMB Memorandum M-11-32 above, Agencies shall have a goal of paying all prime Contractors within 15 days of receiving proper documentation. In an effort to support small business growth, drive economic activity and job creation, the Contractor is encouraged to accelerate payments to their small business subcontractors.

In accordance with the requirements of the Debt Collection Improvement Act of

1996, all payments under this order will be made by electronic funds transfer

(EFT). The Contractor shall provide financial institution information to the Finance

Office designated above in accordance with FAR 52.232-33 Payment by

Electronic Funds Transfer – Central Contractor Registration.

G.3. KEY PERSONNEL (HHSAR 352.242-70, JANUARY 2006)

The contractor shall propose Key Personnel whose technical skills and experience are essential to the accomplishment of the task. The Offeror’s Technical Proposal shall in-clude the resume of any individuals designated as key personnel. No substitutions shall be made of accepted key personnel except for sudden illness or death, or termination of employment. Contractor requests for substitution of key personnel shall be submitted in writing to the COR and the Contracting Officer at least twenty-five (25) calendar days in advance of the effective date, whenever possible. Such requests shall include a de-tailed explanation of the circumstances necessitating the proposed substitution, a re-sume for the proposed substitute, and any other information requested by the Contract-ing Officer necessary to approve or disapprove the proposed substitution. An interview may also be requested. The COR and the Contracting Officer will evaluate substitution requests and promptly notify the Contractor of approval or disapproval in writing.

The Government reserves the right to evaluate the technical skill and competence of any Contractor staff members, to require removal and replacement, upon…