TWMS_PWS_Version_2.docx

Version 2 12/5/2016

PMW-230 Global Combat Support System-Marine Corps (GCSS-MC)

Performance Work Statement (PWS)

Tactical-Warehouse Management System (T-WMS)

Table of Contents

1. General Information. This Performance Work Statement (PWS) establishes the baseline for the development, integration, and fielding of an Automated Information System (AIS) that provides warehouse management capabilities to the United States Marine Corps at the retail level of supply, and possesses the ability to expand to provide an enterprise warehouse capability. The initial capability is intended to replace the Web Storage Retrieval Automated Tracking Integrated System (Web STRATIS), while future expansions of the capability should facilitate the consolidation, migration, integration, interoperability and/or retirement of other logistics Information Technology (IT) systems.

1.1 Background. The United States Marine Corps (USMC) requires a single, scalable, integrated warehouse management solution that centralizes the view of USMC enterprise-level inventory and is accessible in both deployed and garrison environments. The Tactical-Warehouse Management System (T-WMS) seeks to address this need in an incremental approach by modernizing retail-level warehouse processes and integrating with the currently fielded Global Combat Support System-Marine Corps/Logistics Chain Management Increment 1 (GCSS-MC/LCM Incr 1) Enterprise Resource Planning (ERP) system, while also considering future opportunities to make other Marine Corps warehouses more efficient and accurate. The functional sponsor, Deputy Commandant for Installations and Logistics, has planned for the retail portion of Marine Corps warehouse management, to include the Supply Management Units (SMUs), Reparable Issue Points (RIPs), Initial Issue Provisioning (IIP), Marine Forces Reserves (MARFORRES) and Using Units (UUs).

Ultimately, the vision for USMC’s Logistics Operational Architecture is to provide a platform for welldefined, standardized interfaces that ease integration with existing systems, new systems, and emerging technologies. The goal is to provide commanders and logistics personnel an enabling software tool to help improve asset visibility, calculate supply posture and readiness, track the location of inbound supplies, and streamline the warfighter’s procedures for requesting support. T-WMS will advance this vision by modernizing, automating, and standardizing supply and inventory management functions for inbound processes, warehouse management, and outbound processes, while preparing the USMC for future expansion to full enterprise warehouse management. It is expected that the solution used for TWMS has the capability to be used across the enterprise to achieve automated, standardized, and modernized processes that enable warehousing for expanded classes of supply, while integrating with GCSS-MC/LCM Incr 1.

The USMC does not have an integrated, enabling AIS to support retail-level warehouse management operations at the Marine Expeditionary Force (MEF) and below. Marines input data into numerous systems, applications, spreadsheets, and manual processes to manage warehoused inventory. At the SMUs, warehouse management is performed using Web STRATIS interfacing with GCSS-MC/LCM Incr 1 (Attachment 3 – STRATIS Interface Design Document). At the other retail-level warehouses (i.e., RIPs, IIPs, MARFORRES, and UUs), spreadsheets and “home grown” databases are used to augment warehouse management activities and inventory management functions currently offered through GCSS-MC/LCM Incr 1.

Retail-level (intermediate and consumer level supply) warehouses require a consistent, repeatable, and dependable warehouse management solution to reduce costs, complexity, and inventory errors. The T-WMS solution will inject automation to reduce manual errors and aid in the execution of business processes, e.g., inventory imbalance resolution. A single warehouse management system will, in turn, augment the USMC’s supply chain management by providing commanders confidence in their logistics pipeline and reduce time lost by the warfighter resolving and correcting warehousing issues. A single, integrated, software solution will provide retail warehouses consistency in operation and training. Additionally, a single solution will reduce errors that result from various systems operating with unsynchronized inventory data. This solution will integrate with GCSS-MC/LCM Incr 1 and potentially replace the existing wholesale warehouse systems in the future.

The goal for T-WMS is a streamlined architecture which leverages the GCSS-MC/LCM Incr 1 database. This architecture will allow for reduced onsite maintenance and hardware, a centralized helpdesk, common tools, standardized operating procedures, and more efficient warehouse processing.

Additionally, the current retail-level warehouse management capabilities do not provide Item Unique Identification (IUID) capability. The USMC must transition to the use of a Unique Item Identifier (UII) to comply with various Department of Defense (DoD) mandates (DoDI 8320.04, DoDI 5000.64, DoDD 8320.03), Marine Corps Orders (MCO 4410.28, MCO 4000.51C, MCO 4000.150) and Military Standards (MIL-STD-129 and 130). The use of IUID will provide improved data integrity, data quality, and enable total asset visibility throughout the lifecycle of assets. The T-WMS capability will facilitate the transition to IUID by ensuring the system can read, store, and forward UII-related data.

