Embed
Email

SAMPLE ONLY

Document Sample
SAMPLE ONLY
Shared by: HC1111261656
Categories
Tags
Stats
views:
8
posted:
11/26/2011
language:
English
pages:
15
SAMPLE ONLY



STATEMENT OF WORK



For



JINTACCS Program



Technical and Engineering Support Services









Prepared by:



UNITED STATES MARINE CORPS

Marine Corps Tactical Systems Support Activity

Test Certification Group (TCG)

Camp Pendleton, CA 92055-5171









REFERENCE #: M68909JINTAC 1

1.0 INTRODUCTION



1.1 Background



The Marine Corps Tactical Systems Support Activity (MCTSSA), Marine Corps Systems

Command (MARCORSYSCOM) provides technical support for the integration and

interoperability assessment of C4I systems and is the Marine Corps primary focal point

for configuration management of Joint Interoperability Standards and Joint Certification

test and evaluation. MCTSSA performs mission analysis, assessment of the technology

base, concept exploration, basic research, demonstration of technology, engineering in

support of production, system engineering, support of operating forces, and integration of

C4ISR systems.



MCTSSA Test Certification Group (TCG) is responsible for providing support for the

integration, validation, and certification of C4I and other Tactical Data Systems (TDS).

The Joint Interoperability of Tactical Command and Control Systems (JINTACCS)

primary areas of responsibility are the performance of Interoperability Certification

Testing and analysis, and the development and maintenance of Tactical Data Exchange

Standards and Technical Interoperability Standards. Additionally, development and

implementation of Service, Joint and Combined operational procedures, and

interoperability support to the Marine Corps Network Design Facility for design,

implementation, and operation of interoperable Joint Tactical Information Distribution

System (JTIDS) networks is of primary concern.



1.2 Scope



This sample Statement of Work (SOW) defines the non-personal technical and

engineering support services required by MCTSSA for the fulfillment of the JINTACCS

Project’s responsibilities related to interoperability standards, certification testing, and

JTIDS network design. This is a level-of-effort task order.



2.0 APPLICABLE DOCUMENTS



2.1 The following documents are applicable to this SOW and provide guidance to achieve

interoperability among Marine Corps tactical systems:



a. DoD Directive/Instruction 4630.5, Interoperability and Supportability of

Information Technology (IT) and National Security Systems (NSS), dtd

May 5, 2004.

b. DoD Directive/Instruction 4630.8, Procedures for Interoperability and

Supportability of Information Technology (IT) and National Security Systems

(NSS), dtd June 30, 2004.

c. Chairman Joint Chiefs of Staff Instruction (CJCSI) 6212.01D, Interoperability

and Supportability of Information Technology (IT) and National Security Systems

(NSS), dtd March 14, 2007.

d. DoD Net Centric Data Strategy, dtd 9 May 2003

e. MCO 3093.1C, Intraoperability and Interoperability of Marine Corps Tactical



REFERENCE #: M68909JINTAC 2

C4I

Systems, dtd June 15, 1989.

f. Joint Interoperability Test Command (JITC) Plan 3006 (current version).



2.2 The following technical and procedural standards documents are applicable to this

SOW to the extent specified herein:



a. Department of Defense Interface Standard. Tactical Data Link (TDL) Link

11/11B Message Standard (MIL-STD-6011C), dtd 1 Aug 2002.

b. Department of Defense Interface Standard. Tactical Data Link (TDL) Link 16

Message Standard (MIL-STD-6016C Change 1), dtd 28 Mar 2005.

c. Department of Defense Interface Standard. Variable Message Format (MIL-

STD-6017A) dtd 19 July 2006.

d. USMTF Message Text Format Program MIL-STD-6040, dtd 31 Mar 2006

e. Chairman Joint Chiefs of Staff Manual 6120.01D Joint Multi-Tactical Data

Link Operating Procedures, dtd 22 Nov 2005.

f. Allied Data Publication 33 Multi-Link Standing Operating Procedures,

(ADatP-33)

g. Marine Corps Tactical Data Systems Reference Guide, dtd January 2005.

h. Allied Data Publication 3 NATO Message Text Format Program ADatP-3

Baseline 13

i. Department of Defense Interface Standard Data Forwarding Between Tactical

