BACAPS_Task_Order_-_Exhibit_D_PWS.docx
DOCX document 99 KB Posted
- Attached to
- Business Management and Analytics, Cost Analysis, and Portfolio Support (BACAPS) Competitive 8(a) Set Aside
- Solicitation number
- M67854-15-R-4803
- Issued by
-
United States Marine Corps
About this file
Revised Exhibit D - TO PWS
View the file
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
2612 May 2015
Exhibit D - Task Order Performance Work Statement For Product Manager (PdM) Total Force Information Technology Systems (TFITS) Business Analytics, Cost Analysis and Portfolio Support (BACAPS)
Scope:
The scope of this effort is to deliver Business Management and Analytics, Cost Analysis, and Portfolio Support (BACAPS) for Projects within Product Manager (PdM) Total Force Information Technology Systems (TFITS).
TFITS supports 28 major Projects (Applications/Systems) organized into three Main Portfolios of systems or Tier 2s (See Appendix A - TFITS Organizational Chart):
· Manpower Operation Systems (MOS)
· Warfighting Planning and Analysis (WPA)
· Headquarters Marine Corps (HQMC) Sustainment and Training (HST)
TFITS has categorized each Project requiring support into two defined segments: Managed and Supported. There are 23 Managed and 5 Supported Projects (See Appendix B – TFITS Project Descriptions). The following definitions are provided for clarification:
1) Managed: TFITS has control of all funding required for end-to-end lifecycle acquisition sustainment. Full support of Program Management, Cost Analysis, Engineering, Information Assurance, and Logistics is required.
2) Supported: TFITS has limited programmatic authority of the Project. This includes Joint Projects that require United States Marine Corps (USMC) certification and accreditation, fair share funding, and Configuration Management support.
The number of projects managed by TFITS is expected to change on a year to year basis and the contractor should be prepared to support the addition of two to three new programs/projects annually.
The requirements identified in this PWS will provide support to the following tiers of the TFITS organization:
1) Tier 1: PdM, Deputy Product Manager (DPdM), and functional area Competency Leads. These are the leadership roles within PdM TFITS, reporting to the higher PM-110 Tier 0 level.
2) Tier 2: Three (3) TFITS Portfolio Managers, overseeing TFITS Acquisition and Portfolio Management: MOS; WPA; and HST.
3) Tier 3: TFITS Project Managers (PjM), managing Project-level Applications/Systems within the overarching Tier 2 structure.
The Cost Analysis support requested will enhance TFITS’ government personnel’s ability to draft more standardized Independent Government Cost Estimates (IGCE), and to support the ability to validate vendor cost proposals in support of better buying power initiatives.
To perform this cost analysis support it will be required to get consent from the vendor in order to be able to review rate and costing information. This will be accomplished by a Non-Disclosure Agreement with the vendor.
The Cost Analysis Command Oversight support will be utilized to further support TFITS’ cost analysis needs. These include the drafting and maintenance of project cost products, ranging from informal Project Cost Estimates for the TFITS managed systems, to formal Cost Analysis Requirements Descriptions (CARD), Program Life Cycle Cost Estimates (PLCCE), Logistics Requirements Funding Summaries), and supporting process documentation.
The contractor or any subcontractor utilized in the execution of this contract may potentially eliminate themselves from any future Systems Integration work for systems covered in this contract.
The PdM Tool Set support will be used to update and maintain the existing Tools, to include administration, training and materials, supporting documentation, and tool enhancements.
Purpose:
This Task Order is intended to deliver Business Analytics and Cost Analysis Support. The Task Order Matrix (Attachment 2) and the Task Order Historical Level of Effort (Exhibit A) identifies the anticipated support required by each project and historical support estimates.
Reserved
General Requirements:
3.1 All deliverables shall be submitted to the Contracting Officer’s Representative (COR) and the COR is responsible for tracking and acceptance.
3.2 The Contractor shall organize and attend meetings within 10 miles driving distance of the Quantico Corporate Center located at 1000 Corporate Drive, Stafford, Virginia. Contractor personnel shall attend regular meetings with stakeholders in the general vicinity of Marine Corps Base Quantico and as far away as the Pentagon. The contractor personnel are expected to be physically present at numerous meetings each week in support of PdM TFITS Integrated Product Teams at the Product, Portfolio and project levels.
3.3 The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and 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.
3.4 The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the United States Marine Corps via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:
(1) W, Lease/Rental of Equipment;
(2) X, Lease/Rental of Facilities;
(3) Y, Construction of Structures and Facilities;
(4) S, Utilities ONLY;
(5) V, Freight and Shipping ONLY.
3.5 The Contractor shall submit to the Contracting Officer's Representative quarterly reports showing the total amount of labor costs incurred under this task order, broken out for the Prime Contractor and each Subcontractor. The Government will use this information to ensure the Contractor's compliance with Federal Acquisition Regulation 52.219-14, Limitations on Subcontracting.
Deliverable A0001: COR Quarterly Report
0. During the performance of their duties, the Contractor will work closely with the Government project teams and be exposed to project level data. All Contractor personnel supporting this contract will be required to sign and submit a U.S. MARINE CORPS SUPPORT CONTRACTOR NON-DISCLOSURE AGREEMENT (INDIVIDUAL) and may be ineligible to compete in future system integrationassociated project support contracts.
Specific Requirements:
4.1 Tier 1 Program Management Support:
4.1.1 Within five (5) working days of task order award, the Contractor shall organize and attend a kick off meeting.
4.1.2 Within 30 days of task order award, the Contractor shall develop and maintain a contract management plan.
Deliverable P0001: Contract Management Plan (CMP)
4.1.3 Within 30 days of initial award, the Contractor shall develop and submit a diagram of the company organizational chart depicting the personnel directory with the positions and matrix of support. Once developed, the diagram shall be maintained on a quarterly basis.
Deliverable P0002: Organizational Diagram
4.1.4 The Contractor shall conduct quarterly In-process Reviews (IPRs) that address an overall assessment of contract status, project review, program risk, status of funds, status of vacancies, schedules, completed deliverables, and concerns.
4.1.5 The Contractor shall prepare and submit a Monthly Status Report (MSR) by the fifth (5th) calendar day, for the preceding month of performance, throughout the contract period of performance. The MSR shall cover monthly accomplishments, status of deliverables, planned activities for the next month, status of invoicing and billing, updated risk list and any other items that need the Government’s attention. The Contractor shall collect and report on the performance metrics associated with deliverable and schedule completion. The final format for the report shall be coordinated between the Government and Contractor. At a minimum the MSR shall include:
· Contract Number
· Invoicing Period (start and end dates)
· List of accomplishments during the period by task/deliverable
· Contract issues and risks ranked by severity
· Contract Line Item Number status
· Rationale for deviations from schedule with mitigation plan
· Any other significant issues (schedule, technical, resource, etc.) with proposed resolution
Deliverable P0003: Monthly Status Report
4.1.6 Contract Final Report - The Contractor shall deliver a contract final report summarizing the entire period of performance. The report shall include a summary of all MSRs delivered. The report shall include all contract accomplishments, deviations from plan with background information, and lessons learned from contract activities (what has been experienced, and process improvement recommendations). The Contractor shall provide with the final report a complete set of indexed contract documentation, including the closed contract.
Deliverable P0004: Contract Final Report
4.1.7 The Contractor shall organize and attend Bi-Weekly Business Analytics IPT Meetings within 10 miles driving distance of the Quantico Corporate Center located at 1000 Corporate Drive, Stafford, Virginia. Network and power connections for each attendee are required. Presentation equipment must be available for use to include, but not limited to projectors, televisions, monitors, and conference capable telephones.
4.1.8 The Contractor shall develop, submit and deliver meeting minutes for Bi-Weekly Business Analytics IPT Meetings within two (2) working days following the meeting.
Deliverable P0005: Meeting Minutes
4.1.9 The Contractor shall maintain the PdM TFITS Risk Management Plan.
Deliverable P0006: Risk Management Plan
4.1.10 The Contractor shall organize and attend the PdM TFITS Tier 1 risk management board on a monthly basis and update the PdM TFITS Risk Tracker with input provided by the PdM TFITS Tier 1 and 2 risk management boards.
Deliverable P0007: Risk Tracker
4.1.11 The Contractor shall develop and submit meeting minutes for Monthly Risk management board Meetings.
Deliverable P0008: Risk Management Board Meeting Minutes
4.2 Business Management and Analytics
4.2.1 The contractor shall conduct business management activities to include financial risk assessments for scheduled events, impact of changes, preventative and corrective actions, maintenance of Financial Management Planner (Execution Tool), Analysis of Phasing/Obligation Rates, preparation and delivery of Business Case Analyses and insert results within the Risk Tracker on a monthly basis.
4.2.2 The contractor shall draft, consolidate and submit Risk Assessment data for inclusion in Program Management, Executive, and General Officer Reviews on a monthly basis.
4.2.3 The contractor shall consolidate and monitor all TFITS Project inch stones at a portfolio level (Tier 1 and 2) for funding obligations and identify timelines are being met in accordance with the Office of the Secretary of Defense execution benchmarks on a weekly basis.
4.2.4 The contractor shall perform portfolio aggregate financial analysis and develop and submit the Portfolio Financial Analytical Reports on a weekly basis. This analysis and reporting will include monitoring on the status of portfolio funds within the PdM Tool Set, and consolidating and analyzing changes to TFITS financial artifacts such as Spruill, belt, and inflow/outflow charts. This analysis will support Tier 1 and PM-110 briefings, provide the PM/PdM with decision making information necessary for overall TFITS management, enable TFITS to execute according to plan, and project shortfalls and assets to support Current Year Deficiency submissions and reprogramming submissions.
Deliverable B0001: Weekly Funding Status Report
4.2.5 The contractor shall annually review TFITS Program Objective Memorandum submissions for consistency across the TFITS portfolio and ensure the funding requested is consistent with the Project Cost Estimates.
4.2.6 The contractor shall attend and brief their program support status at the weekly TFITS Tier 1, highlighting the support being provided at the Tier 1, Tier 2, and Tier 3 levels in order to reallocate resources if necessary based on PdM priorities.
4.2.7 The contractor shall develop and deliver reports capturing personnel utilization metrics on a monthly basis to ensure personnel resources are being assigned to PdM TFITS priorities.
Deliverable B0002: Status Slides for TFITS Briefings
4.2.8 The contractor shall obtain and consolidate health assessments from each Competency Lead in order to brief the PdM weekly on the overall assessments.
4.2.9 The contractor shall perform process analysis and develop and maintain Funding life cycle Responsible, Accountable, Consulted and Informed Charts on a quarterly basis.
Deliverable B0003: Responsible, Accountable, Consulted, and Informed Charts
4.2.10 The contractor shall continually administer and maintain the TFITS Microsoft SharePoint Site Collection (and WIKIs) and ensure it is in accordance with Information Systems and Infrastructure (IS&I) policies and directives. The Contractor shall obtain the appropriate Marine Corps Enterprise Information Technology Services account(s) and access to manage document libraries, workflows, and Wiki pages.
4.2.11 The contractor shall attend the IS&I SharePoint Configuration Control Board (CCB) on a monthly basis for impacts and alignment with the TFITS Site Collection.
4.2.12 The contractor shall facilitate, attend, draft meeting minutes, and implement assigned actions identified by the monthly TFITS SharePoint CCB.
Deliverable B0004: Meeting Minutes
4.2.13 The contractor shall continuously provide administrator and issue support for users of the TFITS SharePoint Portal.
4.2.14 The contractor shall continually maintain TFITS SharePoint Portal site development and maintenance procedures documentation.
4.2.15 The contractor shall consolidate and submit the PdM TFITS Weekly Situation Report to PM IS&I.
Deliverable B0005: TFITS Weekly SITREP
4.2.16 Reserved
4.2.17 The contractor shall provide analytical cross competency support to the PdM and DPdM by coordinating and tracking TFITS responses for Marine Corps Action Tracker System taskers (approximately 300 per year).
4.3 Cost Analysis:
4.3.1 The contractor shall coordinate with the Project Officers and submit annual updates to the Project Cost Estimates.
Deliverable B0007: Annual Project Cost Estimate Updates
4.3.2 The contractor shall quarterly review and update the standard TFITS Cost Element Structure included within all TFITS contracts packages.
4.3.3 The contractor shall review TFITS Performance Work Statements/Statements of Work/Statements of Objectives for completeness, clarity, and ensure the information contained is sufficient for a vendor to deliver a valid proposal. It is estimated that TFITS will draft 15-20 Requests for Proposal per year.
4.3.4 The contractor shall train, maintain, and assist in using a standard template for TFITS IGCEs, consistent with the TFITS Cost Estimate Structure.
Deliverable B0008: IGCE Template
4.4 Cost Analysis Command Oversight:
4.4.1 The Contractor shall provide an annual CARD for the Total Force Structure Management System (TFSMS) and the Defense Readiness Reporting System – Marine Corps (DRRS-MC) programs in accordance with the DoD 5000 Series and SECNAVIST 5223.2A requirements. Each CARD will be updated and maintained to reflect the life cycle of the programs providing a foundation upon which to update the PLCCE.
Deliverable C0001: Cost Analysis Requirements Description
4.4.2 The Contractor shall conduct an annual review of all required programmatic description elements to ensure they are thoroughly documented and reconciliation discussions are analytically supported.
4.4.2.1 TFSMS and DRRS-MC only
4.4.3 The Contractor shall create, update, maintain, and deliver each Logistics Requirements and Funding Summary annually for the programs.
4.4.3.1 Update maintain and deliver for TFSMS, DRRS-MC and JFRG-II Modernization efforts
Deliverable C0002: Logistics Requirements and Funding Summary
4.4.4 The Contractor shall create, update, maintain, and deliver the PLCCE on an annual basis.
4.4.4.1 Update maintain and deliver for TFSMS, DRRS-MC and JFRG-II Modernization efforts.
Deliverable C0003: Program Life Cycle Cost Estimate
4.4.5 The Contractor shall coordinate with the Project Manager and Program IPT in order to update and maintain the ground rules and assumptions that establish the parameters of the PLCCEs on an annual basis.
4.4.5.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.6 The Contractor shall update and maintain all the appropriate cost estimating relationships to properly update and maintain the PLCCEs. The PLCCEs shall be thoroughly documented to ensure traceability of algorithmic choices and data sources. Each sub-system in each program shall be traceable throughout the overarching Life Cycle Cost Model (LCCM). The LCCM shall include appropriate cross-checks for significant cost elements. The PLCCEs shall include all associated cost and schedule parameters; risk/uncertainty analyses; cost and schedule driver analyses; "what-if" analyses; and associated sensitivity analyses to support budget and other programmatic decision support needs of the PjMs on an annual basis.
4.4.6.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.7 The Contractor shall develop and present briefings of CARDs and PLCCEs to the respective decision-making authorities at IPRs, Technical Review Boards, and Contract Review Boards. During the CARD review process, the Contractor shall maintain a complete and up-to-date CARD Review Matrix of all CARD comments on an annual basis.
4.4.7.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.8 The Contractor shall track cost, schedule, performance, and technology-driven elements annually within the program Work Breakdown Structure and Cost Element Structure to include, logical impacts and associated risks as specified by the Marine Corps Systems Command (MCSC) Assistant Commander for Programs Assistant Commander for Programs Study Director.
4.4.8.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.9 The Contractor shall participate in the Cost IPT and conduct, analyze, and compile Would Cost/Should Cost scenarios for inclusion in all Project presentations on a monthly basis.
4.4.9.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.10 The Contractor shall develop a complete LCSP for TFSMS, DRRS-MC, TMIP and JFRG-II.
4.4.10.1 For TFSMS, provide updated Cost information in support of a LCSP Update
4.4.10.2 For DRRS-MC, TMIP and JFRG-II Modernization efforts maintain LCSP cost information.
Deliverable C0004: Program LCSP cost information
4.4.11 The Contractor shall draft and maintain cost related briefings for all levels of management, to include the MCSC Milestone Decision Authority on a semi-annual basis.
4.4.11.1 For TFSMS, DRRS-MC and JFRG-II Modernization efforts.
4.4.12 The Contractor shall develop and deliver and maintain project cost models.
4.4.12.1 For TFSMS, DRRS-MC, TMIP and JFRG-II Modernization efforts maintain current project cost models.
Deliverable C0005: Cost Model
4.4.13 Reserved
4.4.14 Reserved
4.4.15 Reserved
4.4.16 Reserved
4.4.17 Reserved
4.4.18 Reserved
4.4.19 Reserved
4.4.20 Reserved
4.4.21 Reserved
4.4.22 Reserved
4.4.23 Reserved
4.4.24 Reserved
4.5 Product Manager Tool Set Support:
4.5.1 The contractor shall continually provide project management, scheduling, coordination of developers and staff for meeting support, demonstrations and training, and confirm SharePoint compliance.
4.5.2 The contractor shall support demonstrations to stakeholders and provide training of the PdM Tool Set to new users.
4.5.3 The contractor shall implement quarterly maintenance changes to Tools to support SharePoint environment changes. Examples of changes include accommodating SharePoint upgrades, DFM Financial Management Tool upgrades, IA compliance, etc.; two CCB approved minor enhancements and one CCB approved major enhancement (Major and minor enhancements are defined in the TFITS Systems Engineering Plan (SEP).
Deliverable T0001: PdM Tool Set Update
4.5.4 The contractor shall participate in monthly working group meetings, capture meeting minutes, submit recommendations to issues, and provide updates and resolution to action items.
Deliverable T0002: PdM Tool Set Working Group Minutes
4.5.5 The contractor shall update training materials to reflect maintenance and enhancement updates.
4.5.6 The contractor shall update the requirements traceability matrix to reflect maintenance and enhancement updates.
Deliverable T0003: PdM Tool Set Documentation Updates
4.5.7 The contractor shall create new and update existing report types in the PdM Tool Kit as identified and approved in the CCB process as well as the insertion of user interfaces and new "dashboard" features.
5 Facilities, Other Direct Costs (ODCs), and Travel Requirements:
Work efforts in support of this task effort will be accomplished at the Contractor’s facilities. This task will require the Contractor to provide a suitable infrastructure to manage program requirements (document library, databases, web site) throughout the course of performance to support the scope of activities. Such facilities are not reimbursed as ODCs. Laptops, cellular equipment/services, and other items of convenience are not reimbursable as ODCs.
All Government printing requirements MUST be done by or through the local Document Automation and Production Service (DAPS, now called DLA Document Services) http://www.daps.dla.mil/dapsonline.html.
Travel outside of the supported geographic region is not anticipated.
6 Security Requirements:
The information provided to the contractor will be unclassified and/or sensitive unclassified information. The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. Any contractor personnel requiring access to U.S. Government sensitive unclassified information shall possess a completed background investigation (minimum of a National Agency Check with Written Inquiries (NACI)) for this Public Trust Position.
7 Common Access Card (CAC) Requirements:
7.1 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 Joint Personnel Adjudication System (JPAS) record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened.) The minimum acceptable investigation is a National Agency Check with Written Inquiries. If a Contractor employee’s open investigation closes and is not favorably adjudicated, the CAC must be immediately retrieved and revoked.
7.2 Facility Security Officers (FSOs) are responsible for notifying the MCSC 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.
7.3 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 their .com e-mail account. 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.
7.4 CACs will only be issued to those Contractors supporting this contract that have been authorized by the COR. The COR will only authorize CACs for those Contractors that meet current (HSPD-12) criteria and have a definitive requirement.
7.5 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. Such individuals must be replaced on the contract as soon as possible, not to exceed 30 calendar days unless otherwise coordinated and approved by the COR. CACs are not issued for convenience.
7.6 All contract support requiring administrative access to IT systems shall have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. This does not apply to contract support working administrative tasks. The Contractor shall meet the applicable information assurance certification requirements, including-
1. DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; IAT level III or IAM Level II or higher preferred and
2. Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.
Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing cyber security functions.
1. Applicable Documents / References:
The following documents provide essential programmatic information that needs to be considered in the contractor’s proposal and deliverables.
0. Contractor Management Documentation
| Document / Reference |
| Intended Use |
| PM TFITS CMP, - final |
| Overarching Configuration Management (CM) Guidance |
| PM TFITS Acquisition Strategy / Acquisition Plan (AS/AP), - Draft |
| Overarching Acquisition Strategy |
| PM TFITS Systems Engineering Plan (SEP), Draft |
| Overarching Systems Engineering Requirements/Guidance |
| PM TFITS Test and Evaluation strategy, - Draft |
| Overarching Test Requirements/Guidance |
| Government Program Work Breakdown Structure (GWBS) |
| Detailed Planning for all Application efforts |
| Appendix B - TFITS Project Definitions |
| Individual Project descriptions, offering system scope/scale |
8.2 System Engineering Documentation
| Document / Reference |
| Intended Use |
| Software Design Specification |
| A comprehensive description of the intended purpose and environment for software under development |
| Application/System |
| A comprehensive description of the intended purpose and environment for system under development |
| Performance Measurement Plan (PMP) - Draft |
| Describe the overarching Application performance measurement process and metrics that reflect program health and provide information for use in estimating future efforts |
| Requirements Management Plan (RMP) - Draft |
| Documenting, analyzing, tracing, prioritizing, and agreeing upon all requirements received or generated, including technical/performance (non-functional) and operational (functional) requirements |
| Quality Assurance Surveillance Plan (QASP) |
| Addresses requirements for quality surveillance and quality control of services, products, deliverables, and procedures provided |
| AS/AP |
| Document Application Acquisition and Milestone support |
8.3 Other Guidance & Standards
| Document / Reference |
| Intended Use |
| Federal Information Security Management Act (FISMA) of 2002 |
| Information Security Requirements/Guidance |
| DoDD 8500.01E, Information Assurance (IA), 24 Oct 2002 (current as of 23 Apr 2007) |
| Information Security Requirements/Guidance |
| DoDI 8500.2, Information Assurance (IA) Implementation, 6 Feb 2003 |
| Information Security Requirements/Guidance |
| DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 Nov 2007 |
| Information Security Requirements/Guidance |
| DoD 8570.01-M, Information Assurance Workforce Improvement Program, Incorporating Change 3, January 24, 2012 |
| Information Security Requirements/Guidance |
| CJCSI 6510.01E, Information Assurance and Computer Network Defense, 15 Aug 2007 |
| Information Security Requirements/Guidance |
| Department of the Navy, DoD Information Assurance Certification and Accreditation Process (DIACAP) Handbook, Version 1.0, 15 July 2008 |
| Information Security Requirements/Guidance |
| SECNAVINST 5000.2D, Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System, 16 Oct 2008 |
| Information Security Requirements/Guidance |
| DoD 5200.2-R, Personnel Security Program |
| Information Security Requirements/Guidance |
| DoDD 8000.01, Management of the DoD Information Enterprise |
| Information Security Requirements/Guidance |
| NFPA 75 (Standard for the Protection of Information Technology Equipment) |
| Information Security Requirements/Guidance |
| MCO 5239.1, Marine Corps Information Assurance Program (MCIAP) |
| Information Security Requirements/Guidance |
| MARADMIN 639/08, MCBUL 5239 USMC IA VULNERABILITY MANAGEMENT (IAVM) PROGRAM |
| Information Security Requirements/Guidance |
| IETF RFC 4346 - The Transport Layer Security (TLS) Protocol, Version 1.1, April 2006. The Certificate Issuing and Management Components (CIMC) Family of Protection Profiles (PPs). (http://www.commoncriteriaportal.org/pp_OD.html) |
| Information Security Requirements/Guidance |
| Net-Centric Enterprise Solutions for Interoperability (NESI) guidance, standards and checklists. (http://nesipublic.spawar.navy.mil/) |
| Information Security Requirements/Guidance |
| Net-Centric Enterprise Services (NCES) (http://www.disa.mil/nces/) |
| Information Security Requirements/Guidance |
| DoD 5000.02, Operation of the Defense Acquisition System |
| MIL/DoD/SECNAC Guidance/Requirements |
| Defense Acquisition Guidebook (https://dag.dau.mil/Pages/Default.aspx) |
| MIL/DoD/SECNAC Guidance/Requirements |
| SECNAVINST 5000.2D, Implementation And Operation Of The Defense Acquisition System And The Joint Capabilities Integration And Development System |
| MIL/DoD/SECNAC Guidance/Requirements |
| IEEE/EIA 12207, Systems and software engineering - Software life cycle processes |
| MIL/DoD/SECNAC Guidance/Requirements |
| ISO/IEC 15289:2006(E), Systems and software engineering - Content of system and software life cycle process information products (Documentation) |
| MIL/DoD/SECNAC Guidance/Requirements |
| DFARS 252.211-7003, "Item Identification and Valuation" |
| MIL/DoD/SECNAC Guidance/Requirements |
| DoD Guide to Uniquely Identifying Items |
| MIL/DoD/SECNAC Guidance/Requirements |
| Modular Open Systems Approach (MOSA), Version 2.0 http://www.acq.osd.mil/osjtf/html/mosa_assessment.html) |
| MIL/DOD/SECNAC Guidance/Requirements |
| DISA Policy and Guidance http://iase.disa.mil/policy-guidance/index.html |
| MIL/DoD/SECNAC Guidance/Requirements |
| Guidebook for Acquisition of Naval Software Intensive Systems |
| MIL/DoD/SECNAC Guidance/Requirements |
| Marine Corps Systems Command Technical Review Handbook v1-04 |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSC Order 5000.3A, 8 Mar 2012, Implementation of MCSC Acquisition Guidebook (MAG) and Probability of Program Success (PoPS) Version 2 (V2) Procedures |
| MIL/DoD/SECNAC Guidance/Requirements |
| Acquisition Policy Letter 02-09, 26 May 2009, Modifications to Systems |
| MIL/DoD/SECNAC Guidance/Requirements |
| Risk Management Guide for DOD Acquisition Sixth Edition V1.0, 4 Aug 2006 |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSC Order 4130.1, 6 Jan 2010, Configuration Management (CM) Policy |
| MIL/DoD/SECNAC Guidance/Requirements |
| MIL-PRF-49506 Logistics Management Information |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCO 5311.1_ Total Force Structure Process |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSCO 4410 Implementation of MCSC LCSP for All Acquisition Programs |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSC Policy Letter 3-08 ILA Process |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSC MPT Requirements Analysis Guide with MAD Tool v1.1 |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCSCO 5000.3A Implementation of MCSC Acquisition Guidebook and Probability of Program Success v2 Procedures |
| MIL/DoD/SECNAC Guidance/Requirements |
| MCO 5311.1_ Total Force Structure Process |
| MIL/DoD/SECNAC Guidance/Requirements |
| MIL-HDBK-470 Designing and Developing Maintainable Products and Systems |
| MIL/DoD/SECNAC Guidance/Requirements |
| MIL-HDBK-781 Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production |
| MIL/DoD/SECNAC Guidance/Requirements |
| MIL-STD-1472F Department of Defense Design Criteria Standard: Human Engineering |
| MIL/DoD/SECNAC Guidance/Requirements |
| ASME Y14.34 (Associated Lists) |
| MIL/DoD/SECNAC Guidance/Requirements |
| ASME Y14.100 Engineering Drawing Practices |
| MIL/DoD/SECNAC Guidance/Requirements |
| EIA-625 Requirements for Handling Electrostatic Discharge-Sensitive (ESDS) Device |
| MIL/DoD/SECNAC Guidance/Requirements |
| EIA-649 National Consensus Standard for Configuration Management |
| MIL/DoD/SECNAC Guidance/Requirements |
| Information Technology Infrastructure Library (ITIL) v3 Foundation |
| MIL/DoD/SECNAC Guidance/Requirements |
| Capabilities Maturity Model Integration (CMMI) v1.3 |
| MIL/DoD/SECNAC Guidance/Requirements |
9 Deliverables List
| Deliverable Number |
| Deliverable |
| PWS Paragraph |
| A0001 |
| COR Quarterly Report |
| 3.5 |
| P0001 |
| Contract Management Plan |
| 4.1.2 |
| P0002 |
| Organizational Diagram |
| 4.1.3 |
| P0003 |
| Monthly Status Report |
| 4.1.5 |
| P0004 |
| Contract Final Report |
| 4.1.6 |
| P0005 |
| Meeting Minutes |
| 4.1.8 |
| P0006 |
| Risk Management Plan |
| 4.1.9 |
| P0007 |
| Risk Tracker |
| 4.1.10 |
| P0008 |
| Risk Management Board Meeting Minutes |
| 4.1.11 |
| B0001 |
| Weekly Funding Status Report |
| 4.2.4 |
| B0002 |
| Status Slides for TFITS Briefings |
| 4.2.7 |
| B0003 |
| Responsible, Accountable, Consulted, and Informed Charts |
| 4.2.9 |
| B0004 |
| Meeting Minutes |
| 4.2.12 |
| B0005 |
| TFITS Weekly SITREP |
| 4.2.15 |
| B0007 |
| Annual Project Cost Estimate Updates |
| 4.3.1 |
| B0008 |
| IGCE Template |
| 4.3.4 |
| C0001 |
| Cost Analysis Requirements Description |
| 4.4.1 |
| C0002 |
| Logistics Requirements and Funding Summary |
| 4.4.3 |
| C0003 |
| Program Life Cycle Cost Estimate |
| 4.4.4 |
| C0004 |
| Program Life Cycle Sustainment Plan |
| 4.4.10 |
| C0005 |
| Cost Model |
| 4.4.12 |
| T0001 |
| PDM Tool Set Update |
| 4.5.3 |
| T0002 |
| PDM Tool Set Working Group Minutes |
| 4.5.4 |
| T0003 |
| PDM Tool Set Documentation Updates |
| 4.5.6 |
10. Period of Performance
The expected ordering period for this task order is ten (10) months.
File details come from the government source that posted it. Updated .