16-236-SOL-0001_Amendment_003.pdf

(x)

16-236-SOL-00001

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/2015000003

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 IT System Design and 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 B.2

Section B.2.B

Section I.

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 125

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

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

16-236-SOL-00001/000003

Section I.4.

Section J.

Section L.2

Section L.4.A

Section L.5

Section L.12

Section M.5.A

Section M.8

Section M.9

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-Software Engineering Support Services Solicitation Number: 16-236-SOL-0001 Amendment 003

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. Contract Type

This government anticipates awarding one award as a Cost-Plus-Award Fee (CPAF) contract.

B.2. 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

CPAF (Amendment 003) basis in accordance with the Schedule shown below.

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

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

Section Required Services and Tasks Proposed Total

Estimated Cost

C.2.1 Basic Services

C.2.2 IT Architecture

C.2.3 Application Level Security Engineering and Compliance

C.2.4 Program Management Support

C.2.5 Software Engineering

C.2.6 Project Management Support

C.2.7 Analysis and Design

C.2.8 Testing

C.2.9 Implementation and Deployment Support

C.2.10 Training and User Documentation Support

C.2.11 User Support

C.2.12 System Administration

C.2.13 Subject Matter Expertise (SME) Support

C.2.14 Quality Assurance

C.2.15 Project Documentation Support

C.2.16 Software Development Lifecycle (SDLC) Tools

C.2.17 Transition Management

C.2.18 Contractor Management Reporting

C.2.19 Meaningful Use- Future Phase Development

(OPTIONAL TASK)

C.2.20 Innovation Lab Development (OPTIONAL

TASK)

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.

Item No. Labor Category Contractor Labor

Category Rate

1.1 Administrative Assistant Level I

1.2 Business Analyst Level I

1.3 Business Analyst Level II

1.4 Business Analyst Level III

1.5 Computer Security Systems Specialist Level III

1.6 Computer systems Analyst Level I

1.7 Computer systems Analyst Level II

1.8 Computer systems Analyst Level III

1.9 Configuration Management Specialist

1.10 Database Administrator

1.11 Database Analyst Level II

1.12 Database Report Writer

1.13 Data Warehouse Analyst

1.14 Data Warehouse Developer

1.15 Deployment/Training/ User Support Manager

1.16 Deployment/Training/User Support Specialist

1.17 Enterprise Architect (Systems Architect Level II)

1.18 Information Architect/ Usability Engineer

1.19 Information Engineer Level II

1.20 Program Manager

1.21 Program Manager Level II

1.22 Program Manager Level III

1.23 Quality Assurance Analyst

1.24 Quality Assurance Manager

1.25 Software Developer Level I

Category Rate

1.26 Software Developer Level II

1.27 Software Developer Level III

1.28 Subject Matter Expert Level II

1.29 Subject Matter Expert Level III

1.30 System Administrator Level II

1.31 System Integration Specialists

1.32 Systems Architect Level I

1.33 Technical Writer Level I

1.34 Technical Writer Level II

1.35 Test Engineer

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

C.2.1 Basic Services

C.2.2 IT Architecture

C.2.6 Project Management Support

C.2.7 Analysis and Design

C.2.8 Testing

C.2.9 Implementation and Deployment Support

C.2.10 Training and User Documentation Support

C.2.11 User Support

C.2.12 System Administration

C.2.13 Subject Matter Expertise (SME) Support

C.2.14 Quality Assurance

C.2.15 Project Documentation Support

C.2.16 Software Development Lifecycle (SDLC) Tools

C.2.17 Transition Management

C.2.18 Contractor Management Reporting

(OPTIONAL Task) including implementation and maintenance phases. If proposed labor categories are different, offerors

Category Rate

1.1 Administrative Assistant Level I

1.2 Business Analyst Level I

1.3 Business Analyst Level II

1.4 Business Analyst Level III

1.5 Computer Security Systems Specialist Level III

1.6 Computer systems Analyst Level I

1.7 Computer systems Analyst Level II

1.8 Computer systems Analyst Level III

1.9 Configuration Management Specialist

1.10 Database Administrator