Data Links (MIL-STD-6020), dtd 31 Mar 2004.

j. Department of Defense Interface Standard. Interoperability Standard for Joint

Range Extension Application Protocol (JREAP) MIL-STD-3011, dtd 30

September 2002.



3.0 REQUIREMENTS



The contractor shall provide non-personal technical and engineering support services and

deliverable products as required in this SOW. The contractor shall provide technical and

engineering support for interoperability certification testing, tactical data exchange

standards, analysis of operational procedures, and information modeling and data

management support.



3.1 Test and Evaluation Support



The contractor shall provide pre-test, test and post-test analysis support during Marine

Corps Interoperability Certification Testing, Joint Interoperability Certification Testing

and NATO Combined Interoperability Testing with Marine Corps Command and Control

Systems and other Joint and NATO participating systems. A primary focus of testing

shall include, but is not necessarily limited to, Tactical Data Links (TDL) 11/11B/16,

Variable Message Format (VMF), United States Message Text Format (USMTF), and

North Atlantic Treaty Organization (NATO)/Allied Validation.



Test and Evaluation Support shall consist of the review of test plans, test procedures and

test scripts. The contractor shall monitor the conduct of tests by verifying adherence to



REFERENCE #: M68909JINTAC 3

the test plans and test scripts. The test plans and procedures will be provided by the

Government to the Contractor prior to commencement of each test. The contractor shall

have access to the systems under test and to the Systems Integration Environment (SIE)

in order to perform this task. The contractor shall take notes on observed system

performance, documenting any anomalies and apparent system failures. Upon completion

of the test, the contractor shall analyze data extraction files and Program Change Reports

(PCR), Trouble Reports (TR), Preliminary Trouble Reports (PTR) and System Trouble

Reports (STR) in order to validate observed performance characteristics. The contractor

shall generate a Test Report to be submitted to the Government for each test supported.



The contractor shall participate in the Joint Analysis Review Panel meeting and prepare a

report to be submitted to the Government for any assigned tests. For estimating purposes,

ten (10) tests are planned for this contract period, six (6) Joint Interoperability

Test/Combined Interoperability Test (JITs/CITs), two (2) MTF Standard Conformance

Test (SCT), and two (2) VMF pre-certification/SCT tests. The individual tasks of Pre-

Test and Test Monitoring, Post-Test Analysis, and Test Review Support are described in

additional detail below. A Draft Joint Test Schedule, Attachment 1, is provided, however,

this schedule is subject to change and not all tests listed will require contractor support.

The JINTACCS Technical Support Officer (TSO) will notify the contractor no later than

ten (10) working days prior to required test support.



3.1.1 Pre-Test Support



The contractor shall review test plans, test procedures and individual test scripts. For

estimating purposes, approximately ten (10) documents of varying complexity shall be

received during the period of performance. Complexity of the documents to be reviewed

is classified as simple, 20% (40 hours for

review, analysis and reporting). Complexity of documents will be identified for each

document. The following documents anticipated for review include, but are not limited

to:



a. Test Plans, Test Procedures/Scripts, and Test Reports.



b. Contractor provided engineering manuals, reports, and/or design

specifications.



c. Military Standards for Tactical Data Communications.



d. DoD tactical system testing documents or manuals.



(CDRL A001, Pre-Test Support – Test Plan Review Report)



3.1.2 Test Monitoring



The contractor shall monitor the conduct of system and interoperability tests by

verification of adherence to the test plans and test scripts. The test plans and procedures

will be provided to the Contractor by the Government prior to commencement of each



REFERENCE #: M68909JINTAC 4

test. The contractor shall have access to the systems under test and to the SIE test

environment in order to perform this task. The contractor shall take notes on observed

system performance, documenting any anomalies and apparent system failures. Test

observation notes obtained during testing shall be utilized during Post-Test Analysis and

development of the Post-Test Analysis Report.



(CDRL A002, Test Monitoring – Daily Status Report)



3.1.3 Post-Test Analysis



Upon completion of the test, the contractor shall analyze data extraction files PCRs, TRs,

PTRs and STRs in order to validate observed performance characteristics. The contractor

shall generate Trouble Reports and a Post-Test Analysis Report to be submitted to the

Government as a CDRL item for each test assigned. The contractor shall review the test

