PWS_(PDS__PDSAT)_-_Watermark_-Draft.pdf

PERFORMANCE WORK STATEMENT

PREPOSITIONING PLANS & DATA SUPPORT

USMC, BLOUNT ISLAND COMMAND

JACKSONVILLE, FLORIDA

TABLE OF CONTENTS

1. GENERAL

2. APPLICABLE DOCUMENTS AND REFERENCES

3. CONTRACT DATA REQUIREMENTS LISTING & PWS REFERENCES

4. QUALITY

5. PREPOSITIONING OBJECTIVE (PO) TAILORING

6. PLANNING SUPPORT

7. DATA MANAGEMENT

8. LOGISTICS AUTOMATED INFORMATION SYSTEMS (LOGAIS)

9. ITEM UNIQUE IDENTIFICATION (IUID) AND RADIO FREQUENCY IDENTIFICATION (RFID)

10. PROGRAMMING SUPPORT AND SOFTWARE ENHANCEMENT

11. TRAINING

APPENDIX A DEFINITIONS

APPENDIX B INFORMATION TECHNOLOGY CONTROLS

APPENDIX C SECURITY REQUIREMENTS AND CONTROLS

APPENDIX D ACRONYMS

APPENDIX E PLANS & DATA MILESTONES

APPENDIX F PREPOSITIONING DECISION SUPPORT AND ANALYSIS TOOL (PDSAT) – PWS

1. GENERAL

1.1 BACKGROUND. The Marine Corps Prepositioning Programs (MCPP) requires the prepositioning of equipment and supplies aboard 16 (which include a fuel ship and a container ship) Navy owned or chartered ships strategically located around the world. These 16 ships are divided into three Maritime Prepositioned Squadrons

(MPSRON) of five or six ships each, designated MPSRON-1, MPSRON-2, and MPSRON-3, located, respectively;

in the Mediterranean Sea; Diego Garcia in the Indian Ocean; and Guam and Saipan in the Pacific Ocean.

Maritime Prepositioning Force (MPF) is a term utilized to describe the combat capability derived when combining a

Marine operating force with the assets loaded aboard the MPSRON. Each squadron carries a Marine Expeditionary

Brigade (MEB) sized Marine Air Ground Task Force (MAGTF) worth of equipment that includes tanks, amphibious assault vehicles (AAV), light armored vehicles (LAV), artillery, ammunition, rations, medical supplies, fuel, water, everything the MEB might need for up to 30 days of sustained combat.

A fourth prepositioned MEB set of equipment and supplies is maintained in six caves and two airfield sites in central

Norway as part of the Marine Corps Prepositioning Program-Norway (MCPP-N).

Continental United States (CONUS) based support for this entire program is conducted at Marine Corps Support

Facility Blount Island (MCSF-BI), Jacksonville, Florida. The breadth and depth of the equipment and supplies prepositioned (over 11,000 national stock numbered items totaling to slightly over 52 million pieces) provides significant capability and flexibility enabling the combatant commander to conduct numerous crisis response missions. The concept of combining the speed of strategic airlift with the storage capacity of prepositioned sealift has greatly reduced force closure times in response to contingency scenarios.

Blount Island Command (BIC) is responsible for preparing, maintaining and updating spreadload and embarkation plans in support of the MPF Maintenance Cycle (MMC). In accordance with Headquarters Marine Corps (HQMC) and MarFor/Marine Expeditionary Force (MEF) Commander’s guidance, the Maritime Prepositioning Ship (MPS)

Plans Management Branch provides various plans and data collection in support of the MMC.

The Norway Prepositioning Management Office (NPMO) at BIC is responsible for the accountability of the ground material and equipment located in the caves in Norway. MCPP-N serves multiple activities and missions capable of global support to all Regional Combatant Commanders (RCCs). Equipment and supplies are stored for selective withdrawal and movement and can be tailored to meet multiple tasks. Logistics services conducted in Norway are performed by Norwegian Ministry of Defense (MOD) personnel. The Plans & Data Management Contractor

(PDMC) shall provide Prepositioning Objective (PO) tailoring, plans, and data support of assets assigned to MCPP-

N.

1.2 SCOPE. This is a Cost Plus Fixed Fee (Completion Form) Contract. The PDMC shall provide the full range and depth of logistics services and software systems support, for the MCPP which includes the MPS Program and the MCPP-N. In addition to prepositioning support, the PDMC shall provide operational logistics support to engaged Marine Corps and Department of Defense (DoD) operating forces. This support shall enable the operating forces to rapidly and successfully conduct and quickly recover from assigned missions across the full spectrum of expeditionary warfare and anti-terrorist operations. The peacetime effort focuses on the $6.4 billion dollars of equipment and supplies prepositioned within these two programs. The work for this completion form Cost Plus

Fixed Fee contract is described by stating specific end products (see paragaph 3 herein).

1.3 REQUIREMENTS. The PDMC shall provide services and products in support of the six major areas; PO Tailoring, Planning Support, Technical Data (Tech Data), Logistics Automated Information Systems (LOGAIS) Support, Programming Support and Software Enhancement. The PDMC shall provide other services as required by this Performance Work Statement (PWS). The successful offeror will provide detailed transition plan that describes how the will execute a transfer from the existing to the new contract without interruption or degradation of services.

Due to time restraints the transition plan shall not exceed 15 days.

2. APPLICABLE DOCUMENTS AND REFERENCES. The PDMC shall adhere to all relevant orders, directives, policies and Standard Operating Procedures (SOPs) pertaining to the load planning of prepositioned equipment and supplies, Information Technology (IT), use of IT equipment, and use of IT software and systems security. However, this section is not all encompassing, nor singularly authoritative on the subjects contained herein,

3. CONTRACT DATA REQUIREMENTS (CDRL) LIST & PWS REFERENCES

Data Item

Number Data Item Title PWS Reference

B001 Contract Cost and Status Report Contract Section F

B002 IUID & RFID Status Report 10.3.2

B003 Training Report 12.3.2.3