1.2 Objectives. The objectives for this effort are to efficiently provide Warfighter customers with serviceable items of equipment while improving overall management and operations; provide item management, accountability, and Total Asset Visibility; improve management and warehousing processes; and provide fielding, training and product support.

1.3 Scope. The purpose of this requirement is to develop, integrate, field and sustain an AIS that provides warehouse management capabilities to the United States Marine Corps at the retail level of supply. With an eye towards the reduction of stove-piped systems and associated sustainment costs, the solution will serve as a capability integration platform that supports expansion to enterprise warehouse Management and other key Logistics business processes as part of the modernization of logistics Marine Corps IT systems.

The contractor shall provide the following services to meet the objectives of the contract scope:

· Program Management

· Systems Engineering Management & Planning

· Solution Design & Development

· Test & Evaluation

· Product Support Management

· Solution Deployment

· Business Process Change Management

· Operations & Support

· Studies, Analyses, Assessments and Improvements

1.4 Place of Performance. The work to be performed under this contract shall be performed at the contractor facility, with occasional travel to the government program management office in Stafford, VA. Additionally, occasional trips may be required at the following Continental United States (CONUS) and Outside the Continental United States (OCONUS) locations to support training and fielding:

· Camp Lejeune, NC

· Camp Pendleton, CA

· Marine Corps Base, Kaneohe Bay, HI

· Blount Island Command, Jacksonville, FL

· Okinawa, Japan

· Various Marine Forces Reserve Commands, U. S

1.5 Quality Assurance. The government will evaluate the contractor’s performance under this contract in accordance with the T-WMS Quality Assurance Surveillance Plan. This plan’s primary focus is on what the Government must do to ensure the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6 Contracting Officer Representative (COR). The Contracting Officer will designate a COR for this contract. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract.

1.7 Identification of Contractor Employees. Contractor employees shall identify themselves as contractor personnel by introducing themselves, or the Government introducing them, as contractor personnel and by displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

1.8 Data Rights. The Government has unlimited rights to all documents/material produced under this contract, including those associated with the design and delivery of all training materials for the user and/or end user. All documents and materials, to include the compiled and non-compiled source codes of any software produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights. See relevant FAR clauses in Sections H and I of the Solicitation (CDRL B018 Computer Software Baseline, CDRL B019 Configuration Status Accounting Information, and CDRL B020 Software Version Description (SVD)).

1.9 Organizational Conflict of Interest (OCI). The Contractor shall notify the Contracting Officer immediately whenever it becomes aware of an actual or potential OCI and shall promptly submit a plan to the Contracting Officer to mitigate or avoid any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2. Specific Tasks. The Contractor shall provide products and services to the Government based on a suite of COTS products, commercial standards practices, innovation, and risk management to meet the requirements in Attachment 5 – T-WMS Requirements Specification.

2.1 Security Requirements.

This contract will require the contractor to have a Secret Facility Clearance and will require certain contractors to obtain and maintain classified access eligibility. The contractor shall have a valid Secret Facility Clearance and a Secret Document Safeguarding Level prior to classified performance at the contractor’s facility. The prime contractor and all sub-contractors (through the prime contractor) shall adhere to all aspects of DoD Directive 5220.22-M. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD Form 254) as an attachment.

2.1.1 The contractor shall notify the Government (written notice) within twenty-four hours of any contractor personnel added or removed from the contract that have been granted classified access, issued a Common Access Card (CAC) and/or MARCORSYSCOM Building access.

2.1.2 All Contractors providing information assurance (IA) functions to meet the requirements of this PWS, and requiring administrative access to USMC IT systems, shall have the proper and current cyber certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program.

2.1.3 To ensure reciprocity, contract trustworthiness determinations will be adjudicated by the Department of the Navy, Central Adjudication Facility. Favorable trustworthy determinations will support public trust positions only. This scope of investigation does not meet the standards for security clearance eligibility.

2.1.4 Common Access Cards (CACs). The COR will identify and approve those contractor employees performing on this contract that require CACs in order to perform their job function. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, contractor employees requiring a CAC, must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI). Prior to authorizing a CAC, the employee’s JPAS record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened). If a contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked by the Contractor and provided to the COR.