analysis and provide recommendations on all PCRs, TRs, PTRs and STRs assigned an

operational impact rating in accordance with JITC guidance. At the conclusion of each

Test, the contractor shall evaluate any technical issues related to the operation of the

System Under Test (SUT). This evaluation shall be included in the Post-Test Analysis

Report and is intended to provide the Certifying Official for the system under test with

decision-making information.



(CDRL A003, Post-Test Analysis – Post-Test Analysis Report)

(CDRL A004, Post-Test Analysis – Problem Reports)



3.1.4 Test Review Support



The contractor shall attend Pre-Test Briefs and Post-Test Debriefs associated with the

tests supported by the contractor. In addition, the contractor shall attend Technical

Review Boards at the conclusion of the data analysis cycle in order to provide technical

clarification of any questions regarding test conduct and results. The contractor shall

attend the JARP meetings and be an active participant in review, analysis and

clarification of information pertaining to trouble reports and certification assessment of

the System Under Test. The JINTACCS TSO will notify the contractor no later than ten

(10) working days prior to the meeting attendance requirement.



(CDRL A005, Test Review Support – Joint Analysis Review Panel Meeting Report)



3.2 Joint Message Standards Analysis Support



The contractor shall provide technical and engineering support for the review, analysis

and development of message standards (TDL, VMF, USMTF), and related

interoperability and system documentation. The contractor shall support technical

interoperability meetings and participate in the discussion and proposal of new and

revised interoperability requirements. The individual tasks of Interoperability Document

Review and Interoperability Technical Meeting Support are described in additional detail

below.



3.2.1 Joint Interoperability Document Review

REFERENCE #: M68909JINTAC 5

The contractor shall review, analyze, and provide written evaluations on system

specifications, message standards, Interface Change Proposals (ICPs), and related

interoperability documentation. The contractor shall review assigned documentation to

determine technical accuracy of content and conformance to format requirements.

Documents shall be reviewed and analyzed to determine the impact on command and

control operational requirements documents, existing standardized rules and procedures,

and interoperability of Marine Corps Command and Control Systems. The contractor

shall use the applicable Military Standards, Specifications, and Publications as the basis

for evaluation. As part of Interoperability Document Reviews, the contractor shall use

standard formats provided by the Government to report results of analysis.



Complexity of the documents to be reviewed is classified as simple, 80% (40 hours for review, analysis and reporting).



(CDRL A006, Joint Interoperability Document Review – Evaluation of Interface Change

Proposals)



3.2.2 Joint Interoperability Technical Meeting Support



The contractor shall prepare for, attend and provide technical support to the Marine Corps

representative during Joint or Combined Standards meetings. Following each meeting,

the contractor shall provide a report documenting decisions made as a result of technical

discussions, and the impact of these decisions to the interoperability and performance of

Marine Corps Command and Control Systems.



(CDRL A007, Joint Interoperability Technical Meeting Support – Working Group

Meeting Report)



3.3 Marine Corps Analysis



The contractor shall provide technical and engineering support for the review, analysis

and development of Marine Corps documents that provide Marine Corps users (tactical

systems operators, planners, commanders, interoperability specialist, and tactical system

acquisition personnel) with information that assists them in the performance of their

duties. The contractor shall review, analyze and provide written comments on system

specifications, tactical data link message standards, Joint Network design and Allied

design publications, joint and other service Network Design Documents, and related

interoperability documentation. The contractor shall review and analyze assigned

documentation to determine technical accuracy of content, impact on command and

control operations systems, compliance with existing standardized rules and procedures,

the viability of joint interfaces, and the interoperability of Marine Corps C4I systems.



3.3.1 Marine Corps Technical Interoperability Standards Working Group

Support



The contractor shall prepare for, attend when directed, and provide technical support to

the MCTSSA representative during Marine Corps interoperability meetings. Primary



REFERENCE #: M68909JINTAC 6

support will be provided to the Chairman of the Marine Corps Technical Interoperability

Standards Working Group (TISWG) to assist in development of agendas and track

Marine Corps interoperability issues. Following each meeting, the contractor shall

provide a report documenting decisions made as a result of technical discussions, and the

impact of these decisions to the interoperability and performance of Marine Corps

Command and Control Systems.



(CDRL A008, Marine Corps Technical Interoperability Standards Working Group

Support – Working Group Meeting Minutes)