1.11 Database Analyst Level II

1.12 Database Report Writer

1.13 Data Warehouse Analyst

1.14 Data Warehouse Developer

1.15 Deployment/Training/ User Support Manager

1.16 Deployment/Training/User Support Specialist

1.17 Enterprise Architect (Systems Architect Level II)

1.18 Information Architect/ Usability Engineer

1.19 Information Engineer Level II

1.20 Program Manager

1.21 Program Manager Level II

1.22 Program Manager Level III

1.23 Quality Assurance Analyst

1.24 Quality Assurance Manager

1.25 Software Developer Level I

1.26 Software Developer Level II

1.27 Software Developer Level III

1.28 Subject Matter Expert Level II

1.29 Subject Matter Expert Level III

1.30 System Administrator Level II

1.31 System Integration Specialists

1.32 Systems Architect Level I

1.33 Technical Writer Level I

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

C.2.1 Basic Services

C.2.2 IT Architecture

C.2.6 Project Management Support

C.2.7 Analysis and Design

C.2.8 Testing

C.2.9 Implementation and Deployment Support

C.2.10 Training and User Documentation Support

C.2.11 User Support

C.2.12 System Administration

C.2.13 Subject Matter Expertise (SME) Support

C.2.14 Quality Assurance

C.2.15 Project Documentation Support

C.2.16 Software Development Lifecycle (SDLC) Tools

C.2.17 Transition Management

C.2.18 Contractor Management Reporting including implementation and maintenance phases. If proposed labor categories are different, offerors

Category Rate

1.1 Administrative Assistant Level I

1.2 Business Analyst Level I

1.3 Business Analyst Level II

1.4 Business Analyst Level III

1.5 Computer Security Systems Specialist Level III

1.6 Computer systems Analyst Level I

1.7 Computer systems Analyst Level II

1.8 Computer systems Analyst Level III

1.9 Configuration Management Specialist

1.10 Database Administrator

1.11 Database Analyst Level II

1.12 Database Report Writer

1.13 Data Warehouse Analyst

Category Rate

1.14 Data Warehouse Developer

1.15 Deployment/Training/ User Support Manager

1.16 Deployment/Training/User Support Specialist

1.17 Enterprise Architect (Systems Architect Level II)

1.18 Information Architect/ Usability Engineer

1.19 Information Engineer Level II

1.20 Program Manager

1.21 Program Manager Level II

1.22 Program Manager Level III

1.23 Quality Assurance Analyst

1.24 Quality Assurance Manager

1.25 Software Developer Level I

1.26 Software Developer Level II

1.27 Software Developer Level III

1.28 Subject Matter Expert Level II

1.29 Subject Matter Expert Level III

1.30 System Administrator Level II

1.31 System Integration Specialists

1.32 Systems Architect Level I

1.33 Technical Writer Level I

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

C.2.1 Basic Services

C.2.2 IT Architecture

C.2.6 Project Management Support

C.2.7 Analysis and Design

C.2.8 Testing

C.2.9 Implementation and Deployment Support

C.2.10 Training and User Documentation Support

C.2.11 User Support

C.2.12 System Administration

C.2.13 Subject Matter Expertise (SME) Support

C.2.14 Quality Assurance

C.2.15 Project Documentation Support

C.2.16 Software Development Lifecycle (SDLC) Tools

C.2.17 Transition Management

C.2.18 Contractor Management Reporting including implementation and maintenance phases. If proposed labor categories are different, offerors

Category Rate

1.1 Administrative Assistant Level I

1.2 Business Analyst Level I

1.3 Business Analyst Level II

1.4 Business Analyst Level III

1.5 Computer Security Systems Specialist Level III

1.6 Computer systems Analyst Level I

1.7 Computer systems Analyst Level II

1.8 Computer systems Analyst Level III

1.9 Configuration Management Specialist

1.10 Database Administrator

1.11 Database Analyst Level II

1.12 Database Report Writer

1.13 Data Warehouse Analyst

1.14 Data Warehouse Developer

1.15 Deployment/Training/ User Support Manager

1.16 Deployment/Training/User Support Specialist

