Modification to a Previous Presolicitation Notice – D– Provide Attachment 001 entitled, “PERFORMANCE WORK STATEMENT (PWS) FOR THE U.S. ARMY LOGISTICS MODERNIZATION PROGRAM (LMP) SERVICES”

Source:

Federal Information & News Dispatch, Inc.

Modification to a Previous Presolicitation Notice - D-- Provide Attachment 001 entitled, "PERFORMANCE WORK STATEMENT (PWS) FOR THE U.S. ARMY LOGISTICS MODERNIZATION PROGRAM (LMP) SERVICES"

Notice Type: Modification to a Previous Presolicitation Notice

Posted Date: 23-NOV-11

Office Address: Department of the Army; Army Contracting Command; ITEC4, NCR PARC (NCR-CC); Directorate of Contracting , 2461 Eisenhower Avenue, Alexandria, VA 22331-0700

Subject: D-- Provide Attachment 001 entitled, "PERFORMANCE WORK STATEMENT (PWS) FOR THE U.S. ARMY LOGISTICS MODERNIZATION PROGRAM (LMP) SERVICES"

Classification Code: D - Information technology services, including telecommunications services

Solicitation Number: W91QUZ12D0LMP

Contact: Tiffany Green, 703-325-3432 mailto:[email protected] [ITEC4, NCR PARC (NCR-CC)]

Setaside: N/AN/A

Place of Performance (address): Army Contracting Command - National Capital Region (ACC-NCR) 200 Stovall Street Alexandria VA

Place of Performance (zipcode): 22332-1800

Place of Performance Country: US

Description: Department of the Army

Army Contracting Command

ITEC4, NCR PARC (NCR-CC)