3.3.2 Marine Corps Training Support



The contractor shall develop/maintain a Joint Interoperability of Tactical Command

Systems (JINTACCS) primer (training package) for use in training Marine Corps

requirements officers, acquisition personnel, and operational forces. The Training Primer

shall include an overview of the information contained in the individual Tactical Data

Exchange Standards (TDL, VMF, USMTF, and others), Joint Interoperability

Certification process and requirements, Joint Tactical Information Distribution System

(JTIDS) Network Design and Net Centric data strategy requirements. The contractor shall

utilize Government training materials when available. When not available, the contractor

shall develop training materials. An annual update shall be provided to the JINTACCS

TSO on all training materials developed by the contractor.



(CDRL A009, Marine Corps Training Support – Training Primer)



3.3.3 The Marine Corps Tactical Data Systems Reference Guide



The Marine Corps Tactical Data Systems (MCTDS) Reference Guide provides a

succinct source of information which describes each tactical data system employed by the

United States Marine Corps, the data links each tactical data system employs, and the

message standards which support the data link. The contractor shall produce updates and

improvements to the document once a year. During this period, one draft update shall be

provided for review and comment by the Government. The contractor shall incorporate

all Government comments to the draft document and provide a final document within 30

days of the Government receipt of the draft document. The contractor shall produce and

distribute copies of the MCTDS Reference Guide to Marine Corps users of the document.

The number of copies and a distribution list for the documents will be provided to the

contractor by separate correspondence. For estimating purposes, 1,500 copies were

produced and distributed in FY05.



(CDRL A010, Marine Corps Tactical Data Systems Reference Guide - Marine Corps

Tactical Data Systems Reference Guide)



3.3.4 Marine Corps Tactical Data Systems Interoperability Test Status Report



The Marine Corps Tactical Data Systems Interoperability Status Report documents the

capabilities of each Marine Corps Tactical Data System to exchange information through

the implementation of a Service, Joint, or Allied message standard and the status of



REFERENCE #: M68909JINTAC 7

Marine Corps validation test or Joint Interoperability Test Command (JITC) Certification

testing of each Marine Corps System. The contractor shall provide updates to this

document as information changes through results of the testing process. A semi-annual

report shall be submitted to the Government.



(CDRL A011, Marine Corps Tactical Data Systems Interoperability Test Status Report -

Marine Corps Tactical Data Systems Interoperability Test Status Report)



3.3.5 Marine Corps System Implementation Document Development



Interoperable Systems Management and Requirements Transformation (iSMART) and

Capabilities and Limitations (C&L) – The development, maintenance and

implementation of the tactical data standards requires detailed knowledge and

understanding of the technical and operational uses of these standards. The iSMART and

C&L are DoD directed efforts that ensure through verification, validation, and use in

certification testing that Marine Corps C4ISR systems are developed and fielded as

interoperable systems. The contractor shall provide technical support in the populating

and maintenance of these databases, and produce reports based on interoperability

analysis of the information contained on these systems.



(CDRL A012, Marine Corps System Implementation Document Development -

iSMART/ Capabilities & Limitation Document Development)



3.3.6 Net Centric Data Modeling and Management



Net Centric Data Management Working Groups – All levels of organization in the

Federal Government have established data management working groups to address data

standardization issues. MCTSSA JINTACCS’ role is to provide technical representation

to multiple working groups within the Marine Corps and DoD. Examples include the

Marine Corps Net Centric Data Working Group, ASD NII Universal Common Core,

Strike Data Management Working Group, and Blue Force Tracking (BFT) Communities

of Interest (COI) currently. The contractor shall provide technical expertise in support of

the migration of tactical C2 data that will assist the Government in adopting the best

overall approach toward net centric operations. The contractor shall produce analytical

reports of technical studies and data modeling efforts conducted in support of the Net

Centric migration of tactical C2 data. Analysis will include comparisons of existing data

standards with data models proposed to meet future net centric requirements. Studies of

logical and physical data models and creation of Extensible Markup Language (XML)

Schemas and Extensible Style Sheet Language Transformations (XSLT) will be end

products.



(CDRL A013, Net Centric Data Modeling and Management - Data Modeling Analysis

Report)

(CDRL A014, Net Centric Data Modeling and Management - Data Management Meeting

Report)