1.17 Enterprise Architect (Systems Architect Level II)

1.18 Information Architect/ Usability Engineer

1.19 Information Engineer Level II

1.20 Program Manager

1.21 Program Manager Level II

1.22 Program Manager Level III

1.23 Quality Assurance Analyst

1.24 Quality Assurance Manager

1.25 Software Developer Level I

1.26 Software Developer Level II

1.27 Software Developer Level III

1.28 Subject Matter Expert Level II

1.29 Subject Matter Expert Level III

Category Rate

1.30 System Administrator Level II

1.31 System Integration Specialists

1.32 Systems Architect Level I

1.33 Technical Writer Level I

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

C.2.1 Basic Services

C.2.2 IT Architecture

C.2.6 Project Management Support

C.2.7 Analysis and Design

C.2.8 Testing

C.2.9 Implementation and Deployment Support

C.2.10 Training and User Documentation Support

C.2.11 User Support

C.2.12 System Administration

C.2.13 Subject Matter Expertise (SME) Support

C.2.14 Quality Assurance

C.2.15 Project Documentation Support

C.2.16 Software Development Lifecycle (SDLC) Tools

C.2.17 Transition Management

C.2.18 Contractor Management Reporting including implementation and maintenance phases. If proposed labor categories are different, offerors

Category Rate

1.1 Administrative Assistant Level I

1.2 Business Analyst Level I

1.3 Business Analyst Level II

1.4 Business Analyst Level III

Category Rate

1.5 Computer Security Systems Specialist Level III

1.6 Computer systems Analyst Level I

1.7 Computer systems Analyst Level II

1.8 Computer systems Analyst Level III

1.9 Configuration Management Specialist

1.10 Database Administrator

1.11 Database Analyst Level II

1.12 Database Report Writer

1.13 Data Warehouse Analyst

1.14 Data Warehouse Developer

1.15 Deployment/Training/ User Support Manager

1.16 Deployment/Training/User Support Specialist

1.17 Enterprise Architect (Systems Architect Level II)

1.18 Information Architect/ Usability Engineer

1.19 Information Engineer Level II

1.20 Program Manager

1.21 Program Manager Level II

1.22 Program Manager Level III

1.23 Quality Assurance Analyst

1.24 Quality Assurance Manager

1.25 Software Developer Level I

1.26 Software Developer Level II

1.27 Software Developer Level III

1.28 Subject Matter Expert Level II

1.29 Subject Matter Expert Level III

1.30 System Administrator Level II

1.31 System Integration Specialists

1.32 Systems Architect Level I

1.33 Technical Writer Level I

B.2.A NEGOTIATED OVERHEAD RATES

Pursuant to the provisions of FAR 52.216-7 - Allowable Cost and Payment, indirect costs under this contract shall be obtained by applying the final rate or rates negotiated, subject to the approval of the Contracting Officer.

Reimbursement for indirect costs shall be made on the basis of the following rates or on the most current approved rate under the latest negotiated indirect cost rate agreement (NICRA) that does not exceed the ceiling rates below:

ITEM PROVISIONAL

RATE

CEILING

RATE

BASE *

The indirect cost rate ceilings shall be applicable throughout the life of the contract and shall not be exceeded for any reason.

* The costs on which the indirect rate is applied shall be specified as the base.

It is further agreed that, unless the prior approval of the Contracting Officer is obtained, the Contractor shall not change its methods of accounting under this contract in such a manner as to account for any item of cost on a direct-cost basis if such item of cost was previously considered as an indirect charge.

B.2.B AWARD FEE

All interested offerors are to complete the performance assessment chart in

Section H.18 (Amendment 003) of this solicitation. The Government will review the proposed minimum and maximum fees per metric and determine the reasonableness and realism of proposed costs. This will make the basis for determining the award fee.

The following items will be negotiated at the time of award to establish the final award (Amendment 003) fee:

a. Maximum Fee (100% Performance Rating)

b. Minimum Fee (80% Performance Rating)

B.3 TRAVEL / OTHER DIRECT COSTS (Amendment 003)