Facility Security Officers (FSOs) are responsible for notifying the CDET Security Director if any contractor performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the MCSC Security Director of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any contractor issued a CAC, regardless of whether a JPAS Incident Report is submitted.

Each CAC is issued with a “ctr.usmc.mil” e-mail account that the individual contractor is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to any e-mail account that is not .mil. If the ctr.usmc.mil e-mail account is not kept active, the G-6 will deactivate the account and CAC will lose its functionality.

If a contractor loses their eligibility for a CAC due to an adverse adjudicative decision, they have also lost their eligibility to perform on MCSC contracts and must be replaced promptly. CACs are not issued for convenience.

2.1.5 The individual Contractor is responsible for keeping their CAC issued with a “ctr.usmc.mil” e-mail account active by logging in on a regular basis (at least twice a month), sending e-mail and clearing unneeded e-mails. Contractors are prohibited from “auto-forwarding” their .mil e-mail account to their .com e-mail account. If the ctr.usmc.mil e-mail account is not kept active, the Marine Corps Base Quantico, G-6 Telecommunications Office, will deactivate the account and CAC will lose its functionality.

2.2 Physical Security. The contractor shall be responsible for safeguarding all government property (equipment and information) provided for Contractor use.

2.2.1 The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

2.2.2 In the event keys are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, a re-keying cost of $700 may be deducted from a payment due the Contractor and a CLIN price will be unilaterally decreased by this amount for each occurrence.

2.2.3 The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor employees whom are authorized to work under this contract. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

2.3 Key Personnel. The Contractor shall designate and assign key personnel to the project throughout the life of the contract. At a minimum, the following key personnel shall be designated:

2.3.1 Substitution of Key Personnel. The qualifications for the key personnel initially proposed and accepted at contract award shall serve as the minimum key personnel qualifications throughout the life of the contract. No substitutions shall be made except in accordance with this clause.

2.3.2 All substitution requests shall be submitted to the Contracting Officer and COR, in writing, at least 15 calendar days in advance of the proposed substitutions. Upon acceptance by the PCO, the substitute shall assume the duties and responsibilities of the replaced individual and the parties will execute a modification to this "Key Personnel" requirement.

2.3.3 Replacement of Key Personnel. Upon resignation notice of any key personnel, the Contractor shall hire a fully qualified replacement within 30 calendar days. It is the Contractor’s responsibility to cover all costs to hire, train, and relocate personnel. If any Key Personnel are reassigned, terminated or otherwise become unavailable to perform under the contract and are not replaced with an approved individual within 30 days, the PCO may take appropriate action, to include withholding payment, (downward) equitable adjustment or contract termination.

2.3.4 All requests for substitutions or replacements shall provide a detailed explanation of the circumstances necessitating the proposed substitution or replacements and any other information requested by the Contracting Officer. All proposed substitutions or replacements shall have qualifications that are equal to or higher than the qualifications of the person to be replaced. The Contracting Officer or his authorized representative will evaluate such requests and promptly notify the Contractor of his/her approval or disapproval thereof.

2.4 Contractor Travel. Contractor personnel shall be required to travel within the Continental United States (CONUS) and outside the Continental United States (OCONUS) during the performance of this contract to attend meetings, workshops, demonstrations, site visits, and to facilitate training. The specific number of required trips is unknown and is based on necessity; however, at least one trip is required for each of the locations listed in Section 1.5, Place of Performance. The Contractor shall comply with the Status of Forces Agreement (SOFA) of the host country in which they have personnel performing the requirements of this contract.

When travel requirements are identified, the COR will provide planning information to the Contractor (e.g. plans, agenda, itinerary, dates). Within 10 business days, the Contractor shall submit a travel request with a travel plan (including costs). All travel requests must be submitted to the COR for approval. All authorized travel must be approved by the COR. Upon approval, the travel costs become a "not to exceed" amount. Any incurred costs greater-than the approved "not to exceed" amount for that trip is an unallowable expense (that cannot be offset by future travel underruns). Costs for travel shall be billed in accordance with FAR 31.205-46 Travel Costs.

The Contractor will be authorized travel expenses consistent with the applicable provisions of the Joint Travel Regulation and the limitations specified in this contract.. All OCONUS travel shall be entered into the Synchronized Pre-deployment and Operational Tracker (SPOT) database and approved by the Government prior to travel. All personnel who may be required to travel shall have and maintain a current passport. The Contractor shall notify the Contracting Officer and COR when authorized travel expenses reach 75% of the CLIN amount. Travel costs in excess of the funded value shall not be reimbursed.

