DRAFT-CJIF-OIR-BI Tool Development SRVCS PWS_CALIBRE_REV_1_(4).docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

SUSTAINMENT READINESS TOOL (SRT)

INTRODUCTION

Client Organization 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.

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

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

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

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.

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.

Information Technology/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.

SIPRNET Option 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.

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.

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.

Develop Dashboards to meet User Requirements 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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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 recosde and retest those areas and remediate the errors. The contractor shall conduct multiple levels of testing, which include functional, integration, and regression testing.

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

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.

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.

The Contractor shall support functional user testing of the dashboards.

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.

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.

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

The Contractor shall then implement these recommendations and develop dashboards to track process improvements against KPIs.

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.

DISA BI Tool IA Compliance Coordination.

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

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

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.

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:

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

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.

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

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

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

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

Network Architecture and Security 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.

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

The Contractor shall facilitate establishment of Single Sign on (SSO) for Computer Access Card (CAC) access.

The Contractor shall support the following:

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

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.

Financial Recovery 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.

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

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

Command Deployment ReadinesReadiness Dashboards (Optional Task) Contractor shall maintain and provide Command Deployment readiness and property accountability dashboard support (CLIN 009). Provide and sustain readiness, property accountability, and in transit status and visibility for units/organizations during pre-deployment, deployment, transfer of authority, re-deployment, and recovery. Use iterative rapid application development processes and prototyping to provide continuous improvement to readiness and accountability dashboards and reports.

Command Deployment readiness CLIN 009 tasks include:

Unit Deployment Support. Integrate reporting processes between existing organization processes and CJTF-OIR processes. Develop and migrate reports between deploying organization and CJTF-OIR SRT to support echeloned support and assist in transfer of authority. Provide report migration and development to allow home station visibility of CJTF-OIR dashboards and reports. Provide additional support/visibility of theater readiness.

Develop and integrate deployment Task Force organization file with existing views to provide to-be equipment readiness status of the deployed force structure.

Migrate, modify, and integrate dashboard and report capabilities for Unit-maintained equipment (UME) readiness visibility. Develop and deploy modified or new dashboard and report capabilities to support home station readiness management during pre-deployment and post-deployment. Develop and deploy modified or new dashboard and report capabilities to provide home station visibility of deployed organization and unit equipment readiness, property accountability and financial management.

Deployment and re-deployment financial, supply and property reconciliation support. Provide transactional system analysis to support auditability, accountability, and readiness management during transition periods before and after deployments. Provide property and financial accountability views and dashboards to track status of redeployment to support FLIPL and property management processes.

Provide Financial Reconciliation and Funds Recovery during pre-deployment and re-deployment to maintain accountability and auditability throughout the pre-deployment through re-deployment process.

Option Period An option period is available for exercise within 60 days of the expiration of the base period in accordance with clause 52.217-9 in section 13.0 of this PWS. The option period covers the services identified in section 3.3, 3.4, and 3.5 of this PWS, only, and extends the contract for an additional 12 month period upon exercise.

DELIVERABLES AND ACCEPTANCE

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 task order.

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.

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.

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

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 task order. 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.

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 task order. 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 task order

· 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

BI Tool Documentation Project Schedule and Milestones 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.

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.

IT Systems Environment Establishment 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. The Government shall utilize this information to coordinate the provision of GFE required for the contractor to stand up the test environment and live application. Details on the Format will be determined via coordination with the COR or designated customer representative. The report is due within 14 calendar days after task start date.

Establish a test environment to host the BI Tool for user test purposes.

The Contractor shall establish a test environment to host the BI Tool for user test purposes installed on the local Camp Arifjan IT system infrastructure.

The Contractor shall support maintenance of the system configuration, compliant with MAC III, Sensitive but Unclassified (SBU) information, DoD and Army IA controls and configuration standards per applicable DISA Security Technical Implementation Guides (STIGs) and checklists; National Security Agency guides; and Security Readiness Review Evaluation Scripts (SRRs) including DISA Gold Disk (Platinum Option), database compliance scripts, and eEye Retina.