4.0 Deliverables

REFERENCE #: M68909JINTAC 8

4.1 Monthly Status Report



The contractor shall prepare and deliver an electronic monthly status report concurrently

with each invoice presented for payment. The report shall be delivered no later than the

10th of each month. The report shall be delivered in Microsoft Office 2000 Word format.

The report shall include a copy of the Cost Breakdown Report for the reporting period,

the format of which is subject to Government approval. The monthly report shall be sent

via e-mail TBD.



(CDRL A015, Monthly Status Report – Monthly Status Report)



4.2 Cost Breakdown Report



Invoices shall include a Cost Breakdown Report as an itemized spreadsheet delineating

how the billed funds were expended. All items billed must be listed on the report. The

report shall contain all the information as described in CDRL A015, Monthly Status

Report.



4.3 Contract Data Requirements List (CDRL) Items



a. (CDRL A001, Pre-Test Support - Test Plan Review Report)



b. (CDRL A002, Test Monitoring – Daily Status Report)



c. (CDRL A003, Post-Test Analysis - Post-Test Analysis Report)



d. (CDRL A004, Post-Test Analysis – Problem Reports)



e. (CDRL A005, Test Review Support – Joint Analysis Review Panel Meeting

Report)



f. (CDRL A006, Joint Interoperability Document Review – Evaluation of

Interface Change Proposals Report)



g. (CDRL A007, Joint Interoperability Technical Meeting Support – Working

Group Meeting Report)



h. (CDRL A008, Marine Corps Technical Interoperability Standards Working

Group Support – Working Group Meeting Minutes)



i. (CDRL A009, Marine Corps Training Support – Training Primer)



j. (CDRL A010, Marine Corps Tactical Data Systems Reference Guide - Marine

Corps Tactical Data Systems Reference Guide)



k. (CDRL A011, Marine Corps Tactical Data Systems Interoperability Test

Status Report - Marine Corps Tactical Data Systems Interoperability Test Status



REFERENCE #: M68909JINTAC 9

Report)



l. (CDRL A012, Marine Corps System Implementation Document Development

– iSMART/Capabilities & Limitations Document Development)



m. (CDRL A013, Net Centric Data Modeling and Management - Data Modeling

Analysis Report)



n. (CDRL A014, Net Centric Data Modeling and Management - Data

Management Meeting Report)



o. (CDRL A015, Monthly Status Report – Monthly Status Report)



4.4 Delivery Instructions



Deliverables associated with the above specified tasks will be subject to the following

criteria.



4.4.1 Unclassified End Products



Unclassified end products shall be delivered with a letter of transmittal TBD.



4.4.2 Classified End Products



Classified end products shall be delivered directly to the MCTSSA Classified Material

Control Center (CMCC) using normal security channels. A copy of the letter of

transmittal shall be forwarded the JINTACCS TBD. All classified documents shall be

classified in accordance with the NISPOM (DOD Directive 5220.22-M).



4.5 Schedule of Deliveries



The contractor shall provide a written request for all delivery schedule revisions at least

five (5) working days prior to the required delivery date, for Government evaluation and

approval. Revised delivery dates may only be authorized by issuance of a duly executed

delivery order modification to the task order by the Contracting Officer.



5.0 Performance Location



Performance of work associated with this project will be performed primarily at

MCTSSA, Camp Pendleton. The contractor shall be required to travel in order to attend

meetings and briefings. Employees shall work 90% on-site at MCTSSA and 10% offsite

at the Contractor’s facility.



6.0 Inspection/Acceptance of Deliverables



6.1 TBD.





REFERENCE #: M68909JINTAC 10

6.2 Inspection and acceptance of the contract deliverables are the responsibility of the

JINTACCS TBD, except as otherwise specified in the contract. The JINTACCS TBD

will make official acceptance notification to the contractor on all final deliverables

(excluding informal memoranda, etc.) via signature of acceptance on task order.

Rejection of deliverables will be provided to the contractor via written correspondence in

a letter. Minor corrections required to deliverables will be verbally discussed with the

contractor and noted on deliverable products. A revised deliverable shall be resubmitted

to the Government within three (3) working days.



6.3 All report deliverables shall be submitted to the JINTACCS TBD in matching hard