2.5 Other Direct Costs (ODCs). The Contractor may be reimbursed for ODCs incurred in support of this contract. ODCs include the procurement of necessary items associated with the fielding and training of the T-WMS solution, and require the written, advanced direction and approval of the Contracting Officer and COR.

2.6 Project Management. The Contractor shall provide Project Management support to ensure planned activities are executed within cost, schedule and performance parameters.

2.6.1 Post Award Conference (PAC). The Contractor shall attend a Post Award Conference (PAC) convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The purpose of the PAC is to achieve a clear and mutual understanding of all contract requirements and identify and resolve potential problems. As part of the PAC, the Contractor shall introduce key personnel and present program implementation processes to be utilized under the contract. The Contractor shall provide an overview of their Risk Management process and discuss key risks to include dependencies and mitigation for each identified risk. The Contractor shall also present the proposed Integrated Master Schedule (IMS) and brief the Critical Path and Near Critical Path (i.e., tasks with 10 days or less total slack), and provide an overview of the schedule change management and schedule baseline management processes, and present the results of the Schedule Risk Assessment. The Government will provide the PAC agenda to the Contractor not later than two weeks before the conference.

2.6.2 Program Management Plan (PMP). Within 30 days after completion of the Post Award Conference, the Contractor shall establish a comprehensive PMP describing the processes and procedures associated with how the project will be managed and executed, and ensures accurate and timely cost, schedule and performance information throughout the lifecycle of the project.

The PMP shall include an overview of the Contractor’s organization, personnel assignments and duties/responsibilities, management procedures/policies to be used, management reporting requirements, management methodology (process, task, and other narratives as necessary), and high level schedule to accomplish contract tasks. The PMP shall provide the structure for managing and controlling the Contractor’s events, activities, and related tasks. [CDRL A001 Program Management Plan]

2.6.3 Contractor Work Breakdown Structure (CWBS). The Contractor shall define, implement, and maintain a comprehensive CWBS [CDRL A002 Contractor Work Breakdown Structure] and associated dictionary, compliant with MIL-STD-881C, which identifies all Contractor activities to the lowest level of detail necessary to deliver the T-WMS solution.

2.6.4 Schedule Management. Within 30 days of contract award, the Contractor shall develop and submit a detailed Integrated Master Plan (IMP) and IMS [CDRL A003 Integrated Program Management Report (IPMR)]. The IMP shall include the major events, accomplishments, and criteria required to deliver the T-WMS solution including milestones, program reviews, CDRL deliverables, software builds, test events, training, cutover to production, fielding to designated locations, sustainment activities, legacy system retirement, and other elements as needed to address the entire scope of work. The IMS shall be an integrated, networked schedule containing all of the discrete work packages and planning packages, or lower level tasks, necessary to support the events, accomplishments, and criteria as detailed in the IMP. The IMS shall be developed in accordance with the applicable standards in the IPMR Data Item Description (DI-MGMT-81861A) tailored in CDRL A003.

After the Government’s review and approval of the first IMS submission, any changes to the IMS baseline shall be agreed upon by the Government and Contractor. Changes to the baseline schedule shall be made in accordance with the Government’s schedule change management process. The Contractor shall provide updates to the IMS at the frequency established in CDRL A003 and coordinate with the T-WMS Team to identify and establish linkages (i.e., task dependencies and/or work relationships) between Government and Contractor schedules, and to jointly seek to identify and resolve schedule and performance concerns, risks, and issues. The Contractor shall perform appropriate analyses of the IMS tasks, report potential or existing problem areas to the T-WMS Team, and recommend corrective actions to eliminate or reduce schedule impact. The Contractor will also identify and report the Critical Path and Near Critical Path. The Near Critical Path will include discrete tasks that have 10 days or less total slack.

2.6.5 Program Management Review (PMR). The Contractor shall support quarterly PMRs as required by the COR. The COR will provide 20 business days’ notice on scheduling the PMR. PMRs may be conducted in person or virtually via teleconference and web conference, at the Government’s discretion. At the review, the Contractor shall develop and present a brief [CDRL A004 Program Status Reports] that addresses, at a minimum, the following areas:

· Contractor IMS to identify status of scheduled tasks, dependency impacts, critical path, explanation of deviations from the baseline schedule, and changes to the critical path, and forecasted schedule impacts