B004 PDSAT Status Report PDSAT PWS 1.3.10

D001 Ship Spreadload Plan 6.3.3.2

D002 Squadron Level Plan 6.3.3.3

D003 Squadron MSE Plan 6.3.3.4

D004 Sustainment Plan 6.3.3.5

D005 Individual Ship Plan 6.3.3.6

D006 Ship MSE Plan 6.3.3.6.1

D007 Armory Plan 6.3.3.6.2

D008 Mobile Load Plan 6.3.3.6.3

D009 Association Plan 6.3.3.6.4

D010 Square Load Plan 6.3.4.1

D011 Container Plan 6.3.4.2

D012 Embarkation Diagrams 6.3.4.3

D013 Special Handling Reports 6.3.5

D014 Miscellaneous MPE/S Plans 6.4

4. QUALITY

4.1 INTRODUCTION. Quality Assurance (QA) is defined as the functions and associated actions performed by the Government to ensure that contract requirements are performed in accordance with specified standards, and that an appropriate level of contractor quality control is in place and operational. ISO 9001:2008 is the basic structure utilized for Blount Island Command’s contract administration and QA programs. Quality Control (QC) is the responsibility of the PDMC and includes the activities that sustain the quality of a product or service in order to satisfy given requirements. QC is a major component of total quality management and is applicable to all logistics functions performed under this contract. The PDMC shall comply with the principles of ISO 9001:2008 to ensure the delivery of quality services and products.

4.2 OBJECTIVE. The BIC vision is to remain the global premier supplier of Prepositioning and Other

Logistics Support Services. Commitment to quality control is the path for BIC to reach and maintain its goals of 1)

100% Readiness for equipment prepositioned aboard ships and in Norwegian cave sites, 2) 100% Attainment of the

PO, and 3) 100% Data Accuracy. Compliance with the QA Program should bring about the following benefits:

Achieve better understanding and consistency of all quality practices throughout the Command and contracted logistics support provider’s organization.

Improve documentation.

Improve quality awareness.

4.3 REQUIREMENTS. The PDMC shall provide a QC Plan that complies with the Government QA Program and ISO 9001:2008. The PDMC’s QC Plan shall be in compliance with ISO 9001:2008 during the first year of the contract. The PDMC shall become ISO 9001:2008 certified within the second year of the contract.

4.3.1 QC Plan. The PMDC Quality Manager shall deliver an approved QC Plan within 90 days of contract award. The QC Plan, with consideration of the references above, shall describe as a minimum the following:

Quality Management System

Management Responsibilities

Resource Management

Measurement, Analysis, and Process Improvement

4.3.2 CRITICALITY OF QUALITY. The MCPP provide the equipment and supplies that the Marine

Corps goes to war with. Quality failures are not acceptable.

Ensure continued use of a documented, codified system year after year.

Improve documentation.

Improve quality awareness.

Form a foundation and discipline for Continuous Process Improvement (CPI) activities through a series of process inspections and audits.

5. PREPOSITIONING OBJECTIVE (PO) TAILORING

5.1 SCOPE. Tailoring the MPF and MCPP-N PO involves myriad sequential and concurrent tasks which will ensure the most capable equipment and supplies are prepositioned. Tailoring is the process of refining the MEB force structure and the PO to fit aboard each MPSRON and within the storage facilities in Norway.

5.2 OBJECTIVE. Tailoring is an iterative process by which the PO refined in a coordinated effort by Marine Corps and Navy, facilitated and integrated by HQMC Installation &Logistics (I&L). The objective of tailoring is to review, revise, and approve a PO for the equipment and supplies to be assigned to the MPF and MCPP-N programs in order to ensure prepositioned equipment and supplies support the current requirements of the Marine Corps. This includes the Expeditionary Airfield (EAF), Naval Support Element (NSE), Naval Mobile Construction Battalion (NMCB), and Expeditionary Medical Facilities (EMF), Fleet Hospital (FH), Aviation Ground Support Equipment (AGSE), and ammunition capabilities loaded aboard each MPSRON.

Tailoring ensures interoperability across MPSRONs and MCPP-N and provides the operating forces the opportunity to influence MPF and MCPP-N planning and inventory changes. The MPF program and MCPP-N are dynamic programs with Force List (F/L) and the associated Equipment Density List (EDL) changes occurring commensurate with changes in the Navy and Marine Corps operating forces capabilities and structure. Marine Corps Bulletin (MCBul) 3501 defines the notional MPF MEB.

The end state of Tailoring is a HQMC approved PO that provides to Deputy Commandant (DC), Combat Development and Integration (CD&I) a loadable Approved Acquisition Objective (AAO) for future program procurement and Program Objective Memorandum (POM) requirements.

5.3 REQUIREMENTS. The PDMC shall provide all assigned logistics actions and data analysis necessary to ensure MCPP and PO Tailoring goals are achieved.

5.3.1 The PDMC shall provide services to BIC in all matters regarding the PO. The PDMC shall interface with the staffs and commands external to the MPF to collect, assimilate and maintain accurate and consistent prepositioning requirements information. The PDMC shall ensure the information obtained is provided to the BIC MCPP Offices and posted to Marine Corps Prepositioning Information Center (MCPIC). All information posted to MCPIC shall be reviewed and approved by the Government prior to posting. All pending Acquisition Logistics Documents (ALDs) shall be maintained and submitted with the report to include visibility of all submission/feedback given by the Command.

5.3.2 The PDMC shall collect all official correspondence that affects the prepositioning throughout the

MMC.

5.3.3 The PDMC shall collect and maintain databases for all types of information that affect the MCPP (documents and correspondence). Examples are as follows, (this list is not all inclusive):

- Prepositioning Objective

- ALDs (such as fielding plans)

- All Change Requests

- SL-3 changes

- Technical Manual (TM) changes

- Naval Messages, such as Commanders Guidance and Calling Messages

- Other documents relative to Prepositioning Programs provided by other government entities.

5.3.4 The PDMC shall provide their recommended PO changes to the MPS Plans Management Branch.