copy and soft copy formats and shall be clearly labeled to indicate content. All soft copy

report deliverables shall be in the Microsoft Office 2000 Suite Word, Excel, or Power

Point format. The JINTACCS TBD will approve any changes in report deliverable

formats in advance of submission.



7.0 Period of Performance



The period of performance for this task order is one (1) year from date specified in the

award, with two (2) one year option periods.



8.0 GOVERNMENT FURNISHED EQUIPMENT AND FACILITIES



8.1 Government Furnished Equipment



No Government Furnished Equipment (GFE) is planned for this task order.



8.2 Access to Government Property



The Government will provide access to the Test Certification Group (TCG) test lab of the

Test Certification Group (TCG) for the performance of tasks under this SOW. Access

outside of the hours of 0730 – 1700 will be requested by the JINTACCS TSO and

approved by the MCTSSA Security Officer at least one (1) working day prior to access.



8.3 Government Furnished Material



The contractor shall furnish their own administrative supplies and office supplies

required for the performance of the subject task order requirements. Access to

Government computers, telephones, office space, and lab space will be furnished by the

Government for work directly in support of this task order conducted primarily at the

Government site. If Government telephones are provided, the Government will not

reimburse the contractor for cell phone charges under Other Direct Costs.



8.4 Government Furnished Information



The Government will provide access to the following automated services in support of

this SOW.





REFERENCE #: M68909JINTAC 11

a. The Government will provide the contractor access to the technical information

required for the performance of the tasking in this SOW.



b. The Government will provide the contractor a Class A (DSN and commercial

long distance) telephone service when determined by the Government to be necessary for

work completion.



b. The Government will provide the contractor a user and mail account on the

MCTSSA SIPRNET domain when determined by the Government to be necessary for

work completion.



c. The Government will provide the contractor a user and email account on the

NMCI to include a CAC card to support PKI access and Marine Corps Web Services

when determined by the Government to be necessary for work completion.



d. The Government will provide the contractor NMCI computer resources when

determined by the Government to be necessary for work completion.



9.0 SECURITY REQUIREMENTS



9.1 Technical tasks associated with this statement of work require access to classified

information and clearance up to the NATO SECRET level. The contractor shall not

divulge any information regarding files, data, processing activities/functions, user ID's,

passwords, or other knowledge that may be gained, to anyone who is not authorized to

have access to such information. Contractor personnel shall abide by all Government

rules, procedures, and standards of conduct.



9.2 The work to be performed under this order as delineated in the DD Form 254,

Attachment (2), involves access to and handling of classified material up to and including

NATO Secret. The requirements of the clause FAR 52.204-2, Security Requirements are

applicable to this order. The contractor shall (1) be responsible for all security aspects of

the work performed under this contract, and (2) assure compliance with the NISPOM

(DOD Directive 5220.22-M).



9.3 A SECRET clearance with NATO access is required for analyst personnel

supporting these tasks.



10.0 PERSONNEL



10.1 Personnel Requirements



The contractor shall provide SME(s) to support the Marine Corps Technical

Interoperability Standards Working Group (TISWG) process, configuration management

of tactical data exchange standards to include Link 11/11B, Link 16, VMF, USMTF, and

JTIDS Network Design and Management. The contractor shall identify and provide

resume(s) for key personnel who are subject matter experts (SME) in Joint

interoperability standards and procedures, interoperability testing/evaluation



REFERENCE #: M68909JINTAC 12

methodologies and requirements, Joint system interfaces and architectures, and

physical/logical data models and their implementation. Specific experience with

operations and message implementation of Marine Corps Tactical Systems is also

required. No single individual is required to be an expert in all areas; however

individuals should collectively have expertise across all areas.



Key personnel shall not be substituted without the permission of the Contracting Officer.

During the term of the contract performance, no personnel substitutions will be permitted

unless such substitutions are necessitated by an individual’s sudden illness, death, or

termination of employment. Requests for approval of substitutions shall be made in

writing with a detailed explanation of the circumstances along with a resume of the

proposed individual. Proposed substitutions shall at minimum have the equivalent

qualifications of the person being replaced.



11.0 Other Direct Cost



11.1 Other Direct Costs (Materials)



Other Direct Costs (Materials) will be pre-approved by the Contracting Officer, and