· Contractor IMS will identify CDRL delivery of critical plans, e.g. Test Plan and Strategy, Systems Engineering Management Plan (SEMP), Software/System Integration Plan (SIP), etc. in support of the project execution. It is required that sufficient time be available for team review and comment of the CDRLs, plans and other key deliverables. In addition to deliverable due dates the IMS shall indicate timelines for comment and review for CDRLs.

· Contractor metrics and corrective action plans

· Project risks, issues and mitigations

· Technical progress and status on any problems reported during the preceding period

· Actual accomplishments, planned accomplishments, and status of action items

· Subcontract management

2.6.6 Risk Management. The Contractor shall conduct risk management processes to identify and mitigate project and technical risks and provide metrics to monitor project status. The Contractor shall participate with the Government to review and collaborate on risk assessments and mitigation approaches in accordance with the Department of Defense Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs, dated June 2015, and the GCSS-MC Risk, Issue, and Opportunity Management Plan.

2.6.7 Quality Assurance. The Contractor shall perform quality assurance as a process that monitors the overall plan, procedures, and controls that the Contractor will use to provide and maintain a satisfactory quality system for the duration of the contract.

2.6.8 Configuration Management (CM). The Contractor shall plan and conduct a comprehensive CM approach in accordance with GEIA-HB-649A, for configuration management processes, and is consistent with the GCSS-MC Configuration Management Plan and processes. The Contractor shall work with the GCSS-MC CM Team to ensure system integrity while changes are made to the system throughout the period of performance.

2.6.9 Phase-in/Phase-out. To ensure a smooth phase-in to the next contractor and to prevent possible decreases in productivity or service quality, the Contractor shall provide a phase-out plan [CDRL A005 Phase-Out Transition Plan] for the 30 calendar days prior to the contract end date (i.e., at the end of all option periods). During this period, while still maintaining full performance, the Contractor shall make available to key incoming contractor personnel, a representative of the incumbent Contractor who is versed in the operations of all functions to be performed. All non-proprietary data, documentation, templates, schedules, processes, procedures, work instructions, configuration management repositories, etc. used to execute the performance of the contract shall be transferred to the Government at the beginning of the phase-out period. Transfer of Government Furnished Property will be made at the end of the phase-out period.

2.7 Systems Engineering Management and Planning. The Contractor shall plan and manage all engineering tasks required to achieve a balanced set of activities, which includes any analysis, design, development, integration, data conversion/migration, cutover, test and support functions to satisfy T-WMS requirements throughout the project lifecycle. The Contractor shall provide a Software Development Plan to the Government that documents the Contractor’s plan for conducting any software development effort, including how the software will be integrated. [CDRL B001 Software Development Plan]

2.7.1 Engineering Management. The Contractor shall perform management activities to oversee and support the analysis, design, development, integration, test and cutover of the T-WMS solution, including facilitating workshops, conducting meetings and technical reviews, providing the appropriate documentation (e.g. meeting minutes, technical documentation, CDRLs), strategizing and coordinating cutover activities with GCSS-MC PMO and STRATIS, and ensuring compliance with DoD policies, the MCSC Systems Engineering Technical Review (SETR) Handbook “SIAT-HDBK-001, 06 August 2014”, Institute of Electrical Engineers standard 1220 “Standard for Application and Management of the System Engineering Process,” and proven industry best practices.

The Contractor shall provide details of its Systems Engineering Management approach within the System Engineering Management Plan (SEMP) [CDRL B002 System Engineering Management Plan]. The SEMP shall comply with and conform to expectations contained in the GCSS-MC Systems Engineering Plan (SEP) and be aligned to the content and structure of the T-WMS SEP (Attachment 7). The SEMP shall be updated with each update of the T-WMS SEP and as needed. The SEMP shall reflect technical progress achieved and changes in the technical approaches stemming from results of technical reviews and validation events, program reviews, milestones, or other program decision points. The SEMP shall describe the technical Systems Engineering approach and plan for the execution, management, and control of the GCSS-MC/T-WMS integration and implementation effort.

The current GCSS-MC operational environment is based on the Oracle EBS product which has significant customizations, e.g. Reports, Interfaces, Conversions, Extensions, Customizations, Personalizations and Workflows (RICECPW). Due to the importance of a smooth and efficient development, testing and implementation effort, the Contractor shall support an early, initial review of how the Contractor intends to integrate and implement its solution. This review will address unique considerations associated with the proposed solution integration, testing and implementation with the existing GCSS-MC/LCM Incr 1 operational environment such as how the Contractor will:

· Identify and evaluate any changes to the operational GCSS-MC/LCM Incr 1