This deliverable is due 7 calendar days prior to the first scheduled test date identified in the contractors milestone schedule.

Change Requests.

The Contractor shall provide a list specifying the changes requested and it shall be in MS Word format and submitted via the ITSS Action Memo for COR approval. The Change Request shall include details to identify the changes requested, impact, projected time to implement, and source of the change request including contact info from the source. Format will be determined via coordination with the COR or designated customer representative. All changes recommended by the Government or Contractor shall be documented and submitted for CMB review and approval as Change Requests are completed.

Functionality and User Testing of all completed BI Tools.

The Contractor shall provide the following:

Active Testing Program Plan.

The plan shall address and operate in tight coordination with the mockup and prototyping processes. The Contractor shall design a testing process to confirm throughout the development cycle that the BI Tool meets customer requirements and integrates business processes throughout the entire design. The contractor shall submit the report within 60 calendar days of task award for COR approval.

Client Test Scenarios.

In support of the user acceptance test process, the Contractor shall develop test scenarios related to the new functionality, as well as to the existing functionality, which the scheduled release may impact. The Contractor shall work with the COR or designated customer functional area lead to identify participants in the test and to coordinate testing activity and closely monitor the test environment, document any errors, and collect usability feedback. The Contractor shall submit the Client test Scenario which is due one calendar day prior to the start of the unit/modular/system test for each release or enhancement testing scheduled.

Test Description.

The Contractor shall submit the Test Description reflecting the details of the testing planned for the baseline BI Tool or each enhancement to-be tested and projected testing date and relevant information. The Contractor shall submit each report which is due one calendar day prior to the start of the unit/modular/system testing scheduled.

Test Report.

The Contractor shall submit the Test Report reflecting the results of the testing completed. The Contractor shall submit each report one day prior to each release or enhancement testing scheduled.

Quality Feedback Loop.

The Contractor shall provide a quality feedback loop, for the customer and the developers use in sharing BI Tool government feedback and shall be established within the BI Tool and allow Government review of each feedback response. The Contractor shall provide a quality feedback loop due 60 calendar days from date of award. The contractor shall maintain the feedback loop and sustain this tool throughout the task order period of performance.

Push to Production.

Push to Production of all BI System Tools and enhancements will occur on a scheduled basis. Any products to be deployed shall be submitted and approved by the COR and contain a System Version Description (SVD) document and details to the release and any system availability issues during the push.

Software Anomaly Report.

The Contractor shall provide a report with the details of all identified BI Tool software anomalies. The report shall include a title of each anomaly, description, impact, solution, source and contact information. Format will be determined via coordination with the COR or designated customer representative. The documentation is due within 1 business day following identification of each software anomaly.

Software Anomaly Resolution Report.

The Contractor shall provide a report with the resultant resolution and date resolved. The resolution and report is due within 48 hours of identification of the problem.

Application Configuration Management Plan.

The Contractor shall provide an Application Configuration Management Plan for sustaining quality and changes in the BI Tool and dashboard. Format will be determined via coordination with the COR or designated customer representative. The documentation is due within 30 calendar days of task order award and 15 calendar days from changes identification.

System Version Description.

The Contractor shall provide the BI Tool system version description in a report. Format will be determined via coordination with the COR or designated customer representative. The documentation is due with each system version release.

Trip Reports.

The Contractor shall provide a trip report with the details of each trip completed in performance of this task order. Format will be determined via coordination with the COR or designated customer representative. Report may be consolidated when multiple travelers participate in the same trip. The Contractor shall submit the report for COR approval, which is due within 14 calendar days following completion of each trip.

Presentations and Demonstrations Demonstrations The Contractor shall provide demonstrations of required functionality provided over the period of performance.

The Contractor shall use standard rapid application development practices that incorporate iterative releases that integrate functionality within individual modules as well as within the overall business management capability the Log BI Tool meets.