reimbursed for the actual allowable costs not to exceed the allowable estimate. The

Contracting Officer will give the contractor a written authorization to proceed with the

material purchase. If the contractor proceeds without written authorization, the

contractor shall not be reimbursed.



11.2 Travel Requirements



The contractor is authorized to travel to the locations listed below in support of this effort

when notified by the JINTACCS TSO. Authorized travel shall be in accordance with

DoD Joint Travel Regulations. Actual travel required will vary depending on the

technical issues and schedules as they evolve throughout the period of performance of

this task order.



The following list is the estimated number of trips and locations expected. Each trip is

expected to require only one (1) person.



Purpose of Trip & Number of Location Duration

Meetings

MC TWG meeting (1) Quantico, VA 3 Days

MC EIWG (2) Stafford, VA 3 Days

MC TISWG (4) Stafford, VA 4 Days

IMP/Integration meetings (2) Herndon, VA 3 Days

JCAS Symposium (1) East Coast 5 Days

VMF Subgroup meetings (3) Herndon, VA 5 Days

USMTF CCB/TRP meetings (3) Herndon, VA 5 Days

Interoperability Working Groups (2) East Coast 3 Days

Test WG meetings (1) Fort Huachuca, AZ 3 Days



REFERENCE #: M68909JINTAC 13

Purpose of Trip & Number of Location Duration

Meetings

Data Management WG/COI (4) East Coast 5 Days

Joint Analysis Review Panel (6) Fort Huachuca, AZ 5 Days





12.0 INVOICING



12.1 Invoice



The contractor shall submit an electronic copy of an invoice and any necessary

supporting documentation not more often than once a month via Wide Area Workflow

(WAWF).



The contractor shall be required to implement the DFARS process to submit an electronic

submission of payment request. To implement DFARS 252.232-7003, "ELECTRONIC

SUBMISSION OF PAYMENT REQUEST (MAR 2007)", the United States Marine

Corps (USMC) utilizes Wide Area WorkFlow-Receipt and Acceptance (WAWF-RA) to

electronically process vendor requests for payment. This application allows DoD vendors

to submit and track Invoices and Receipt/ Acceptance documents electronically. The

contractor is required to utilize this system when processing invoices and receiving

reports. The contractor shall (i) ensure an Electronic Business Point of Contact is

designated in Central Contractor Registration at http://www.ccr.gov

and (ii) register to use WAWF-RA at the https://wawf.eb.mil

site, within ten (10) calendar days after award of this contract or

modification. Step by step procedures to register are available at the https://wawf.eb.mil

site.



13.0 ADMINISTRATIVE AUTHORITY



13.1 Contracting Officer



Only the Contracting Officer has the authority to authorize deviations from the terms and

conditions of this order, including deviations from the specifications and requirements

stated herein. In the event the Contractor does deviate, without the issuance of a duly

executed delivery order or modification, such deviation shall be at the risk of, and any

costs related thereto shall be borne by the Contractor.



13.2 Technical Support Officer



TBD------ Technical Support Officer for this task order. The JINTACCS TSO is limited

to providing program specific clarification to the Contractor's Task Leader for this task

order, and does not have the authority to take any action, either directly or indirectly, that

would change the pricing, quality, place-of-performance, delivery schedule, or any other

terms and conditions of this task order or to direct work that goes beyond the scope of

this task orders statement of work. When the JINTACCS TSO requests effort outside the

existing scope of this task order, the Contractor shall promptly notify the Contracting



REFERENCE #: M68909JINTAC 14

Officer in writing. No action shall be taken by the Contractor under such direction until

the Contracting Officer has issued a contractual change or otherwise resolved the issue.









REFERENCE #: M68909JINTAC 15


Related docs
Other docs by HC1111261656
O U T L I N E
Views: 0  |  Downloads: 0
Last Will and Testament
Views: 0  |  Downloads: 0
slsj
Views: 3  |  Downloads: 0
DAMI-CP &nb
Views: 1  |  Downloads: 0
Contract Meeting
Views: 1  |  Downloads: 0
ACT 2
Views: 0  |  Downloads: 0
Examination of the Head and Neck
Views: 0  |  Downloads: 0
Head - Neck
Views: 0  |  Downloads: 0
Kapak Hesabi
Views: 4  |  Downloads: 0
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!