ID40160115-SOLICITATION.doc

ID40160115 PWS UCF DRAFT V.01 June 28, 2016

Business Intelligence Readiness Sustainment Tool (BI-SRT)

RATING

PAGE

OF PAGES

| 106

2. CONTRACT NO.

3. SOLICITATION NO.

ID40160115

4. TYPE OF SOLICITATION

SEALED BID (IFB)

NEGOTIATED (RFP)

5. DATE ISSUED

8/24/2016

6. REQUISITION/PURCHASE NO.

7. ISSUED BY

CODE

8. ADDRESS OFFER TO (If other than Item 7)

GSA Federal Acquisition Services, Southeast Sunbelt

National IT Commodities Program (NITCP)

Submit through ITSS ONLY

NOTE: In sealed bid solicitations “offer” and “offeror” mean “bid” and “bidder”

SOLICITATION

9. Offers (specified in Section L) for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8 or, if handcarried, in the depository located in N/A until August 30, 2016 4:00 PM. EST CAUTION ( LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR INFORMATION CALL:

A. NAME

Elizabeth F. Kennedy

B. TELEPHONE NO. (NO COLLECT CALLS)

(404) 710-5582

C. EMAIL ADDRESS

Elizabeth.Kennedy@gsa.gov

11. TABLE OF CONTENTS

AND OTHER STATEMENTS OF OFFERORS

OFFER (Must be fully completed by offeror)

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (180 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

10 CALENDAR DAYS

20 CALENDAR DAYS

30 CALENDAR DAYS

CALENDAR DAYS

(The offeror acknowledges receipt of amendments to the numbered and dated:

15A. NAME

AND

ADDRESS

OF

OFFEROR

CODE

FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER (Type or print)

AREA CODE

NUMBER

EXT

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED

20. AMOUNT

21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

41 U.S.C. 253(c)( ) 10 U.S.C. 2304(c) ( )

23. SUBMIT INVOICES TO ADDRESS SHOWN IN (4 copies unless otherwise specified)

ITEM

24. ADMINISTERED BY (If other than Item 7)

CODE

25. PAYMENT WILL BE MADE BY

CODE

See Section G

26. NAME OF CONTRACTING OFFICER (Type or print)

Elizabeth F. Kennedy

27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT -- Award will be made on this Form, or on Standard Form 1449, or by other authorized official written notice.

Table of Contents

1SOLICITATION, OFFER AND AWARD

PART I – THE SCHEDULE

SECTION B – SUPPLIES AND SERVICES

B.1

SCHEDULE OF SUPPLIES/SERVICES TO BE PROVIDED

B.2

PERIOD OF PERFORMANCE

SECTION C – DESCRIPTION/SPECIFICATIONS/PERFORMANCE STATEMENT OF WORK

C.1

BACKGROUND

C.2

SCOPE OF EFFORT

C.2.1

AGENCY MISSION

C.2.2

PERFORMANCE/TECHNICAL REQUIREMENTS

C.2.2.1

PROGRAM MANAGMENT

C.2.2.1 .1 Kick Off Meeting C.2.2.2

IT/NETWORKING ENVIRONMENT SUPPORT

C.2.2.1

.1 SIPRNET

C.2.2.3

DESIGN AND BUILD BUSINESS INTELLIGENCE (BI) TOOL

C.2.2.3.1 Define BI Tool User Requirements C.2.2.3.2 Develop Dashboards to meet User Requirements C.2.2.3.2.1 Lateral Transfer Dashboards C.2.2.3.2.2 Financial Liability Investigations of Property Loss (FLIPL) Dashboard C.2.2.3.2.3 Distribution Dashboard C.2.2.3.3 Weapon System Costing C.2.2.3.4 Data Integration C.2.2.3.5 Prototyping C.2.2.3.5.1 Rapid Application Development (Requirements/Solutions/Implementations) C.2.2.3.6 Configuration Management Board C.2.2.3.6.1 Requirements Traceability Matrix (RTM) C.2.2.3.6.2 CMB Approval C.2.2.3.7 Screen Shots/Production Dashboards

C.2.2.3.8 MOA/MOU/SIA

C.2.2.3.8.1 Parameters C.2.2.3.8.2 Data Feeds C.2.2.4

TESTING

C.2.2.4.1 Functionality and User Testing C.2.2.4.2 Comprehensive Test Plan C.2.2.4.2.1 Implement BI Testing C.2.2.4.2.2 Active Testing Program C.2.2.4.3 Functional User Testing C.2.2.5

LESSONS LEARNED

C.2.2.5.1 Process Improvement Recommendations C.2.2.5.1.1 Assessment and documentation C.2.2.5.1.2 Track Process Improvements C.2.2.6

CAPABILITY MATURITY MODEL INTEGRATION (CMMI) DEPLOYMENT

C.2.2.7

DISA BI TOOL IA COMPLIANCE COORDINATION

C.2.2.7.1 DISA Compliance Coordination C.2.2.7.2 IA Security Posture Maintenance C.2.2.8

SUSTAINMENT AND MAINTENANCE

C.2.2.8.1 Task 1 C.2.2.8.2 Task 2 C.2.2.8.3 Task 3 C.2.2.8.4 Task 4 C.2.2.8.5 Task 5 C.2.2.8.6 Task 6 C.2.2.9

NETWORK ARCHITECTURE AND SECURITY

C.2.2.9.1 Risk Management Framework (RMF) Certification C.2.2.9.2 Accessing BI Tools C.2.2.9.3 Single Sign On (SSO) C.2.2.9.3.1 Task 1 C.2.2.9.3.2 Task 2

C.2.2.10 FINANCIAL RECOVERY

C.2.2.10.1 Financial Analysis Support C.2.2.10.2 Analyze Data C.2.2.10.3 Document Number Reconciliation

SECTION D – PACKING AND MARKING

D.1

LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB 1998

SECTION E – INSPECTION AND ACCEPTANCE

LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB 1998)

E.1 INSPECTION AND ACCEPTANCE

E.2 QUALITY CONTROL PROGRAM

E.3 GOVERNMENT SURVEILLANCE

E.4 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

E.4.1 Performance Standard Services Summary

E.5 PAST PERFORMANCE INFORMATION

SECTION F – DELIVERIES AND PERFORMANCE

F.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 25.252-2)(FEB 1998)

F.2

PERIOD OF PERFORMANCE

F.3

PLACE OF PERFORMANCE

F.4

HOURS OF OPERATION

F.5

DELIVERABLES, REPORTS AND NOTIFICATIONS DELIVERY OF REPORTS

F.5.1

MILESTONE SCHEDULE

F.5.2

DELIVERABLES

F.5.3

REPORTS

F.5.3.1 Kickoff Meeting Minutes F.5.3.2 Weekly Reconciliation Report (WRR) F.5.3.3 Monthly Status Report F.5.4

BI TOOL DOCUMENTATION

F.5.4.1 Project Schedule and Milestones F.5.4.2 BI Tool Rapid Application Development (RAD) Plan F.5.4.3 Risk Management Plan F.5.5

IT SYSTEMS ENVIRONMENT ESTABLISHMENT

F.5.5.1 Software and Hardware Requirements and Specification F.5.5.2 Establish a test environment to host the BI tool for user Test purposes F.5.5.3 Change Requests F.5.5.4 Functionality and User Testing of all completed BI Tools F.5.5.4.1 Active Testing Program Plan F.5.5.4.2 Client Test Scenarios F.5.5.4.3 Test Description F.5.5.4.4 Test Report F.5.5.4.5 Quality Feedback Loop F.5.5.5 Push to Production F.5.5.5.1 Software Anomaly Report F.5.5.5.2 Software Anomaly Resolution Report F.5.5.6 Application Configuration Management Plan F.5.5.7 System Version Description (SVD) F.5.6

TRIP REPORTS

F.5.7

PRESENTATIONS AND DEMONSTRATIONS

F.5.7.1 Demonstrations F.5.8

FINAL DELIVERABLES

F.5.8.1 Source Code F.5.9

SCHEDULE AND DELIVERY INSTRUCTIONS

F.6

KEY PERSONNEL

F.6.1 Expertise F.6.1.1 Task 1 F.6.1.2 Project Management Personnel Requirements

33SECTION G – CONTRACT ADMINISTRATION DATA

33G.1

CONTRACTING OFFICER RESPONSIBILITIES

G.2

INVOICE REQUIREMENTS

G.2.1 Invoice Submittal 34G.2.2

INVOICE INFORMATION

G.2.3 Invoice Information:

G.2.4 Invoice Processing Guidelines G.2.5 Ceiling Price Notification G.2.6 Final Invoice/Contract Closeout

SECTION H – SPECIAL CONTRACT REQUIREMENTS

H.1

TRAVEL REQUIREMENTS

H.1.1 Post Differential H.2

OTHER DIRECT COSTS (ODC)/TRAINING/MATERIALS

H.2.1 Defense Base Act (DBA) Insurance Coverage H.2.2 Kuwait Visa 18, Phones, other ODCs H.2.3 Training H.2.4 Materials H.3

GOVERNMENT FURNISHED EQUIPMENT (GFE) AND GOVERNMENT FURNISHED INFORMATION (GFI)

H.3.1

GFE

H.3.2

GFI

H.3.3 Contractor Furnished Items H.4

SECURITY REQUIREMENTS

H.4.1 Contractor Idenification Badges H.4.2 Controlled Restricted Areas H.4.3 Security Incidents and Violations H.4.4 Privacy Act H.5 ORGANIZATIONAL CONFLICT OF INTEREST (Oct 2010) – Alternatives III, IV, VI H.6

SAFETY REQUIREMENTS

H.7

PERSONAL SERVICES

H.8 SECTION 508 COMPLIANCE

PART II - CONTRACT CLAUSES

SECTION I – CONTRACT CLAUSES

I.1

CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

SECTION J – LIST OF ATTACHMENTS

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

K.1 Solicitation Provisions Incorporated By Reference (FAR 52.252-1) (FEB 1998) K.2 52.213-3 Offeror Representations and Certifications-Commecial Items (Apr 2016) K.3 52.209-7-Information Regarding Responsibility Matters (Jul 2013) K.4 DFARS 252.209-7999 REPRESENTATION BY CORPORATIONS REGARDING UNPAID DELINQUENT TAX LIABILITY OR FELONY CONVICTION UNDER ANY FEDERAL LAW (JAN 2012)

SECTION L – INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS OR RESPONDENTS

L.1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FAR 52.252-1) (FEB 1998)