These practices include routine standup meetings and pushes to production. The Contractor shall coordinate the requirements, solution, and any data sources with the COR prior to the development cycle start. This pre-development effort will speed the dashboard development into a rapid process.

Final Deliverables Source Code Source code and code documentation shall be delivered at the completion of the following milestone:

· Final BI Tool System Approval

· Each Enhancement BI Tool System Approval All source code developed under this PWS becomes sole property of the government w/o restriction.

All source code and accompanying documentation is the property of the Government from date of delivery for COR acceptance. Designated Government representative(s) will have access to the development, test and production code at any time. The Contractor shall maintain documentation within the application.

The Contractor shall identify the proposed format and method of delivery in the initial proposal, as size limitations may prohibit submission via ITSS. COR acceptance will be documented in an action memo in ITSS.

Schedule and Delivery Instructions The specific deliverables and schedule for delivery shall be per the Performance/Deliverables Matrix. The COR reserves the right to prioritize work and negotiate any changes in delivery dates.

The COR will review the contractor’s performance indicators in accordance with all the specifications stated in this document. Only the SCO, COR, CAM or authorized alternate has the authority to inspect, accept, or reject work performed under this task order.

Performance Measures

Inspection and Acceptance.

For deliverables associated with the FFP requirements, inspection and acceptance will occur in accordance with FAR 52.212-4, Deliverables which are not separately priced will be inspected and the contractor notified of the COR’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 for priced services rendered 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 handled in accordance with the terms at FAR 52.212-4. 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.

Quality Control The Government will evaluate the contractor’s performance of this task order. For those services listed in the Performance/Deliverables Matrix, the Client Representative, Contracting Officer Representative (COR), or evaluators will follow the method of surveillance specified in this task order. Government personnel will record all surveillance observations. When an observation indicates defective performance, the Client Representative, COR, or evaluators will require the task order manager or representative at the site to initial the observation. The initialing of the observation acknowledges that he or she has been made aware of the defective performance and does not necessarily constitute concurrence with the observation. Government surveillance of services not listed in the Performance/Deliverables Matrix or by methods other than those listed in the Performance/Deliverables Matrix (such as provided in the Inspection of Services clause) may occur during the performance period of this task order. Such surveillance will be done according to standard inspection procedures or other task order provisions. Any action taken by the SCO as a result of surveillance will be according to the terms of this task order.

Reimbursable Costs Sections 6.1 through 6.4 govern supplies and materials utilized by the contractor in the performance of the task order service. Travel requirements are also included in this section.

Travel The contractor shall ensure that the requested travel costs will not exceed what has been authorized in the task order. Contractor incurred actual expenses resulting from Government directed travel are cost reimbursable but are limited by the Government Joint Travel Regulations (JTR) and must be pre-approved by the COR and Contracting Command SCO. The contractor shall include any anticipated travel costs in the proposal. Indirect costs on Travel will only be allowed if it is specifically provided for in the contractor’s Schedule contract and quoted in the contractor’s quote for this task order and supported by DCMA Rate Authorization Letter.

Locations and the duration of travel cannot be established at this time so a not-to-exceed travel budget (inclusive of indirect costs) for the entire effort is estimated as follows:

Other Direct Costs Contractor incurred actual expenses for other direct costs are cost reimbursable and must be included in the response to this RFQ. Indirect costs on ODCs will only be allowed if it is specifically provided for in the contractor’s Schedule contract and quoted in the contractor’s quote for this task order and supported by DCMA Rate Authorization Letter.

Post Differential Contractor shall invoice post differential rates in accordance with the rates posted by the Department of State at https://aoprals.state.gov/Web920/hardship.asp. Contractor is authorized to charge the current posted rate for Kuwait (Other) during the month to be invoiced.

Defense Base Act (DBA) Insurance Coverage Contractor shall invoice mandatory DBA Insurance coverage costs for all personnel assigned to positions in Kuwait in accordance with the quotation provided in response to this RFQ.