· Utilize established environments as necessary to support Development, Test, Training, and Production

· Minimize undue impact to the operational GCSS-MC/LCM Incr 1

· Incorporate CM processes established by the Marine Corps in support of GCSS-MC/LCM Incr 1

2.7.2 Enterprise Architecture Management and Maintenance. The Contractor shall manage the development of solution-specific architecture viewpoints; maintain DoD Architecture Framework (DoDAF) architecture viewpoints to ensure the architecture remains consistent with current solution configurations and designs; and ensure compliance with the prevailing release of the DoD Business Enterprise Architecture. The Contractor shall support the GCSS-MC PMO assessment of changes required to the current GCSS-MC architectures as a result of T-WMS implementation.

2.7.3 Operating Environments. The Government will provide all hardware, operating system, and network services associated with operation of the GCSS-MC solution. The Contractor shall integrate T-WMS with the current GCSS-MC logical and physical architectures at the hosting facility. The Contractor shall design and develop the logical and physical architectures required to support T-WMS at the current Government hosting facility [CDRL B003 Operating Environment Requirements and Design].

The Contractor shall configure and field the application server software (e.g., Web, database), while the Government hosting facility will provide management and configuration of the operating system, tools and monitoring, system administration, and storage capacity. The Contractor shall support the Government and T-WMS Team with validation and testing of all aspects related to IA and security.

The Contractor shall coordinate with the GCSS-MC PMO to ensure the Contractor’s design can be supported with the network and hardware offered by the hosting facility. The Contractor shall develop engineering documentation for the T-WMS Team to support changes required at the hosting facility in support of integration, testing, acceptance, cutover rehearsals, and product cutover. This documentation shall discuss data and user account migration (to include data quality management) required to have a successful cutover. It shall also discuss any impact to the production in the current capability during cutover including time to execute and validate a complete cutover [CDRL B003 Operating Environment Requirements and Design].

2.7.4 Technical Reviews. The Contractor shall develop and provide documentation to satisfy entrance and exit criteria for all SETR events. The Contractor shall participate in, record minutes, and address/respond to assigned actions (Requests for Actions, Requests for Information, etc.) for all technical reviews (e.g., SRR, PDR, CDR) to assess and validate the system and software design. [CDRL B004 System Engineering Technical Review Packages] [CDRL B002 System Engineering Management Plan]

2.8 Solution Design and Development. The Contractor shall perform all analysis, design, development, test, and integration activities necessary for the successful delivery of the T-WMS solution.

2.8.1 Solution Design Support.

2.8.1.1 Business Process Analysis. The Contractor shall leverage the existing T-WMS To-Be Process Specifications to compare its solution to the T-WMS requirements; conduct Business Process Reengineering (BPR) to evaluate potential business process changes to align with the COTS product; and to identify system configuration and/or customization requirements. The Contractor shall map any new T-WMS user roles to the current GCSS-MC user roles. [CDRL B005 Fit/Gap Report] [CDRL B006 Business Process Design] [CDRL B007 Requirements Traceability Matrix]

2.8.1.2 System Technical Analysis. The Contractor shall:

· Conduct a technical risk baseline assessment to identify risks and provide mitigation strategies associated with end-to-end system performance, software limitation, security, legacy data access, and integration.

· Conduct a performance and scalability assessment to determine user capacity, data capacity, and computing resource requirements for hosting and provisioning at the Government hosting facility. This includes providing source code and documentation needed to configure the solution at the targeted hosting site. [CDRL B008 Computer Software Product]

· The Contractor shall collect system performance data, conduct performance analysis, and prepare performance metrics reports for the solution. [CDRL B009 System Performance Reports]

2.8.1.3 Interface Definition. The Contractor shall collaborate with GCSS-MC PMO to assess its solution and determine the required interface or integration points with the current GCSS-MC/LCM Incr 1 baseline; define data exchanges at the data format level; and document interface and/or integration specifications. The Contractor shall determine where data synchronization will be required between GCSS-MC/LCM Incr 1 and T-WMS, and how data currency between GCSS-MC/LCM Incr 1 and T-WMS will be maximized. The Contractor shall develop and configure any interfaces to allow the T-WMS solution to send and receive data electronically over the Government network and to maintain data integrity. [CDRL B010 Interface Control Document] [CDRL B011 Interface Requirements Specification]

2.8.1.4 Architecture Development. The Contractor shall develop and update business, system and technical architecture artifacts (physical and logical drawings) and associated descriptions to support solution and test design. [CDRL B012 Architecture Viewpoints and Plan] [CDRL B006 Business Process Design]