Contractor will be required to travel during the performance of this contract to attend meetings and conferences and to provide training. The contractor may be required to travel to off-site locations in support of this PWS. Contractor will be authorized travel expenses consistent with the substantive provisions of Federal Travel Regulation (FTR) and the limitation of funds specified in this contract. All travel requires Government ap-proval/authorization and notification to the COR. Travel shall not exceed the following:

Period Travel Travel Total of Base Effort

Optional Ef-fort Amount

Performance ($) ($) ($)

Base Period $40,000.00 $10,000.00 $50,000.00

Option Period 1 $40,000.00 $10,000.00 $50,000.00

Option Period 2 $40,000.00 $10,000.00 $50,000.00

Option Period 3 $40,000.00 $10,000.00 $50,000.00

Option Period 4 $40,000.00 $10,000.00 $50,000.00

TOTAL

AMOUNT $200,000.00 $50,000.00 $250,000.00

Other Direct Costs: This category includes expenses associated with training activities

(i.e. reproduction and shipping), subscriptions to standards such as National Council for

Prescription Drug Programs and other software development reference material that may be required, software, and technical subscriptions as required to fulfill the obliga-tions of the contract and to support optional tasks (19) and (20). All ODCs must be au-thorized by the COR and CO and shall not exceed the following:

Period ODCs ODCs Total of

Base Ef-fort

Optional Ef-fort Amount

Performance ($) ($) ($)

Base Period $10,000.00 $5,000.00 $15,000.00

Option Period 1 $10,000.00 $5,000.00 $15,000.00

Option Period 2 $10,000.00 $5,000.00 $15,000.00

Option Period 3 $10,000.00 $5,000.00 $15,000.00

Option Period 4 $10,000.00 $5,000.00 $15,000.00

TOTAL

AMOUNT $50,000.00 $25,000.00 $75,000.00

SECTION C - DESCRIPTION/SPECIFICATION /WORK STATEMENT

1. General: This is a non-personal services contract to provide full lifecycle software development, architecture, and operations support services. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract 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, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform full lifecycle software development, architecture, and operations 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 Information 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 interface (GUI) applications utilizing various languages, ranging from Delphi to C# .NET, have been developed to support certain business processes, while other applications retain legacy character-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, image 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 Technology (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 full software development lifecycle services to support and meet the mission needs of the IHS through quality software development, strong SDLC management controls and use of computer assisted software engineering tools and practices in the key areas below.

RPMS Architecture

RPMS application support services

Align IHS Software lifecycle programs and processes with current best practices in application architecture, design and management

Requirements elicitation, systems analysis, design and coding

Transition to a true service-oriented architecture (SOA)

Transition disparate GUIs into a common interface framework compliant with accessibility and usability best practices in a platform-independent context

(i.e. support for Web, mobile, machine, and other ancillary interfaces)

Maturing processes and models related to IT governance, project and portfolio management, system development life cycle, security integration, and software quality assurance

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 software 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. IT Architecture

3. Application level security engineering and compliance

4. Program management support

5. Software engineering

6. Project management support

7. Analysis and design

8. Testing

9. Implementation and deployment support

10. Training and documentation support

11. User support

12. System administration

13. Subject Matter Expert support

14. Quality assurance

15. Project documentation support

16. Software development lifecycle (SDLC) tools selection, implementation, maintenance and support

17. Transition Management

18. Contractor Management Reporting

1.5 Special Qualifications:

Preferred IT Certifications/Accreditations, include: Capability Maturity Model Integrated

(CMMI) Level III and higher; demonstrated, proven performance or certification in implementing agile or other iterative development models at an enterprise scale; and experience with ensuring conformance to electronic health record (EHR) certification requirements for Meaningful Use. It is preferred that project managers and PMO team members are certified at Project Management Professional, Agile practitioners, or both.

2.0 Project Tasks

2.1. Task 1 - Basic Services:

The contractor shall provide fully qualified staff to support ongoing software development and user support for the existing RPMS applications that are oriented toward: health information management, clinical care, clinical quality measurement, practice management, 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 reporting 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 assist IHS with evolving the RPMS software lifecycle programs and processes and to align them with current best practices in application architecture, design and management. This includes a full range of lifecycle software development, architecture, and operations support services assessments, interfaces, including software installation onto RPMS systems, configuration and customization for specific site needs, deployment, training and troubleshooting.