Due to system constraints, the Performance Work Statement (PWS), Attachment 001, was not provided under the original Presolicitation Notice, located under Solicitation Number: W91QUZ12D0LMP dated November 22, 2011. Two modifications will be completed; these modifications hereby provide the PWS as referenced in the Presolicitation Notice (W91QUZ12D0LMP) as Attachment 001. MODIFICATION 1 OF 2 PERFORMANCE WORK STATEMENT (PWS) FOR THE U.S. ARMY LOGISTICS MODERNIZATION PROGRAM (LMP) SERVICES Attachment 001 1 GENERAL 1.1 Introduction. This Performance Work Statement (PWS) is applicable to the performance of the contract from 29 December 2011 to 28 December 2015 and an additional one-year option from 29 December 2015 to 28 December 2016. 1.2 Scope. This document specifies the services the Contractor is required to provide in support of the U.S Army LMP. In accordance with the contract Section H clause entitled H-X "Services to be Ordered," the Program Executive Office Enterprise Information Systems (PEO EIS) shall order from the Contractor, for the period from December 29, 2011 through December 28, 2015 and an additional one-year option, all of the services described in this PWS. These services include Logistics Modernization Services (paragraph 2), Program Management (paragraph 3), Modernized Sustainment Services (paragraph 4), Residual Legacy Sustainment Services (paragraph 5) and Modernized Data Processing/Infrastructure Services (paragraph 6), Transition Services (paragraph 7) and Delivery of Solution and Associated Data (paragraph 8). The Contractor shall perform mutually agreed upon services in accordance with Department of Defense Instruction (DoDI) 5000.02, Operation of the Defense Acquisition System; Business Capability Lifecycle model for Defense Business Systems; and/or other mandated requirements for defense technology projects and acquisition programs. Where mutual agreement is required under this PWS, the Contractor and Government shall jointly use the LMP Issue Management Process. 1.3 Program Data Management Contractor Integrated Technical Information Services (CITIS). The Contractor shall provide CITIS by a mutually agreed methodology which shall: allow authorized Government and Contractor personnel access to digital information during performance of the Contract; provide content management of digital information to include updates, archiving and retirement; provide access to the PAPR; and provide a repository for programmatic documents. Authorized access will be granted by the Contractor's security organization. Access must be possible using personal computer devices running current versions of popular browser software. 1.3.1 Data Accession List (DAL) - CDRL Exhibit A, Data Item No. A001. All Contractor, technical data or computer software generated in the performance of this contract or any subcontract hereunder shall be identified IAW CDRL Exhibit A, Data Item A001, the Data Accession List (DAL), and shall be delivered, if ordered under DFARS 252.227-7027 Deferred Ordering of Technical Data or Computer Software, when not already otherwise ordered. The Government's rights in this technical data or computer software shall be as specified in Clause H-xx. 1.3.2 Use of DD Form 1423-1 The Office of Management and Budget (OMB) approved DD Form 1423-1, and incorporated within the text of this PWS for ease of referencing. All references to DD Form 1423, Contract Data Requirements List (CDRLS) at Attachment AA. 1.3.3 Data Deliverables The Contractor shall utilize Contractor Integrated Technical Information Services (CITIS) for uploading and delivery of all unclassified data deliverables specified in Attachment AA. The contractor will provide E-mail (e-mail) notification to the Contracting Officer (KO) and Contracting Officer COR upon upload/delivery of documents to the CITIS. E-mail notification shall be used as a Letter of Transmittal (LT) e-mailed with each data delivery. The LT shall indicate the contract number, Contract Line Item, Sub-Line Item Number, Data Item Number, Title and Subtitle (when applicable) of the data, PWS paragraph number reference which required the data to be prepared and the date of transmittal. 1.3.3.1 Unclassified: All unclassified data delivered during this contract shall be furnished electronically by uploading digital files to the CITIS established for this contract. E-mail will be used for other correspondence during the contract. 1.3.3.2 Classified: Classified data shall be provided on magnetic or optical media with one hard copy prepared using the file formats specified in 1.3.3. Classified data shall be placed in separate and severable classified appendices rather than making the entire document classified. Classified data shall be handled and delivered in accordance with the DoD 5220.22-M "National Industrial Security Program" - Operating Manual, dated 28 February 2006. 1.3.4 Marking of Documentation Submitted All documentation submitted to the Government must be clearly and completely identified. The Contractor shall include the CDRL sequence number, contractor's name, address, and point of contact; name of project and/or product/system; classification of project; date of submittal; revision level of documentation; name and designator of Government product director; and other data deemed appropriate by the Contractor. Additional identification requirements are specified in Section D of the contract. 1.3.5 Marking of Resubmitted Documentation Documentation resubmitted for evaluation should include a Revision Status page indicating the revision level of each page contained in the re-submission. Additionally, the individual changes on each page should be highlighted (e.g. using change-bar symbols, underlining, asterisks, bold or emphasized print, or similar marking). Although highlighting is not required, it will expedite Government evaluation of the re-submission. 1.3.6 Media and File Format The Microsoft Office suite of applications (MS Word, MS Excel, MS PowerPoint, and MS Project) and Adobe Acrobat PDF are the preferred file formats for data furnished under this contract. For unclassified data uploaded to the Contractor's CITIS, MS Internet Explorer is the preferred browser. All plans, processes and procedures shall be produced in a format compatible with Microsoft Word for Windows using only TrueType fonts and shall be uploaded to the Contractor's CITIS. 1.3.7 Applicable documents All Government documents cited by reference within this PWS will be furnished by the Government. 2 LOGISTICS MODERNIZATION SERVICES The Contractor shall provide the Modernized Services as specified below: 2.1 Implementation Approach 2.1.1 LMP Change Lifecycle Process - CDRL Exhibit B, Data Item No. A002 The Contractor shall use the LMP Change Lifecycle Process. This process shall provide a thorough, defined set of activities for managing development requirements (submit IAW CDRL Exhibit B, Data Item No. A002 and this PWS). The Contractor and Customer Subject Matter Experts shall work together to analyze, integrate, and confirm the LMP requirements. The Contractor shall administer the joint Government-Contractor LMP management boards to include but not limited to the following: Engineering Process Group, Issues Management, Change Review, Architecture Review, Executive Management, and Risk Management. The Contractor shall perform data activities in accordance with the LMP Change Lifecycle Process and the LMP Data Management Plan. 2.1.2 Business Process Map Maintenance - CDRL Exhibit C, Data Item No. A003 The Contractor shall update and maintain Business Process Maps to reflect changes in the Deployed/Operational Production Baseline or the Customer's business processes. Changes to the Deployed/Operational Production Baseline shall be triggered as part of the development lifecycle, whereas, the business process changes will be provided by the Customer. These activities will be conducted throughout all phases. The Contractor shall establish and publish, ongoing basis and as part of the Configuration Management Process as described in section 3.8 below, procedures for preparation; update and maintenance of Business Process Maps (submit IAW CDRL Exhibit C, Data Item No. A003 and this PWS). 2.2 Implementation Activities. The LMP has a Deployed/Operational Production Baseline, which is currently supporting deployed sites. The Deployed/Operational Production Baseline will serve as the basis for future implementation activities. This section 2.2 describes activities that may be executed to accomplish an implementation activity, increase the business effectiveness of the Deployed/Operational Production Baseline, or facilitate effective use of the Deployed/Operational Production Baseline by the Customer. Where applicable, these activities are described in the context of AcceleratedSAP ("ASAP") Methodology Phases in which the activities are typically executed. The Government and the Contractor will mutually agree to the activities and sequence of activities to be executed for future implementation activities in accordance with DoDI 5000.02, Operation of the Defense Acquisition System; Business Capability Lifecycle model for Defense Business Systems; and/or other mandated requirements for defense technology projects and acquisition programs. 2.2.1 Project Preparation. The Contractor shall review its applicable processes and (except where mutual agreement is expressly required in this PWS) update them as the Contractor deems necessary. The Contractor shall update the Integrated Program Master Schedule (IPMS) IAW section 3.6 as applicable to reflect activities to be accomplished and resources needed for the agreed planning horizon. 2.2.2 Business Blueprint. CDRL Exhibit D. Data Item No. A004 The Contractor shall conduct activities to identify gaps across applicable CatalystSM Domains of Change to be addressed in future deployment or other implementation activities. Business Blueprint may also include rapid prototyping activities and requirements documentation production to be reviewed and approved by Government. (submit IAW CDRL Exhibit D, Data Item No. A004 and this PWS). 2.2.3 Business Transformation Management Plan - CDRL Exhibit E, Data Item No. A005. The Contractor shall review and update the Business Transformation Management Plan (BTMP) (submit IAW CDRL Exhibit E, Data Item No. A005 and this PWS) as mutually agreed and execute Business Transformation activities during Business Blueprint in accordance with the approved BTMP to include the following: 1) Stakeholder Alignment, 2) Site Readiness Activities, 3) Business Process Mapping, 4) Stakeholder Education, and 5) Data Quality Education and Benchmarking, 6) Functional Security Role Development and 7) Development of Data Cleanup Activities. 2.2.4 Domains of Change Gap Identification - CDRL Exhibit F, Data Item No. A005. The Contractor shall conduct Solution Demonstration LabsSM or other workshops as appropriate to demonstrate the LMP solution and identify gaps in applicable CatalystSM Domains of Change. The Contractor shall document the identified gaps and mitigation strategies, which will form the basis for planning future enhancements or other implementation activities (submit IAW CDRL Exhibit F, Data Item No. A005 and this PWS). 2.2.5 Realization. The Contractor shall execute Realization activities as mutually agreed by the Government and Contractor. Realization activities shall include specification development, Reports, Interfaces, Conversions, Enhancements, and Forms (RICEF) object development, training material production, training of key users and end-users, deployment of solution in to production, and break-fix. 2.2.6 Final Preparation Prior to production/go-live, the Contractor shall execute final preparation activities including but not limited to: unit testing, integration testing, user training and testing, and cut-over/migration of cleansed master data and transaction data. 2.2.7 Go Live & Support The Contractor shall cutover development efforts from a project-oriented, pre-production environment to a fully-operational live production system. 2.2.8 Application. The Contractor shall implement application changes to the Deployed/Operational Production Baseline in accordance with the LMP Development Lifecycle and Process Guide and the IPMS and subject to the Configuration Management Process described in section 3.8 below 2.2.9 Compliance. The LMP is required to maintain compliance across a broad spectrum of areas. The deployed operational baseline as of 28 December 2011 will be the initial baseline for compliance. All compliance requirements will be maintained or the developed IAW the life cycle process for applicable enhancements, extensions, modifications and upgrades. The Government shall secure the appropriate independent assessment groups for compliance requirements (e.g., AAA for FFMIA, BTA for SFIS, DoDIG for USSGL). In addition, the Government shall monitor progress of demonstrating compliance by the targeted dates, and proactively addresses risks or issues as they are identified. The Contractor shall implement compliance changes to the Deployed/Operational Production Baseline in accordance with the LMP Development Lifecycle and Process Guide and the IPMS and subject to the Configuration Management Process described in section 3.8 below 2.2.9.1 Standard Financial Information Systems (SFIS) evaluations - (as required by Financial Management Regulation (FMR) Volume 1) SFIS Version 8 is the current version. The Contractor shall in collaboration with the Government review/analyze and provide an assessment to the government within 90 days of new SFIS Version (s), of any changes and/or additions required to maintain and achieve compliance, to include a determination against the existing baseline, which changes/adds are in the currently deployed baseline and which require added functionality/documentation to support LMP's compliance. The LMP Final Regression Test (FRT) process shall include verification that SFIS compliance is maintained prior to releases at a level of detail that allows an outside audit agency to perform periodic audits and/or full attestation. SFIS requirements not in the current baseline shall be identified to the Army. LMP shall be required to maintain compliance thru out its system life time. Periodic reviews and evaluations will be required throughout the systems life time 2.2.9.2 New Blue Book Requirements Federal Financial Management Improvement Act (FFMIA) - in accordance with Blue Book updates (Version January 2011 is the current version with updates/new versions every other year). The current FFMIA baseline is 1,298 requirements. The Contractor in collaboration with the Government shall review/analyze and provide an assessment to the government within 90 days of new Blue Book Version, of any changes and/or additions required to maintain and achieve compliance, to include a determination against the existing baseline, which changes/adds are in the currently deployed baseline and which require added functionality/documentation to support LMP's compliance. The LMP Final Regression Test (FRT) process shall include verification that FFMIA compliance is maintained prior to releases at a level of detail that allows an outside audit agency to perform periodic audits and/or full attestation. LMP shall be required to maintain compliance thru out its system life time. Periodic reviews and evaluations will be required throughout the systems life time. 2.2.9.3 Financial Improvement and Audit Readiness (FIAR) The contractor shall, in collaboration with the Government and in accordance with OMB Circular A-123, and the May 2010 FIAR Guidance, insure the LMP system maintains full compliance as detailed in OMB Circular A-123, and the May 2010 FIAR Guidance. The contractor shall, in collaboration with the Government and on a periodic basis, every other year, perform a review and assessment of the currently deployed LMP to insure LMP compliance and ability to achieve FIAR in 2017. The contractor shall, in collaboration with the Government identify any changes and/or additions required to maintain and achieve compliance, to include a determination against the existing baseline, which changes/adds are in the currently deployed baseline and which require added functionality/documentation to support LMP's compliance. The LMP Final Regression Test (FRT) process shall include verification that compliance is maintained prior to releases at a level of detail that allows an outside audit agency to perform periodic audits and/or full attestation as defined in the FIAR and OMB Circular A-123. LMP shall be required to maintain compliance thru out its system life time and achieve full compliance by 2017 as outlined in FIAR/OMB Circular A-123. Periodic reviews and evaluations will be required throughout the systems life time. 2.2.9.4 United States Standard General Ledger (USSGL) - (required by DoDIG and the FMR Volume 1 and Blue Book requirements) In accordance with any updates/changes/adds based on new Blue Book versions, SFIS versions and changes to the USSGL directed by OSD or Treasury thru changes in FMR Volume 1 the contractor shall insure that the LMP system maintains the correct chart of accounts to support all aspects of compliance. The contractor shall in collaboration with the Government on a periodic basis, every other year, perform a review and assessment of the currently deployed LMP chart of accounts/USSGL and insure LMP compliance. The contractor shall identify any changes and/or additions required to maintain and achieve compliance, to include a determination against the existing baseline, which changes/adds are in the currently deployed baseline and which require added functionality/documentation to support LMP's compliance. The LMP Final Regression Test (FRT) process shall include verification that USSGL/chart of accounts compliance is maintained prior to releases at a level of detail that allows an outside audit agency to perform periodic audits and/or full attestation. LMP shall be required to maintain compliance thru out its system life time. Periodic reviews and evaluations will be required throughout the systems life time. 2.3 COTS Application Software. The Contractor shall assess, recommend strategies and approaches, and, as mutually agreed by the Government and Contractor, implement new, or upgrades to, COTS application software applicable to the Deployed/Operational Production Baseline on a regularly and mutually agreed to basis in order to maintain COTS application software current and within supportability matrix defined by the COTS application software vendor. Contractor shall ensure that any enhancements or changes made to the RICEF objects by Contractor do not conflict with the COTS software. 2.4 Solution Architecture The Contractor shall provide guidance (to establish architectural direction, maintain the integrity of the Deployed/Operational Production Baseline, and support its alignment with Army's Business Systems Information Technology (BSIT) strategy and Business Enterprise Architecture, 2.4.1 Business Enterprise Architecture - CDRL Exhibit G, Data Item No. A006. Upon request from Government and at minimum on an annual basis, Contractor shall create, maintain and deliver IAW CDRL Exhibit G, Data Item No. A006 and this PWS to Government artifacts required for Business Enterprise Architecture (BEA) compliance that include the Department of Defense Architecture Framework (DoDAF). Upon request from the Government, the Contractor shall assist and provide information required to complete the Architecture Compliance And Requirements Traceability (ACART) (https://acart.bta.mil/) tool from the Business Transformation Agency (BTA), and Army Portfolio Management Solution (APMS) assertion forms. Contractor assistance shall include pertinent materiel, personnel and resources knowledgeable with the DoDAF and ACART requirements, as well as hands-on knowledge with LMP relevant to the BEA requirements. Contractor shall provide upon request from Government access for Government designated personnel to the ARIS modeling tool or similar. 2.5 Release Management Procedure. The Contractor shall provide support for application software release strategies for the Deployed/Operational Production Baseline. The Contractor is responsible for coordination and communication of release content in accordance with the Release Management Procedure 2.6 Emerging Requirements. Under any task order issued to incorporate modified or additional Government requested functionality, the Contractor shall perform requirement analysis, software design, coding, testing, system integration, and provide complete documentation, for the requested functionality. Examples of additional functionality are engineering change proposals/functionality changes, and ongoing compliancy changes. These include but not limited to: LMP Site Support Training Enterprise Data Warehouse (EDW) Query Writing Integration Workshops Other ERP Integration 3 PROGRAM MANAGEMENT The Contractor shall provide program management of its performance in the following areas: 3.1 Facilities Administration Planning. Coordination and administration of Contractor space used by Contractor, subcontractor and Government personnel. 3.2 Contract Administration. Contract negotiation, administration and close out. 3.3 Subcontract Administration. Subcontract negotiation, administration and close out. 3.4 Financial Administration. Planning and tracking of contract costs and related data and financial reporting as specified in Reporting section 3.9. 3.5 Human Resources Administration. Coordination of Contractor staffing requirements, solicitation of qualified resources, market research, processing new hires and terminations. 3.6 Integrated Program Master Schedule. The Contractor shall develop and maintain the IPMS. IPMS shall be managed IAW LMP IPMS Maintenance Processes and support the LMP Earned Value Management System IAW para. 3.9.1. The IPMS shall provide the framework and overall schedule for managing and integrating the program. The IPMS includes the following: 1) Work breakdown structure that decomposes the program into major units of work, 2) Dependencies among major units of work for the program, 3) Contractor work effort and Contractor resources required, and 4) Schedule highlighting the program lifecycle activities or key events. 3.7 Security Administration. Management of personal and facility-related security in accordance with Contractor's security policies and procedures and DoD 8570.01-M, Information Assurance Workforce Improvement Program (DFARS 252.239-7001 Information Assurance Contractor Training Certification, 239.7103(b)), DoDI 8500.2 Information Assurance Implementation, February 6, 2003, Information Assurance Contractor Training and Certification, as prescribed in as well as paragraph 6.2 of this PWS. 3.8 Configuration Management - CDRL Exhibit H, Data Item No. A007 The Contractor shall provide configuration management in accordance with the Configuration Management Plan. The Contractor shall review the Configuration Management Plan annually and update as mutually agreed by the Government and Contractor. The Contractor shall support Government configuration management audits, as well as, Government Accountability Office (GAO) audits, Army Audit Agency (AAA) and other government agencies as required. Submit IAW CDRL Exhibit H, Data Item No. A007 and this PWS. 3.9 Reporting. The Contractor shall provide to the Government accurate and timely reporting as described in this document as well as referenced attachments and memoranda in accordance with mutually agreed-upon formalized standards, and formats prescribed by Federal regulatory policies and/or Department of Defense procedures in accordance with DoDI 5000.2, Operation of the Defense Acquisition System, reporting requirements for defense technology projects and acquisition programs. All reports shall be submitted to the Government in formats as directed in the applicable DID. 3.9.1 Earned Value Management (EVM). The contractor shall establish, maintain, and use in the performance of the Cost Plus portions of the contract, an integrated performance management system for reporting purposes. Central to this integrated system shall be a validated Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor's management processes and systems to include the IPMS, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic and most likely duration for each activity and event. 3.9.2 Integrated Baseline Reviews (IBRs) - CDRL Exhibit I, Data Item No. A008. The contractor shall engage jointly with the Government's program manager in IBRs to evaluate and report the risks inherent in the contract's EVMS performance measurement baseline. Risks shall be reported IAW CDRL Exhibit I, Data Item No. A008 and this PWS. Initially, this shall occur as soon as feasible but not later than six months after award of the contract modification incorporating this PWS, and subsequently following all major changes to the baseline. Each IBR shall verify that the contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR shall also record and report any indications that effective Earned Value Management (EVM) is not being used 3.9.3 Contractor Performance Report (CPR) - CDRL Exhibit J, Data Item No. A009 The contractor shall prepare and deliver a Contractor Performance Report IAW CDRL Exhibit J, Data Item No. A009 and this PWS as mutually agreed upon by the Contractor and the Government in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in ANSI/EIA-748. 3.9.4 Contractor Cost Data Report (CCDR) - CDRL Exhibit K, Data Item No. A010 The contractor shall prepare and deliver a Contractor Cost Data Report IAW CDRL Exhibit K, Data Item No. A010 and this PWS as mutually agreed upon by the Contractor and the Government in accordance with Department of Defense Instruction (DoDI) 5000.02, Operation of the Defense Acquisition System; Business Capability Lifecycle model for Defense Business Systems; and/or other mandated requirements for defense technology projects and acquisition programs. 3.9.5 Software Resource Data Report (SRDR) - CDRL Exhibit L, Data Item No. A011 The contractor shall prepare and deliver a Software Resource Data Report IAW CDRL Exhibit L, Data Item No. A011 and this PWS as mutually agreed upon by the Contractor and the Government in accordance with Department of Defense Instruction (DoDI) 5000.02, Operation of the Defense Acquisition System; Business Capability Lifecycle model for Defense Business Systems; and/or other mandated requirements for defense technology projects and acquisition programs. 3.9.6 Key Performance Parameters (KPPs) - CDRL Exhibit M, Data Item No. A012. KPPs will be reported formally and submitted IAW CDRL Exhibit M, Data Item No. A012 and this PWS. KPPs are identified in Attachment XX. 3.9.7 CPFF Labor Distribution Report On a weekly basis, the Contractor shall provide to the Government a CPFF Labor Distribution Report. This CPFF Labor Distribution Report shall be submitted by Friday of the following week. The CPFF Labor Distribution Report shall be in the format of the "LMP CPFF Labor Dist 12-07-07.pdf". 3.9.8 Canary Report On a weekly basis, the Contractor shall provide to the Government a Program Dashboard Report (aka Canary Report). This Program Dashboard Report shall be submitted by Friday of the following week. The weekly Program Dashboard Report shall be in the format of the "Logistics Modernization Program Canary Report" dated October 5, 2007 or other format as mutually agreed by the Government and Contractor. On a weekly basis, the Contractor shall provide to the Government then-current IPMS will be provided to the government in Adobe pdf format and upon request in MS Project format. The IPMS will be posted on the CITIS by Wednesday of each week. Reported data should be no older than previous Friday. 3.9.9 CPFF Budget to Actual and Variance Cost Report On a monthly basis until EVMS is implemented, the contractor shall provide to the Government a CPFF Budget to Actual and Variance Cost Report. This Budget to Actual and Variance Cost Report shall be submitted by the third Friday of the following month. The Budget to Actual and Variance Cost Report shall be in the format of the "LMP Baseline BvA-Sept 07_Govt.xls" and will report all costs (direct and indirect, including travel and other direct costs) for services ordered on a CPFF basis. 3.9.10 Program Monthly Status Report - CDRL Exhibit N, Data Item No. A013. On a monthly basis, the Contractor shall provide to the Government a program status report (submit IAW CDRL Exhibit N, Data Item No. A013 and this PWS). The Program Monthly Status Report shall include information related to the Logistics Modernization Services and Modernized Sustainment Services. The Program Monthly Status Report shall be in the format of the CSC Document Control Number: W0123P000007 and dated May 13, 2011 without Canary Report. 3.9.11 Program Dashboard Report. On a weekly basis, a Program Dashboard Report (Quad Chart/Weekly Status Report) shall be submitted by Friday of the following week. 3.9.12 System Change Status Report - CDRL Exhibit O, Data Item No. A014. The System Change Status Report shall document the Contractor's planning and progress in the implementation of task order system change requirements and/or projects work efforts and shall contain accomplishments toward completion of active system change requests detailing the contractor's estimated completion date, percentage of the work completed, development status phase, planned release and any risk management issues or other comments pertinent to the work to be completed (submit IAW CDRL Exhibit O, Data Item No. A014, and this PWS). 3.9.13 Contractor Other Direct Cost (ODC) Report The Contractor shall provide a monthly ODC report to include Facilities cost, Number of workstations, Number of Square Feet, Cost per Square Foot and Total Cost and Teleconference cost, Teleconference numbers, Rate charged, Minutes per month for each number, Charge per month for each number, and total cost per month. 3.10 Quality System Plan - CDRL Exhibit P, Data Item No. A015. The Contractor shall provide, to the Government quality management in accordance with the Quality System Plan. The Contractor shall document Quality System Plan details of the Contractor's quality system, including management commitment to quality, system elements, policy, and practices. In the Plan, the Contractor shall identify the means by which the Contractor will ensure quality system effectiveness and demonstrate comprehensive management and review of data, such that the results may be used to indicate trends and progress in quality of LMP application design, build, and test. The Plan shall describe what is measured, how often it is tracked, and who reviews and assures that appropriate action is initiated when trends are unfavorable. The Contractor shall review the Quality System Plan annually and update as mutually agreed between the Government and Contractor (submit IAW CDRL Exhibit P, Data Item No. A015 and this PWS). 3.11 Risk Management Plan - CDRL Exhibit Q, Data Item A016. The Contractor shall provide risk management in accordance with the Risk Management Plan. The Contractor shall review the Risk Management Plan annually and update as mutually agreed by the Government and Contractor (submit IAW CDRL Exhibit Q, Data Item A016 and this PWS). 3.12 Management of Program Documentation, Plans, Processes and Procedures The Contractor shall document and post on the PAPR all Program-Level processes and procedures on the CITIS. These processes will be reviewed and approved by the Engineering Process Group (EPG). Additionally, as mutually agreed-upon by Government and Contractor, the Contractor shall support the creation and updating of program documentation in accordance with DoDI 5000.02, Operation of the Defense Acquisition System; Business Capability Lifecycle model for Defense Business Systems; and/or other mandated, requirements for defense technology projects and acquisition programs. The contractor will at a minimum support the creation and updating of the below documents, plans, processes and procedures: Data Management Strategy Information Support Plan (ISP) Lifecycle Sustainment Plan Test Plan Acquisition Information Assurance (IA) Strategy Systems Engineering Plan 3.13 Deployed/Operational Production Baseline Documentation In accordance with the Solution Manager Processes, the Contractor shall populate and maintain in Solution Manager the following Deployed/Operational Production Baseline documentation:, 1) Technical Object Functional and Technical Specifications, and 2) Business Process Maps in pdf format. Contractor shall populate and maintain in uPerform Training and Reference Documentation. The Contractor shall review the Solution Manager Processes annually and update as mutually agreed by the Government. 3.13.1 Testing (Individual Test Plans and Master Test Plan) - CDRL Exhibit R, Data Item No. A017. The Contractor shall test all changes, additions and/or deletions to the Deployed/Operational Production Baseline IAW Directive-Type Memorandum (DTM) 11-009, Acquisition Policy for Defense Business Systems (DBS) dated June 23, 2011 concerning the Business Capability Lifecycle (BCL). All contractor testing shall be conducted to align with BCL requirements and the program's Business Case documentation testing requirements, and integrated with other programmatic activities such as portfolio management, Business Process ReEngineering (BPR), system requirements, integration risk, technical architecture, enterprise architecture compliance, NetOps requirements, change management, policy and process documentation, system installation, system configuration, training development, information assurance, organizational realignment, training, user support, software and hardware distribution, and operations and support. The Contractor shall obtain Government concurrence as mutually agreed to by the Government and Contractor prior to release of all changes, additions and/or deletions to the Deployed/Operational Production Baseline. Government concurrence shall be obtained in accordance with the Individual Test Plans. The Contractor shall store Change Request test results in an appropriate repository. Test Defects and Problem Trouble Reports (PTRs) shall be documented and tracked in accordance with the Problem Tracking and Correction section of the LMP Test Plan. The Contractor will support additional evaluations (for example Federal Financial Management Improvement Act (FFMIA), Army Audit Agency (AAA), Army Test and Evaluation Command (ATEC), Operational Assessment) and the Test & Evaluation (T&E) Working Level Integrated Product Team (WIPT) as needed, and as directed by the Program Director to ensure compliance with BCL directives for testing. (submit IAW CDRL Exhibit R, Data Item No. A017 and this PWS). 3.13.2 Testing Strategy. The Contractor shall adhere to the testing strategy and approach as documented in the LMP Test Plan. The Contractor shall review the LMP Test Plan and the Program's Business Case LMP Test Plan and the Program's Business Case documentation annually and whenever the program is significantly changed or restructured to ensure compliance and update plans as mutually agreed by the Government and Contractor. This plan will include individual plans below in addition to any formal test events required for future deployment, upgrades, task orders, and/or audit/compliance reasons to include Federal Financial Management Improvement Act (FFMIA) Testing. The contractor shall document the specific approach in each of the following Individual Test Plans and shall support all Test and Evaluation reviews as required by the program: 1) Unit and String Testing, 2) Integration Testing, 3) Targeted Regression Testing, 4) Functional Security Role Testing, 5) Process and Data Integration Test (PDIT) 6) Final Regression Testing (FRT), 7) Interface Testing, 8) Business Operations Test (BOT) 9) Data Migration Testing, 10) Sustainment Testing, 11) Infrastructure and Information Assurance Testing and 12) FFMIA Compliance and Attestation Testing. 3.13.3 LMP Test Plan. The LMP Test Plan shall define the overall testing strategy and approach for the Logistics Modernization Program and integrated with the Program's Business Case documentation. The LMP Test Plan shall document the scope, approach, test strategies, roles and responsibilities, for the contractor, LMP Project Office, and affected organizations within the Army test environment, defect resolution, assumptions, risks and constraints. The LMP Test Plan shall define an approach by which individual test plans will indicate what lessons learned from prior tests or releases have been applied to the test and how. The LMP Test Plan shall reference the required Individual Test Plans. 3.13.4 Individual Test Plans. Each Individual Test Plan referenced in the LMP Test Plan shall be a separate document. Each Individual Test Plan shall describe the purpose, scope, approach, roles and responsibilities, test environment, test measurement metrics, sequence of intended testing activities, test entrance criteria, test exit criteria, Problem Trouble Reporting (PTR), internal and external interfaces, as applicable, and use of Operational Data, as applicable, in testing activities, and lessons learned being applied to the test. Each Individual Test Plan shall describe the generation of Test Scripts that will have pass-fail criteria and specific testing conditions (to consider Boundary Testing and Variant Testing, and Positive Testing and Negative Testing). The Individual Test Plan shall reference the templates to be used in documenting the test activities. 3.13.5 Test Scripts. Contractor shall create test scripts per the requirements with a requirements traceability mechanism for mapping purposes. A requirements traceability mechanism shall only apply to changes to the Deployed/Operational Production Baseline. The test scripts define the scenarios and data elements needed to test the requirement. Scripts must be approved by the Architecture Review Board (ARB) prior to starting a test. 3.13.6 Test Schedule. Contractor shall include date and duration of each test in the IPMS. In addition, the Contractor shall develop and maintain detailed schedules for all major test events including but not limited to FRT, FFMIA testing and any other formal test event required for future deployments, upgrades, task orders, and/or audit/compliance reasons as mutually agreed by the Government and Contractor. 3.13.7 Test Readiness Review (TRR). The Contractor shall perform a TRR with the Government prior to the start of FRT, FFMIA testing, and any other formal test event required for future deployments, upgrades, task orders, and/or audit/compliance reasons as mutually agreed by the Government and Contractor, for additional test events. The Contractor shall obtain Government concurrence prior to commencing any formal test event. Government concurrence shall be dependent partly but not exclusively on the entrance criteria specified in the test's individual test plan having been fully met. 3.14 Contractor Manpower Reporting. The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor will report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor is required to completely fill in all the information in the format using the following web address: https://contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer's Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of Contractor employee entering data; (5) Estimated direct labor hours (including subcontractors); (6) Estimated direct labor dollars paid this reporting period (including subcontractors); (7) Total payments (including subcontractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where Contractor and subcontractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and subcontractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor's systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web. 4 MODERNIZED SUSTAINMENT SERVICES The Contractor shall provide the Modernized Sustainment Services as specified below: 4.1 Modernized Sustainment Services. The Contractor shall furnish, operate and manage the Deployed/Operational Production Baseline. Operation and management shall ensure that the sustainment services meet the KPPs identified in attachment XX. The operation and management shall be in accordance with the following plans resident in the PAPR: 1) LMP Services Management Plan, 2) LMP Sustainment Plan, 3) LMP Archiving Plan, and 4) LMP Data Management Plan and in accordance with Deployed/Operational Production Baseline documentation resident in Solution Manager. These services shall be available 24/7 for the Deployed/Operational Production Baseline, except for outages resulting from; Defense Information System Agency (DISA) or Department of Army Theater Network Operation Support Center (TNOSC) activities; Government approved scheduled maintenance activities; Disaster Recovery Plan (DRP) and disaster recovery activation. The Contractor shall provide an objective methodology for monitoring and reporting Deployed/Operational Production Baseline availability and performance. 4.1.1 Disaster Recovery Plan (DRP) - CDRL Exhibit S, Data Item A018. The Contractor shall provide a Disaster Recovery Plan (DRP) to Government to facilitate the recovery and restoration of system function compliant with DoD MAC II system requirements or better. Contractor shall ensure that any material changes to the system and its components that affect DRP will be subject to version control as described in Section 3.8 and will be updated in a timely manner. Disaster Recovery capability shall be tested on an annual basis upon request by the Government and submit IAW CDRL Exhibit S, Data Item A018 and this PWS. 4.2 Initial Requirements Analysis - The Contractor shall evaluate Government-proposed Work Requests to assess feasibility and impact on the Deployed/Operational Production Baseline and provide an execution plan. The execution plan will include classification and time to complete the Work Request. 4.3 Corrective, Preventive and Adaptive Maintenance. The Contractor shall provide corrective, preventive and adaptive maintenance to the Deployed/Operational Production Baseline as follows: 4.3.1 Corrective Maintenance Corrective Maintenance shall be provided to all components of the Deployed/Operational Production Baseline, including the hardware, operating systems, COTS application software, developed software, and network assets when necessary to restore the Deployed/Operational Production Baseline. 4.3.2 Preventive Maintenance Preventive Maintenance shall be provided as Contractor deems necessary to avoid degradation of the Deployed/Operational Production Baseline. 4.3.3 Adaptive Maintenance Adaptive Maintenance shall be provided to: 1) ensure that the Deployed/Operational Production Baseline remains in compliance with Fiscal Year changes and regulatory changes; 2) provide production maintenance changes, external applications interfaces, and access control; and 3) implement processing efficiencies. 4.4 Help Desk Support - Help Desk Report - CDRL Exhibit T Data Item A019. The LMP Help Desk will provide end user support with a mix of live and automated support 24 x7 for any issues that cannot be resolved by resources at the Command sites. The Help Desk resources will receive calls and track them using the Unicenter Service Desk (USD) system. The mission of the LMP Help Desk is to provide a single effective primary point of contact for all appropriate levels of computing, networking services and technical support. The Help Desk will resolve the issue (first call resolution) or distribute the call to the appropriate LMP support staff or technology group to best meet the needs of the Commands. The LMP Help Desk staff will field questions and issues via telephone, e-mail or the LMP CITIS. The contractor shall provide the government with a Help Desk Report consisting of extract tables refreshed from production USD. Tables shall consist of: Call_Req-Current Open Tickets, Call_Req-Tickets Closed Last 30 Days; Call_Req-Tickets Closed 31-60 Days Ago, Call_Req-Tickets Closed 61 to 90 Days Ago, contacts, CR-STAT, Loc, Org, Pri, and PROB_CTG and submit IAW CDRL T, Data Item A019 and this PWS. 4.5 Deployed/Operational Production Baseline Support Services. The Contractor shall provide Deployed/Operational Production Baseline Support services for all functional areas supported by the Deployed/Operational Production Baseline. These services include: Initial consultations with the Customer on proposed change(s) to the Deployed/Operational Production Baseline. Assessment of impacts to the Deployed/Operational Production Baseline for proposed changes. Participation (in person or telephonically) in technical and/or functional interchange meetings where the topics discussed could affect the Deployed/Operational Production Baseline. (Note: OCONUS travel, if required, will be mutually agreed by the Government and Contractor.) 4.5.1 Training Materials - CDRL Exhibit AJ, Data Item A034. The Contractor shall create and/or update training materials when required by corrective, preventive or adaptive maintenance activities that change the Deployed/Operational Production Baseline. Submit IAW CDRL Exhibit AJ, Data Item No. A034 and this PWS. 4.6 Solution Documentation - CDRL Exhibit AK, Data Item A035. The Contractor shall update solution documentation when required by corrective, preventive or adaptive maintenance activities that change the Deployed/Operational Production Baseline. Submit IAW CDRL Exhibit AK, Data Item No. A035 and this PWS. 4.7 Additional Functionality - CDRL Exhibit AL, Data Item A036. Under any task order issued to incorporate modified or additional Government requested functionality, the Contractor shall perform requirement analysis, software design, coding, testing, system integration, and provide complete documentation and required training, for the requested functionality. Examples of additional functionality are engineering change proposals/functionality changes, and ongoing compliancy changes. Submit IAW CDRL Exhibit AL, Data Item No. A036 and this PWS. 5 RESIDUAL LEGACY SUSTAINMENT SERVICES The Contractor shall provide Legacy Sustainment Services as specified below for the residual legacy systems (Attachment XX). 5.1 Help Desk Support Services User support through the operation of a 24/7 Help-Desk staffed with a mix of live and automated support. The contractor shall submit on a monthly basis, by the second week of the month following the report period, the Help Desk Problem Report (PR)/Interim Change Package (ICP) Report. This report shall allow the Government to verify the acceptability of ICPs fielded as solutions to Help Desk initiated PRs. Report should include: PR number, Date PR opened, name of caller, phone number of caller, email of caller, Application(s) affected, status, description, closed date, comments. 5.2 Access Control. Access Control function for archived data files. 5.3 Maintenance of Residual Legacy Systems and Subsystems. Maintenance will include analysis, design, development, testing, documentation, release management and training to ensure continuity of service to the users and maintain baseline functionality of the Systems and Subsystems. The Contractor will provide application code and/or parametric changes to implement, as Contractor deems necessary, Data Center Related Changes, Fiscal Year Changes, and Regulatory Changes, changes to address Production Processing Problems, External Application Interface Changes and Processing Efficiency Improvements. The Contractor will maintain and sustain the legacy data archive environment and access tools and assist users in viewing the data. 5.4 Subject Matter Expert Services. As requested by the Contracting Officer or Contracting Officer's Representatives (COR), provide Subject Matter Expert Services across all functional areas supported by the Residual Legacy Systems and Subsystems as follows: Assessments of impacts of Customer-requested and/or Contractor-proposed change(s) to the Residual Legacy Systems and Subsystems. Participation in technical and/or functional interchange meetings where the topics discussed could affect the Residual Legacy Systems and Subsystems. Software installation assistance at Customer sites. 5.5 Change Notification. Notify Customer's user base of any Contractor-planned and Contractor-implemented changes to the Residual Legacy Systems and Subsystems. 5.6 Documentation - CDRL Exhibit AM, Data Item A037. Update baseline documentation when required by changes to the Residual Legacy Systems and Subsystems, and provide notification to the users of updated baseline documentation. Submit IAW CDRL Exhibit AM, Data Item No. A037 and this PWS. 5.7 Additional Functionality - CDRL Exhibit AN, Data Item A038. Under any task order issued to incorporate modified or additional Government-requested functionality, the Contractor shall perform requirement analysis, software design, coding, testing, system integration, and provide documentation, for the approved changes. The Contractor shall perform Replication, Distribution, Installation, and Training (RDIT) resulting from these approved changes. Submit IAW CDRL Exhibit AN, Data Item No. A038 and this PWS. 6 MODERNIZED DATA PROCESSING/INFRASTRUCTURE SERVICES The Contractor shall provide the Data Processing/Infrastructure Services specified below: 6.1 Data Processing/Infrastructure Services for the Deployed/Operational Production Baseline. The Contractor shall operate and manage the infrastructure necessary to support the Deployed/Operational Production Baseline and the applicable development, quality assurance and training environments, including the hardware, networking equipment and network lines up to the demarcation point, software, software licenses facilities, maintenance, and upgrades. At no cost to the Contractor, individual Government user sites/installations will provide and maintain their own desktop PC and local area network communications capabilities to utilize the Deployed/Operational Production Baseline. The Government will provide the long-haul communications network requirements at no cost to the Contractor. The services shall be available 24/7 for the Deployed/Operational Production Baseline, except for outages resulting from: Defense Information System Agency (DISA) or Department of Army Theater Network Operation Support Center (TNOSC) activities; Government approved scheduled maintenance activities; and disaster recovery activation. The Contractor shall provide monitoring and reporting Deployed/Operational Production Baseline availability and performance. 6.1.1 User Access Management Tool. The Contractor shall develop, document, educate, train, implement, and sustain the User Access Management (UAM) Tool. 6.2 Information Assurance Compliance. The Contractor shall implement information assurance standards in accordance with AR 25-2, Information Assurance, 24 Oct 2007 6.2.1 Information Assurance Requirements. DIACAP-required activities to be performed by the Contractor include: Maintain the currency of the LMP Authority to Operate (ATO) and associated Accreditation Documentation. Provide Information Assurance Security Officer (IASO) and alternate IASO who will perform the roles and duties defined in the DIACAP. Perform Infrastructure and Information Assurance Testing in accordance with paragraph 3.14.2. 6.2.2 Information Assurance (IA) Certification & Accreditation (C&A). LMP is required to maintain IA C&A according to DOD and Army IA Policies and Regulations that includes DoD Information Assurance Certification and Accreditation Process (DIACAP) certification with Authority to Operate (ATO), DISA Authority to Connect (ATC), Certificate of NetWorthiness (CoN) and Private Impact Assessment certification (PIA). Contractor shall support the creation and updating the following below: i) DIACAP Certification Checklist, ii) Information Assurance (IA) Plan Of Action and Milestones (POAM), iii) the Risk Acceptance and Mitigation report, and iv) List of Immediate Trading Partner Interfaces and provide support for the site survey by PEO/EIS IA Program Manager. Contractor shall produce and maintain the following IAW CDRLS listed below: i) Listing of Hardware and Software List used by LMP and ii) Network Topology Diagram. 6.2.2.1 Listing of Hardware and Software used by LMP - CDRL Exhibit U, Data Item No. A020 and this PWS 6.2.2.2 Network Topology Diagram - CDRL Exhibit V, Data Item No. A021 and this PWS 6.2.2.3 Recertification Plans - CDRL Exhibit W, Data Item No. A022. Should re-accreditation be required: the contractor shall perform the certification testing as mutually agreed by the Government and Contractor, to include vulnerability assessment and risk analysis in accordance with AR 25-2, and update documentation as mutually agreed by Government and Contractor. The Agent of the Certification Authority (ACA) will review drafts of documentation, supply its comments to the Contractor and the Contractor shall then update the documentation and redeliver them to the ACA and submit IAW CDRL Exhibit W, Data Item No. A022 and this PWS. Issues not resolved during this process will be referred to the Issue Management Board. 7 TRANSITION SERVICES: The contractor shall provide services to assist the government in transitioning from contractor-provided services as set forth in sections 2 through6 of this PWS to organic capability with support contractor augmentation. 7.1 Phases and Work Streams: The transition services will be provided in two phases as follows: Phases: Phase I - Planning Phase II - Implementation The transition will be governed by an overarching Transition Work Plan to be completed and mutually agreed to by the Government and CSC during the Planning Phase. The Transition Work Plan (TWP) will mandate the development of three Component Implementation Plans - one for each of the following components that coincide with how CSC services are provided: Component 1 - Sustainment and Development Component 2 - Hosting Component 3 - Residual Legacy Sustainment The contractor and the Government will work together during the Planning Phase to develop the Component Implementation Plans. Each Component Implementation Plan will describe the necessary events, activities and products required to achieve a smooth transition of LMP services from CSC to an organic service provider. Each Component Implementation Plan shall further include all related and pertinent data and or information required to transfer both explicit and tacit knowledge of the component to organic service provider(s). As applicable, for each component and phase of the transition, the contractor shall provide the Government with the LMP solution and service and such information, documentation and support as is reasonably necessary to transition the LMP Services to organic service providers while maintaining acceptable levels of performance including compliance with Key Performance Parameters (Attachment XX) and while ensuring the continuous provisions of services (as described in Section XX). Such information, documentation and support may include, but may not be limited to, the items listed in Attachment YY. PERFORMANCE WORK STATEMENT CONTINUED IN MODIFICATION 2 OF 2.