2.8.1.5 Requirements Analysis. The Contractor shall analyze the T-WMS functional and non-functional requirements and decompose/derive requirements in a Dynamic Object Oriented Requirements Management System (DOORS) compatible format or another requirements tool as determined by the Government. The Contractor shall allocate decomposed requirements to the software component level. The Contractor shall determine optimal hosting infrastructure requirements and any supporting system operations (i.e., those supporting systems/environments required for the T-WMS solution to operate effectively) at the Government hosting site. The Contactor shall also ensure bi-directional traceability to functional and allocated requirements. [CDRL B007 Requirements Traceability Matrix] [CDRL B011 Interface Requirements Specification] [CDRL B013 Software Requirements Specification (SRS)]

2.8.1.6 System/Software Design. The Contractor shall identify and conduct build-specific design activities; develop specific functional, non-functional, and integration artifacts required to enable efficient and effective software development activities; and identify system constraints, limitations and implementation dependencies. [CDRL B014 Software Design Description (SDD)] [CDRL B015 Interface Design Description (IDD)] [CDRL B016 Database Design Description]

2.8.2 Solution Development Support.

2.8.2.1 Capability Development and Integration. The Contractor shall develop and integrate the software services, modules, and products identified during the analysis and design phases to fill capability gaps and deliver a complete T-WMS solution. Along with this effort, the Contractor shall assess the current GCSS-MC/LCM Incr 1 to determine if changes need to be made to incorporate the T-WMS solution capabilities. The Contractor shall submit an Engineering Change Proposal (ECP) to the GCSS-MC PMO documenting changes required to the GCSS-MC/LCM Incr 1 baseline. [CDRL B017 GCSS-MC/LCM Incr 1 Engineering Change Proposal (ECP)]

2.8.2.2 Software/System Integration. The Contractor shall integrate all software solution components for use on the Marine Corps Enterprise Network (MCEN) and ensure integration with GCSS-MC/LCM Incr 1 is complete. The Contractor shall provide a Software Development Plan, which includes a System/Software Integration Plan, to the Government and maintain updates as needed. [CDRL B001 Software Development Plan]

2.8.2.3 Capability Configuration. The Contractor shall configure all system parameters to implement the defined business processes and capability design to include infrastructure level parameters to meet performance requirements.

2.8.2.4 Development Test. The Contractor shall perform development testing at the component and integration levels to ensure all requirements have been met and the system is ready for the Government Acceptance Test (GAT). The Contractor shall provide written test results [CDRL C003 Software Test Report].

2.8.2.5 Solution Delivery. The Contractor shall install, configure and deliver the complete turn-key T-WMS solution at the designated Government facility and certify that the solution is ready for Government test. (CDRL B018 Computer Software Baseline, CDRL B019 Configuration Status Accounting Information, andCDRL B020 Software Version Description (SVD)).