2.2. Task 2- IT Architecture:

2.2.1 Sub-Task 2.1 Enterprise Architecture: The Contractor shall provide enterprise architecture services, including the documentation of current state and future state business models, data models, application inventories, and technical design patterns in order to enable IHS to align its IT systems and infrastructure with IHS strategic priorities and plans. The Contractor shall also support federally and agency mandated reporting requirements.

2.2.2 Sub-Task 2.2 Service-Oriented Architecture: The Contractor shall develop architectural deliverables, such as standards, design patterns, service catalogs, technical interfaces, etc., in order to support IHS’s intent to migrate to a more scalable, maintainable service-oriented architecture.

2.2.3 Sub-Task 2.3 Standards Development and Adoption: The Contractor shall document and achieve buy-in on the necessary data and technical standards to achieve the future state architecture.

2.3 Task 3- Application Level Security Engineering and Compliance:

2.3.1 Sub-Task 3.1 Identity and access management (IAM): The Contractor shall provide technical application engineering services to support the development of a cohesive identity and access management strategy, which will enable IHS to achieve strategic aims in the areas of security, meaningful use, mobile health, patient access to health information, national interoperability of health information, and cloud computing – among others. In doing so, the Contractor must work collaboratively with other divisions within OIT, including the Division of Information Security, which specifies agency-level security requirements and policy, and the Division of IT Operations, which provides operational support and system administration for many of IHS’s current IAM capabilities, including directory services.

2.3.2 Sub-Task 3.2 Compliance: Ensuring conformance of application architectures with

FISMA, Privacy Act, and HIPAA requirements. The Contractor shall provide expert level services in the areas of designing, constructing, and implementing secure systems and supporting processes in order to protect the privacy, security, integrity, and availability of

IHS systems, patients’ sensitive protected health information, and personal identifiable information.

2.3.3 Sub-Task 3.3 Health IT certification: Given the important role of IHS systems in supporting the delivery of healthcare, the Contractor must provide expertise in order to ensure conformance with all industry health IT standards, health IT certification requirements, and Meaningful Use requirements. This task includes providing consulting services, policy development support, and standards conformance testing in the areas of health IT certification.

2.4 Task 4- Program Management Support

2.4.1 Sub-Task 4.1 Program Planning. The Contractor shall provide program planning support that enables the program level planning integration of many simultaneous projects and in support of a defined release management process. This task includes the staffing of an agile Program Management Office (PMO) that is capable of integrating agile and waterfall projects into an integrated and published product roadmap. At a high level this task includes all activities related to program planning, program plan execution, program plan monitoring and controlling, program risk management, and program management of other project management process areas.

2.4.2 Sub-Task 4.2 Product Roadmap Development: The Contractor shall develop, publish, and maintain an integrated, easy-to-understand product roadmap that depicts the integrated release of new capabilities, products, services, meta-processes, and significant infrastructure updates. The purpose of the roadmap is to serve as a stakeholder communication tool and to enable program integration of product iteration and release cycles.

2.4.3 Sub-Task 4.3 Agile Portfolio Management: The Contractor shall provide for program level application and project portfolio management. This task includes but is not limited to: conducting earned value analysis, supporting the program’s capital planning and investment control (CPIC) reporting requirements in accordance with OMB and agency guidelines, supporting program budgeting activities (including budget formulation, execution, and review), supporting project cost accounting, implementing and maintaining project accounting systems, supporting program communications planning and execution, including the preparation and review of communication matrices, product marketing plans, written correspondence, and executive presentations.

2.4.4 Sub-Task 4.4 Policy Analysis. The Contractor shall provide health IT consulting services to support the development and review of federal, agency, and programmatic policies and standard operating procedures, especially in the areas of health information technology, health information management, and federal information systems management.

2.5 Task 5- Software Engineering:

The Contractor shall provide robust, high quality software development and engineering services in order to construct secure, reliable, and user-friendly clinical, administrative, infrastructure (middleware), integration, and IAM systems, using a combination of client-server architectures, web-based architectures, mobile application architectures, and cloud computing architectures that are currently in use at IHS, Tribal, and Urban facilities nationwide or that the Contractor develops in accordance with agency published standards. This task includes the development, documentation, review, and integration of source code, user interfaces, application program interfaces (APIs), web services, application and database scripts, routines, etc. It incorporates the principles of secure coding and agile programming methods.

2.6 Task 6- Project Management Support:

2.6.1 Sub-Task 6.1 Agile Project Management at an Enterprise Scale: The Contractor shall provide agile project management support services that enable the effective management of IHS health IT related projects according to widely accepted Agile

Project Management principles and methods. This task includes but is not limited to project communications management, project scheduling, project budgeting, product, release, and iteration backlog management and reporting, scrum meeting management, and project communications management. “At scale” means that the contractor must integrated enterprise governance requirements as specified in the HHS Enterprise

Performance Lifecycle. These governance areas include the integration of portfolio management, CPIC, enterprise architecture, security, privacy, accessibility (Section 508 and WCAG), records management, etc., using Agile approaches and principles.

2.6.2 Sub-Task 6.2 Release and Iteration Planning and Management: The Contractor shall develop, document, achieve buy-in and iterate iteration and release management plans. These plans should be easily understood by all impacted stakeholders, including product owners, technical stakeholder groups, and executives. It shall be the responsibility of the Contractor to integrate its own software development teams.

However, the Contractor will also be required to integrate modules from the open source community, development teams, and other stakeholders. Iteration and release plans must take these dependencies into account.

2.6.3 Sub-Task 6.3 Retrospective Management: The Contractor shall conduct

Retrospective reviews in a manner to inspect itself and create a plan for improvements to be enacted during the next sprint. The contractor shall identify and order the major items that went well and areas where potential improvements are needed and create a plan for implementing improvements for team management. These “lessons learned” and “corrective action plans” should be tracked and managed in order to realize the benefits of continuous process improvement.

2.6.4 Sub-Task 6.4 Product Backlog Management

The product backlog shall be managed to contain a high-level view of all the work that must be completed to create the defined product. The product backlog shall rank the user stories and provide sufficient detail for decomposition and sprint cycle planning.

The product backlog will also be a tool to support program budget planning and executive communications requirements.

2.6.5 Sub-Task 6.5 Sprint Backlog Management

The sprint backlog shall list the tasks and requirements to be completed within a sprint.

The sprint backlog shall include: user stories within the sprint in order of priority, tasks necessary to develop each user story, and effort, in hours, to complete each task. A

“burndown chart” shall be provided that identifies the status of the work the development team has completed.

2.7 Task 7- Analysis and Design:

2.7.1 Sub- Task 7.1 Requirements Definition and Management

The contractor shall perform Agile requirements definition and management (RDM) services to support product development. The requirements and features shall be captured and defined for the product backlog to sufficiently transition the non/functional and functional details into a planning cycle for a development sprint. The end goal being detail such as user stories, architecture stories, visualizations, models, functional requirements, usability performance requirements, etc. that are prioritized and aligned to complete each defined respective sprint cycle. In some cases, documents that need to be created to pass certain organizational milestones, such as HHS EPLC stage gates or product certification, will be required and shall be included the requirements backlog.

The Contractor shall coordinate with the respective government product owners

(generally a medical informatictist) in carrying out this task. The Contractor shall also coordinate through the respective product owners to conduct user research and requirements analysis with professional specialty groups (i.e. user groups) and field stakeholders.

2.7.2 Sub-Task 7.2 Design

Prior to development, a decomposition process by which the product backlog items are communicated and refined shall be conducted in collaboration with the assigned OIT personnel and the development team(s). The product development process shall be driven to a large extent by the quality and clarity of requirements process. The contractor shall perform product design using a range design practices (i.e. from high-level architectural modeling, iteration modeling, database refactoring, end user engagement (formative usability testing), continuous regression testing practices to low-level programming test practices).