Additionally the PDMC shall collect and maintain recommended PO changes from BIC and external organizations. All maintained PO changes shall be delivered to the MPS Plans Management Branch prior to each Planning Conference (e.g., Initial Planning Conference (IPC), Main Planning Conference (MPC) and Final Planning Conference (FPC).

5.3.5 The PDMC shall maintain a database of all recommended PO Class II and Class VII listings changes (approved and disapproved) along with supporting documentation.

5.3.6 The PDMC shall prepare all change requests for all approved PO changes and submit them to the

MPS Plans Management Branch and NPMO for signature and submission to and HQMC for final approval and inclusion in the PO.

5.3.7 The PDMC shall develop products such as briefings, PowerPoint Presentations, and information papers relative to maintaining the PO and respective plans as required.

5.3.8 The PDMC shall attend various conferences and working groups such as MPF and MCPP-N Tailoring Conferences (e.g., Initial, Main and Final), Program Reviews, and Equipment Fielding & Integration Symposiums (EFIS) and provide advice and recommendations regarding issues that affect the PO. After attending any conferences or working groups, the PDMC shall provide a written synopsis of issues affecting the PO to the respective MPS Plans Management Branch.

5.3.9 The PDMC shall attend planning meetings, Plans Branch Meetings, Maintenance Production Meetings, teleconferences, and any other meeting as directed by the Contracting Officer Representative

(COR).

5.3.10 The PDMC shall conduct required space analysis and assessments in support of prepositioning planning as directed by the COR.

6. PLANNING SUPPORT

6.1 SCOPE. The PDMC shall prepare, maintain, and update all spreadload and embarkation plans in support of the MMC. The PDMC shall monitor and track all recommended and approved changes to the PO and spreadload plans. The PDMC shall be familiar with all timelines as established in the references listed in Section 2 of this PWS.

The PDMC shall provide various plans and reports in support of the MMC planning timelines and ensure adherence to HQMC and Marine Forces (MarFor)/MEF Commander’s Guidance. In addition, the PDMC shall maintain documentation supporting decisions made during the planning process as it effects the distribution of Maritime

Prepositioned Equipment and Supplies (MPE/S). The documentation shall be posted to MCPIC and shall be made available the in the form of a report to the MPS Plans Management Branch (PMB). The PDMC shall maintain a log of all necessary modifications to the planning modules.

6.2 OBJECTIVE. The PDMC shall provide to the MPS PMB various plans and reports in support of the MMC planning timeline and ensure adherence to HQMC and MarFor/MEF Commander’s Guidance. Plans and reports shall be provided in accordance with Table 1, Section 3 of this PWS. The PDMC shall adhere to timelines provided.

Table 1, Section 3 provides detailed reporting requirements for the reports referenced in this section (Section 6) of this PWS.

The PDMC shall provide Equipment Fielding Support to ensure all equipment issues that may affect the MMC and MCPP-N planning processes are identified and addressed as early as possible.

6.3 REQUIREMENTS

6.3.1 SHIP’S PLANS CHANGES. Ship’s Plans changes are documented, routed, and recorded using a Change Request Form. The PDMC shall prepare Ships Plans Change Requests and route as directed.

6.3.1.1 The PDMC shall prepare Plans Change Request forms and route through pre-designated routing/distribution lists.

6.3.1.2 The PDMC shall utilize the approved Plans Change Requests to update the Ships Plans and associated documents and records.

6.3.1.3 The PDMC shall maintain a record of all Plans Changes Requests processed (including approved and not approved requests.

6.3.2 NEW EQUIPMENT FIELDING AND OBSOLETE EQUIPMENT. To ensure all planning documents reflect the most accurate and up-to-date information regarding equipment fielding and equipment obsolescence, the following is required:

6.3.2.1 The PDMC shall obtain, review, analyze and retain records of new equipment fielding documents. The analysis shall include identifying any deficiencies in the fielding quantities for

MPS, comparing fielding timelines to MMC schedules and identifying any significant effects on available space aboard the ships through space analysis or impact statements.

6.3.2.2 The PDMC shall interface with MPS Plans Management Branch, NPMO, and Logistics

Division Commodity Managers on all newly fielded items to ensure all issues, concerns, and requirements are identified, documented, and addressed upfront and early. The PDMC shall maintain information on newly fielded equipment and provide as necessary.

6.3.2.3 The PDMC shall identify and maintain a listing of all “Obsolete Equipment”. The PDMC shall provide this listing as required.

6.3.2.4 The PDMC shall incorporate newly fielded items into the spreadload plans, as required, with the approval of the MPS PMB and NPMO.

6.3.2.5 The PDMC shall delete obsolete equipment from the spreadload plans with the approval of the MPS PMB and NPMO.

6.3.2.6 The PDMC shall monitor and track all recommended and approved changes to the spreadload plans as it pertains to newly fielded and obsolete equipment.

6.3.3 SPREADLOAD PLANS. The PDMC shall provide the following Spreadload Plans to the MPS

PMB.

6.3.3.1 PREPOSITIONING VALIDATION PLANS. The validation plan shall display the published PO allowances for Class II, IV, VII, VIII and their prepositioned quantity. This plan shall be accomplished using the Prepositioning Planning System (PPS).

6.3.3.2 SHIP SPREADLOAD PLANNING. The PDMC shall prepare the Squadron 4/5 Ship

Spreadload Plan (CDRL D001) 190 days prior to the first MPS of the designated squadrons’ MMC offload unless otherwise directed by the Government. The Government will provide the necessary direction and documentation (e.g. Capability Set (CAPSET)) letter, Marine Expeditionary Unit

(MEU) equipment listing, etc., during the final planning conference (approximately 240 days prior to the first MPS of the designated squadrons’ MMC offload.

6.3.3.3 SQUADRON LEVEL PLANS. The PDMC shall prepare the Squadron-Level Plans

(CDRL D002) based upon the established PO for all Marine Corps, NSE, NMCB, EAF, FH, and

AGSE 190 days prior to the first MPS of the designated squadrons’ MMC offload unless otherwise directed by the Government.

6.3.3.4 SQUADRON MSE PLANS. The PDMC shall prepare the Squadron Major Subordinate

Elements (MSE) Plans (CDRL D003) shall be delivered to the Government 190 days prior to the first MPS of the designated squadrons’ MMC offload unless otherwise directed by the

Government. . The squadron MSE plan shall display the distribution of required prepositioned quantities for Class II, IV, VII and VIII among the MSE’s to include, but not limited to, Command

Element (CE), Ground Combat Element (GCE), Aviation Combat Element (ACE), Logistics

Combat Element (LCE) and their respective MEU elements, NSE, AGSE, FH, EAF, and NMCB.

The plan has a column for differences between the PO and the proposed spreadload.

6.3.3.5 SUSTAINMENT PLANS. The Government will provide Squadron Level sustainment plans to the PDMC to be posted in MCPIC, 190 days prior to the arrival of the first MPS of a squadron. The sustainment plans will display the distribution of Class I, III, IV, IX, Battery, Consumables (Secondary Repairable), Care-in-Stores (CIS) and Offload Preparation Party (OPP) among the ships of a squadron. The PDMC shall post the Sustainment Plan (CDRL D004) in

MCPIC within 72 hours of receipt from the Government.

6.3.3.6 INDIVIDUAL SHIP PLANS. The Individual Ship Plan (CDRL D005) for the first ship of each squadron shall be submitted to the Government at least 190 days prior to the first ship

MMC offload unless otherwise directed by the Government. Subsequent ship plans shall be submitted in monthly increments following the first submission until all ships within the squadron have been received. The plans shall include, but not be limited to; the Ship MSE Spread, Square

Load, Armory, Container and Mobile Load and Commodity Mobile Load plans for all Marine

Corps, AGSE, NSE, NMCB, EAF, and FH. The individual ship plans will include:

6.3.3.6.1 SHIP MSE PLANS. The Ship MSE Plan (CDRL D006) shall spread each ship’s Class II, IV (Table of Authorized Material Control Number (TAMCN) Controlled

Items), VII and VIII assets down to the respective MSE’s. The sum of the individual ships

MSE assignments shall not exceed the squadron MSE plan. The intent of this report is to ensure adequate distribution of assets between the MSEs and ships to meet Prepositioning spreadload requirements.

6.3.3.6.2 ARMORY PLAN. The Armory Plan (CDRL D007) shall list the total for

TAMCN to be stowed in the armory and the TAMCNs distribution by MSE.

6.3.3.6.3 MOBILE LOAD PLANS. The Mobile Load Plan (CDRL D008) shall list the total for TAMCN to be mobile loaded and each TAMCNs distribution by MSE.

6.3.3.6.4 ASSOCIATION PLANS. The Association Plan (CDRL D009) shall assign each item to a specific platform maintaining MSE integrity, while complying with height and deck restrictions in accordance with the Ship Loading Characteristics Pamphlet

(SLCP). The association plan will also describe any other assets assigned to each specific platform (e.g. RFID tags, support equipment, etc.).

6.3.4 SQUARE LOAD AND CONTAINER PLANS

6.3.4.1 SQUARE LOAD PLANS. The Square Load Plan (CDRL D010) shall list the totals for the TAMCN to be square loaded and the TAMCNs distribution by MSE.

6.3.4.2 CONTAINER PLANS. The Container Plan (CDRL D011) shall list the total for

TAMCN to be stowed in containers and each TAMCNs distribution by MSE. The PDMC shall create a container estimate worksheet. The container plan shall be in accordance with the PO, commodity sections container estimates (to include identification of special stow items and hazardous material), MarFor/MEF Commanders Guidance and HQMC guidance, TSS, SLCP, TM4790-14 and the International Maritime Dangerous Goods (IMDG). Container diagrams will identify all MarFor/MEF Commanders Guidance, MSE, Item ID, description, height and IMO code. The PDMC shall continue to update the container plan and estimate worksheet until E-4 when plans are turned over to the Government for execution. The PDMC shall continue through execution to update the container estimate worksheet and work with the BIC hazardous material section in obtaining an approved Dangerous Cargo Manifest (DCM). The PDMC shall provide additional embarkation assistance and reports as requested by the Government.

6.3.4.3 EMBARKATION DIAGRAMS. The PDMC shall create and deliver Embarkation

Diagrams (CDRL D012) that include all planned square loaded and containers for each MPS.

Embarkation diagrams will be prepared in accordance with the PO ship spread, Commanders

Guidance, Trim Stress and Stability (TSS) booklet, SLCP, and the TM4790-14. Diagrams will be prepared utilizing the current automated embarkation program identifying MSE, Item ID, description, and height. Initial square load plans shall be provided to the Government 11 months prior to the first MPS of the designated squadrons’ MMC offload in preparation to the tailoring initial planning conference, then for subsequent planning conferences. The PDMC shall continue to update the square load plan until 30 days prior to backload when plans are turned over to the

Government for execution. The PDMC shall provide additional embarkation assistance and reports as requested by the Government.

6.3.5 SPECIAL HANDLING REPORTS. The PDMC shall develop, maintain, and deliver the Special

Handling Report (CDRL D013) as directed by the Government, which are designed to assist in identifying

CAPSETs, associations, SL-3 requirements and any special handling or loading instructions. The Special

Handling Reports include:

6.3.5.1 CAPSET Report. There are seven CAPSETs authorized for MPF use. The CAPSET Report identifies the assets that comprise each set and details the MPS on which they are loaded.

The report is also the primary input to the Special Handling Report that enables users to identify the TAMCNs, quantities, and MSE allocations of a capability.

6.3.5.2 CMS Container Report. This report identifies communications security (COMSEC) equipment that cannot be stowed with its associated PEI. The report reflects the quantity to be loaded, MSE designations, and PEI associations.

6.3.5.3 A8000 Series Report. This report reflects all COMSEC equipment and its relationship to PEIs, allowing end users to validate quantities and MSE distributions.

6.3.5.4 SINCGARS and Radios Report. This report details the types of Single Channel Ground and Airborne Radio System (SINCGARS) and other follow-on or subsequent radios loaded onto each vehicle and includes the MSE breakout, ensuring that specific force elements are matched to specific radio types.

6.3.5.5 Squadron Medium Tactical Vehicle Replacement (MTVR) Mix. This report identifies how MTVRs should be spread loaded across a squadron and includes breakouts by ship, MSE, and model number.

6.3.5.6 MTVR Spare Tire &Tow Bar Breakout. This report details the distribution of MTVR spares, following the 1:5 ratio across MSEs and ships.

6.3.5.7 Enhanced Position Location Reporting System (EPLRS) Spread. This report designates by ship and MSE how the E-PLRS will be installed.

6.3.5.8 High Mobility Multipurpose Wheeled Video (HMMWV) A2 Model Breakout. This report identifies the distribution of HMMWVs to each MSE by model number and configuration.

6.3.5.9 Ribbon Bridge. This report directs the loading of the ribbon bridge components aboard specific ships in a squadron and the bridge configuration specifics.

6.3.5.10 Stock Listing - 3 (SL-3) Deficiency Reports. This report shall all SL-3 deficiencies. The Government will provide the PDMC with the specific information to be included in this report.

The Government will provide the process details to the PDMC.

6.4 MISCELLEANOUS PLANS REPORT. The PDMC shall develop and deliver the Miscellaneous Plans Report (CDRL D014). It shall consist of special ad-hoc reports and plans as required. This report shall include but not limited to the following:

6.4.1 MMC COMPARISON MATRIX. The PDMC shall provide a MMC Comparison Matrix to the

MPS PMB 30 days prior to the IPC. The MMC Comparison Matrix shall contain a detailed comparison of the previous MPRSON by ship and squadron to the current MPRSON being planned.

6.4.2 ARMORING PLAN. The PDMC shall provide the Armoring Plan based on the Commanders

Guidance and the Armoring Strategy.

6.4.3 EQUIPMENT CONFIGURATION PLAN. The Equipment Configuration Plan shall provide details such as:

6.4.3.1 Cab-up with mount configurations and quantities by vehicle types

6.4.3.2 Cab-down configurations and quantities by vehicle types

6.5 PREPOSITONING OBJECTIVE ANALYSIS. The PDMC shall provide technical analyst support to

Logistics Division (LOGDIV), to assist in correlating and analyzing PO adjustments and requirements, based on equipment fielding phase-in and phase-out plans, and MPS tailoring results. The effort includes assistance in identifying MEB Table of Equipment (MEB T/E) quantities, squadron totals, ships spread; along with affected tools kits and associated TAMCNs.

7. DATABASE SUPPORT

7.1 SCOPE. The PDMC shall develop and maintain various databases. The PDMC shall utilize existing Marine Corps Functional Area Manager (FAM) approved software such as Microsoft Access, Microsoft SQL, Oracle, Sybase, etc. to develop the databases. The databases will be initially populated with information that currently resides in government owned databases and software systems such as MDSS II and MCPIC. The databases shall also contain government provided equipment logistics information. The PDMC shall also populate the database with various types of Government provided equipment logistics information such as standard letters, technical instruction and published naval messages. The Government provided information shall be submitted to the PDMC in an electronic format that can be readily manipulated by the PDMC.

7.2 OBJECTIVE. The databases shall be structured in a manner that allows the end-user to extract the data and import it into the government owned software programs such as Microsoft Word, Microsoft Excel and Adobe Acrobat.

7.3 REQUIRMENTS

7.3.1 EQUIPMENT LOGISTICS INFORMATION. The PDMC shall develop and maintain an

Equipment Logistics Information database using data extracted from the existing government sources and databases. The database shall be accessible via the local internet. The Equipment Logistics Information database shall be updated on a quarterly basis or as approved by the COR.

7.3.1.1 The database shall contain the following fields of information and shall be sort-able on any of the fields:

Ship Name

TAMCN

Model

Nomenclature/Item Name

Serial Number

Issue

Example:

SHIP TAMCN MODEL NOMENCLATURE SERIAL NUMBER ISSUE MISC

7.4 PRE-MMC PLANNING and MPS OFFLOAD PLANNING. The PDMC shall develop and maintain databases that contain Pre-MMC Planning and MPS Offload Planning Data. The databases shall allow the end-users to extract the data into an Excel, Word or PDF document. . The databases shall be updated on a quarterly basis or as approved by the COR. The databases shall consist of the following Government (LOGDIV) provided information:

7.4.1 PRE-MMC PLANNING DOCUMENTATION/DATA

7.4.1.1 The PDMC shall develop and maintain a Pre-MMC Planning database. The PDMC shall obtain official information and documentation from various government sources to develop and maintain a database of the following types of information:

Safety Of Use Message (SOUM)

Engineer Change Proposal (ECP)

Modification Instructions

Annual PM Consideration Signed Consolidated Asset Listing (CAL)

Equipment Stock Rotation Programs

Post MMC maintenance issues (identified in the ship’s operational advisory)

Special Testing and Operation Requirements

7.4.2 MPS OFFLOAD (EXERCISE & CONTINGENCY) PLANNING

7.4.2.1 The PDMC shall develop and maintain an MPF Offload Planning database that contains the following information:

Post MMC maintenance issues (identified in the ship’s operational advisory)

Association Components o B2127 Attachments o Arty SL-3 Component Locations o Weapons Components

Equipment Warranty Listing

Lifting/Locking Device Requirements

Reduced “Armored” Vehicle Listing

Known Restrictions (LO/LO)

Long-Term Storage Considerations

Known FIE (Batteries, Critical SL-3 & Hazmat Material)

Special Stowe Requirements (Cab Sling)

7.5 SL-3 USING UNIT RESPONSIBILITY ITEM (UURI) DATABASE. The PDMC shall utilize government provided information to establish and maintain a SL-3 “UURI database which identifies and tracks equipment that identifies and tracks approved SL-3 “UURI” quantities, associated with prepositioned (MPS &

MCPP-N) assets. The Government provided information will be submitted to the PDMC in an electronic format that can be manipulated by the PDMC. The PDMC shall utilize existing Marine Corps Functional Area Manager (FAM) approved software such as Microsoft Access, Microsoft SQL, Oracle, Sybase, etc. to develop the database. . The database shall be updated on a quarterly basis or as approved by the COR. For example:

7.5.1 The database shall contain the following fields of information and shall be sort-able on those fields:

TAMCN

model part name

National Stock Number (NSN)

Unit of Issue (U/I)

Quantity (QTY)

Remarks

Example:

Table # TBD

TAMCN MODEL PART NAME NSN U/I QTY Remarks

D0009 AMK-31 Brush: wire, battery 5120-00-926-5175 EA 1

D0009 AMK-31 Cable assy: inter-vehicle 5995-00-772-8813 EA 0

D0009 AMK-31 Cable kit:NATO slave 2590-00-148-7961 EA 1

7.6 COMMODITY CHECK LIST/REGENERATION CHECKLIST DATABASE. The PDMC shall provide analyst support in developing and maintaining an equipment database to identify unique equipment considerations, to support equipment regeneration process. The database shall be capable of producing a Commodity

Check List, sorted by TAMCN, model, serial number and subject.

The initial information required to develop the Commodity Regeneration Check List, will be provided by the

Government (LOGDIV) within 30 days after contract award. The database shall allow the end-user to extract the

Commodity Regeneration Check List into an Excel, PDF, or Word document. The database shall have the capability of tailoring the Commodity Regeneration Check List, based on the actual offload EDL. The database shall be updated on a quarterly basis or as approved by the COR.

For example:

D0015, MTVR (7-Ton) Wrecker

Fluid Levels (3/4 Tank)

Vehicle’s Long Exhaust/Intake Stacks

Crane Placed In Transport Mode

Either System Disconnected

Height Restrictions (126 Inches)

Mobile Load (Yes or No)

Temp Jacket (W/Keys)

Copy SF-91 (As Required)

Copy Of completed (Exercise) EROs

Copy Of Pending Warranty Claim

Courtesy Equipment Repair Order/Equipment Repair Order Shopping List (ERO/EROSL)

7.7 QA TOOL. The PDMC shall develop and maintain an automated “commodity” QA tool, using government owned scanner software technology and hardware. The QA tool shall be updated as required and approved by the COR.

7.7.1 The QA tool shall be cable of producing a standardized QA Check List in support of Engineers, Motor Transport, Ordnance, Communication/Electronic (COMM/Elect), and Nuclear, Biological Chemical

(NBC) functional areas.

7.7.2 The QA tool shall allow the end-user to extract the Commodity QA Check List into an Excel, PDF, or Word document.

7.7.3 The QA tool will incorporate equipment and configuration data from MDSS II; plans data from

MCPIC; physical QA results, and provide an interface with the Command’s local HQMS System to record and capture QA results.

7.7.4 The QA tool shall be capable of producing a Commodity Equipment Check List, sorted by

TAMCN, model, and ID #. The initial information required to populate the Commodity QA tool will be provided by the Government within 60 days after contact award.

7.7.5 The QA Tool shall contain/verify the following information:

Equipment Configuration: such as Cab Up, Cab Down

Associated TAMCNs, such as C7036, E1123 and E1126

Fuel Levels: ¼, ½, ¾ or full

LogMar Data: NSN and Item Name

Ship Sticker, i.e. Ship Name

MSE Label: GCE, ACE, LCE

SL-3 Complete: MK-175, Local Packing, Preservation, Packing & Packaging (PP&P)

Special Stowe: Cab Sling

Equipment Records: Key w/locks, SL-3 Extract

PP&P

Equipment Data: NSN, Model, ID#, Item Name

Load Test Certification: Marking, Load Test Record

Equipment Defects: Hydraulic System, Electrical System, Coolant Systems, Brake System, Air System, Body and Frame.

7.8 PREPOSITIONING OBJECTIVE. The PDMC shall provide to the Government within 45 days, prior to the start of each MMC cycle, with a complete PO listing of Class II, III, IV, VII, and IX shortages and excesses, based on the previous MMC load out data versus the approved planned PO listing. The listing shall be provided in an Microsoft Excel spreadsheet. Class II, III, IV, and IX shall be listed by NSN, Item name, and QTY; and, Class VII shall be listed by TAMCN Group, NSN, Item Name, and QTY. The PDMC shall post the file on a common drive that is accessible for viewing by logistics division personnel.

8. DATA MANAGEMENT

8.1 SCOPE. Data Management is the process used by BIC to store, organize, and manipulate information that is related to the MCPP. Handling this information requires utilizing the government owned systems such as MDSS II, MCPIC, and Integrated Computerized Deployment System (ICODES) to collect, store and update Plans & Data.

The effective management of the MCPP requires the efficient management, manipulation, conversion and storage of very large amounts of data that is generated by entities both within and outside of BIC. Users of this data, software systems and databases require support, assistance, and training.

Some MCPP entities, such as the MCPP-N utilize systems that have unique interface requirements. MCPP-N utilizes

Norway Equipment Inventory Management System (NEIMS) for in-country data management; however, this data is not compatible with MDSS II without data conversion.

During the course of conducting each Maintenance Cycle, there is a need to input, transfer, and download information between systems and individual entities. There is also a need to periodically reconcile the information to ensure data accuracy and quality control.

8.2 OBJECTIVE. The objective of Data Management is to ensure data accuracy and QA in all records and data associated with and related to the MCPP. Effective Data Management is essential to ensure the data utilized to develop all Prepositioning Plans is accurate and current.

8.3 REQUIREMENTS. After the backload of a ship or other operations and exercises, there is a reconciliation of the records to ensure the actual quantities loaded aboard the ships match planned quantities listed in the official databases and systems, such as ICODES, PO, MDSS II and Tech Data. Data and reports are generated and forwarded to various users involved in the MMC.

Data and Reports are all defined as formal reports, such as, plans, databases and documents managed by the PDMC and forwarded to the Government (e.g., MDSS II Data Milestones and MDSS II Final Unit Deployment Listing

(UDL)).

8.3.1 Data Milestones. During the MPS MMC, LOGAIS/MDSS II data is broken into milestones for delivery by the PDMC. The following milestones are illustrated below:

8.3.1.1 E-10. Essential Embarkation Data Elements for ICODES load plans and staging plan development. LOGAIS/MDSS II data fields necessary to develop ship load plans and subsequent vehicle and container staging plans. (i.e., Major end items – Square loaded and Containers).

8.3.1.2 E-4. LOGAIS/MDSS II data fields necessary to ensure Child Plan and associated merge prior to being loaded aboard MPS.

8.3.1.3 E-Day. DCM Data Elements. LOGAIS/MDSS II data fields necessary to ensure DCM can be completed before the physical loading of MPS.

8.3.1.4 E-+10. MDSS II data complete. All LOGAIS/MDSS II data and reports, to include the ship’s MDSS II UDL and SL-3 deficiency reports shall be submitted to the Government.

8.3.2 Data Entry. Individual items of equipment are resident in MDSS II with all required fields accurately populated into appropriate MDSS II parent/child plans. The PDMC shall adhere to the

Government QA process before posting any information to MCPIC.

8.3.2.1 When processing NPMO data, the PDMC shall interface with NPMO QA to verify information for accuracy.

8.3.3 Data Cleansing/Verification. The PDMC shall monitor the storage of all data related to current and past MMCs/Operations. Once verified by MCMC & LOGDIV, that data is no longer required, the PDMC shall delete selected plans and data.

8.3.3.1 The PDMC shall compare planning data from PPS with actual data from the MDSS II

Master UDL. This comparison shall show ships and squadrons plans to ensure data accuracy.

8.3.4 The PDMC shall update the Tech Data records to reflect changes to NSN and TAMCN that are due to various reasons such as:

Newly Fielded Equipment

Obsolete NSNs

Substitute Part Number

Local TAMCN assignments

Substitute NSNs

8.3.5 The PDMC shall reconcile the Government’s Tech Data with the MCMC data and the data in the

Federal Logistics Database (FEDLOG).

8.3.6 The PDMC shall create UDLs for all MCPP users/customers including; Prepositioning Programs

BIC, Norwegian Defense Logistics Organization/MEB (NDLO/MEB), MEF, AGSE prime contractors, FH, NMCB and the MCMC.

8.3.7 The PDM shall provide support for the operation of data retrieval systems, i.e., scanners, to assist in inventory and identification.

8.3.8 The PDMC shall interact with external users’ program administrators to ensure an interface is configured for data conversion into MDSS II and MCPIC.

8.3.9 The PDMC shall maintain a database that tracks all ships plans for all Plans & Data Reports identified in the Planning Section to ensure accuracy, consistency, and traceability in developing and modifying Ships Plans.

8.3.10 The PDMC shall provide data manipulation support establishing procedures and programs to support all interface requirements when necessary, produce reports through report generating software and develop and implement programs that support day-to-day operations as well as special requests, update all reference tables to support LOGAIS to include, but not limited to: Dangerous Cargo Manifest National Stock Number (DCMNSN), Limited Quantity (LTDQTY), and Technical Data.

8.3.11 The PDMC shall verify/validate all data before providing the data to other users.

9. LOGAIS

9.1 SCOPE. MCPP utilizes government owned LOGAIS, Databases and Software Programs to develop, and maintain program related information. Those Systems, Databases and Software Programs allow instant and unrestricted continual access to all pertinent entities and personnel involved with MCPP. In the performance of this PWS, the PDMC shall utilize and manage Government-provided Automated Information Systems (AIS). Any and all exceptions must be requested and approved in writing prior to implementation by the Information Systems Management Office (ISMO).

9.2 OBJECTIVE. The PDMC shall perform technical and functional assistance tasks that relate to LOGAIS, to include ICODES, MDSS II, PPS and MCPIC systems that support the logistics management of the MCPP. The PDMC shall provide the same support for future systems are anticipated to migrate to GCSS-MC.

The PDMC shall provide LOGAIS services to MPF, MCPP-N, BIC Government commodities, MCMC, BIC

Aviation Support Management Branch (ASMB) prime contractor work sections, deployment sites, aboard MPS, and other sites of users of MPF data as coordinated by the Government.

The PDMC shall plan, train, and provide all needed support necessary in reference to LOGAIS systems, AIT, Logistics Applications of Automated Marking and Reading Symbols (LOGMARS), and RFID in support of contingency operations, and exercises, as required by the COR.

9.3 REQUIREMENTS

9.3.1 The PDMC shall perform the following technical and functional tasks:

9.3.1.1 Automated Information Technology (AIT), LOGMARS system setup

9.3.1.2 RFID systems, training, troubleshooting

9.3.1.3 Support all LOGAIS planning and execution functions, contingency operation and exercises.

9.3.1.4 Troubleshooting, maintenance, and system upgrades

9.3.1.5 Software interface enhancement

9.3.1.6 Technical requirements analysis

9.3.1.7 Systems interface installations

9.3.1.8 Technical problem resolution, tracking, and reporting

9.3.1.9 Data conversion

9.3.1.10 Ad hoc report generation

9.3.1.11 Support coordination

9.3.1.12 Cost benefit analysis

9.3.1.13 Provide support necessary in reference to LOGAIS systems, AIT, LOGMARS, and

RFID in support of contingency operations.

9.3.2 SYSTEM SUPPORT

9.3.2.1 The PDMC shall respond to all problems and requests for assistance for LOGAIS systems, to include MAGTF LOGAIS, ICODES, PPS, MCPIC and other follow on systems.

9.3.2.2 The PDMC shall establish a helpdesk to monitor and track requests for assistance. The

PDMC shall document and implement a Corrective Action Process for handling all problems detected. The Corrective Action Process shall ensure that detected problems are promptly reported and entered into the corrective action process, action is initiated, resolution is achieved, status is tracked and reported, and records of the problems are maintained for the life of the contract.

9.3.3 ICODES

9.3.3.1 The PDMC shall use the software program ICODES to manipulate ships loads plans.

9.3.3.2 The PDMC shall convert ships load plans into diagrams which depict the actual planned locations of equipment to be loaded on the each ship.

9.3.3.3 The PDMC shall upload ship load plans in the ICODES format into MDSS II.

9.3.4 MDSS II

9.3.4.1 The PDMC shall provide MDSS II support to all approved users.

9.3.4.2 The PDMC shall establish levels of access to MDSS II in accordance with guidelines approved by the Government.

9.3.4.3 The PDMC shall facilitate MDSS II interface as required and approved by the

Government.

9.3.4.4 The PDMC shall provide MDSS II training as required.

9.3.5 MCPIC. The PDMC shall maintain MCPIC and ensure all files are kept current.

9.3.5.1 The PDMC shall maintain MCPIC to provide access to prepositioning reference material.

9.3.5.2 The PDMC shall collect, assimilate and develop user requirements in MCPIC as requested and provide all required documentation to support a Government Configuration Control

Board (CCB). The Government will prioritize all user feedback to determine the amount of resources that will be applied to individual requirements.

9.3.5.3 The PDMC shall define each MCPIC user associate to a specific functionality and assign a code in order to track requirements through development, testing and implementation.

Documentation of requirements shall include the results of testing.

9.3.5.4 The PDMC shall ensure all reports and plans identified in Section 7 of this PWS are posted to and maintained (kept current) in MCPIC.

9.3.6 INSTALLATION. The PDMC shall install Government prior approved MDSS II and ICODES related software, programs and systems upgrades.

9.3.7 SYSTEMS TRAINING. The PDMC shall provide training on government owned LOGAIS (to include RFID functionality), MCPIC and PPS systems for BIC, MEF, MCMC, ASMB prime contractor, FH and NMCB as coordinated and approved by the COR.

9.3.7.1 The PDMC shall provide training as required and approved by the Government.

9.3.7.2 The PDMC shall prepare a training plan for the Government. Training will be required for organizations internal and external to BIC.

9.3.7.3 Training shall be documented and maintained for a minimum of one year.

9.3.7.4 Training in the form of on-line help shall be provided on MCPIC or other approved government website.

9.3.7.5 Provide support necessary in reference to LOGAIS systems, AIT, LOGMARS, and RFID in support of contingency operations.

10. IUID and RFID Support

10.1 SCOPE. The DoD mandates the use of the IUID and RFID application for government owned equipment for inventory and tracking purposes. To ensure compliance with Government mandates, the PDMC shall provide services to facilitate IUID and RFID project management, tag placement, data collection, data registry, and system support. The PDMC shall train Government personnel and contractor personnel, as needed, in the use of the associated software programs and ancillary hardware/equipment used read the devices.

10.2 OBJECTIVE. The PDMC shall provide IUID and RFID project management, tag placement, data collection, data registry, systems support to the MCPP to enable asset inventory and tracking.

10.3 REQUIREMENTS. The PDMC shall provide support to BIC, NDLO/MEB, MEF, AGSE prime contractors, FH and NMCB and other entities as coordinated and approved by the COR.

10.3.1 The PDMC shall plan, train, and provide all needed support necessary in reference to IUID and

RFID in support of contingency operations and exercises as required by the COR for that particular operation or inspection.

10.3.2 The PDMC shall develop and deliver an IUID and RFID Status Report (CDRL B002) on quarterly basis.

11. PROGRAMMING SUPPORT AND SOFTWARE ENHANCEMENT

11.1 SCOPE. Provide programming support and software enhancements in direct support of MCPP. The PDMC shall not provide research and development functions under this PWS.

11.2 OBJECTIVE. The objective is to tailor government Commercial Off the Shelf (COTS) and Government Off the Shelf (GOTS) software to meet MCPP requirements. Software development is not authorized under this

PWS.

11.3 REQUIREMENTS

11.3.1 PROGRAMMING SUPPORT AND SOFTWARE ENHANCEMENT. The PDMC shall perform cost/benefit analysis to propose system changes that are the most cost effective while offering the least amount of risk. It is essential that both functional and technical considerations be integrated to provide an ordered set of risks, potential cost impacts and recommended strategies. The PDMC shall document and implement procedures for risk management. The P

DMC shall identify, analyze, prioritize, and monitor the areas of the software enhancement that involve potential technical, cost or schedule risks.

11.3.2 SOFTWARE SYSTEMS. The PDMC shall provide software enhancement services to validate functionality when requirements are ambiguous and further definition is required.

11.3.2.1 System requirements analysis shall consist of, but not limited to the following: functional and capability specifications: performance, physical characteristics, and environmental conditions, organizational and user requirements, external interfaces, design constraints and qualification requirements, security specifications, safety specifications, data definition and database requirements, installation and acceptance requirements and user documentation.

11.3.2.2 The system requirements shall be documented for traceability to acquisition needs, consistency with acquisition needs, testability, feasibility of system design and feasibility of operation and maintenance.

11.3.2.3 The PDMC shall perform detailed analysis and design on security and technology concerns to streamline the automated functions within the command. Throughout this effort, the

PDMC shall ensure all changes to existing applications are fully tested, documented, and that adequate training is provided to the end users. As changes are accomplished with this system, the

PDMC shall ensure that interoperability is accomplished and that data integrity is maintained.

11.3.2.4 The PDMC shall submit monthly schedules that list actual start and end dates of each task. The monthly schedule shall include the cumulative percentage of work completed by task and the cumulative percentage of total contract work completed to date.

11.3.3 SOFTWARE ENHANCEMENT

11.3.3.1 The PDMC shall provide user documentation immediately upon implementation of new or modified procedures or programs or upon request.

11.3.3.2 The PDMC shall implement a process for managing the enhancement of software deliverables.