2.8.2.6 Configuration Audits. The Contractor shall prepare a list of all hardware, software and Firmware in support of Functional and Physical Configuration Audits (FCA/PCA). [CDRL B021 Configuration Audit Summary Report (FCA and PCA]

2.8.3 Cybersecurity and Program Protection Support. Marine Corps Order (MCO) 5239.2A establishes an information systems lifecycle management approach to protect critical Marine Corps information and intelligence. The contractor shall execute to the requirements within this order and DoDI 8510.01 Risk Management Framework (RMF) for DoD IT as appropriate. The contractor shall support, all certification and accreditation (C&A) activities throughout the period of performance in accordance with the latest releases or revisions of the cybersecurity policies. [CDRL B022 Risk Management Framework (RMF) Package]

2.8.3.1 Assessment and Authentication (A&A)/Cybersecurity Compliance. The Contractor shall perform the requirements of MCO 5239.2A and DoDI 8510.01 by establishing and implementing proactive protection, detection, reaction, and restoration capabilities to include the detection and reporting of unauthorized activities. The level of protection will be for a Mission Assurance Category II system. At a minimum, the contractor shall:

· Submit documentation to maintain the system’s Authority-to-Operate or Marine Corps Certified Application review and update documentation required for each system as defined by the MCSC Defense Information Assurance Risk Management Framework processes, and fulfill all annual cybersecurity requirements for the solution.

· Assess and implement cybersecurity best practices (code reviews, system scans, vulnerability alerts, vendor notifications, Security Technical Implementation Guides (STIGs)).

· Provide guidance to the Information Systems Security Manager (ISSM) in implementing cybersecurity best practices to increase the security of the system and eliminate vulnerability threats to include code reviews, system scans, vulnerability alerts, vendor notifications, and STIGs.

· Verify and validate all security updates and patches are tested and applied to software and operating systems.

· Verify and validate all vulnerabilities identified by the hosting facility’s vulnerability scans are incorporated and mitigated.

· Conduct software quality code reviews with Government provided automated tool(s). The Government will provide access to, and training material for the tool(s).

· Participate in providing timely completion of Annual Security Reviews, Annual Security Control testing, Annual Contingency Plan testing, and quarterly update and submission of quarterly Plan of Action and Milestones (POA&M) updates in compliance with the Federal Information Security Management Act (FISMA).

· Use the Government’s IA tool, MCCAST, to submit, maintain, and review C&A documentation and workflow. The Government will provide access to, and training material for the tool.

· Implement a system for the assessment, remediation, tracking, and reporting of system vulnerabilities per Information Assurance Vulnerability Management and Operational Directives.

· Confirm compliance of annual IA awareness training status.

· Provide a monthly identification of vulnerabilities and remediation in accordance with Communications Tasking Order 08-005 Scanning and Remediation and DoDI 8510.01.

· Support Independent Verification and Validation events. This includes the review of systems security documentation, performance of pre-assessment scans, review of vulnerability scan results, evaluation of test results, preparation and review of POA&Ms, and remediation of findings.

· Support Command Cyber Readiness Inspection events. This includes the review of systems security documentation, performance of pre-assessment scans, review of vulnerability scan results, evaluation of test results, preparation and review of POA&Ms, and remediation of findings.

2.8.3.2 Program Protection. The Contractor shall develop and update the Critical Functional Analysis (CFA), vulnerabilities assessments, risk assessments, identification and counter measurement implementations, demonstrations of visibility into supply chain and Software Assurance for critical components, and update of CFA results and Program Protection risks and mitigations at each Systems Engineering Technical Review. [CDRL B023 Critical Functional Analysis]

2.8.3.3 Software Assurance. The Contractor shall provide a plan to achieve and demonstrate confidence that the software is reliable, secure, functions as intended, and is free from security vulnerabilities and malicious code, either intentionally or unintentionally designed or inserted as part of the software, throughout the lifecycle. At a minimum, the plan shall include countermeasures to prevent, detect, respond, and report to the Government vulnerabilities in software, continuous monitoring, and adherence to secure coding standards [B001 Software Development Plan].

The Contractor shall develop, document, and update Software Assurance Countermeasures, Table 5.3.3-1 of the Deputy Assistant Secretary of Defense for Systems Engineering, Program Protection Plan Outline & Guidance, v1.0, which summarizes the planned and current state of a program’s software assurance activities in accordance with the table description provided in the Defense Acquisition Guidebook section 13.7.3 [B001 Software Development Plan].

The Contractor shall verify all software code developed for T-WMS against the Common Weakness Enumerations, Common Vulnerabilities and Exposures, and Common Attack Platform Enumeration and Classification.

The Contractor shall remediate Government identified vulnerabilities or weaknesses in the solution and software design/coding, to include reporting and responding to IA violations IAW Cyber Command mandated timelines – Category (CAT) I vulnerabilities shall be mitigated or remediated immediately, not to extend beyond 25 calendar days; CAT II vulnerabilities shall be mitigated or remediated within 60 calendar days; CAT III vulnerabilities shall be remediated within 180 calendar days.

2.9 Test and Evaluation. The Contractor shall provide requisite support during all Test and Evaluation (T&E) events. The outcomes of T&E activities provide feedback to the Government on the progress of the design process and product compliance with contractual requirements. The feedback aids the Government in evaluating the ability of the system to meet the complete set of validated and derived capability requirements and to support production and fielding. The level of test and evaluation rigor shall identify risk areas and demonstrate the reduction of risk to acceptable levels.

2.9.1 Requirements Testability. The Contractor shall conduct a requirements testability analysis to (1) determine if the requirements will be proved via Analysis, Inspection, Demonstration, or Test; (2) identify the requirements with test limitations or constraints that reduce testability; and (3) provide recommendations to improve requirements testability. [CDRL C001 Requirements Testability Analysis Report]

2.9.2 Test and Evaluation Activities. The Contractor shall identify, prepare, coordinate, plan, conduct, execute, review, support and document T&E activities (e.g., performance,…