L.2 52.216-1 TYPE OF CONTRACT (APR 1984)

L.3 PROPOSAL PREPARATION INSTRUCTIONS

L.4 52.233-2 Service of Protest L.5 552.219-73 Goals for Subcontracting Plan

SECTION M – EVALUATION FACTORS FOR AWARD

M.1 NOTICE LISTING SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

M.2 OVERALL BASIS FOR AWARD

PART I – THE SCHEDULE

SECTION B – SUPPLIES AND SERVICES

B.1

SCHEDULE OF SUPPLIES/SERVICES TO BE PROVIDED

(a) The contractor shall provide their total proposed amounts in blocks 23 and 24 of the SF1449 cover page through the GSA business systems portal, ITSS (https://portal.fas.gsa.gov/web/guest) for all contract line item numbers (CLINS). The contractor shall provide the items required by this contract on a Firm Fixed Price (FFP) basis.

(b) The contractor (independently, and not as an agent of the Government) shall provide all resources (except as may be expressly stated in this contract as furnished by the Government) required to accomplish the work efforts as specifically set forth in this contract and within the scope of the performance work requirements stated in Section C.

B.2

PERIOD OF PERFORMANCE

The contract will consist of a basic period of performance for one (1) Year from the Effective Date of the contract, and will include two (2) additional one-year options. See Section F. The following CLINs are applicable to this contract.

CLINS

Description

Type 0001/1001/2001 Non Severable Support-ODC FFP 0002/1002/2002 Travel/Post Differential/Per Diem CR 0003/1003/2003 Defense Base Act Insurance Coverage FFP

0004/1004/2004 Severable Sustainment Labor FFP

(END OF SECTION B)

SECTION C – DESCRIPTION/SPECIFICATIONS/PERFORMANCE STATEMENT OF WORK

C.1

BACKGROUND

Changes, reductions, and drawdowns in US Army force structure put continuous and increasing pressure on efficient and effective operations. The CJTF-OIR requires a business intelligence capability to provide near real time visibility of financial and logistics data to manage equipment readiness and property accountability across a geographically dispersed Command. Visibility of logistics and financial data is required in both garrison and deployed environments to provide leadership the information required to make fiscally sound and auditable decisions on issues of property accountability.

This undertaking is time sensitive on two fronts: the CJTF-OIR deploys for a year starting September 2015, and the redistribution of property will commence shortly after that. During the redistribution, CJTF-OIR and its subordinate units will divest a Division-plus of equipment across the Army.

C.2

SCOPE OF EFFORT

The purpose of this action is to obtain IT Systems Support to produce a logistics business intelligence tool that will provide an electronic dashboard to view current logistics information of units while assigned under the CJTF-OIR. This tool will use inputs from systems of record while permitting customized displays and smart filters focused on exception management driven success. Additionally, the tool will identify mismatched or non-supportable supply and financial records for potential cancelation, leading to increased available obligation authority.

The Contractor shall build a Business Intelligence (BI) Tool that serves as a logistics collaboration portal to provide reports and dashboards to view the current logistics status of the CJTF-OIR and Building Partner Capacity (BPC) sites.

C.2.1

AGENCY MISSION

The Combined Joint Task Force (CJTF) – Operation Inherent Resolve (OIR) mission is to provide a strategic crisis response force manned and trained to deploy rapidly by air, sea, and land anywhere in the world, prepared to fight upon arrival and win. CJTF-OIR operates in a complex external command environment, prepared to support any of the unified combatant commands across the range of operational environments.

C.2.2

PERFORMANCE/ TECHNICAL REQUIREMENTS

The Contractor shall provide all labor, materials, and services necessary to deliver, for government review and approval, a logistics collaboration portal. This portal shall gather and display requested maintenance, financial, and supply data from the Services’ authoritative Enterprise Resource Planning (ERP) systems, legacy data from authoritative data sources, and locally maintained data sources. The portal shall display this data and the status of logistics business processes using standardized formats required by the CJTF-OIR J4 guidance.

This tool shall be the entry point for logistics and readiness information being provided to CJTF-OIR and CENTCOM leadership. Support of this logistics collaboration portal shall include rapid configuration deployment with continuous, on-going refinements to meet evolving CJTF-OIR requirements. The portal requires operations and maintenance of the prototype system along with associated NIPRNET and SIPRNET (if required) production infrastructure.

The tool shall enable users to conduct data queries and analysis for specified Army materiel. Query elements shall include at minimum Line Item Number (LIN), nomenclature, National Stock Number (NSN) / National Item Identification Number (NIIN), unit designations, Department of Defense Activity Address Codes (DoDAACs), as well as status, priority and location information.

The BI tool shall use Army authoritative information and systems of record, including LMP, GCSS-Army, Logistics Information Warehouse (LIW), Property Book Unit Supply Enhanced (PBUSE), Federal Logistics Data (FEDLOG), Department of Defense Activity Address File (DoDAAF), and Standard Army Management Information System (STAMIS) transactional data as required.

The government will provide all appropriate government data as Government Furnished Information (GFI). The contractor shall identify, document, and integrate data from Army authoritative information and systems of record and local offline unique data sources. The contractor shall aggregate information from these disparate logistics and financial systems data sources to build a BI tools to support improved unit readiness.

C.2.2.1

PROGRAM MANAGEMENT

The Contractor shall provide program management, oversight, and reports for all contractor support activities conducted in support of this PWS. The Contractor shall provide close interaction with the government and provide effective management of scope, schedule, and cost. The Contractor shall document the results of the project efforts for this PWS and perform as the primary representative coordinating completion of all associated milestones and deliverables and coordinating government review and approval through project completion.

C.2.2.1.1 Kick Off Meeting

A Kick-Off meeting shall be conducted within Fourteen (14) Calendar days of the date of award. The Contractor shall coordinate with the COR and Customer Account Manager (CAM) the meeting, agenda, and record the minutes of the meeting to capture the basic contacts, milestones, dates, deliverables, actions required, and administration details of the contract.

C.2.2.2

IT/NETWORKING ENVIRONMENT SUPPORT

The Contractor shall identify the IT and networking equipment the BI Tool requires for development and support. The Government will furnish and/or establish the appropriate network to support the requirements listed below. It is a vision that this effort will reside in an unclassified but sensitive environment with the Government accessing via Virtual Machine (VM) configuration using .mil security template via the DoD NIPRNET (Non-Secure Internet Protocol Router Network). Any exceptions to this process must be negotiated by the Government.

The Contractor shall provide personnel to establish initial operating capability of the VM environment. The Contractor shall provide close coordination among CJTF-OIR J4, J6, and Signal Command shared services.

C.2.2.2.1

SIPRNET

If the Government determines that the data when aggregated by the SRT becomes classified, the Contractor shall replicate the dashboard environment on the SIPRNET (Secret Internet Protocol Router Network) in an architecture provided by the Government. The Government recognizes that this migration will become part of the agreed upon priority list and other requirements may move down the list.

C.2.2.3

DESIGN AND BUILD BUSINESS INTELLIGENCE (BI) TOOL

Central to the solution, a logistics BI tool will reside within the Government provided architecture to provide users with a web-based collaborative repository for viewing, updating, and sharing critical logistics information. BI Application and Tools developed in accordance with CJTF-OIR requirements.

C.2.2.3.1 Define BI Tool User Requirements The Contractor functional BI analyst shall work with key stakeholders to define, document, and refine requirements. The Contractor shall break out the requirements into small, fully designed tasks and define the data sources.

C.2.2.3.2 Develop Dashboards to meet User Requirements C.2.2.3.2.1 Lateral Transfer Dashboards

The Contractor shall develop a dashboard to track the lateral transfer of equipment from the Owning Units to the Gaining Units to balance excess property in one unit with shortages in another.

C.2.2.3.2.2 Financial Liability Investigations of Property Loss (FLIPL) Dashboard

Contractor shall incorporate into the BI Tool the Financial Liability Investigations of Property Loss (FLIPL) dashboard. The dashboard shall provide specific information for equipment losses and/or recovered equipment.

C.2.2.3.2.3 Distribution Dashboard The dashboard shall identify those items in-transit based on RFID tag and or Transportation Control Number (TCN).

C.2.2.3.3 Weapon System Costing The Contractor shall demonstrate Weapon System Costing experience using accepted Army cost data sources. This includes at a minimum the following:

· Flying hour and ground system Operations Tempo (OPTEMPO) (hours flown/miles driven), repair parts,

· Training ammunition,

· Maintenance.

C.2.2.3.4 Data Integration Contractor shall incorporate and demonstrate an understanding of data integration with legacy, G-Army, GFEBS ERP systems in the following areas:

· Weapon system repair parts and supply requisition data structures and functionality

· PBUSE data structures and PBUSE functionality.

· FEDLOG and SLAMIS catalog data as they relate to accurate FLIPL reporting.

· Maintenance data structures and functionality.

· Flying hour and mileage reporting data structures and functionality.

· Training ammunition data structures and functionality.

C.2.2.3.5 Prototyping

The contractor shall incorporate prototyping to allow the Government to closely map the BI report and dashboard designs to customer business, decision-making, and management processes based on direct user input, review, and approval.

C.2.2.3.5.1 Rapid Application Development (Requirements/Solutions/Implementations)

The Contractor shall provide recommended requirements, proposed solutions, and implementations using Rapid Application Development and continuous refinement to meet user needs.

The Contractor shall use mockups and prototypes throughout the entire design, development, test, and implementation process using industry Rapid Application Development (RAD) standards. The Contractor shall use mockups to support alternatives and courses of action (COAs) analyses as part of the BI design process.

The Contractor shall develop and maintain a BI Tool RAD Plan to guide the Government’s rapid application BI development process. The Contractor shall use this document to manage the test driven development approach, incorporating the Government’s prototyping and mockup steps, iterative development processes, integrated test plans, and component migration.

The Contractor shall integrate these activities across the BI Tool capability.

C.2.2.3.6 Configuration Management Board

The Contractor shall participate in the Configuration Management Board (CMB) meetings to review all changes to the baseline and shall provide support to validate the requirement and resource availability. The CMB shall make recommendations on baseline configuration and any changes.

C.2.2.3.6.1 Requirements Traceability Matrix (RTM)

The contractor shall establish a RTM. The RTM shall track BI Tool components and their technical specifications, as they are identified, approved, and prioritized. The RTM shall increase the traceability and visibility and improve cost-risk-tradeoff decisions, by making clear, the cost and schedule for components that are required to implement the value proposition.

C.2.2.3.6.2 CMB Approval

The Contractor shall record CMB approval by updating the RTM which shall be included in the Monthly Summary Report. This information will be used by the CMB in monitoring the baseline system development and changes.

C.2.2.3.7 Screen Shots/Production Dashboards

The Contractor personnel shall gather requirements, develop mock up screen shots for COR approval, and create production dashboards. Mockups shall reflect experience supporting deployed forces with logistics business intelligence services.

C.2.2.3.8

MOA/MOU/SIA

The Contractor shall provide the Business Intelligence Tool with feeds from financial and logistics systems identified by CJTF-OIR, based on establishment of Memorandums of Understanding (MOU) / Memorandums of Agreement (MOA) and system interface agreements (SIA) between AMC LOGSA, AESIP, and other system owners and CJTF-OIR prior to going into production.

C.2.2.3.8.1 Parameters

The Contractor shall operate within the parameters established by MOA/MOU/.

C.2.2.3.8.2 Data Feeds The Contractor shall demonstrate an ability to establish data feeds based on SIAs using interface scripts and data connection procedures.

C.2.2.4

TESTING

The Contractor shall test the business rules or logic in the database before building the initial prototype capability of the new views and metrics for evaluation for approval by the customer.

C.2.2.4.1 Functionality and User Testing

Functionality and User Testing of all completed BI Tools. Prior to releasing any new functionality, the Contractor shall address all recorded errors or problems and recode and retest those areas and remediate the errors. The contractor shall conduct multiple levels of testing, which include functional, integration, and regression testing.

C.2.2.4.2 Comprehensive Test Plan

The Contractor shall develop and follow comprehensive test plans prior to any software release.

C.2.2.4.2 .1 Implement BI Testing The Contractor shall implement BI testing to validate the applicability of the solution to the business process capability requirement. Testing shall focus on verifying the functionality of the dashboard and report designs and their adherence to the CJTF-OIR business management processes and associated requirements.

C.2.2.4.2 .2 Active Testing Program The Contractor shall provide an active testing program that operates in tight coordination with the mockup and prototyping processes. The Contractor shall provide a quality feedback loop, for the customer and the developers.

C.2.2.4.3 Functional User Testing

The Contractor shall support functional user testing of the dashboards.

C.2.2.5

LESSONS LEARNED

After each push to production and as part of the weekly development kickoff meeting, the Contractor shall participate and share lessons learned and incorporate them to enhance the process, reduce any issues, and better manage risk.

C.2.2.5.1 Process Improvement Recommendations The Contractor shall provide process improvement recommendations to support asset availability and excess management, equipment availability and resourcing, readiness management, and supply and financial over-age requisition reconciliation management processes.

C.2.2.5.1.1 Assessment and documentation The Contractor shall accomplish this through high level assessment and documentation of current process performance, and identification and establishment of benchmarks and key process indicators (KPIs).

C.2.2.5.1.2 Track Process Improvements The Contractor shall then implement these recommendations and develop dashboards to track process improvements against KPIs.

C.2.2.6

CAPABILITY MATURITY MODEL INTEGRATION (CMMI) DEPLOYMENT

The Contractor shall follow at least Capability Maturity Model Integration (CMMI) II procedures to deploy dashboards to the production environment.

C.2.2.7

DISA BI TOOL IA COMPLIANCE COORDINATION

The Contractor shall configure the BI Tool application infrastructure that meets all DoD Information Assurance (IA) requirements.

C.2.2.7.1 DISA Compliance Coordination

After each environment is configured, the Contractor shall coordinate and maintain DISA Compliance confirmation.

C.2.2.7.2 IA Security Posture Maintenance Contractor shall work with DISA or local DOIM to coordinate maintenance of the IA security posture by tracking, researching, and testing all required Information Assurance Vulnerability Alerts (IAVA) and other software, operating system (OS), and MS SQL Server or Oracle RDBMS database security patches, perform regular scans to verify IA compliance, and update security templates.

C.2.2.8

SUSTAINMENT AND MAINTENANCE

The Contractor shall perform full lifecycle support consistent with Compatibility Maturity Model Integration (CMMI) Level II practices. The Contractor support shall include operations, maintenance, enhancements, planning, monitoring of applications, architecture and associated networks.

Tasks include:

C.2.2.8 .1 Establishing and maintaining scheduled data updating based on MOU/MOAs.

C.2.2.8 .2 Supporting the BI applications and reports, data updates, and connectivity requirements. Contractor shall monitor data transfers, network connectivity, network security, access control, and data integrity.

C.2.2.8 .3 Maintaining the BI dashboard data model to effectively balance dashboard performance, ease of use, referential integrity, and de-normalization as required.

C.2.2.8 .4 Ensuring data elements used in dash boarding are in compliance with Army and CJTF-OIR Data Governance requirements.

C.2.2.8 .5 Maintaining BI repository and catalog configuration control using source code control systems and properly backing up repositories and catalogs.

C.2.2.8 .6 Identifying, planning, and executing BI system updates and upgrades required for Information Assurance and system operation and maintenance purposes.

C.2.2.9

NETWORK ARCHITECTURE AND SECURITY

C.2.2.9.1 Risk Management Framework (RMF) Certification Contractor shall provide support to the CJTF-OIR J6 and Camp Arifjan, Kuwait Network Enterprise Center (NEC) in maintaining Risk Management Framework (RMF) certification as it relates to this effort.

C.2.2.9.2 Accessing BI Tools Contractor shall support security requirements for accessing the BI tools including roles and permissions, authentication, and user account management.

C.2.2.9.3 Single Sign On (SSO) The Contractor shall facilitate establishment of Single Sign on (SSO) for Computer Access Card (CAC) access and will support the following:

C.2.2.9.3.1 Maintaining, managing, and updating the Microsoft Internet Information Services (IIS) which is required to make the BI dashboards web-enabled and enables the data transfers required for data Extract Transform and Load (ETL).

C.2.2.9.3.2 Maintaining Windows IIS configurations in compliance with Defense Information Systems Agency (DISA) standards and make adjustments and changes to the configurations in response to IAVA notifications or findings from DISA Gold Disk, iRetina, and Security Readiness Review (SRR) Script vulnerability scanning tool. Maintaining and updating software configuration per DISA standards to ensure continued CAC authenticated user access and DISA Information Assurance (IA) standards per the PWS.

C.2.2.10

FINANCIAL RECOVERY

C.2.2.10.1 Financial Analysis Support Contractor shall provide financial analysis support to research supply and financial transactions, identifying funds that can be recovered and returned by the J8 to the Command.

C.2.2.10.2 Analyze Data The Contractor shall analyze supply, maintenance, and financial data and provide recommendations for daily operations using the authoritative data source.

C.2.2.10.3 Document Number Reconciliation

The Contractor shall perform document number reconciliation between the supply and financial systems to determine if there are invalid document numbers with obligations applied.

The Contractor shall perform analysis and search for incorrect obligation(s) and incorrect billing in the:

· Funds Control Module (FCM),

· Standard Army Financial System (STANFINS)

· General Funds Enterprise Business System (GFEBS) The Contractor shall deliver documentation to the J8 for corrective action(s).

(END OF SECTION C)

SECTION D – PACKING AND MARKING

D.1

LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (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 the addresses below:

FAR website:

http://acquisition.gov/far/index.html DFARS website:

http://farsite.hill.af.mil/ GSAM website:

http://acquisiton.gov/comp/gsam/gsam.html

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

CLAUSE NO. DATE TITLE

None included

II. DFAR SUPPLEMENT (48 CFR CHAPTER 2)

None Included

III. GSAM FAR SUPPLEMENT (48 CFR CHAPTER 18)

None Included

(END OF SECTION D)

SECTION E – INSPECTION AND ACCEPTANCE

LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (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):

DFAR website:

http://farsite.hill.af.mil/ GSAM website:

http://acquisiton.gov/comp/gsam/gsam.html

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

CLAUSE NO. DATE TITLE

II. DFAR SUPPLEMENT (48 CFR CHAPTER 2)

252.227-7015 Technical Data-Commercial Items (Feb 2014)

252.227-7022 Government Rights (Unlimited) (MAR 1979)

FEB 2014

MAR 1979

Technical Data-Commercial Items Government Rights (Unlimited)

III. GSAM FAR SUPPLEMENT (48 CFR CHAPTER 18)

None Included

E.1 INSPECTION AND ACCEPTANCE

Inspection and acceptance will occur in accordance with FAR 52-212-4 Contract Terms and Conditions Commercial Items. In the absence of other agreements negotiated with respect to time provided for Government review, deliverables will be inspected and the contractor notified of the Client Representative’s findings within fifteen (15) calendar days of normally scheduled review. If the deliverables are not acceptable, the Client Representative will notify the contractor immediately. Acceptance of invoices shall constitute acceptance of performance.

Unsatisfactory Work. Performance by the contractor to correct defects found by the Government as a result of quality assurance surveillance and by the contractor as a result of quality control shall be at the contractor’s own expense without additional reimbursement by the Government. Unless otherwise negotiated, the contractor shall correct or replace all non-conforming services or deliverables not later than five (5) calendar days after notification of non-conformance.

E.2 QUALITY CONTROL PROGRAM

Management of the quality control program is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the Government. The Contractor shall develop, implement and maintain an effective Quality Control System which includes a written Quality Control Plan (QCP). The QCP shall implement standardized procedure/methodology for monitoring and documenting contract performance to ensure all contract requirements are met. The Contractors’ QCP must contain a systematic approach to monitor operations to ensure acceptable services/products are provided to the Government. The QCP, as a minimum, shall address continuous process improvement; procedures for scheduling, conducting and documentation of inspection; discrepancy identification and correction; corrective action procedures to include procedures for addressing Government discovered non-conformances; procedures for root cause analysis to identify the root cause and root cause corrective action to prevent re-occurrence of discrepancies; procedures for trend analysis; procedures for collecting and addressing customer feedback/complaints. The contractor shall provide to the Government their comprehensive quality control written documentation within 30 days after contract award, and three copies shall be submitted to the KO and COR within five (5) working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the Contracting Officer’s acceptance in writing of any proposed change to their QC system.

E.3 GOVERNMENT SURVEILLANCE

The Government shall monitor the Contractor's performance under this contract using the quality assurance criteria specified in the Services Summary and the Quality Assurance Surveillance Plan (QASP). The Contractor shall cooperate with inspectors and auditors and provide any requested information relating to the operations covered by the contract. The Contractor shall allow inspectors and auditors to periodically access work areas and access to any files required by this contract. The Contractor shall correct discrepancies and/or violations noted during safety/security/fire/performance inspections and prepare a written response providing information on action taken to correct discrepancies and/or violations. The Contractor shall provide this response to the COR within the time frame specified by the inspecting agency. Errors noted in material locations shall be corrected within four working hours.

The Contractor shall notify the COR, within one workday, of complaints in writing received by the Contractor on services or supplies covered by or received under this contract. These complaints could include, but are not limited to, those received from customers receiving deliveries, commercial shippers, and discrepancies in Shipment Reports (Standard Form 361). The Contractor is responsible for researching and submitting proposed answers to all deficiencies to the COR within five calendar days of the problem notification. All issues shall be resolved to CJTF-OIR satisfaction within 30 calendar days of problem notification.

E.4 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

The Government will evaluate the contractor’s performance under this contract. The Government will record all surveillance observations. When an observation indicates defective performance, the COR will require the contractor’s representative at the site to initial the observation documentation. The contractor’s representative initialing the observation documentation does not constitute concurrence with the observation, only acknowledgment. Government surveillance of tasks may occur at any time during the performance period. The performance objectives and standards the government will use to assess performance are as follows:

Contractor Performance Standards. The contractor shall perform to the standards outlined in the Services Summary (SS):

E.4.1 Performance Standard Services Summary

E.5 PAST PERFORMANCE INFORMATION

The Government will provide and record Past Performance Information for acquisitions over $150,000 utilizing the Contractor Performance Assessment Reporting System (CPARS). The CPARS process allows contractors to view and comment on the Government's evaluation of the contractor's performance before it is finalized. Once the contractor’s past performance evaluation is finalized in CPARS it will be transmitted into the Past Performance Information Retrieval System (PPIRS). Contractors are required to register in the CPARS, so contractors may review and comment on past performance reports submitted through the CPARS. Go to the following website to register in the CPARS: https://www.cpars.csd.disa.mil/

(END OF SECTION E)

SECTION F – DELIVERIES AND PERFORMANCE

F.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (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 the address below:

DFAR website:

http://farsite.hill.af.mil/ GSAM website:

http://acquisiton.gov/comp/gsam/gsam.html

I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

CLAUSE NO. DATE TITLE

F.2

PERIOD OF PERFORMANCE

This contract shall be effective as of contract award, and the base period shall continue up through twelve (12) months, unless terminated sooner according to its terms. Two (2) annual optional periods are included.

POP FROM TO

F.3

PLACE OF PERFORMANCE

Majority of technical support shall be performed off site at the Contractor’s facility.

Contractor off site locations must provide .mil based network access, which comply with government network and personnel security restrictions. Remote staff may monitor and perform security, maintenance, and testing to manage and validate BI standards, procedures, and conventions for dashboard use.

The contractor shall travel once a month to customer facilities to ensure stability of operations and communicate IA efforts. All travel shall be in accordance with the requirements and guidelines set forth by the Defense Travel Management Office’s (DTMO) Joint Travel Regulations (JTR).

On-Site Support Shall be located at the following CJTF-OIR address:

CJTF-OIR/J4

Bldg 505 Camp Arifjan, Kuwait 09306 F.4

HOURS OF OPERATION

Operational hours will be Monday through Saturday, from 0700 to 1900 hours local time. Personnel required to travel on what is normally a non-duty day for the supported region may be compensated for no more than 8 hours of travel time for that travel day. Travel will be reimbursed at cost in accordance with the policy at FAR subpart 31.205-46.

F.5

DELIVERABLES, REPORTS AND NOTIFICATIONS DELIVERY OF REPORTS

Following the CMMI model, software development is a continuous effort with on-going scheduled updates and reports. The milestone schedule shall have high level activity not weekly software development activity. The software milestones are captured on a rolling basis as in RAD environment.

The Contractor shall provide the Milestones, associated deliverables and projected Schedule in the quote. The Contractor shall monitor and track milestones and project deliverables during the duration of the contract.

F.5.1

MILESTONE SCHEDULE

The Contractor shall define the milestone schedule associated with the development of the BI Tool and sustainment in the offeror’s quote.

The Government will host a meeting with the Contractor to determine and prioritize requirements. Within five days of the meeting, the Government will provide the Contractor with an approved prioritized list of requirements. The Contractor shall review the list and identify any elements outside of the scope of the contract and provide a response within five days of receipt.

Based upon the mutually agreed upon list of requirements, the Contractor shall modify the project schedule including milestones and provide it to the Government within 30 calendar days.

The Contractor shall track the schedule in the monthly status report. The Contractor shall identify any proposed modifications to the schedule in the status report for approval by the COR.

F.5.2

DELIVERABLES

The Contractor shall submit all deliverables IAW the provisions of the PWS. Unless otherwise designated, all deliverable documents shall be delivered to the Government via electronic means utilizing Contracting Command electronic contract management system and submitting in ITSS Action Memos for each deliverable submitted to the COR for approval. All reports and documents shall be in Microsoft Office compatible format or Adobe portable document (PDF) format, as required. Documents shall be prepared in a Government approved Contractor format utilizing commercial best practices. All documentation, reports, software, databases, presentation, and similar material prepared under this contract shall be the property of the Government. The Deliverables below pertain to the life of the contract, including option years.

F.5.3

REPORTS

F.5.3.1

Kickoff Meeting Minutes The Contractor shall capture and provide the minutes of the Kickoff meeting. The report shall be submitted to the government via the Contracting Command IT Solutions Shop (ITSS) web-based contract management system within 5 calendar days of the Kickoff meeting.

F.5.3.2

Weekly Reconciliation Report (WRR) The Contractor shall provide a weekly reconciliation report which shall be submitted by the close of business (COB) on the agreed upon day of the week, until completion of the contract. The report shall be submitted to the government via the Contracting Command IT Solutions Shop (ITSS) web-based contract management system. Format will be determined via coordination with the COR or designated customer representative.

F.5.3.3

Monthly Status Report The Contractor shall provide a monthly status report which shall be submitted by the 15th day of each month until completion of the contract. The report shall be submitted to the government via the Contracting Command IT Solutions Shop (ITSS) web-based contract management system.

The Monthly Progress Report (MPR) shall include the following information:

· Brief description of requirements

· All program management actions

· Summary of new actions and Work Orders initiated.

· Summary of accomplishments during the reporting period and significant events regarding the contract.

· Any current or anticipated problems and the resolution

· Summary of all actions projected and work accomplishments for the next reporting period.

· Summary of all major events and other pertinent information

· Summary of travel completed during the month, to include purpose, name, location, dates.

· Summary of planned travel, to include purpose, name, location, dates.

· Work Order schedules/work plans

· Monthly user statistics reporting

· Summary of development activity

· Summary of test activity

· Upon deployment, summary of Change Requests

· Summary of financial obligation issues identified in the reporting period

· Task performance metrics

· Documentation of Project Schedule

· Proposed modifications to the Project Schedule

F.5.4

BI TOOL DOCUMENTATION

F.5.4.1

Project Schedule and Milestones

F.5.4.2

BI Tool Rapid Application Development (RAD) Plan

The Contractor shall document in a BI Tool RAD Plan the activities to manage the test driven development approach, incorporating the Government’s prototyping and mockup steps, iterative development processes, integrated test plans, and component migration. The report shall be updates as changes occur. The initial report is due 30 calendar days from the task start date and updates submitted within 15 calendar days of the changes identified.

F.5.4.3

Risk Management Plan

The Contractor shall develop the Risk Management Plan in association with the BI Tool development and sustainment on an annual basis. The contractor shall deliver the plan within 15 calendar days from task start date and updated annually and submitted within 15 days of each option period start date exercised.

F.5.5

IT SYSTEMS ENVIRONMENT ESTABLISHMENT

F.5.5.1

Software and Hardware Requirements and Specification

The Contractor shall provide the Software and Hardware Requirements in MS Excel compatible format. The report shall include all the required Software, Software License, Hardware, Network Equipment and connectivity requirements, Server requirements, quantities of each item required.