2.7.3 Sub-Task 7.3 Coding Standards

Programming language shall be specified as a requirement and coding managed in development sprints. Sprints shall be managed and their sprint backlogs consistently maintained. The final deliverable for any software development task (including maintenance tasks) shall include:

• Compiled software code

• Source code for all applicable software

• All required documentation (Installation, Technical, and User manuals see

Task 5.10)

2.7.4 Sub-Task 7.4 Trade Study Support:

The Contractor shall conduct trade off study services to support System/Product Design through activities performed by a multidisciplinary team to identify the most balanced technical solutions among a set of proposed viable solutions.

Trade off studies and services shall be provided for services such as application design, user-centered research and design, requirements research and analysis, business process analysis, workflow design, task flow analysis, data architecture, database design, and systems design.

Trade studies shall also be conducted in support of major architectural decisions, generally accepted engineering decision-support techniques.

2.8 Task 8- Testing:

The Contractor shall provide services including module test planning, module accessibility testing (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 testing. 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.

2.9 Task 9- 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.

2.10 Task 10- Training and User Documentation Support:

2.10.1 Sub-Task 10.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 development methodology initially and on a continuous basis to ensure the success of the product development 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 requirements 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. Release 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 required 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 included 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 functionality delivered by the software application (or new functionality in the case of software upgrades – patches or versions). This will form the basis for the official user documentation 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 developer 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 specified by the individual project. Test cases and scenarios for user acceptance and usability 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.

2.11 Task 11- User Support:

2.11.1 Sub-Task 11.1 User Support Analysis and Resolution Services: The Contractor shall provide services including program/project level help desk integration within service levels, monitoring, researching, and responding to help desk tickets, documenting and updating tickets, resolving and closing tickets, escalating issues, maintaining systems’ knowledge base records, monitoring 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

2.12 Task 12- System Administration

The Contractor shall provide services including coordinating and administering application environments, including development, integrated testing, staging, certification testing, training, and production environments – within the IHS data center or a cloud computing environment.

2.13 Task 13- Subject Matter Expertise (SME) Support

The Contractor shall provide services in areas that require specific expertise such as

Biomedical Informatics, SDLC Consultants, Cloud Storage Architects. SME’s will provide services, such as, but not limited to: Health Information Technology (HIT) that includes terminology standards maintenance and support, health information management (HIM) support, clinical informatics consulting, health IT policy consulting and development, clinical quality and performance measurement and health IT strategic planning.

2.14 Task 14- Quality Assurance

The Contractor shall provide services including implementing a process maturity framework, executing 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.

2.15 Task 15- Project Documentation Support

The Contractor shall provide services including development, review, approval, and version control of required project documentation in an accessible format that conforms to the chosen SDLC methodology and government security and privacy requirements.

Supporting documentation activities would include the development and implementation of consistent processes and procedures to maintain a centralized project documentation repository and associated standards.

2.16 Task 16- Software Development Lifecycle (SDLC) 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 management, configuration management, source control, project scheduling, resources planning, earned value, testing, build management, release management, risk management, issue management, problem management, management reporting, project communications, and documentation 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 continuous basis and to meet the communications, policy, and usability needs of all product stakeholders.

2.17 Task 17- 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 conducting knowledge acquisition sessions with follow-on contractors at the end of the performance period.

2.18. Task 18- Contractor Management Reporting

2.18.1 Sub-task 18.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 resources (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.

2.18.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 attention of IHS. Issues, risks, and problems should also include corrective action plans or mitigation plans. The report shall also include contract and program level burn charts (projected versus actual (dollars and hours)), a QASP dashboard (with performance against performance objectives in the PWS), and current staffing plan. It will also be used by the government as a program 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 preceding 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 reporting or procedure requirements imposed by the government that do not adhere to the EV

Management standard set forth in the ANSI/EIA 748 1998 standards will be clarified before implementation. Any changes to Work Plans that substantially affect the scope of work will be reflected in the EV reporting system to accurately reflect the work requirements on which performance 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.

2.19. Task 19- Meaningful Use – Future Phase Development (OPTIONAL)

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

Patient Management System…