Kuwait Visa 18, Phones, other ODCs Contractor shall invoice mandatory Kuwait Visa 18 costs for all personnel assigned to positions in Kuwait in accordance with the quotation provided in response to this RFQ. Additional ODCs will be reimbursed on a cost reimbursable basis IAW the quotation provided in response to this RFQ.

Training Training of contractor employees assigned to this task order shall be performed at the contractor’s own expense, with these exceptions:

· The Government has given prior approval for training to meet special requirements that are peculiar to the environment and/or operations

· Limited contractor employee training may be authorized if the Government changes hardware or software during the performance of this task order, and it is determined to be in the best interest of the Government

· The Government will not authorize contractor employees training to attend seminars, symposiums, or other similar conferences unless the Contracting Officer or designee certifies and approves that attendance is mandatory for the performance of the task requirements.

In the event that the Government has approved and paid for contractor employee training, reimbursement shall not be authorized for costs associated with re-training replacement individual(s) should the employee(s) terminate from this task order. Costs that are not authorized include labor, travel, and any associated re-training expenses.

Materials As authorized by COR.

PERFORMANCE CRITERIA

Period of Performance Base Period: 07/01/2016-06/30/2017 Option Year 1: 07/01/2017-06/30/2018 Option Year 2: 07/01/2018-06/30/2019 Place of Performance Majority of technical support shall be performed off site at the Contractor’s facility.

On-site support shall be located at CJTF-OIR / J4, BLDG 505, Camp Arifjan, Kuwait, 09306.

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.

Hours of Work The core hours of operations shall be Monday through Saturday from 0700 to 1900 hrs local time.

Key Personnel The contractor shall designate the Program Manager as Key Personnel. All Key Personnel shall be designated in the offeror’s technical quote.

Key Personnel may not be added or removed from the task without coordination with the Contracting Officer or designee. The contractor must attach a copy of the request and KO acknowledgment to the project in the IT Solutions Shop (ITSS) web-based Order Processing System or equivalent. Substitutions of Key Personnel are discouraged, and any substitutions must be of equal of better qualified person(s).

Expertise The contractor is responsible for providing personnel with experience and education as follows:

The contractor shall have proven past performance:

· Operating secure .mil network nodes

· Performing certification and accreditation (C&A) activities

· Interfacing with network enterprise technology command (NETCOM) and related network management authorities

· Developing Business Intelligence tools in support of sustainment readiness and financial management Project Management Personnel Requirements It is mandatory contractor personnel possess a minimum of 10 years’ experience in US Army Supply and or Finance systems, which include the following areas:

· Supply Chain and Financial Reconciliation

· Army Asset Management

· Database Management

· Business Intelligence Information Education: BS/BA/BBA Government Furnished Resources Government Furnished Equipment (GFE) The Government will provide adequate physical work space, desk, telephone service, and computer access as required for on-site contractor personnel.

Items for on-site contractor support include:

· Access to printers.

· Software required in performing task activities.

· Network access for contractor provided laptops and/or desktops.

· Class A telephones.

· Applicable User Ids and passwords.

· Expendable office supplies (pencils, pens, tape, paper, etc.)

· Desktop Locks for laptops and/or CPUs, when needed.

· Development, Test, and Production envionments Limitations. Contractor personnel shall not take Government property from the work place, nor modify it without written request to the Government and written Government permission by the Government’s COR or SCO.

The Contractor shall be responsible for reimbursement to the Government, for the repair or replacement of GFE that is in his possession and that is damaged or lost due to negligence, misuse, or abuse on the part of Supplier’s employees.

Government Furnished Information The Government will provide Government Furnished Information (GFI) including any technical data, drawings, or models necessary for contract performance that are in the Government’s possession.

GFI includes access to the following systems:

· Commodity Command Standard System (CCSS)

· Department of Defense Activity Address File (DoDAAF)

· Federal Logistics Data (FEDLOG)

· Funds Control Module (FCM)

·…